Project

General

Profile

Actions
Copy link

Bug #5394

closed

teuthology-lock should not fail silently when an invalid architecture is set.

Added by Anonymous almost 11 years ago. Updated over 9 years ago.

Status:
Can't reproduce
Priority:
Normal
Assignee:
-
Category:
-
% Done:

0%

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

Description

Background: I was testing on ARM machines and while doing so, I created a .teuthology.yaml file that had the entry: 'arch: armv7l' I blithely forgot about this when I started testing on the vms machines. Teuthology locks started to fail mysteriously. They did not return any output (hint that something's wrong but I missed it the first couple of times). Entries were added to the database, but the downbursts more than likely failed/did not run.

Actions
Copy link
 #1

Updated by Zack Cerza over 9 years ago

  • Assignee set to Anonymous
Actions
Copy link
 #2

Updated by Anonymous over 9 years ago

  • Status changed from New to Can't reproduce

I tried reproducing this on a few vms and could not get it to happen. I suspect that this has been fixed by downburst and teuthology lock changes implemented in the past year.

Actions
Copy link

Also available in: Atom PDF