Bug #2231
closed
Hostgroup deletion follows adoption policy
Added by Daniel Lobato Garcia about 12 years ago.
Updated almost 7 years ago.
Description
Given a hostgroup hierarchy like:
/base
/base/test01
/base/test01/test02
/base/test01/test03
Currently, if /base/test01 is deleted, it leads to a clunky configuration
/base
/test02
/test03
This change makes a hostgroup adopt orphans so that removing test01 would lead to:
/base
/base/test02
/base/test03
https://github.com/theforeman/foreman/pull/419
- Description updated (diff)
Given a hostgroup hierarchy like:
/base
/base/test01
/base/test01/test02
/base/test01/test03
Currently, if /base/test01 is deleted, it leads to a clunky configuration
/base
/test02
/test03
In addition to that, it might lead to having several hostgroups with the same name:
/base
/test/base
If test is deleted, we would end up with
/base
/base
This change restricts hostgroup deletion only to hostgroups who have no children so that the problems above can be avoided.
https://github.com/theforeman/foreman/pull/924
- Status changed from New to Ready For Testing
- Target version set to 1.4.0
- Target version deleted (
1.4.0)
- Target version set to 1.15.0
- Target version changed from 1.15.0 to 1.10.0
- Target version changed from 1.10.0 to 1.9.3
- Target version changed from 1.9.3 to 1.9.2
- Assignee set to Daniel Lobato Garcia
- Translation missing: en.field_release set to 2
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by Anonymous