Bug 846578 - EAP 6 resource-name doesn't change after modification of connection settings
EAP 6 resource-name doesn't change after modification of connection settings
Status: CLOSED WONTFIX
Product: JBoss Operations Network
Classification: JBoss
Component: UI (Show other bugs)
JON 3.1.0
Unspecified Unspecified
unspecified Severity unspecified
: ---
: JON 3.1.2
Assigned To: RHQ Project Maintainer
Mike Foley
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-08-08 03:37 EDT by Jochen Cordes
Modified: 2012-09-25 16:19 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-09-25 16:19:01 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Changing hotsname in Connection Settings (256.39 KB, image/png)
2012-08-08 03:37 EDT, Jochen Cordes
no flags Details

  None (edit)
Description Jochen Cordes 2012-08-08 03:37:26 EDT
Created attachment 602955 [details]
Changing hotsname in Connection Settings

Description of problem:

Usually all EAP 6 Servers discovered have the resource-name displayed as EAP (127.0.0.1:9990) in the UI.

When changing 127.0.0.1 to the actual hostname in EAP/Inventory/Connection Settings and clicking on "save" the resource-name still stays EAP (127.0.0.1:9990).


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


How reproducible:


Steps to Reproduce:
1. Start a new EAP 6 instance (with an agent running on the instance)
2. Import the resource from the discovery queue
3. Go to EAP / Inventory / Connection Settings and change the hostname
4. Click on save
  
Actual results:

Resouce is still displayed as EAP (127.0.0.1:9990).

Expected results:

Resource should be displayed as EAP (<host-name>:9990).

Additional info:
Comment 1 mark yarborough 2012-09-25 16:19:01 EDT
Per ccrouch, resource names are not dynamically updated.

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