On Wed, Aug 19, 2020 at 12:01 PM Raphael Höser <raph...@hoeser.info> wrote: > > Thanks Didi, > > > On Wed, Aug 19, 2020 at 10:33 AM Raphael Höser <raphael(a)hoeser.info> > > wrote: > > > > It does - and also the full log below. It means it fails on the host, > > not inside the engine vm. > I meant, that the output wasn't changed by this. > > > It probably fails because our internal "minidnf" does not support all > > the stuff you try to do to dnf. > This seems to be the case. > > > You can try: > > > > hosted-engine --deploy > > --otopi-environment=PACKAGER/dnfpackagerEnabled=bool:False > This Works! > > Thanks a lot for your support!
You are welcome, thanks for the report! :-) > > For anyone stumbling upon this at a later point: > This workaround might work for you, if you made changes to /etc/dnf/dnf.conf > for dnf to work on your CentOS8 instance. > In our case the problem was the proxy authentication method dnf uses. Actually, AFAICT, we never really need dnfpackager anymore, as all the very little logic around installing/removing the appliance is now done in ovirt-ansible-hosted-engine-setup. So it's safe to always use (and thus skip the lengthy dnf cache update etc.). Feel free to open a bug to get this removed and use an "offline packager" (like --offline in engine-setup). Best regards, -- Didi _______________________________________________ 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/FVIF2JE7YFBKNRIMDIJWPZXPNI2CEJNW/
