Actions
Bug #6164
closedteuthology-lock --unlock vpmXXX leaves uncleanable VM if downburst not found
Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
% Done:
0%
Source:
Development
Tags:
Backport:
Regression:
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Crash signature (v1):
Crash signature (v2):
Description
I don't conform to teuthology's ideas about having downburst in my path all the time, so
I got into the hole of:
1) lock a vps successfully (with downburst in path)
2) unlock from a different shell (without downburst)
2) fails because it can't find downburst to destroy the vm, but it fails after
unlocking on the lock server, so the vpm appears unlocked, and further --unlocks,
even with downburst available, fail.
lock.py should check for downburst before doing the lockserver transaction.
Actions