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:
Two error message shows when press "Attach" button in rhsm gui "All available Subscriptions" tab when the system can not connect to the candlepin server 

Version-Release number of selected component (if applicable):
subscription-manager-1.10.8-1.el7
subscription-manager-gui-1.10.8-1.el7
subscription-manager-firstboot-1.10.8-1.el7
python-rhsm-1.10.8-1.el7

How reproducible:
always

Steps to Reproduce:
1.register the system
2.open subscription-manager-gui and go to "All available Subscriptions" tab, press "Update" button
3.let the candlepin server become unreachable, in my case I use cmd "ifconfig eth0 down"
4.select one of the listed subscription and press "Attach" button.

Actual results:
Two error message shows to tell you that "Network error". They located in the same place so after you press "OK" button on the front one, you will find there is still a error message. 

Expected results:
Only one error message window should show.

Additional info:

Created attachment 839385 [details]
the two error message window.

I think I'm going to close this, I understand that this behaviour is weird but the double error occurs once because the bind fails, then we return to the all subscriptions screen, which automatically tries to refresh and fails causing another error popup.

However to even get to this point, the server must be up when we list subscriptions, but go down by the time we hit attach. Given the likely very small interval between these two events, the complexity in communicating between these two pieces of code that an error has occurred previously, and the fact that this is a very minor bug, I'm going to close this as a WONTFIX as I don't think it's worth the errort / complexity to solve.

If this proves to be a serious issue for anyone we can reopen.