On Fri, Mar 22, 2019 at 10:06 AM Artem Tambovskiy < [email protected]> wrote:
> Hi, > > I have exactly the same issue after upgrade from 4.2.8 to 4.3.2. I can > reach the host from SHE but the VDSM is constantly failing to start on the > host after upgrade. > Can you please attach the output of systemctl status vdsmd and your /var/log/vdsm/vdsm.log? > > чт, 21 мар. 2019 г., 19:48 Simone Tiraboschi <[email protected]>: > >> >> >> On Thu, Mar 21, 2019 at 3:47 PM Arif Ali <[email protected]> wrote: >> >>> Hi all, >>> >>> Recently deployed oVirt version 4.3.1 >>> >>> It's in a self-hosted engine environment >>> >>> Used the steps via cockpit to install the engine, and was able to add >>> the rest of the oVirt nodes without any specific problems >>> >>> We tested the HA of the hosted-engine without a problem, and then at one >>> point of turn off the machine that was hosting the engine, to mimic >>> failure to see how it goes; the vm was able to move over successfully, >>> but some of the oVirt started to go into Unassigned. From a total of 6 >>> oVirt hosts, I have 4 of them in this state. >>> >>> Clicking on the host, I see the following message in the events. I can >>> get to the hosts via the engine, and ping the machine, so not sure what >>> it's doing that it's no longer working >>> >>> VDSM <snip> command Get Host Capabilities failed: Message timeout which >>> can be caused by communication issues >>> >>> Mind you, I have been trying to resolve this issue since Monday, and >>> have tried various things, like rebooting and re-installing the oVirt >>> hosts, without having much luck >>> >>> So any assistance on this would be grateful, maybe I've missed something >>> really simple, and I am overlooking it >>> >> >> Can you please check that VDSM is correctly running on that nodes? >> Are you able to correctly reach that nodes from the engine VM? >> >> >>> >>> -- >>> regards, >>> >>> Arif Ali >>> _______________________________________________ >>> Users mailing list -- [email protected] >>> To unsubscribe send an email to [email protected] >>> 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/[email protected]/message/FYG7NEV24JCCR4RIXLOMZ2CAPYAH4GDH/ >>> >> _______________________________________________ >> Users mailing list -- [email protected] >> To unsubscribe send an email to [email protected] >> 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/[email protected]/message/Y7YVXSLFJ3XCQSPJSPQ2K2OCCMS2F465/ >> >
_______________________________________________ Users mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected]/message/IHBNGSSPVISINL53SWM2SG6PJCWPPWRC/
