- Infra - oVirt List Archives

[CQ]: 95989, 7 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 06 Feb '19

06 Feb '19

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

1 0

[JIRA] (OVIRT-2672) Nicer URLs in jenkins
by Nir Soffer (oVirt JIRA) 06 Feb '19

06 Feb '19

Nir Soffer created OVIRT-2672: --------------------------------- Summary: Nicer URLs in jenkins Key: OVIRT-2672 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2672 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra Jenkinks OST URLs are too ugly. When looking for OST manual job, we go to: https://jenkins.ovirt.org/view/oVirt%20system%20tests/ This should be something like: https://jenkins.ovirt.org/view/ost/ Or https://jenkins.ovirt.org/view/ovirt-system-tests Then we click on "ovirt-system-tests_manual" which links to: https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-test… Here we can easily make the url much nicer by modifying the URL to: https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ Now we can start a build, and easily get a nice URL for the build to paste on gerrit, like: https://jenkins.ovirt.org/job/ovirt-system-tests_manual/4025/ So this looks like an easy fix, make the links point to https://jenkins.ovirt.org/job/<job name> Why should we make URLs nicer? Ugly URLs are a broken window: https://en.wikipedia.org/wiki/Broken_windows_theory Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

Nicer URLs in jenkins
by Nir Soffer 06 Feb '19

06 Feb '19

Jenkinks OST URLs are too ugly. When looking for OST manual job, we go to: https://jenkins.ovirt.org/view/oVirt%20system%20tests/ This should be something like: https://jenkins.ovirt.org/view/ost/ Or https://jenkins.ovirt.org/view/ovirt-system-tests Then we click on "ovirt-system-tests_manual" which links to: https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-test… Here we can easily make the url much nicer by modifying the URL to: https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ Now we can start a build, and easily get a nice URL for the build to paste on gerrit, like: https://jenkins.ovirt.org/job/ovirt-system-tests_manual/4025/ So this looks like an easy fix, make the links point to https://jenkins.ovirt.org/job/<job name> Why should we make URLs nicer? Ugly URLs are a broken window: https://en.wikipedia.org/wiki/Broken_windows_theory Nir

1 0

[CQ]: 97544, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 06 Feb '19

06 Feb '19

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

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 06 Feb '19

06 Feb '19

Failed to run project_setup.sh for: #3466 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-9bpmd.

1 0

[CQ]: 95988, 6 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 06 Feb '19

06 Feb '19

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

1 0

[CQ]: 97562, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 06 Feb '19

06 Feb '19

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

1 0

[CQ]: 97479,7 (cockpit-ovirt) failed "ovirt-master" system tests
by oVirt Jenkins 06 Feb '19

06 Feb '19

Change 97479,7 (cockpit-ovirt) 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/97479/7 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12721/

1 0

[CQ]: 93ba412 (ovirt-ansible-v2v-conversion-host) failed "ovirt-4.2" system tests
by oVirt Jenkins 06 Feb '19

06 Feb '19

Change 93ba412 (ovirt-ansible-v2v-conversion-host) is probably the reason behind recent system test failures in the "ovirt-4.2" 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://github.com/oVirt/ovirt-ansible-v2v-conversion-host/commit/93ba4120b… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3837/

1 0

[JENKINS] Failed to setup proejct vdsm_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 06 Feb '19

06 Feb '19

Failed to run project_setup.sh for: #2629 vdsm [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0038.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct vdsm_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 06 Feb '19

06 Feb '19

Failed to run project_setup.sh for: #2628 vdsm [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0094.workers-phx.ovirt.org.

1 0

[CQ]: 97437, 6 (ovirt-hosted-engine-setup) failed "ovirt-master" system tests
by oVirt Jenkins 06 Feb '19

06 Feb '19

Change 97437,6 (ovirt-hosted-engine-setup) 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/97437/6 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12716/

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 06 Feb '19

06 Feb '19

Failed to run project_setup.sh for: #3454 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-xbpkf.

1 0

[JIRA] (OVIRT-2671) Re: Rename GitHub repo ovirt-ansible-v2v-conversion-host
by Anton Marchukov (oVirt JIRA) 06 Feb '19

06 Feb '19

Anton Marchukov created OVIRT-2671: -------------------------------------- Summary: Re: Rename GitHub repo ovirt-ansible-v2v-conversion-host Key: OVIRT-2671 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2671 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Anton Marchukov Assignee: infra Openning a ticket. On Tue, Feb 5, 2019 at 11:55 AM Tomáš Golembiovský <tgolembi(a)redhat.com> wrote: > Hi, > > I would like to rename the GitHub repo ovirt-ansible-v2v-conversion-host > to v2v-conversion-host. Is there a list of things I should do before > or after the operation? Will the automation still work? > > Tomas > > -- > Tomáš Golembiovský <tgolembi(a)redhat.com> > _______________________________________________ > Infra mailing list -- infra(a)ovirt.org > To unsubscribe send an email to infra-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/infra@ovirt.org/message/WFEG3OQ3Q2DDX… > -- Anton Marchukov Team Lead - Release Management - RHV DevOps - Red Hat -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

Rename GitHub repo ovirt-ansible-v2v-conversion-host
by Tomáš Golembiovský 06 Feb '19

06 Feb '19

Hi, I would like to rename the GitHub repo ovirt-ansible-v2v-conversion-host to v2v-conversion-host. Is there a list of things I should do before or after the operation? Will the automation still work? Tomas -- Tomáš Golembiovský <tgolembi(a)redhat.com>

5 5

[JIRA] (OVIRT-2670) ReadTheDocs content is out of date
by Barak Korren (oVirt JIRA) 06 Feb '19

06 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2670?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2670: ------------------------------------- RTD runs from GitHub, but GitHub does seem to contain the latest commit: https://github.com/oVirt/infra-docs/commit/346247a826baa70bc855c0aff225395a… The last RTD buils seems to have happened 5 months, 1 week ago. So we're having some issue with triggering. I've started a build right now, changed some settings so it might work next time - not sure... > ReadTheDocs content is out of date > ---------------------------------- > > Key: OVIRT-2670 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2670 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: infra > > I was trying to look up docs that were merged several weeks ago and couldn't find it. > Sample commit: > https://github.com/oVirt/infra-docs/commit/8ed6635042ef06d7ff7af7388ceb2fae… > Content in git: > https://github.com/oVirt/infra-docs/blob/master/docs/Phoenix_Lab/OpenShift.… > Section absent completely on RTD: > https://ovirt-infra-docs.readthedocs.io/en/latest/Phoenix_Lab/OpenShift/ind… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2669) CI scripts try to modify unrelated bugs
by Anton Marchukov (oVirt JIRA) 06 Feb '19

06 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2669?page=com.atlassian.jira.… ] Anton Marchukov commented on OVIRT-2669: ---------------------------------------- ---------- Forwarded message --------- From: Nir Soffer <nsoffer(a)redhat.com> Date: Tue, Feb 5, 2019 at 10:16 AM Subject: CI scripts try to modify unrelated bugs To: <infra-support(a)ovirt.org> Cc: infra <infra(a)ovirt.org>, devel <devel(a)ovirt.org>, Vojtech Juranek < vjuranek(a)redhat.com> If a commit message mention another bug, the CI script try to add the patch to the bug in the commit message, and change the bug to POST. Mentioning another bug in a commit message is good practice, making it easier to follow, and avoiding unclear forms like "bug 1000000" or "BZ#1000000", or even worse shortened urls like https://goo.gl/bPuFGo. Does it make sense that we cannot link to Red Hat bugzilla like god intended? Here is a proof: https://gerrit.ovirt.org/c/97568/ gerrit-hooks Patch Set 1: Check Bug-Url::10000000::WARN, failed to get bug info (private bug or bug doesn't exist Check Product::IGNORE, not relevant for branch: master Check TM::IGNORE, not relevant for branch: master Check Backport::IGNORE, not relevant for branch: master Set POST::#10000000::WARN, failed to get bug info (private bug or bug doesn't exist) Update Tracker::#10000000::WARN, failed to get bug info (private bug or bug doesn't exist) CI scripts should process urls only inside Bug-Url: tag. Expected behavior: Extract bug urls *only* from Bug-Url: label. The same issue exists with Related-To: label. This is not a new bug. I reported it few years ago but for some reason the issue was not understood. Nir _______________________________________________ Infra mailing list -- infra(a)ovirt.org To unsubscribe send an email to infra-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/YZKHQTISCF6W3… -- Anton Marchukov Team Lead - Release Management - RHV DevOps - Red Hat > CI scripts try to modify unrelated bugs > --------------------------------------- > > Key: OVIRT-2669 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2669 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > If a commit message mention another bug, the CI script try to add the patch > to the bug in the commit message, and change the bug to POST. > Mentioning another bug in a commit message is good practice, making it > easier to follow, and avoiding unclear forms like "bug 1000000" or > "BZ#1000000", > or even worse shortened urls like https://goo.gl/bPuFGo. > Does it make sense that we cannot link to Red Hat bugzilla like god > intended? > Here is a proof: > https://gerrit.ovirt.org/c/97568/ > gerrit-hooks > Patch Set 1: > Check Bug-Url::10000000::WARN, failed to get bug info (private bug or > bug doesn't exist > Check Product::IGNORE, not relevant for branch: master > Check TM::IGNORE, not relevant for branch: master > Check Backport::IGNORE, not relevant for branch: master > Set POST::#10000000::WARN, failed to get bug info (private bug or bug > doesn't exist) > Update Tracker::#10000000::WARN, failed to get bug info (private bug or > bug doesn't exist) > CI scripts should process urls only inside Bug-Url: tag. > Expected behavior: > Extract bug urls *only* from Bug-Url: label. > The same issue exists with Related-To: label. > This is not a new bug. I reported it few years ago but for some reason the > issue > was not understood. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

snt.utwente.nl mirror out of date
by Evgheni Dereveanchin 06 Feb '19

06 Feb '19

Hello, Our monitoring reports that the oVirt mirror hosted at http://ftp.snt.utwente.nl/pub/software/ovirt is out of date and not updating for several days. Could you please check and fix the sync issue? -- Regards, Evgheni Dereveanchin

1 1

[CQ]: 96974fa (ovirt-ansible-hosted-engine-setup) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 06 Feb '19

06 Feb '19

A system test invoked by the "ovirt-master" change queue including change 96974fa (ovirt-ansible-hosted-engine-setup) failed. However, this change seems not to be the root cause for this failure. Change 9267118 (ovirt-ansible- hosted-engine-setup) 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 9267118 (ovirt-ansible-hosted- engine-setup) 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-ansible-hosted-engine-setup/commit/96974fad1… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/9267118f4… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12712/

1 0

[JIRA] (OVIRT-2670) ReadTheDocs content is out of date
by Evgheni Dereveanchin (oVirt JIRA) 06 Feb '19

06 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2670?page=com.atlassian.jira.… ] Evgheni Dereveanchin commented on OVIRT-2670: --------------------------------------------- Here's the gerrit change so that we can follow up how CI worked after merging: https://gerrit.ovirt.org/#/c/97010/ > ReadTheDocs content is out of date > ---------------------------------- > > Key: OVIRT-2670 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2670 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: infra > > I was trying to look up docs that were merged several weeks ago and couldn't find it. > Sample commit: > https://github.com/oVirt/infra-docs/commit/8ed6635042ef06d7ff7af7388ceb2fae… > Content in git: > https://github.com/oVirt/infra-docs/blob/master/docs/Phoenix_Lab/OpenShift.… > Section absent completely on RTD: > https://ovirt-infra-docs.readthedocs.io/en/latest/Phoenix_Lab/OpenShift/ind… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2670) ReadTheDocs content is out of date
by Evgheni Dereveanchin (oVirt JIRA) 06 Feb '19

06 Feb '19

Evgheni Dereveanchin created OVIRT-2670: ------------------------------------------- Summary: ReadTheDocs content is out of date Key: OVIRT-2670 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2670 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Evgheni Dereveanchin Assignee: infra I was trying to look up docs that were merged several weeks ago and couldn't find it. Sample commit: https://github.com/oVirt/infra-docs/commit/8ed6635042ef06d7ff7af7388ceb2fae… Content in git: https://github.com/oVirt/infra-docs/blob/master/docs/Phoenix_Lab/OpenShift.… Section absent completely on RTD: https://ovirt-infra-docs.readthedocs.io/en/latest/Phoenix_Lab/OpenShift/ind… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[CQ]: 97075, 12 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 06 Feb '19

06 Feb '19

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

1 0

[CQ]: 97572, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 06 Feb '19

06 Feb '19

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

1 0

[CQ]: 97521, 2 (ovirt-provider-ovn) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 06 Feb '19

06 Feb '19

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

1 0

[CQ]: 96490,17 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 06 Feb '19

06 Feb '19

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

1 0

[CQ]: 97395, 9 (ovirt-provider-ovn) failed "ovirt-master" system tests
by oVirt Jenkins 06 Feb '19

06 Feb '19

Change 97395,9 (ovirt-provider-ovn) 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/97395/9 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12692/

1 0

[CQ]: 97521, 2 (ovirt-provider-ovn) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 06 Feb '19

06 Feb '19

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

1 0

[CQ]: 97395, 9 (ovirt-provider-ovn) failed "ovirt-master" system tests
by oVirt Jenkins 06 Feb '19

06 Feb '19

Change 97395,9 (ovirt-provider-ovn) 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/97395/9 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12684/

1 0

[CQ]: 97561, 2 (ovirt-engine-ui-extensions) failed "ovirt-master" system tests
by oVirt Jenkins 06 Feb '19

06 Feb '19

Change 97561,2 (ovirt-engine-ui-extensions) 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/97561/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12679/

1 0

oVirt infra daily report - unstable production jobs - 727
by jenkins＠jenkins.phx.ovirt.org 06 Feb '19

06 Feb '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/727//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 97532,2 (ovirt-appliance) failed "ovirt-master" system tests
by oVirt Jenkins 05 Feb '19

05 Feb '19

Change 97532,2 (ovirt-appliance) 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/97532/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12674/

1 0

[CQ]: 88c6916 (ovirt-ansible-infra) failed "ovirt-master" system tests
by oVirt Jenkins 05 Feb '19

05 Feb '19

Change 88c6916 (ovirt-ansible-infra) 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://github.com/oVirt/ovirt-ansible-infra/commit/88c6916af18b01228c7823e… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12669/

1 0

[CQ]: 97479,7 (cockpit-ovirt) failed "ovirt-master" system tests
by oVirt Jenkins 05 Feb '19

05 Feb '19

Change 97479,7 (cockpit-ovirt) 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/97479/7 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12664/

1 0

[CQ]: 97437, 6 (ovirt-hosted-engine-setup) failed "ovirt-master" system tests
by oVirt Jenkins 05 Feb '19

05 Feb '19

Change 97437,6 (ovirt-hosted-engine-setup) 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/97437/6 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12659/

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 05 Feb '19

05 Feb '19

Failed to run project_setup.sh for: #3440 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-msx6n.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 05 Feb '19

05 Feb '19

Failed to run project_setup.sh for: #3440 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-q0s3t.

1 0

[CQ]: 96974fa (ovirt-ansible-hosted-engine-setup) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Feb '19

05 Feb '19

A system test invoked by the "ovirt-master" change queue including change 96974fa (ovirt-ansible-hosted-engine-setup) failed. However, this change seems not to be the root cause for this failure. Change 9267118 (ovirt-ansible- hosted-engine-setup) 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 9267118 (ovirt-ansible-hosted- engine-setup) 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-ansible-hosted-engine-setup/commit/96974fad1… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/9267118f4… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12655/

1 0

[JIRA] (OVIRT-2666) OST fails with LagoDeployError: ... failed with status 1 on lago-basic-suite-master-host-0
by Dafna Ron (oVirt JIRA) 05 Feb '19

05 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2666?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2666: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > OST fails with LagoDeployError: ... failed with status 1 on lago-basic-suite-master-host-0 > ------------------------------------------------------------------------------------------ > > Key: OVIRT-2666 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2666 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > Labels: ost_failures, ost_packages > > I had 2 OST failure today with the same infrastructure failure, before > running any test: > + install_cmd='yum install --nogpgcheck --downloaddir=/dev/shm -y' > + yum install --nogpgcheck --downloaddir=/dev/shm -y ntp net-snmp > ovirt-engine ovirt-log-collector 'ovirt-engine-extension-aaa-ldap*' > otopi-debug-plugins cronie > Error: Package: 7:device-mapper-event-1.02.149-10.el7_6.3.x86_64 > (alocalsync) > Requires: device-mapper = 7:1.02.149-10.el7_6.3 > Installed: 7:device-mapper-1.02.149-10.el7_6.2.x86_64 (installed) > device-mapper = 7:1.02.149-10.el7_6.2 > ret=1 > + echo 'install failed with status 1' > + exit 1 > - STDERR > Links to failed builds: > - > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_man… > - > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_man… > The last successful build was at Feb 1: > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/4004/ > The trend show that all builds failed since Feb 3 9:02 am. > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/buildTimeTrend > This issue is blocking 4.3 work on 4k support. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2666) OST fails with LagoDeployError: ... failed with status 1 on lago-basic-suite-master-host-0
by Dafna Ron (oVirt JIRA) 05 Feb '19

05 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2666?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2666: ---------------------------------- Galit merged a fix and upstream is fix. Closing this as resolved. Please re-open if this is still happening for you. > OST fails with LagoDeployError: ... failed with status 1 on lago-basic-suite-master-host-0 > ------------------------------------------------------------------------------------------ > > Key: OVIRT-2666 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2666 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > Labels: ost_failures, ost_packages > > I had 2 OST failure today with the same infrastructure failure, before > running any test: > + install_cmd='yum install --nogpgcheck --downloaddir=/dev/shm -y' > + yum install --nogpgcheck --downloaddir=/dev/shm -y ntp net-snmp > ovirt-engine ovirt-log-collector 'ovirt-engine-extension-aaa-ldap*' > otopi-debug-plugins cronie > Error: Package: 7:device-mapper-event-1.02.149-10.el7_6.3.x86_64 > (alocalsync) > Requires: device-mapper = 7:1.02.149-10.el7_6.3 > Installed: 7:device-mapper-1.02.149-10.el7_6.2.x86_64 (installed) > device-mapper = 7:1.02.149-10.el7_6.2 > ret=1 > + echo 'install failed with status 1' > + exit 1 > - STDERR > Links to failed builds: > - > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_man… > - > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_man… > The last successful build was at Feb 1: > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/4004/ > The trend show that all builds failed since Feb 3 9:02 am. > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/buildTimeTrend > This issue is blocking 4.3 work on 4k support. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2669) CI scripts try to modify unrelated bugs
by Ehud Yonasi (oVirt JIRA) 05 Feb '19

05 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2669?page=com.atlassian.jira.… ] Ehud Yonasi updated OVIRT-2669: ------------------------------- Resolution: Duplicate Status: Done (was: To Do) > CI scripts try to modify unrelated bugs > --------------------------------------- > > Key: OVIRT-2669 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2669 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > If a commit message mention another bug, the CI script try to add the patch > to the bug in the commit message, and change the bug to POST. > Mentioning another bug in a commit message is good practice, making it > easier to follow, and avoiding unclear forms like "bug 1000000" or > "BZ#1000000", > or even worse shortened urls like https://goo.gl/bPuFGo. > Does it make sense that we cannot link to Red Hat bugzilla like god > intended? > Here is a proof: > https://gerrit.ovirt.org/c/97568/ > gerrit-hooks > Patch Set 1: > Check Bug-Url::10000000::WARN, failed to get bug info (private bug or > bug doesn't exist > Check Product::IGNORE, not relevant for branch: master > Check TM::IGNORE, not relevant for branch: master > Check Backport::IGNORE, not relevant for branch: master > Set POST::#10000000::WARN, failed to get bug info (private bug or bug > doesn't exist) > Update Tracker::#10000000::WARN, failed to get bug info (private bug or > bug doesn't exist) > CI scripts should process urls only inside Bug-Url: tag. > Expected behavior: > Extract bug urls *only* from Bug-Url: label. > The same issue exists with Related-To: label. > This is not a new bug. I reported it few years ago but for some reason the > issue > was not understood. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2669) CI scripts try to modify unrelated bugs
by Ehud Yonasi (oVirt JIRA) 05 Feb '19

05 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2669?page=com.atlassian.jira.… ] Ehud Yonasi commented on OVIRT-2669: ------------------------------------ Closing this ticket, opening in d/s jira. > CI scripts try to modify unrelated bugs > --------------------------------------- > > Key: OVIRT-2669 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2669 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > If a commit message mention another bug, the CI script try to add the patch > to the bug in the commit message, and change the bug to POST. > Mentioning another bug in a commit message is good practice, making it > easier to follow, and avoiding unclear forms like "bug 1000000" or > "BZ#1000000", > or even worse shortened urls like https://goo.gl/bPuFGo. > Does it make sense that we cannot link to Red Hat bugzilla like god > intended? > Here is a proof: > https://gerrit.ovirt.org/c/97568/ > gerrit-hooks > Patch Set 1: > Check Bug-Url::10000000::WARN, failed to get bug info (private bug or > bug doesn't exist > Check Product::IGNORE, not relevant for branch: master > Check TM::IGNORE, not relevant for branch: master > Check Backport::IGNORE, not relevant for branch: master > Set POST::#10000000::WARN, failed to get bug info (private bug or bug > doesn't exist) > Update Tracker::#10000000::WARN, failed to get bug info (private bug or > bug doesn't exist) > CI scripts should process urls only inside Bug-Url: tag. > Expected behavior: > Extract bug urls *only* from Bug-Url: label. > The same issue exists with Related-To: label. > This is not a new bug. I reported it few years ago but for some reason the > issue > was not understood. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 05 Feb '19

05 Feb '19

Failed to run project_setup.sh for: #3436 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-xxlnf.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 05 Feb '19

05 Feb '19

Failed to run project_setup.sh for: #3433 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-n1p89.

1 0

[JIRA] (OVIRT-2669) CI scripts try to modify unrelated bugs
by Nir Soffer (oVirt JIRA) 05 Feb '19

05 Feb '19

Nir Soffer created OVIRT-2669: --------------------------------- Summary: CI scripts try to modify unrelated bugs Key: OVIRT-2669 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2669 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra If a commit message mention another bug, the CI script try to add the patch to the bug in the commit message, and change the bug to POST. Mentioning another bug in a commit message is good practice, making it easier to follow, and avoiding unclear forms like "bug 1000000" or "BZ#1000000", or even worse shortened urls like https://goo.gl/bPuFGo. Does it make sense that we cannot link to Red Hat bugzilla like god intended? Here is a proof: https://gerrit.ovirt.org/c/97568/ gerrit-hooks Patch Set 1: Check Bug-Url::10000000::WARN, failed to get bug info (private bug or bug doesn't exist Check Product::IGNORE, not relevant for branch: master Check TM::IGNORE, not relevant for branch: master Check Backport::IGNORE, not relevant for branch: master Set POST::#10000000::WARN, failed to get bug info (private bug or bug doesn't exist) Update Tracker::#10000000::WARN, failed to get bug info (private bug or bug doesn't exist) CI scripts should process urls only inside Bug-Url: tag. Expected behavior: Extract bug urls *only* from Bug-Url: label. The same issue exists with Related-To: label. This is not a new bug. I reported it few years ago but for some reason the issue was not understood. Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

CI scripts try to modify unrelated bugs
by Nir Soffer 05 Feb '19

05 Feb '19

If a commit message mention another bug, the CI script try to add the patch to the bug in the commit message, and change the bug to POST. Mentioning another bug in a commit message is good practice, making it easier to follow, and avoiding unclear forms like "bug 1000000" or "BZ#1000000", or even worse shortened urls like https://goo.gl/bPuFGo. Does it make sense that we cannot link to Red Hat bugzilla like god intended? Here is a proof: https://gerrit.ovirt.org/c/97568/ gerrit-hooks Patch Set 1: Check Bug-Url::10000000::WARN, failed to get bug info (private bug or bug doesn't exist Check Product::IGNORE, not relevant for branch: master Check TM::IGNORE, not relevant for branch: master Check Backport::IGNORE, not relevant for branch: master Set POST::#10000000::WARN, failed to get bug info (private bug or bug doesn't exist) Update Tracker::#10000000::WARN, failed to get bug info (private bug or bug doesn't exist) CI scripts should process urls only inside Bug-Url: tag. Expected behavior: Extract bug urls *only* from Bug-Url: label. The same issue exists with Related-To: label. This is not a new bug. I reported it few years ago but for some reason the issue was not understood. Nir

1 0

[JIRA] (OVIRT-2668) WildFly 15 packages got to tested-4.3 repo, but not to tested-master repo
by Ehud Yonasi (oVirt JIRA) 05 Feb '19

05 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2668?page=com.atlassian.jira.… ] Ehud Yonasi reassigned OVIRT-2668: ---------------------------------- Assignee: Ehud Yonasi (was: infra) > WildFly 15 packages got to tested-4.3 repo, but not to tested-master repo > ------------------------------------------------------------------------- > > Key: OVIRT-2668 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2668 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Martin Perina > Assignee: Ehud Yonasi > > Hi, > I have a problem with publishing WildFly 15 packages to tested repos for master and 4.3. I've merged [#97474|https://gerrit.ovirt.org/97474] and next day I've found out that [ovirt-engine-wildfly-15.0.1-1.el7.x86_64.rpm|https://plain.resources.ovirt.…] and [ovirt-engine-wildfly-overlay-15.0.1-1.el7.noarch.rpm|https://plain.resource…] packages appeared in ovirt-4.3 tested repo, but they were not published to master-tested repo, although I have both branches mentioned in [stdci.yaml|https://github.com/oVirt/ovirt-engine-wildfly/blob/master/stdci.…] in the project. > Is it some issue with stdci.yaml or something went wrong in CQ publishing? > The absence of WildFly 15 in master-tested repo blocks finishing of [BZ1671635|https://bugzilla.redhat.com/1671635] > Thanks > Martin -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2668) WildFly 15 packages got to tested-4.3 repo, but not to tested-master repo
by Ehud Yonasi (oVirt JIRA) 05 Feb '19

05 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2668?page=com.atlassian.jira.… ] Ehud Yonasi commented on OVIRT-2668: ------------------------------------ Hi [~mwperina], It was published into master CQ, but since there was a packaging issue that was solved today, all master cq jobs failed. I've re-added your patch into the cq system and if it passes CQ, it should be published to tested. > WildFly 15 packages got to tested-4.3 repo, but not to tested-master repo > ------------------------------------------------------------------------- > > Key: OVIRT-2668 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2668 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Martin Perina > Assignee: infra > > Hi, > I have a problem with publishing WildFly 15 packages to tested repos for master and 4.3. I've merged [#97474|https://gerrit.ovirt.org/97474] and next day I've found out that [ovirt-engine-wildfly-15.0.1-1.el7.x86_64.rpm|https://plain.resources.ovirt.…] and [ovirt-engine-wildfly-overlay-15.0.1-1.el7.noarch.rpm|https://plain.resource…] packages appeared in ovirt-4.3 tested repo, but they were not published to master-tested repo, although I have both branches mentioned in [stdci.yaml|https://github.com/oVirt/ovirt-engine-wildfly/blob/master/stdci.…] in the project. > Is it some issue with stdci.yaml or something went wrong in CQ publishing? > The absence of WildFly 15 in master-tested repo blocks finishing of [BZ1671635|https://bugzilla.redhat.com/1671635] > Thanks > Martin -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2668) WildFly 15 packages got to tested-4.3 repo, but not to tested-master repo
by Martin Perina (oVirt JIRA) 05 Feb '19

05 Feb '19

Martin Perina created OVIRT-2668: ------------------------------------ Summary: WildFly 15 packages got to tested-4.3 repo, but not to tested-master repo Key: OVIRT-2668 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2668 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Martin Perina Assignee: infra Hi, I have a problem with publishing WildFly 15 packages to tested repos for master and 4.3. I've merged [#97474|https://gerrit.ovirt.org/97474] and next day I've found out that [ovirt-engine-wildfly-15.0.1-1.el7.x86_64.rpm|https://plain.resources.ovirt.…] and [ovirt-engine-wildfly-overlay-15.0.1-1.el7.noarch.rpm|https://plain.resource…] packages appeared in ovirt-4.3 tested repo, but they were not published to master-tested repo, although I have both branches mentioned in [stdci.yaml|https://github.com/oVirt/ovirt-engine-wildfly/blob/master/stdci.…] in the project. Is it some issue with stdci.yaml or something went wrong in CQ publishing? The absence of WildFly 15 in master-tested repo blocks finishing of [BZ1671635|https://bugzilla.redhat.com/1671635] Thanks Martin -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

Build failed in Jenkins: system-sync_mirrors-fedora-base-fc29-x86_64 #269
by jenkins＠jenkins.phx.ovirt.org 05 Feb '19

05 Feb '19

See <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-base-fc29-x86_64/26…> Changes: [Sandro Bonazzola] ovirt-release: move to check-patch to v2 ------------------------------------------ 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-fc29-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 0c58c6af77462077362709504192b5388a90f207 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 0c58c6af77462077362709504192b5388a90f207 Commit message: "ovirt-release: move to check-patch to v2" > git rev-list --no-walk 2475ed85fd8420315ce9833bd51cc956f7bda7e8 # timeout=10 [system-sync_mirrors-fedora-base-fc29-x86_64] $ /bin/bash -xe /tmp/jenkins8359310665409060836.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror fedora-base-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-base-fc29 x86_64 jenkins/data/mirrors-reposync.conf + local command=resync_yum_mirror + command_args=("${@:2}") + local command_args + cmd_resync_yum_mirror fedora-base-fc29 x86_64 jenkins/data/mirrors-reposync.conf + local repo_name=fedora-base-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-base-fc29 yum + local repo_name=fedora-base-fc29 + local repo_type=yum + sudo install -o jenkins -d /var/www/html/repos/yum /var/www/html/repos/yum/fedora-base-fc29 /var/www/html/repos/yum/fedora-base-fc29/base + check_yum_sync_needed fedora-base-fc29 x86_64 jenkins/data/mirrors-reposync.conf sync_needed + local repo_name=fedora-base-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-base-fc29 ++ IFS=, ++ echo x86_64 + for arch in '$(IFS=,; echo $repo_archs)' ++ run_reposync fedora-base-fc29 x86_64 jenkins/data/mirrors-reposync.conf --urls --quiet ++ local repo_name=fedora-base-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-base-fc29 --arch=x86_64 --cachedir=/home/jenkins/mirrors_cache --download_path=/var/www/html/repos/yum/fedora-base-fc29/base --norepopath --newest-only --urls --quiet 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 189, in __init__ raise MetaLinkRepoErrorParseFail, "File %s is not XML" % filename yum.metalink.MetaLinkRepoErrorParseFail: File /home/jenkins/mirrors_cache/fedora-base-fc29/metalink.xml is not XML + reposync_out='Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=fedora-29&arch=x86_64 error was 16: error opening file from https://mirrors.fedoraproject.org/metalink?repo=fedora-29&arch=x86_64, IOError: [Errno 2] No such file or directory: '\''/home/jenkins/mirrors_cache/fedora-base-fc29/metalink.xml.tmp'\''' Build step 'Execute shell' marked build as failure

1 1

oVirt infra daily report - unstable production jobs - 726
by jenkins＠jenkins.phx.ovirt.org 05 Feb '19

05 Feb '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/726//artifact/exported-a… Cheers, Jenkins

1 0