August 2017 - Infra - oVirt List Archives

[CQ]: 81154, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 30 Aug '17

30 Aug '17

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

1 0

[CQ]: 81138, 1 (ovirt-log-collector) failed "ovirt-master" system tests
by oVirt Jenkins 30 Aug '17

30 Aug '17

Change 81138,1 (ovirt-log-collector) 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/81138/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/2151/

1 0

[CQ]: 81182,5 (ovirt-engine) failed "ovirt-4.1" system tests
by oVirt Jenkins 30 Aug '17

30 Aug '17

Change 81182,5 (ovirt-engine) is probably the reason behind recent system test failures in the "ovirt-4.1" 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/81182/5 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.1_change-queue-tester/919/

1 0

[JIRA] (OVIRT-1613) Re: [oVirt Jenkins] ovirt-system-tests_ansible-suite-master - Build # 7 - Still Failing!
by Ondra Machacek (oVirt JIRA) 30 Aug '17

30 Aug '17

This is a multi-part message in MIME format... ------------=_1504086936-32328-213 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1613?page=com.atlassian.jira.… ] Ondra Machacek commented on OVIRT-1613: --------------------------------------- Path which add a collecting of logs: https://gerrit.ovirt.org/#/c/81199/1 Path which fixes the job: https://gerrit.ovirt.org/#/c/81107/ > Re: [oVirt Jenkins] ovirt-system-tests_ansible-suite-master - Build # 7 - Still Failing! > ---------------------------------------------------------------------------------------- > > Key: OVIRT-1613 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1613 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nadav Goldin > Assignee: Ondra Machacek > > Adding @infra-support to open a ticket. > 1. From the console logs the error seems to be: > 02:50:07 TASK [ovirt-deploy : Import template from glance] > ****************************** > 02:50:12 An exception occurred during task execution. To see the full > traceback, use -vvv. The error was: AttributeError: 'TemplatesModule' > object has no attribute 'wait_for_import' > 02:50:12 fatal: [lago-ansible-suite-master-engine]: FAILED! => > {"changed": false, "failed": true, "msg": "'TemplatesModule' object > has no attribute 'wait_for_import'"} > 02:50:12 to retry, use: --limit > @/home/jenkins/workspace/ovirt-system-tests_ansible-suite-master/ovirt-system-tests/ansible-suite-master/engine.retry > Maybe something changed recently in the Ansible roles? > 2. There is a bug in the suite, that when the ansible deploy fails, > the logs are not collected. That is why you see no logs(the logs you > see are right after 'initialize_engine', and not after the ansible > failure). > 3. I recommend adding '-vvv' to the ansible command. Might get more > verbose logs, but easier to debug next time. > Thanks, > Nadav. > On Thu, Aug 24, 2017 at 9:49 AM, Martin Perina <mperina(a)redhat.com> wrote: > > Hi, > > > > Ansible test suite is failing for a few days, Lago says that it's failing on > > engine initialization. I've been looking on the logs, but I was unable to > > find any error. But there's something strange in wildfly logs on engine: > > > > 1. boot.log looks good, I see that WildFly 11 is starting > > 2. server.log also looks good, I see engine was deployed, but it seems to me > > that it's not complete (like WildFly was killed during engine deployment) > > 3. engine.log is completely empty - that's very strange, but it's probably > > related to my suspicion above > > > > In lago logs I can see that ovirt-engine service is being started, but no > > info about being killed/stop. > > > > Any idea what could have happened? > > > > Thanks a lot > > > > Martin > > > > > > On Thu, Aug 24, 2017 at 4:50 AM, <jenkins(a)jenkins.phx.ovirt.org> wrote: > >> > >> Project: > >> http://jenkins.ovirt.org/job/ovirt-system-tests_ansible-suite-master/ > >> Build: > >> http://jenkins.ovirt.org/job/ovirt-system-tests_ansible-suite-master/7/ > >> Build Number: 7 > >> Build Status: Still Failing > >> Triggered By: Started by timer > >> > >> ------------------------------------- > >> Changes Since Last Success: > >> ------------------------------------- > >> Changes for Build #5 > >> [Eyal Shenitzky] basic-suite-master: add cold_storage_migration test > >> > >> [Barak Korren] Adapting OST manual job to macro changes > >> > >> [Daniel Belenky] Add support for secrets and credentials to STD CI > >> > >> > >> Changes for Build #6 > >> No changes > >> > >> Changes for Build #7 > >> [Your Name] Use a long name with special chars as a network name > >> > >> [Barak Korren] Fix small bug in slave repo setup > >> > >> [Daniel Belenky] mock_runner fix empty mrmap bug > >> > >> > >> > >> > >> ----------------- > >> Failed Tests: > >> ----------------- > >> All tests passed > > > > > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > -- This message was sent by Atlassian JIRA (v1001.0.0-SNAPSHOT#100059) ------------=_1504086936-32328-213 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1613?page=com.atlassian.jira.… ]</pre> <h3>Ondra Machacek commented on OVIRT-1613:</h3> Path which add a collecting of logs: <a href="https://gerrit.ovirt.org/#/c/81199/1">https://gerrit.ovirt.org/#/c/81199/1</a> Path which fixes the job: <a href="https://gerrit.ovirt.org/#/c/81107/">https://gerrit.ovirt.org/#/c/81107/</a> <blockquote><h3>Re: [oVirt Jenkins] ovirt-system-tests_ansible-suite-master – Build # 7 – Still Failing!</h3> <pre> Key: OVIRT-1613 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1613 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nadav Goldin Assignee: Ondra Machacek</pre> Adding @infra-support to open a ticket. <ol><li>From the console logs the error seems to be:</li></ol> 02:50:07 TASK [ovirt-deploy : Import template from glance] **************************** 02:50:12 An exception occurred during task execution. To see the full traceback, use -vvv. The error was: AttributeError: ‘TemplatesModule’ object has no attribute ‘wait_for_import’ 02:50:12 fatal: [lago-ansible-suite-master-engine]: FAILED! => {"changed": false, “failed”: true, “msg”: “'TemplatesModule' object has no attribute 'wait_for_import'”} 02:50:12 to retry, use: --limit @/home/jenkins/workspace/ovirt-system-tests_ansible-suite-master/ovirt-system-tests/ansible-suite-master/engine.retry Maybe something changed recently in the Ansible roles? <ol><li>There is a bug in the suite, that when the ansible deploy fails,</li></ol> the logs are not collected. That is why you see no logs(the logs you see are right after ‘initialize_engine’, and not after the ansible failure). <ol><li>I recommend adding ‘-vvv’ to the ansible command. Might get more</li></ol> verbose logs, but easier to debug next time. Thanks, Nadav. On Thu, Aug 24, 2017 at 9:49 AM, Martin Perina <mperina(a)redhat.com> wrote: <blockquote>Hi, Ansible test suite is failing for a few days, Lago says that it's failing on engine initialization. I've been looking on the logs, but I was unable to find any error. But there's something strange in wildfly logs on engine: <ol><li>boot.log looks good, I see that WildFly 11 is starting</li> <li>server.log also looks good, I see engine was deployed, but it seems to me</li></ol> that it's not complete (like WildFly was killed during engine deployment) <ol><li>engine.log is completely empty – that's very strange, but it's probably</li></ol> related to my suspicion above In lago logs I can see that ovirt-engine service is being started, but no info about being killed/stop. Any idea what could have happened? Thanks a lot Martin On Thu, Aug 24, 2017 at 4:50 AM, <jenkins(a)jenkins.phx.ovirt.org> wrote: <blockquote><pre>Project: http://jenkins.ovirt.org/job/ovirt-system-tests_ansible-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_ansible-suite-master/7/ Build Number: 7 Build Status: Still Failing Triggered By: Started by timer</pre> <pre>------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #5 [Eyal Shenitzky] basic-suite-master: add cold_storage_migration test</pre> <pre>[Barak Korren] Adapting OST manual job to macro changes</pre> <pre>[Daniel Belenky] Add support for secrets and credentials to STD CI</pre> <pre>Changes for Build #6 No changes</pre> <pre>Changes for Build #7 [Your Name] Use a long name with special chars as a network name</pre> <pre>[Barak Korren] Fix small bug in slave repo setup</pre> <pre>[Daniel Belenky] mock_runner fix empty mrmap bug</pre> <pre>----------------- Failed Tests: ----------------- All tests passed</pre></blockquote> _____________________________________________ Infra mailing list Infra(a)ovirt.org <a href="http://lists.ovirt.org/mailman/listinfo/infra">http://lists.ovirt.org/mailman/listinfo/infra</a></blockquote></blockquote> — This message was sent by Atlassian JIRA (v1001.0.0-SNAPSHOT#100059) <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> ------------=_1504086936-32328-213--

1 0

[JIRA] (OVIRT-1614) ovirt-engine-setup-plugin-dockerc zombie
by Barak Korren (oVirt JIRA) 30 Aug '17

30 Aug '17

This is a multi-part message in MIME format... ------------=_1504086704-16972-303 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1614?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1614: ------------------------------------- Yeah, it seesm I was too strict about checking the parameters to the job. By now it was already triggered by other things, to repodata was already recreated. I suppose we just need to check in 2-3 days that the package indeed vanishes from the nightly repos and doe not reappear. > ovirt-engine-setup-plugin-dockerc zombie > ---------------------------------------- > > Key: OVIRT-1614 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1614 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Since commit 15051d04c3543fbc15b20445da2e5b9e75876e4d the subpackage > ovirt-engine-setup-plugin-dockerc is not built anymore. > Within ovirt-master-snapshot, the rpm reaper is keeping latest version of > it after having reaped the corresponding ovirt-engine build, causing > repository closure issues: > Error: Package: > ovirt-engine-setup-plugin-dockerc-4.2.0-0.0.master.20170801132431.gitcce9360.el7.centos.noarch > (ovirt-master-snapshot) > Requires: ovirt-engine-setup-plugin-ovirt-engine = > 4.2.0-0.0.master.20170801132431.gitcce9360.el7.centos > Available: > ovirt-engine-setup-plugin-ovirt-engine-4.2.0-0.0.master.20170822172135.git20a2fee.el7.centos.noarch > (ovirt-master-snapshot) > ovirt-engine-setup-plugin-ovirt-engine = > 4.2.0-0.0.master.20170822172135.git20a2fee.el7.centos > Available: > ovirt-engine-setup-plugin-ovirt-engine-4.2.0-0.0.master.20170823165744.git116f435.el7.centos.noarch > (ovirt-master-snapshot) > ovirt-engine-setup-plugin-ovirt-engine = > 4.2.0-0.0.master.20170823165744.git116f435.el7.centos > Installing: > ovirt-engine-setup-plugin-ovirt-engine-4.2.0-0.0.master.20170824144339.git6a41b6c.el7.centos.noarch > (ovirt-master-snapshot) > ovirt-engine-setup-plugin-ovirt-engine = > 4.2.0-0.0.master.20170824144339.git6a41b6c.el7.centos > Error: Package: > ovirt-engine-setup-plugin-dockerc-4.2.0-0.0.master.20170801132431.gitcce9360.el7.centos.noarch > (ovirt-master-snapshot) > Requires: ovirt-engine-setup-plugin-ovirt-engine-common = > 4.2.0-0.0.master.20170801132431.gitcce9360.el7.centos > Available: > ovirt-engine-setup-plugin-ovirt-engine-common-4.2.0-0.0.master.20170822172135.git20a2fee.el7.centos.noarch > (ovirt-master-snapshot) > ovirt-engine-setup-plugin-ovirt-engine-common = > 4.2.0-0.0.master.20170822172135.git20a2fee.el7.centos > Available: > ovirt-engine-setup-plugin-ovirt-engine-common-4.2.0-0.0.master.20170823165744.git116f435.el7.centos.noarch > (ovirt-master-snapshot) > ovirt-engine-setup-plugin-ovirt-engine-common = > 4.2.0-0.0.master.20170823165744.git116f435.el7.centos > Installing: > ovirt-engine-setup-plugin-ovirt-engine-common-4.2.0-0.0.master.20170824144339.git6a41b6c.el7.centos.noarch > (ovirt-master-snapshot) > ovirt-engine-setup-plugin-ovirt-engine-common = > 4.2.0-0.0.master.20170824144339.git6a41b6c.el7.centos > Please clean up all needed places avoiding to > get ovirt-engine-setup-plugin-dockerc published on ovirt-master-snapshot > -- > SANDRO BONAZZOLA > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D > Red Hat EMEA <https://www.redhat.com/> > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian JIRA (v1001.0.0-SNAPSHOT#100059) ------------=_1504086704-16972-303 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1614?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren commented on OVIRT-1614:</h3> Yeah, it seesm I was too strict about checking the parameters to the job. By now it was already triggered by other things, to repodata was already recreated. I suppose we just need to check in 2-3 days that the package indeed vanishes from the nightly repos and doe not reappear. <blockquote><h3>ovirt-engine-setup-plugin-dockerc zombie</h3> <pre> Key: OVIRT-1614 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1614 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra</pre> Since commit 15051d04c3543fbc15b20445da2e5b9e75876e4d the subpackage ovirt-engine-setup-plugin-dockerc is not built anymore. Within ovirt-master-snapshot, the rpm reaper is keeping latest version of it after having reaped the corresponding ovirt-engine build, causing repository closure issues: <pre>Error: Package:</pre> ovirt-engine-setup-plugin-dockerc-4.2.0-0.0.master.20170801132431.gitcce9360.el7.centos.noarch (ovirt-master-snapshot) <pre>Requires: ovirt-engine-setup-plugin-ovirt-engine =</pre> 4.2.0-0.0.master.20170801132431.gitcce9360.el7.centos <pre>Available:</pre> ovirt-engine-setup-plugin-ovirt-engine-4.2.0-0.0.master.20170822172135.git20a2fee.el7.centos.noarch (ovirt-master-snapshot) <pre>ovirt-engine-setup-plugin-ovirt-engine =</pre> 4.2.0-0.0.master.20170822172135.git20a2fee.el7.centos <pre>Available:</pre> ovirt-engine-setup-plugin-ovirt-engine-4.2.0-0.0.master.20170823165744.git116f435.el7.centos.noarch (ovirt-master-snapshot) <pre>ovirt-engine-setup-plugin-ovirt-engine =</pre> 4.2.0-0.0.master.20170823165744.git116f435.el7.centos <pre>Installing:</pre> ovirt-engine-setup-plugin-ovirt-engine-4.2.0-0.0.master.20170824144339.git6a41b6c.el7.centos.noarch (ovirt-master-snapshot) <pre>ovirt-engine-setup-plugin-ovirt-engine =</pre> 4.2.0-0.0.master.20170824144339.git6a41b6c.el7.centos Error: Package: ovirt-engine-setup-plugin-dockerc-4.2.0-0.0.master.20170801132431.gitcce9360.el7.centos.noarch (ovirt-master-snapshot) <pre>Requires: ovirt-engine-setup-plugin-ovirt-engine-common =</pre> 4.2.0-0.0.master.20170801132431.gitcce9360.el7.centos <pre>Available:</pre> ovirt-engine-setup-plugin-ovirt-engine-common-4.2.0-0.0.master.20170822172135.git20a2fee.el7.centos.noarch (ovirt-master-snapshot) <pre>ovirt-engine-setup-plugin-ovirt-engine-common =</pre> 4.2.0-0.0.master.20170822172135.git20a2fee.el7.centos <pre>Available:</pre> ovirt-engine-setup-plugin-ovirt-engine-common-4.2.0-0.0.master.20170823165744.git116f435.el7.centos.noarch (ovirt-master-snapshot) <pre>ovirt-engine-setup-plugin-ovirt-engine-common =</pre> 4.2.0-0.0.master.20170823165744.git116f435.el7.centos <pre>Installing:</pre> ovirt-engine-setup-plugin-ovirt-engine-common-4.2.0-0.0.master.20170824144339.git6a41b6c.el7.centos.noarch (ovirt-master-snapshot) <pre>ovirt-engine-setup-plugin-ovirt-engine-common =</pre> 4.2.0-0.0.master.20170824144339.git6a41b6c.el7.centos Please clean up all needed places avoiding to get ovirt-engine-setup-plugin-dockerc published on ovirt-master-snapshot — SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <<a href="https://www.redhat.com/">https://www.redhat.com/</a>> <<a href="https://red.ht/sig">https://red.ht/sig</a>> TRIED. TESTED. TRUSTED. <<a href="https://redhat.com/trusted">https://redhat.com/trusted</a>></blockquote> — This message was sent by Atlassian JIRA (v1001.0.0-SNAPSHOT#100059) <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> ------------=_1504086704-16972-303--

1 0

Openshift v2 being retired -- plans
by Marc Dequènes (Duck) 30 Aug '17

30 Aug '17

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --qGg0xr0KhPITwWGP6kDUxEDLh49FS267b Content-Type: multipart/mixed; boundary="ex7GsPnaoga3jsavcgi6sDwPIF35xSPdf"; protected-headers="v1" From: =?UTF-8?B?TWFyYyBEZXF1w6huZXMgKER1Y2sp?= <duck(a)redhat.com> To: oVirt Infra <infra(a)ovirt.org> Message-ID: <9052deac-ac64-1058-c166-940869a4f1c0(a)redhat.com> Subject: Openshift v2 being retired -- plans --ex7GsPnaoga3jsavcgi6sDwPIF35xSPdf Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable Quack, Our assets: - user 'ovirt': + wiki: I don't have access to this account, the old wiki is dead, so unless there is another wiki around I don't know I guess this is unuse= d - user 'ovirtweb': + beta: this is the website; we would need a small VM with httpd (static website) and that's about it; I've got Ansible rules I can use to build it very fast and adapting the current publishing from the builder host is already Ansible-managed and easy + status: this is the Cachet instance; I guess Evegheni knows more about it and could move this in another VM quicky too So let's prioritize this and get it over with. \_o< --ex7GsPnaoga3jsavcgi6sDwPIF35xSPdf-- --qGg0xr0KhPITwWGP6kDUxEDLh49FS267b Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEcpcqg+UmRT3yiF+BVen596wcRD8FAlmj6nAACgkQVen596wc RD+GgBAAyJY9XM6a/41jkD2HXxtuM1D5/FTyhFGo1eOMSS63ViBfYlJwslscujD7 UIIXIDK4WMhd4QAq4/GNtgjXH83S2G7H65uAjS706U34NAX1sFIWIoNNHuaSHBi1 mrTDbYkT943+IWONM3shLIE7Dgz57RF57WhRSfCcWAJ9pYpGdnj1Z1pyM1aXV2tJ fxjpzjMV02QftRjG/Us372ZO0bZiz2CXRMGL0aJvq2HFAedVnPNht9eBGnerVy6M f8YEcFy5t7aWngxMi11xIhfdMeeudxSCxMB29fNLqRHC/rxEb7taXbZvqbHuHVop g2e4mz5D9LWrZlyX58N02woKUUJ7L0u9GtixmjmLafHhSgsEODu/beWWKIRC2VyF 6g/ihgGu833vI37HG/qZMzFPW/Mq0YGqe3MOPI3ehDaZvDZVlob4/Kz0dTrmCAaH Yva3D1jP0KMvmDpU7OrVvLNG7wMDIp+0kuWrjz8Rh9qGB6GD9Mcdd8KxrUl4tDQ1 xX+Zy+1lPQ8mZcX1r5WK0DwD8Tf2y5wffGE2QkEITjC7AiIteFEJG/GUpeXR34u6 Q27KCk4nIn0tV9B7LwVACqRYDSyxxZhHhubWVLbypzxh9ceXFQ7d/Ix1onTMd4EC xMJJFzqjXP1zJH2wYp9npT2SFUYYivqkoyc0pAvKYpqKp7bcPgM= =LBq7 -----END PGP SIGNATURE----- --qGg0xr0KhPITwWGP6kDUxEDLh49FS267b--

3 8

[JIRA] (OVIRT-1621) Service Alert: PHX Ovirt-Srv 02/Total Processes is WARNING
by Evgheni Dereveanchin (oVirt JIRA) 30 Aug '17

30 Aug '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1621?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1621: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Service Alert: PHX Ovirt-Srv 02/Total Processes is WARNING > ---------------------------------------------------------- > > Key: OVIRT-1621 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1621 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > since iSCSI was enabled we see more processes on hosts using it so nagios started showing alerts. Opening ticket to reconfigure process thresholds on hypervisors, mainly ovirt-srv01 ovirt-0srv02 and ovirt-srv03 -- This message was sent by Atlassian JIRA (v1001.0.0-SNAPSHOT#100059)

1 0

[JIRA] (OVIRT-1621) Service Alert: PHX Ovirt-Srv 02/Total Processes is WARNING
by Evgheni Dereveanchin (oVirt JIRA) 30 Aug '17

30 Aug '17

This is a multi-part message in MIME format... ------------=_1504082549-23550-105 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Evgheni Dereveanchin created OVIRT-1621: ------------------------------------------- Summary: Service Alert: PHX Ovirt-Srv 02/Total Processes is WARNING Key: OVIRT-1621 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1621 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Evgheni Dereveanchin Assignee: infra since iSCSI was enabled we see more processes on hosts using it so nagios started showing alerts. Opening ticket to reconfigure process thresholds on hypervisors, mainly ovirt-srv01 ovirt-0srv02 and ovirt-srv03 -- This message was sent by Atlassian JIRA (v1001.0.0-SNAPSHOT#100059) ------------=_1504082549-23550-105 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Evgheni Dereveanchin created OVIRT-1621:</h3> <pre> Summary: Service Alert: PHX Ovirt-Srv 02/Total Processes is WARNING Key: OVIRT-1621 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1621 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Evgheni Dereveanchin Assignee: infra</pre> since iSCSI was enabled we see more processes on hosts using it so nagios started showing alerts. Opening ticket to reconfigure process thresholds on hypervisors, mainly ovirt-srv01 ovirt-0srv02 and ovirt-srv03 — This message was sent by Atlassian JIRA (v1001.0.0-SNAPSHOT#100059) <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> ------------=_1504082549-23550-105--

1 0

[vdsm][tag][ovirt-4.1] Vdsm tagged: v4.19.30
by Francesco Romani 30 Aug '17

30 Aug '17

Hi infra, we have a new Vdsm tag on branch ovirt-4.1 for oVirt 4.1.6: tag v4.19.30 Tagger: Francesco Romani <fromani(a)redhat.com> Date: Wed Aug 30 10:26:01 2017 +0200 Vdsm 4.19.30 for oVirt 4.1.6 RC 2 commit a8759be6e94e24d03559e37190d85b62dfc788f6 Bests, -- Francesco Romani Senior SW Eng., Virtualization R&D Red Hat IRC: fromani github: @fromanirh

1 0

[CQ]: 81153, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 30 Aug '17

30 Aug '17

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

1 0