Bug 1413735 - OpenShift section not locked when a Deployment has been started
Summary: OpenShift section not locked when a Deployment has been started
Keywords:
Status: NEW
Alias: None
Product: Red Hat Quickstart Cloud Installer
Classification: Red Hat
Component: WebUI
Version: 1.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 1.2
Assignee: John Matthews
QA Contact: Sudhir Mallamprabhakara
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-01-16 20:37 UTC by Matt Reid
Modified: 2017-01-20 21:14 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)
Deployment was started (43.31 KB, image/png)
2017-01-16 20:37 UTC, Matt Reid
no flags Details
OpenShift section is still editable after Deployment has started (64.45 KB, image/png)
2017-01-16 20:37 UTC, Matt Reid
no flags Details

Description Matt Reid 2017-01-16 20:37:24 UTC
Created attachment 1241400 [details]
Deployment was started

Description of problem:
Configurable content is supposed to become read-only once a deployment has started, but on a deployment I have that errored out (OpenShift has been deployed successfully, CFME had an issue), I can still adjust my type and other node details for OpenShift. 

Clearly, whatever I modify here will have no impact on anything, since the deployment has already been set up. To prevent any confusion, and be consistent with other sections, it should no longer be editable once the Deploy button has been pressed.

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


Additional info:

Comment 2 Matt Reid 2017-01-16 20:37:55 UTC
Created attachment 1241401 [details]
OpenShift section is still editable after Deployment has started


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