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.

Bug 2131415

Summary: After changing Satellite hostname Capsules still have packages referring to old hostname
Product: Red Hat Satellite Reporter: Paul Dudley <pdudley>
Component: InstallationAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED MIGRATED QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.11.2CC: ahumbe, ehelms
Target Milestone: UnspecifiedKeywords: MigratedToJIRA, Triaged, WorkAround
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-06-06 12:34:55 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Paul Dudley 2022-09-30 23:39:22 UTC 
On Satellite-capsule 6.11.2 rhel 8, receive this error when a content host registered to the Capsule attempts to install a package:
~~~
Sep 27 12:27:34 oldname pulpcore-content[523678]: ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: Hostname mismatch, certificate is not valid for 'oldname.example.com'. (_ssl.c:1131)
~~~

Looking into this, we find that all remotes on the Capsules are correct - they reference the correct new name:
~~~
From Sat to Cap:
- # curl --cert /etc/pki/katello/certs/pulp-client.crt --key /etc/pki/katello/private/pulp-client.key   https://capsule.example.com/pulp/api/v3/remotes/rpm/rpm/ | python -m json.tool | grep \"url\"\:
            "url": "https://newname.example.com/pulp/content/ghost/prod/rhel9/content/dist/rhel9/9/x86_64/appstream/os/"
            "url": "https://newname.example.com/pulp/content/ghost/prod/rhel9/content/dist/rhel9/9/x86_64/baseos/os/"
            "url": "https://newname.example.com/pulp/content/ghost/prod/rhel9/content/dist/layered/rhel9/x86_64/sat-client/6/os/"
            "url": "https://newname.example.com/pulp/content/ghost/prod/rhel8/content/dist/rhel8/8/x86_64/appstream/os/"
            "url": "https://newname.example.com/pulp/content/ghost/prod/rhel8/content/dist/rhel8/8/x86_64/baseos/os/"
            "url": "https://newname.example.com/pulp/content/ghost/prod/rhel8/content/dist/layered/rhel8/x86_64/sat-tools/6.10/os/"
            "url": "https://newname.example.com/pulp/content/ghost/prod/SmallCV/content/dist/rhel/server/7/7Server/x86_64/sat-tools/6.6/os/"
...

- # curl --cert /etc/pki/katello/certs/pulp-client.crt --key /etc/pki/katello/private/pulp-client.key   https://capsule.example.com/pulp/api/v3/remotes/rpm/rpm/ | python -m json.tool | grep \"url\"\: | grep oldname | wc
      0       0       0 <-- no results for the old Satellite name
...

- # curl --cert /etc/pki/katello/certs/pulp-client.crt --key /etc/pki/katello/private/pulp-client.key   https://capsule.example.com/pulp/api/v3/remotes/rpm/rpm/ | python -m json.tool | grep \"url\"\: | grep newname | wc
      7      14     930 <-- all remotes have new Satellite name
~~~

However, if we look at the remoteartifacts, plenty of them still reference the old Satellite name:
~~~
On Capsule:
- # su - postgres -c "psql pulpcore -c \"select url from core_remoteartifact;\"" | grep oldname.example.com | wc
some number (not 0)

- # su - postgres -c "psql pulpcore -c \"select url from core_remoteartifact;\"" | grep newname.example.com | wc
some number (also not 0)
~~~

It looks like after changing the Satellite hostame, and subsequent needed changes on the Capsules, like successful syncs, the url on remotes themselves are changed as we expect, but urls on remoteartifacts are not updated. This means that any content previously synced on the Capsule(s) before the change will look for the wrong Satellite name to download the rpm from.

Expectation here would be that after changing the Satellite hostname, all necessary changes are made on Capsule side to change all content to reference the new Satellite name.

To reproduce:
- Install Satellite and Capsule
- Add content to Satellite, sync to Capsule
- Change Satellite hostname
- Sync Capsule to find that remotes are all updated correctly
- Add more content to Satellite, sync that content to both Sat and Cap
- Check remote artifacts to find that there are references to both the old and new Satellite name
Comment 1 Paul Dudley 2022-09-30 23:42:35 UTC 
To update remote artifacts You can run this (assuming rhel8):
~~~
On Capsule:
- # sudo -u pulp PULP_SETTINGS='/etc/pulp/settings.py' DJANGO_SETTINGS_MODULE='pulpcore.app.settings' pulpcore-manager dbshell
pulpcore=> BEGIN;
pulpcore=> update "core_remoteartifact"
pulpcore=> set url = REPLACE(url, 'https://oldname.example.com','https://newname.example.com');
- verified old name no longer found - if problems, ROLLBACK; -
COMMIT;
~~~
Comment 3 Eric Helms 2024-06-06 12:34:55 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.