Bug 888842
| Summary: | Candlepin Server seemingly not recognizing cert_v3 enabled | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Community] Candlepin (Migrated to Jira) | Reporter: | Dennis Crissman <dcrissman> | ||||
| Component: | candlepin | Assignee: | candlepin-bugs | ||||
| Status: | CLOSED NOTABUG | QA Contact: | Eric Sammons <esammons> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 0.9 | CC: | dcrissman | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-12-20 20:57:14 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: | |||||||
| Attachments: |
|
||||||
We checked today and are getting the correct message. [2012-12-19T12:07:37.631477-05:00] [host:s04.candlepin.stage.ext.phx2.redhat.com] [app:org.quartz.SchedulerException] Job threw an unhandled exception. [See nested exception: java.lang.RuntimeException: org.candlepin.util.CertificateSizeException: Too many content sets for certificate. Please upgrade to a newer client to use subscription: Red Hat Employee Subscription] We will keep an eye on this with the next push to stage. Strong possibility this is not a big just confusion between configuration, restarting services, and a concurrent problem with async bind error handling. There is an issue where a bind to to large of a cert for a consumer manually created in the portal will error out, and the async job does not correctly handle that error. At the time this message was captured, I believe the server was not properly configured, v3 was still disabled in config, or something needed a restart. During the day yesterday we asked for double checking on config and restarting services, which was done. I believe we then tried to reproduce (using the async bind method), saw the job still freeze, but didn't notice that the message in the logs had changed slightly to be the correct notice that the cert has too many content sets, *not* that v3 is disabled on the server. This would be very easy to do, but as it stands now stage is definitely giving out v3 certs for normal system binds, and for async we are also now seeing the correct message. Leaving this open for a bit but likely notabug. Build has been pushed to stage. We can now verify. Thanks. Everything is working properly now. Closing issue. |
Created attachment 666204 [details] candlepin.conf in stage We have cert_v3 enabled in stage, however I received the following error which based on the candlepin code, would indicate the server is not recognizing the property (see DefaultEntitlementCertServiceAdapter#prepareV1Extensions line 273). [2012-12-18T09:18:13.949319-05:00] [host:s03.candlepin.stage.ext.phx2.redhat.com] [app:java.lang.RuntimeException] org.candlepin.util.CertificateSizeException: The support of V3 certificates is not enabled on the server and is required for large content set subscription: Red Hat Employee Subscription See attached StageCandlepinConf, you will see that the cert_v3 is in-face enabled.