- Infra - oVirt List Archives

[JIRA] (OVIRT-2034) Recreate the transactional CI mirrors with Pulp
by Barak Korren (oVirt JIRA) 17 May '18

17 May '18

Barak Korren created OVIRT-2034: ----------------------------------- Summary: Recreate the transactional CI mirrors with Pulp Key: OVIRT-2034 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2034 Project: oVirt - virtualization made easy Issue Type: New Feature Components: CI Mirrors Reporter: Barak Korren Assignee: infra Right now, the CI mirrors are created and maintained by a set of custom scripts and jobs. It seems that [Pulp|https://pulpproject.org/] can do what our current system does. The reason behind not using it when we first made the mirrors system was out desire to provide a quick solution and avoid adding more services to maintain. There are however, quite a few reasons to want to switch to pulp: # Aside from RPMs it can also manage other interesting kinds of resources like Containers, DEB packages and Python packages. # If it works well for us - we can maintain less code by dropping the existing mirror management code # It has built-in distribution mechanisms that can be useful to scale it up. # It seems it has support for assigning packages to multiple repos. This cab be used as a tagging mechanism to implement OVIRT-2033 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[oVirt Jenkins] ovirt-system-tests_network-suite-4.2 - Build # 213 - Failure!
by jenkins＠jenkins.phx.ovirt.org 17 May '18

17 May '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-4.2/213/ Build Number: 213 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #213 [Sandro Bonazzola] new suite: he-basic-iscsi-suite-4.2 ----------------- Failed Tests: ----------------- No tests ran.

1 2

[oVirt Jenkins] ovirt-system-tests_network-suite-master - Build # 212 - Failure!
by jenkins＠jenkins.phx.ovirt.org 17 May '18

17 May '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-master/212/ Build Number: 212 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #212 [Gal Ben Haim] run_suite: Print lago status on exit ----------------- Failed Tests: ----------------- No tests ran.

1 5

[JIRA] (OVIRT-2033) Provide a "tagging" mecahnism for transactional mirrors.
by Barak Korren (oVirt JIRA) 17 May '18

17 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2033?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2033: -------------------------------- Epic Link: OVIRT-400 > Provide a "tagging" mecahnism for transactional mirrors. > -------------------------------------------------------- > > Key: OVIRT-2033 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2033 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: CI Mirrors > Reporter: Barak Korren > Assignee: infra > > Right now when using the CI mirrors, one can either: > # Use the latest snapshots from all mirrors as mock_runner and all the jobs do. > # Use a specific snapshot by using the direct URL to it as we do on slaves. > It is desirable to be able to mark or tag specific mirror snapshots for various uses. The primary use for this is to track which mirror snapshots have been tested successfully by the change queue in a similar fashion to the way we track passing packages by storing them in the 'tested' repo. The motivation behind doing this is described in OVIRT-1444 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[JIRA] (OVIRT-2033) Provide a "tagging" mecahnism for transactional mirrors.
by Barak Korren (oVirt JIRA) 17 May '18

17 May '18

Barak Korren created OVIRT-2033: ----------------------------------- Summary: Provide a "tagging" mecahnism for transactional mirrors. Key: OVIRT-2033 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2033 Project: oVirt - virtualization made easy Issue Type: New Feature Components: CI Mirrors Reporter: Barak Korren Assignee: infra Right now when using the CI mirrors, one can either: # Use the latest snapshots from all mirrors as mock_runner and all the jobs do. # Use a specific snapshot by using the direct URL to it as we do on slaves. It is desirable to be able to mark or tag specific mirror snapshots for various uses. The primary use for this is to track which mirror snapshots have been tested successfully by the change queue in a similar fashion to the way we track passing packages by storing them in the 'tested' repo. The motivation behind doing this is described in OVIRT-1444 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

Change in ds-jenkins-stg[master]: Updated US source to: 28865d2 testing asdf
by review＠gerrit-staging.phx.ovirt.org 17 May '18

17 May '18

From Daniel Belenky <dbelenky(a)redhat.com>: Daniel Belenky has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/155 ) Change subject: Updated US source to: 28865d2 testing asdf ...................................................................... Patch Set 1: ci test please -- To view, visit https://gerrit-staging.phx.ovirt.org/155 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: ds-jenkins-stg Gerrit-Branch: master Gerrit-MessageType: comment Gerrit-Change-Id: I245e8658317dc9ac36fb0e9607c5386255bae8f4 Gerrit-Change-Number: 155 Gerrit-PatchSet: 1 Gerrit-Owner: Jenkins CI <infra(a)ovirt.org> Gerrit-Reviewer: Daniel Belenky <dbelenky(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-Comment-Date: Thu, 17 May 2018 08:34:31 +0000 Gerrit-HasComments: No

1 0

[JIRA] (OVIRT-2032) Mounting device files prevents using systemd-nspawn in mock
by Barak Korren (oVirt JIRA) 17 May '18

17 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2032?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2032: ------------------------------------- Issue [#87|https://github.com/rpm-software-management/mock/issues/87] has been resolved with PR [#171|https://github.com/rpm-software-management/mock/pull/171]. We need to check: # If we can now remove our mount point creation code from {{mock_runner}}. # If this paves the way to using {{systemd-nspawn}} in {{mock_runner}}. > Mounting device files prevents using systemd-nspawn in mock > ----------------------------------------------------------- > > Key: OVIRT-2032 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2032 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: mock_runner > Reporter: Barak Korren > Assignee: infra > Labels: upstream-issue > > The systemd-nspawn functionality in mock is introduced in OVIRT-2031. > When using systemd-nspawn mock uses some kind of a layered FS that is created when it starts and removed when it exits. This is different from the way it works when using chroot where the directory that the chroot is configured in stays around until it is explicitly removed. > mock had an issue where if you tried to bind-mount something into the mock environment, you had to have the mount point ready for it. We worked around this in {{mock_runner}} by using the fact the chroot was persistent, going into it and setting up the mount points as needed before actually starting to use it to run the STDCI script. > Since the mock authors were aware of the issue when the implemented the systemd-nspawn functionality, they made mock pre-create mount point in the container as needed. However, they only supported directory mount points, so if we tried to bind-mount a socket we would get en error message failing to mount a socket file on a directory. > We reported this issue to the mock developers as issue [#87|https://github.com/rpm-software-management/mock/issues/87] -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[JIRA] (OVIRT-2032) Mounting device files prevents using systemd-nspawn in mock
by Barak Korren (oVirt JIRA) 17 May '18

17 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2032?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2032: -------------------------------- Labels: upstream-issue (was: ) > Mounting device files prevents using systemd-nspawn in mock > ----------------------------------------------------------- > > Key: OVIRT-2032 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2032 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: mock_runner > Reporter: Barak Korren > Assignee: infra > Labels: upstream-issue > > The systemd-nspawn functionality in mock is introduced in OVIRT-2031. > When using systemd-nspawn mock uses some kind of a layered FS that is created when it starts and removed when it exits. This is different from the way it works when using chroot where the directory that the chroot is configured in stays around until it is explicitly removed. > mock had an issue where if you tried to bind-mount something into the mock environment, you had to have the mount point ready for it. We worked around this in {{mock_runner}} by using the fact the chroot was persistent, going into it and setting up the mount points as needed before actually starting to use it to run the STDCI script. > Since the mock authors were aware of the issue when the implemented the systemd-nspawn functionality, they made mock pre-create mount point in the container as needed. However, they only supported directory mount points, so if we tried to bind-mount a socket we would get en error message failing to mount a socket file on a directory. > We reported this issue to the mock developers as issue [#87|https://github.com/rpm-software-management/mock/issues/87] -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[JIRA] (OVIRT-2032) Mounting device files prevents using systemd-nspawn in mock
by Barak Korren (oVirt JIRA) 17 May '18

17 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2032?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2032: -------------------------------- Epic Link: OVIRT-400 > Mounting device files prevents using systemd-nspawn in mock > ----------------------------------------------------------- > > Key: OVIRT-2032 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2032 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: mock_runner > Reporter: Barak Korren > Assignee: infra > > The systemd-nspawn functionality in mock is introduced in OVIRT-2031. > When using systemd-nspawn mock uses some kind of a layered FS that is created when it starts and removed when it exits. This is different from the way it works when using chroot where the directory that the chroot is configured in stays around until it is explicitly removed. > mock had an issue where if you tried to bind-mount something into the mock environment, you had to have the mount point ready for it. We worked around this in {{mock_runner}} by using the fact the chroot was persistent, going into it and setting up the mount points as needed before actually starting to use it to run the STDCI script. > Since the mock authors were aware of the issue when the implemented the systemd-nspawn functionality, they made mock pre-create mount point in the container as needed. However, they only supported directory mount points, so if we tried to bind-mount a socket we would get en error message failing to mount a socket file on a directory. > We reported this issue to the mock developers as issue [#87|https://github.com/rpm-software-management/mock/issues/87] -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[JIRA] (OVIRT-2032) Mounting device files prevents using systemd-nspawn in mock
by Barak Korren (oVirt JIRA) 17 May '18

17 May '18

Barak Korren created OVIRT-2032: ----------------------------------- Summary: Mounting device files prevents using systemd-nspawn in mock Key: OVIRT-2032 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2032 Project: oVirt - virtualization made easy Issue Type: Bug Components: mock_runner Reporter: Barak Korren Assignee: infra The systemd-nspawn functionality in mock is introduced in OVIRT-2031. When using systemd-nspawn mock uses some kind of a layered FS that is created when it starts and removed when it exits. This is different from the way it works when using chroot where the directory that the chroot is configured in stays around until it is explicitly removed. mock had an issue where if you tried to bind-mount something into the mock environment, you had to have the mount point ready for it. We worked around this in {{mock_runner}} by using the fact the chroot was persistent, going into it and setting up the mount points as needed before actually starting to use it to run the STDCI script. Since the mock authors were aware of the issue when the implemented the systemd-nspawn functionality, they made mock pre-create mount point in the container as needed. However, they only supported directory mount points, so if we tried to bind-mount a socket we would get en error message failing to mount a socket file on a directory. We reported this issue to the mock developers as issue [#87|https://github.com/rpm-software-management/mock/issues/87] -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[CQ]: 91277, 2 (ovirt-engine-api-model) failed "ovirt-master" system tests
by oVirt Jenkins 17 May '18

17 May '18

Change 91277,2 (ovirt-engine-api-model) 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/91277/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7622/

1 0

[JIRA] (OVIRT-2031) Use the systemd-nspawn mode for mock
by Barak Korren (oVirt JIRA) 17 May '18

17 May '18

Barak Korren created OVIRT-2031: ----------------------------------- Summary: Use the systemd-nspawn mode for mock Key: OVIRT-2031 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2031 Project: oVirt - virtualization made easy Issue Type: Improvement Components: mock_runner Reporter: Barak Korren Assignee: infra Mock has long had the ability to use a full container via systemd-nspawn as opposed to a plain chroot. If we can leverage this, we can get many of the benefits of using containers without rebuilding our whole system on a new container backend. There were many issue in the past that prevented us from using that functionality. This ticket if for collecting tickets tracking these issues together. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[JIRA] (OVIRT-2031) Use the systemd-nspawn mode for mock
by Barak Korren (oVirt JIRA) 17 May '18

17 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2031?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2031: -------------------------------- Epic Link: OVIRT-400 > Use the systemd-nspawn mode for mock > ------------------------------------ > > Key: OVIRT-2031 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2031 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: mock_runner > Reporter: Barak Korren > Assignee: infra > Labels: tracker > > Mock has long had the ability to use a full container via systemd-nspawn as opposed to a plain chroot. If we can leverage this, we can get many of the benefits of using containers without rebuilding our whole system on a new container backend. > There were many issue in the past that prevented us from using that functionality. This ticket if for collecting tickets tracking these issues together. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[JIRA] (OVIRT-2029) Add cache pre-seed functionality to JJB
by Barak Korren (oVirt JIRA) 17 May '18

17 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2029?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2029: -------------------------------- Issue Type: Improvement (was: Task) > Add cache pre-seed functionality to JJB > --------------------------------------- > > Key: OVIRT-2029 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2029 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: JJB > Reporter: Barak Korren > Assignee: infra > Labels: upstream-contribution > > Since we run JJB from STDCI, we cannot have it rely on the existence of a persistent cache from its previous operation. Since JJB is most efficient when it has such a cache, our STDCI script generates such a cache for it from the contents of the previous commit. > To do that we essentially had to implement parts of the JJB internals (The cache handling) on our own. It desirable to have an option in JJB that would do that instead. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[JIRA] (OVIRT-2030) Add cache-based deletion option to JJB
by Barak Korren (oVirt JIRA) 17 May '18

17 May '18

Barak Korren created OVIRT-2030: ----------------------------------- Summary: Add cache-based deletion option to JJB Key: OVIRT-2030 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2030 Project: oVirt - virtualization made easy Issue Type: Improvement Components: JJB Reporter: Barak Korren Assignee: infra JJB currently supports two ways to delete jobs: # The {{delete}} command which deletes specific jobs that are specified on the command line # The {{--delete-old}] option to the {{update}} command which delete all jobs in Jenkins that are not included in the current update. Both thes options do not do what we want whic is to delete all jobs not included in the current update that were previously manage by JJB. To get this functionality we've made our scripts check the difference between to current and previous commits to find out which jobs were deleted. Instead we would like JJB to have the option for the {{update}} command to inspect the job cache from previous run (Or generated as explained in OVIRT-2029), and delete jobs found there that are not included in current update. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[JIRA] (OVIRT-2030) Add cache-based deletion option to JJB
by Barak Korren (oVirt JIRA) 17 May '18

17 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2030?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2030: -------------------------------- Epic Link: OVIRT-400 > Add cache-based deletion option to JJB > -------------------------------------- > > Key: OVIRT-2030 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2030 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: JJB > Reporter: Barak Korren > Assignee: infra > Labels: upstream-contribution > > JJB currently supports two ways to delete jobs: > # The {{delete}} command which deletes specific jobs that are specified on the command line > # The {{--delete-old}] option to the {{update}} command which delete all jobs in Jenkins that are not included in the current update. > Both thes options do not do what we want whic is to delete all jobs not included in the current update that were previously manage by JJB. > To get this functionality we've made our scripts check the difference between to current and previous commits to find out which jobs were deleted. Instead we would like JJB to have the option for the {{update}} command to inspect the job cache from previous run (Or generated as explained in OVIRT-2029), and delete jobs found there that are not included in current update. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[JIRA] (OVIRT-2029) Add cache pre-seed functionality to JJB
by Barak Korren (oVirt JIRA) 17 May '18

17 May '18

Barak Korren created OVIRT-2029: ----------------------------------- Summary: Add cache pre-seed functionality to JJB Key: OVIRT-2029 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2029 Project: oVirt - virtualization made easy Issue Type: Task Components: JJB Reporter: Barak Korren Assignee: infra Since we run JJB from STDCI, we cannot have it rely on the existence of a persistent cache from its previous operation. Since JJB is most efficient when it has such a cache, our STDCI script generates such a cache for it from the contents of the previous commit. To do that we essentially had to implement parts of the JJB internals (The cache handling) on our own. It desirable to have an option in JJB that would do that instead. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[JIRA] (OVIRT-2029) Add cache pre-seed functionality to JJB
by Barak Korren (oVirt JIRA) 17 May '18

17 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2029?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2029: -------------------------------- Epic Link: OVIRT-400 > Add cache pre-seed functionality to JJB > --------------------------------------- > > Key: OVIRT-2029 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2029 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: JJB > Reporter: Barak Korren > Assignee: infra > Labels: upstream-contribution > > Since we run JJB from STDCI, we cannot have it rely on the existence of a persistent cache from its previous operation. Since JJB is most efficient when it has such a cache, our STDCI script generates such a cache for it from the contents of the previous commit. > To do that we essentially had to implement parts of the JJB internals (The cache handling) on our own. It desirable to have an option in JJB that would do that instead. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[JIRA] (OVIRT-2028) Re: [Infra-private] Please remove ykleinbe@redhat.com from infra@ovirt.org
by Barak Korren (oVirt JIRA) 17 May '18

17 May '18

Barak Korren created OVIRT-2028: ----------------------------------- Summary: Re: [Infra-private] Please remove ykleinbe(a)redhat.com from infra(a)ovirt.org Key: OVIRT-2028 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2028 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Barak Korren Assignee: infra Forwarding to infra-support to get a Jira ticet. On 15 May 2018 at 10:34, Yaniv Kaul <ykaul(a)redhat.com> wrote: > He has left Red Hat long ago, and his email has been forwarded to Allon, > which recently left Red Hat - and now I'm getting those emails. > > TIA, > Y. > > _______________________________________________ > Infra-private mailing list -- infra-private(a)ovirt.org > To unsubscribe send an email to infra-private-leave(a)ovirt.org > oVirt Code of Conduct: https://www.ovirt.org/community/about/community- > guidelines/ > List Archives: > > -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

Re: [ovirt-users] Re: [ovirt-devel] Re: Mailing-Lists upgrade
by Nir Soffer 17 May '18

17 May '18

On Tue, May 8, 2018 at 11:56 AM Zach Brown <zachb1121(a)gmail.com> wrote: > It sounds like the mailing list just upgraded. I'm not sure if it's a bug > or not... But I unsubscribed from this list a long time ago (months ago) > and am now suddenly getting emails from it again. > > Just thought I'd give a heads up in case something may have gone wonky. > Another issue, old links to the mailing list are broken now: https://lists.ovirt.org/mailman/listinfo/devel Try to google "ovirt devel mailing list" to get the old links. We need to configure the http server to redirect to the new mailing list info page when old links are accessed. Nir > > On Tue, May 8, 2018, 3:04 AM Eyal Edri <eedri(a)redhat.com> wrote: > >> Great news! so happy to see this :) >> Thanks for the efforts for making it happen! >> >> On Tue, May 8, 2018 at 6:47 AM, Marc Dequènes (Duck) <duck(a)redhat.com> >> wrote: >> >>> I forgot to cross-post to other lists. Please read announcement below. >>> >>> On 05/08/2018 12:45 PM, Marc Dequènes (Duck) wrote: >>> > Quack, >>> > >>> > On 04/28/2018 09:34 AM, Marc Dequènes (Duck) wrote: >>> > >>> >> A few months ago we had to rollback the migration because of a nasty >>> >> bug. This is fixed in recent versions of Mailman 3 so we're >>> rescheduling >>> >> it on Tuesday 8th during the slot 11:00-12:00 JST. >>> > >>> > Just a word to say the migration happened and no problem was detected. >>> > >>> > The archive posts reindexation is not finished yet, and greylisting is >>> > slowing down things a bit, but it should soon be over. Some information >>> > like post count and little graphs in the web UI are handled via regular >>> > cron jobs and should also soon be accurate. >>> > >>> > Old links to the archives, for pre-migration posts, are still working. >>> > Posts URLS were not stable in Mailman 2 but been synced in >>> > https://lists.ovirt.org/pipermail/ >>> > >>> > You can contact me directly by mail or IRC, or open a JIRA ticket if >>> you >>> > hit any problem. >>> > >>> > \_o< >>> > >>> >>> >>> _______________________________________________ >>> >> Devel mailing list -- devel(a)ovirt.org >>> >> To unsubscribe send an email to devel-leave(a)ovirt.org >>> %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s >>> >> >> >> >> -- >> >> Eyal edri >> >> >> MANAGER >> >> RHV DevOps >> >> EMEA VIRTUALIZATION R&D >> >> >> Red Hat EMEA <https://www.redhat.com/> >> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> >> phone: +972-9-7692018 <+972%209-769-2018> >> irc: eedri (on #tlv #rhev-dev #rhev-integ) >> _______________________________________________ >> > Users mailing list -- users(a)ovirt.org >> To unsubscribe send an email to users-leave(a)ovirt.org >> > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org >

2 6

Change in ds-jenkins-stg[master]: Updated US source to: 28865d2 testing asdf
by review＠gerrit-staging.phx.ovirt.org 17 May '18

17 May '18

From Daniel Belenky <dbelenky(a)redhat.com>: Daniel Belenky has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/154 ) Change subject: Updated US source to: 28865d2 testing asdf ...................................................................... Patch Set 1: ci test please -- To view, visit https://gerrit-staging.phx.ovirt.org/154 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: ds-jenkins-stg Gerrit-Branch: master Gerrit-MessageType: comment Gerrit-Change-Id: Ie4d717e4e7c69b6ce48056b1929b563a63e0e885 Gerrit-Change-Number: 154 Gerrit-PatchSet: 1 Gerrit-Owner: Jenkins CI <infra(a)ovirt.org> Gerrit-Reviewer: Daniel Belenky <dbelenky(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-Comment-Date: Thu, 17 May 2018 06:08:21 +0000 Gerrit-HasComments: No

1 0

[JIRA] (OVIRT-2015) CQ marks two different changes in two different projects as cause of failure - both are not the cause
by Dafna Ron (oVirt JIRA) 17 May '18

17 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2015?page=com.atlassian.jira.… ] Dafna Ron reassigned OVIRT-2015: -------------------------------- Assignee: Dafna Ron (was: infra) > CQ marks two different changes in two different projects as cause of failure - both are not the cause > ----------------------------------------------------------------------------------------------------- > > Key: OVIRT-2015 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2015 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: Dafna Ron > Labels: CQ_false_report > > we have what seems to be a code regression in deploy ovn on upgrade suite: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7492/artifact… > The failure caused failure in two different projects otopi+imgbased: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7492/ > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7488/ > CQ marked a change in each of the projects as the cause of failure: > Otopi: > For further details about the change see: > https://gerrit.ovirt.org/#/c/88930/2 > imgbase; > For further details about the change see: > https://gerrit.ovirt.org/#/c/90692/43 > Since the cause of failure is the same for these two projects and the changes themselves do not seem like they can be the cause of failure I am reporting this ticket for further investigation. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[JIRA] (OVIRT-2021) CQ reporting wrong change as root cause
by Dafna Ron (oVirt JIRA) 17 May '18

17 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2021?page=com.atlassian.jira.… ] Dafna Ron closed OVIRT-2021. ---------------------------- Resolution: Fixed > CQ reporting wrong change as root cause > ---------------------------------------- > > Key: OVIRT-2021 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2021 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > > [CQ]: 91188, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause > For further details about the change see: > https://gerrit.ovirt.org/#/c/91188/2 > For further details about the change that seems to be the root cause behind the > testing failures see: > https://gerrit.ovirt.org/#/c/91084/1 > For failed test results see: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7552/ > The failure is a time out which was caused by a NPE (which is a real bug). > CQ reported the failure as related to JSONRPC which after discussing it with the developers has nothing to do with the NPE. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[JIRA] (OVIRT-2021) CQ reporting wrong change as root cause
by Dafna Ron (oVirt JIRA) 17 May '18

17 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2021?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2021: ----------------------------- Status: In Progress (was: To Do) > CQ reporting wrong change as root cause > ---------------------------------------- > > Key: OVIRT-2021 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2021 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > > [CQ]: 91188, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause > For further details about the change see: > https://gerrit.ovirt.org/#/c/91188/2 > For further details about the change that seems to be the root cause behind the > testing failures see: > https://gerrit.ovirt.org/#/c/91084/1 > For failed test results see: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7552/ > The failure is a time out which was caused by a NPE (which is a real bug). > CQ reported the failure as related to JSONRPC which after discussing it with the developers has nothing to do with the NPE. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[JIRA] (OVIRT-2021) CQ reporting wrong change as root cause
by Dafna Ron (oVirt JIRA) 17 May '18

17 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2021?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2021: ---------------------------------- Issue was resolved with fix: https://gerrit.ovirt.org/#/c/91225/ we have a green ovirt-engine build from: Build #7613 [1: 91071,4 (ovirt-engine)] (May 16, 2018 4:34:15 PM) > CQ reporting wrong change as root cause > ---------------------------------------- > > Key: OVIRT-2021 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2021 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > > [CQ]: 91188, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause > For further details about the change see: > https://gerrit.ovirt.org/#/c/91188/2 > For further details about the change that seems to be the root cause behind the > testing failures see: > https://gerrit.ovirt.org/#/c/91084/1 > For failed test results see: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7552/ > The failure is a time out which was caused by a NPE (which is a real bug). > CQ reported the failure as related to JSONRPC which after discussing it with the developers has nothing to do with the NPE. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[JIRA] (OVIRT-2027) NPE with no thread appears in engine log
by Dafna Ron (oVirt JIRA) 17 May '18

17 May '18

Dafna Ron created OVIRT-2027: -------------------------------- Summary: NPE with no thread appears in engine log Key: OVIRT-2027 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2027 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra This is not failing tests but should be fixed [CQ]: 84817,6 (ovirt-engine) failed "ovirt-master" system tests For further details about the change see: https://gerrit.ovirt.org/#/c/84817/6 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7601/ 2018-05-16 03:10:00,001-04 ERROR [org.ovirt.engine.core.bll.AutoRecoveryManager] (EE-ManagedThreadFactory-engineScheduled-Thread-92) [] Exception in recover: NullPointerException: -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[JIRA] (OVIRT-2024) virt-sparsify fails silently
by Dafna Ron (oVirt JIRA) 17 May '18

17 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2024?page=com.atlassian.jira.… ] Dafna Ron reassigned OVIRT-2024: -------------------------------- Assignee: Dafna Ron (was: infra) > virt-sparsify fails silently > ----------------------------- > > Key: OVIRT-2024 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2024 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: Dafna Ron > Labels: ost_failures > > virt-sparsify fails silently (intentionally silently). > you can see the error in the host vdsm log (even on successful builds) > 018-05-14 07:15:02,271-0400 ERROR (tasks/6) [root] Job u'796dd36e-0095-4adc-afb9-8b011f6b8ced' failed (jobs:221) > Traceback (most recent call last): > File "/usr/lib/python2.7/site-packages/vdsm/jobs.py", line 157, in run > self._run() > File "/usr/lib/python2.7/site-packages/vdsm/storage/sdm/api/sparsify_volume.py", line 56, in _run > virtsparsify.sparsify_inplace(self._vol_info.path) > File "/usr/lib/python2.7/site-packages/vdsm/virtsparsify.py", line 71, in sparsify_inplace > raise cmdutils.Error(cmd, rc, out, err) > Error: Command ['/usr/bin/virt-sparsify', '--machine-readable', '--in-place', u'/rhev/data-center/mnt/192.168.200.4:_exports_nfs_share1/96157fda-d60a-49d1-adb8-f306e402a0cf/images/156eaf32-5219-4be7-b61e-b5104f2b6c4d/77eb6602-13ac-46aa-a4 > 39-af9e51e3c2cb'] failed with rc=1 out=['3/12'] err=['virt-sparsify: error: libguestfs error: guestfs_launch failed.', 'This usually means the libguestfs appliance failed to start or crashed.', 'Do:', ' export LIBGUESTFS_DEBUG=1 LIBGUEST > FS_TRACE=1', 'and run the command again. For further information, read:', ' http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs', "You can also run 'libguestfs-test-tool' and post the *complete* output", 'into a bug report or > message to the libguestfs mailing list.', '', 'If reporting bugs, run virt-sparsify with debugging enabled and include the ', 'complete output:', '', ' virt-sparsify -v -x [...]'] > 2018-05-14 07:15:02,273-0400 INFO (tasks/6) [root] Job u'796dd36e-0095-4adc-afb9-8b011f6b8ced' will be deleted in 3600 seconds (jobs:249) > 2018-05-14 07:15:02,273-0400 DEBUG (tasks/6) [jsonrpc.Notification] Sending event {"params": {"status": "failed", "description": "sparsify_volume", "job_type": "storage", "error": {"message": "General Exception: ('Command [\\'/usr/bin/vir > t-sparsify\\', \\'--machine-readable\\', \\'--in-place\\', u\\'/rhev/data-center/mnt/192.168.200.4:_exports_nfs_share1/96157fda-d60a-49d1-adb8-f306e402a0cf/images/156eaf32-5219-4be7-b61e-b5104f2b6c4d/77eb6602-13ac-46aa-a439-af9e51e3c2cb\\ > '] failed with rc=1 out=[\\'3/12\\'] err=[\\'virt-sparsify: error: libguestfs error: guestfs_launch failed.\\', \\'This usually means the libguestfs appliance failed to start or crashed.\\', \\'Do:\\', \\' export LIBGUESTFS_DEBUG=1 LIBGU > ESTFS_TRACE=1\\', \\'and run the command again. For further information, read:\\', \\' http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs\\', \"You can also run \\'libguestfs-test-tool\\' and post the *complete* output\", \\' > into a bug report or message to the libguestfs mailing list.\\', \\'\\', \\'If reporting bugs, run virt-sparsify with debugging enabled and include the \\', \\'complete output:\\', \\'\\', \\' virt-sparsify -v -x [...]\\']',)", "code": 1 > 00}, "notify_time": 4295843980, "id": "796dd36e-0095-4adc-afb9-8b011f6b8ced"}, "jsonrpc": "2.0", "method": "|jobs|status|796dd36e-0095-4adc-afb9-8b011f6b8ced"} (__init__:180) > 2018-05-14 07:15:02,273-0400 DEBUG (tasks/6) [vds] Sending notification |jobs|status|796dd36e-0095-4adc-afb9-8b011f6b8ced with params {'status': 'failed', 'description': 'sparsify_volume', 'job_type': 'storage', 'error': {'message': 'Gene > ral Exception: (\'Command [\\\'/usr/bin/virt-sparsify\\\', \\\'--machine-readable\\\', \\\'--in-place\\\', u\\\'/rhev/data-center/mnt/192.168.200.4:_exports_nfs_share1/96157fda-d60a-49d1-adb8-f306e402a0cf/images/156eaf32-5219-4be7-b61e-b5 > 104f2b6c4d/77eb6602-13ac-46aa-a439-af9e51e3c2cb\\\'] failed with rc=1 out=[\\\'3/12\\\'] err=[\\\'virt-sparsify: error: libguestfs error: guestfs_launch failed.\\\', \\\'This usually means the libguestfs appliance failed to start or crash > ed.\\\', \\\'Do:\\\', \\\' export LIBGUESTFS_DEBUG=1 LIBGUESTFS_TRACE=1\\\', \\\'and run the command again. For further information, read:\\\', \\\' http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs\\\', "You can also run \ > \\'libguestfs-test-tool\\\' and post the *complete* output", \\\'into a bug report or message to the libguestfs mailing list.\\\', \\\'\\\', \\\'If reporting bugs, run virt-sparsify with debugging enabled and include the \\\', \\\'complet > e output:\\\', \\\'\\\', \\\' virt-sparsify -v -x [...]\\\']\',)', 'code': 100}, 'notify_time': 4295843980, 'id': u'796dd36e-0095-4adc-afb9-8b011f6b8ced'} (clientIF:225) > 2018-05-14 07:15:02,274-0400 INFO (tasks/6) [storage.ThreadPool.WorkerThread] FINISH task 041a7423-8c05-44b2-b3c9-6d5cf8710edc (threadPool:210) > 2018-05-14 07:15:04,229-0400 DEBUG (qgapoller/1) [vds] Not sending QEMU-GA command 'guest-get-users' to vm_id='e1317264-a572-47e0-98b4-d492239e285e', command is not supported (qemuguestagent:192) > 2018-05-14 07:15:04,230-0400 DEBUG (qgapoller/2) [vds] Not sending QEMU-GA command 'guest-get-users' to vm_id='29a56e04-51c7-4f25-b3c8-6df5489b2445', command is not supported (qemuguestagent:192) > 2018-05-14 07:15:05,186-0400 DEBUG (vmchannels) [vds] Timeout on fileno 63. (vmchannels:126) > Shmuel is investigating and we need to follow up with him. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[JIRA] (OVIRT-2026) CQ job killed on time-out - need to see why
by Dafna Ron (oVirt JIRA) 17 May '18

17 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2026?page=com.atlassian.jira.… ] Dafna Ron reassigned OVIRT-2026: -------------------------------- Assignee: Dafna Ron (was: infra) > CQ job killed on time-out - need to see why > ------------------------------------------- > > Key: OVIRT-2026 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2026 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: Dafna Ron > Labels: ost_failures > > [CQ]: 84817,6 (ovirt-engine) failed "ovirt-master" system tests > For further details about the change see: > https://gerrit.ovirt.org/#/c/84817/6 > For failed test results see: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7601/ > we can see a gap in times and we can see the exit was on check-connectivity for network but need to investigate further: > 07:16:44 [upgrade-from-release-suit] Running in /home/jenkins/workspace/ovirt-master_change-queue-tester/exported-artifacts/upgrade-from-release-suit-master-el7 > [Pipeline] [upgrade-from-release-suit] { > [Pipeline] [upgrade-from-release-suit] unstash > [Pipeline] [upgrade-from-release-suit] } > [Pipeline] [upgrade-from-release-suit] // dir > [Pipeline] [upgrade-from-release-suit] } > 08:12:19 [basic-suit] Error while running thread > 08:12:19 [basic-suit] Traceback (most recent call last): > 08:12:19 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue > 08:12:19 [basic-suit] queue.put({'return': func()}) > 08:12:19 [basic-suit] File "/home/jenkins/workspace/ovirt-master_change-queue-tester/ovirt-system-tests/basic-suite-master/test-scenarios/003_basic_networking.py", line 194, in _bond_nics > 08:12:19 [basic-suit] [bond]) > 08:12:19 [basic-suit] File "/home/jenkins/workspace/ovirt-master_change-queue-tester/ovirt-system-tests/basic-suite-master/test_utils/network_utils_v4.py", line 44, in attach_network_to_host > 08:12:19 [basic-suit] check_connectivity=True) > 08:12:19 [basic-suit] File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 37188, in setup_networks > 08:12:19 [basic-suit] return self._internal_action(action, 'setupnetworks', None, headers, query, wait) > 08:12:19 [basic-suit] File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 299, in _internal_action > 08:12:19 [basic-suit] return future.wait() if wait else future > 08:12:19 [basic-suit] File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait > 08:12:19 [basic-suit] return self._code(response) > 08:12:19 [basic-suit] File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 296, in callback > 08:12:19 [basic-suit] self._check_fault(response) > 08:12:19 [basic-suit] File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 130, in _check_fault > 08:12:19 [basic-suit] body = self._internal_read_body(response) > 08:12:19 [basic-suit] File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 316, in _internal_read_body > 08:12:19 [basic-suit] self._connection.check_xml_content_type(response) > 08:12:19 [basic-suit] File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 849, in check_xml_content_type > 08:12:19 [basic-suit] response.headers > 08:12:19 [basic-suit] File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 889, in _check_content_type > 08:12:19 [basic-suit] raise Error(msg) > 08:12:19 [basic-suit] Error: The response content type 'text/html; charset=iso-8859-1' isn't the expected XML > 08:12:19 [basic-suit] Error while running thread > 08:12:19 [basic-suit] Traceback (most recent call last): > 08:12:19 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue > 08:12:19 [basic-suit] queue.put({'return': func()}) > 08:12:19 [basic-suit] File "/home/jenkins/workspace/ovirt-master_change-queue-tester/ovirt-system-tests/basic-suite-master/test-scenarios/003_basic_networking.py", line 194, in _bond_nics > 08:12:19 [basic-suit] [bond]) > 08:12:19 [basic-suit] File "/home/jenkins/workspace/ovirt-master_change-queue-tester/ovirt-system-tests/basic-suite-master/test_utils/network_utils_v4.py", line 44, in attach_network_to_host > 08:12:19 [basic-suit] check_connectivity=True) > 08:12:19 [basic-suit] File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 37188, in setup_networks > 08:12:19 [basic-suit] return self._internal_action(action, 'setupnetworks', None, headers, query, wait) > 08:12:19 [basic-suit] File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 299, in _internal_action > 08:12:19 [basic-suit] return future.wait() if wait else future > 08:12:19 [basic-suit] File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait > 08:12:19 [basic-suit] return self._code(response) > 08:12:19 [basic-suit] File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 296, in callback > 08:12:19 [basic-suit] self._check_fault(response) > 08:12:19 [basic-suit] File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 130, in _check_fault > 08:12:19 [basic-suit] body = self._internal_read_body(response) > 08:12:19 [basic-suit] File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 316, in _internal_read_body > 08:12:19 [basic-suit] self._connection.check_xml_content_type(response) > 08:12:19 [basic-suit] File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 849, in check_xml_content_type > 08:12:19 [basic-suit] response.headers > 08:12:19 [basic-suit] File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 889, in _check_content_type > 08:12:19 [basic-suit] raise Error(msg) > 08:12:19 [basic-suit] Error: The response content type 'text/html; charset=iso-8859-1' isn't the expected XML > 08:41:12 [basic-suit] ./automation/basic_suite_master.sh: line 152: 183236 Killed timeout --kill-after 5m 100m ./run_suite.sh -o "$run_path" "${extra_cmds[@]}" "$SUITE" > 08:41:12 [basic-suit] + res=137 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[JIRA] (OVIRT-2026) CQ job killed on time-out - need to see why
by Dafna Ron (oVirt JIRA) 17 May '18

17 May '18

Dafna Ron created OVIRT-2026: -------------------------------- Summary: CQ job killed on time-out - need to see why Key: OVIRT-2026 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2026 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra [CQ]: 84817,6 (ovirt-engine) failed "ovirt-master" system tests For further details about the change see: https://gerrit.ovirt.org/#/c/84817/6 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7601/ we can see a gap in times and we can see the exit was on check-connectivity for network but need to investigate further: 07:16:44 [upgrade-from-release-suit] Running in /home/jenkins/workspace/ovirt-master_change-queue-tester/exported-artifacts/upgrade-from-release-suit-master-el7 [Pipeline] [upgrade-from-release-suit] { [Pipeline] [upgrade-from-release-suit] unstash [Pipeline] [upgrade-from-release-suit] } [Pipeline] [upgrade-from-release-suit] // dir [Pipeline] [upgrade-from-release-suit] } 08:12:19 [basic-suit] Error while running thread 08:12:19 [basic-suit] Traceback (most recent call last): 08:12:19 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue 08:12:19 [basic-suit] queue.put({'return': func()}) 08:12:19 [basic-suit] File "/home/jenkins/workspace/ovirt-master_change-queue-tester/ovirt-system-tests/basic-suite-master/test-scenarios/003_basic_networking.py", line 194, in _bond_nics 08:12:19 [basic-suit] [bond]) 08:12:19 [basic-suit] File "/home/jenkins/workspace/ovirt-master_change-queue-tester/ovirt-system-tests/basic-suite-master/test_utils/network_utils_v4.py", line 44, in attach_network_to_host 08:12:19 [basic-suit] check_connectivity=True) 08:12:19 [basic-suit] File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 37188, in setup_networks 08:12:19 [basic-suit] return self._internal_action(action, 'setupnetworks', None, headers, query, wait) 08:12:19 [basic-suit] File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 299, in _internal_action 08:12:19 [basic-suit] return future.wait() if wait else future 08:12:19 [basic-suit] File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait 08:12:19 [basic-suit] return self._code(response) 08:12:19 [basic-suit] File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 296, in callback 08:12:19 [basic-suit] self._check_fault(response) 08:12:19 [basic-suit] File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 130, in _check_fault 08:12:19 [basic-suit] body = self._internal_read_body(response) 08:12:19 [basic-suit] File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 316, in _internal_read_body 08:12:19 [basic-suit] self._connection.check_xml_content_type(response) 08:12:19 [basic-suit] File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 849, in check_xml_content_type 08:12:19 [basic-suit] response.headers 08:12:19 [basic-suit] File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 889, in _check_content_type 08:12:19 [basic-suit] raise Error(msg) 08:12:19 [basic-suit] Error: The response content type 'text/html; charset=iso-8859-1' isn't the expected XML 08:12:19 [basic-suit] Error while running thread 08:12:19 [basic-suit] Traceback (most recent call last): 08:12:19 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue 08:12:19 [basic-suit] queue.put({'return': func()}) 08:12:19 [basic-suit] File "/home/jenkins/workspace/ovirt-master_change-queue-tester/ovirt-system-tests/basic-suite-master/test-scenarios/003_basic_networking.py", line 194, in _bond_nics 08:12:19 [basic-suit] [bond]) 08:12:19 [basic-suit] File "/home/jenkins/workspace/ovirt-master_change-queue-tester/ovirt-system-tests/basic-suite-master/test_utils/network_utils_v4.py", line 44, in attach_network_to_host 08:12:19 [basic-suit] check_connectivity=True) 08:12:19 [basic-suit] File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 37188, in setup_networks 08:12:19 [basic-suit] return self._internal_action(action, 'setupnetworks', None, headers, query, wait) 08:12:19 [basic-suit] File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 299, in _internal_action 08:12:19 [basic-suit] return future.wait() if wait else future 08:12:19 [basic-suit] File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait 08:12:19 [basic-suit] return self._code(response) 08:12:19 [basic-suit] File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 296, in callback 08:12:19 [basic-suit] self._check_fault(response) 08:12:19 [basic-suit] File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 130, in _check_fault 08:12:19 [basic-suit] body = self._internal_read_body(response) 08:12:19 [basic-suit] File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 316, in _internal_read_body 08:12:19 [basic-suit] self._connection.check_xml_content_type(response) 08:12:19 [basic-suit] File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 849, in check_xml_content_type 08:12:19 [basic-suit] response.headers 08:12:19 [basic-suit] File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 889, in _check_content_type 08:12:19 [basic-suit] raise Error(msg) 08:12:19 [basic-suit] Error: The response content type 'text/html; charset=iso-8859-1' isn't the expected XML 08:41:12 [basic-suit] ./automation/basic_suite_master.sh: line 152: 183236 Killed timeout --kill-after 5m 100m ./run_suite.sh -o "$run_path" "${extra_cmds[@]}" "$SUITE" 08:41:12 [basic-suit] + res=137 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #1489
by jenkins＠jenkins.phx.ovirt.org 17 May '18

17 May '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/1489/displ…> Changes: [Martin Perina] wildfly: wildfly-overlay: Add FC28 builds [Martin Perina] engine-extensions: Add FC28 builds ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/ws/> > 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 977b0caf47b7fe509306b7c39aafc31c6e9ce968 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 977b0caf47b7fe509306b7c39aafc31c6e9ce968 Commit message: "engine-extensions: Add FC28 builds" > git rev-list --no-walk 630c77cd624b7341a969291aa6cc1d4ee2734a11 # timeout=10 [system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/jenkins5253678888424837886.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror epel-el6 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Error setting up repositories: failure: repodata/3cab53a138fc7bfa07f8b20a2618ad23c0b544cbc99c5f53a4276d5592db7529-primary.sqlite.bz2 from epel-el6: [Errno 256] No more mirrors to try. https://ny-mirrors.evowise.com/epel/6/x86_64/repodata/3cab53a138fc7bfa07f8b…: [Errno 14] HTTPS Error 404 - Not Found https://ewr.edge.kernel.org/fedora-buffet/epel/6/x86_64/repodata/3cab53a138…: [Errno 14] HTTPS Error 404 - Not Found http://mirror.math.princeton.edu/pub/epel/6/x86_64/repodata/3cab53a138fc7bf…: [Errno 14] HTTP Error 404 - Not Found http://mirror.grid.uchicago.edu/pub/linux/epel/6/x86_64/repodata/3cab53a138…: [Errno 14] HTTP Error 404 - Not Found https://download-ib01.fedoraproject.org/pub/epel/6/x86_64/repodata/3cab53a1…: [Errno 14] HTTPS Error 404 - Not Found http://fedora.mirrors.pair.com/epel/6/x86_64/repodata/3cab53a138fc7bfa07f8b…: [Errno 14] HTTP Error 404 - Not Found https://la-mirrors.evowise.com/epel/6/x86_64/repodata/3cab53a138fc7bfa07f8b…: [Errno 14] HTTPS Error 404 - Not Found https://sjc.edge.kernel.org/fedora-buffet/epel/6/x86_64/repodata/3cab53a138…: [Errno 14] HTTPS Error 404 - Not Found http://mirror.compevo.com/epel/6/x86_64/repodata/3cab53a138fc7bfa07f8b20a26…: [Errno 14] HTTP Error 404 - Not Found http://mirror.solarvps.com/epel/6/x86_64/repodata/3cab53a138fc7bfa07f8b20a2…: [Errno 12] Timeout on http://mirror.solarvps.com/epel/6/x86_64/repodata/3cab53a138fc7bfa07f8b20a2…: (28, 'Connection timed out after 30001 milliseconds') https://mirror.redsox.cc/fedora-epel/6/x86_64/repodata/3cab53a138fc7bfa07f8…: [Errno 14] HTTPS Error 404 - Not Found https://mirror.steadfast.net/epel/6/x86_64/repodata/3cab53a138fc7bfa07f8b20…: [Errno 14] HTTPS Error 404 - Not Found http://mirrors.kernel.org/fedora-epel/6/x86_64/repodata/3cab53a138fc7bfa07f…: [Errno 14] HTTP Error 404 - Not Found https://mirror.chpc.utah.edu/pub/epel/6/x86_64/repodata/3cab53a138fc7bfa07f…: [Errno 14] HTTPS Error 404 - Not Found http://mirror.metrocast.net/fedora/epel/6/x86_64/repodata/3cab53a138fc7bfa0…: [Errno 14] HTTP Error 404 - Not Found http://mirror.beyondhosting.net/epel/6/x86_64/repodata/3cab53a138fc7bfa07f8…: [Errno 14] HTTP Error 404 - Not Found https://mirrors.cat.pdx.edu/epel/6/x86_64/repodata/3cab53a138fc7bfa07f8b20a…: [Errno 14] HTTPS Error 404 - Not Found https://mirror.hmc.edu/epel/6/x86_64/repodata/3cab53a138fc7bfa07f8b20a2618a…: [Errno 14] HTTPS Error 404 - Not Found http://mirror.seas.harvard.edu/epel/6/x86_64/repodata/3cab53a138fc7bfa07f8b…: [Errno 14] HTTP Error 404 - Not Found http://mirror.cogentco.com/pub/linux/epel/6/x86_64/repodata/3cab53a138fc7bf…: [Errno 14] HTTP Error 404 - Not Found http://ftp.cse.buffalo.edu/pub/epel/6/x86_64/repodata/3cab53a138fc7bfa07f8b…: [Errno 14] HTTP Error 404 - Not Found https://pubmirror2.math.uh.edu/fedora-buffet/epel/6/x86_64/repodata/3cab53a…: [Errno 14] HTTPS Error 404 - Not Found http://mirror.texas3006.com/epel/6/x86_64/repodata/3cab53a138fc7bfa07f8b20a…: [Errno 14] curl#6 - "Could not resolve host: mirror.texas3006.com; Name or service not known" http://mirror.ancl.hawaii.edu/linux/epel/6/x86_64/repodata/3cab53a138fc7bfa…: [Errno 14] HTTP Error 404 - Not Found https://pubmirror1.math.uh.edu/fedora-buffet/epel/6/x86_64/repodata/3cab53a…: [Errno 14] HTTPS Error 404 - Not Found http://mirrors.tummy.com/pub/fedora.redhat.com/epel/6/x86_64/repodata/3cab5…: [Errno 14] HTTP Error 404 - Not Found http://mirror.coastal.edu/epel/6/x86_64/repodata/3cab53a138fc7bfa07f8b20a26…: [Errno 14] HTTP Error 404 - Not Found http://mirrors.develooper.com/epel/6/x86_64/repodata/3cab53a138fc7bfa07f8b2…: [Errno 14] HTTP Error 404 - Not Found http://mirror.prgmr.com/pub/epel/6/x86_64/repodata/3cab53a138fc7bfa07f8b20a…: [Errno 14] HTTP Error 404 - Not Found https://dl.fedoraproject.org/pub/epel/6/x86_64/repodata/3cab53a138fc7bfa07f…: [Errno 14] HTTPS Error 404 - Not Found https://muug.ca/mirror/fedora-epel/6/x86_64/repodata/3cab53a138fc7bfa07f8b2…: [Errno 14] HTTPS Error 404 - Not Found https://mirror.csclub.uwaterloo.ca/fedora/epel/6/x86_64/repodata/3cab53a138…: [Errno 14] HTTPS Error 404 - Not Found http://fedora.westmancom.com/epel/6/x86_64/repodata/3cab53a138fc7bfa07f8b20…: [Errno 14] HTTP Error 404 - Not Found Build step 'Execute shell' marked build as failure

1 1

Change in ds-jenkins-stg[master]: Updated US source to: 28865d2 testing asdf
by review＠gerrit-staging.phx.ovirt.org 16 May '18

16 May '18

From Daniel Belenky <dbelenky(a)redhat.com>: Daniel Belenky has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/154 ) Change subject: Updated US source to: 28865d2 testing asdf ...................................................................... Patch Set 1: ci test please -- To view, visit https://gerrit-staging.phx.ovirt.org/154 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: ds-jenkins-stg Gerrit-Branch: master Gerrit-MessageType: comment Gerrit-Change-Id: Ie4d717e4e7c69b6ce48056b1929b563a63e0e885 Gerrit-Change-Number: 154 Gerrit-PatchSet: 1 Gerrit-Owner: Jenkins CI <infra(a)ovirt.org> Gerrit-Reviewer: Daniel Belenky <dbelenky(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-Comment-Date: Wed, 16 May 2018 19:04:56 +0000 Gerrit-HasComments: No

1 0

Change in ds-jenkins-stg[master]: Updated US source to: 28865d2 testing asdf
by review＠gerrit-staging.phx.ovirt.org 16 May '18

16 May '18

From Daniel Belenky <dbelenky(a)redhat.com>: Daniel Belenky has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/154 ) Change subject: Updated US source to: 28865d2 testing asdf ...................................................................... Patch Set 1: ci test please -- To view, visit https://gerrit-staging.phx.ovirt.org/154 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: ds-jenkins-stg Gerrit-Branch: master Gerrit-MessageType: comment Gerrit-Change-Id: Ie4d717e4e7c69b6ce48056b1929b563a63e0e885 Gerrit-Change-Number: 154 Gerrit-PatchSet: 1 Gerrit-Owner: Jenkins CI <infra(a)ovirt.org> Gerrit-Reviewer: Daniel Belenky <dbelenky(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-Comment-Date: Wed, 16 May 2018 18:32:38 +0000 Gerrit-HasComments: No

1 0

Change in us-jenkins-stg2[master]: testing asdf
by review＠gerrit-staging.phx.ovirt.org 16 May '18

16 May '18

From Daniel Belenky <dbelenky(a)redhat.com>: Daniel Belenky has submitted this change and it was merged. ( https://gerrit-staging.phx.ovirt.org/152 ) Change subject: testing asdf ...................................................................... testing asdf Change-Id: I880050f1ee5d1737acb169945efccac0510f9fde Signed-off-by: Daniel Belenky <dbelenky(a)redhat.com> --- M upstream-file2.txt 1 file changed, 1 insertion(+), 0 deletions(-) Approvals: Jenkins CI: Passed CI tests Daniel Belenky: Looks good to me, approved; Verified; Passed CI tests -- To view, visit https://gerrit-staging.phx.ovirt.org/152 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: us-jenkins-stg2 Gerrit-Branch: master Gerrit-MessageType: merged Gerrit-Change-Id: I880050f1ee5d1737acb169945efccac0510f9fde Gerrit-Change-Number: 152 Gerrit-PatchSet: 1 Gerrit-Owner: Daniel Belenky <dbelenky(a)redhat.com> Gerrit-Reviewer: Daniel Belenky <dbelenky(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org>

1 0

Change in us-jenkins-stg2[master]: testing asdf
by review＠gerrit-staging.phx.ovirt.org 16 May '18

16 May '18

From Daniel Belenky <dbelenky(a)redhat.com>: Daniel Belenky has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/152 ) Change subject: testing asdf ...................................................................... Patch Set 1: Verified+1 Code-Review+2 Continuous-Integration+1 -- To view, visit https://gerrit-staging.phx.ovirt.org/152 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: us-jenkins-stg2 Gerrit-Branch: master Gerrit-MessageType: comment Gerrit-Change-Id: I880050f1ee5d1737acb169945efccac0510f9fde Gerrit-Change-Number: 152 Gerrit-PatchSet: 1 Gerrit-Owner: Daniel Belenky <dbelenky(a)redhat.com> Gerrit-Reviewer: Daniel Belenky <dbelenky(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-Comment-Date: Wed, 16 May 2018 18:12:08 +0000 Gerrit-HasComments: No

1 0

oVirt infra weekly meeting notes 16.05.2018
by Evgheni Dereveanchin 16 May '18

16 May '18

Hi everyone, Please find the topics of this week's infra meeting below: *PHX DC - Foreman partially broken due to cert expiration OVIRT-1994 <https://ovirt-jira.atlassian.net/browse/OVIRT-1994>- SSL status:- Jenkins SSL patch rebased and updated OVIRT-1471 <https://ovirt-jira.atlassian.net/browse/OVIRT-1471>- CentOS 7.5 package conflicts causing issues on PPC RHBZ#1568676 <https://bugzilla.redhat.com/1568676>- Jenkins update pending OVIRT-1970 <https://ovirt-jira.atlassian.net/browse/OVIRT-1970>- Low space on resources, cleanup patch under review OVIRT-1277 <https://ovirt-jira.atlassian.net/browse/OVIRT-1277>Other topics - Mailman3 migration status sync- Links to archives were missing - fixed- Old subscribers weren’t removed - cleanup done- Footer changed after migration- Minor crashes in mailman (may be CentOS 7.5 related)- Website security hardening in progressAction Items: - Ensure the new mailing list server is monitored- Back up Mailman2 VM and shut it down* -- Regards, Evgheni Dereveanchin

1 0

[oVirt Jenkins] ovirt-node-ng_master_build-artifacts-el7-x86_64 - Build # 793 - Failure!
by jenkins＠jenkins.phx.ovirt.org 16 May '18

16 May '18

Project: http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6… Build: http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6… Build Number: 793 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #793 [Daniel Belenky] Allow requirement of project specific nodes [Barak Korren] Fix Git user for 'jenkins' repo V1 jobs [Yuval Turgeman] scripts: small changes to setup-node-appliance ----------------- Failed Tests: ----------------- No tests ran.

1 4

ovirt-engine travis CI
by Sandro Bonazzola 16 May '18

16 May '18

Hi, today I pushed a fix for Travis CI on oVirt Engine. While discussing the fix it has been asked why we need Travis CI in first place, isn't our Jenkins testing enough? Thanks, -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://redhat.com/summit>

4 6

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-master - Build # 387 - Failure!
by jenkins＠jenkins.phx.ovirt.org 16 May '18

16 May '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/387/ Build Number: 387 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #387 [Gal Ben Haim] run_suite: Print lago status on exit [Daniel Belenky] Allow requirement of project specific nodes [Barak Korren] Fix Git user for 'jenkins' repo V1 jobs ----------------- Failed Tests: ----------------- No tests ran.

1 3

[CQ]: 89197, 1 (ovirt-engine-wildfly) failed "ovirt-master" system tests
by oVirt Jenkins 16 May '18

16 May '18

Change 89197,1 (ovirt-engine-wildfly) 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/89197/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7609/

1 0

[oVirt Jenkins] ovirt-system-tests_network-suite-4.2 - Build # 206 - Failure!
by jenkins＠jenkins.phx.ovirt.org 16 May '18

16 May '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-4.2/206/ Build Number: 206 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #206 [Marcin Mirecki] network: add multiple networks connected by single router ----------------- Failed Tests: ----------------- No tests ran.

1 6

[CQ]: 84817,6 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 16 May '18

16 May '18

Change 84817,6 (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/84817/6 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7601/

2 1

[CQ]: 91221,3 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 16 May '18

16 May '18

Change 91221,3 (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/91221/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7604/

1 0

Build failed in Jenkins: system-sync_mirrors-centos-updates-el7-x86_64 #1565
by jenkins＠jenkins.phx.ovirt.org 16 May '18

16 May '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_64/…> ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_64/…> > 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 630c77cd624b7341a969291aa6cc1d4ee2734a11 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 630c77cd624b7341a969291aa6cc1d4ee2734a11 Commit message: "Fix Git user for 'jenkins' repo V1 jobs" > git rev-list --no-walk 630c77cd624b7341a969291aa6cc1d4ee2734a11 # timeout=10 [system-sync_mirrors-centos-updates-el7-x86_64] $ /bin/bash -xe /tmp/jenkins8762047267967619493.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-updates-el7 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 175, 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 1465, in _commonLoadRepoXML local = self.cachedir + '/repomd.xml' File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 774, in <lambda> cachedir = property(lambda self: self._dirGetAttr('cachedir')) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 757, in _dirGetAttr self.dirSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 735, in dirSetup self._dirSetupMkdir_p(dir) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 712, in _dirSetupMkdir_p raise Errors.RepoError, msg yum.Errors.RepoError: Error making cache directory: /home/jenkins/mirrors_cache/epel-el6/packages error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/epel-el6/packages' Build step 'Execute shell' marked build as failure

1 1

Build failed in Jenkins: system-sync_mirrors-fedora-base-fc26-x86_64 #1166
by jenkins＠jenkins.phx.ovirt.org 16 May '18

16 May '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-base-fc26-x86_64/11…> ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-base-fc26-x86_64/ws/> > 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 630c77cd624b7341a969291aa6cc1d4ee2734a11 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 630c77cd624b7341a969291aa6cc1d4ee2734a11 Commit message: "Fix Git user for 'jenkins' repo V1 jobs" > git rev-list --no-walk 630c77cd624b7341a969291aa6cc1d4ee2734a11 # timeout=10 [system-sync_mirrors-fedora-base-fc26-x86_64] $ /bin/bash -xe /tmp/jenkins5329269943468505159.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror fedora-base-fc26 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 175, 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 1479, in _commonLoadRepoXML result = self._getFileRepoXML(local, text) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1256, in _getFileRepoXML size=102400) # setting max size as 100K File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1022, in _getFile result = self.grab.urlgrab(misc.to_utf8(relative), local, File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 700, in <lambda> grab = property(lambda self: self._getgrab()) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 695, in _getgrab self._setupGrab() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 632, in _setupGrab urls = self.urls File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 878, in <lambda> urls = property(fget=lambda self: self._geturls(), File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 875, in _geturls self._baseurlSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 821, in _baseurlSetup mirrorurls.extend(list(self.metalink_data.urls())) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 918, in <lambda> metalink_data = property(fget=lambda self: self._getMetalink(), File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 914, in _getMetalink self._metalink = metalink.MetaLinkRepoMD(self.metalink_filename) File "/usr/lib/python2.7/site-packages/yum/metalink.py", line 185, in __init__ raise MetaLinkRepoErrorParseFail, "File %s does not exist" %filename yum.metalink.MetaLinkRepoErrorParseFail: File /home/jenkins/mirrors_cache/fedora-base-fc26/metalink.xml does not exist Build step 'Execute shell' marked build as failure

1 1

[JIRA] (OVIRT-2021) CQ reporting wrong change as root cause
by Dafna Ron (oVirt JIRA) 15 May '18

15 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2021?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2021: ---------------------------------- we can close this ticket. the issue was this change: https://gerrit.ovirt.org/#/c/91038/ which failed on build-artifacts (so CQ did not even start). it was merged on May 9th We had 3 other issues last week: 1. centos changing the repos for 7.5 2. broken packages (vdsm-jsonrpc) 3. ost broken due to upgrade patch our first failure in cq detecting this change was: Build #7552 [1: 91188,2 (ovirt-engine)] (May 13, 2018 3:52:53 PM) but ovirt-engine was continuously broken due to different issues and CQ was behaving as expected. > CQ reporting wrong change as root cause > ---------------------------------------- > > Key: OVIRT-2021 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2021 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > > [CQ]: 91188, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause > For further details about the change see: > https://gerrit.ovirt.org/#/c/91188/2 > For further details about the change that seems to be the root cause behind the > testing failures see: > https://gerrit.ovirt.org/#/c/91084/1 > For failed test results see: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7552/ > The failure is a time out which was caused by a NPE (which is a real bug). > CQ reported the failure as related to JSONRPC which after discussing it with the developers has nothing to do with the NPE. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[JIRA] (OVIRT-2023) mailing lists footer macros are broken
by Emil Natan (oVirt JIRA) 15 May '18

15 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2023?page=com.atlassian.jira.… ] Emil Natan commented on OVIRT-2023: ----------------------------------- [~gshereme(a)redhat.com] duplicates https://ovirt-jira.atlassian.net/browse/OVIRT-2016 > mailing lists footer macros are broken > -------------------------------------- > > Key: OVIRT-2023 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2023 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: infra > > mailing lists footer macros are broken. Examples: > > Devel mailing list -- devel(a)ovirt.org > > To unsubscribe send an email to devel-leave(a)ovirt.org > > %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s > > > _______________________________________________ > Devel mailing list -- devel(a)ovirt.org > To unsubscribe send an email to devel-leave(a)ovirt.org > %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s > -- > GREG SHEREMETA > SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX > Red Hat NA > <https://www.redhat.com/> > gshereme(a)redhat.com IRC: gshereme > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100084)

2 7

Change in us-jenkins-stg2[master]: Change to sync D/S
by review＠gerrit-staging.phx.ovirt.org 15 May '18

15 May '18

From Daniel Belenky <dbelenky(a)redhat.com>: Daniel Belenky has submitted this change and it was merged. ( https://gerrit-staging.phx.ovirt.org/149 ) Change subject: Change to sync D/S ...................................................................... Change to sync D/S Change-Id: Ibf357c2b3aac87f0e101dc6d5ce8f4e9d23febdf Signed-off-by: Daniel Belenky <dbelenky(a)redhat.com> --- M upstream-file1.txt 1 file changed, 1 insertion(+), 0 deletions(-) Approvals: Daniel Belenky: Looks good to me, approved; Verified; Passed CI tests Objections: Jenkins CI: Failed CI tests -- To view, visit https://gerrit-staging.phx.ovirt.org/149 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: us-jenkins-stg2 Gerrit-Branch: master Gerrit-MessageType: merged Gerrit-Change-Id: Ibf357c2b3aac87f0e101dc6d5ce8f4e9d23febdf Gerrit-Change-Number: 149 Gerrit-PatchSet: 1 Gerrit-Owner: Daniel Belenky <dbelenky(a)redhat.com> Gerrit-Reviewer: Daniel Belenky <dbelenky(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org>

1 0

Change in us-jenkins-stg2[master]: Change to sync D/S
by review＠gerrit-staging.phx.ovirt.org 15 May '18

15 May '18

From Daniel Belenky <dbelenky(a)redhat.com>: Daniel Belenky has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/149 ) Change subject: Change to sync D/S ...................................................................... Patch Set 1: Verified+1 Code-Review+2 Continuous-Integration+1 -- To view, visit https://gerrit-staging.phx.ovirt.org/149 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: us-jenkins-stg2 Gerrit-Branch: master Gerrit-MessageType: comment Gerrit-Change-Id: Ibf357c2b3aac87f0e101dc6d5ce8f4e9d23febdf Gerrit-Change-Number: 149 Gerrit-PatchSet: 1 Gerrit-Owner: Daniel Belenky <dbelenky(a)redhat.com> Gerrit-Reviewer: Daniel Belenky <dbelenky(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-Comment-Date: Tue, 15 May 2018 11:22:46 +0000 Gerrit-HasComments: No

1 0

[oVirt Jenkins] ovirt-node-ng_ovirt-4.2-pre_build-artifacts-el7-x86_64 - Build # 334 - Failure!
by jenkins＠jenkins.phx.ovirt.org 15 May '18

15 May '18

Project: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2-pre_build-artifacts-el… Build: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2-pre_build-artifacts-el… Build Number: 334 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #334 [Miguel Duarte Barroso] Adding myself to the list [Sandro Bonazzola] ovirt-host: add fc28 on master [Evgheni Dereveanchin] Verify IPv6 router advertisement settings from global_setup [Ryan Barry] image-update: fail upgrades if there is a local storage domain on / ----------------- Failed Tests: ----------------- No tests ran.

1 6

[CQ]: 90249, 18 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 15 May '18

15 May '18

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

1 0