Bug 1503462

Summary: Jolokia agent fails on certificates with spaces
Product: OpenShift Container Platform Reporter: Juraci Paixão Kröhling <jcosta>
Component: HawkularAssignee: Juraci Paixão Kröhling <jcosta>
Status: CLOSED WONTFIX QA Contact: Junqi Zhao <juzhao>
Severity: low Docs Contact:
Priority: unspecified    
Version: 3.7.1CC: aos-bugs
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-10-18 08:09: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:

Description Juraci Paixão Kröhling 2017-10-18 08:05:00 UTC 
When the CA bundle on a pod has trailing spaces, the Jolokia agent throws an exception.

See https://bugzilla.redhat.com/show_bug.cgi?id=1500464#c8

```
Could not start Jolokia agent: java.lang.IllegalStateException: Cannot use keystore for https communication: java.security.cert.CertificateException: Could not parse certificate: java.io.IOException: Illegal header: -----BEGIN CERTIFICATE-----  
```

This is a configuration issue and the proper solution is to get the cert to be made available without trailing spaces.

A workaround for the other parts dealing with the Java cert toolchain was made as part of BZ 1471251 (and related) and a similar workaround could be made for the Jolokia agent, if necessary.

This affects all versions of the Jolokia Agent included in Metrics.
Comment 1 Juraci Paixão Kröhling 2017-10-18 08:08:50 UTC 
I'm closing this as WONTFIX, as this is a configuration issue. If a workaround is required, like for the linked BZs, please reopen this.