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.
Bug 1994654 - [RFE] In Satellite WebUI -> Hosts -> Register Host page >> Advanced Activation Keys should be auto selected in case of single Activation Key.
Summary: [RFE] In Satellite WebUI -> Hosts -> Register Host page >> Advanced Activatio...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Registration
Version: 6.10.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: 6.15.0
Assignee: Girija Soni
QA Contact: Gaurav Talreja
Zuzana Lena Ansorgova
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-17 15:58 UTC by Kshitij
Modified: 2024-04-23 17:10 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
.Satellite auto-selects the activation key during host registration When you register a host using *Hosts* > *Register Host* in the {ProjectWebUI} and there is only one activation key available for the organization and location selected in the registration form, Satellite selects the activation key automatically.
Clone Of:
Environment:
Last Closed: 2024-04-23 17:10:51 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-17376 0 None None None 2023-05-11 13:02:04 UTC
Red Hat Issue Tracker SAT-4845 0 None None None 2021-09-02 07:30:20 UTC
Red Hat Product Errata RHSA-2024:2010 0 None None None 2024-04-23 17:10:52 UTC

Description Kshitij 2021-08-17 15:58:58 UTC 
Description of problem


At the time of host registration the Activation key should be selected automatically in case of a single activation key In Satellite WebUI -> Hosts -> Register Host page >> Advanced Tab >> Activation key

Version-Release number of selected component (if applicable):

6.10 

How reproducible:



Steps to Reproduce:
1. Create a single activation key on Red Hat Satellite.
2. On Satellite Web UI >> Host >> Register host >> Advanced >> Activation Keys 

Actual results:

Activation Keys need to be selected manually even though there is a single Activation key on Red Hat Satellite.

Expected results:

If there is a single Activation Key then it should be auto-selected. If there are multiple Activation keys then the current behavior is correct.


Additional info:
Comment 1 Brad Buckingham 2023-03-06 11:37:55 UTC 
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.
Comment 2 Maria Svirikova 2023-03-21 13:42:17 UTC 
A couple of improvements for multiple Activation keys displayed in the form 

1. If there are many AKs, do not preselect any. And keep a primary button of the form disabled

2. Do not display an error upon a user's arrival to the form, even if there are required fields. Let a user interacts with the page first.

3. Display an error upon interaction with the required field without filling it out or the loss of focus.

4. Display an error according to PF4 -  Red helper text under the field, a red icon on the left from the caret, underlined field, AND erase a toast alert. (Toast shouldn't be used this way)
See PF4 form guidelines: https://www.patternfly.org/v4/components/form/design-guidelines/#errors-and-validation or https://www.patternfly.org/v4/components/form-control#select
Comment 3 Leos Stejskal 2023-03-27 04:40:46 UTC 
The following fields are marked as required in the UI but they shouldn't be:

* Organization
* Location
* Setup REX
* Setup Insights
* REX pull

viz API doc /apidoc/v2/registration_commands.en.html
Comment 5 Brad Buckingham 2023-04-06 16:33:19 UTC 
Based upon further review from the engineering team, this bugzilla will not be closed at this time.
Comment 6 Girija Soni 2023-04-12 17:16:21 UTC 
Created redmine issue https://projects.theforeman.org/issues/36295 from this bug
Comment 7 Girija Soni 2023-04-18 10:57:54 UTC 
Created redmine issue https://projects.theforeman.org/issues/36312 from this bug
Comment 10 Brad Buckingham 2023-10-30 11:29:29 UTC 
Bulk setting Target Milestone = 6.15.0 where sat-6.15.0+ is set.
Comment 14 errata-xmlrpc 2024-04-23 17:10:51 UTC 
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 (Important: Satellite 6.15.0 release), 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/RHSA-2024:2010
Note You need to log in before you can comment on or make changes to this bug.