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.

comment #6 is proving hard to reproduce, since it does happen when there is a dns failure for the cdn hostname. I've seen it in firstboot where networking wasn't quite up yet when we ran our module (since mitigated by some rhn-client-tools changes that make this scenario less likely by being stricter about when it decides it actually needs and has networking). 

The traceback does need better error handling here though, but given
the circumstance of it being a somewhat unrecoverable network error, I don't think that's a huge deal.

The only way I've hit this was in an early implementation of activation keys where we didn't utilize any of the information assigned to an activation key, and then you tried to auto-attach some new subscriptions. Now that activation keys work properly, and we don't allow empty activation keys to be used during registration, I think this will be very hard to run into.

Think this is safe to close Alex?

I think this is safe to close.