On Tue, Jun 9, 2020 at 9:39 AM Anton Louw via Users <users(a)ovirt.org> wrote:
Hi Everybody,
Just a bit of background. A couple of weeks back I moved my self-hosted engine to a
standalone manager. Everything went smooth, my environment is up and running without any
issues.
How exactly did you do that?
Just one thing, when I want to reconfigure settings on my self-hosted
engine, it says:
“It seems that you are running your engine inside of the hosted-engine VM and are not in
"Global Maintenance" mode”
This message is in engine-setup, right?
engine-setup's code is checking this by:
/usr/share/ovirt-engine/setup/plugins/ovirt-engine-common/ovirt-engine/system/he.py
SELECT vm_guid, run_on_vds
FROM vms
WHERE vm_name = %(HostedEngineVmName)s;
where HostedEngineVmName is either the option of same name from
vdc_options, or 'HostedEngine' if missing. Then, where VdsId is
'run_on_vds' column of the result of above:
SELECT vds_id, ha_global_maintenance
FROM vds_statistics
WHERE vds_id = %(VdsId)s;
So if this isn't a hosted-engine setup anymore, it should probably be
safe to do:
update vds_statistics set ha_global_maintenance=f;
and perhaps restart the engine (in case it also does similar checks
itself but caches this data).
Please note that I didn't try this myself.
When trying to enable global maintenance from my node, I also get the below:
“Cannot connect to the HA daemon, please check the logs”
This is expected, no? You say it's not a hosted-engine setup anymore.
Is there something I missed when I moved my self-hosted engine to a standalone manager?
Either Yes, or the procedure you followed is incomplete. If latter,
please file a bug about it. Thanks!
Best regards,
--
Didi