Bug 1492456

Summary: Instead of an error message, I get a success message when I upload a bad file as a plan
Product: Red Hat OpenStack Reporter: Udi <ukalifon>
Component: openstack-tripleo-uiAssignee: Ana Krivokapic <akrivoka>
Status: CLOSED ERRATA QA Contact: Udi <ukalifon>
Severity: medium Docs Contact:
Priority: medium    
Version: 12.0 (Pike)CC: beth.white, jjoyce, jschluet, slinaber, tvignaud
Target Milestone: Upstream M2Keywords: Triaged
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-ui-8.2.1-0.20180227100337.517cd78.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 Udi 2017-09-17 13:17:17 UTC
Description of problem:
In the Plans page, I selected a plan and clicked "Edit", and I uploaded a png image instead of a .tar.gz archive. I got a success message "The plan plan1 was successfully updated", although it really wasn't updated and I should have gotten an error message.


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. Navigate to the Plans page
2. For one of the plans, click on the kebab menu and click "Edit"
3. Upload a new file instead of the .tar.gz file (I used a png file in my example)
4. Click "Upload Files and Create Plan"


Actual results:
You get a success message, although the plan wasn't updated at all.


Expected results:
Error message.

Comment 5 Udi 2018-04-15 09:43:47 UTC
Verified in: openstack-tripleo-ui-8.3.1-2.el7ost.noarch

Comment 7 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.

https://access.redhat.com/errata/RHEA-2018:2086