Hide Forgot
Description of problem: This can be particularly seen with Satellite installations defining another repository than cdn.redhat.com. When the repository is *not* resolvable through DNS, but is only known to /etc/hosts, the upgrade of the system fails with the following error in "phase 2" (systemd-nspawn -D /var/lib/leapp/el8userspace ...): [MIRROR] irqbalance-1.4.0-4.el8.x86_64.rpm: Curl error (6): Couldn't resolve host name for https://<HOSTNAME>/content/dist/rhel8/8.1/x86_64/baseos/os/Packages/i/irqbalance-1.4.0-4.el8.x86_64.rpm [Could not resolve host: <HOSTNAME>] Version-Release number of selected component (if applicable): leapp-0.9.0-1.el7.rpm How reproducible: Always Steps to Reproduce: 1. Make sure "cdn.redhat.com" is not available through DNS - add "PEERDNS=no" in /etc/sysconfig/network-scripts/ifcfg-XXX file - restart the network - empty file /etc/resolv.conf - add entry to /etc/hosts: 95.101.56.251 cdn.redhat.com 10.4.204.72 subscription.rhsm.redhat.com 2. Run "leapp upgrade" Actual results: Fails fetching packages in 2nd phase Additional info: This is due to /etc/hosts from the hosts not being available in /var/lib/leapp/el8userspace. Instead /var/lib/leapp/el8userspace/etc/hosts contains the default file (with "localhost" entries only) installed by setup-2.12.2-2.el8_1.1.noarch.rpm
Prior to executing phase 2 ("systemd-nspawn -D /var/lib/leapp/el8userspace ..."), /etc/hosts from the system must be copied to /var/lib/leapp/el8userspace/etc
Thanks Renaud for report and investigation! I have feeling that we probably missed this possible issue several times. I will add fix fix soon.
Note that probably other files need to be copied as well, e.g. /etc/nsswitch.conf if using alternative resolution methods (Centrify, ...)
Good point. I will probably sync with network sst about the proper solution as it looks this is just the tip of the iceberg.
related PR: https://github.com/oamg/leapp-repository/pull/474
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:1959