Project

General

Profile

Actions
Copy link

Bug #44236

open

Unlocking lab machines is not intuitive

Added by Nathan Cutler about 4 years ago. Updated almost 4 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Crash signature (v1):
Crash signature (v2):

Description

I locked a smithi using a command like this:

teuthology-lock --machine-type smithi --lock-many 1 --os-type opensuse --os-version 15.2 --owner foo

This worked great, however:

(virtualenv) smithfarm@teuthology:~/teuthology$ teuthology-lock -a --brief | grep smithfarm
smithi183.front.sepia.ceph.com   locked smithfarm "None" 
(virtualenv) smithfarm@teuthology:~/teuthology$ teuthology-lock --unlock smithi183.front.sepia.ceph.com
2020-02-21 09:59:38,920.920 ERROR:teuthology.lock.ops:Failed to unlock: smithi183.front.sepia.ceph.com

With some help from Thomas Bechtold, I was able to unlock it by doing something like this:

$ teuthology-lock --list-targets --owner smithfarm > mine.yml
$ teuthology-nuke -t mine.yml -r -u --owner smithfarm
Actions
Copy link

Also available in: Atom PDF