VM's are not destroyed at the end of the tests for saucy smoke tests
Bug #1178241 reported by
Para Siva
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| UTAH |
Fix Released
|
Critical
|
Max Brustkern | ||
Bug Description
With utah version utah-common_
The issue is not occurring in the jobs using utah-common_
The jobs do not have -n flag on them to have kept the VMs deliberately.
This is happening with all the VMs in the saucy smoke tests and it's cluttering the server.
'Stopping VM' and 'Forced shutdown requested' can not be seen in the utah-server.log in the corresponding jobs.
Related branches
lp://staging/~nuclearbob/utah/bug1178241
- Javier Collado (community): Approve
-
Diff: 142 lines (+94/-14)3 files modifieddebian/changelog (+5/-1)
tests/test_vm.py (+67/-0)
utah/provisioning/vm.py (+22/-13)
| summary: |
- VM's are not destroyed at the end of the tests for saucy raring smoke - tests + VM's are not destroyed at the end of the tests for saucy smoke tests |
| Changed in utah: | |
| importance: | Undecided → Critical |
| Changed in utah: | |
| assignee: | nobody → Max Brustkern (nuclearbob) |
| Changed in utah: | |
| milestone: | none → 0.12.2 |
| status: | New → Fix Committed |
| Changed in utah: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
