Bug #2231: Hostgroup deletion follows adopt policy

[dLobatog]

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

http://projects.theforeman.org/issues/2231

[ohadlevy]

which version of the ancestry gem is required? it does not work on my local 1.3 version

gems/ancestry-1.3.0/lib/ancestry/class_methods.rb:26:in `orphan_strategy=': Invalid orphan strategy,
 valid ones are :rootify, :restrict and :destroy. (Ancestry::AncestryException)

[dLobatog]

That caused some problems in here as well, if you check the README for the gem you have installed is not actually 1.3.0 but something older, I thought it was our problem but apparently the only way to get around it is to get the gem from the repo itself not Rubygems.

gem "ancestry", :git => "git://github.com/stefankroes/ancestry.git" on the Gemfile should do it

[ohadlevy]

I see...then we should wait for a new release of the gem... Maybe we could
ping the author to release a new version?

[ohadlevy]

[test]

[theforeman-bot]

Test Results: FAILURE (http://ci.theforeman.org/job/test_develop_pull_request/42/)

[theforeman-bot]

Evaluated up to 8215371

[ohadlevy]

closing for now, as the gem is not released, see stefankroes/ancestry#123.

once ready, I'll be more than happy to merge