Description of problem:

After updating the content view by added a repository or by promoting a different version to a lifecycle environment on the Satellite, it is expected that the entitlement certificate for the host should change for all hosts with said lifecycle and content view set. This is not happening.

How reproducible:

Every time

Is this issue a regression from an earlier version:

Yes

Steps to Reproduce:

1. Register a system to Satellite

2. Create a content view with 1 repository in it and publish

3. Assign the registered host to this content view version and lifecycle

4. Update the content view adding another repository and publish

5. Perform a `subscription-manager refresh` on the client to have the client call to the Satellite to confirm its certificates

Actual behavior:
The old certificate is being presented to the client as opposed to the new certificate with the new content view version

Expected behavior:
The new entitlement certificate should be offered to the client when calling the Satellite's /rhsm/consumer/<UUID>/certificates/serials

Business Impact / Additional info:

This prevents rhsmcertd and custom workflows from adopting content view changes made on the Satellite to the client on their next check-in.

A workaround for this is to use the command `subscription-manger refresh --force` to tell the Satellite to regenerate the certificates based on the client's profile. In which the changes for the CV are adopted.