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:
When updating a host via hammer, it should validate if the new attribute belongs to the same taxonomy (organization/location). Example:
Host A in Location Loc1 that is associated with Domain D1 (only). Via hammer, I am able to change the Host's domain to D2 without a problem.
This creates issues when trying to update the host later on - such updates fail due to invalid domain/puppet environment/operating system details/.. .
Please add either warning when selecting a domain/puppet environment outside the taxonomy, or rather dont allow it at all.
(not sure if this is hammer or foreman bug. Since the change is not allowed in WebUI, hammer is in suspicion more than foreman)
Version-Release number of selected component (if applicable):
Sat6.1.5
rubygem-hammer_cli-0.1.4.13-1.el7sat.noarch
rubygem-hammer_cli_foreman-0.1.4.14-1.el7sat.noarch
How reproducible:
100%
Steps to Reproduce:
1. Have 2 domains d1.example.com and d2.example.com
2. Have a location Loc1 associated with d1.example.com only
3. Have a Host in Loc1 with domain d1
4. hammer -u admin -p password host update --domain "d2.example.com" --name "myhost.d1.example.com"
Actual results:
4. passes and the host has a domain not listed in it's Location.
Any attempt to update the host via WebUI fails due to domain mismatch.
Expected results:
4. should not pass, further unrelated actions in WebUI or hammer should be possible.
Additional info:
Note again the example above is just one specific scenario with domains. The bugzilla is meant to be more generic - any change of a parameter associated with taxonomy must be verified wrt. the taxonomy before committing it.
Still reproducible with Sat 6.2.5 and latest upstream. This is not specific to domains but all taxable resources therefore I'm moving to Organizations and Locations component. We need some more generic solution, maybe we could use parameter filters layer that was introduced with strong params.
If this happens, there's a way to find all such mismatches. Navigate to edit page of organization of the host in WEB UI, you should see resources that needs to be assigned to this organization marked by red color with error message "you cannot remove domains that are used by hosts or inherited."
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.