Bug 1492464 – Clearer message when trying to upload a plan with a name that already exists

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1492464 - Clearer message when trying to upload a plan with a name that already exists

Summary:	Clearer message when trying to upload a plan with a name that already exists

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat OpenStack
Classification:	Red Hat
Component:	openstack-tripleo-common (Show other bugs)
Sub Component:
Version:	12.0 (Pike)
Hardware:	Unspecified Unspecified

Priority	low Severity low
Target Milestone:	Upstream M3
Target Release:	13.0 (Queens)
Assigned To:	Jiri Tomasek
QA Contact:	Udi
Docs Contact:

URL:
Whiteboard:
Keywords:	Triaged

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2017-09-17 09:49 EDT by Udi
Modified:	2018-06-27 09:37 EDT (History)
CC List:	9 users (show)

See Also:
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 09:36:16 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Screenshot showing the UI displays the relevant error message (30.26 KB, image/png) 2018-01-29 07:19 EST, Ana Krivokapic	no flags	Details
Plan Creation Failed (109.76 KB, image/png) 2018-01-29 08:15 EST, Udi	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Bugzilla	1492728	None	CLOSED	Occasionally, you get "Deployment parameters could not be loaded" when editing parameters of enabled environment files	2018-07-16 09:18 EDT
Launchpad	1745944	None	None	None	2018-01-29 10:55 EST
OpenStack gerrit	538844	None	master: MERGED	tripleo-ui: Set error names explicitly (Id0ae3b9427a07a1910e7a6976da76a06abb104f1)	2018-02-28 08:36 EST
Red Hat Product Errata	RHEA-2018:2086	None	None	None	2018-06-27 09:37 EDT

Groups: None (edit)

Description Udi 2017-09-17 09:49:54 EDT

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):
openstack-tripleo-ui-7.2.1-0.20170819031831.070a522.el7ost.noarch


How reproducible:
100%


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 07:19 EST

Created attachment 1387732 [details]
Screenshot showing the UI displays the relevant error message

Comment 5 Ana Krivokapic 2018-01-29 07:20:25 EST

Could not reproduce this (see screenshot). Could you re-test please.

Comment 6 Udi 2018-01-29 08:15 EST

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 08:30:36 EST

Jirka, any ideas on this one?

Comment 8 Jiri Tomasek 2018-01-29 08:54:58 EST

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 10:53:45 EST

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 05:45:52 EDT

Verified in: 
openstack-tripleo-ui-8.3.1-2.el7ost.noarch
openstack-tripleo-common-8.5.1-0.20180326153322.91f52e9.el7ost.noarch

Comment 13 errata-xmlrpc 2018-06-27 09:36:16 EDT

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-2018:2086

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