Bug 1302322
Summary: | Secure server-agent communication using sslsocket incorrectly requires a truststore password | ||
---|---|---|---|
Product: | [JBoss] JBoss Operations Network | Reporter: | Filip Brychta <fbrychta> |
Component: | Agent, Usability | Assignee: | Josejulio Martínez <jmartine> |
Status: | CLOSED ERRATA | QA Contact: | Filip Brychta <fbrychta> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | JON 3.3.5 | CC: | jmartine, loleary, spinder |
Target Milestone: | DR01 | Keywords: | EasyFix, Triaged |
Target Release: | JON 3.3.6 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-07-27 15:32:30 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: | |||
Bug Depends On: | 867148 | ||
Bug Blocks: |
Description
Filip Brychta
2016-01-27 13:42:27 UTC
This issue had been identified in upstream Bug 867148. The issue is that rhq.agent.client.security.truststore.password becomes a required parameter even though it is not used once you set sslsocket. The result is the agent fails to start unless you add the unused property and provide some meaningless dummy value. To fix this, the property and its value should only be used if it is defined and not an empty string. commit bbb0359b56d9f74e637fa9e1d021b83a5879bb7a Author: Josejulio Martínez <jmartine> Date: Fri Feb 12 13:14:29 2016 -0600 Bug 1302322 - Secure server-agent communication using sslsocket incorrectly requires a truststore password. Made ClientSenderSecurityTruststorePassword(client.security.truststore.password) property optional, no longer storing null in the configuration map. This avoids passing a map with nulls to org.jboss.remoting.Client which causes an Exception on it's connect method. This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions Moving to ON_QA as available to test with JON 3.3.6 DR01 brew build: https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=499890 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, 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://rhn.redhat.com/errata/RHSA-2016-1519.html |