Actually, this one wasn't stupid. The host was running version 4.3.3 and was upgraded to 4.3.4 after yum update. And this solved the issue ... thanks a lot! Looing at the bugtracker (https://bugzilla.redhat.com/ buglist.cgi?classification=oVirt&f1=flagtypes.name&o1= substring&query_format=advanced&target_milestone=ovirt-4.3.4&v1=blocker) I don't see a suitable bug for this. perhaps vdsmd reconfiguration + yum upgrade + host reboot did the trick. Thank you very much for spending a time on this! Regards, Artem On Tue, Jun 11, 2019 at 5:19 PM Shani Leviim <sleviim(a)redhat.com&gt; wrote: > A stupid one: did you try to yum update? > > > > *Regards,* > > *Shani Leviim* > > > On Tue, Jun 11, 2019 at 5:11 PM Artem Tambovskiy < > artem.tambovskiy(a)gmail.com&gt; wrote: > >> >> Just tried this: >> >> [root@ovirt1 vdsm]# vdsm-tool configure --force >> >> Checking configuration status... >> >> abrt is already configured for vdsm >> Managed volume database is already configured >> lvm is configured for vdsm >> libvirt is already configured for vdsm >> SUCCESS: ssl configured to true. No conflicts >> Current revision of multipath.conf detected, preserving >> >> Running configure... >> Reconfiguration of abrt is done. >> Reconfiguration of passwd is done. >> Reconfiguration of libvirt is done. >> >> Done configuring modules to VDSM. >> >> And tried to restart vdsmd - it failed again. >> >> [root@ovirt1 vdsm]# journalctl -xe >> Jun 11 17:07:58 ovirt1.telia.ru systemd[1]: ovirt-ha-broker.service >> failed. >> Jun 11 17:07:58 ovirt1.telia.ru systemd[1]: ovirt-ha-broker.service >> holdoff time over, scheduling restart. >> Jun 11 17:07:58 ovirt1.telia.ru systemd[1]: Cannot add dependency job >> for unit lvm2-lvmetad.socket, ignoring: Unit is masked. >> Jun 11 17:07:58 ovirt1.telia.ru systemd[1]: Stopped oVirt Hosted Engine >> High Availability Communications Broker. >> -- Subject: Unit ovirt-ha-broker.service has finished shutting down >> -- Defined-By: systemd >> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel >> -- >> -- Unit ovirt-ha-broker.service has finished shutting down. >> Jun 11 17:07:58 ovirt1.telia.ru systemd[1]: Started oVirt Hosted Engine >> High Availability Communications Broker. >> -- Subject: Unit ovirt-ha-broker.service has finished start-up >> -- Defined-By: systemd >> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel >> -- >> -- Unit ovirt-ha-broker.service has finished starting up. >> -- >> -- The start-up result is done. >> Jun 11 17:07:59 ovirt1.telia.ru systemd[1]: mom-vdsm.service holdoff >> time over, scheduling restart. >> Jun 11 17:07:59 ovirt1.telia.ru systemd[1]: Cannot add dependency job >> for unit lvm2-lvmetad.socket, ignoring: Unit is masked. >> Jun 11 17:07:59 ovirt1.telia.ru systemd[1]: Stopped MOM instance >> configured for VDSM purposes. >> -- Subject: Unit mom-vdsm.service has finished shutting down >> -- Defined-By: systemd >> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel >> -- >> -- Unit mom-vdsm.service has finished shutting down. >> Jun 11 17:07:59 ovirt1.telia.ru systemd[1]: start request repeated too >> quickly for supervdsmd.service >> Jun 11 17:07:59 ovirt1.telia.ru systemd[1]: Failed to start Auxiliary >> vdsm service for running helper functions as root. >> -- Subject: Unit supervdsmd.service has failed >> -- Defined-By: systemd >> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel >> -- >> -- Unit supervdsmd.service has failed. >> -- >> -- The result is failed. >> Jun 11 17:07:59 ovirt1.telia.ru systemd[1]: Dependency failed for >> Virtual Desktop Server Manager. >> -- Subject: Unit vdsmd.service has failed >> -- Defined-By: systemd >> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel >> -- >> -- Unit vdsmd.service has failed. >> -- >> -- The result is dependency. >> Jun 11 17:07:59 ovirt1.telia.ru systemd[1]: Dependency failed for MOM >> instance configured for VDSM purposes. >> -- Subject: Unit mom-vdsm.service has failed >> -- Defined-By: systemd >> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel >> -- >> -- Unit mom-vdsm.service has failed. >> -- >> -- The result is dependency. >> Jun 11 17:07:59 ovirt1.telia.ru systemd[1]: Job mom-vdsm.service/start >> failed with result 'dependency'. >> Jun 11 17:07:59 ovirt1.telia.ru systemd[1]: Job vdsmd.service/start >> failed with result 'dependency'. >> Jun 11 17:07:59 ovirt1.telia.ru systemd[1]: supervdsmd.service failed. >> >> I also tried to enable DEBUG level but failed. >> >> [root@ovirt1 vdsm]# vdsm-client Host setLogLevel level=DEBUG >> vdsm-client: Connection to localhost:54321 with use_tls=True, timeout=60 >> failed: [Errno 111] Connection refused >> >> >> Regards, >> Artem >> >> >> >> On Tue, Jun 11, 2019 at 4:45 PM Shani Leviim <sleviim(a)redhat.com&gt; wrote: >> >>> Until will get a response from Dan (maybe it's related to a network >>> issue), I would suggest to re-configure the vdsm: >>> vdsm-tool configure --force >>> >>> some further steps are available here: https://www.ovirt.org/develop/ >>> developer-guide/vdsm/installing-vdsm-from-rpm.html# >>> installing--configuring-vdsm >>> >>> Let me know if it helped. >>> >>> Also, can you please attach a VDSM log with DEBUG level? >>> To do so: >>> vdsm-client Host setLogLevel level=DEBUG >>> >>> >>> *Regards,* >>> >>> *Shani Leviim* >>> >>> >>> On Tue, Jun 11, 2019 at 3:04 PM Artem Tambovskiy < >>> artem.tambovskiy(a)gmail.com&gt; wrote: >>> >>>> Hi Shani, >>>> >>>> yes, you are right - I can do ssh form aby to any hosts in the >>>> cluster. vdsm.log attached. >>>> I have tried to restart vdsm manually and even done a host restart >>>> several times with no success. >>>> Host activation fails all the time ... >>>> >>>> Thank you in advance for your help! >>>> Regard, >>>> Artem >>>> >>>> On Tue, Jun 11, 2019 at 10:51 AM Shani Leviim <sleviim(a)redhat.com&gt; >>>> wrote: >>>> >>>>> Hi Artem, >>>>> According to oVirt documentation [1], hosts on the same cluster >>>>> should be reachable from one to each other. >>>>> >>>>> Can you please share your vdsm log? >>>>> I suppose you do manage to ssh that inactive host (correct me if I'm >>>>> wrong). >>>>> While getting the vdsm log, maybe try to restart the network and >>>>> vdsmd services on the host. >>>>> >>>>> Another thing you can try on the UI is putting the host on >>>>> maintenance and then activate it. >>>>> >>>>> [1] https://www.ovirt.org/documentation/admin-guide/ >>>>> chap-Clusters.html#introduction-to-clusters >>>>> >>>>> >>>>> *Regards,* >>>>> >>>>> *Shani Leviim* >>>>> >>>>> >>>>> On Mon, Jun 10, 2019 at 4:42 PM Artem Tambovskiy < >>>>> artem.tambovskiy(a)gmail.com&gt; wrote: >>>>> >>>>>> Hello, >>>>>> >>>>>> May I ask you for and advise? >>>>>> I'm running a small oVirt cluster and couple of months ago I decided >>>>>> to do an upgrade from oVirt 4.2.8 to 4.3 and having an issues since that >>>>>> time. I can only guess what I did wrong - probably one of the problems that >>>>>> I haven't switched the cluster from iptables to firewalld. But this is just >>>>>> my guess. >>>>>> >>>>>> The problem is that I have upgraded the engine and one host, and >>>>>> then I done an upgrade of second host I can't bring it to active state. >>>>>> Looks like VDSM can't detect the network and fails to start. I even tried >>>>>> to reinstall the hosts from UI (I have seen that the packages being >>>>>> installed) but again, VDSM doesn't startup at the end and reinstallation >>>>>> fails. >>>>>> >>>>>> Looking at hosts process list I see script *wait_for_ipv4s* >>>>>> hanging forever. >>>>>> >>>>>> vdsm 8603 1 6 16:26 ? 00:00:00 /usr/bin/python >>>>>> /usr/share/ovirt-hosted-engine-ha/ovirt-ha-agent >>>>>> >>>>>> *root 8630 1 0 16:26 ? 00:00:00 /bin/sh >>>>>> /usr/libexec/vdsm/vdsmd_init_common.sh --pre-startroot 8645 8630 6 >>>>>> 16:26 ? 00:00:00 /usr/bin/python2 /usr/libexec/vdsm/wait_for_ipv4s* >>>>>> root 8688 1 30 16:27 ? 00:00:00 /usr/bin/python2 >>>>>> /usr/share/vdsm/supervdsmd --sockfile /var/run/vdsm/svdsm.sock >>>>>> vdsm 8715 1 0 16:27 ? 00:00:00 /usr/bin/python >>>>>> /usr/share/ovirt-hosted-engine-ha/ovirt-ha-broker >>>>>> >>>>>> The all hosts in cluster are reachable from each other ... That >>>>>> could be the issue? >>>>>> >>>>>> Thank you in advance! >>>>>> -- >>>>>> Regards, >>>>>> Artem >>>>>> _______________________________________________ >>>>>> Users mailing list -- users(a)ovirt.org >>>>>> To unsubscribe send an email to users-leave(a)ovirt.org >>>>>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >>>>>> oVirt Code of Conduct: https://www.ovirt.org/ >>>>>> community/about/community-guidelines/ >>>>>> List Archives: https://lists.ovirt.org/ >>>>>> archives/list/users(a)ovirt.org/message/TQX3LN2TEM4DECKKUMMRCWXTRM6BGI >>>>>> AB/ >>>>>> >>>>> >>>> >>>> -- >>>> Regards, >>>> Artem >>>> >>> >> >> -- >> Regards, >> Artem >> > -- Regards, Artem