Bug 1173479 - 4.13: Native Management Port/Host does not take into account port offset?
Summary: 4.13: Native Management Port/Host does not take into account port offset?
Keywords:
Status: ON_QA
Alias: None
Product: RHQ Project
Classification: Other
Component: Configuration, Operations, Plugin Container, Plugins
Version: 4.13
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: RHQ 4.13
Assignee: Thomas Heute
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1175664
TreeView+ depends on / blocked
 
Reported: 2014-12-12 08:56 UTC by Stian Lund
Modified: 2022-03-31 04:27 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
: 1175664 (view as bug list)
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)
Port offset for all server on one host. (73.32 KB, image/png)
2014-12-12 08:56 UTC, Stian Lund
no flags Details

Description Stian Lund 2014-12-12 08:56:36 UTC
Created attachment 967524 [details]
Port offset for all server on one host.

Description of problem:

When upgrading our 4.5.1 RHQ Server to 4.13, there are two new setting under Connection Settings for Jboss AS7:

Native management API host
Native management API port

I also notice that for most of the AS7 servers in inventory after upgrade, this port is set to 9999 for all server instances.

This is wrong, since we run many instances on the same host with port offset 100. So it should be 9999, 10099 and so on.

I tried uninventory of all AS7 on one host and import, and the result was that the Native Port was set correctly for the instances.

However having to do this for potentially hundreds of servers is not something I can easily do.

So the question is:
Is there a bug in discovery that would result it not taking offset into consideration when upgrading servers already in inventory?

Not sure when this connection settings property was introduced but it must have been after 4.5.1? Maybe even just the last releases?


Version-Release number of selected component (if applicable):

RHQ 4.13 
AS7 Agent 4.13

How reproducible:

When upgrading servers this happens to most servers, but not every server.
When doing uninventory and import the servers seem to get the correct native management port.

Steps to Reproduce:
Upgrade servers from older version of RHQ. Might only affect very old (4.5.1) versions.

Actual results:

Management native port set to 9999 for all servers which is wrong according to offset.

Expected results:

Expect management native port to be set correctly.

Additional info:

Comment 1 Libor Zoubek 2014-12-15 16:00:58 UTC
Yes, there is a bug in resource upgrade code, which does not care about native host & port at all right now, so values you get in UI are defaults comming from plugin descriptor.

Comment 2 Libor Zoubek 2015-01-07 14:21:05 UTC
branch:  master
link:    https://github.com/rhq-project/rhq/commit/0832e0af3
time:    2015-01-07 15:17:21 +0100
commit:  0832e0af3505ff5ac07206884d4cdefadeda8267
author:  Libor Zoubek - lzoubek
message: Bug 1173479 - 4.13: Native Management Port/Host does not take into
         account port offset/

         Fixed AS7 resourceUpgrade code to always detect native
         management host/port in case resource is running and defaults
         are set


Note You need to log in before you can comment on or make changes to this bug.