Bug 1343633
| Summary: | [GSS](6.4.z):read-proxies-configuration and :read-proxies-info fail when there is no httpd | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Aaron Ogburn <aogburn> |
| Component: | mod_cluster | Assignee: | Aaron Ogburn <aogburn> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Peter Mackay <pmackay> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.4.8 | CC: | bmaxwell, bperkins, bspyrkos, jclere, jtruhlar, msochure, pmackay |
| Target Milestone: | CR1 | ||
| Target Release: | EAP 6.4.11 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | https://github.com/jbossas/jboss-eap/pull/2801 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-01-17 13:09:57 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: | |||
| Bug Blocks: | 1361648 | ||
PR: https://github.com/jbossas/jboss-eap/pull/2801 EAP7 JIRA: https://issues.jboss.org/browse/JBEAP-5111 EAP7 PR: https://github.com/jbossas/jboss-eap7/pull/560 WF JIRA: https://issues.jboss.org/browse/WFLY-6680 WF PR: https://github.com/wildfly/wildfly/pull/8962 Kabir Khan <kabir.khan> updated the status of jira JBEAP-5111 to Resolved EAP 7.0.z JIRA: https://issues.jboss.org/browse/JBEAP-6094 EAP 7.0.z PR: https://github.com/jbossas/jboss-eap7/pull/560 EAP 7.1 JIRA: https://issues.jboss.org/browse/JBEAP-5111 EAP 7.1 PR: https://github.com/jbossas/jboss-eap7/pull/570 Verified with EAP 6.4.11.CP.CR1 Retroactively bulk-closing issues from released EAP 6.4 cummulative patches. |
Description of problem: When the modcluster subsystem is unable to connect to a proxy, the jboss-cli commands :read-proxies-configuration and :read-proxies-info fail with an unhelpful error. On both the domain controller and application host, :read-proxies-info and :read-proxies-configuration fail with the same error. This is the output from the application host: [domain@localhost:9999 subsystem=modcluster] pwd /host=localhost/server=cluster2/subsystem=modcluster [domain@localhost:9999 subsystem=modcluster] :list-proxies { "outcome" => "success", "result" => [ "web02:8009", "web01:8009" ] } [domain@localhost:9999 subsystem=modcluster] :read-proxies-configuration { "outcome" => "failed", "result" => undefined, "failure-description" => "JBAS014749: Operation handler failed: newValue is null", "rolled-back" => true } [domain@localhost:9999 subsystem=modcluster] :read-proxies-info { "outcome" => "failed", "result" => undefined, "failure-description" => "JBAS014749: Operation handler failed: newValue is null", "rolled-back" => true } Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Set modcluster's proxy-list 2. Don't run httpd on that specified proxy-list ip/port 3. Attempt a :read-proxies-configuration or :read-proxies-info command Actual results: The CLI commands fail if an httpd is down Expected results: The CLI command works if an httpd is down