Project

General

Profile

Bug #4736

org edit ui has unselectable environment

Added by Thomas McKay about 5 years ago. Updated 11 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Web Interface
Target version:
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:

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.

orgenv.png View orgenv.png 32.4 KB Thomas McKay, 03/20/2014 01:26 AM
Orgenv

Associated revisions

Revision 9f3cad15 (diff)
Added by Joseph Magen almost 5 years ago

fixes #4736 - organization edit ui has unselectable environment

Revision fcc83555 (diff)
Added by Joseph Magen almost 5 years ago

fixes #4736 - organization edit ui has unselectable environment

(cherry picked from commit 9f3cad157f366904c1e145d19bf35e8cd0282cf0)

History

#1 Updated by Mike McCune about 5 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 ...

#2 Updated by Ohad Levy about 5 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.

#3 Updated by Joseph Magen about 5 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.

#4 Updated by Joseph Magen about 5 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Joseph Magen

#5 Updated by Joseph Magen about 5 years ago

  • Target version set to 1.8.4

#6 Updated by Dmitri Dolguikh about 5 years ago

  • Target version changed from 1.8.4 to 1.8.3

#7 Updated by Dmitri Dolguikh about 5 years ago

  • Target version changed from 1.8.3 to 1.8.4

#8 Updated by Dmitri Dolguikh about 5 years ago

  • Target version changed from 1.8.4 to 1.8.3

#9 Updated by Thomas McKay about 5 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).

#10 Updated by Thomas McKay about 5 years ago

I retract my "unusable" statement about the UI: It has a "Fix Mismatches" button which did the reassociation.

#11 Updated by Dmitri Dolguikh about 5 years ago

  • Target version changed from 1.8.3 to 1.8.2

#12 Updated by Thomas McKay almost 5 years ago

  • Bugzilla link set to https://bugzilla.redhat.com/show_bug.cgi?id=1103870

#13 Updated by Dmitri Dolguikh almost 5 years ago

  • Target version changed from 1.8.2 to 1.8.1

#14 Updated by Joseph Magen almost 5 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#15 Updated by Dominic Cleal almost 5 years ago

  • Legacy Backlogs Release (now unused) set to 18

#16 Updated by Checheta Yan over 3 years ago

Also available in: Atom PDF