Sometimes tempest.scenario.test_network_basic_ops.TestNetworkBasicOps.test_network_basic_ops fail via port in state Down

Bug #1710845 reported by Sofiia Andriichenko
30
This bug affects 6 people
Affects Status Importance Assigned to Milestone
tempest
New
Undecided
Unassigned

Bug Description

Description: Sometimes tempest.scenario.test_network_basic_ops.TestNetworkBasicOps.test_network_basic_ops fail via port in state Down, it can not get in time status ACTIVE

Trace:
tempest.scenario.test_network_basic_ops.TestNetworkBasicOps.test_network_basic_ops
----------------------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/rally/.rally/verification/verifier-1d2512ee-7146-486f-8ac2-de4b8a666e52/repo/tempest/test.py", line 103, in wrapper
    return f(self, *func_args, **func_kwargs)
  File "/home/rally/.rally/verification/verifier-1d2512ee-7146-486f-8ac2-de4b8a666e52/repo/tempest/scenario/test_network_basic_ops.py", line 398, in test_network_basic_ops
    self._setup_network_and_servers()
  File "/home/rally/.rally/verification/verifier-1d2512ee-7146-486f-8ac2-de4b8a666e52/repo/tempest/scenario/test_network_basic_ops.py", line 122, in _setup_network_and_servers
    floating_ip = self.create_floating_ip(server)
  File "/home/rally/.rally/verification/verifier-1d2512ee-7146-486f-8ac2-de4b8a666e52/repo/tempest/scenario/manager.py", line 844, in create_floating_ip
    port_id, ip4 = self._get_server_port_id_and_ip4(thing)
  File "/home/rally/.rally/verification/verifier-1d2512ee-7146-486f-8ac2-de4b8a666e52/repo/tempest/scenario/manager.py", line 822, in _get_server_port_id_and_ip4
    "No IPv4 addresses found in: %s" % ports)
  File "/home/rally/.rally/verification/verifier-1d2512ee-7146-486f-8ac2-de4b8a666e52/repo/tempest/test.py", line 680, in assertNotEmpty
    self.assertTrue(items, msg)
  File "/usr/local/lib/python2.7/dist-packages/unittest2/case.py", line 702, in assertTrue
    raise self.failureException(msg)
AssertionError: [] is not true : No IPv4 addresses found in: [{u'allowed_address_pairs': [], u'extra_dhcp_opts': [], u'updated_at': u'2017-08-15T09:27:57Z', u'device_owner': u'compute:None', u'revision_number': 7, u'port_security_enabled': True, u'binding:profile': {}, u'fixed_ips': [{u'subnet_id': u'c990e714-13d7-4d77-add2-a58f13cbd9e1', u'ip_address': u'10.100.0.13'}], u'id': u'a2e76fb8-687e-4ba1-a410-d6ef44e8e63d', u'security_groups': [u'2cc793f9-c452-4673-a6eb-2fe0814c3c0e'], u'binding:vif_details': {u'port_filter': True, u'ovs_hybrid_plug': True}, u'binding:vif_type': u'ovs', u'mac_address': u'fa:16:3e:cc:f4:44', u'project_id': u'84393730e1f94f4489ea2a879e6dbb26', u'status': u'DOWN', u'binding:host_id': u'cfg01', u'description': u'', u'tags': [], u'device_id': u'160942cc-813c-4bed-8733-c0290df7112f', u'name': u'', u'admin_state_up': True, u'network_id': u'730405cc-fce0-41be-bf3b-c8c47b1b4c97', u'tenant_id': u'84393730e1f94f4489ea2a879e6dbb26', u'created_at': u'2017-08-15T09:27:56Z', u'binding:vnic_type': u'normal'}]

======
Totals
======

Ran: 1 tests in 24.242 sec.
 - Success: 0
 - Skipped: 0
 - Expected failures: 0
 - Unexpected success: 0
 - Failures: 1

Changed in tempest:
assignee: nobody → Sofiia Andriichenko (sandriichenko)
Revision history for this message
zhufl (zhu-fanglei) wrote :

3 patches have been trying to solve the similar problem, maybe we need more discussion.
And would you please read the following patchhes to see if any other opinion
https://review.openstack.org/#/c/477445
https://review.openstack.org/#/c/383049
https://review.openstack.org/#/c/367113

Revision history for this message
Slawek Kaplonski (slaweq) wrote :

Do You have link to logs of such failed test? I would like to take a look why port was DOWN all time.

Revision history for this message
Manik Bindlish (manikbindlish19) wrote :

I think, merging of https://review.openstack.org/#/c/383049 will solve the purpose of this issue.

Revision history for this message
Attila Fazekas (afazekas) wrote :

The port implicitly created with the machine should not be down state after the machine become active, the interfaces added later may require time for being wired.

Revision history for this message
Manik Bindlish (manikbindlish19) wrote :

@Sofiia Andriichenko: Are you still working on this issue or should we move it to un-assigned category so that someone can assign it and fix it?

Revision history for this message
Manik Bindlish (manikbindlish19) wrote :

One more issue of similar type on which work is still in progress: https://bugs.launchpad.net/tempest/+bug/1728600

Revision history for this message
Martin Kopec (mkopec) wrote :

Long inactivity.

Changed in tempest:
assignee: Sofiia Andriichenko (sandriichenko) → nobody
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.