- Infra - oVirt List Archives

[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 25 Sep '19

25 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

oVirt infra daily report - unstable production jobs - 958
by jenkins＠jenkins.phx.ovirt.org 25 Sep '19

25 Sep '19

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/958//artifact/exported-a… Cheers, Jenkins

1 0

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

25 Sep '19

A system test invoked by the "ovirt-master" change queue including change 102935,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/102935/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/16032/

1 0

[CQ]: 102934,5 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 24 Sep '19

24 Sep '19

Change 102934,5 (ovirt-engine) is probably the reason behind recent system test failures in the "ovirt-master" 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/102934/5 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/16028/

1 0

[CQ]: 103476,2 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 24 Sep '19

24 Sep '19

Change 103476,2 (vdsm) is probably the reason behind recent system test failures in the "ovirt-master" 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/103476/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/16022/

1 0

[oVirt CI] standard-enqueue - Build #24069 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 24 Sep '19

24 Sep '19

Build: http://jenkins.ovirt.org/job/standard-enqueue/24069/ Build Name: #24069 Build Description: Gerrit: 103524 - ovirt-engine (4.2) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/103524 - title: core: Fill jackson deserialization whitelist - project: ovirt-engine - branch: ovirt-engine-4.2 - author: Martin Peřina <mperina(a)redhat.com>

1 0

[oVirt CI] standard-enqueue - Build #24065 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 24 Sep '19

24 Sep '19

Build: http://jenkins.ovirt.org/job/standard-enqueue/24065/ Build Name: #24065 Build Description: Gerrit: 103533 - ovirt-engine (4.3.5.z) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/103533 - title: build: post ovirt-engine-4.3.5.5 - project: ovirt-engine - branch: ovirt-engine-4.3.5.z - author: Sandro Bonazzola <sbonazzo(a)redhat.com>

1 2

[JIRA] (OVIRT-2798) add ovirt-provider-ovn project to the new gating system
by Anton Marchukov (oVirt JIRA) 24 Sep '19

24 Sep '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2798?page=com.atlassian.jira.… ] Anton Marchukov commented on OVIRT-2798: ---------------------------------------- We are currently working on running OST in gating and can switch once it is finished. > add ovirt-provider-ovn project to the new gating system > ------------------------------------------------------- > > Key: OVIRT-2798 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2798 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Miguel Duarte de Mora Barroso > Assignee: infra > > Hi, > I'd like to request that ovirt-provider-ovn is added to the new gating system. > Thanks in advance, > Miguel -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100111)

1 0

[JIRA] (OVIRT-1448) Enable devs to specifiy patch dependencies for OST
by Barak Korren (oVirt JIRA) 24 Sep '19

24 Sep '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1448?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1448: ------------------------------------- well, we're probably not going to implement this, but as long as we use CQ - we can still get issues where dependent patches get tested alone > Enable devs to specifiy patch dependencies for OST > -------------------------------------------------- > > Key: OVIRT-1448 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1448 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: change-queue > > We have an issue with our system ATM where if there are patches for different projects that depend on one another, the system is unaware of that dependency. > What typically happens in this scenario is that sending the dependent patch makes the experimental test fail and keep failing until the other patch is also merged. > The change queue will handle this better, but the typical behaviour for it would be to reject both patches, unless they are somehow coordinated to make it into the same test. > The change queue core code already includes the ability to track and understand dependencies between changes. What is missing is the ability for developers to specify theses dependencies. > We would probably want to adopt OpenStack's convention here. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100111)

1 0

[JIRA] (OVIRT-2801) ovirt-provider-ovn needs to be built downstream: last built: '1.2.26' while last tagged is '4.2.2.5'
by Sandro Bonazzola (oVirt JIRA) 24 Sep '19

24 Sep '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2801?page=com.atlassian.jira.… ] Sandro Bonazzola reassigned OVIRT-2801: --------------------------------------- Assignee: Sandro Bonazzola (was: infra) > ovirt-provider-ovn needs to be built downstream: last built: '1.2.26' while last tagged is '4.2.2.5' > ---------------------------------------------------------------------------------------------------- > > Key: OVIRT-2801 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2801 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Sandro Bonazzola > Assignee: Sandro Bonazzola > > Hi, > just noticed this weird error while checking latest available version with > my tools: > ovirt-provider-ovn needs to be built downstream: last built: '1.2.26' while > last tagged is '4.2.2.5' > and checking https://github.com/oVirt/ovirt-provider-ovn/releases I indeed > see > on 20 Mar 2018 ovirt-engine-4.2.2.5 tag. > can you please check what screwed up ovirt-provider-ovn tagging? > Thanks, > -- > Sandro Bonazzola > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100110)

1 0

oVirt infra daily report - unstable production jobs - 957
by jenkins＠jenkins.phx.ovirt.org 24 Sep '19

24 Sep '19

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/957//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: ceeadd7 (ovirt-web-ui) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 23 Sep '19

23 Sep '19

A system test invoked by the "ovirt-master" change queue including change ceeadd7 (ovirt-web-ui) failed. However, this change seems not to be the root cause for this failure. Change b1ee64c (ovirt-web-ui) 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 b1ee64c (ovirt-web-ui) 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://github.com/oVirt/ovirt-web-ui/commit/ceeadd7fe44a51ff5f8058bf425680… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-web-ui/commit/b1ee64c14323aca370dc5470426e87… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/16011/

1 0

[CQ]: f8c4d90 (ovirt-web-ui) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 23 Sep '19

23 Sep '19

A system test invoked by the "ovirt-master" change queue including change f8c4d90 (ovirt-web-ui) failed. However, this change seems not to be the root cause for this failure. Change b1ee64c (ovirt-web-ui) 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 b1ee64c (ovirt-web-ui) 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://github.com/oVirt/ovirt-web-ui/commit/f8c4d909dcd43905770f8701f9f334… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-web-ui/commit/b1ee64c14323aca370dc5470426e87… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/16006/

1 0

[CQ]: 9c0c59c (v2v-conversion-host) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 23 Sep '19

23 Sep '19

A system test invoked by the "ovirt-master" change queue including change 9c0c59c (v2v-conversion-host) failed. However, this change seems not to be the root cause for this failure. Change 6797e49 (v2v-conversion-host) 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 6797e49 (v2v-conversion-host) 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://github.com/oVirt/v2v-conversion-host/commit/9c0c59c9a0bbaf7c2cccee4… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/v2v-conversion-host/commit/6797e499cb10860cbe4684c… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/16001/

1 0

[CQ]: ceeadd7 (ovirt-web-ui) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 23 Sep '19

23 Sep '19

A system test invoked by the "ovirt-4.3" change queue including change ceeadd7 (ovirt-web-ui) failed. However, this change seems not to be the root cause for this failure. Change b1ee64c (ovirt-web-ui) 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 b1ee64c (ovirt-web-ui) 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://github.com/oVirt/ovirt-web-ui/commit/ceeadd7fe44a51ff5f8058bf425680… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-web-ui/commit/b1ee64c14323aca370dc5470426e87… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2163/

1 0

[JIRA] (OVIRT-2801) ovirt-provider-ovn needs to be built downstream: last built: '1.2.26' while last tagged is '4.2.2.5'
by Sandro Bonazzola (oVirt JIRA) 23 Sep '19

23 Sep '19

Sandro Bonazzola created OVIRT-2801: --------------------------------------- Summary: ovirt-provider-ovn needs to be built downstream: last built: '1.2.26' while last tagged is '4.2.2.5' Key: OVIRT-2801 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2801 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Sandro Bonazzola Assignee: infra Hi, just noticed this weird error while checking latest available version with my tools: ovirt-provider-ovn needs to be built downstream: last built: '1.2.26' while last tagged is '4.2.2.5' and checking https://github.com/oVirt/ovirt-provider-ovn/releases I indeed see on 20 Mar 2018 ovirt-engine-4.2.2.5 tag. can you please check what screwed up ovirt-provider-ovn tagging? Thanks, -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100110)

1 0

[CQ]: f8c4d90 (ovirt-web-ui) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 23 Sep '19

23 Sep '19

A system test invoked by the "ovirt-4.3" change queue including change f8c4d90 (ovirt-web-ui) failed. However, this change seems not to be the root cause for this failure. Change b1ee64c (ovirt-web-ui) 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 b1ee64c (ovirt-web-ui) 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://github.com/oVirt/ovirt-web-ui/commit/f8c4d909dcd43905770f8701f9f334… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-web-ui/commit/b1ee64c14323aca370dc5470426e87… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2161/

1 0

[CQ]: 103226,15 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 23 Sep '19

23 Sep '19

Change 103226,15 (ovirt-engine) is probably the reason behind recent system test failures in the "ovirt-master" 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/103226/15 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15997/

1 0

[CQ]: 9c0c59c (v2v-conversion-host) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 23 Sep '19

23 Sep '19

A system test invoked by the "ovirt-master" change queue including change 9c0c59c (v2v-conversion-host) failed. However, this change seems not to be the root cause for this failure. Change 6797e49 (v2v-conversion-host) 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 6797e49 (v2v-conversion-host) 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://github.com/oVirt/v2v-conversion-host/commit/9c0c59c9a0bbaf7c2cccee4… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/v2v-conversion-host/commit/6797e499cb10860cbe4684c… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15992/

2 1

[JIRA] (OVIRT-2212) Document the steps needed to add a new distro for CI slaves
by Evgheni Dereveanchin (oVirt JIRA) 23 Sep '19

23 Sep '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2212?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2212: ------------------------------------------- Assignee: Shlomi Zidmi (was: infra) > Document the steps needed to add a new distro for CI slaves > ----------------------------------------------------------- > > Key: OVIRT-2212 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2212 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Documentation, Jenkins Slaves > Reporter: Evgheni Dereveanchin > Assignee: Shlomi Zidmi > > Adding a new distro/architecture to CI involves multiple steps like installing software, creating users, managing software mirrors. This process needs to be documented on ReadTheDocs -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100110)

1 0

[CQ]: 9c0c59c (v2v-conversion-host) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 23 Sep '19

23 Sep '19

A system test invoked by the "ovirt-4.3" change queue including change 9c0c59c (v2v-conversion-host) failed. However, this change seems not to be the root cause for this failure. Change 6797e49 (v2v-conversion-host) 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 6797e49 (v2v-conversion-host) 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://github.com/oVirt/v2v-conversion-host/commit/9c0c59c9a0bbaf7c2cccee4… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/v2v-conversion-host/commit/6797e499cb10860cbe4684c… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2158/

1 0

[JIRA] (OVIRT-2800) gerrit.ovirt.org crash 23.09.2019
by Evgheni Dereveanchin (oVirt JIRA) 23 Sep '19

23 Sep '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2800?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2800: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > gerrit.ovirt.org crash 23.09.2019 > --------------------------------- > > Key: OVIRT-2800 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2800 > Project: oVirt - virtualization made easy > Issue Type: Outage > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > Priority: High > > Gerrit went down for ~6 minutes due to an OOM today. Logging a ticket to understand the reason and fix it. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100110)

1 0

[JIRA] (OVIRT-2268) Enable IPv6 for resources.ovirt.org
by Eyal Edri (oVirt JIRA) 23 Sep '19

23 Sep '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2268?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2268: ---------------------------------- [~accountid:557058:caa507e4-2696-4f45-8da5-d2585a4bb794] [~accountid:557058:06620dac-7815-415e-9b2a-b834ef470861] perhaps we can mirror just ovirt snapshots to OSAS community cage, same as we did with Glance? it should be around 25 GB for master and 4.3 content. > Enable IPv6 for resources.ovirt.org > ----------------------------------- > > Key: OVIRT-2268 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2268 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt Infra > Reporter: Dominik Holler > Assignee: infra > > To allow access to resources.ovirt.org in IPv6 only setups, IPv6 should be enabled for resources.ovirt.org. > This would allow users in IPv6 only setups to install oVirt. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100110)

1 0

[JIRA] (OVIRT-2268) Enable IPv6 for resources.ovirt.org
by Eyal Edri (oVirt JIRA) 23 Sep '19

23 Sep '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2268?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2268: ---------------------------------- For now PHX2 (our DC) doesn’t support IPV6 and also our future platform won’t support it from day 1 (PSI). The only solution, for now, is to use one of the mirrors of oVirt available here: [https://www.ovirt.org/develop/infra/repository-mirrors.html|https://www.ovi…] The only problem is that it doesn’t include non-released oVirt content. > Enable IPv6 for resources.ovirt.org > ----------------------------------- > > Key: OVIRT-2268 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2268 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt Infra > Reporter: Dominik Holler > Assignee: infra > > To allow access to resources.ovirt.org in IPv6 only setups, IPv6 should be enabled for resources.ovirt.org. > This would allow users in IPv6 only setups to install oVirt. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100110)

1 0

[JIRA] (OVIRT-2800) gerrit.ovirt.org crash 23.09.2019
by Evgheni Dereveanchin (oVirt JIRA) 23 Sep '19

23 Sep '19

Evgheni Dereveanchin created OVIRT-2800: ------------------------------------------- Summary: gerrit.ovirt.org crash 23.09.2019 Key: OVIRT-2800 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2800 Project: oVirt - virtualization made easy Issue Type: Outage Reporter: Evgheni Dereveanchin Assignee: infra Priority: High Gerrit went down for ~6 minutes due to an OOM today. Logging a ticket to understand the reason and fix it. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100110)

1 0

[JIRA] (OVIRT-2242) Improve Hosted Engine tests since it's the common way users use oVirt
by Eyal Edri (oVirt JIRA) 23 Sep '19

23 Sep '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2242?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2242: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > Improve Hosted Engine tests since it's the common way users use oVirt > --------------------------------------------------------------------- > > Key: OVIRT-2242 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2242 > Project: oVirt - virtualization made easy > Issue Type: Epic > Reporter: Gal Ben Haim > Assignee: infra > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100110)

1 0

[JIRA] (OVIRT-2212) Document the steps needed to add a new distro for CI slaves
by Eyal Edri (oVirt JIRA) 23 Sep '19

23 Sep '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2212?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2212: ---------------------------------- [~accountid:557058:caa507e4-2696-4f45-8da5-d2585a4bb794] is this something [~accountid:5c977456c430371a3c67dbf6] can handle? now that he helped with upgrading to new Fedora? > Document the steps needed to add a new distro for CI slaves > ----------------------------------------------------------- > > Key: OVIRT-2212 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2212 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Documentation, Jenkins Slaves > Reporter: Evgheni Dereveanchin > Assignee: infra > > Adding a new distro/architecture to CI involves multiple steps like installing software, creating users, managing software mirrors. This process needs to be documented on ReadTheDocs -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100110)

1 0

[JIRA] (OVIRT-1866) Use PERFORMANCE_OPTIMIZED pipelines instead of MAX_SURVIVABILITY
by Eyal Edri (oVirt JIRA) 23 Sep '19

23 Sep '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1866?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-1866: ---------------------------------- [~accountid:557058:caa507e4-2696-4f45-8da5-d2585a4bb794] [~accountid:557058:5ca52a09-2675-4285-a044-12ad20f6166a] is this something we can check as part of further optimizing the Jenkins server? > Use PERFORMANCE_OPTIMIZED pipelines instead of MAX_SURVIVABILITY > ---------------------------------------------------------------- > > Key: OVIRT-1866 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1866 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Master > Reporter: Daniel Belenky > Assignee: infra > Labels: jenkins > > It seems that pipelines now have support to configure their behavior of serialization of objects, and since we know that this serialization never worked for us as we'd expect it to, maybe we should consider using PERFORMANCE_OPTIMIZED mode which will avoid serializing and maybe boost the performance. > [Link to subject in jenkincci-dev google|https://groups.google.com/forum/#!msg/jenkinsci-dev/F4zcOWLI32w/51qi…] -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100110)

1 0

[JIRA] (OVIRT-1678) Move gerrit-admin project to be standard CI
by Eyal Edri (oVirt JIRA) 23 Sep '19

23 Sep '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1678?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-1678: ---------------------------------- [~accountid:557058:5ca52a09-2675-4285-a044-12ad20f6166a] can it be done by [~accountid:5c977456c430371a3c67dbf6] as part of learning STD-CI? > Move gerrit-admin project to be standard CI > ------------------------------------------- > > Key: OVIRT-1678 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1678 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Gerrit/git, Gerrit Hooks > Reporter: Eyal Edri > Assignee: infra > > Since we're moving all projects on CI to be a std-ci project ( i.e have automation/ dir with all the relevant scripts inside ), we should also move the gerrit-admin project which holds all the code for the Gerrit hooks. > This will help lay the ground for adding unit-tests and deployments for the hooks in a standard way. > I would start with adding a 'check-patch.sh' script which will do basic sanity on the code, maybe using partner-bugizlla instance and a test bug for testing the hooks. > It's also a great way to learn more about how to create a stanard CI project. > More info on it can be found on the infra docs page: > http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Build_and_test_standard… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100110)

1 0

[JIRA] (OVIRT-1448) Enable devs to specifiy patch dependencies for OST
by Eyal Edri (oVirt JIRA) 23 Sep '19

23 Sep '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1448?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-1448: ---------------------------------- [~accountid:557058:5fc78873-359e-47c9-aa0b-4845b0da8143] can we close this since patch dependencies will be included as part of the Zuul deployment? > Enable devs to specifiy patch dependencies for OST > -------------------------------------------------- > > Key: OVIRT-1448 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1448 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: change-queue > > We have an issue with our system ATM where if there are patches for different projects that depend on one another, the system is unaware of that dependency. > What typically happens in this scenario is that sending the dependent patch makes the experimental test fail and keep failing until the other patch is also merged. > The change queue will handle this better, but the typical behaviour for it would be to reject both patches, unless they are somehow coordinated to make it into the same test. > The change queue core code already includes the ability to track and understand dependencies between changes. What is missing is the ability for developers to specify theses dependencies. > We would probably want to adopt OpenStack's convention here. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100110)

1 0

[JIRA] (OVIRT-2002) Sun-setting foreman and puppet for oVirt
by Eyal Edri (oVirt JIRA) 23 Sep '19

23 Sep '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2002?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2002: ---------------------------------- [~accountid:557058:caa507e4-2696-4f45-8da5-d2585a4bb794] I suggest to split this ticket to 2 at least, and focusing on dropping puppet in favor of Ansible. Right now we only have Jenkins server left and resources that are still using puppet? > Sun-setting foreman and puppet for oVirt > ----------------------------------------- > > Key: OVIRT-2002 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2002 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Eyal Edri > Assignee: infra > > This is a tracking ticket for an effort to stop using Foreman and puppet on oVirt. > Work has already begun to decouple Jenkins slaves from puppet by using glboal_setup.sh scripts, however, there are still services that use it and foreman for user mgmt and production VMs. > Maintaining the foreman and puppet services including future required upgrades for security or bug fixing takes time and effort from the team without too much value. > We should look into alternatives that won't require maintaining new services and reduce load from the team, > E.g - using Ansible playbooks to deploy servers instead of puppet and using a different way to handle users ( Ansible also ? ) > Please use this as a parent ticket to track all sub-tasks relevant to this effort. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100110)

1 0

[JIRA] (OVIRT-2799) Fix HOST SSH warn messages on Gerrit (ssh_host_ecdsa_384_key: Invalid DER: object is not an OID: SEQUENCE)
by Eyal Edri (oVirt JIRA) 23 Sep '19

23 Sep '19

Eyal Edri created OVIRT-2799: -------------------------------- Summary: Fix HOST SSH warn messages on Gerrit (ssh_host_ecdsa_384_key: Invalid DER: object is not an OID: SEQUENCE) Key: OVIRT-2799 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2799 Project: oVirt - virtualization made easy Issue Type: Bug Components: Gerrit/git Reporter: Eyal Edri Assignee: infra Gerrit.ovirt.org error log is spammed with the following error: [2019-09-23 10:36:14,932] [sshd-SshServer[7c68a63c]-nio2-thread-3] WARN org.apache.sshd.common.keyprovider.FileKeyPairProvider : Failed (StreamCorruptedException) to load k ey resource=/home/gerrit2/review_site/etc/ssh_host_ecdsa_384_key: Invalid DER: object is not an OID: SEQUENCE Quick search found this thread:https://groups.google.com/forum/#!msg/repo-discuss/VF5-TtBCbuM/Rp0pA… Which talks about regenerating host ssh keys to fix the issue ( its possible leftover from CentOS6 and we need to run the generation of keys again on CentOS 7) Otherwise worth asking on the Gerrit IRC/Groups again. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100110)

1 0

[oVirt CI] standard-enqueue - Build #24008 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 23 Sep '19

23 Sep '19

Build: http://jenkins.ovirt.org/job/standard-enqueue/24008/ Build Name: #24008 Build Description: Gerrit: 103221 - ovirt-engine (master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/103221 - title: core: Add a VmDiskOperationParameterBase(Disk) C'tor - project: ovirt-engine - branch: master - author: Shani Leviim <sleviim(a)redhat.com>

1 0

[CQ]: 9c0c59c (v2v-conversion-host) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 23 Sep '19

23 Sep '19

A system test invoked by the "ovirt-4.3" change queue including change 9c0c59c (v2v-conversion-host) failed. However, this change seems not to be the root cause for this failure. Change 6797e49 (v2v-conversion-host) 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 6797e49 (v2v-conversion-host) 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://github.com/oVirt/v2v-conversion-host/commit/9c0c59c9a0bbaf7c2cccee4… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/v2v-conversion-host/commit/6797e499cb10860cbe4684c… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2154/

1 0

Build failed in Jenkins: system-sync_mirrors-fedora-updates-fc29-x86_64 #953
by jenkins＠jenkins.phx.ovirt.org 23 Sep '19

23 Sep '19

See <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-updates-fc29-x86_64…> ------------------------------------------ Started by timer Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-updates-fc29-x86_64…> No credentials specified > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision 1a2692064da3db124fd886cebd0cca5d0fa92bb4 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 1a2692064da3db124fd886cebd0cca5d0fa92bb4 Commit message: "nightly-system-tests: big suits -> big containers" > git rev-list --no-walk 1a2692064da3db124fd886cebd0cca5d0fa92bb4 # timeout=10 [system-sync_mirrors-fedora-updates-fc29-x86_64] $ /bin/bash -xe /tmp/jenkins8327505478610300298.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror fedora-updates-fc29 x86_64 jenkins/data/mirrors-reposync.conf + MIRRORS_MP_BASE=/var/www/html/repos + MIRRORS_HTTP_BASE=http://mirrors.phx.ovirt.org/repos + MIRRORS_CACHE=/home/jenkins/mirrors_cache + MAX_LOCK_ATTEMPTS=120 + LOCK_WAIT_INTERVAL=5 + LOCK_BASE=/home/jenkins + OLD_MD_TO_KEEP=100 + HTTP_SELINUX_TYPE=httpd_sys_content_t + HTTP_FILE_MODE=644 + main resync_yum_mirror fedora-updates-fc29 x86_64 jenkins/data/mirrors-reposync.conf + local command=resync_yum_mirror + command_args=("${@:2}") + local command_args + cmd_resync_yum_mirror fedora-updates-fc29 x86_64 jenkins/data/mirrors-reposync.conf + local repo_name=fedora-updates-fc29 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local sync_needed + mkdir -p /home/jenkins/mirrors_cache + verify_repo_fs fedora-updates-fc29 yum + local repo_name=fedora-updates-fc29 + local repo_type=yum + sudo install -o jenkins -d /var/www/html/repos/yum /var/www/html/repos/yum/fedora-updates-fc29 /var/www/html/repos/yum/fedora-updates-fc29/base + check_yum_sync_needed fedora-updates-fc29 x86_64 jenkins/data/mirrors-reposync.conf sync_needed + local repo_name=fedora-updates-fc29 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local p_sync_needed=sync_needed + local reposync_out + echo 'Checking if mirror needs a resync' Checking if mirror needs a resync + rm -rf /home/jenkins/mirrors_cache/fedora-updates-fc29 ++ IFS=, ++ echo x86_64 + for arch in '$(IFS=,; echo $repo_archs)' ++ run_reposync fedora-updates-fc29 x86_64 jenkins/data/mirrors-reposync.conf --urls --quiet ++ local repo_name=fedora-updates-fc29 ++ local repo_arch=x86_64 ++ local reposync_conf=jenkins/data/mirrors-reposync.conf ++ extra_args=("${@:4}") ++ local extra_args ++ reposync --config=jenkins/data/mirrors-reposync.conf --repoid=fedora-updates-fc29 --arch=x86_64 --cachedir=/home/jenkins/mirrors_cache --download_path=/var/www/html/repos/yum/fedora-updates-fc29/base --norepopath --newest-only --urls --quiet Traceback (most recent call last): File "/usr/bin/reposync", line 373, in <module> main() File "/usr/bin/reposync", line 185, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1482, in _commonLoadRepoXML result = self._getFileRepoXML(local, text) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1259, in _getFileRepoXML size=102400) # setting max size as 100K File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1025, in _getFile result = self.grab.urlgrab(misc.to_utf8(relative), local, File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 703, in <lambda> grab = property(lambda self: self._getgrab()) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 698, in _getgrab self._setupGrab() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 635, in _setupGrab urls = self.urls File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 881, in <lambda> urls = property(fget=lambda self: self._geturls(), File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 878, in _geturls self._baseurlSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 824, in _baseurlSetup mirrorurls.extend(list(self.metalink_data.urls())) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 921, in <lambda> metalink_data = property(fget=lambda self: self._getMetalink(), File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 900, in _getMetalink raise Errors.RepoError, msg yum.Errors.RepoError: Cannot retrieve metalink for repository: fedora-updates-fc29. Please verify its path and try again + reposync_out= Build step 'Execute shell' marked build as failure

1 1

[JIRA] (OVIRT-2798) add ovirt-provider-ovn project to the new gating system
by Miguel Duarte de Mora Barroso (oVirt JIRA) 23 Sep '19

23 Sep '19

Miguel Duarte de Mora Barroso created OVIRT-2798: ---------------------------------------------------- Summary: add ovirt-provider-ovn project to the new gating system Key: OVIRT-2798 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2798 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Miguel Duarte de Mora Barroso Assignee: infra Hi, I'd like to request that ovirt-provider-ovn is added to the new gating system. Thanks in advance, Miguel -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100110)

1 0

what is a telecommunications job
by kumarfield28＠gmail.com 23 Sep '19

23 Sep '19

These days, you will often come across telecommunication field technician jobs on the internet and newspapers. This must have gotten you curious regarding telecom engineer jobs. You might be wondering whether it would be the right career option for you and what kind of telecom services you will need to provide if this is the field you opt for. If that is the case, this is where your search culminates since we will provide you with the required details regarding telecom engineer jobs and services among other things. https://www.fieldengineer.com/blogs/telecom-engineer-job-description/

3 2

oVirt infra daily report - unstable production jobs - 956
by jenkins＠jenkins.phx.ovirt.org 23 Sep '19

23 Sep '19

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/956//artifact/exported-a… Cheers, Jenkins

1 0

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

22 Sep '19

A system test invoked by the "ovirt-master" change queue including change 103254,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 102717,6 (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 102717,6 (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/103254/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/102717/6 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15985/

1 0

Build failed in Jenkins: system-sync_mirrors-centos-sclo-rh-release-x86_64 #1
by jenkins＠jenkins.phx.ovirt.org 22 Sep '19

22 Sep '19

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-sclo-rh-release-x86…> ------------------------------------------ [...truncated 3.06 MB...] Removing ror40-rubygem-diff-lcs-doc-1.1.3-5.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-erubis-2.7.0-7.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-erubis-doc-2.7.0-7.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-execjs-1.4.0-7.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-execjs-doc-1.4.0-7.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-fakeweb-1.3.0-12.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-fakeweb-doc-1.3.0-12.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-hike-1.2.1-5.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-hike-doc-1.2.1-5.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-http_connection-1.4.1-9.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-i18n-0.6.4-3.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-i18n-doc-0.6.4-3.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-introspection-0.0.2-9.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-introspection-doc-0.0.2-9.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-jbuilder-1.5.0-2.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-jbuilder-doc-1.5.0-2.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-jquery-rails-3.1.0-1.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-jquery-rails-doc-3.1.0-1.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-mail-2.5.4-1.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-mail-doc-2.5.4-1.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-metaclass-0.0.1-9.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-metaclass-doc-0.0.1-9.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-mime-types-1.19-4.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-mime-types-doc-1.19-4.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-mocha-0.13.1-1.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-mocha-doc-0.13.1-1.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-mongo-1.9.2-1.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-mongo-doc-1.9.2-1.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-multi_json-1.7.7-2.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-multi_json-doc-1.7.7-2.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-net-http-persistent-2.8-3.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-net-http-persistent-doc-2.8-3.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-polyglot-0.3.3-4.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-polyglot-doc-0.3.3-4.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-rack-1.5.2-4.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-rack-cache-1.2-3.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-rack-cache-doc-1.2-3.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-rack-protection-1.2.0-9.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-rack-protection-doc-1.2.0-9.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-rack-test-0.6.2-1.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-rails-4.0.2-1.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-rails-doc-4.0.2-1.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-rails-observers-0.1.2-2.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-rails-observers-doc-0.1.2-2.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-railties-4.0.2-3.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-railties-doc-4.0.2-3.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-ref-1.0.0-5.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-ref-doc-1.0.0-5.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-rspec-2.11.0-3.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-rspec-core-2.11.1-4.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-rspec-core-doc-2.11.1-4.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-rspec-expectations-2.11.1-5.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-rspec-expectations-doc-2.11.1-5.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-rspec-mocks-2.11.1-5.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-rspec-mocks-doc-2.11.1-5.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-sass-3.2.6-2.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-sass-doc-3.2.6-2.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-sass-rails-4.0.0-2.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-sass-rails-doc-4.0.0-2.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-sdoc-0.4.0-4.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-sdoc-doc-0.4.0-4.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-sinatra-1.3.2-13.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-sinatra-doc-1.3.2-13.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-sprockets-2.8.2-3.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-sprockets-doc-2.8.2-3.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-sprockets-rails-2.0.0-3.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-sprockets-rails-doc-2.0.0-3.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-sqlite3-1.3.6-5.el7.x86_64.rpm due to failed signature check. Removing ror40-rubygem-sqlite3-doc-1.3.6-5.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-test_declarative-0.0.5-5.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-test_declarative-doc-0.0.5-5.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-therubyracer-0.11.0-6.el7.x86_64.rpm due to failed signature check. Removing ror40-rubygem-therubyracer-doc-0.11.0-6.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-thor-0.18.1-3.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-thor-doc-0.18.1-3.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-thread_safe-0.1.3-2.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-thread_safe-doc-0.1.3-2.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-tilt-1.3.3-13.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-tilt-doc-1.3.3-13.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-treetop-1.4.10-7.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-turbolinks-1.3.0-2.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-turbolinks-doc-1.3.0-2.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-tzinfo-0.3.37-2.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-tzinfo-doc-0.3.37-2.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-uglifier-2.2.1-4.el7.noarch.rpm due to failed signature check. Removing ror40-rubygem-uglifier-doc-2.2.1-4.el7.noarch.rpm due to failed signature check. Removing ror40-runtime-1.1-4.el7.x86_64.rpm due to failed signature check. Removing ror40-scldevel-1.1-4.el7.x86_64.rpm due to failed signature check. Removing ruby193-1.1-9.el7.x86_64.rpm due to failed signature check. Removing ruby193-build-1.1-9.el7.x86_64.rpm due to failed signature check. Removing ruby193-mod_passenger40-4.0.18-12.el7.x86_64.rpm due to failed signature check. Removing ruby193-ruby-1.9.3.484-51.el7.x86_64.rpm due to failed signature check. Removing ruby193-ruby-devel-1.9.3.484-51.el7.x86_64.rpm due to failed signature check. Removing ruby193-ruby-doc-1.9.3.484-51.el7.x86_64.rpm due to failed signature check. Removing ruby193-ruby-irb-1.9.3.484-51.el7.noarch.rpm due to failed signature check. Removing ruby193-ruby-libs-1.9.3.484-51.el7.x86_64.rpm due to failed signature check. Removing ruby193-ruby-tcltk-1.9.3.484-51.el7.x86_64.rpm due to failed signature check. Removing ruby193-rubygem-ZenTest-4.8.1-1.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-ZenTest-doc-4.8.1-1.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-actionmailer-3.2.8-1.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-actionmailer-doc-3.2.8-1.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-actionpack-3.2.8-20.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-actionpack-doc-3.2.8-20.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-activemodel-3.2.8-2.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-activemodel-doc-3.2.8-2.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-activerecord-3.2.8-8.2.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-activerecord-doc-3.2.8-8.2.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-activeresource-3.2.8-2.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-activeresource-doc-3.2.8-2.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-activesupport-3.2.8-5.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-arel-3.0.2-3.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-arel-doc-3.0.2-3.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-bacon-1.1.0-8.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-bacon-doc-1.1.0-8.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-bcrypt-ruby-3.0.1-8.el7.x86_64.rpm due to failed signature check. Removing ruby193-rubygem-bigdecimal-1.1.0-51.el7.x86_64.rpm due to failed signature check. Removing ruby193-rubygem-bson-1.9.2-1.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-bson-doc-1.9.2-1.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-bson_ext-1.9.2-2.el7.x86_64.rpm due to failed signature check. Removing ruby193-rubygem-bson_ext-doc-1.9.2-2.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-builder-3.0.0-3.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-builder-doc-3.0.0-3.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-bundler-1.3.5-1.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-bundler-doc-1.3.5-1.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-coffee-rails-3.2.2-4.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-coffee-rails-doc-3.2.2-4.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-coffee-script-2.2.0-4.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-coffee-script-doc-2.2.0-4.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-coffee-script-source-1.3.3-3.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-coffee-script-source-doc-1.3.3-3.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-diff-lcs-1.1.3-1.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-diff-lcs-doc-1.1.3-1.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-erubis-2.7.0-4.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-erubis-doc-2.7.0-4.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-execjs-1.4.0-6.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-execjs-doc-1.4.0-6.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-fakeweb-1.3.0-8.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-fakeweb-doc-1.3.0-8.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-hike-1.2.1-3.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-hike-doc-1.2.1-3.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-http_connection-1.4.1-7.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-i18n-0.6.0-3.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-i18n-doc-0.6.0-3.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-introspection-0.0.2-7.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-introspection-doc-0.0.2-7.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-io-console-0.3-51.el7.x86_64.rpm due to failed signature check. Removing ruby193-rubygem-journey-1.0.4-2.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-journey-doc-1.0.4-2.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-jquery-rails-2.0.2-2.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-jquery-rails-doc-2.0.2-2.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-json-1.5.5-51.el7.x86_64.rpm due to failed signature check. Removing ruby193-rubygem-mail-2.4.4-4.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-mail-doc-2.4.4-4.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-metaclass-0.0.1-8.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-metaclass-doc-0.0.1-8.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-mime-types-1.19-1.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-mime-types-doc-1.19-1.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-minitest-2.5.1-51.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-mocha-0.12.10-1.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-mocha-doc-0.12.10-1.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-mongo-1.9.2-1.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-mongo-doc-1.9.2-1.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-multi_json-1.3.6-2.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-multi_json-doc-1.3.6-2.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-net-http-persistent-2.7-3.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-net-http-persistent-doc-2.7-3.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-passenger40-4.0.18-12.el7.x86_64.rpm due to failed signature check. Removing ruby193-rubygem-passenger40-devel-4.0.18-12.el7.x86_64.rpm due to failed signature check. Removing ruby193-rubygem-passenger40-doc-4.0.18-12.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-passenger40-native-4.0.18-12.el7.x86_64.rpm due to failed signature check. Removing ruby193-rubygem-passenger40-native-libs-4.0.18-12.el7.x86_64.rpm due to failed signature check. Removing ruby193-rubygem-polyglot-0.3.3-2.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-polyglot-doc-0.3.3-2.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-rack-1.4.1-5.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-rack-cache-1.2-2.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-rack-cache-doc-1.2-2.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-rack-protection-1.2.0-7.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-rack-protection-doc-1.2.0-7.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-rack-ssl-1.3.2-7.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-rack-ssl-doc-1.3.2-7.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-rack-test-0.6.1-3.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-rails-3.2.8-2.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-railties-3.2.8-3.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-railties-doc-3.2.8-3.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-rake-0.9.2.2-51.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-rdoc-3.9.5-51.el7.x86_64.rpm due to failed signature check. Removing ruby193-rubygem-ref-1.0.0-3.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-ref-doc-1.0.0-3.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-rspec-2.11.0-2.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-rspec-core-2.11.1-2.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-rspec-core-doc-2.11.1-2.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-rspec-expectations-2.11.1-3.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-rspec-expectations-doc-2.11.1-3.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-rspec-mocks-2.11.1-2.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-rspec-mocks-doc-2.11.1-2.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-sass-3.1.20-3.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-sass-doc-3.1.20-3.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-sass-rails-3.2.5-2.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-sass-rails-doc-3.2.5-2.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-sinatra-1.3.2-12.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-sinatra-doc-1.3.2-12.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-sprockets-2.4.5-4.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-sprockets-doc-2.4.5-4.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-sqlite3-1.3.6-3.el7.x86_64.rpm due to failed signature check. Removing ruby193-rubygem-sqlite3-doc-1.3.6-3.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-test_declarative-0.0.5-3.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-test_declarative-doc-0.0.5-3.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-therubyracer-0.11.0-0.9.beta5.el7.x86_64.rpm due to failed signature check. Removing ruby193-rubygem-therubyracer-doc-0.11.0-0.9.beta5.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-thor-0.18.1-2.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-thor-doc-0.18.1-2.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-tilt-1.3.3-10.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-tilt-doc-1.3.3-10.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-treetop-1.4.10-6.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-tzinfo-0.3.33-2.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-tzinfo-doc-0.3.33-2.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-uglifier-1.2.6-4.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygem-uglifier-doc-1.2.6-4.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygems-1.8.23-51.el7.noarch.rpm due to failed signature check. Removing ruby193-rubygems-devel-1.8.23-51.el7.noarch.rpm due to failed signature check. Removing ruby193-runtime-1.1-9.el7.x86_64.rpm due to failed signature check. Removing ruby193-scldevel-1.1-9.el7.x86_64.rpm due to failed signature check. Removing ruby200-1.1-7.el7.x86_64.rpm due to failed signature check. Removing ruby200-build-1.1-7.el7.x86_64.rpm due to failed signature check. Removing ruby200-ruby-2.0.0.645-25.el7.x86_64.rpm due to failed signature check. Removing ruby200-ruby-devel-2.0.0.645-25.el7.x86_64.rpm due to failed signature check. Removing ruby200-ruby-doc-2.0.0.645-25.el7.noarch.rpm due to failed signature check. Removing ruby200-ruby-irb-2.0.0.645-25.el7.noarch.rpm due to failed signature check. Removing ruby200-ruby-libs-2.0.0.645-25.el7.x86_64.rpm due to failed signature check. Removing ruby200-ruby-tcltk-2.0.0.645-25.el7.x86_64.rpm due to failed signature check. Removing ruby200-rubygem-bigdecimal-1.2.0-25.el7.x86_64.rpm due to failed signature check. Removing ruby200-rubygem-io-console-0.4.2-25.el7.x86_64.rpm due to failed signature check. Removing ruby200-rubygem-json-1.7.7-25.el7.x86_64.rpm due to failed signature check. Removing ruby200-rubygem-minitest-4.3.2-25.el7.noarch.rpm due to failed signature check. Removing ruby200-rubygem-psych-2.0.0-25.el7.x86_64.rpm due to failed signature check. Removing ruby200-rubygem-rake-0.9.6-25.el7.noarch.rpm due to failed signature check. Removing ruby200-rubygem-rdoc-4.0.0-25.el7.noarch.rpm due to failed signature check. Removing ruby200-rubygems-2.0.14-25.el7.x86_64.rpm due to failed signature check. Removing ruby200-rubygems-devel-2.0.14-25.el7.noarch.rpm due to failed signature check. Removing ruby200-runtime-1.1-7.el7.x86_64.rpm due to failed signature check. Removing ruby200-scldevel-1.1-7.el7.x86_64.rpm due to failed signature check. Removing v8314-2.1-1.el7.x86_64.rpm due to failed signature check. Removing v8314-build-2.1-1.el7.x86_64.rpm due to failed signature check. Removing v8314-gyp-0.1-0.20.0bb6747git.el7.noarch.rpm due to failed signature check. Removing v8314-runtime-2.1-1.el7.x86_64.rpm due to failed signature check. Removing v8314-scldevel-2.1-1.el7.x86_64.rpm due to failed signature check. Removing v8314-v8-3.14.5.10-9.el7.x86_64.rpm due to failed signature check. Removing v8314-v8-devel-3.14.5.10-9.el7.x86_64.rpm due to failed signature check. Build step 'Execute shell' marked build as failure

1 6

oVirt infra daily report - unstable production jobs - 955
by jenkins＠jenkins.phx.ovirt.org 22 Sep '19

22 Sep '19

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/955//artifact/exported-a… Cheers, Jenkins

1 0

oVirt infra daily report - unstable production jobs - 954
by jenkins＠jenkins.phx.ovirt.org 21 Sep '19

21 Sep '19

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/954//artifact/exported-a… Cheers, Jenkins

1 0