Bug 1297468

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.