- Infra - oVirt List Archives

[CQ]: 103551, 3 (ovirt-engine-nodejs-modules) failed "ovirt-4.3" system tests
by oVirt Jenkins 25 Sep '19

25 Sep '19

Change 103551,3 (ovirt-engine-nodejs-modules) is probably the reason behind recent system test failures in the "ovirt-4.3" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/103551/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2181/

1 0

[CQ]: 98356,4 (ovirt-provider-ovn) failed "ovirt-4.3" system tests
by oVirt Jenkins 25 Sep '19

25 Sep '19

Change 98356,4 (ovirt-provider-ovn) is probably the reason behind recent system test failures in the "ovirt-4.3" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/98356/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2179/

1 0

[JIRA] (OVIRT-2803) Re: CI is not triggered for pushed gerrit updates
by Barak Korren (oVirt JIRA) 25 Sep '19

25 Sep '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2803?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2803: ------------------------------------- This is a known issue - tacker ticket: https://ovirt-jira.atlassian.net/browse/OVIRT-2802 Will close new ticket as a duplicate On Wed, 25 Sep 2019 at 13:08, Nir Soffer <nsoffer(a)redhat.com> wrote: > On Wed, Sep 25, 2019 at 12:42 PM Amit Bawer <abawer(a)redhat.com> wrote: > >> CI has stopped from being triggered for pushed gerrit updates. >> > > Adding infra-suppoort(a)ovirt.org - this file a bug in infra bug tracker. > > Example at: https://gerrit.ovirt.org/#/c/103320/ >> last PS did not trigger CI tests. >> > > More examples: > https://gerrit.ovirt.org/c/103490/2 > https://gerrit.ovirt.org/c/103455/4 > > Last triggered build was seen here: > https://gerrit.ovirt.org/c/103549/1 > Sep 24 18:42. > > "ci test" also did not trigger a build, but I tried now again using "ci > please test" > and it worked. > https://gerrit.ovirt.org/c/103490/2#message-8d40f6de_bd0564ff > > Maybe someone changed the pattern? > > > -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted > Re: CI is not triggered for pushed gerrit updates > ------------------------------------------------- > > Key: OVIRT-2803 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2803 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > On Wed, Sep 25, 2019 at 12:42 PM Amit Bawer <abawer(a)redhat.com> wrote: > > CI has stopped from being triggered for pushed gerrit updates. > > > Adding infra-suppoort(a)ovirt.org - this file a bug in infra bug tracker. > Example at: https://gerrit.ovirt.org/#/c/103320/ > > last PS did not trigger CI tests. > > > More examples: > https://gerrit.ovirt.org/c/103490/2 > https://gerrit.ovirt.org/c/103455/4 > Last triggered build was seen here: > https://gerrit.ovirt.org/c/103549/1 > Sep 24 18:42. > "ci test" also did not trigger a build, but I tried now again using "ci > please test" > and it worked. > https://gerrit.ovirt.org/c/103490/2#message-8d40f6de_bd0564ff > Maybe someone changed the pattern? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100111)

1 0

[JIRA] (OVIRT-2803) Re: CI is not triggered for pushed gerrit updates
by Ehud Yonasi (oVirt JIRA) 25 Sep '19

25 Sep '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2803?page=com.atlassian.jira.… ] Ehud Yonasi updated OVIRT-2803: ------------------------------- Resolution: Fixed Status: Done (was: To Do) > Re: CI is not triggered for pushed gerrit updates > ------------------------------------------------- > > Key: OVIRT-2803 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2803 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > On Wed, Sep 25, 2019 at 12:42 PM Amit Bawer <abawer(a)redhat.com> wrote: > > CI has stopped from being triggered for pushed gerrit updates. > > > Adding infra-suppoort(a)ovirt.org - this file a bug in infra bug tracker. > Example at: https://gerrit.ovirt.org/#/c/103320/ > > last PS did not trigger CI tests. > > > More examples: > https://gerrit.ovirt.org/c/103490/2 > https://gerrit.ovirt.org/c/103455/4 > Last triggered build was seen here: > https://gerrit.ovirt.org/c/103549/1 > Sep 24 18:42. > "ci test" also did not trigger a build, but I tried now again using "ci > please test" > and it worked. > https://gerrit.ovirt.org/c/103490/2#message-8d40f6de_bd0564ff > Maybe someone changed the pattern? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100111)

1 0

CI is not triggered for pushed gerrit updates
by Amit Bawer 25 Sep '19

25 Sep '19

CI has stopped from being triggered for pushed gerrit updates. Example at: https://gerrit.ovirt.org/#/c/103320/ last PS did not trigger CI tests. Please advise.

3 3

[JIRA] (OVIRT-2803) Re: CI is not triggered for pushed gerrit updates
by Ehud Yonasi (oVirt JIRA) 25 Sep '19

25 Sep '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2803?page=com.atlassian.jira.… ] Ehud Yonasi commented on OVIRT-2803: ------------------------------------ Hey, There was a problem with the gerrit trigger plugin and we ended up upgrading it and restarting jenkins. We didn’t change the pattern to trigger a build. Closing as duplicated. > Re: CI is not triggered for pushed gerrit updates > ------------------------------------------------- > > Key: OVIRT-2803 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2803 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > On Wed, Sep 25, 2019 at 12:42 PM Amit Bawer <abawer(a)redhat.com> wrote: > > CI has stopped from being triggered for pushed gerrit updates. > > > Adding infra-suppoort(a)ovirt.org - this file a bug in infra bug tracker. > Example at: https://gerrit.ovirt.org/#/c/103320/ > > last PS did not trigger CI tests. > > > More examples: > https://gerrit.ovirt.org/c/103490/2 > https://gerrit.ovirt.org/c/103455/4 > Last triggered build was seen here: > https://gerrit.ovirt.org/c/103549/1 > Sep 24 18:42. > "ci test" also did not trigger a build, but I tried now again using "ci > please test" > and it worked. > https://gerrit.ovirt.org/c/103490/2#message-8d40f6de_bd0564ff > Maybe someone changed the pattern? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100111)

1 0

[JIRA] (OVIRT-2803) Re: CI is not triggered for pushed gerrit updates
by Nir Soffer (oVirt JIRA) 25 Sep '19

25 Sep '19

Nir Soffer created OVIRT-2803: --------------------------------- Summary: Re: CI is not triggered for pushed gerrit updates Key: OVIRT-2803 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2803 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra On Wed, Sep 25, 2019 at 12:42 PM Amit Bawer <abawer(a)redhat.com> wrote: > CI has stopped from being triggered for pushed gerrit updates. > Adding infra-suppoort(a)ovirt.org - this file a bug in infra bug tracker. Example at: https://gerrit.ovirt.org/#/c/103320/ > last PS did not trigger CI tests. > More examples: https://gerrit.ovirt.org/c/103490/2 https://gerrit.ovirt.org/c/103455/4 Last triggered build was seen here: https://gerrit.ovirt.org/c/103549/1 Sep 24 18:42. "ci test" also did not trigger a build, but I tried now again using "ci please test" and it worked. https://gerrit.ovirt.org/c/103490/2#message-8d40f6de_bd0564ff Maybe someone changed the pattern? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100111)

1 0

[JIRA] (OVIRT-2802) Gerrit trigger plugin not working on Jenkins
by Evgheni Dereveanchin (oVirt JIRA) 25 Sep '19

25 Sep '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2802?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2802: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Gerrit trigger plugin not working on Jenkins > -------------------------------------------- > > Key: OVIRT-2802 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2802 > Project: oVirt - virtualization made easy > Issue Type: Outage > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > Priority: Highest > > Jenkins can't connect to Gerrit so CI doesn't trigger. I've seen some exceptions in the logs and the staging system works just fine so it's likely a fault in the plugin. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100111)

1 0

[JIRA] (OVIRT-2802) Gerrit trigger plugin not working on Jenkins
by Evgheni Dereveanchin (oVirt JIRA) 25 Sep '19

25 Sep '19

Evgheni Dereveanchin created OVIRT-2802: ------------------------------------------- Summary: Gerrit trigger plugin not working on Jenkins Key: OVIRT-2802 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2802 Project: oVirt - virtualization made easy Issue Type: Outage Reporter: Evgheni Dereveanchin Assignee: infra Priority: Highest Jenkins can't connect to Gerrit so CI doesn't trigger. I've seen some exceptions in the logs and the staging system works just fine so it's likely a fault in the plugin. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100111)

1 0

[CQ]: 102936, 5 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 24 Sep '19

24 Sep '19

A system test invoked by the "ovirt-master" change queue including change 102936,5 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 102934,5 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 102934,5 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/102936/5 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/102934/5 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/16036/

1 0