We have a couple OLVM instances. Completely separate with their own managers (ovirt-engine). One is lab and one is prod. I updated the lab engine from 4.5.4-1.0.31.el8 to 4.5.5-1.22.el8 and as soon as that was done and it rebooted I no longer can open VM consoles.
This was the update process followed: https://docs.oracle.com/en/virtualization/oracle-linux-virtualization-manager/admin/admin-update-engine-she-kvm.html#update-engine-she-kvm In troubleshooting I checked for the SASL db which appears to be /etc/libvirt/passwd.db # grep sasldb_path /etc/sasl2/libvirt.conf sasldb_path: /etc/libvirt/passwd.db I can verify the vdsm user and realm is in there # sasldblistusers2 -f /etc/libvirt/passwd.db vdsm@ovirt: userPassword We are using noVNC in the browser and when I click on a vm and then console it opens a new window and just has the "connecting" message. I switched to Native VNC client and downloaded the console.vv file which looks normal inside and when I try and open it with vnc viewer or remote-viewer etc. I get a window that connects, authenticates with the password found in the console.vv but then presented with a display that says "Guest has not initialized the display (yet)." Thinking perhaps I need to update the KVM hosts too I proceeded with the update document listed above but even with the hosts updated nothing has changed. If I tail /var/log/messages when opening a console connection all I see is this: Oct 14 10:33:52 olvm2 kernel: sd 6:0:0:1: Warning! Received an indication that the LUN reached a thin provisioning soft threshold. Oct 14 10:34:41 olvm2 saslpasswd2[55701]: error deleting entry from sasldb: BDB0073 DB_NOTFOUND: No matching key/data pair found Oct 14 10:34:41 olvm2 saslpasswd2[55701]: error deleting entry from sasldb: BDB0073 DB_NOTFOUND: No matching key/data pair found Oct 14 10:34:41 olvm2 saslpasswd2[55701]: error deleting entry from sasldb: BDB0073 DB_NOTFOUND: No matching key/data pair found Oct 14 10:34:41 olvm2 saslpasswd2[55701]: error deleting entry from sasldb: BDB0073 DB_NOTFOUND: No matching key/data pair found I checked the production OLVM cluster which has not been updated and has a properly functioning vnc consoles and it produces the exact same errors shown above in the logs when opening a console. So I don't think that error is the cause if the issue although likely something that needs to be fixed. If I check the VM guest log when opening a console I get nothing. tail -f /var/log/libvirt/qemu/<vm_hostname>.log Has anyone else run into this issue when updating? Any ideas on what more I can look at or troubleshoot? Thanks Malcolm _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/RQOLV7MBMIL5SPJXSPUSPIFYLW37XECR/
