Bug 1312454 - Open support case for EAP7 failed to auto load product name and product version
Open support case for EAP7 failed to auto load product name and product version
Status: CLOSED WONTFIX
Product: JBoss Operations Network
Classification: JBoss
Component: Plugin -- JBoss EAP 7 (Show other bugs)
JON 3.3.5
All Unspecified
unspecified Severity high
: ---
: ---
Assigned To: Simeon Pinder
Mike Foley
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-02-26 12:55 EST by Jeeva Kandasamy
Modified: 2016-03-04 12:09 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-03-04 11:59:21 EST
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)
open support case page (33.74 KB, image/png)
2016-02-26 12:55 EST, Jeeva Kandasamy
no flags Details

  None (edit)
Description Jeeva Kandasamy 2016-02-26 12:55:11 EST
Created attachment 1130890 [details]
open support case page

Description of problem:
When open support case for JBoss EAP 7 from inventory. It's failing to auto loading of product name and product version.


Version-Release number of selected component (if applicable):
JBoss ON 3.3.5 with EAP plugin pack update03-DR01

How reproducible:
always

Steps to Reproduce:
1. Navigate to "EAP instance"
2. Right click on EAP and select "Open Support Case"
3. Sign into the Red Hat Customer Portal with Red Hat access credentials (if not signed in already).

Actual results:
Product name and version are not loading automatically.

Expected results:
When we select from inventory, product name and version should loaded automatically.

Additional info: screen shot is attached.
Comment 4 Larry O'Leary 2016-03-04 12:09:43 EST
This bug will not be fixed as this capability is going away. Bug 1314859 has been captured to remove the "Open Support Case" menu option.

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