Bug #2946
open
Removing a class doesn't remove it from hostgroup that own it
Added by ohad basan over 11 years ago.
Updated over 11 years ago.
Category:
Puppet integration
|
|
Description
I noticed a problem on my foreman 1.1 instance.
I performed a class rename and afterwards I had to remove the deleted class from all the hostgroups that included it and readd the new class.
even if foreman does not understand that the class rename.
it should, in my opinion, remove the deleted class automatically from all the hostgroups that own it
- Category set to Puppet integration
- Status changed from New to Feedback
- Priority changed from High to Normal
Did you re-import the classes after the rename?
What should happen is on the import page, you'll be given a list of modules that have changed and can tick the button next to the one that was removed or updated. When you do this, you will see the puppet class be removed from the puppet classes list, which should also cause it to be removed from hosts and/or host groups.
If you don't re-import and tick the box, then the module will remain in the system.
I did "import" and the system saw that the puppet class was removed, yet the hostgroups were not updated.
- Status changed from Feedback to New
Also available in: Atom
PDF
Updated by 
Updated by