I think that first you need to install the appliance and then in offline mode ot should skip connecting to yum repos. Best Regards,Strahil Nikolov On Fri, Aug 13, 2021 at 19:56, Andrew Lamarra<andrew.lamarra(a)gmail.com> wrote: Hi there. I'm trying to get oVirt up & running on a server in a network that has no access to the Internet. We do host mirrors of CentOS 7 & 8 repos (no Stream). I first tried the latest version of oVirt 4.4, however, I ran into an issue when trying to do the Hosted Engine deployment. The command I used was "hosted-engine --deploy --ansible-extra-vars=he_offline_deployment=true". But at some point, I get the following error: [ INFO  ] DNF Errors during downloading metadata for repository 'ovirt-4.4-centos-ceph-pacific':           - Status code: 404 for http://mirror.centos.org/centos/8-stream/storage/x86_64/ceph-pacific/repo... [ ERROR ] DNF 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 Seems like it's still trying to download something from the CentOS 8 Stream repo. So I figured that since we have the CentOS 7 repos hosted, I'll try oVirt v4.3. However, I don't see an option to do an "offline deployment" with this version. It says the "--ansible-extra-vars" option is invalid. I tried doing a regular deployment but it tries downloading from the oVirt repo: [ INFO ] TASK [ovirt.hosted_enging_setup : Install ovirt-engine-appliance rpm] [ ERROR ] fatal: [localhost]: FAILED! => ["attempts": 10, "changed": false, "msg": "Failure talking to yum: cannot retrieve metalink for repository: ovirt-4.3-epel/x86_64. Please verify its path and try again"} I can bring over a mirror of the ovirt-4.3 repo. I also see that there's some other repos in the "ovirt-4.3-dependencies.repo" file. Are those required for deploying the hosted engine VM as well? Or does anyone know if there's a way to do this deployment completely offline? Thank you for your time. _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)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/GDWCIZ3X3OK...

Thank you, both, for the help! I see that there's a version 4.3.10. Will that version not work? Andrew

Moin, We require a stable Centos Version and we selected Centos 7. I think the 4.4 is moved to Centos 8 and i am not sure if you can deploy it offline with the stream in background. We use the Ovirt Node installer for the servers with an Kickstart file and after the bare metal installation we start do to a lot with ansible but not the gluster deployment and the hosted engine deployment. Good working ansible scripts are missing yet. but if you have Ovirt 4.4 running without any internet activities please give me an information. Thanks Marcel ------ Originalnachricht ------ Von: "Strahil Nikolov via Users" <users(a)ovirt.org&gt; An: "Andrew Lamarra" <andrew.lamarra(a)gmail.com>; users(a)ovirt.org Gesendet: 15.08.2021 15:48:31 Betreff: [ovirt-users] Re: oVirt Hosted Engine Offline Deployment

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. 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).