This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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.
Bug 2160484 - Failed to update linux on RHEL-8.5_HVM-20220127-x86
Summary: Failed to update linux on RHEL-8.5_HVM-20220127-x86
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: ec2-images
Version: 8.5
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: rc
: ---
Assignee: Dennis Gregorovic
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-01-12 15:05 UTC by canicks@amazon.com
Modified: 2023-09-11 13:06 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-11 13:06:18 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-2897 0 None Migrated None 2023-09-11 13:06:18 UTC
Red Hat Issue Tracker RHELPLAN-144966 0 None None None 2023-01-12 15:08:41 UTC

Description canicks@amazon.com 2023-01-12 15:05:57 UTC 
Description of problem:
AMI ami-08ee530f98edc54d8 (RHEL-8.5_HVM-20220127-x86_64-3-Hourly2-GP2) from account 309956199498 is failing to update in multiple regions (ap-south-1, us-east-1)

Version-Release number of selected component (if applicable):
8.5

How reproducible:
Run sudo yum update

Steps to Reproduce:
1. Launch AMI in EC2 using image ID ami-08ee530f98edc54d8 in ap-south-1/us-east-1
2. SSH into instance and run sudo yum update
3.

Actual results:
Problem 1: cannot install both NetworkManager-libnm-1:1.40.0-5.el8_7.x86_64 and NetworkManager-libnm-1:1.40.0-2.el8_7.x86_64  - package NetworkManager-cloud-setup-1:1.40.0-2.el8_7.x86_64 requires NetworkManager-libnm(x86-64) = 1:1.40.0-2.el8_7, but none of the providers can be installed
  - cannot install the best update candidate for package NetworkManager-libnm-1:1.32.10-4.el8.x86_64
  - cannot install the best update candidate for package NetworkManager-cloud-setup-1:1.32.10-4.el8.x86_64 Problem 2: package authselect-compat-1.2.5-1.el8.x86_64 requires authselect(x86-64) = 1.2.5-1.el8, but none of the providers can be installed
  - cannot install both authselect-1.2.5-2.el8_7.x86_64 and authselect-1.2.5-1.el8.x86_64  - cannot install the best update candidate for package authselect-compat-1.2.2-3.el8.x86_64
  - cannot install the best update candidate for package authselect-1.2.2-3.el8.x86_64
 Problem 3: problem with installed package NetworkManager-cloud-setup-1:1.32.10-4.el8.x86_64  - package NetworkManager-cloud-setup-1:1.32.10-4.el8.x86_64 requires NetworkManager = 1:1.32.10-4.el8, but none of the providers can be installed
  - package NetworkManager-cloud-setup-1:1.32.10-5.el8_5.x86_64 requires NetworkManager = 1:1.32.10-5.el8_5, but none of the providers can be installed  - package NetworkManager-cloud-setup-1:1.36.0-4.el8.x86_64 requires NetworkManager = 1:1.36.0-4.el8, but none of the providers can be installed
  - package NetworkManager-cloud-setup-1:1.36.0-7.el8_6.x86_64 requires NetworkManager = 1:1.36.0-7.el8_6, but none of the providers can be installed
  - package NetworkManager-cloud-setup-1:1.36.0-9.el8_6.x86_64 requires NetworkManager = 1:1.36.0-9.el8_6, but none of the providers can be installed
  - package NetworkManager-cloud-setup-1:1.40.0-1.el8.x86_64 requires NetworkManager = 1:1.40.0-1.el8, but none of the providers can be installed
  - package NetworkManager-cloud-setup-1:1.40.0-2.el8_7.x86_64 requires NetworkManager = 1:1.40.0-2.el8_7, but none of the providers can be installed  - cannot install both NetworkManager-1:1.40.0-5.el8_7.x86_64 and NetworkManager-1:1.32.10-4.el8.x86_64
  - package NetworkManager-1:1.40.0-5.el8_7.x86_64 obsoletes NetworkManager < 1:1.36.0-0.6 provided by NetworkManager-1:1.32.10-4.el8.x86_64
  - cannot install both NetworkManager-1:1.40.0-5.el8_7.x86_64 and NetworkManager-1:1.32.10-5.el8_5.x86_64  - package NetworkManager-1:1.40.0-5.el8_7.x86_64 obsoletes NetworkManager < 1:1.36.0-0.6 provided by NetworkManager-1:1.32.10-5.el8_5.x86_64
  - cannot install both NetworkManager-1:1.40.0-5.el8_7.x86_64 and NetworkManager-1:1.36.0-4.el8.x86_64  - cannot install both NetworkManager-1:1.40.0-5.el8_7.x86_64 and NetworkManager-1:1.36.0-7.el8_6.x86_64
  - cannot install both NetworkManager-1:1.40.0-5.el8_7.x86_64 and NetworkManager-1:1.36.0-9.el8_6.x86_64
  - cannot install both NetworkManager-1:1.40.0-5.el8_7.x86_64 and NetworkManager-1:1.40.0-1.el8.x86_64
  - cannot install both NetworkManager-1:1.40.0-5.el8_7.x86_64 and NetworkManager-1:1.40.0-2.el8_7.x86_64
  - package NetworkManager-team-1:1.40.0-5.el8_7.x86_64 requires NetworkManager(x86-64) = 1:1.40.0-5.el8_7, but none of the providers can be installed
  - cannot install the best update candidate for package NetworkManager-team-1:1.32.10-4.el8.x86_64
 Problem 4: problem with installed package authselect-compat-1.2.2-3.el8.x86_64
  - package authselect-compat-1.2.2-3.el8.x86_64 requires authselect(x86-64) = 1.2.2-3.el8, but none of the providers can be installed
  - package authselect-compat-1.2.5-1.el8.x86_64 requires authselect(x86-64) = 1.2.5-1.el8, but none of the providers can be installed
  - package authselect-1.2.2-3.el8.x86_64 requires authselect-libs(x86-64) = 1.2.2-3.el8, but none of the providers can be installed
  - package authselect-1.2.5-1.el8.x86_64 requires authselect-libs(x86-64) = 1.2.5-1.el8, but none of the providers can be installed
  - cannot install both authselect-libs-1.2.5-2.el8_7.x86_64 and authselect-libs-1.2.2-3.el8.x86_64
  - cannot install both authselect-libs-1.2.5-2.el8_7.x86_64 and authselect-libs-1.2.5-1.el8.x86_64
  - cannot install the best update candidate for package authselect-libs-1.2.2-3.el8.x86_64

Expected results:
Expected to update without issues
Comment 1 canicks@amazon.com 2023-01-12 15:19:26 UTC 
ap-south-1, eu-south-1, eu-west-1, eu-west-2, us-east-1
Comment 2 canicks@amazon.com 2023-01-12 15:20:10 UTC 
Impacted regions now include the previously commented regions.
Comment 3 Gregg Tanzillo 2023-01-12 16:04:41 UTC 
It tried to recreate, using the steps above and was not successful.

I launched image "RHEL-8.5_HVM-20220127-x86_64-3-Hourly2-GP2" (ami-019599717e2dd5baa) in us-east-1, while logged into the rhui-dev account. I was able to run yum update and it successfully ran to completion. I'll try the same steps in one of the other regions.
Comment 4 canicks@amazon.com 2023-01-12 16:08:08 UTC 
Just attempted in ap-south-1 and got the same issue. I will also try again in different regions.
Comment 5 Martin Minar 2023-01-12 16:28:06 UTC 
I was able to reproduce it in eu-west-1.
Upon investigation problem is caused by two packages:
NetworkManager-cloud-setup
authselect-compat
Since those two packages are only ones from a group (NetworkManager and authselect) that are in different repository (Appstream instead of BaseOS) and since according to Gregg a problem is no longer present in us-east-1, I'm inclined to say that it look like synchronization issue. CDN-RHUI synchronization issue in particular, since even forcing sync in eu-west-1 did not resolved the issue it might be something on CDN side.

We'll try to find out what happened there - unless issue won't fix itself by follow up synces.

In the meantime - recomended --allow-erasing and/or --nobest options work - first one being destructive in the sense that it removes those two culprits, second one installing newer versions, but not latest - but both will install latest packages of the rest of OS.
Comment 6 canicks@amazon.com 2023-01-12 16:34:22 UTC 
Confirmed no longer experiencing in us-east-1, but still the same in ap-south-1, eu-west-1, eu-west-2 and eu-south-1
Comment 7 Radek Bíba 2023-01-12 17:18:58 UTC 
Ap-south-1 and eu-west-1 are synced now.
Comment 8 Joe Vlcek 2023-01-12 17:31:16 UTC 
The failing packages have dependencies in multiple repositories. In order to succeed all repositories must be synchronized, which takes at most 6 hours after new content is made available. In this case it appears access was failing only in the window of time when the cross dependency repositories were sync-ing.

Therefore this issue will be resolved in at most 6 hours.
Comment 9 canicks@amazon.com 2023-01-12 17:42:18 UTC 
Confirmed these are working. eu-west-2 is the last region noted that isn't working.
Comment 10 canicks@amazon.com 2023-01-12 19:56:11 UTC 
Region ap-northeast-1 is also being affected. It was left out by mistake.
Comment 11 Gregg Tanzillo 2023-01-12 21:15:02 UTC 
I just tested region ap-northeast-1 and it is now working. I would expect that should there be any remaining regions affected, they will be corrected soon as they run their periodic sync with the CDN
Comment 12 RHEL Program Management 2023-09-11 13:04:06 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 13 RHEL Program Management 2023-09-11 13:06:18 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.