Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
The current default behavior of yum4/dnf is skip_if_unavailable=True. This default behavior is being changed to False on bz1679509.
While one can manually set change this parameter setting in each individual repository file, it is also desired to have a global configuration setting as well so that repository configurations that do not have a behavior defined will default to False in order to be as safe as possible. Presumeably this parameter would be defined in /etc/yum.repos.d/{yum, dnf}.conf
Background reasoning:
With a default behavior of yum4/dnf is skip_if_unavailable=True, dnf will log messages that a repository is unavailable, but continue with changes for other repositories that are available.
This could cause scripts to appear as though they have succeeded when in fact the repo is unavailable. Install, search, or update operations will result in a return code of 0. Again, this occurs only if the desired repo is unavailable.
Users may incorrectly assume that security errata was applied, or that complex layered applications such as openstack were updated as a complete state along with the OS, when in fact some repositories might have been unavailable.
This could be seen as a behavioral regression to prior releases of yum-3 in RHEL 7 and earlier.
Workaround:
As a workaround one can add "skip_if_unavailable=False" to each of the BaseOS and AppStream repository entries in the /etc/yum.repos.d/redhat.repo file. This results in the behavior seen with yum3 on RHEL 7.
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/RHSA-2019:3583