On Tue, Oct 25, 2016 at 12:32 PM, knarra <knarra@redhat.com> wrote:

Hi All,

I am currently using ovirt master branch, having hosted-engine setup with glusterfs as the storage domain. I launched some vms and try to start them. VMs fails to start on two other hosts in the cluster and both of them go into error state. why does the hosts go into error state ?

I see the following error in the vdsm logs on why the vm start process fails.

2016-10-25 12:13:37,320 ERROR (Thread-301489) [virt.vm] vmId=`0b84e276-3375-46e8-8f5f-3e0ccee82f95`::The vm start process failed (vm:582) Traceback (most recent call last): File "/usr/share/vdsm/virt/vm.py", line 523, in _startUnderlyingVm self._run() File "/usr/share/vdsm/virt/vm.py", line 1855, in _run domxml = hooks.before_vm_start(self._buildDomainXML(), File "/usr/share/vdsm/virt/vm.py", line 1555, in _buildDomainXML self._appendDevices(domxml) File "/usr/share/vdsm/virt/vm.py", line 1502, in _appendDevices deviceXML = dev.getXML().toxml(encoding='utf-8') File "/usr/share/vdsm/virt/vmdevices/storage.py", line 422, in getXML self._validate() File "/usr/share/vdsm/virt/vmdevices/storage.py", line 491, in _validate raise ValueError("Network disk without hosts") ValueError: Network disk without hosts

Regarding this error - it seems like an issue with the vdsm build that you're using.

seeing following error in the events tab "Host hosted_engine2 will be switched to Error status for 30 minutes because it failed to run a VM."

seeing following error in the engine logs.

2016-10-25 06:44:36,912 INFO [org.ovirt.engine.core.vdsbroker.FailedToRunVmVDSCommand] (org.ovirt.thread.pool-6-thread-1) [20bafb6a] START, FailedToRunVmVDSCommand(HostName = hosted_engine2, FailedToRunVmVDSCommandParameters:{runAsync='true', hostId='fcf264de-6f03-4835-8c26-6927417d848b'}), log id: 5b369412 2016-10-25 06:44:36,920 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (org.ovirt.thread.pool-6-thread-1) [20bafb6a] START, SetVdsStatusVDSCommand(HostName = hosted_engine2, SetVdsStatusVDSCommandParameters:{runAsync='true', hostId='fcf264de-6f03-4835-8c26-6927417d848b', status='Error', nonOperationalReason='NONE', stopSpmFailur eLogged='false', maintenanceReason='null'}), log id: 3ae9ae50 2016-10-25 06:44:36,927 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (org.ovirt.thread.pool-6-thread-1) [20bafb6a] FINISH, SetVdsStatusVDSCommand, log id: 3ae9ae50 2016-10-25 06:44:36,934 ERROR [org.ovirt.engine.core.dal.dbb roker.auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-6-thread-1) [20bafb6a] Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: Host hosted_engine2 will be switched to Error status for 30 minutes because it failed to run a VM.

Not sure if this behaviour was introduced recently or not. Infra/Virt team could help?

2016-10-25 06:44:36,934 INFO [org.ovirt.engine.core.vdsbroker.VdsManager] (org.ovirt.thread.pool-6-thread-1) [20bafb6a] Vds 'hosted_engine2' moved to Error mode after 3 att empts. Time: Tue Oct 25 06:44:36 UTC 2016 2016-10-25 06:44:36,934 INFO [org.ovirt.engine.core.vdsbroker.FailedToRunVmVDSCommand] (org.ovirt.thread.pool-6-thread-1) [20bafb6a] FINISH, FailedToRunVmVDSCommand, log id : 5b369412

Thanks

kasturi

_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users