job ovirt-system-tests_manual
by Shlomo Ben David
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
6 years, 5 months
Fwd: [CQ]: 83325, 1 (ovirt-engine) failed "ovirt-4.1" system tests
by Dafna Ron
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">
<p>Hi, <br>
</p>
<p>We had a failure on ovirt-4.1 system tests. <br>
</p>
<p>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></p>
<p>which seems, was already fixed. <br>
</p>
<p>Thanks, <br>
</p>
<p>Dafna</p>
<p><br>
</p>
<div class="moz-forward-container"><br>
<br>
-------- 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>
<br>
<br>
<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--
6 years, 5 months
[ OST Failure Report ] [ oVirt master ] [ 29-10-2017 ] [ 098_ovirt_provider_ovn.test_ovn_provider_rest ]
by Shlomo Ben David
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/artifa...
(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
6 years, 5 months
[oVirt 4.2 Localization Question #8] "Welcome to"
by Yuko Katabami
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
6 years, 6 months
[oVirt 4.2 Localization Question #7]
by Yuko Katabami
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
6 years, 6 months
[ OST Failure Report ] [ oVirt Master ] [ Oct 27 ] [ 002_bootstrap.verify_add_hosts ]
by Dafna Ron
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">
<p>Hi, <br>
</p>
<p>we have a failed test that is caused by failing to start vdsm on
host-0. <br>
</p>
<p><br>
</p>
<p><b><span style="font-weight:normal;">
<p dir="ltr"
style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><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></p>
<p dir="ltr"
style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><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></p>
</span></b><b><span style="font-weight:normal;">
<p dir="ltr"
style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><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><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;"></span><a
class="moz-txt-link-freetext"
href="https://gerrit.ovirt.org/#/c/83186/3">https://gerrit.ovirt.org/#/c/83186/3</a></p>
</span></b></p>
<p><b><span style="font-weight:normal;">
<p><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:</span><span
style="font-weight:normal;">
<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></p>
</span></b></p>
<p><b><span style="font-weight:normal;">
<p dir="ltr"
style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><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></p>
</span></b><b><span style="font-weight:normal;"><br>
<p dir="ltr"
style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><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></p>
<p dir="ltr"
style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><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></span></p>
<br>
Error in host deploy log: <br>
</span></b></p>
<p><b><span style="font-weight:normal;">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:<br>
A dependency job for vdsmd.service failed. See 'journalctl
-xe' for details.<br>
<br>
2017-10-27 11:52:22,516-0400 DEBUG otopi.context
context._executeMethod:143 method exception<br>
Traceback (most recent call last):<br>
File "/tmp/ovirt-GJGz7NSZHZ/pythonlib/otopi/context.py",
line 133, in _executeMethod<br>
method['method']()<br>
File
"/tmp/ovirt-GJGz7NSZHZ/otopi-plugins/ovirt-host-deploy/vdsm/packages.py",
line 220, in _start<br>
self.services.state('vdsmd', True)<br>
File
"/tmp/ovirt-GJGz7NSZHZ/otopi-plugins/otopi/services/systemd.py",
line 141, in state<br>
service=name,<br>
RuntimeError: Failed to start service 'vdsmd'<br>
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'<br>
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<br>
)<br>
</span></b></p>
<p><b><br>
</b></p>
<p><b><span style="font-weight:normal;">Actual error from messages
log: <br>
</span></b></p>
<p><b><span style="font-weight:normal;"><br>
</span></b></p>
<p><b><span style="font-weight:normal;">Oct 27 11:52:24
lago-basic-suite-master-host-0 systemd: Started Auxiliary vdsm
service for running helper functions as root.<br>
Oct 27 11:52:24 lago-basic-suite-master-host-0 systemd:
Starting Auxiliary vdsm service for running helper functions
as root...<br>
Oct 27 11:52:24 lago-basic-suite-master-host-0 python2:
detected unhandled Python exception in
'/usr/share/vdsm/supervdsmd'<br>
Oct 27 11:52:24 lago-basic-suite-master-host-0 abrt-server:
Not saving repeating crash in '/usr/share/vdsm/supervdsmd'<br>
Oct 27 11:52:25 lago-basic-suite-master-host-0 daemonAdapter:
Traceback (most recent call last):<br>
Oct 27 11:52:25 lago-basic-suite-master-host-0 daemonAdapter:
File "/usr/share/vdsm/supervdsmd", line 22, in <module><br>
Oct 27 11:52:25 lago-basic-suite-master-host-0 daemonAdapter:
from vdsm import supervdsm_server<br>
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><br>
Oct 27 11:52:25 lago-basic-suite-master-host-0 daemonAdapter:
from vdsm.storage import fuser<br>
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><br>
Oct 27 11:52:25 lago-basic-suite-master-host-0 daemonAdapter:
from vdsm.storage import misc<br>
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><br>
Oct 27 11:52:25 lago-basic-suite-master-host-0 daemonAdapter:
from vdsm import commands<br>
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><br>
Oct 27 11:52:25 lago-basic-suite-master-host-0 daemonAdapter:
from .utils import terminating<br>
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><br>
Oct 27 11:52:25 lago-basic-suite-master-host-0 daemonAdapter:
from vdsm.common.compat import pickle<br>
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><br>
Oct 27 11:52:25 lago-basic-suite-master-host-0 daemonAdapter:
import subprocess32 as subprocess<br>
Oct 27 11:52:25 lago-basic-suite-master-host-0 daemonAdapter:
ImportError: No module named subprocess32<br>
Oct 27 11:52:25 lago-basic-suite-master-host-0 systemd:
supervdsmd.service: main process exited, code=exited,
status=1/FAILURE<br>
Oct 27 11:52:25 lago-basic-suite-master-host-0 systemd: Unit
supervdsmd.service entered failed state.<br>
Oct 27 11:52:25 lago-basic-suite-master-host-0 systemd:
supervdsmd.service failed.<br>
Oct 27 11:52:25 lago-basic-suite-master-host-0 systemd:
supervdsmd.service holdoff time over, scheduling restart.<br>
Oct 27 11:52:25 lago-basic-suite-master-host-0 systemd: start
request repeated too quickly for supervdsmd.service<br>
Oct 27 11:52:25 lago-basic-suite-master-host-0 systemd: Failed
to start Auxiliary vdsm service for running helper functions
as root.<br>
Oct 27 11:52:25 lago-basic-suite-master-host-0 systemd: Unit
supervdsmd.service entered failed state.<br>
Oct 27 11:52:25 lago-basic-suite-master-host-0 systemd:
supervdsmd.service failed.<br>
<br>
<p dir="ltr"
style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><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></span></p>
<br>
</span></b></p>
<p><b><br>
</b></p>
</body>
</html>
--------------5D6A91148DA6085EC6E1019D--
6 years, 6 months
[oVirt 4.2 Localization Question #5] VM SLA Policy command does not change anything.
by Yuko Katabami
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
6 years, 6 months
