Hi,

I'm facing a strange issue with ovirt host.

I can't list nodes status running virsh, vdsdm seems bad. 

I can't even delete the hosted engine, nor ping it, but I can still access my infra vm inside it😉

My outputs :
[root@moe ~]# /usr/sbin/ovirt-hosted-engine-cleanup
 This will de-configure the host to run ovirt-hosted-engine-setup from scratch.
Caution, this operation should be used with care.
Are you sure you want to proceed? [y/n]
y
  -=== Destroy hosted-engine VM ===-
You must run deploy first
setlocale: No such file or directory
error: failed to connect to the hypervisor
error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory
  -=== Stop HA services ===-
  -=== Shutdown sanlock ===-
shutdown force 1 wait 0
shutdown done -111
  -=== Disconnecting the hosted-engine storage domain ===-
You must run deploy first
  -=== De-configure VDSM networks ===-
ovirtmgmt
ovirtmgmt
 A previously configured management bridge has been found on the system, this will try to de-configure it. Under certain circumstances you can loose network connection.
Caution, this operation should be used with care.
Are you sure you want to proceed? [y/n]
y
  -=== Stop other services ===-
  -=== De-configure external daemons ===-
  -=== Removing configuration files ===-
? /etc/init/libvirtd.conf already missing
? /etc/libvirt/nwfilter/vdsm-no-mac-spoofing.xml already missing
? /etc/ovirt-hosted-engine/answers.conf already missing
? /etc/ovirt-hosted-engine/hosted-engine.conf already missing
? /etc/vdsm/vdsm.conf already missing
? /etc/pki/vdsm/*/*.pem already missing
? /etc/pki/CA/cacert.pem already missing
? /etc/pki/libvirt/*.pem already missing
? /etc/pki/libvirt/private/*.pem already missing
? /etc/pki/ovirt-vmconsole/*.pem already missing
? /var/cache/libvirt/* already missing
? /var/run/ovirt-hosted-engine-ha/* already missing
[root@moe ~]# ping 192.168.33.143
PING 192.168.33.143 (192.168.33.143) 56(84) bytes of data.
64 bytes from 192.168.33.143: icmp_seq=1 ttl=64 time=0.132 ms
64 bytes from 192.168.33.143: icmp_seq=2 ttl=64 time=0.082 ms
64 bytes from 192.168.33.143: icmp_seq=3 ttl=64 time=0.072 ms
64 bytes from 192.168.33.143: icmp_seq=4 ttl=64 time=0.083 ms
64 bytes from 192.168.33.143: icmp_seq=5 ttl=64 time=0.075 ms
64 bytes from 192.168.33.143: icmp_seq=6 ttl=64 time=0.082 ms
^C
--- 192.168.33.143 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 4999ms
rtt min/avg/max/mdev = 0.072/0.087/0.132/0.022 ms
[root@moe ~]# nodectl check
Status: WARN
Bootloader ... OK
  Layer boot entries ... OK
  Valid boot entries ... OK
Mount points ... OK
  Separate /var ... OK
  Discard is used ... OK
Basic storage ... OK
  Initialized VG ... OK
  Initialized Thin Pool ... OK
  Initialized LVs ... OK
Thin storage ... OK
  Checking available space in thinpool ... OK
  Checking thinpool auto-extend ... OK
vdsmd ... BAD
[root@moe ~]# virsh -r list
setlocale: No such file or directory
error: failed to connect to the hypervisor
error: Failed to connect socket to '/var/run/libvirt/libvirt-sock-ro': No such file or directory
[root@moe ~]#

Have you guys ever faced this issue?
How can I access VM inside my virtual data center while the VM Manager is broken?
Any solution to work around this please?

Regards,
Eugène NG
--
LesCDN
engontang@lescdn.com
------------------------------------------------------------
Aux hommes il faut un chef, et au chef il faut des hommes!
L'habit ne fait pas le moine, mais lorsqu'on te voit on te juge!