Project

General

Profile

Actions
Copy link

Bug #2277

open

qa: flock test broken

Added by Sage Weil about 12 years ago. Updated over 4 years ago.

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

0%

Source:
Q/A
Tags:
Backport:
Regression:
Severity:
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
qa-suite
Labels (FS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

ubuntu@teuthology:/a/nightly_coverage_2012-04-12-b/687
ubuntu@teuthology:/a/nightly_coverage_2012-04-11-b/525

this used to work...

Actions
Copy link
 #1

Updated by Greg Farnum about 12 years ago 

2012-04-12T13:58:11.463 INFO:teuthology.task.locktest.locktest.client.err:shared file create: Permission denied
2012-04-12T23:02:01.256 INFO:teuthology.task.ceph.mon.a.err:2012-04-12 23:02:01.253914 7fb978f50700 -1 mon.a@0(leader) e1 *** Got Signal Terminated ***
2012-04-12T23:02:01.256 INFO:teuthology.task.ceph.mon.b.err:2012-04-12 23:02:01.254069 7fd3d1a3c700 -1 mon.b@1(peon) e1 *** Got Signal Terminated ***
2012-04-12T23:02:01.257 INFO:teuthology.task.ceph.mon.c.err:2012-04-12 23:02:01.254043 7fad0791b700 -1 mon.c@2(peon) e1 *** Got Signal Terminated ***
2012-04-12T23:02:01.258 INFO:teuthology.task.ceph.mds.a.err:2012-04-12 23:02:01.255238 7ff909ead700 -1 mds.0.1 *** got signal Terminated ***
2012-04-12T23:05:26.547 ERROR:paramiko.transport:Socket exception: Connection reset by peer (104)

The error is coming out of the locktest.c executable from xfstests, complaining that it can't access the file it's supposed to be running on. Neither that file nor the locktest task in teuthology have changed in a very long time.
I'd look at the logs and try to figure out what's going on, but you'll see there that the client machine reset its connection, so there aren't any from that box.

So I'm thinking the kernel client got broken somehow. :(

Actions
Copy link
 #2

Updated by Greg Farnum about 12 years ago

  • Source changed from Development to Q/A

I was going to move this over to the kernel client project and then realized I can't — should we close this bug (reject?) and open another one in the right project? That's probably best in terms of the tracker but will skew our stats some.

Actions
Copy link
 #3

Updated by Sage Weil almost 12 years ago

  • Priority changed from High to Normal
Actions
Copy link
 #4

Updated by Ian Colle about 11 years ago

  • Status changed from 12 to Closed

No longer an issue.

Actions
Copy link
 #5

Updated by Greg Farnum about 11 years ago

  • Project changed from Ceph to teuthology
  • Category deleted (qa)
  • Status changed from Closed to 12

It's not an issue because these tests aren't being run any more. They should be run, though. ;)

That said, this wasn't a kclient issue; the test was based on timings rather than triggers and those timings weren't sufficiently deterministic. (At least, if I remember it correctly!)

Actions
Copy link
 #6

Updated by Sage Weil over 9 years ago

  • Project changed from teuthology to CephFS
Actions
Copy link
 #7

Updated by Greg Farnum over 7 years ago

  • Category set to Testing
  • Component(FS) qa-suite added
Actions
Copy link
 #8

Updated by John Spray over 7 years ago

For reference: locktest.py still exists in ceph-qa-suite, with a single use from suites/marginal/fs-misc/tasks/locktest.yaml -- should be presumed broken as afaik nobody runs that.

Actions
Copy link
 #9

Updated by Patrick Donnelly over 4 years ago

  • Status changed from 12 to New
Actions
Copy link

Also available in: Atom PDF