3:32 p.m.
On Tue, Feb 14, 2023 at 1:36 PM <lars.stolpe(a)bvg.de> wrote:
Hi,
thank you for your answer, your hints are helpful
> Hi!
>
> On Tue, Feb 14, 2023 at 12:40 PM <lars.stolpe(a)bvg.de> wrote:
>
> It's not completely clear, what you are trying to do. I suppose you
> refer to hosted-engine deployment with --restore-from-file.
>
I do an upgrade vorm 4.3 to 4.4 according to the official oVirt upgrade guide.
the deploy command is as follow:
hosted-engine --deploy --restore-from-file=/root/backup_ovirtman13.bck
OK. That's a hosted-engine upgrade. A standalone engine is somewhat different.
>
> IIUC this code runs inside the engine VM, not the host, so your
> customizations on the host do not apply there. The appliance image
> used for creating the engine VM includes in itself a suitable
> ovirt-release package, which also includes the above failing repo.
> Does the engine VM (via the host it's running on) have direct access
> to the Internet? Or do you force all comm to go through your satellite
> proxy?
>
The hosts do not have direct access to the internet. The new engine have per default no
access to MAN either.
The 4.3 appliance did not need accass for installation, why would one change that...
Many software packages upgrade themselves during installation, I think
that's more-or-less the norm these days - no?
A concrete reason: If your current engine is newer than the one included in the
appliance, engine-backup inside the appliance will refuse to restore
your backup.
Upgrading to the latest before running engine-backup mitigates this issue.
> Anyway, some ways you can try to overcome the situation:
> - Run it offline (--ansible-extra-vars=he_offline_deployment=true)
> - Provide a custom enginevm_before_engine_setup hook to patch the
> configuration. See e.g. how this is done in ovirt-system-tests [1].
> - Pass (similarly to above) he_pause_before_engine_setup=true . Should
> work since 4.4.7, https://bugzilla.redhat.com/show_bug.cgi?id=1959273
> .
What is "offline deployment" doing different, are the necessary packets
transferred internally?
In this context, it means it's "offline" - does not require Internet
access.
In practice it means that whatever that's included in the appliance is
going to be
used for setup/deployment, without updating. You are welcome to search
ovirt-engine-appliance source code for he_offline_deployment, to see the actual
details - they are not that many.
> - See also [2]
>
> [1] https://github.com/oVirt/ovirt-system-tests Search the code for
> 'proxy', 'socks', etc.
> [2]
> https://github.com/didib/ovirt-ansible-collection/tree/master/roles/hoste...
>
>
> Good luck and best regards,
Can the management bridge switched to another interface after installation? That opens up
some easier ways to enable access to repositories.
The point where your deployment failed is before using the management
bridge configured by the engine - it's a more-or-less the default
'default' libvirt network.
I know, that in 4.3 is is not possible to do that.
...i miss the option to install the engine during deploy with OS .iso file ;)
At the time I also felt bad about this. Now, I can easily say it was worth it.
The number of issues/problems that people ran into after we introduced the
appliance and removed the option to do this manually greatly diminished, IMO.
at least that pause parameter will give me the chance to fix the repositories
Good luck,
--
Didi