Bug #4736
closed
org edit ui has unselectable environment
Description
After creating puppet environments through the API, then hosts using those environments, visiting the org UI shows a red Environments and the message "Select this since it belongs to a host". However, it is not selectable.
Files
Updated by Mike McCune about 10 years ago
I think that is working as intended. You can't modify the taxonomy of the Environment if it is in use. You have to remove those hosts from the Environment first. Someone else can correct me if I'm wrong ...
Updated by Ohad Levy about 10 years ago
- Assignee set to Joseph Magen
I think its a bug, as if its in used, the selection should be disabled on the left side, vs the right side.
Updated by Joseph Magen about 10 years ago
- Assignee deleted (
Joseph Magen)
When a KT environment is created, why is it also inserted in Puppet Environments? I thought they were different. I'm confused how Foreman is classifying the KT environments as "used". It is only used for the environment is the same a host's environment field.
Updated by Joseph Magen about 10 years ago
- Status changed from New to Ready For Testing
- Assignee set to Joseph Magen
Updated by Anonymous almost 10 years ago
- Target version changed from 1.8.4 to 1.8.3
Updated by Anonymous almost 10 years ago
- Target version changed from 1.8.3 to 1.8.4
Updated by Anonymous almost 10 years ago
- Target version changed from 1.8.4 to 1.8.3
Updated by Thomas McKay almost 10 years ago
This is still a blocker for me. It impacts both organization and location UI pages.
If the user somehow manages to get a Location removed from an Organization (in my case it was via api) then the tool effectively becomes unusable. The UI shows the error but does not allow me to correct it (ie. in the Location UI the red Organization cannot be selected to move back into the "Selected Items" table. The Organization is red and a message of "You cannot remove organizations that are used by hosts or inherited." as if I had just made the change when visiting the page (rather than the relationship getting messed up earlier).
Updated by Thomas McKay almost 10 years ago
I retract my "unusable" statement about the UI: It has a "Fix Mismatches" button which did the reassociation.
Updated by Anonymous almost 10 years ago
- Target version changed from 1.8.3 to 1.8.2
Updated by Thomas McKay almost 10 years ago
- Bugzilla link set to https://bugzilla.redhat.com/show_bug.cgi?id=1103870
Updated by Anonymous almost 10 years ago
- Target version changed from 1.8.2 to 1.8.1
Updated by Joseph Magen almost 10 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 9f3cad157f366904c1e145d19bf35e8cd0282cf0.
Updated by Dominic Cleal almost 10 years ago
- translation missing: en.field_release set to 18
Updated by Checheta Yan