Not sure if this should be filed under yum or dnf component.
Description of problem:
Customer is using a complex build/configuration process which involves creating services in post section of a kickstart, these services install various rpms from various custom repos (that have signed metadata).
When using this build process with RHEL8.1 rpm installs failed as not all repos were available.
We have narrowed this down to running yum repolist command in sysv init script on startup (running same script in unit file also fails).
This worked on RHEL8.0 and if I upgrade the yum and dnf packages (see below) in the kickstart before rebooting the server I can reproduce the same behaviour.
yum repolist command works correctly in installed system.
Version-Release number of selected component (if applicable):
The following package versions appear to be involved
Steps to Reproduce:
1. install RHEL8.1 using attached kickstart (modify my.repo to point to your own custom repos)
2. This will run /usr/local/bin/repocheck.sh in sysv init script on start, which runs "yum -y repolist" in a loop until all required repos are listed
The sysv init script outputs the following until all repos are found
INFO: 0 out of 3 REPOs are loaded - Tue 10 Dec 04:51:32 EST 2019
INFO: 0 out of 3 REPOs are loaded - Tue 10 Dec 04:51:38 EST 2019
INFO: 3 out of 3 REPOs are loaded - Tue 10 Dec 04:51:44 EST 2019
script also collects stderr and this shows importing gpg_key but only for first repo it finds, each time through the loop it imports one gpg key until all repo keys are imported
yum -y repolist should import all required keys in one transaction like on RHEL8.0
This also produces same result if I run the repocheck script in a unit file.
This does not appear to be a change in systemd as if I update just the systemd packages in the kickstart from 8.0 to 8.1 versions problem does not reproduce.
The repocheck script is just to illustrate the problem and mimic customer's complex build process.
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.
*** Bug 1792506 has been marked as a duplicate of this bug. ***