I believe there's a bug here:
https://github.com/oVirt/ovirt-ansible-collection/blob/master/roles/engine_setup/tasks/main.yml
which besides the he_offline_deployment condition it relies
on ovirt_engine_setup_perform_upgrade which is never passed to from the
hosted_engine_setup role.
If he can post the full log, it will be easier to understand where the
issue is and why does ansible triggers yum repos.
Another way to workaround it is to create a pre engine setup hook as
ansible task and use it to configure the repos on the engine vm that it
will use the local repos and not reach the internet at any point.
On Thu, Apr 28, 2022 at 8:55 PM Strahil Nikolov via Users <users@ovirt.org>
wrote:
> Theoretically everything is possible.
> In this situation I can recommend you to open an issue as
> he_offline_deployment=true should really mean offline.
>
> Currently you can modify the Ansible code on the system and modify the
> repos pointing to your Satellite.
>
> Best Regards,
> Strahil Nikolov
>
> On Tue, Apr 26, 2022 at 12:02, v...@itiviti.com
> <v...@itiviti.com> wrote:
> Hi Everyone,
> In my compagny, we try to deploy engine on 2 RHEL8 hosts we already
> installed.
>
> We don't have direct internet access, so the RHEL8 hosts have been setup
> using some internal EL repo (using redhat satellite)
>
> We have also duplicated internaly the necessary ovirt repositories, so all
> ovirt packages can be installed.
>
> Now the blocking part is the deployment of the engine. Is it really
> possible to deploy an engine without having internet connection?
>
> We tried several time but never succeeded.
>
> I tried with ansible extra var "he_offline_deployment=true", naively
> thinking it will download necessary packages for the engine through the
> repositories already configured on the physical hosts (like the physical
> host act as proxy)
>
> I also tried by specifying the ova file with
> he_appliance_ova=/usr/share/ovirt-engine-appliance/ovirt-engine-appliance-4.4-20211020135049.1.el8.ova
>
> both options have also been tried together
> (--ansible-extra-vars=he_appliance_ova=/usr/share/ovirt-engine-appliance/ovirt-engine-appliance-4.4-20211020135049.1.el8.ova
> --ansible-extra-vars=he_offline_deployment=true)
>
> But at the end, it seems the engine deployment process makes the engine to
> need to reach the ovirt internet repositories, as it always failed with:
>
> 2022-04-24 17:39:53,268+0100 ERROR
> otopi.ovirt_hosted_engine_setup.ansible_utils
> ansible_utils._process_output:110 fatal: [localhost -> 192.168.1.154]:
> FAILED! => {"changed": false, "msg": "Failed to download metadata for repo
> 'ovirt-4.4-centos-ceph-pacific': Cannot download repomd.xml: Cannot
> download repodata/repomd.xml: All mirrors were tried", "rc": 1, "results":
> []}
>
> FYI the pacific repo works fine when we download packages on physical
> hosts.
> ANother thing to know is that before being able to use our internal repo
> present on our redhat satellite, a system need to install the satellite
> crtificate, and register to satellite.
>
> it would be so nice if we can achieve a fully offline engine deploy (which
> mean no internet access at all, including the engine itself), but we start
> to lack of clues if it's really possible.
>
> Here are all the ovirt packages installed on the physical hosts:
>
> $rpm -qa | grep ovirt
> ovirt-ansible-collection-1.6.5-1.el8.noarch
> ovirt-imageio-daemon-2.3.0-1.el8.x86_64
> ovirt-host-4.4.9-2.el8.x86_64
> ovirt-engine-appliance-4.4-20211020135049.1.el8.x86_64
> ovirt-imageio-common-2.3.0-1.el8.x86_64
> python3-ovirt-engine-sdk4-4.4.15-1.el8.x86_64
> ovirt-host-dependencies-4.4.9-2.el8.x86_64
> ovirt-hosted-engine-setup-2.5.4-2.el8.noarch
> ovirt-imageio-client-2.3.0-1.el8.x86_64
> ovirt-vmconsole-host-1.0.9-1.el8.noarch
> ovirt-provider-ovn-driver-1.2.34-1.el8.noarch
> cockpit-ovirt-dashboard-0.15.1-1.el8.noarch
> python3-ovirt-setup-lib-1.3.2-1.el8.noarch
> ovirt-hosted-engine-ha-2.4.9-1.el8.noarch
> ovirt-vmconsole-1.0.9-1.el8.noarch
>
> thanks a lot in advance
> _______________________________________________
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/5IKRUH4A3MY26URYVWIQEAXTIVA4ZEA3/
>
> _______________________________________________
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/OTS7PU7DMWC6KEKTOAHJ5OILFGE6BI4K/
>
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/NTFKYX32VGDFBHDUPTXDJEXOEXOGRKUS/
