[RFE] Create way to reset validations data

Bug #1657853 reported by Dan Trainor
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Expired
Undecided
Unassigned

Bug Description

Validations data is very persistent. A way to reset all the validations data to the state that you'd find the validations data in before running any validations would help with troubleshooting or otherwise re-running validations.

This is likely to be a Mistral action.

Tags: ui validations
Dan Trainor (dtrainor)
description: updated
Changed in tripleo:
status: New → Triaged
importance: Undecided → Low
Changed in tripleo:
milestone: none → pike-1
Changed in tripleo:
milestone: pike-1 → pike-2
Changed in tripleo:
milestone: pike-2 → pike-3
Changed in tripleo:
milestone: pike-3 → pike-rc1
Changed in tripleo:
milestone: pike-rc1 → queens-1
Changed in tripleo:
milestone: queens-1 → queens-2
Changed in tripleo:
milestone: queens-2 → queens-3
Revision history for this message
Liz Blanchard (lblanchard) wrote :

Dan - Do you envision a user doing this through the UI? Just making sure in case there are mock ups needed :)

Revision history for this message
Dan Trainor (dtrainor) wrote :

I think that since there is already a visual indication that a validation has run / passed / failed, there should be a way in the UI to either reset the validations data on an individual basis or all at once. That being said, yes, I do envision a user doing this through the UI. Mockups may be necessary :)

Changed in tripleo:
milestone: queens-3 → queens-rc1
Changed in tripleo:
milestone: queens-rc1 → rocky-1
Changed in tripleo:
milestone: rocky-1 → rocky-2
Changed in tripleo:
milestone: rocky-2 → rocky-3
Changed in tripleo:
milestone: rocky-3 → rocky-rc1
Changed in tripleo:
milestone: rocky-rc1 → stein-1
Changed in tripleo:
milestone: stein-1 → stein-2
Revision history for this message
Emilien Macchi (emilienm) wrote : Cleanup EOL bug report

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (FUTURE, PIKE, QUEENS, ROCKY, STEIN).
  Valid example: CONFIRMED FOR: FUTURE

Changed in tripleo:
importance: Low → Undecided
status: Triaged → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.