Bug #4736: org edit ui has unselectable environment - Foreman

Custom queries

3.11.5 release DONE
3.11.5 release TODO
3.12.2 release DONE
3.12.2 release TODO
3.13.0 release DONE
3.13.0 release TODO
All bugs by votes
All issues closed in the last 3 weeks
Easy and Trivial Issues
Easy Issues (only)
Foreman - new open issues in last 10 days
Good first issues - Foreman core
high prio open bugs
Host registration [open]
Mine
My issues closed in the last 3 weeks
old bugs
Open with target version set (aka blockers)
registration
taken-none
Team Atlas untriaged bugs
templates
Trivial Issues
Untriaged and opened in the past two weeks

Actions

Copy link

Bug #4736

closed

org edit ui has unselectable environment

Added by Thomas McKay over 10 years ago. Updated over 6 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Joseph Magen

Category:

Web Interface

Target version:

1.5.2

Difficulty:

Triaged:

Bugzilla link:

1103870

Pull request:

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

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

orgenv.png

View orgenv.png

32.4 KB

Thomas McKay, 03/20/2014 01:26 AM

History
Notes
Property changes
Associated revisions

Actions

Copy link

Updated by Mike McCune over 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 ...

Actions

Copy link

Updated by Ohad Levy over 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.

Actions

Copy link

Updated by Joseph Magen over 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.

Actions

Copy link

Updated by Joseph Magen over 10 years ago

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

https://github.com/theforeman/foreman/pull/1347

Actions

Copy link

Updated by Joseph Magen over 10 years ago

Target version set to 1.8.4

Actions

Copy link

Updated by Anonymous over 10 years ago

Target version changed from 1.8.4 to 1.8.3

Actions

Copy link

Updated by Anonymous over 10 years ago

Target version changed from 1.8.3 to 1.8.4

Actions

Copy link

Updated by Anonymous over 10 years ago

Target version changed from 1.8.4 to 1.8.3

Actions

Copy link

Updated by Thomas McKay over 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).

Actions

Copy link

#10