[ovirt-users] Re: oVirt 4.5.2 is now generally available

[Diego Ercolani]

Here is my bugreport: https://bugzilla.redhat.com/show_bug.cgi?id=2117917
___
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/5RWLUEYPSSQJVDVITLNLHIAOH7AEZL3Q/

[ovirt-users] Q: libvirtd-tls startup failure on node (v4.4.10)

[Andrei Verovski]

Hi,

I have one problematic node, and identified a culprit why vdsmd service 
can't start:


-- The unit libvirtd-tls.socket has entered the 'failed' state with 
result 'service-start-limit-hit'.

Aug 13 15:00:45 node14.starlett.lv systemd[1]: Closed Libvirt TLS IP socket.
-- Subject: Unit libvirtd-tls.socket has finished shutting down
-- Defined-By: systemd
-- Support: https://access.redhat.com/support

Node was installed on clean CentOS Stream from oVirt Web (not oVirt node 
disk image), and was working fine until recent problem with certificates.
Can't reinstall/reconfigure node from oVirt Web since it is marked as 
non-responsive.


How to fix this?
Thanks in advance for any help.

-

[root@node14 vdsm]# cat /etc/centos-release
CentOS Stream release 8

[root@node14 vdsm]# rpm -qa | grep vdsm
vdsm-api-4.40.100.2-1.el8.noarch
vdsm-hook-openstacknet-4.40.100.2-1.el8.noarch
vdsm-client-4.40.100.2-1.el8.noarch
vdsm-network-4.40.100.2-1.el8.x86_64
vdsm-hook-vhostmd-4.40.100.2-1.el8.noarch
vdsm-4.40.100.2-1.el8.x86_64
vdsm-http-4.40.100.2-1.el8.noarch
vdsm-common-4.40.100.2-1.el8.noarch
vdsm-hook-fcoe-4.40.100.2-1.el8.noarch
vdsm-python-4.40.100.2-1.el8.noarch
vdsm-jsonrpc-4.40.100.2-1.el8.noarch
vdsm-hook-ethtool-options-4.40.100.2-1.el8.noarch
vdsm-yajsonrpc-4.40.100.2-1.el8.noarch

[root@node14 vdsm]# vdsm-tool validate-config
SUCCESS: ssl configured to true. No conflicts

[root@node14 vdsm]# systemctl --failed
  UNIT  LOAD   ACTIVE SUBDESCRIPTION
● libvirtd.service  loaded failed failed Virtualization daemon
● libvirtd-admin.socket loaded failed failed Libvirt admin socket
● libvirtd-ro.socketloaded failed failed Libvirt local read-only socket
● libvirtd-tls.socket   loaded failed failed Libvirt TLS IP socket
● libvirtd.socket   loaded failed failed Libvirt local socket
___
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/SD5JVRWUSZ7SGOV6XOBJFPCQJVASUTJE/

[ovirt-users] Re: Changing Cluster Compatibility Version from 4.6 to 4.7 issue

[Alexandr Mikhailov]

This is solution: update vm_static set time_zone='Etc/GMT' where 
vm_name='HostedEngine';
___
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/CL4MI3IJH6MPDXS3B23FQ3BDJXHHSKAG/