Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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:
Global Registration Page throws warning for
Invalid field: Activation Keys on General tab whereas the field for activation key is under Advanced tab
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1. sat web ui -> Hosts -> Register Host
Invalid field: Activation Keys
under general tab whereas activation key field to be selected is under Advanced tab
Actual results:
Expected results:
Either move this warning to the Advanced tab or move activation key field to the general tab
Additional info:
Thanks for attaching the screenshot!
It appears that this is a duplicate of bug 2059829. While that bugzilla was opened after this one, I am going to close this one since the other has been cloned upstream.
If there are any questions or concerns, do re-open with the appropriate details.
*** This bug has been marked as a duplicate of bug 2059829 ***