Bug 953262

Summary: Right-click import wizard from platform resource for most server resource types is incomplete
Product: [JBoss] JBoss Operations Network Reporter: dsteigne
Component: UIAssignee: RHQ Project Maintainer <rhq-maint>
Status: CLOSED DUPLICATE QA Contact: Mike Foley <mfoley>
Severity: medium Docs Contact:
Priority: unspecified    
Version: JON 3.1.2CC: dsteigne, jshaughn, loleary
Target Milestone: ---   
Target Release: JON 3.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-06-04 20:42:43 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:

Description dsteigne 2013-04-17 19:30:37 UTC 
Description of problem:
The Import> JMX Server wizard opened by right-clicking on the Platform resource is broken. I give a screen asking for Resource Name then a screen with the timeout setting and the nothing else, and the Finish button on the last screen is greyed out.

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

How reproducible:
Everytime

Steps to Reproduce:
1. Open the JON UI, navigate to a Platform resource
2. Right-click > select Import > select JMX Server
3. Enter a Resource Name, click Next
4. Enter a Timeout
  
Actual results:
The Finish button stays grey and there is no screen to enter the properties of the JMX Server

Expected results:
See the same screens as if the Import Wizard was opened from the Platform > Inventory > Child Resources tab.

Additional info:
Comment 1 Larry O'Leary 2013-04-17 22:40:31 UTC 
This issue is not limited to JMX. It affects JBossAS4, AS5, JMX Server, Process, Script Server, and Tomcat Server. Additionally, on Apache, JBossAS7, and Postgres Server (whatever that is).
Comment 2 Jay Shaughnessy 2013-06-04 15:35:55 UTC 
I could not reproduce. I believe this is a duplicate of Bug 913121, which has been fixed.
Comment 3 dsteigne 2013-06-04 17:58:02 UTC 
Jay,

What additional info do you need from me?
Comment 4 dsteigne 2013-06-04 19:17:50 UTC 
Jay,
If you are asking me if Bug 913121 is the same, it appears that it is.
Comment 5 dsteigne 2013-06-04 20:42:43 UTC 

*** This bug has been marked as a duplicate of bug 913121 ***
Comment 6 Larry O'Leary 2013-06-04 20:56:02 UTC 
Marking this as a duplicate of 918973 instead as that is the product bug. 913121 is an upstream community bug and a product bug can not duplicate a community bug. :)

*** This bug has been marked as a duplicate of bug 918973 ***