Np :)
On Tuesday, June 11, 2019, Artem Tambovskiy
wrote:
> 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/
>
> probably one of the problems that I
> haven't switched the cluster from iptables to firewalld. But this is just
> my guess.
>
When switching to from 4.2.8 to 4.3.3 I did not change one host from iptables
to firewalld as well. I was still able to change it later even if the
documentation
Shani,
supervdsm failing too.
[root@ovirt1 vdsm]# systemctl status supervdsmd
● supervdsmd.service - Auxiliary vdsm service for running helper functions
as root
Loaded: loaded (/usr/lib/systemd/system/supervdsmd.service; static;
vendor preset: enabled)
Active: failed (Result: start-limit)
+Dan Kenigsberg
Hi Artem,
Thanks for the log.
It seems that this error message appears quite a lot:
2019-06-11 12:10:35,283+0300 ERROR (MainThread) [root] Panic: Connect to
supervdsm service failed: [Errno 2] No such file or directory (panic:29)
Traceback (most recent call last):
File
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,
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
6 matches
Mail list logo
