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.
Verified on Satellite 6.10.2, snap 1.
Steps to Test:
1. Add the following line to /etc/candlepin/candlepin.conf to set the CRLUpdateJob to run every 3 minutes:
candlepin.async.jobs.CRLUpdateJob.schedule=0 0/3 * * * ?
2. Restart the tomcat service:
# systemctl restart tomcat
3. Register a host to Satellite.
4. Check the time when /var/lib/candlepin/candlepin-crl.crl was last updated:
5. Follow the Candlepin log and wait for the CRLUpdateJob to run.
6. Between two runs of the job, attach a subscription to the host registered in step 3, then immediately remove that subscription.
7. After the job runs again, check the last modified time of the CRL file again:
Expected Results:
On a Satellite 6.10.2 that was upgraded from Satellite 6.9, the CRL file is not updated. On a Satellite 6.10.2 that was freshly installed, the file is never created.
Actual Results:
On a Satellite 6.10.2 that was upgraded from Satellite 6.9, the CRL file is not updated. On a Satellite 6.10.2 that was freshly installed, the file is never created.
In both cases, the job run results in an error in /var/log/candlepin/candlepin.log:
```
2022-01-04 15:00:00,199 [thread=QuartzScheduler_Worker-4] [=, org=, csid=] INFO org.candlepin.async.JobManager - Job queued: AsyncJobStatus [id: 8a8182757e26a962017e26ad52b40016, name: CRLUpdateJob, key: CRLUpdateJob, state: QUEUED]
2022-01-04 15:00:00,284 [thread=Thread-5 (ActiveMQ-client-global-threads)] [job=8a8182757e26a962017e26ad52b40016, job_key=CRLUpdateJob, org=, csid=] ERROR org.candlepin.async.JobManager - No registered job class for job: CRLUpdateJob
2022-01-04 15:00:00,284 [thread=Thread-5 (ActiveMQ-client-global-threads)] [=, org=, csid=] ERROR org.candlepin.async.JobMessageReceiver - Job processing failed terminally; committing job message as acknowledged: Message [id: 2147484742, address: job, body: {"jobId":"8a8182757e26a962017e26ad52b40016","jobKey":"CRLUpdateJob"}]
```
This error reflects the fact that the CRLUpdateJob was removed from Candlepin and replaced with the CertificateCleanupJob in https://github.com/candlepin/candlepin/pull/3078.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Moderate: Satellite 6.10.2 Async Bug Fix Update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2022:0190
Verified on Satellite 6.10.2, snap 1. Steps to Test: 1. Add the following line to /etc/candlepin/candlepin.conf to set the CRLUpdateJob to run every 3 minutes: candlepin.async.jobs.CRLUpdateJob.schedule=0 0/3 * * * ? 2. Restart the tomcat service: # systemctl restart tomcat 3. Register a host to Satellite. 4. Check the time when /var/lib/candlepin/candlepin-crl.crl was last updated: 5. Follow the Candlepin log and wait for the CRLUpdateJob to run. 6. Between two runs of the job, attach a subscription to the host registered in step 3, then immediately remove that subscription. 7. After the job runs again, check the last modified time of the CRL file again: Expected Results: On a Satellite 6.10.2 that was upgraded from Satellite 6.9, the CRL file is not updated. On a Satellite 6.10.2 that was freshly installed, the file is never created. Actual Results: On a Satellite 6.10.2 that was upgraded from Satellite 6.9, the CRL file is not updated. On a Satellite 6.10.2 that was freshly installed, the file is never created. In both cases, the job run results in an error in /var/log/candlepin/candlepin.log: ``` 2022-01-04 15:00:00,199 [thread=QuartzScheduler_Worker-4] [=, org=, csid=] INFO org.candlepin.async.JobManager - Job queued: AsyncJobStatus [id: 8a8182757e26a962017e26ad52b40016, name: CRLUpdateJob, key: CRLUpdateJob, state: QUEUED] 2022-01-04 15:00:00,284 [thread=Thread-5 (ActiveMQ-client-global-threads)] [job=8a8182757e26a962017e26ad52b40016, job_key=CRLUpdateJob, org=, csid=] ERROR org.candlepin.async.JobManager - No registered job class for job: CRLUpdateJob 2022-01-04 15:00:00,284 [thread=Thread-5 (ActiveMQ-client-global-threads)] [=, org=, csid=] ERROR org.candlepin.async.JobMessageReceiver - Job processing failed terminally; committing job message as acknowledged: Message [id: 2147484742, address: job, body: {"jobId":"8a8182757e26a962017e26ad52b40016","jobKey":"CRLUpdateJob"}] ``` This error reflects the fact that the CRLUpdateJob was removed from Candlepin and replaced with the CertificateCleanupJob in https://github.com/candlepin/candlepin/pull/3078.