TestNetworkAdvancedServerOps.test_server_connectivity_resize fails

Bug #1307029 reported by Matt Riedemann
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
Undecided
Unassigned

Bug Description

http://logs.openstack.org/47/69047/18/check/check-tempest-dsvm-neutron/0fa44f7/console.html#_2014-04-12_20_22_18_001

2014-04-12 20:22:18.617 | Traceback (most recent call last):
2014-04-12 20:22:18.617 | File "tempest/test.py", line 122, in wrapper
2014-04-12 20:22:18.617 | return f(self, *func_args, **func_kwargs)
2014-04-12 20:22:18.617 | File "tempest/scenario/test_network_advanced_server_ops.py", line 198, in test_server_connectivity_resize
2014-04-12 20:22:18.617 | self._wait_server_status_and_check_network_connectivity()
2014-04-12 20:22:18.617 | File "tempest/scenario/test_network_advanced_server_ops.py", line 141, in _wait_server_status_and_check_network_connectivity
2014-04-12 20:22:18.617 | self._check_network_connectivity()
2014-04-12 20:22:18.617 | File "tempest/scenario/test_network_advanced_server_ops.py", line 136, in _check_network_connectivity
2014-04-12 20:22:18.617 | should_connect=should_connect)
2014-04-12 20:22:18.617 | File "tempest/scenario/test_network_advanced_server_ops.py", line 119, in _check_public_network_connectivity
2014-04-12 20:22:18.617 | should_connect=should_connect)
2014-04-12 20:22:18.617 | File "tempest/scenario/manager.py", line 777, in _check_vm_connectivity
2014-04-12 20:22:18.618 | msg=msg)
2014-04-12 20:22:18.618 | File "/usr/lib/python2.7/unittest/case.py", line 420, in assertTrue
2014-04-12 20:22:18.618 | raise self.failureException(msg)
2014-04-12 20:22:18.618 | AssertionError: Timed out waiting for 172.24.4.41 to become reachable

message:"FAIL: tempest.scenario.test_network_advanced_server_ops.TestNetworkAdvancedServerOps.test_server_connectivity_resize" AND tags:console

http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiRkFJTDogdGVtcGVzdC5zY2VuYXJpby50ZXN0X25ldHdvcmtfYWR2YW5jZWRfc2VydmVyX29wcy5UZXN0TmV0d29ya0FkdmFuY2VkU2VydmVyT3BzLnRlc3Rfc2VydmVyX2Nvbm5lY3Rpdml0eV9yZXNpemVcIiBBTkQgdGFnczpjb25zb2xlIiwiZmllbGRzIjpbXSwib2Zmc2V0IjowLCJ0aW1lZnJhbWUiOiI2MDQ4MDAiLCJncmFwaG1vZGUiOiJjb3VudCIsInRpbWUiOnsidXNlcl9pbnRlcnZhbCI6MH0sInN0YW1wIjoxMzk3MzM3NTY5OTU4fQ==

54 hits in 7 days, all failures. Only happens on neutron jobs.

Revision history for this message
Matt Riedemann (mriedem) wrote :

Seeing a lot of warnings like this in the n-cpu logs:

WARNING nova.network.neutronv2.api [-] [instance: bcaa46a8-4034-4f93-8cdb-7d729461550b] No network configured!

The instance in the failure above is cbe6a1cb-1f54-4173-81a7-ef8cad77de07 and I'm not seeing any errors in the neutron server log for that port. Looks like the IP is allocated here:

http://logs.openstack.org/47/69047/18/check/check-tempest-dsvm-neutron/0fa44f7/logs/screen-q-svc.txt.gz#_2014-04-12_20_03_16_899

Maybe this is related to the ssh bug 1253896 with neutron?

Revision history for this message
Matt Riedemann (mriedem) wrote :
Revision history for this message
Joe Gordon (jogo) wrote :

Not seeing this in the gate anymore. marking it as fixed.

Changed in nova:
status: New → Fix Committed
Changed in nova:
milestone: none → juno-2
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in nova:
milestone: juno-2 → 2014.2
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.