I was able to change the maintenance state in the database to finish the upgrade with engine-setup.
these are the lines: select vds_id,ha_global_maintenance from vds_statistics where vds_id = '706599d5-2dbc-400c-b9da-5b5906de6dbd'; update vds_statistics set ha_global_maintenance = 't' where vds_id = '706599d5-2dbc-400c-b9da-5b5906de6dbd'; Now it's time to wait if the host and engine can reboot and start the vm's. regards gregor Am 26.11.18 um 06:07 schrieb gregor: > Hello, > > I upgraded one host from 4.0 to 4.1 without problems. Now I have a > problem with another host, in another network, where the Global > Maintenance mode is not recognized by engine-setup. > > Is there a way to force the setup or set the maintenance mode inside the > database? > > One problem can be that an the host was accidentally upgraded to 4.1 > before I upgraded the engine. > > kind regards > gregor > _______________________________________________ > 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/RQOX7YHHW3GTYEOP5YMG6NF2OD4BHUC7/ > _______________________________________________ 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/TLXT24MHJHSPQDI7ENVVJO2WVOBHHLB4/
