February 2019 - Infra - oVirt List Archives

[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