Description of problem:

• Force registering from a Capsule to the Satellite using global registration template fails with HTTP error code 422: Unprocessable Entity error.

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

• satellite-6.14.0-3.el8sat.noarch

How reproducible:

• Only when the capsule registered to originally does not have the Lifecycle Environments associated.

Steps to Reproduce:

1. Deploy a Capsule

2. Capsule should not be associated with any lifecycles.

3. Register client to the Capsule using global registration template.

The registration will report the following message but will be successful even though yum repositories reports 404.

~~~
Validation failed: Content view environment content facets is invalid (HTTP error code 422: Unprocessable Entity)
~~~

~~~
8 | client.example.com | RedHat 8.7 | | 10.10.180.1 | 92:fa:8c:47:dc:b9 | Warning | |
~~~

~~~
Errors during downloading metadata for repository 'rhel-8-for-x86_64-baseos-rpms':

• Status code: 404 for https://capsule.example.com/pulp/content/RedHat/Library/content/dist/rhel8/8/x86_64/baseos/os/repodata/repomd.xml (IP: 10.10.125.2)
  Error: Failed to download metadata for repo 'rhel-8-for-x86_64-baseos-rpms': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
  ~~~

4. Now, try to force register the client to Satellite using global registration template by using the Force option.

Actual results:

• The script unregisters the client successfully.

~~~
Unregistering from: capsule.example.com:443/rhsm
System has been unregistered.
~~~

After this, it fails with following message.

~~~
Validation failed: Host client.example.com: Cannot add content view environment to content facet. The host's content source 'capsule.example.com' does not sync lifecycle environment 'Library'. (HTTP error code 422: Unprocessable Entity)
~~~

• Client can only be registered after removing the profile from the Satellite manually.

Expected results:

• Client should be re-registered to the Satellite.

Additional info:

• This behavior is not present on 6.13. Force option can be used to register from Capsule to Satellite on 6.13.