test_volume_extend fails with timeout error

Bug #1376421 reported by Armando Migliaccio
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
Invalid
Medium
Unassigned
tempest
Invalid
Undecided
Unassigned

Bug Description

This failure has been observed in the gate:

http://logs.openstack.org/24/123624/3/check/check-tempest-dsvm-neutron-full-2/5cad17d/logs/testr_results.html.gz

The stacktrace is:

Traceback (most recent call last):
  File "tempest/api/volume/test_volumes_extend.py", line 34, in test_volume_extend
    self.volume = self.create_volume()
  File "tempest/api/volume/base.py", line 103, in create_volume
    cls.volumes_client.wait_for_volume_status(volume['id'], 'available')
  File "tempest/services/volume/json/volumes_client.py", line 181, in wait_for_volume_status
    raise exceptions.TimeoutException(message)
TimeoutException: Request timed out
Details: Volume ab3d0a31-4aa7-463b-90f0-6b17daef2cc6 failed to reach available status within the required time (196 s).

On test:

test_volume_extend

Revision history for this message
John Griffith (john-griffith) wrote :

Where can I find actual logs for this run?

Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

My apologies, I thought it was implied there were in:

http://logs.openstack.org/24/123624/3/check/check-tempest-dsvm-neutron-full-2/5cad17d

Is that what you're looking for?

Revision history for this message
John Griffith (john-griffith) wrote :

@Armando
Thanks!! For some reason I couldn't extract them from the link you gave.

Revision history for this message
John Griffith (john-griffith) wrote :

Wow! So we're just completely blowing the timeout here it looks like. Tracing the volume-create in the c-vol log the create comes in and does complete succesfully; however.... it looks like just the create is taking over 3 minutes??

Start of create process:
http://logs.openstack.org/24/123624/3/check/check-tempest-dsvm-neutron-full-2/5cad17d/logs/screen-c-vol.txt.gz#_2014-10-01_18_57_37_592

Completion and update to success:
http://logs.openstack.org/24/123624/3/check/check-tempest-dsvm-neutron-full-2/5cad17d/logs/screen-c-vol.txt.gz#_2014-10-01_19_00_54_426

seems like we're crushing the Instance maybe, trying to figure out how/why the create is all hung up.

Changed in cinder:
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
John Griffith (john-griffith) wrote :

BTW, I started poking around kernel and syslogs to see if I could find any hints to why an lvcreate that normally takes a second or two is taking over 3 minutes and there's all sorts of ugliness going on:

http://logs.openstack.org/24/123624/3/check/check-tempest-dsvm-neutron-full-2/5cad17d/logs/kern_log.txt.gz#_Oct__1_18_52_49

and

http://logs.openstack.org/24/123624/3/check/check-tempest-dsvm-neutron-full-2/5cad17d/logs/syslog.txt.gz#_Oct__1_18_46_27

Revision history for this message
Mike Perez (thingee) wrote :

Pretty sure this is related to https://bugs.launchpad.net/cinder/+bug/1376941

Revision history for this message
Ghanshyam Mann (ghanshyammann) wrote :

From above analysis, it looks like nothing to do with tempest. Please feel free to open in case of any tempest update required.

Changed in tempest:
status: New → Invalid
Revision history for this message
Sean McGinnis (sean-mcginnis) wrote : Bug Cleanup

Closing stale bug. If this is still an issue please reopen.

Changed in cinder:
status: Triaged → Invalid
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.