Bug 1611612

Summary: Extra flash message after canceling provisioning
Product: Red Hat CloudForms Management Engine Reporter: Matouš Mojžíš <mmojzis>
Component: UI - OPSAssignee: Hilda Stastna <hstastna>
Status: CLOSED DUPLICATE QA Contact: Matouš Mojžíš <mmojzis>
Severity: low Docs Contact:
Priority: unspecified    
Version: 5.10.0CC: dmetzger, hkataria, hstastna, lavenel, mpovolny, obarenbo, rhrazdil, simaishi, vparekh
Target Milestone: GA   
Target Release: 5.10.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: ui:provision
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-22 17:41:46 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: CFME Core Target Upstream Version:
Embargoed:
Attachments:
Description Flags
canceled_provision none

Description Matouš Mojžíš 2018-08-02 13:14:27 UTC
Created attachment 1472698 [details]
canceled_provision

Description of problem:


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

How reproducible:
Always

Steps to Reproduce:
1. Go to Compute -> Cloud -> Instances -> Provision 
2. Select Provision Instance
3. Cancel provisioning

Actual results:
There is extra success flash message.

Expected results:


Additional info:

Comment 2 Hilda Stastna 2018-08-13 09:30:33 UTC
Note: This problem occurs also while provisioning VMs under Compute > Infra > VMs.

Comment 3 Hilda Stastna 2018-08-13 09:57:29 UTC
Fixes: https://github.com/ManageIQ/manageiq-ui-classic/pull/4460

Comment 4 Hilda Stastna 2018-08-22 14:46:22 UTC
The PR above fixing the BZ is still in progress.

Comment 5 Hilda Stastna 2018-08-22 15:49:00 UTC
*** Bug 1593572 has been marked as a duplicate of this bug. ***

Comment 6 Hilda Stastna 2018-09-21 09:22:48 UTC
*** Bug 1629708 has been marked as a duplicate of this bug. ***

Comment 7 Satoe Imaishi 2018-10-22 17:41:46 UTC

*** This bug has been marked as a duplicate of bug 1639213 ***