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.

The following was filed automatically by firstboot:
firstboot 1.110.8 exception report
Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/firstboot/interface.py", line 105, in _nextClicked
    self.advance()
  File "/usr/lib/python2.6/site-packages/firstboot/interface.py", line 148, in advance
    result = module.apply(self, self.testing)
  File "/usr/share/rhn/up2date_client/firstboot/rhn_login_gui.py", line 63, in apply
    rhnregGui.try_to_activate_hardware()
  File "/usr/share/rhn/up2date_client/rhnregGui.py", line 1372, in try_to_activate_hardware
    code = rhnreg._activate_hardware(username, password)
  File "/usr/share/rhn/up2date_client/rhnreg.py", line 612, in _activate_hardware
    login, password, hardwareInfo)
  File "/usr/share/rhn/up2date_client/rhnreg.py", line 643, in activateHardwareInfo
    hardwareInfo, other)
  File "/usr/share/rhn/up2date_client/rhnserver.py", line 50, in __call__
    return rpcServer.doCall(method, *args, **kwargs)
  File "/usr/share/rhn/up2date_client/rpcServer.py", line 277, in doCall
    raise up2dateErrors.CommunicationError(e.errmsg)
CommunicationError: Error communicating with server. The message was:
Service Temporarily Unavailable

Created attachment 486571 [details]
File: backtrace

CommunicationError: Error communicating with server. The message was:
Service Temporarily Unavailable


This is something we cannot fix in the RHEL RHN Client. If the RHN Hosted services are down, they are down, all we can do is report this to the client. 

Regards,
Cliff