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 1001739 - Support CRL propagation to Capsules
Summary: Support CRL propagation to Capsules
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Pulp
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
: 1145708 (view as bug list)
Depends On: 1145708
Blocks: sat6-pulp-future
TreeView+ depends on / blocked
 
Reported: 2013-08-27 15:47 UTC by Justin Sherrill
Modified: 2021-04-06 18:27 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
: 1145708 (view as bug list)
Environment:
Last Closed: 2015-03-20 17:33:53 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Pulp Redmine 253 0 Normal CLOSED - WONTFIX Support CRL propagation to Capsules Never

Description Justin Sherrill 2013-08-27 15:47:21 UTC 
Description of problem:

Currently the CRL from the pulp server is not propagated to the nodes.  Katello needs this so that systems who have had their certificates revoked on the server will also have them revoked on the nodes
Comment 1 Jeff Ortel 2014-05-07 15:45:43 UTC 
The interval in which CRLs expire and need to be updated seems different than the interval for syncing nodes.  I don't think we want users doing a node sync just to keep their CRLs updated.  IMHO, that should be a different mechanism.  This bug should not be worked until this is resolved.
Comment 2 Brian Bouterse 2014-08-25 18:59:21 UTC 
With 2.4.0, Pulp implements CRL revocation using the webserver's CRL support which typically is Apache. Users who want to apply CRLs to Pulp servers or Nodes will need to distribute the CRLs outside of Pulp.
Comment 5 Michael Hrivnak 2015-03-03 19:27:08 UTC 
CRLs are currently enforced by apache directly, without involvement from pulp. Pulp does not propagate apache configs to nodes, so this would be likely be in the domain of config management.

Put another way, sat6 should have apache configured to use CRLs from *somewhere*, but I don't know what that source is. Whatever the source is, making it available on capsules is outside of pulp's scope.
Comment 7 Brian Bouterse 2015-03-05 21:46:02 UTC 
*** Bug 1145708 has been marked as a duplicate of this bug. ***
Comment 8 Brian Bouterse 2015-03-20 17:00:39 UTC 
The Pulp upstream bug status is at CLOSED - WONTFIX. Updating the external tracker on this bug.
Comment 9 Brian Bouterse 2015-03-20 17:00:40 UTC 
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
Comment 10 Mike McCune 2015-03-20 17:33:53 UTC 
This isn't going to be implemented in any time in the near future. The current situation is an acceptable tradeoff.

Clients will continue to get content until their subscriptions are refreshed.
Note You need to log in before you can comment on or make changes to this bug.