Bug 1992283
Summary: | [RFE] In Satellite WebUI -> Hosts -> Register Host page, the mandatory fields mentioned within Advanced tab should be moved to General tab | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Jayant Bhatia <jbhatia> |
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, aruzicka, bangelic, dsinglet, gtalreja, lstejska, mhulan, nalfassi, pcreech, rlavi, zuansorg |
Target Milestone: | 6.14.0 | Keywords: | FutureFeature, Triaged, UserExperience |
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | rubygem-foreman_remote_execution-10.0.0 | Doc Type: | Bug Fix |
Doc Text: |
.Optional fields in the Host Registration form no longer marked as mandatory
Previously, in the {ProjectWebUI}, the following fields in *Hosts* > *Register Host* were marked with an asterisk as required: *Organization*, *Location*, *Setup REX*, *Setup Insights*, *Install packages*, *Token life time*, and *REX pull mode*.
This fix removes the asterisk mark, because those fields are optional, and moves the mandatory *Activation Keys* field from the *Advanced* tab to the *General* tab.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2023-11-08 14:17:34 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
Jayant Bhatia
2021-08-10 21:00:27 UTC
Hi the only mandatory fields are 'Activation keys' and 'token lifetime', other fields are not mandatory. * 'Activation keys' are in advanced tab because they can be inherited from selected host group (in general tab), so user don't have to fill the 'Activation keys' field * 'token lifetime' have default value 4 hours So theoretically users have to select only host group and they are ready to go. However you are not first person suggesting to move 'activation keys' back to general tab, plus this could be useful for users who don't use host groups (if there are any?). @mhulan I don't have any strong opinions here, but this is not for the first time someone reported it, some of users (from QA & support) find this change confusing. --- DEV Note: The code change would be really simple and practically risk-free when getting it into the 6.10 Yeah, we discussed this with Ashish as well. I'd prefer to keep activation key in the advanced tab because we should encourage people to prefer the host group to automate the registration. Host group can be the only thing that user selects. The activation key has relations to the LCE that user can override and it's good to have these two next to each other. But we don't want to overwhelm user in the General tab with too many fields. I'd keep this BZ open for a while and if we see too many cases being attached despite we recommend leveraging host groups, we can reconsider. Hello, Thank you for your reply. Currently setting 'Host group' is not mandatory, hence there is a strong possibility that customer do not select 'Host group' and just click on 'Generate' without looking into the 'Advanced' tab, and then go back to 'Advanced' tab and set 'Activation Key', then click on 'generate' again. If we are going to make 'Host group' mandatory field in 6.10 GA, then I think we can close out this BugZilla. But if 'Host group' will not be a mandatory field in 6.10 GA, I will strongly suggest to move at least the 'Activation Key' field within 'General' tab. Well the host group should never be mandatory, just highly recommended. User can still fill in the form completely without using the host group. It's the same logic as in provisioning form. If you chose the host group in the first tab, it fills in the rest of the form in other tabs. If user does not want to use host groups, they need to go through all the fields. Note that the activation key in the provisioning form is in one of the last tabs called Parameters. Let's see what the triage team thinks, moving the field should be an easy and safe fix for 6.10 if that's preferred. 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. 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. Created redmine issue https://projects.theforeman.org/issues/36307 from this bug Created redmine issue https://projects.theforeman.org/issues/36308 from this bug Moving this bug to POST for triage into Satellite since the upstream issues https://projects.theforeman.org/issues/36307, https://projects.theforeman.org/issues/36308 have been resolved. Added a fully reviewed Release Note. Verified. Tested on Satellite 6.14.0 Snap 1.0 Steps: 1. Navigate to Hosts -> Register Host 2. Check required and non-required fields in host registration form Observations: Optional fields in the Host Registration form no longer marked as mandatory. Previously, these fields in host registration form were marked with an asterisk as required: Organization, Location, Setup REX, Setup Insights, Token life time, and REX pull mode, now this fix removes the asterisk mark which makes these fields optional. And, Activation key field is alreadt been moved to General tab in BZ 2059829 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.14 security and bug fix update), 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-2023:6818 |