February 2018 - Infra - oVirt List Archives

[CQ]: 86968, 1 (ovirt-engine-wildfly) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 01 Feb '18

01 Feb '18

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

1 0

[CQ]: 86967, 1 (ovirt-hosted-engine-setup) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 01 Feb '18

01 Feb '18

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

1 0

[oVirt CI] standard-enqueue - Build #9474 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 01 Feb '18

01 Feb '18

------=_Part_451_1469550335.1517479434683 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/standard-enqueue/9474/ Build Name: #9474 Build Description: Gerrit: 82649 - ovirt-image-uploader (4.0, 4.1, 4.2, master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/82649 - title: automation: drop snapshot repos - project: ovirt-image-uploader - branch: ovirt-image-uploader-4.0 - author: Sandro Bonazzola <sbonazzo(a)redhat.com> ------=_Part_451_1469550335.1517479434683--

1 1

[JIRA] (OVIRT-1871) Wrong target milestone check on new 4.2 branches for ovirt-host-deploy
by sbonazzo (oVirt JIRA) 01 Feb '18

01 Feb '18

This is a multi-part message in MIME format... ------------=_1517478412-30235-139 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1871?page=com.atlassian.jira.… ] sbonazzo updated OVIRT-1871: ---------------------------- Epic Link: OVIRT-400 > Wrong target milestone check on new 4.2 branches for ovirt-host-deploy > ---------------------------------------------------------------------- > > Key: OVIRT-1871 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1871 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Gerrit/git > Reporter: sbonazzo > Assignee: infra > > I branched ovirt-host-deploy for 4.2 stabilization and on the new branch named ovirt-host-deploy-1.7 I get: > Check TM::#1539040::WARN, wrong target milestone: ovirt-4.2.1 (-1) https://gerrit.ovirt.org/#/c/86992/ > I'd like to configure the hook to match the branch with the ovirt-4.2* target milestones but couldn't find documentation on how to do that. > When fixing this, please also include link to how to do that, I've other projects that will need similar change. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100078) ------------=_1517478412-30235-139 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1871?page=com.atlassian.jira.… ]</pre> <h3>sbonazzo updated OVIRT-1871:</h3> <pre>Epic Link: OVIRT-400</pre> <blockquote><h3>Wrong target milestone check on new 4.2 branches for ovirt-host-deploy</h3> <pre> Key: OVIRT-1871 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1871 Project: oVirt - virtualization made easy Issue Type: Bug Components: Gerrit/git Reporter: sbonazzo Assignee: infra</pre> <p>I branched ovirt-host-deploy for 4.2 stabilization and on the new branch named ovirt-host-deploy-1.7 I get: Check TM::#1539040::WARN, wrong target milestone: ovirt-4.2.1 (-1) <a href="https://gerrit.ovirt.org/#/c/86992/">https://gerrit.ovirt.org/#/c/86992/</a> I'd like to configure the hook to match the branch with the ovirt-4.2* target milestones but couldn't find documentation on how to do that. When fixing this, please also include link to how to do that, I've other projects that will need similar change.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100078)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" 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> ------------=_1517478412-30235-139--

1 0

[JIRA] (OVIRT-1871) Wrong target milestone check on new 4.2 branches for ovirt-host-deploy
by sbonazzo (oVirt JIRA) 01 Feb '18

01 Feb '18

This is a multi-part message in MIME format... ------------=_1517478412-20389-117 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit sbonazzo created OVIRT-1871: ------------------------------- Summary: Wrong target milestone check on new 4.2 branches for ovirt-host-deploy Key: OVIRT-1871 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1871 Project: oVirt - virtualization made easy Issue Type: Bug Components: Gerrit/git Reporter: sbonazzo Assignee: infra I branched ovirt-host-deploy for 4.2 stabilization and on the new branch named ovirt-host-deploy-1.7 I get: Check TM::#1539040::WARN, wrong target milestone: ovirt-4.2.1 (-1) https://gerrit.ovirt.org/#/c/86992/ I'd like to configure the hook to match the branch with the ovirt-4.2* target milestones but couldn't find documentation on how to do that. When fixing this, please also include link to how to do that, I've other projects that will need similar change. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100078) ------------=_1517478412-20389-117 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>sbonazzo created OVIRT-1871:</h3> <pre> Summary: Wrong target milestone check on new 4.2 branches for ovirt-host-deploy Key: OVIRT-1871 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1871 Project: oVirt - virtualization made easy Issue Type: Bug Components: Gerrit/git Reporter: sbonazzo Assignee: infra</pre> <p>I branched ovirt-host-deploy for 4.2 stabilization and on the new branch named ovirt-host-deploy-1.7 I get: Check TM::#1539040::WARN, wrong target milestone: ovirt-4.2.1 (-1) <a href="https://gerrit.ovirt.org/#/c/86992/">https://gerrit.ovirt.org/#/c/86992/</a> I'd like to configure the hook to match the branch with the ovirt-4.2* target milestones but couldn't find documentation on how to do that. When fixing this, please also include link to how to do that, I've other projects that will need similar change.</p> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100078)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" 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> ------------=_1517478412-20389-117--

1 0

[JIRA] (OVIRT-1712) OST jobs fails on "address already in use"
by Daniel Belenky (oVirt JIRA) 01 Feb '18

01 Feb '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1712?page=com.atlassian.jira.… ] Daniel Belenky commented on OVIRT-1712: --------------------------------------- [~eedri] We'll probably add a cleanup function to global setup to ensure that lago can run smoothly. I'll talk with [~gbenhaim(a)redhat.com] offline to see what needs to be done. > OST jobs fails on "address already in use" > ------------------------------------------ > > Key: OVIRT-1712 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1712 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri > Assignee: Gal Ben Haim > Priority: High > > Evgheni, > Was there any change recently to Lago slaves? > On Fri, Oct 20, 2017 at 11:05 AM, Piotr Kliczewski < > piotr.kliczewski(a)gmail.com> wrote: > > I attempted to run manual OST twice and both failed with below issue. > > Can someone take a look? > > > > Thanks, > > Piotr > > > > 2017-10-20 07:59:12,485::log_utils.py::__exit__::607::ovirtlago.prefix: > > :DEBUG:: > > File "/usr/lib/python2.7/site-packages/lago/log_utils.py", line 636, > > in wrapper > > return func(*args, **kwargs) > > File "/usr/lib/python2.7/site-packages/ovirtlago/reposetup.py", line > > 111, in wrapper > > with utils.repo_server_context(args[0]): > > File "/usr/lib64/python2.7/contextlib.py", line 17, in __enter__ > > return self.gen.next() > > File "/usr/lib/python2.7/site-packages/ovirtlago/utils.py", line > > 100, in repo_server_context > > root_dir=prefix.paths.internal_repo(), > > File "/usr/lib/python2.7/site-packages/ovirtlago/utils.py", line 76, > > in _create_http_server > > generate_request_handler(root_dir), > > File "/usr/lib64/python2.7/SocketServer.py", line 419, in __init__ > > self.server_bind() > > File "/usr/lib64/python2.7/BaseHTTPServer.py", line 108, in server_bind > > SocketServer.TCPServer.server_bind(self) > > File "/usr/lib64/python2.7/SocketServer.py", line 430, in server_bind > > self.socket.bind(self.server_address) > > File "/usr/lib64/python2.7/socket.py", line 224, in meth > > return getattr(self._sock,name)(*args) > > > > 2017-10-20 07:59:12,485::cmd.py::do_run::365::root::ERROR::Error > > occured, aborting > > Traceback (most recent call last): > > File "/usr/lib/python2.7/site-packages/ovirtlago/cmd.py", line 362, in > > do_run > > self.cli_plugins[args.ovirtverb].do_run(args) > > File "/usr/lib/python2.7/site-packages/lago/plugins/cli.py", line > > 184, in do_run > > self._do_run(**vars(args)) > > File "/usr/lib/python2.7/site-packages/lago/utils.py", line 501, in > > wrapper > > return func(*args, **kwargs) > > File "/usr/lib/python2.7/site-packages/lago/utils.py", line 512, in > > wrapper > > return func(*args, prefix=prefix, **kwargs) > > File "/usr/lib/python2.7/site-packages/ovirtlago/cmd.py", line 166, > > in do_deploy > > prefix.deploy() > > File "/usr/lib/python2.7/site-packages/lago/log_utils.py", line 636, > > in wrapper > > return func(*args, **kwargs) > > File "/usr/lib/python2.7/site-packages/ovirtlago/reposetup.py", line > > 111, in wrapper > > with utils.repo_server_context(args[0]): > > File "/usr/lib64/python2.7/contextlib.py", line 17, in __enter__ > > return self.gen.next() > > File "/usr/lib/python2.7/site-packages/ovirtlago/utils.py", line > > 100, in repo_server_context > > root_dir=prefix.paths.internal_repo(), > > File "/usr/lib/python2.7/site-packages/ovirtlago/utils.py", line 76, > > in _create_http_server > > generate_request_handler(root_dir), > > File "/usr/lib64/python2.7/SocketServer.py", line 419, in __init__ > > self.server_bind() > > File "/usr/lib64/python2.7/BaseHTTPServer.py", line 108, in server_bind > > SocketServer.TCPServer.server_bind(self) > > File "/usr/lib64/python2.7/SocketServer.py", line 430, in server_bind > > self.socket.bind(self.server_address) > > File "/usr/lib64/python2.7/socket.py", line 224, in meth > > return getattr(self._sock,name)(*args) > > error: [Errno 98] Address already in use > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > > > -- > 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 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100078)

1 0

[JIRA] (OVIRT-1870) kubevirt_kubevirt_standard-check-pr jobs often get stuck
by Barak Korren (oVirt JIRA) 01 Feb '18

01 Feb '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1870?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1870: -------------------------------- Epic Link: OVIRT-400 > kubevirt_kubevirt_standard-check-pr jobs often get stuck > -------------------------------------------------------- > > Key: OVIRT-1870 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1870 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: CI client projects, Standard CI (Pipelines) > Reporter: Evgheni Dereveanchin > Assignee: infra > > kubevirt_kubevirt_standard-check-pr jobs often get stuck waiting forever for a connection to get established: > http://jenkins.ovirt.org/job/kubevirt_kubevirt_standard-check-pr/376/console > http://jenkins.ovirt.org/job/kubevirt_kubevirt_standard-check-pr/377/console > http://jenkins.ovirt.org/job/kubevirt_kubevirt_standard-check-pr/378/console > http://jenkins.ovirt.org/job/kubevirt_kubevirt_standard-check-pr/380/console > The following message keeps repeating all the time: > 17:03:32 [check-patch.el7.x86_64] ++ awk '/virt-controller/ && /true/' > 17:03:32 [check-patch.el7.x86_64] ++ kubectl get pods -n kube-system '-ocustom-columns=status:status.containerStatuses[*].ready,metadata:metadata.name' --no-headers > 17:03:32 [check-patch.el7.x86_64] ++ wc -l > 17:03:32 [check-patch.el7.x86_64] ++ cluster/kubectl.sh get pods -n kube-system '-ocustom-columns=status:status.containerStatuses[*].ready,metadata:metadata.name' --no-headers > 17:03:44 [check-patch.el7.x86_64] Unable to connect to the server: dial tcp 192.168.121.111:6443: getsockopt: no route to host > 17:03:44 [check-patch.el7.x86_64] + '[' 0 -lt 1 ']' > 17:03:44 [check-patch.el7.x86_64] + echo 'Waiting for KubeVirt virt-controller container to become ready ...' > 17:03:44 [check-patch.el7.x86_64] Waiting for KubeVirt virt-controller container to become ready ... > 17:03:44 [check-patch.el7.x86_64] + kubectl get pods -n kube-system '-ocustom-columns=status:status.containerStatuses[*].ready,metadata:metadata.name' --no-headers > 17:03:44 [check-patch.el7.x86_64] + awk '/virt-controller/ && /true/' > 17:03:44 [check-patch.el7.x86_64] + cluster/kubectl.sh get pods -n kube-system '-ocustom-columns=status:status.containerStatuses[*].ready,metadata:metadata.name' --no-headers > 17:03:44 [check-patch.el7.x86_64] + wc -l > 17:03:56 [check-patch.el7.x86_64] Unable to connect to the server: dial tcp 192.168.121.111:6443: getsockopt: no route to host > 17:03:56 [check-patch.el7.x86_64] 0 > 17:03:56 [check-patch.el7.x86_64] + sleep 10 > Need to implement timeouts as this takes up bare metal systems for days and weeks until someone manually kills the job -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100078)

1 0

[JIRA] (OVIRT-1870) kubevirt_kubevirt_standard-check-pr jobs often get stuck
by Barak Korren (oVirt JIRA) 01 Feb '18

01 Feb '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1870?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1870: ----------------------------------- Assignee: Barak Korren (was: infra) Component/s: Standard CI (Pipelines) CI client projects Epic Link: OVIRT-400 Issue Type: Outage (was: Bug) Priority: Highest (was: Medium) > kubevirt_kubevirt_standard-check-pr jobs often get stuck > -------------------------------------------------------- > > Key: OVIRT-1870 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1870 > Project: oVirt - virtualization made easy > Issue Type: Outage > Components: CI client projects, Standard CI (Pipelines) > Reporter: Evgheni Dereveanchin > Assignee: Barak Korren > Priority: Highest > > kubevirt_kubevirt_standard-check-pr jobs often get stuck waiting forever for a connection to get established: > http://jenkins.ovirt.org/job/kubevirt_kubevirt_standard-check-pr/376/console > http://jenkins.ovirt.org/job/kubevirt_kubevirt_standard-check-pr/377/console > http://jenkins.ovirt.org/job/kubevirt_kubevirt_standard-check-pr/378/console > http://jenkins.ovirt.org/job/kubevirt_kubevirt_standard-check-pr/380/console > The following message keeps repeating all the time: > 17:03:32 [check-patch.el7.x86_64] ++ awk '/virt-controller/ && /true/' > 17:03:32 [check-patch.el7.x86_64] ++ kubectl get pods -n kube-system '-ocustom-columns=status:status.containerStatuses[*].ready,metadata:metadata.name' --no-headers > 17:03:32 [check-patch.el7.x86_64] ++ wc -l > 17:03:32 [check-patch.el7.x86_64] ++ cluster/kubectl.sh get pods -n kube-system '-ocustom-columns=status:status.containerStatuses[*].ready,metadata:metadata.name' --no-headers > 17:03:44 [check-patch.el7.x86_64] Unable to connect to the server: dial tcp 192.168.121.111:6443: getsockopt: no route to host > 17:03:44 [check-patch.el7.x86_64] + '[' 0 -lt 1 ']' > 17:03:44 [check-patch.el7.x86_64] + echo 'Waiting for KubeVirt virt-controller container to become ready ...' > 17:03:44 [check-patch.el7.x86_64] Waiting for KubeVirt virt-controller container to become ready ... > 17:03:44 [check-patch.el7.x86_64] + kubectl get pods -n kube-system '-ocustom-columns=status:status.containerStatuses[*].ready,metadata:metadata.name' --no-headers > 17:03:44 [check-patch.el7.x86_64] + awk '/virt-controller/ && /true/' > 17:03:44 [check-patch.el7.x86_64] + cluster/kubectl.sh get pods -n kube-system '-ocustom-columns=status:status.containerStatuses[*].ready,metadata:metadata.name' --no-headers > 17:03:44 [check-patch.el7.x86_64] + wc -l > 17:03:56 [check-patch.el7.x86_64] Unable to connect to the server: dial tcp 192.168.121.111:6443: getsockopt: no route to host > 17:03:56 [check-patch.el7.x86_64] 0 > 17:03:56 [check-patch.el7.x86_64] + sleep 10 > Need to implement timeouts as this takes up bare metal systems for days and weeks until someone manually kills the job -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100078)

1 0