| Summary: | Jenkins build will fail when using haproxy as load balancer fronting multiple OpenShift brokers | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Johnny Liu <jialiu> |
| Component: | Node | Assignee: | Miciah Dashiel Butler Masters <mmasters> |
| Status: | CLOSED NOTABUG | QA Contact: | libra bugs <libra-bugs> |
| Severity: | high | Docs Contact: | |
| Priority: | low | ||
| Version: | 1.2.1 | CC: | bleanhar, jialiu, libra-onpremise-devel, lmeyer |
| 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: | 2014-05-12 14:04:40 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: | |
| Bug Depends On: | 1008352 | ||
| Bug Blocks: | |||
|
Description
Johnny Liu
2013-09-06 03:00:33 UTC
Broker keys and AUTH_SALT need to be the same across all the brokers, c.f. https://access.redhat.com/site/documentation/en-US/OpenShift_Enterprise/2/html-single/Deployment_Guide/index.html#Configuring_the_Required_Services "Note: The AUTH_PRIV_KEY_FILE, AUTH_PRIV_KEY_PASS and AUTH_PUB_KEY_FILE settings must specify the same private key on all associated brokers for the Jenkins authentication to work." If this is not the case, you will see exactly these symptoms (or a slightly different one, "padding error" but with the same stack trace in production.log). Can you comment on whether this note was followed? Three things will actually break if not: 1. Jenkins 2. Auto-scaling 3. Registering deployments to the broker ... all for the same reason. #3 wasn't a concern when this bug was filed, and #2 can easily go unnoticed. The docs need updating to call this out better. One other thing that I suspect could go wrong is that since Jenkins is using the Java client, it could stop connecting if the SSL cert it's getting from the load balancer is different from the URL of the load balancer. I expect that would look different, though. Indeed follow the instruction, "Note: The AUTH_PRIV_KEY_FILE, AUTH_PRIV_KEY_PASS and AUTH_PUB_KEY_FILE settings must specify the same private key on all associated brokers for the Jenkins authentication to work." Jenkins build and auto-scaling is working well, seem like it is a configuration issue from me. Thanks for your comments. I'm closing this based on Comment #6. Thanks for all the help. |