Bug 1119240
Summary: | Adding http-interface in the host controller's host-slave.xml is not recognised by JBoss ON Agent causing Host Controller's availability to stay DOWN | ||
---|---|---|---|
Product: | [JBoss] JBoss Operations Network | Reporter: | bkramer <bkramer> |
Component: | Plugin -- JBoss EAP 6 | Assignee: | Libor Zoubek <lzoubek> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Armine Hovsepyan <ahovsepy> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | JON 3.2 | CC: | loleary, lzoubek, mauro.nobre, mfoley, mkoci, theute |
Target Milestone: | ER01 | ||
Target Release: | JON 3.3.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
If the management interface in the host-slave.xml file was changed, the JBoss ON Agent threw an "Invalid port: 0" error while trying to discover the JON server. Restarting the JON server and agent did not clear the error. JBoss ON discovered the Host Controller but it was marked as DOWN and a WARN log event was added to the agent.log file. The Plug-in UI did not adequately show an indication of the issue. The fix now displays a warning icon next to the availability icon on the resource. When clicked, a window displays with the following explanation: "Unable to detect management port. Please enable management HTTP interface on <server> and then set the correct port number in Connection Settings of this resource". The same warning is logged in the agent.log file as a WARN message when the host controller is started.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2014-12-11 13:59:53 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: | 1119242 |
Description
bkramer
2014-07-14 11:08:16 UTC
Additional info - to work around this: * remove (uninventory) unavailable host controller from the JBoss ON inventory; * let JBoss ON Agent on the machine 2 to discover HC again; * inventory discovered Host Controller again; * make sure that the username/password is set correctly in the host controller Connection Settings page; * execute "Execute Availability Scan" operation for RHQ Agent resource on the machine 2. Actually .. plugin cannot change plugin configuration once resource was already discovered. So once it is discovered with incorrectly detected port user has to set up management interface and also update Connection Settings and set correct port number. I've changed plugin, so when it fails to detect port it fails to start component -> this results to yellow triangle right next to availability icon on resource. User can then read the message and do appropriate action. in master commit 2d3a7af207833a95e619422e3b788cb30e7ffb69 Author: Libor Zoubek <lzoubek> Date: Thu Aug 7 17:33:36 2014 +0200 Bug 1119240 - Adding http-interface in the host controller's host-slave.xml is not recognised by JBoss ON Agent causing Host Controller's availability to stay DOWN throw InvalidPluginConfiguration exception when http mgmt interface port is detected as 0 (not-detected). User is advised to set his host controller up and then update connection settings. in 3.3. branch commit e0836720cfb52e05a59d2979d3800b5b52a0a94b Author: Libor Zoubek <lzoubek> Date: Thu Aug 7 17:33:36 2014 +0200 Bug 1119240 - Adding http-interface in the host controller's host-slave.xml is not recognised by JBoss ON Agent causing Host Controller's availability to stay DOWN throw InvalidPluginConfiguration exception when http mgmt interface port is detected as 0 (not-detected). User is advised to set his host controller up and then update connection settings. (cherry picked from commit 2d3a7af207833a95e619422e3b788cb30e7ffb69) Signed-off-by: Libor Zoubek <lzoubek> Moving to ON_QA as available to test in the following brew build: https://brewweb.devel.redhat.com//buildinfo?buildID=379025 Moving to VERIFIED. If the http-interface is not specified in host-slave.xml, the host controller appears to be down. As described in Comment 2, there appears a triangle icon next to availability icon which, when clicked, opens the window with further explanation: "Unable to detect management port. Please enable management HTTP interface on and then set correct port number in Connection Settings of this resource". The same warning is logged in agent.log file as a WARN message while starting the host controller. |