- Infra - oVirt List Archives

[CQ]: 83487, 1 (imgbased) failed "ovirt-4.1" system tests, but isn't the failure root cause
by oVirt Jenkins 02 Nov '17

02 Nov '17

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

1 0

[JIRA] (OVIRT-1736) Kubevirt's check-patch leaves orphan networks
by Gal Ben Haim (oVirt JIRA) 02 Nov '17

02 Nov '17

This is a multi-part message in MIME format... ------------=_1509638452-18687-239 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1736?page=com.atlassian.jira.… ] Gal Ben Haim reassigned OVIRT-1736: ----------------------------------- Assignee: Barak Korren (was: infra) > Kubevirt's check-patch leaves orphan networks > --------------------------------------------- > > Key: OVIRT-1736 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1736 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Gal Ben Haim > Assignee: Barak Korren > Priority: Highest > > Kubevirt's check-patch leaves 2 orphan networks: > - kubevirt0 > - vagrant-libvirt > kubevirt0 as the IP 192.168.200.1, which is in the range of lago's networks (lago's range is 192.168.200.x - 192.168.255.x). > This issue cause jobs that use lago to fail. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070) ------------=_1509638452-18687-239 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1736?page=com.atlassian.jira.… ]</pre> <h3>Gal Ben Haim reassigned OVIRT-1736:</h3> <pre>Assignee: Barak Korren (was: infra)</pre> <blockquote><h3>Kubevirt's check-patch leaves orphan networks</h3> <pre> Key: OVIRT-1736 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1736 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Gal Ben Haim Assignee: Barak Korren Priority: Highest</pre> <p>Kubevirt's check-patch leaves 2 orphan networks:</p> <pre>- kubevirt0 - vagrant-libvirt</pre> <p>kubevirt0 as the IP 192.168.200.1, which is in the range of lago's networks (lago's range is 192.168.200.x – 192.168.255.x). This issue cause jobs that use lago to fail.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1509638452-18687-239--

1 0

[JIRA] (OVIRT-1736) Kubevirt's check-patch leaves orphan networks
by Gal Ben Haim (oVirt JIRA) 02 Nov '17

02 Nov '17

This is a multi-part message in MIME format... ------------=_1509638440-20995-207 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Gal Ben Haim created OVIRT-1736: ----------------------------------- Summary: Kubevirt's check-patch leaves orphan networks Key: OVIRT-1736 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1736 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Gal Ben Haim Assignee: infra Priority: Highest Kubevirt's check-patch leaves 2 orphan networks: - kubevirt0 - vagrant-libvirt kubevirt0 as the IP 192.168.200.1, which is in the range of lago's networks (lago's range is 192.168.200.x - 192.168.255.x). This issue cause jobs that use lago to fail. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070) ------------=_1509638440-20995-207 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Gal Ben Haim created OVIRT-1736:</h3> <pre> Summary: Kubevirt's check-patch leaves orphan networks Key: OVIRT-1736 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1736 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Gal Ben Haim Assignee: infra Priority: Highest</pre> <p>Kubevirt's check-patch leaves 2 orphan networks:</p> <pre>- kubevirt0 - vagrant-libvirt</pre> <p>kubevirt0 as the IP 192.168.200.1, which is in the range of lago's networks (lago's range is 192.168.200.x – 192.168.255.x).</p> <p>This issue cause jobs that use lago to fail.</p> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1509638440-20995-207--

1 0

[CQ]: 83509, 2 (ovirt-engine) failed "ovirt-4.1" system tests, but isn't the failure root cause
by oVirt Jenkins 02 Nov '17

02 Nov '17

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

1 0

[CQ]: 83527, 1 (ovirt-live) failed "ovirt-4.1" system tests, but isn't the failure root cause
by oVirt Jenkins 02 Nov '17

02 Nov '17

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

1 0

[CQ]: 82219, 14 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 02 Nov '17

02 Nov '17

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

1 0

[CQ]: 83472,4 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 02 Nov '17

02 Nov '17

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

1 0

[CQ]: 83527, 1 (ovirt-live) failed "ovirt-4.1" system tests, but isn't the failure root cause
by oVirt Jenkins 02 Nov '17

02 Nov '17

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

1 0

[JIRA] (OVIRT-1735) Upgrade ovirt production in PHX to 4.2 (beta/rc)
by eyal edri (oVirt JIRA) 02 Nov '17

02 Nov '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1735?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1735: ----------------------------- Epic Link: OVIRT-403 > Upgrade ovirt production in PHX to 4.2 (beta/rc) > ------------------------------------------------ > > Key: OVIRT-1735 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1735 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri > Assignee: infra > Priority: High > > Since oVirt 4.2 is very stable to our best knowledge, with people even upgraded production environments to alpha build even, we should start working on upgrading ( hosts first and then engine ) our PHX env as well. > Since we have staging env, we can start there with the beta build and then continue to the production one. > This can help us find critical issues that might not be found on normal testing and a chance to fix them before GA. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)

1 0

[JIRA] (OVIRT-1735) Upgrade ovirt production in PHX to 4.2 (beta/rc)
by eyal edri (oVirt JIRA) 02 Nov '17

02 Nov '17

This is a multi-part message in MIME format... ------------=_1509628570-32224-145 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit eyal edri created OVIRT-1735: -------------------------------- Summary: Upgrade ovirt production in PHX to 4.2 (beta/rc) Key: OVIRT-1735 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1735 Project: oVirt - virtualization made easy Issue Type: Task Reporter: eyal edri Assignee: infra Priority: High Since oVirt 4.2 is very stable to our best knowledge, with people even upgraded production environments to alpha build even, we should start working on upgrading ( hosts first and then engine ) our PHX env as well. Since we have staging env, we can start there with the beta build and then continue to the production one. This can help us find critical issues that might not be found on normal testing and a chance to fix them before GA. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070) ------------=_1509628570-32224-145 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>eyal edri created OVIRT-1735:</h3> <pre> Summary: Upgrade ovirt production in PHX to 4.2 (beta/rc) Key: OVIRT-1735 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1735 Project: oVirt - virtualization made easy Issue Type: Task Reporter: eyal edri Assignee: infra Priority: High</pre> <p>Since oVirt 4.2 is very stable to our best knowledge, with people even upgraded production environments to alpha build even, we should start working on upgrading ( hosts first and then engine ) our PHX env as well.</p> <p>Since we have staging env, we can start there with the beta build and then continue to the production one.</p> <p>This can help us find critical issues that might not be found on normal testing and a chance to fix them before GA.</p> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1509628570-32224-145--

1 0