Project

General

Profile

Bug #1477

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

Added by Alexander Chuzhoy over 7 years ago. Updated about 1 year ago.

Status:
Closed
Priority:
Normal
Category:
-
Target version:
Difficulty:
easy
Triaged:
Bugzilla link:
Team Backlog:
Fixed in Releases:
Found in Releases:

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

Related to Foreman - Bug #12342: Puppet classes disapear when changing environment after cloning hostgroupClosed2015-10-28
Has duplicate Foreman - Bug #12421: Moving a hostgroup between environments loses associated puppet classesDuplicate2015-11-09

Associated revisions

Revision 8b98d8e0 (diff)
Added by Ondřej Pražák almost 4 years ago

Fixes #1477 - Hostgroup no longer looses puppet classes when environment changed during hostgroup editing

History

#1 Updated by Ohad Levy over 7 years ago

  • Assignee set to Ohad Levy
  • Target version set to 1.0

#2 Updated by Ohad Levy over 7 years ago

  • Difficulty set to easy

#3 Updated by Ohad Levy about 7 years ago

  • Target version deleted (1.0)

#4 Updated by Ohad Levy about 7 years ago

  • Assignee deleted (Ohad Levy)

#5 Updated by Benjamin Papillon about 6 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

#6 Updated by Dominic Cleal over 5 years ago

  • Description updated (diff)
  • Status changed from Closed to New

#7 Updated by Dominic Cleal over 5 years ago

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

#8 Updated by Jon McKenzie over 5 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.

#9 Updated by Jon McKenzie over 5 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.

#10 Updated by The Foreman Bot about 4 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/2582 added

#11 Updated by Dominic Cleal almost 4 years ago

  • Assignee set to Ondřej Pražák
  • Legacy Backlogs Release (now unused) set to 63

#12 Updated by Ondřej Pražák almost 4 years ago

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

#13 Updated by Dominic Cleal almost 4 years ago

  • Related to Bug #12342: Puppet classes disapear when changing environment after cloning hostgroup added

#14 Updated by Dominic Cleal almost 4 years ago

  • Has duplicate Bug #12421: Moving a hostgroup between environments loses associated puppet classes added

Also available in: Atom PDF