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 1814330 - Manifest refresh does not import new CDN certificates into Pulp
Summary: Manifest refresh does not import new CDN certificates into Pulp
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Repositories
Version: Unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Cole Higgins
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-17 16:44 UTC by Justin Sherrill
Modified: 2023-10-06 19:26 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-18 19:44:22 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Justin Sherrill 2020-03-17 16:44:30 UTC 
This bug was initially created as a copy of Bug #1688973

I am copying this bug because: 

There have been reports of this happening again, but no more details (such as task exports) exist to help debug the situation. 


1) On a Satellite with an expired set of subscriptions, try and sync repos from the CDN and ensure they fail. You need expired, non-valid subscriptions where you get Permission Denied errors syncing. 

2) Find the x509 certs stored in one of the Pulp repositories, substitute the repo-id of say.. the RHEL7 Server repo

#  curl -k -u admin:************ https://localhost/pulp/api/v2/repositories/33fb2576-e5f7-4946-944d-66e0593271aa/?details=true  | json_reformat 

3) Copy the ssl_client* fields to a text file for future reference

4) Download an updated un-expired manifest with new subscriptions

5) Import into Satellite 6

6) Try to sync repos again, note that you *still* get Permission Denied errors from the CDN.

7) Repeat step (2) and (3) and note that there is still the old expired ssl_certs in the pulp feed ssl certs.

WORKAROUND:

Run this foreman-rake task to refresh the certs out of Candlepin:

# LIFECYCLE_ENVIRONMENT=Library foreman-rake katello:refresh_pulp_repo_details
Comment 3 Justin Sherrill 2020-03-17 16:49:35 UTC 
To assist in further debugging this issue, we need a task export showing the manifest refresh.
Comment 4 Mike McCune 2022-01-28 22:30:40 UTC 
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team. Thank you.
Comment 5 Mike McCune 2022-03-18 19:44:22 UTC 
Thank you for your interest in Red Hat Satellite. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this feel free to contact your Red Hat Account Team. Thank you.
Note You need to log in before you can comment on or make changes to this bug.