I Also tried to run 
service vdsmd stop
vdsm-tool configure --force
service vdsmd start

and then restart the ha agent on all nodes but it doesnt help, the upgraded to 4.3 node is still not able to start hte engine.

/ E

Den tir. 12. feb. 2019 kl. 22:01 skrev Endre Karlson <endre.karlson@gmail.com>:
Yes that seems correct, but is there no way to work around it ?

Den tir. 12. feb. 2019 kl. 06:24 skrev Sahina Bose <sabose@redhat.com>:


On Tue, Feb 12, 2019 at 10:51 AM Endre Karlson <endre.karlson@gmail.com> wrote:
It's a upgrade from 4.2.x < latest version of 4.2 series. I upgraded by adding the 4.3 repo and doing the steps on the upgrade guide page 




Den man. 11. feb. 2019 kl. 23:35 skrev Greg Sheremeta <gshereme@redhat.com>:
Hi,

Is this an upgrade or a fresh installation? What version? What installation or upgrade commands / methods did you use?

Best wishes,
Greg



On Mon, Feb 11, 2019 at 5:11 PM Endre Karlson <endre.karlson@gmail.com> wrote:
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@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@ovirt.org/message/OWKVL6PWBCPYPKD6QWQJERZDDRYRIUKU/


--

GREG SHEREMETA

SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX

Red Hat NA

gshereme@redhat.com    IRC: gshereme

_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@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@ovirt.org/message/LYXZVYVJAJFEBITTNQBNNF6WVTPNZJMJ/