Description of problem:

If a host is registered to specific Location and Lifecycle Environment (LCE) and when this LCE is added to Capsule then this specific Location is also getting assigned to Capsule. This Location cannot be removed from the Capsule without removing LCE, which is not desirable.

It appears that these are any locations that have existing hosts assigned to them and have a content view associated with one of the added lifecycle environments.

How reproducible:

Easily

Is this issue a regression from an earlier version:

• No

Steps to Reproduce:

1. Create a Lifecycle environment and location. Register a host with this new location and Lifecycle environment.
2. Now deploy a fresh Capsule or use a Capsule which do not have this new Lifecycle environment assigned and add this new Lifecycle environment to the Capsule server.

Actual behavior:

• Location gets auto-assigned to Capsule server which is not even desired.

Expected behavior:

• Should be able to assign only desired location to Capsule server.

Business Impact / Additional info: