- Devel - oVirt List Archives

Fwd: Jenkins OST fails
by Barak Korren 30 Oct '17

30 Oct '17

Forwarding to devel as this question seems to have nothing to do with OST mechanics and is probably better answered be people knowledgeable about the engine build process and DB configuration. ---------- Forwarded message ---------- From: Maor Lipchuk <mlipchuk(a)redhat.com> Date: 30 October 2017 at 22:00 Subject: Jenkins OST fails To: infra <infra(a)ovirt.org> Hi, I've ran the OST on few patches which I wanted to merge and I got an error with the following message (see [1]): [ ERROR ] schema.sh: Please fix numbering to interval 04020701 to 04020710 and run the upgrade script. [ ERROR ] Failed to execute stage 'Misc configuration': Engine schema refresh failed\n[ INFO ] Rolling back database schema My patch clearly indicates the upgrade script is 04020710 (see [2]). I wonder if it is somehow related to the reverted patch (see [3]) which removed the upgrade script packaging/dbscripts/upgrade/04_02_0710_ <https://gerrit.ovirt.org/#/c/83228/2/packaging/dbscripts/upgrade/04_02_0710…>nullify... [1] http://jenkins.ovirt.org/job/ovirt-system-tests_manual/1470/testReport/juni… [2] https://gerrit.ovirt.org/#/c/82251/26/packaging/dbscripts/upgrade/04_02_071… [3] https://gerrit.ovirt.org/#/c/83228/ Regards, Maor _______________________________________________ Infra mailing list Infra(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/infra -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted

1 0

job ovirt-system-tests_manual
by Shlomo Ben David 30 Oct '17

30 Oct '17

Hi All, The 'ovirt-system-tests_manual' job currently run with no limits on how many builds to keep. We want to limit the kept builds for 14 days only. If you are using the job and you need to keep your build(s) more than 14 days, please let us know. Best Regards, Shlomi Ben-David | Software Engineer | Red Hat ISRAEL RHCSA | RHCE | RHCVA IRC: shlomibendavid (on #rhev-integ, #rhev-dev, #rhev-ci) OPEN SOURCE - 1 4 011 && 011 4 1

1 0

Rebasing master Fedora to 27?
by Sandro Bonazzola 30 Oct '17

30 Oct '17

Hi, there's a bit of a mess in Jenkins around master on Fedora with some packages built only for version 25 and other only for 26. With Fedora 27 going to be released on November 7th and being it already supported by Jenkins CI, I would suggest to mass migrate master to Fedora 27. Thoughts? -- 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> <http://www.teraplan.it/redhat-osd-2017/>

2 1

Fwd: [CQ]: 83325, 1 (ovirt-engine) failed "ovirt-4.1" system tests
by Dafna Ron 30 Oct '17

30 Oct '17

This is a multi-part message in MIME format. --------------51E2FFF96B6D869ED1298324 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Hi, We had a failure on ovirt-4.1 system tests. the failure is actually because of build artifacts job: http://jenkins.ovirt.org/job/ovirt-engine_4.1_build-artifacts-el7-x86_64/ which seems, was already fixed. Thanks, Dafna -------- Forwarded Message -------- Subject: [CQ]: 83325,1 (ovirt-engine) failed "ovirt-4.1" system tests Date: Mon, 30 Oct 2017 09:44:32 +0000 (UTC) From: oVirt Jenkins <jenkins(a)ovirt.org> To: infra(a)ovirt.org Change 83325,1 (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/83325/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.1_change-queue-tester/1219/ _______________________________________________ Infra mailing list Infra(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/infra --------------51E2FFF96B6D869ED1298324 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: 7bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=windows-1252"> </head> <body text="#000000" bgcolor="#FFFFFF"> Hi, We had a failure on ovirt-4.1 system tests. the failure is actually because of build artifacts job: <a class="moz-txt-link-freetext" href="http://jenkins.ovirt.org/job/ovirt-engine_4.1_build-artifacts-el7-x86_64/">http://jenkins.ovirt.org/job/ovirt-engine_4.1_build-artifacts-el7-x86_64/</a> which seems, was already fixed. Thanks, Dafna <div class="moz-forward-container"> -------- Forwarded Message -------- <table class="moz-email-headers-table" border="0" cellspacing="0" cellpadding="0"> <tbody> <tr> <th valign="BASELINE" align="RIGHT" nowrap="nowrap">Subject: </th> <td>[CQ]: 83325,1 (ovirt-engine) failed "ovirt-4.1" system tests</td> </tr> <tr> <th valign="BASELINE" align="RIGHT" nowrap="nowrap">Date: </th> <td>Mon, 30 Oct 2017 09:44:32 +0000 (UTC)</td> </tr> <tr> <th valign="BASELINE" align="RIGHT" nowrap="nowrap">From: </th> <td>oVirt Jenkins <a class="moz-txt-link-rfc2396E" href="mailto:jenkins@ovirt.org"><jenkins(a)ovirt.org></a></td> </tr> <tr> <th valign="BASELINE" align="RIGHT" nowrap="nowrap">To: </th> <td><a class="moz-txt-link-abbreviated" href="mailto:infra@ovirt.org">infra(a)ovirt.org</a></td> </tr> </tbody> </table> <pre>Change 83325,1 (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: <a class="moz-txt-link-freetext" href="https://gerrit.ovirt.org/#/c/83325/1">https://gerrit.ovirt.org/#/c/83325/1</a> For failed test results see: <a class="moz-txt-link-freetext" href="http://jenkins.ovirt.org/job/ovirt-4.1_change-queue-tester/1219/">http://jenkins.ovirt.org/job/ovirt-4.1_change-queue-tester/1219/</a> _______________________________________________ Infra mailing list <a class="moz-txt-link-abbreviated" href="mailto:Infra@ovirt.org">Infra(a)ovirt.org</a> <a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/infra">http://lists.ovirt.org/mailman/listinfo/infra</a> </pre> </div> </body> </html> --------------51E2FFF96B6D869ED1298324--

2 1

gitreview support
by Roy Golan 30 Oct '17

30 Oct '17

I sent a patch [1] to add gitreview file for zero git review setup. gitreview is a git command to for submitting branches for gerrit and can help to ease submitting and reviewing. Checkout the Usage page: https://docs.openstack.org/infra/git-review/usage.html [1] https://gerrit.ovirt.org/83335

3 4

[ OST Failure Report ] [ oVirt master ] [ 29-10-2017 ] [ 098_ovirt_provider_ovn.test_ovn_provider_rest ]
by Shlomo Ben David 29 Oct '17

29 Oct '17

Hi, Link to suspected patches: https://gerrit.ovirt.org/#/c/83158/ Link to Job: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3525/console Link to all logs: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3525/artifact… (Relevant) error snippet from the log: <error> File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 129, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 59, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 78, in wrapper prefix.virt_env.engine_vm().get_api(api_ver=4), *args, **kwargs File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 59, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/home/jenkins/workspace/ovirt-master_change-queue-tester/ovirt-system-tests/basic-suite-master/test-scenarios/098_ovirt_provider_ovn.py", line 441, in test_ovn_provider_rest _remove_iface_from_vm(api, VM0_NAME, IFACE_NAME) File "/home/jenkins/workspace/ovirt-master_change-queue-tester/ovirt-system-tests/basic-suite-master/test-scenarios/098_ovirt_provider_ovn.py", line 400, in _remove_iface_from_vm nic_service.remove() File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 27808, in remove self._internal_remove(headers, query, wait) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 262, in _internal_remove return future.wait() if wait else future File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 53, in wait return self._code(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 259, in callback self._check_fault(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 123, in _check_fault self._raise_error(response, body) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 109, in _raise_error raise error 'Fault reason is "Operation Failed". Fault detail is "[Cannot remove Interface. The VM Network Interface is plugged to a running VM.]". </error> Best Regards, Shlomi Ben-David | Software Engineer | Red Hat ISRAEL RHCSA | RHCE | RHCVA IRC: shlomibendavid (on #rhev-integ, #rhev-dev, #rhev-ci) OPEN SOURCE - 1 4 011 && 011 4 1

1 0

[oVirt 4.2 Localization Question #8] "Welcome to"
by Yuko Katabami 28 Oct '17

28 Oct '17

Sorry, #7 was not my last question. Here is one additional post. *File: *messages *Resource ID: *obrand.welcome.welcome.text *String: *Welcome to *Question:* I am wondering this string is going to be followed by the product name (i.e. Welcome to oVirt Open Virtualization Manager). If so, could you please include a variable representing the product name (i.e. Welcome to {0}), so that we are able to change the order of the word required by the language we translated into. In Japanese, order will have to be reversed (i.e. oVirt Open Virtualization Manager にようこそ). Without having the product name included in the string, we have no control and the translation shown on the screen will not make sense to users. Kind regards, Yuko

2 2

[oVirt 4.2 Localization Question #7]
by Yuko Katabami 27 Oct '17

27 Oct '17

This is my last question for the current translation cycle. *File: *CommonApplicationConstants *Resource ID: *connectAutomaticallyMessage *String: *If ovirt-engine has the user's password connect automatically to the first running VM if there is one on User Portal login *Question:* Should "User Portal" be replaced by "VM Portal" Should "connect" be "it connects"? In "if there is one", what is "one" referring? VM or password? Kind regards, Yuko

2 4

[ OST Failure Report ] [ oVirt Master ] [ Oct 27 ] [ 002_bootstrap.verify_add_hosts ]
by Dafna Ron 27 Oct '17

27 Oct '17

This is a multi-part message in MIME format. --------------5D6A91148DA6085EC6E1019D Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Hi, we have a failed test that is caused by failing to start vdsm on host-0. ** *Link to suspected patches: * * patch reported as reason: https://gerrit.ovirt.org/#/c/83275/ ** patch reported as a more likely reason: https://gerrit.ovirt.org/#/c/83186/3 * ** *Link to Job:http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3505* ** ** *Link to all logs: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3505/artifact* *** (Relevant) error snippet from the log: <error> Error in host deploy log: * *2017-10-27 11:52:22,516-0400 DEBUG otopi.plugins.otopi.services.systemd plugin.execute:926 execute-output: ('/usr/bin/systemctl', 'start', 'vdsmd.service') stderr: A dependency job for vdsmd.service failed. See 'journalctl -xe' for details. 2017-10-27 11:52:22,516-0400 DEBUG otopi.context context._executeMethod:143 method exception Traceback (most recent call last): File "/tmp/ovirt-GJGz7NSZHZ/pythonlib/otopi/context.py", line 133, in _executeMethod method['method']() File "/tmp/ovirt-GJGz7NSZHZ/otopi-plugins/ovirt-host-deploy/vdsm/packages.py", line 220, in _start self.services.state('vdsmd', True) File "/tmp/ovirt-GJGz7NSZHZ/otopi-plugins/otopi/services/systemd.py", line 141, in state service=name, RuntimeError: Failed to start service 'vdsmd' 2017-10-27 11:52:22,519-0400 ERROR otopi.context context._executeMethod:152 Failed to execute stage 'Closing up': Failed to start service 'vdsmd' 2017-10-27 11:52:22,520-0400 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:204 DIALOG:SEND **%EventEnd STAGE closeup METHOD otopi.plugins.ovirt_host_deploy.vdsm.packages.Plugin._start (odeploycons.packages.vdsm.started ) * * * *Actual error from messages log: * * * *Oct 27 11:52:24 lago-basic-suite-master-host-0 systemd: Started Auxiliary vdsm service for running helper functions as root. Oct 27 11:52:24 lago-basic-suite-master-host-0 systemd: Starting Auxiliary vdsm service for running helper functions as root... Oct 27 11:52:24 lago-basic-suite-master-host-0 python2: detected unhandled Python exception in '/usr/share/vdsm/supervdsmd' Oct 27 11:52:24 lago-basic-suite-master-host-0 abrt-server: Not saving repeating crash in '/usr/share/vdsm/supervdsmd' Oct 27 11:52:25 lago-basic-suite-master-host-0 daemonAdapter: Traceback (most recent call last): Oct 27 11:52:25 lago-basic-suite-master-host-0 daemonAdapter: File "/usr/share/vdsm/supervdsmd", line 22, in <module> Oct 27 11:52:25 lago-basic-suite-master-host-0 daemonAdapter: from vdsm import supervdsm_server Oct 27 11:52:25 lago-basic-suite-master-host-0 daemonAdapter: File "/usr/lib/python2.7/site-packages/vdsm/supervdsm_server.py", line 50, in <module> Oct 27 11:52:25 lago-basic-suite-master-host-0 daemonAdapter: from vdsm.storage import fuser Oct 27 11:52:25 lago-basic-suite-master-host-0 daemonAdapter: File "/usr/lib/python2.7/site-packages/vdsm/storage/fuser.py", line 25, in <module> Oct 27 11:52:25 lago-basic-suite-master-host-0 daemonAdapter: from vdsm.storage import misc Oct 27 11:52:25 lago-basic-suite-master-host-0 daemonAdapter: File "/usr/lib/python2.7/site-packages/vdsm/storage/misc.py", line 50, in <module> Oct 27 11:52:25 lago-basic-suite-master-host-0 daemonAdapter: from vdsm import commands Oct 27 11:52:25 lago-basic-suite-master-host-0 daemonAdapter: File "/usr/lib/python2.7/site-packages/vdsm/commands.py", line 33, in <module> Oct 27 11:52:25 lago-basic-suite-master-host-0 daemonAdapter: from .utils import terminating Oct 27 11:52:25 lago-basic-suite-master-host-0 daemonAdapter: File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 47, in <module> Oct 27 11:52:25 lago-basic-suite-master-host-0 daemonAdapter: from vdsm.common.compat import pickle Oct 27 11:52:25 lago-basic-suite-master-host-0 daemonAdapter: File "/usr/lib/python2.7/site-packages/vdsm/common/compat.py", line 86, in <module> Oct 27 11:52:25 lago-basic-suite-master-host-0 daemonAdapter: import subprocess32 as subprocess Oct 27 11:52:25 lago-basic-suite-master-host-0 daemonAdapter: ImportError: No module named subprocess32 Oct 27 11:52:25 lago-basic-suite-master-host-0 systemd: supervdsmd.service: main process exited, code=exited, status=1/FAILURE Oct 27 11:52:25 lago-basic-suite-master-host-0 systemd: Unit supervdsmd.service entered failed state. Oct 27 11:52:25 lago-basic-suite-master-host-0 systemd: supervdsmd.service failed. Oct 27 11:52:25 lago-basic-suite-master-host-0 systemd: supervdsmd.service holdoff time over, scheduling restart. Oct 27 11:52:25 lago-basic-suite-master-host-0 systemd: start request repeated too quickly for supervdsmd.service Oct 27 11:52:25 lago-basic-suite-master-host-0 systemd: Failed to start Auxiliary vdsm service for running helper functions as root. Oct 27 11:52:25 lago-basic-suite-master-host-0 systemd: Unit supervdsmd.service entered failed state. Oct 27 11:52:25 lago-basic-suite-master-host-0 systemd: supervdsmd.service failed. * *</error>* * * * * --------------5D6A91148DA6085EC6E1019D Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> Hi, we have a failed test that is caused by failing to start vdsm on host-0. <span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">Link to suspected patches: <span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">patch reported as reason: <a class="moz-txt-link-freetext" href="https://gerrit.ovirt.org/#/c/83275/">https://gerrit.ovirt.org/#/c/83275/</a> <span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">patch reported as a more likely reason: <span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;"><a class="moz-txt-link-freetext" href="https://gerrit.ovirt.org/#/c/83186/3">https://gerrit.ovirt.org/#/c/83186/3</a> <span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">Link to Job: <a class="moz-txt-link-freetext" href="http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3505">http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3505</a> <span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">Link to all logs: <a class="moz-txt-link-freetext" href="http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3505/artifact">http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3505/artifact</a> <span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;">(Relevant) error snippet from the log: <span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;"><error> Error in host deploy log: 2017-10-27 11:52:22,516-0400 DEBUG otopi.plugins.otopi.services.systemd plugin.execute:926 execute-output: ('/usr/bin/systemctl', 'start', 'vdsmd.service') stderr: A dependency job for vdsmd.service failed. See 'journalctl -xe' for details. 2017-10-27 11:52:22,516-0400 DEBUG otopi.context context._executeMethod:143 method exception Traceback (most recent call last): File "/tmp/ovirt-GJGz7NSZHZ/pythonlib/otopi/context.py", line 133, in _executeMethod method['method']() File "/tmp/ovirt-GJGz7NSZHZ/otopi-plugins/ovirt-host-deploy/vdsm/packages.py", line 220, in _start self.services.state('vdsmd', True) File "/tmp/ovirt-GJGz7NSZHZ/otopi-plugins/otopi/services/systemd.py", line 141, in state service=name, RuntimeError: Failed to start service 'vdsmd' 2017-10-27 11:52:22,519-0400 ERROR otopi.context context._executeMethod:152 Failed to execute stage 'Closing up': Failed to start service 'vdsmd' 2017-10-27 11:52:22,520-0400 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:204 DIALOG:SEND **%EventEnd STAGE closeup METHOD otopi.plugins.ovirt_host_deploy.vdsm.packages.Plugin._start (odeploycons.packages.vdsm.started ) Actual error from messages log: Oct 27 11:52:24 lago-basic-suite-master-host-0 systemd: Started Auxiliary vdsm service for running helper functions as root. Oct 27 11:52:24 lago-basic-suite-master-host-0 systemd: Starting Auxiliary vdsm service for running helper functions as root... Oct 27 11:52:24 lago-basic-suite-master-host-0 python2: detected unhandled Python exception in '/usr/share/vdsm/supervdsmd' Oct 27 11:52:24 lago-basic-suite-master-host-0 abrt-server: Not saving repeating crash in '/usr/share/vdsm/supervdsmd' Oct 27 11:52:25 lago-basic-suite-master-host-0 daemonAdapter: Traceback (most recent call last): Oct 27 11:52:25 lago-basic-suite-master-host-0 daemonAdapter: File "/usr/share/vdsm/supervdsmd", line 22, in <module> Oct 27 11:52:25 lago-basic-suite-master-host-0 daemonAdapter: from vdsm import supervdsm_server Oct 27 11:52:25 lago-basic-suite-master-host-0 daemonAdapter: File "/usr/lib/python2.7/site-packages/vdsm/supervdsm_server.py", line 50, in <module> Oct 27 11:52:25 lago-basic-suite-master-host-0 daemonAdapter: from vdsm.storage import fuser Oct 27 11:52:25 lago-basic-suite-master-host-0 daemonAdapter: File "/usr/lib/python2.7/site-packages/vdsm/storage/fuser.py", line 25, in <module> Oct 27 11:52:25 lago-basic-suite-master-host-0 daemonAdapter: from vdsm.storage import misc Oct 27 11:52:25 lago-basic-suite-master-host-0 daemonAdapter: File "/usr/lib/python2.7/site-packages/vdsm/storage/misc.py", line 50, in <module> Oct 27 11:52:25 lago-basic-suite-master-host-0 daemonAdapter: from vdsm import commands Oct 27 11:52:25 lago-basic-suite-master-host-0 daemonAdapter: File "/usr/lib/python2.7/site-packages/vdsm/commands.py", line 33, in <module> Oct 27 11:52:25 lago-basic-suite-master-host-0 daemonAdapter: from .utils import terminating Oct 27 11:52:25 lago-basic-suite-master-host-0 daemonAdapter: File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 47, in <module> Oct 27 11:52:25 lago-basic-suite-master-host-0 daemonAdapter: from vdsm.common.compat import pickle Oct 27 11:52:25 lago-basic-suite-master-host-0 daemonAdapter: File "/usr/lib/python2.7/site-packages/vdsm/common/compat.py", line 86, in <module> Oct 27 11:52:25 lago-basic-suite-master-host-0 daemonAdapter: import subprocess32 as subprocess Oct 27 11:52:25 lago-basic-suite-master-host-0 daemonAdapter: ImportError: No module named subprocess32 Oct 27 11:52:25 lago-basic-suite-master-host-0 systemd: supervdsmd.service: main process exited, code=exited, status=1/FAILURE Oct 27 11:52:25 lago-basic-suite-master-host-0 systemd: Unit supervdsmd.service entered failed state. Oct 27 11:52:25 lago-basic-suite-master-host-0 systemd: supervdsmd.service failed. Oct 27 11:52:25 lago-basic-suite-master-host-0 systemd: supervdsmd.service holdoff time over, scheduling restart. Oct 27 11:52:25 lago-basic-suite-master-host-0 systemd: start request repeated too quickly for supervdsmd.service Oct 27 11:52:25 lago-basic-suite-master-host-0 systemd: Failed to start Auxiliary vdsm service for running helper functions as root. Oct 27 11:52:25 lago-basic-suite-master-host-0 systemd: Unit supervdsmd.service entered failed state. Oct 27 11:52:25 lago-basic-suite-master-host-0 systemd: supervdsmd.service failed. <span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;"></error> </body> </html> --------------5D6A91148DA6085EC6E1019D--

1 0

[oVirt 4.2 Localization Question #5] VM SLA Policy command does not change anything.
by Yuko Katabami 27 Oct '17

27 Oct '17

Hello oVirt developers. I have another question. *File: *AppErrors *Resource ID: *VM_SLA_POLICY_UNCHANGED *String: *VM SLA Policy command does not change anything. *Question:* Could someone explain to me what this actually means? Does it mean "the operation (user performed) to update VM's SLA policy did not change anything" Thanks in advance. Yuko

3 4