Bug 1280365 - Unable to cancel RHCI Deployment from any of the "1. Satellite" pages of the wizard
Summary: Unable to cancel RHCI Deployment from any of the "1. Satellite" pages of the ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Quickstart Cloud Installer
Classification: Red Hat
Component: WebUI
Version: 1.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: TP2
: 1.0
Assignee: jmagen@redhat.com
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks: rhci-sprint-12
TreeView+ depends on / blocked
 
Reported: 2015-11-11 15:02 UTC by bmorriso
Modified: 2016-10-03 19:12 UTC (History)
6 users (show)

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


Attachments (Terms of Use)

Description bmorriso 2015-11-11 15:02:32 UTC
Description of problem:
In the RHCI Installer wizard, if you try to cancel and exit a deployment from any of the Satellite pages (1A-1D), nothing happens. Cancel works correctly on pages in the later sections of the wizard. 

Version-Release number of selected component (if applicable):
RHCI-6.0-RHEL-7-20151104.t.0-RHCI-x86_64-dvd1.iso

How reproducible:
always

Steps to Reproduce:
1. Start a new RHCI deployment. 
2. On any page under section 1, click cancel>exit and delete
3.

Actual results:
Nothing happens

Expected results:
Return to the RHCI Deployments page

Additional info:

Comment 1 John Matthews 2015-11-17 14:22:17 UTC
Joseph,

Please share your thoughts on this BZ.

Is this something we can address, I was under impression we hadn't yet created a deployment object on backend during steps 1A-1D, hence maybe that explains why cancel functionality is missing?

Comment 2 jmagen@redhat.com 2015-12-16 13:42:19 UTC
Fixed.
disable cancel button on steps 1 A, B, C, until deployment is saved
https://github.com/fusor/fusor/pull/571

Comment 3 Antonin Pagac 2016-01-25 13:52:58 UTC
Verified.

TP2 RC3
RHCI-6.0-RHEL-7-20160122.t.1-RHCI-x86_64-dvd1.iso


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