ceph smoketest jobs do not honor timeout

Bug #1085835 reported by Jean-Baptiste Lallement
This bug report is a duplicate of:  Bug #1169510: UTAH doesn't honor jobtimeout. Edit Remove
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
UTAH
Triaged
Medium
Unassigned

Bug Description

The ceph smoketest jobs do not time out and ran for more than 2 days despite timeout is defined in ts_control and tc_control files

for example:
http://10.98.0.1:8080/job/raring-server-i386-smoke-ceph/12/
http://10.98.0.1:8080/job/raring-server-amd64-smoke-ceph/14/

Changed in utah:
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Max Brustkern (nuclearbob) wrote :

I'm looking into this. On the test run I ran to recreate it, the UTAH state file indicated all tests were done executing within a few hours, but the process didn't return for some reason. I'll continue dissecting the process to try to ascertain why.

Revision history for this message
Max Brustkern (nuclearbob) wrote :

When I logged into the machine to run the testsuite, it returned within several hours. I'm getting a more exact time so I can determine if the SSH session is timing out.

Revision history for this message
Joe Talbott (joetalbott) wrote :

http://10.98.0.1:8080/view/Raring/view/Smoke%20Testing/job/raring-server-amd64-smoke-ceph/31/console is an example of this happening too. Paul Larson logged into the console and found that utah was still running and strace showed:

write(1, "ved\nPackage 'libapache2-mod-"..., 4096^C<unfinished...>

I think this is related to the truncated logs issue we have. It looks like we might be filling up the stdout buffer space or something.

Revision history for this message
Joe Talbott (joetalbott) wrote :
summary: - ceph smoketest jobs do not honore timeout
+ ceph smoketest jobs do not honor timeout
Revision history for this message
Max Brustkern (nuclearbob) wrote :

I think we've fixed this. Is it still occurring?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.