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.
DescriptionJustin 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
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.
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.
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.
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.