On Tue, Apr 13, 2021 at 7:42 AM Nur Imam Febrianto <nur_imam(a)outlook.com> wrote:
Fixes the issue by changing OVESETUP_ENGINE_CORE/enable=bool:'False' to
OVESETUP_ENGINE_CORE/enable=bool:'True’
Still don’t know why it shows false, but now I can confirm after changing that to True,
running engine-setup again upgraded my Engien to 4.4.5.
Thanks for your help.
Glad that it worked, and thanks for the report!
I strongly recommend that you spend some time investigating
what/who/why it was changed.
This is most likely a mistake someone made at some point. It might be
broader than just this file, or it might be some other kind of problem
(e.g. a machine crashed in the middle of engine-setup and left files
corrupted).
If you can't find why/who, and suspect it's a bug, we'd definitely
like to get more information.
Some things you can check (other than usual site-specific things like
who logged in, when you changed stuff there, etc.):
- All /var/log/ovirt-engine/setup/* logs, their timestamps, and their
contents (e.g. grep them all for "OVESETUP_ENGINE_CORE/enable").
- /etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf* - the file
itself, and backups (made by engine-setup or otherwise), timestamps
etc.
- /etc/ovirt-engine/uninstall.d/* - engine-setup (and other related
tools) keep there information about all files it created/chagned -
mainly used by engine-cleanup
Good luck and best regards,
--
Didi