Bug 1376470

Summary:	Reusing a deleted deployment name results in error message
Product:	Red Hat Quickstart Cloud Installer	Reporter:	Thom Carlin <tcarlin>
Component:	WebUI	Assignee:	cchase
Status:	CLOSED ERRATA	QA Contact:	Tasos Papaioannou <tpapaioa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	1.0	CC:	cchase, tpapaioa, tsanders
Target Milestone:	---	Keywords:	Triaged
Target Release:	1.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-02-28 01:39:45 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

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