The VM fails to start with error. Denis, could you take a look?
2017-08-16 22:18:31,900-0400 ERROR (vm/260cb6e0) [virt.vm]
(vmId='260cb6e0-441c-4b3f-9f05-a710ab4158f9') The vm start process
failed (vm:853)
Traceback (most recent call last):
File
On Mon, Aug 14, 2017 at 1:39 PM, Barak Korren wrote:
> On 14 August 2017 at 14:21, Yaniv Kaul wrote:
>> I was wondering if there are any examples of mocks written for code written
>> on top of the oVirt Python SDK.
>> I would assume there will be a different
On Tue, Aug 8, 2017 at 2:50 PM, Roy Golan wrote:
> This is for 4.1 https://gerrit.ovirt.org/#/c/78916/ , track that, it should
> be in.
>
Irit's work is about providing reconnect logic which was not
implemented till now.
I think that introducing ping2 won't solve the issue
Hi Sahina,
I've checked http://jenkins.ovirt.org/job/system-tests_hc-basic-suite-mas
ter/22/ and it indeed ran on a host on which nested flag was off.
I've took this host offline that will fix it's configuration.
Thanks,
On Wed, Aug 16, 2017 at 10:52 AM, Sahina Bose wrote:
Hosted-engine setup logs indicate
File
"/usr/lib/python2.7/site-packages/ovirt_hosted_engine_setup/mixins.py",
line 315, in _create_vm
'The VM is not powering up: please check VDSM logs'
RuntimeError: The VM is not powering up: please check VDSM logs
And the vdsm logs:
2017-08-15