Bug 1376470 - Reusing a deleted deployment name results in error message
Summary: Reusing a deleted deployment name results in error message
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Quickstart Cloud Installer
Classification: Red Hat
Component: WebUI
Version: 1.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 1.1
Assignee: cchase
QA Contact: Tasos Papaioannou
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-15 13:49 UTC by Thom Carlin
Modified: 2017-02-28 01:39 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-28 01:39:45 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:0335 0 normal SHIPPED_LIVE Red Hat Quickstart Installer 1.1 2017-02-28 06:36:13 UTC

Description Thom Carlin 2016-09-15 13:49:22 UTC 
Description of problem:

Reusing a deployment name resulted in error message

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

fusor-release

How reproducible:

1.0.0-3.el7_2

Steps to Reproduce:
1. New deployment: Name: test
2. Enter values to get to at least Installation Progress
3. Wait for deployment to get to a stopping point
4. Delete the deployment (using the web UI)
5. Wait for successful deletion
6. Try to create a new deployment: Name test

Actual results:

"This name is already in use.
generated label "test" is not unique"

Expected results:

Able to reuse name

Additional info:

May be able to reproduce earlier than Installation Progress.  Encountered this as the result of another issue

Workaround: Choose another name for the deployment
Comment 2 cchase 2016-09-23 20:18:58 UTC 
I cannot reproduce this issue in 1.1.  Can you reconfirm if this still happens in v1.1?
Comment 3 Tasos Papaioannou 2016-10-07 17:42:09 UTC 
Verified on QCI-1.1-RHEL-7-20161006.t.0.
Comment 6 errata-xmlrpc 2017-02-28 01:39:45 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2017:0335
Note You need to log in before you can comment on or make changes to this bug.