Red Hat Bugzilla – Bug 1273651
[RFE] ask user to confirm when updating location or org for multiple hosts, instead of 'no-op' option
Last modified: 2017-12-05 08:42:44 EST
1. Proposed title of this feature request
- When updating location or org for multiple hosts, there is an unnecessary 'no-op' option
2. Who is the customer behind the request?
Account: USAA / Account # 417106
TAM customer: Yes
SRM customer: No
3. What is the nature and description of the request?
- Customer is having a concerns regarding the default option "Fail on Mismatch" while we are updating the Location or Organisation in the All Hosts Page.
- Customer would like to change the behavior to ask the user to confirm the update.
4. Why does the customer need this? (List the business requirements here)
- Customer is facing issues if he accidentally left it in the default option itself.
5. How would the customer like to achieve this? (List the functional requirements here)
- In customer words "A better solution would be to ask a user to confirm the update to the Organisation or Location."
6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
- Instead of updating with the default option, Satellite server should request for the confirmation before updating.
7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
9. Is the sales team involved in this request and do they have any additional input?
10. List any affected packages or components.
- Not known yet
11. Would the customer be able to assist in testing this functionality if implemented?
The "Fail on mismatch" option is not a no-op. In case all of the modified hosts' resources (e.g. domains, subnets, templates etc.) belong to the new location, "Fail on mismatch" will update the hosts to the new location. The action will only fail in case one of these attributes does not belong to the new location - this is on purpose, so that hosts will not have resources that do not belong to their location or organization. This is set as the default to prevent unexpected consequences of changing a host's location.
The other option, "fix location on mismatch", will add the new location to any host resources that are not currently assigned to that location. This has to be manually chosen, so that the user actively acknowledges that the change may have effect on other resources as well.
Closing this issues as NOTABUG, if I misunderstood the request please reopen it and provide further information.