Hi! On Tue, Feb 14, 2023 at 12:40 PM <lars.stolpe(a)bvg.de&gt; wrote: It's not completely clear, what you are trying to do. I suppose you refer to hosted-engine deployment with --restore-from-file. 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? 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 . - 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, -- Didi

On Tue, Feb 14, 2023 at 1:36 PM <lars.stolpe(a)bvg.de&gt; wrote: OK. That's a hosted-engine upgrade. A standalone engine is somewhat different. 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. 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. 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. 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. Good luck, -- Didi

On Wed, Feb 15, 2023 at 12:41 PM <lars.stolpe(a)bvg.de&gt; wrote: Sorry, I do not remember where this is done. Did you check the logs? Maybe More-or-less yes, in principle. See also https://github.com/oVirt/ovirt-appliance/ . Sorry, do not remember either... A quick search finds: https://bugzilla.redhat.com/show_bug.cgi?id=2087735 https://bugzilla.redhat.com/show_bug.cgi?id=2072881 https://github.com/oVirt/ovirt-engine/pull/244 So it might work. Good luck and best regards, -- Didi

On Wed, Feb 15, 2023 at 2:16 PM <lars.stolpe(a)bvg.de&gt; wrote: When was it usual to destroy it? I think it remains up since at least 4.3, perhaps much longer. 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, -- Didi

On Thu, Feb 16, 2023 at 12:19 PM <lars.stolpe(a)bvg.de&gt; wrote: 8.5? Where? RHV officially supports only RHEL 8.6, AFAIR. oVirt is tested regularly on Stream, so should most likely work on 8.7, or 8.8 when available. Not sure what you mean. vdsm is on the host, not on the engine vm. -- Didi

https://lists.ovirt.org/archives/list/devel@ovirt.org/message/SBCWNXLFLJB... that internal server error is because of updating to the latest updates available xD

The deploy finished successfull now. Task: upgrade oVirt 4.3 to oVirt 4.4 boundary conditions: access to repositories via repository server only (RH Satellite), encapsulated management network (no connection outside this segment) short steps i have done starting with an already installed host: 1. # dnf downgrade microcode_ctl until # vdsm-client Host getCapabilities | grep -i flags shows a matching CPU type (the same as in oVirt cluster configuration) 2. install and start squid on deploy host, no configuration necessary since 192.168.0.0/16 is already allowed 3. # hosted-engine --deploy --restore-from-file=/root/backup_ovirtman.bck --ansible-extra-vars=he_offline_deployment=true --ansible-extra-vars=he_pause_before_engine_setup=true gateway: <any pingable device within the managemant network> check method: ping Pause after adding the host? (Yes, No)[No]: yes (don't miss that "yes") 4. in the local VM: modify repositories as needed to match repo server, add exclude=postgresql-jdbc to CentOS-Stream-AppStream.repo add exclude=ovirt-release44 to ovirt-4.4.repo add proxy entry to /etc/dnf/dnf.conf (proxy=http://<deploy host IP>:3128/) add hostnames to /etc/hosts as needed 5. # dnf upgrade --nobest 6. check if all repos are still working, make corrections if needed check postgresql-jdbc # dnf list postgresql-jdbc must not be 42.2.14* , should be 42.2.3-3.el8_2 7. delete Lock-file 8. at the next stop, start firefox on host and log in to the engine set up host network as required, go on only, if all hosts and all storage domains are up after saving the network configuration the host routing may be broken, chek on host: # cat /proc/sys/net/ipv4/ip_forward if 0 do: # echo 1 > /proc/sys/net/ipv4/ip_forward all hosts und domains should be up again 9. delete Lock-file 10. chose hosted_storage and complete the deploy thanks to Didi for the hints and the patience

Hi, Great job! Perhaps you'd like to post this somewhere more noticeable/findable? I'd love to say "E.g. on the oVirt blog", but I have absolutely no idea how that is updated. Adding Sandro... Best regards, On Thu, Mar 9, 2023 at 6:46 AM <lars.stolpe(a)bvg.de&gt; wrote: -- Didi