Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
Updating Environment / Content view from Hosts -> All Hosts page doesnt reflect on the client

Version-Release number of selected component (if applicable):
satellite-6.3.1-3.el7sat.noarch

How reproducible:
Always

Steps to Reproduce:
1. Navigate to Satellite UI -> Hosts -> All Hosts -> `Edit` a client.
2. Update Lifecycle Environment and Content View. Click Submit.
3. Login to the client which just got updated.
4. `subscription-manager identity` reflects the Lifecycle Environment and Content View. I tried `subscription-manager refresh`, it didn't help.

Actual results:
As said in Step 4 above.

Expected results:
The client should reflect the changes made in Lifecycle Environment and Content View on the Satellite server side.

Additional info:

*** This bug has been marked as a duplicate of bug 1564740 ***