Bug 1096740
| Summary: | "Red Hat JBoss Operations Network 3.2 Update 01" expects default values for jboss.bind.address | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Operations Network | Reporter: | bkramer <bkramer> |
| Component: | Installer | Assignee: | Simeon Pinder <spinder> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike Foley <mfoley> |
| Severity: | urgent | Docs Contact: | |
| Priority: | high | ||
| Version: | JON 3.2 | CC: | fbrychta, loleary, myarboro, spinder |
| Target Milestone: | DR03 | Keywords: | Triaged |
| Target Release: | JON 3.2.2 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-07-29 00:17:31 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: | |||
Moving to DR03 as didn't get included for earlier payload. This is fixed with the following commit to jon.git: 8e2a35305308 The change was to modify both .sh/.bat scripts to use the JBoss values from rhq-server.properties instead of the hardcoded values. Moving to MODIFIED for testing in next available build. Moving to ON_QA as available for test in latest build: http://jon01.mw.lab.eng.bos.redhat.com:8042/dist/release/jon/3.2.2.GA/6-28-2014/ Verified on Version : 3.2.0.GA Update 02 Build Number : 558495c:44428f7 This has been verified and released in Red Hat JBoss Operations Network 3.2 Update 02 (3.2.2) available from the Red Hat Customer Portal[1]. [1]: https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?softwareId=31783 |
Description of problem: When trying to install Red Hat JBoss Operations Network 3.2 Update 01 the following output is logged: ************************************************************************* $ ./apply-updates.sh /opt/jboss/jon/jon-server-3.2.0.GA/ Successfully detected server [/opt/jboss/jon/jon-server-3.2.0.GA/] to be upgraded. Proceeding... Proceeding with application of patch '01' to /opt/jboss/jon/jon-server-3.2.0.GA/ Successfully detected agent [/opt/jboss/jon/rhq-agent] to be upgraded. Proceeding... Proceeding with application of patch '01' to /opt/jboss/jon/rhq-agent Verifying that all [Server] component(s) are stopped... Successfull verified that [Server] is already shut down. Archiving legacy files. This list is cumulative and may attempt to remove files handled by earlier updates. Moving the following files to [./.old] for server and/or [./.old-agent] for agent: See './update.log' for more archive details. Applying the update contents. Applying additional JON Server updates... Starting JON Server... Starting JBoss CLI and applying patches... org.jboss.as.cli.CliInitializationException: Failed to connect to the controller at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:280) at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:240) at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:34) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.jboss.modules.Module.run(Module.java:270) at org.jboss.modules.Main.main(Main.java:411) Caused by: org.jboss.as.cli.CommandLineException: The controller is not available at localhost:6999 at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:951) at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:790) at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:766) at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:278) ... 8 more Caused by: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to remote://localhost:6999. The connection timed out at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:129) at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:71) at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:929) ... 11 more Caused by: java.net.ConnectException: JBAS012144: Could not connect to remote://localhost:6999. The connection timed out at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:131) at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:256) at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70) at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:176) at org.jboss.as.cli.impl.CLIModelControllerClient.getOrCreateChannel(CLIModelControllerClient.java:156) at org.jboss.as.cli.impl.CLIModelControllerClient$2.getChannel(CLIModelControllerClient.java:118) at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:115) at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:90) at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236) at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141) at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127) ... 13 more Stopping the JON Server... You have successfully extracted patch contents into (JON server) and/or (JON agent) installation folder(s). You should do the following as is necessary: i)Closely follow the remainder of the instructions delivered with this update. ii)restart your server(s)* iii)restart agents and request agent updates NOTE: for HA environments you may need to repeat the steps here for each server before patch application is complete. ************************************************************************* Version-Release number of selected component (if applicable): JBoss ON 3.2 How reproducible: Always Steps to Reproduce: 1. jboss.bind.address.management is different then 0.0.0.0 or 127.0.0.1 2. 3. Actual results: The upgrade is not properly finished and the above exception is logged. Expected results: The upgrade is properly finished and no exception is logged. Additional info: To work around this run the following command directly from jboss-cli: <RHQ_SERVER_HOME>/jbossas/bin/jboss-cli.sh --controller=<REAL_BIND_ADDRESS>:<REAL_JBOSS_MANAGEMENT_NATIVE_PORT> --connect --command='/subsystem=datasources/xa-data-source=RHQDS/:write-attribute(name="no-tx-separate-pool", value=true)' where: * <REAL_BIND_ADDRESS> is replaced with *jboss.bind.address.management* from rhq-server.properties file * <REAL_JBOSS_MANAGEMENT_NATIVE_PORT> is replaced with *jboss.management.native.port* from rhq-server.properties file