test_volume_boot_pattern NovaException: iSCSI device not found at

Bug #1229590 reported by Attila Fazekas
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
New
Undecided
Unassigned

Bug Description

iSCSI device not available in time.

The exception:
http://logs.openstack.org/64/47264/2/gate/gate-tempest-devstack-vm-full/dced339/logs/screen-n-cpu.txt.gz#_2013-09-24_04_44_31_806

Possible log stash query:
@tags:"logs/screen-n-cpu.txt" AND @message:"ISCSI volume not yet found at: vda. Will rescan & retry. Try number: 2"

2013-09-24 04:16:36.948 | Traceback (most recent call last):
2013-09-24 04:16:36.948 | File "tempest/scenario/test_volume_boot_pattern.py", line 154, in test_volume_boot_pattern
2013-09-24 04:16:36.948 | keypair)
2013-09-24 04:16:36.948 | File "tempest/scenario/test_volume_boot_pattern.py", line 53, in _boot_instance_from_volume
2013-09-24 04:16:36.948 | create_kwargs=create_kwargs)
2013-09-24 04:16:36.948 | File "tempest/scenario/manager.py", line 390, in create_server
2013-09-24 04:16:36.949 | self.status_timeout(client.servers, server.id, 'ACTIVE')
2013-09-24 04:16:36.949 | File "tempest/scenario/manager.py", line 290, in status_timeout
2013-09-24 04:16:36.949 | self._status_timeout(things, thing_id, expected_status=expected_status)
2013-09-24 04:16:36.949 | File "tempest/scenario/manager.py", line 338, in _status_timeout
2013-09-24 04:16:36.949 | self.config.compute.build_interval):
2013-09-24 04:16:36.949 | File "tempest/test.py", line 237, in call_until_true
2013-09-24 04:16:36.950 | if func():
2013-09-24 04:16:36.950 | File "tempest/scenario/manager.py", line 329, in check_status
2013-09-24 04:16:36.950 | raise exceptions.BuildErrorException(message)
2013-09-24 04:16:36.950 | BuildErrorException: Server %(server_id)s failed to build and is in ERROR status
2013-09-24 04:16:36.950 | Details: <Server: scenario-server-89179012> failed to get to expected status. In ERROR state.

It is not the #1221987, but #1205344 is a similar issue.

Revision history for this message
Matthew Treinish (treinish) wrote :

This looks like a dup of 1226337. The message in console is different but the underlying issue seems to be the same.

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.