
Hello Gerrit.ovirt.org will be upgraded later today. Approximate start time is 4PM UTC. During the upgrade service will be shut down and so will not be available. -- Denis Volkov

Hello I'm starting upgrade, gerrit will be unavailable -- Denis Volkov

On 21. 1. 2022, at 17:05, Denis Volkov <dvolkov@redhat.com> wrote:
Hello
I'm starting upgrade, gerrit will be unavailable
ETA? any complications?
-- Denis Volkov
_______________________________________________ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/IOO66W7HHFP6KA...

Hello Upgrade to the latest version of 2.16 branch is finished. Gerrit is up and running. 2.16 is the last version that supports separate ReviewDb, so as a preparation for future upgrades, migration from ReviewDb to NoteDb was done. There are no more changes planned for today. In case of issues please create ticket in issue tracking system: https://issues.redhat.com/projects/CPDEVOPS/issues -- Denis Volkov

Hello Next iteration of gertit.ovirt.org upgrade is planned later today. Approximate start time is 4PM UTC. During the upgrade service will be shut down and so will not be available. -- Denis Volkov

Hello I'm starting upgrade. Gerrit will be unavailable On Fri, Jan 28, 2022 at 2:05 PM Denis Volkov <dvolkov@redhat.com> wrote:
Hello
Next iteration of gertit.ovirt.org upgrade is planned later today. Approximate start time is 4PM UTC. During the upgrade service will be shut down and so will not be available.
--
Denis Volkov
-- Denis Volkov Red Hat <https://www.redhat.com> <https://www.redhat.com>

Hello Upgrade to version 3.4.3 is finished. Gerrit is up and running. In case of issues please create ticket in issue tracking system: https://issues.redhat.com/projects/CPDEVOPS/issues -- Denis Volkov

Hi, thanks for handling the upgrade. With the new version it's not possible anymore to get contents of the comments which we need for OST gating. i.e. for this patch: https://gerrit.ovirt.org/c/ovirt-system-tests/+/118398 if you try: curl -L https://gerrit.ovirt.org/changes/118398/detail | \ sed 1d | \ jq -r '.messages[]' you'll see for one of my last comments: ... "message": "Patch Set 1:\n\n(1 comment)" ... but there's no "ci ost" string, which is what I actually wrote. It's probably because of the new "comment chips" feature. If it's possible and there are no objections could you please try turning it off? Regards, Marcin On 1/28/22 18:48, Denis Volkov wrote:
Hello
Upgrade to version 3.4.3 is finished. Gerrit is up and running.
In case of issues please create ticket in issue tracking system: https://issues.redhat.com/projects/CPDEVOPS/issues <https://issues.redhat.com/projects/CPDEVOPS/issues>
--
Denis Volkov
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/I676ITKOHKLH4Q...

Hello Marcin Sorry for the late reply I will try checking if that feature can be disabled. Meanwhile I think you could use the `comments` url to get the comments directly: `curl -s -L https://gerrit.ovirt.org/changes/118398/comments|sed 1d|jq '.'` If needed, field `change_message_id` can be used to link message in `details` and `comments` URLs On Mon, Jan 31, 2022 at 12:32 PM Marcin Sobczyk <msobczyk@redhat.com> wrote:
Hi,
thanks for handling the upgrade.
With the new version it's not possible anymore to get contents of the comments which we need for OST gating.
i.e. for this patch:
https://gerrit.ovirt.org/c/ovirt-system-tests/+/118398
if you try:
curl -L https://gerrit.ovirt.org/changes/118398/detail | \ sed 1d | \ jq -r '.messages[]'
you'll see for one of my last comments:
... "message": "Patch Set 1:\n\n(1 comment)" ...
but there's no "ci ost" string, which is what I actually wrote.
It's probably because of the new "comment chips" feature. If it's possible and there are no objections could you please try turning it off?
Regards, Marcin
On 1/28/22 18:48, Denis Volkov wrote:
Hello
Upgrade to version 3.4.3 is finished. Gerrit is up and running.
In case of issues please create ticket in issue tracking system: https://issues.redhat.com/projects/CPDEVOPS/issues <https://issues.redhat.com/projects/CPDEVOPS/issues>
--
Denis Volkov
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/I676ITKOHKLH4Q...
-- Denis Volkov Red Hat <https://www.redhat.com> <https://www.redhat.com>

On 2/1/22 09:58, Denis Volkov wrote:
Hello Marcin
Sorry for the late reply
I will try checking if that feature can be disabled. Meanwhile I think you could use the `comments` url to get the comments directly: `curl -s -L https://gerrit.ovirt.org/changes/118398/comments|sed <https://gerrit.ovirt.org/changes/118398/comments|sed> 1d|jq '.'` If needed, field `change_message_id` can be used to link message in `details` and `comments` URLs
Hi, yeah, I was able to use the /comments endpoint for my purposes, so we can stick with comment chips (although I still find them really weird :) ). Thanks, Marcin
On Mon, Jan 31, 2022 at 12:32 PM Marcin Sobczyk <msobczyk@redhat.com <mailto:msobczyk@redhat.com>> wrote:
Hi,
thanks for handling the upgrade.
With the new version it's not possible anymore to get contents of the comments which we need for OST gating.
i.e. for this patch:
https://gerrit.ovirt.org/c/ovirt-system-tests/+/118398 <https://gerrit.ovirt.org/c/ovirt-system-tests/+/118398>
if you try:
curl -L https://gerrit.ovirt.org/changes/118398/detail <https://gerrit.ovirt.org/changes/118398/detail> | \ sed 1d | \ jq -r '.messages[]'
you'll see for one of my last comments:
... "message": "Patch Set 1:\n\n(1 comment)" ...
but there's no "ci ost" string, which is what I actually wrote.
It's probably because of the new "comment chips" feature. If it's possible and there are no objections could you please try turning it off?
Regards, Marcin
On 1/28/22 18:48, Denis Volkov wrote: > Hello > > Upgrade to version 3.4.3 is finished. Gerrit is up and running. > > In case of issues please create ticket in issue tracking system: > https://issues.redhat.com/projects/CPDEVOPS/issues <https://issues.redhat.com/projects/CPDEVOPS/issues> > <https://issues.redhat.com/projects/CPDEVOPS/issues <https://issues.redhat.com/projects/CPDEVOPS/issues>> > > -- > > Denis Volkov > > > > _______________________________________________ > Users mailing list -- users@ovirt.org <mailto:users@ovirt.org> > To unsubscribe send an email to users-leave@ovirt.org <mailto:users-leave@ovirt.org> > Privacy Statement: https://www.ovirt.org/privacy-policy.html <https://www.ovirt.org/privacy-policy.html> > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ <https://www.ovirt.org/community/about/community-guidelines/> > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/I676ITKOHKLH4Q... <https://lists.ovirt.org/archives/list/users@ovirt.org/message/I676ITKOHKLH4Q7CMRGVSYHYYTPKKHXA/>
--
Denis Volkov
Red Hat <https://www.redhat.com>

Hi I did not find a way to tweak this comment chips behavior, so it looks like we'd need to stay with them On Tue, Feb 1, 2022 at 10:40 AM Marcin Sobczyk <msobczyk@redhat.com> wrote:
Hi, yeah, I was able to use the /comments endpoint for my purposes, so we can stick with comment chips (although I still find them really weird :) ).
Thanks, Marcin
-- Denis Volkov
participants (3)
-
Denis Volkov
-
Marcin Sobczyk
-
Michal Skrivanek