Believe this can be marked invalid for Nova.
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1226337
Title:
tempest.scenario.test_volume_boot_pattern.TestVolumeBootPattern flake
failure
Status in Cinder:
Fix Committed
Status in OpenStack Compute (Nova):
Invalid
Status in Tempest:
Triaged
Bug description:
When running tempest
tempest.scenario.test_volume_boot_pattern.TestVolumeBootPattern.test_volume_boot_pattern
fails with the server going into an ERROR state.
From the console log:
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.
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
Logs are located here:
http://logs.openstack.org/64/47264/2/gate/gate-tempest-devstack-vm-full/dced339
-----------------
Originally the failure was (before some changes to timeouts in
tempest):
t178.1:
tempest.scenario.test_volume_boot_pattern.TestVolumeBootPattern.test_volume_boot_pattern[compute,image,volume]_StringException:
Empty attachments:
stderr
stdout
pythonlogging:'': {{{
2013-09-16 15:59:44,214 Starting new HTTP connection (1): 127.0.0.1
2013-09-16 15:59:44,417 Starting new HTTP connection (1): 127.0.0.1
2013-09-16 15:59:45,348 Starting new HTTP connection (1): 127.0.0.1
2013-09-16 15:59:45,495 Starting new HTTP connection (1): 127.0.0.1
2013-09-16 15:59:47,644 Starting new HTTP connection (1): 127.0.0.1
2013-09-16 15:59:48,762 Starting new HTTP connection (1): 127.0.0.1
2013-09-16 15:59:49,879 Starting new HTTP connection (1): 127.0.0.1
2013-09-16 15:59:50,980 Starting new HTTP connection (1): 127.0.0.1
2013-09-16 16:00:52,581 Connected (version 2.0, client dropbear_2012.55)
2013-09-16 16:00:52,897 Authentication (publickey) successful!
2013-09-16 16:00:53,105 Connected (version 2.0, client dropbear_2012.55)
2013-09-16 16:00:53,428 Authentication (publickey) successful!
2013-09-16 16:00:53,431 Secsh channel 1 opened.
2013-09-16 16:00:53,607 Connected (version 2.0, client dropbear_2012.55)
2013-09-16 16:00:53,875 Authentication (publickey) successful!
2013-09-16 16:00:53,880 Secsh channel 1 opened.
2013-09-16 16:01:58,999 Connected (version 2.0, client dropbear_2012.55)
2013-09-16 16:01:59,288 Authentication (publickey) successful!
2013-09-16 16:01:59,457 Connected (version 2.0, client dropbear_2012.55)
2013-09-16 16:01:59,784 Authentication (publickey) successful!
2013-09-16 16:01:59,801 Secsh channel 1 opened.
2013-09-16 16:02:00,005 Starting new HTTP connection (1): 127.0.0.1
2013-09-16 16:02:00,080 Starting new HTTP connection (1): 127.0.0.1
2013-09-16 16:02:01,127 Starting new HTTP connection (1): 127.0.0.1
2013-09-16 16:02:01,192 Starting new HTTP connection (1): 127.0.0.1
2013-09-16 16:02:01,414 Starting new HTTP connection (1): 127.0.0.1
2013-09-16 16:02:02,494 Starting new HTTP connection (1): 127.0.0.1
2013-09-16 16:02:03,615 Starting new HTTP connection (1): 127.0.0.1
2013-09-16 16:02:04,724 Starting new HTTP connection (1): 127.0.0.1
2013-09-16 16:02:05,825 Starting new HTTP connection (1): 127.0.0.1
}}}
Traceback (most recent call last):
File "tempest/scenario/test_volume_boot_pattern.py", line 157, in
test_volume_boot_pattern
ssh_client = self._ssh_to_server(instance_from_snapshot, keypair)
File "tempest/scenario/test_volume_boot_pattern.py", line 101, in
_ssh_to_server
private_key=keypair.private_key)
File "tempest/scenario/manager.py", line 453, in get_remote_client
return RemoteClient(ip, username, pkey=private_key)
File "tempest/common/utils/linux/remote_client.py", line 47, in __init__
if not self.ssh_client.test_connection_auth():
File "tempest/common/ssh.py", line 148, in test_connection_auth
connection = self._get_ssh_connection()
File "tempest/common/ssh.py", line 70, in _get_ssh_connection
time.sleep(bsleep)
File
"/usr/local/lib/python2.7/dist-packages/fixtures/_fixtures/timeout.py", line
52, in signal_handler
raise TimeoutException()
TimeoutException
Full logs here:
http://logs.openstack.org/80/43280/9/gate/gate-tempest-devstack-vm-
full/cba22ae/testr_results.html.gz
Looks a bit like the instance failed to boot.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1226337/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
