Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1228365
Description of problem:

A had a host IBM_A with a hostgroup CENTOS. This hostgroup had its location set to "Default Location". When I wanted to edit the hostgroup and change the location, it wasn't possible - it was locked because there was a host that had the hostgroup assigned.
This makes sense, so far so good.

However, in the database, the hostgroup had no location set.

When I edited the IBM_A host and unset the hostgroup, the hostgroup's location got unlocked and unset. It was not "Default Location" anymore.

Is this correct? How is it possible, that the hostgroup didn't have a location set in the DB while showing something completely different to the user in UI?

We run into this problem during CFME/Sat6 integration testing. We cannot provision into a hostgroup with no location but at the same time it all looks fine in the UI which makes it that much worse...a

Version-Release number of selected component (if applicable):
6.0.8

How reproducible:
-

Steps to Reproduce:
-

Actual results:
Discrepancy between UI and DB info.

Expected results:
Both UI and DB should give us the same data.

Additional info:
-