On Fri, Aug 27, 2021 at 7:59 PM Thomas Hoberg <thomas@hoberg.net> wrote:
You would do good to mirror everything that oVirt is using, especially if you want to install/rebuild while remaining offline.
The 1.1 GB file you mention is the oVirt appliance initial machine image, which unfortunately seems to get explicitly deleted from time to time, most likely the official clean-up scripts I use, whenever a deployment failed and I want to restart from a clean sheet.
The only place I know of that removes the appliance is in the end of hosted-engine deployment, not ovirt-hosted-engine-cleanup: https://bugzilla.redhat.com/show_bug.cgi?id=1676825 You should be able to prevent that by passing --ansible-extra-vars=he_remove_appliance_rpm=false . I didn't try that. You can also prevent _installing_ (or trying to update) the appliance rpm by passing the ova path as he_appliance_ova (or OVEHOSTED_VM/ovfArchive), e.g.: hosted-engine --deploy --otopi-environment=OVEHOSTED_VM/ovfArchive=str:/path/to/file.ova hosted-engine --deploy --ansible-extra-vars=he_appliance_ova=/path/to/file.ova See e.g. https://gerrit.ovirt.org/c/ovirt-system-tests/+/115589
If you're operating disconnected, security bugs won't scare you, which is where most of the updates are coming from. A good frozen CentOS7 repo state can last a long time, but sometimes even those are glitchy so you need to test thoroughly before going completely offline.
oVirt 4.3 is *very* stable (nothing done any more), but not free of bugs. You may be lucky and in an offline mode the combination may be good... until you want online again or add hardware too novel.
It's how I operate currently with most of my oVirt installations: CentOS7.latest and oVirt-4.3.last-with-bugs, because I want to test stuff in the VMs not underneath the hypervisor (and I am mostly using recycled producation hardware to support a lab).
Best regards, -- Didi