Bug 1994654
Summary: | [RFE] In Satellite WebUI -> Hosts -> Register Host page >> Advanced Activation Keys should be auto selected in case of single Activation Key. | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Kshitij <kupadhya> |
Component: | Registration | Assignee: | Girija Soni <gisoni> |
Status: | CLOSED ERRATA | QA Contact: | Gaurav Talreja <gtalreja> |
Severity: | medium | Docs Contact: | Zuzana Lena Ansorgova <zuansorg> |
Priority: | medium | ||
Version: | 6.10.0 | CC: | ahumbe, dsinglet, gisoni, lstejska, msviriko, rlavi, shwsingh, zuansorg |
Target Milestone: | 6.15.0 | Keywords: | EasyFix, FutureFeature, Triaged, UserExperience |
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
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.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2024-04-23 17:10:51 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Kshitij
2021-08-17 15:58:58 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. 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 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 Based upon further review from the engineering team, this bugzilla will not be closed at this time. Created redmine issue https://projects.theforeman.org/issues/36295 from this bug Created redmine issue https://projects.theforeman.org/issues/36312 from this bug Bulk setting Target Milestone = 6.15.0 where sat-6.15.0+ is set. 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 |