Bug 1470584

Summary: Validation results are not deleted when deleting the plan
Product: Red Hat OpenStack Reporter: Udi Kalifon <ukalifon>
Component: openstack-tripleo-uiAssignee: Florian Fuchs <flfuchs>
Status: CLOSED ERRATA QA Contact: Ola Pavlenko <opavlenk>
Severity: medium Docs Contact:
Priority: medium    
Version: 11.0 (Ocata)CC: beth.white, dtrainor, flfuchs, jjoyce, jschluet, rhel-osp-director-maint, slinaber, tvignaud
Target Milestone: rcKeywords: Triaged
Target Release: 12.0 (Pike)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-ui-7.4.3-3.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-13 21:40:04 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:
Embargoed:

Description Udi Kalifon 2017-07-13 09:08:37 UTC 
Description of problem:
If you delete a plan and create a new one with the same name - the validation results from the previous incarnation of the plan are still persisted.


Version-Release number of selected component (if applicable):
openstack-tripleo-ui-3.2.0-1.el7ost.noarch


How reproducible:
100 %


Steps to Reproduce:
1. Create a plan and make sure all the validators are in initial state (not run). Note that the pre-deployment validators might start automatically but that's OK.
2. Run a few validators. For example I ran the pacemaker validator and it passed (even if there was no overcloud yet).
3. Delete the plan.
4. Create a new plan with the same name.


Actual results:
The results of the validators that were run on the old plan with the same name are displayed, even though this is really not the same plan.
Comment 2 Beth White 2017-11-03 10:18:10 UTC 
backporting to stable/pike
Comment 4 Dan Trainor 2017-11-20 20:42:59 UTC 
A plan uploaded with the same name has all the validation states associated with it reset.  This passes.
Comment 7 errata-xmlrpc 2017-12-13 21:40:04 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:3462