Bug 1370355 - OSE Hello World example app not listed on Summary page
Summary: OSE Hello World example app not listed on Summary page
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Quickstart Cloud Installer
Classification: Red Hat
Component: WebUI
Version: 1.0
Hardware: All
OS: Linux
low
low
Target Milestone: ---
: 1.1
Assignee: cchase
QA Contact: Tasos Papaioannou
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-26 02:53 UTC by Katherine Dubé
Modified: 2017-02-28 01:38 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-28 01:38:44 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:0335 0 normal SHIPPED_LIVE Red Hat Quickstart Installer 1.1 2017-02-28 06:36:13 UTC

Description Katherine Dubé 2016-08-26 02:53:00 UTC 
Description of problem:

The OSE Hello World example app doesn't show that it's been selected to be deployed (or not) on the Summary page under the OSE section. A new field should be added to the list to display what has been selected.

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


How reproducible:

100%

Steps to Reproduce:
1.
2.
3.

Actual results:
Hello World deployment information is missing from the OSE section of the Summary page.

Expected results:
Hello World deployment information should appear in the OSE section of the Summary page.

Additional info:
Comment 2 cchase 2016-09-06 14:29:50 UTC 
https://github.com/fusor/fusor/pull/1207

Since the post-install summary page does have a link to the hello-world app on it, I'm assuming this bug was referring to the review page before deployment.    I added a link on the review page to say
Example Application: Enabled/Disabled
Comment 3 Tasos Papaioannou 2016-09-23 15:08:16 UTC 
Verified on QCI-1.1-RHEL-7-20160922.n.1.
Comment 6 errata-xmlrpc 2017-02-28 01:38:44 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2017:0335
Note You need to log in before you can comment on or make changes to this bug.