Test test_network_basic_ops fails time to time, port doesn't become ACTIVE quickly

Bug #1728600 reported by Sofiia Andriichenko
34
This bug affects 7 people
Affects Status Importance Assigned to Milestone
tempest
Expired
Undecided
Unassigned

Bug Description

Test test_network_basic_ops fails time to time, port doesn't become ACTIVE quickly

Trace:
Traceback (most recent call last):
  File "tempest/scenario/test_security_groups_basic_ops.py", line 185, in setUp
    self._deploy_tenant(self.primary_tenant)
  File "tempest/scenario/test_security_groups_basic_ops.py", line 349, in _deploy_tenant
    self._set_access_point(tenant)
  File "tempest/scenario/test_security_groups_basic_ops.py", line 316, in _set_access_point
    self._assign_floating_ips(tenant, server)
  File "tempest/scenario/test_security_groups_basic_ops.py", line 322, in _assign_floating_ips
    client=tenant.manager.floating_ips_client)
  File "tempest/scenario/manager.py", line 836, in create_floating_ip
    port_id, ip4 = self._get_server_port_id_and_ip4(thing)
  File "tempest/scenario/manager.py", line 814, in _get_server_port_id_and_ip4
    "No IPv4 addresses found in: %s" % ports)
  File "/usr/local/lib/python2.7/dist-packages/unittest2/case.py", line 845, in assertNotEqual
    raise self.failureException(msg)
AssertionError: 0 == 0 : No IPv4 addresses found in: [{u'allowed_address_pairs': [], u'extra_dhcp_opts': [], u'updated_at': u'2017-10-30T10:04:41Z', u'device_owner': u'compute:None', u'revision_number': 9, u'port_security_enabled': True, u'binding:profile': {}, u'fixed_ips': [{u'subnet_id': u'd522b2e5-7e56-4d08-843c-c434c3c2af97', u'ip_address': u'10.100.0.12'}], u'id': u'20d59775-906d-4390-b193-a8ec81817ddb', u'security_groups': [u'908eb03d-2477-49ab-ab9a-fc9999fae454', u'cf62ee1b-eb73-44d0-9ad8-65bb32885505'], 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:02:f3:e8', u'project_id': u'0a8532fba2194d32996c3ba46ae35c96', u'status': u'BUILD', u'binding:host_id': u'cfg01', u'description': u'', u'tags': [], u'device_id': u'5ad8f2be-3cbb-49aa-8d72-e81ca6789665', u'name': u'', u'admin_state_up': True, u'network_id': u'49491fd4-2c1e-4c46-8166-b4648eb75f84', u'tenant_id': u'0a8532fba2194d32996c3ba46ae35c96', u'created_at': u'2017-10-30T10:04:37Z', u'binding:vnic_type': u'normal'}]

Ran 1 test in 25.096s

Changed in tempest:
assignee: nobody → Sofiia Andriichenko (sandriichenko)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tempest (master)

Fix proposed to branch: master
Review: https://review.openstack.org/516372

Changed in tempest:
status: New → In Progress
Changed in tempest:
assignee: Sofiia Andriichenko (sandriichenko) → Alina Nesterova (anesterova)
Changed in tempest:
assignee: Alina Nesterova (anesterova) → Pavlo Shchelokovskyy (pshchelo)
Changed in tempest:
assignee: Pavlo Shchelokovskyy (pshchelo) → Terry Wilson (otherwiseguy)
Revision history for this message
Manik Bindlish (manikbindlish19) wrote :
Revision history for this message
Manik Bindlish (manikbindlish19) wrote :

One more which is related to this issue: https://review.openstack.org/#/c/516372

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

Seems already there is one more issue: https://bugs.launchpad.net/tempest/+bug/1710845

Changed in tempest:
assignee: Terry Wilson (otherwiseguy) → Daniel Alvarez (dalvarezs)
Changed in tempest:
assignee: Daniel Alvarez (dalvarezs) → wes hayutin (weshayutin)
Revision history for this message
Attila Fazekas (afazekas) wrote :

Nova expected to wait for all connected port to become active on instance creation before reporting the instance active.
No additional user/tempest wait is required, no random port status flipping is allowed.

tags: added: testing
tags: added: neutron
Revision history for this message
Terry Wilson (otherwiseguy) wrote :

afazekas: can you point to the documentation re: "no random port status flipping" being allowed? External forces can sometimes take down the underlying port for example.

Changed in nova:
status: New → Incomplete
no longer affects: nova
Revision history for this message
Martin Kopec (mkopec) wrote :

There has been a long inactivity here, so moving to Incomplete for now.

I check http://status.openstack.org/openstack-health/#/test/tempest.scenario.test_network_basic_ops.TestNetworkBasicOps.test_network_basic_ops?duration=P3M and I don't see similar failures like described here.

Tempest always waits a certain amount of time for new resources to get to a desired state. If that time is not enough, it usually helps to decrease the concurrency or increase the timeouts (search for build_timeout options in https://opendev.org/openstack/tempest/src/branch/master/tempest/config.py).

If you still experience the issue, or you hit it again, don't hesitate to reopen this bug.

Changed in tempest:
assignee: wes hayutin (weshayutin) → nobody
status: In Progress → Invalid
status: Invalid → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for tempest because there has been no activity for 60 days.]

Changed in tempest:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.