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.
Created attachment 1555282[details]
"Register System" dialog in cockpit two seconds after clicking "Register".
Description of problem:
below Steps to Reproduce
Version-Release number of selected component (if applicable):
[root@kvm-01-guest04 ~]# rpm -q subscription-manager-cockpit cockpit
subscription-manager-cockpit-1.23.8-35.el8.noarch
cockpit-185-2.el8.x86_64
How reproducible:
100%
Steps to Reproduce:
[root@kvm-01-guest04 ~]# subscription-manager config --server.hostname=subscription.rhsm.stage.redhat.com
[root@kvm-01-guest04 ~]# subscription-manager config --logging.default_log_level=DEBUG
[root@kvm-01-guest04 ~]# systemctl start cockpit.service
[root@kvm-01-guest04 ~]# hostname
kvm-01-guest04.lab.eng.rdu2.redhat.com
OPEN FIREFOX TO https://kvm-01-guest04.lab.eng.rdu2.redhat.com:9090/subscriptions ADVANCED ADD EXCEPTION
Login to cockpit gui with root/password
On Subscriptions tab, click Register and enter valid Login/Password in the dialog and click the dialog Register button.
At this point (while the pointer is spinning), notice the Register button behind the register dialog has flipped to "Unregister" while the spinning task of auto-attach is processing. Moreover, each of the fields on the register dialog are still active and clicking the Cancel button makes the dialog go away, but does NOT actually cancel the background registration process. If you continue watching the cockpit gui, the installed product goes green. Hence "Cancel" does not have intuitive effect the user expects (in otherwords, the user expects the registration process to unroll itself when they press Cancel in the midst of a spinning registration).
My advice would be to disable all of the fields in the registration dialog including the Cancel button until the background registration processing completes. If there was an error, the dialog should re-enable all the fields and wait for the user to make corrections and try again. If there was no error, the dialog disappears after the spinner stops spinning and the system is registered.
Thus the Cancel button is only useful to close the registration dialog when the user decides not to press the Register dialog button.
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/RHBA-2020:1849