Project

General

Profile

Actions
Copy link

Bug #16534

open

teuthology-lock still locks a vm when the downburst PATH is invalid.

Added by Anonymous almost 8 years ago. Updated over 7 years ago.

Status:
Need More Info
Priority:
Normal
Assignee:
-
Category:
-
% Done:

0%

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

Description

my ~/.teuthology.yaml file had a non-existent downburst file in it. The downburst failed and teuthology-lock left a trace, but the vm still got locked.

Actions
Copy link
 #1

Updated by Anonymous almost 8 years ago

I also did not have my public key in the .ssh/authorized_keys file on the host machine where I was trying to lock the vm. This may have also confused the issue.

Actions
Copy link
 #2

Updated by Zack Cerza over 7 years ago

  • Status changed from New to Need More Info
  • Assignee set to Anonymous

What does "my ~/.teuthology.yaml file had a non-existent downburst file in it" mean ?

Actions
Copy link

Also available in: Atom PDF