Bug 1372156

Summary: WebUI should allow users to create Library+ environment1 + environment2 environment path
Product: Red Hat Quickstart Cloud Installer Reporter: Julie <juwu>
Component: WebUIAssignee: John Matthews <jmatthew>
Status: CLOSED NOTABUG QA Contact: Sudhir Mallamprabhakara <smallamp>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.0CC: tsanders
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-09-01 15:17:34 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:
Attachments:
Description Flags
Appllication lifecycle chain none

Description Julie 2016-09-01 04:39:29 UTC
Created attachment 1196583 [details]
Appllication lifecycle chain

Steps to reproduce:
1. In the webUI (content->lifecycle environments), create a environment path that has two or more environments.
2. Create a deployment and get to *1B Update Availability*. Select *After manually publishing them*, select the environment from step1, and click *New Environment Path* in attempt to add another environment to the selected path. 


Current Results,
User cannot add additional environments to an existing path and a new path is created. See attached screenshot. 

Users can only create Library+another environment path.

Expected Results:
1. Users can create  Library+ environment1 + environment2....
2. Or, when user selects an existing path that two environments, and then click *New Environment Path*, the selected path should be deselected so it does not mislead users that they are able to add another environment to the selected path.

Comment 1 Todd Sanders 2016-09-01 15:17:14 UTC
Working as designed.  QCI only supports creation and promotion to first environment past Library.  All other promotions for deployed hosts and content will need to be managed from the Satellite UI.