Bug 1492464

Summary: Clearer message when trying to upload a plan with a name that already exists
Product: Red Hat OpenStack Reporter: Udi <ukalifon>
Component: openstack-tripleo-commonAssignee: Jiri Tomasek <jtomasek>
Status: CLOSED ERRATA QA Contact: Udi <ukalifon>
Severity: low Docs Contact:
Priority: low    
Version: 12.0 (Pike)CC: akrivoka, beth.white, jjoyce, jschluet, jtomasek, mburns, slinaber, tvignaud, ukalifon
Target Milestone: Upstream M3Keywords: Triaged
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: openstack-tripleo-common-8.4.1-0.20180224032817.d51ed49.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-06-27 13:36:16 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 Flags
Screenshot showing the UI displays the relevant error message
Plan Creation Failed none

Description Udi 2017-09-17 13:49:54 UTC
Description of problem:
When you upload 2 plans with the same name, you get an error message saying "plan creation failed" with no details why.

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

How reproducible:

Steps to Reproduce:
1. Upload the same plan twice, with the same name

Actual results:
The error message says "plan creation failed"

Expected results:
The error message should say "a plan with this name already exists"

Comment 4 Ana Krivokapic 2018-01-29 12:19:51 UTC
Created attachment 1387732 [details]
Screenshot showing the UI displays the relevant error message

Comment 5 Ana Krivokapic 2018-01-29 12:20:25 UTC
Could not reproduce this (see screenshot). Could you re-test please.

Comment 6 Udi 2018-01-29 13:15:51 UTC
Created attachment 1387790 [details]
Plan Creation Failed

I'm only getting "Plan Creation Failed" with no additional info. See my screenshot. 

Jiri said he fixed a similar bug, in which the details of the error message did not appear in the minified version of the code. Maybe you can ask him if we're lucky and his fix will cover this bug too (or if he only fixed it for errors coming from heat).

Comment 7 Ana Krivokapic 2018-01-29 13:30:36 UTC
Jirka, any ideas on this one?

Comment 8 Jiri Tomasek 2018-01-29 13:54:58 UTC
Yes, https://bugzilla.redhat.com/show_bug.cgi?id=1492728#c8 fixes the error handling issues in production. This bug should be fixed by it too.

Comment 9 Ana Krivokapic 2018-01-29 15:53:45 UTC
So this is caused by the same underlying issue as BZ1492728. I'll link the appropriate patches and re-assign to Jirka.

Comment 11 Udi 2018-04-15 09:45:52 UTC
Verified in: 

Comment 13 errata-xmlrpc 2018-06-27 13:36:16 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.