Bug 1285541 - Deployment warning modal shows up even if I've fixed the problem
Summary: Deployment warning modal shows up even if I've fixed the problem
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Quickstart Cloud Installer
Classification: Red Hat
Component: Installation - RHCI
Version: 1.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: TP2
: 1.0
Assignee: cchase
QA Contact: Tasos Papaioannou
Dan Macpherson
URL:
Whiteboard:
Depends On:
Blocks: rhci-sprint-12
TreeView+ depends on / blocked
 
Reported: 2015-11-25 21:55 UTC by David Davis
Modified: 2016-10-03 19:13 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-03 19:13:26 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description David Davis 2015-11-25 21:55:10 UTC
Description of problem:

If you hit a warning in the deployment and back up and fix the problem, you still get a modal warning you that there's a warning with the deployment


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


How reproducible:


Steps to Reproduce:
1. Create a RHEV deployment and fill out a bad NFS url (one that doesn't exist)
2. Go to the deployment review screen. Note the warning.
3. Go back and change the url to a working NFS server url
4. Proceed to the deployment review screen. There should no longer be a warning.
5. Click "Deploy >" and you should get a warning modal saying "Are you sure that you want...". 

Actual results:

You get a warning modal even though there are no warnings.


Expected results:

No modal.

Comment 1 David Davis 2015-11-25 21:57:50 UTC
Also, looks like the deployment name doesn't show up in the warning modal.

Comment 2 cchase 2016-01-20 21:30:20 UTC
https://github.com/fusor/fusor/pull/646

Comment 3 John Matthews 2016-01-22 20:20:35 UTC
Compose of 1/22/16

Comment 4 Tasos Papaioannou 2016-01-26 18:48:12 UTC
Verified on RHCI-6.0-RHEL-7-20160125.t.0.

Warning disappears after fixing NFS IP address, and deployment name is displayed under Installation Review.


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