On Wed, Feb 15, 2023 at 2:16 PM <lars.stolpe(a)bvg.de> wrote:
When was it usual to destroy it? I think it remains up since at least 4.3, perhaps much longer.
As i was moving (reinstall with restore) hosted storage to a new SAN (V 4.3), the local VM was shut down before i could take action several times.
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
engine-setup also has an option '--offline'. Running HE deploy with offline should also use this.
Good!
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.
There is no way to skip engine-setup and let you run it manually. You can provide before/after hooks.
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.
Agreed, in principle.
Good luck and best regards,
Almost... The deploy went good, til this host was added. There is a bug that prevents vdsm to read the local configuration. I used RHEL 8.5 and did not update, because the latest update 7.9 made oVirt 4.2 inoperable. So i decided to use the version mentioned in the documentation. Update vdsm and back to square 1 I'm confident it will work afterwards. best regards