On Wed, Feb 15, 2023 at 2:16 PM <lars.stolpe(a)bvg.de> wrote:
well, that's interesting...
The deploy abortion did not destroy the local runing VM as usual.
When was it usual to destroy it? I think it remains up since at least
4.3, perhaps much longer.
So i disabled CentOS-Stream-PowerTools.repo again (was re-enabled by
Did you try to check where/when/what does this? Perhaps on the host on
/var/log/ovirt-hosted-engine-setup, not on the engine VM itself
and provided my modified oVirt repositories.
I ran engine-setup on the running local VM, setup checked for updates,
engine-setup also has an option '--offline'. Running HE deploy with
offline should also use this.
nothing to be done, and then running fine through the complete setup.
Now i have a local VM engine running fine, the hosts are recognized as "up" ,
VMs and storage domains are fine as well.
Is there a way to make the deploy jump to that stage and resume?
Definitely not easily. If you just want to try this as a learning
game, you can try. If you want to automate this, or plan for
production, I'd use a different approach.
Or: can i do the engine-setup(with restore or without) myself after providing my modified
There is no way to skip engine-setup and let you run it manually. You
can provide before/after hooks.
If the deploy finds nothing to be updated, all should run afterwards?
In principle yes, and this might be a good approach - replace all
repos with yours (e.g. in a before hook), make sure yours do not
include a release package that will overwrite your repos.
Since this is the test for upgrading the production i should not depend on "i hope
the local VM is still running after deploy abort"
Agreed, in principle.
All i could find in engine-setup log is, that the repository could not be reached.
Good luck and best regards,