[nailgun] ostf results aren't cleared after resetting environment
Bug #1338669 reported by
Andrew Woodward
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Triaged
|
Low
|
Fuel Sustaining | ||
| Mitaka |
Won't Fix
|
Low
|
Fuel Python (Deprecated) | ||
| Newton |
Triaged
|
Low
|
Fuel Sustaining | ||
Bug Description
After you reset an environment the ostf test results from the last env are still displayed.
steps to reproduce.
deploy env
run tests
reset env
veiw status on ostf page after rest
expected result: test status should be cleared.
| Changed in fuel: | |
| assignee: | nobody → Fuel Python Team (fuel-python) |
| milestone: | none → 5.1 |
Revision history for this message
| Dima Shulyak (dshulyak) wrote | #1 |
| Changed in fuel: | |
| status: | New → Confirmed |
| summary: |
- ostf results aren't cleared after resetting environment + [nailgun] ostf results aren't cleared after resetting environment |
Revision history for this message
| Dima Shulyak (dshulyak) wrote | #2 |
| Changed in fuel: | |
| milestone: | 5.1 → 6.0 |
| tags: | added: release-notes |
| Changed in fuel: | |
| milestone: | 6.0 → 6.1 |
| tags: | added: feature |
| tags: |
added: feature-reset-env module-ostf removed: ostf |
Revision history for this message
| Dmitry Pyzhov (dpyzhov) wrote | #3 |
| Changed in fuel: | |
| milestone: | 6.1 → 7.0 |
| tags: | added: qa-agree-7.0 |
Revision history for this message
| Vladimir Sharshov (vsharshov) wrote | #4 |
| tags: | added: known-issue |
| Changed in fuel: | |
| status: | Confirmed → Won't Fix |
| Changed in fuel: | |
| milestone: | 7.0 → 8.0 |
| no longer affects: | fuel/8.0.x |
| tags: | added: area-python |
Revision history for this message
| Evgeny Sikachev (esikachev) wrote | #5 |
Revision history for this message
| Alexander Kislitsky (akislitsky) wrote | #6 |
| Changed in fuel: | |
| milestone: | 8.0 → 9.0 |
| tags: |
added: area-ostf removed: module-ostf |
| tags: | removed: release-notes |
To post a comment you must log in.
We can store cluster status, and cleanup tests if it is changed, in some scenarios ofcourse.