Bug #1477: Whenever you switch environment for a host group - the host group looses its puppet classes. - Foreman

Custom queries

3.10.0 release DONE
3.10.0 release TODO
3.11.0 release DONE
3.11.0 release TODO
3.8.1 release DONE
3.8.1 release TODO
3.9.2 release DONE
3.9.2 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 #1477

closed

Whenever you switch environment for a host group - the host group looses its puppet classes.

Added by Alexander Chuzhoy over 12 years ago. Updated almost 6 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Ondřej Pražák

Category:

Target version:

1.10.0

Difficulty:

easy

Triaged:

Bugzilla link:

Pull request:

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

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

Whenever you switch environment for a host group - the host group looses its puppet classes. There's no warning and basically someone needs to memorize all the classes the host group had assigned.

I'd expect a warning message notifying about such a major impact, or memorizing the list of already assigned classes somewhere for easy retrieval.

Related issues 2 (0 open — 2 closed)

	Related to Foreman - Bug #12342: Puppet classes disapear when changing environment after cloning hostgroup	Closed	Tom Caspy	10/28/2015			Actions
	Has duplicate Foreman - Bug #12421: Moving a hostgroup between environments loses associated puppet classes	Duplicate		11/09/2015			Actions

Issue # Delay: days Cancel

History
Notes
Property changes
Associated revisions

Actions

Copy link

Updated by Ohad Levy about 12 years ago

Assignee set to Ohad Levy
Target version set to 1.0

Actions

Copy link

Updated by Ohad Levy almost 12 years ago

Difficulty set to easy

Actions

Copy link

Updated by Ohad Levy almost 12 years ago

Target version deleted (~~1.0~~)

Actions

Copy link

Updated by Ohad Levy almost 12 years ago

Assignee deleted (~~Ohad Levy~~)

Actions

Copy link

Updated by Benjamin Papillon almost 11 years ago

Status changed from New to Closed

This bug has been fixed in 1.1 at least and you now have an option to manage mismatches between environments. You can see #2124 for more informations

Actions

Copy link

Updated by Dominic Cleal over 10 years ago

Description updated (diff)
Status changed from Closed to New

Actions

Copy link

Updated by Dominic Cleal over 10 years ago

Re-opening as it sounds like the UI issue may still exist, even though the mismatch problem was fixed.

Actions

Copy link

Updated by Jon McKenzie about 10 years ago

Any update on this issue? This problem is pretty devastating to the use of hostgroups for class management.

We're currently using Foreman 1.4.2 on CentOS 6.

Actions

Copy link

Updated by Jon McKenzie about 10 years ago

By the way, there seem to be two workarounds for this issue:

Use hammer (or the API) to update the hostgroup, not the UI
If updating via the UI, change the environment in the dropdown (which will remove the classes from the Puppet Classes tab), and then refresh the page. The environment will remain the same, but if you navigate back to the Puppet Classes tab, the original classes will reappear. Click Submit.

So this does seem to be isolated to the UI.

Actions

Copy link

#10