yahoo-eng-team team mailing list archive

[Brian Haley <1792472@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

neutron_tempest_plugin.scenario.test_floatingip.FloatingIPPortDetailsTest.test_floatingip_port_details
occasionally fails in the check queue.  An example:

http://logs.openstack.org/97/602097/2/check/neutron-tempest-plugin-
scenario-linuxbridge/849d93e/testr_results.html.gz

Traceback (most recent call last):
  File "/opt/stack/neutron-tempest-plugin/neutron_tempest_plugin/scenario/test_floatingip.py", line 249, in test_floatingip_port_details
    fip, port, status='DOWN', device_id='', device_owner='')
  File "/opt/stack/neutron-tempest-plugin/neutron_tempest_plugin/scenario/test_floatingip.py", line 259, in _check_port_details
    self.assertEqual(status, port_details['status'])
  File "/opt/stack/tempest/.tox/tempest/local/lib/python2.7/site-packages/testtools/testcase.py", line 411, in assertEqual
    self.assertThat(observed, matcher, message)
  File "/opt/stack/tempest/.tox/tempest/local/lib/python2.7/site-packages/testtools/testcase.py", line 498, in assertThat
    raise mismatch_error
testtools.matchers._impl.MismatchError: 'DOWN' != u'BUILD'

The strange thing is that BUILD is not a valid state for a floating IP,
only ACTIVE, DOWN and ERROR are.

I believe this is due to this test using the compute API to get the
floating IP state, it should instead use the neutron API if possible,
for example get_floatingip(), so that a valid object is returned.  I'll
investigate changing the code.

** Affects: neutron
     Importance: Medium
     Assignee: Brian Haley (brian-haley)
         Status: Confirmed


** Tags: tempest

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1792472

Title:
  neutron_tempest_plugin: test_floatingip_port_details occasionally
  fails

Status in neutron:
  Confirmed

Bug description:
  neutron_tempest_plugin.scenario.test_floatingip.FloatingIPPortDetailsTest.test_floatingip_port_details
  occasionally fails in the check queue.  An example:

  http://logs.openstack.org/97/602097/2/check/neutron-tempest-plugin-
  scenario-linuxbridge/849d93e/testr_results.html.gz

  Traceback (most recent call last):
    File "/opt/stack/neutron-tempest-plugin/neutron_tempest_plugin/scenario/test_floatingip.py", line 249, in test_floatingip_port_details
      fip, port, status='DOWN', device_id='', device_owner='')
    File "/opt/stack/neutron-tempest-plugin/neutron_tempest_plugin/scenario/test_floatingip.py", line 259, in _check_port_details
      self.assertEqual(status, port_details['status'])
    File "/opt/stack/tempest/.tox/tempest/local/lib/python2.7/site-packages/testtools/testcase.py", line 411, in assertEqual
      self.assertThat(observed, matcher, message)
    File "/opt/stack/tempest/.tox/tempest/local/lib/python2.7/site-packages/testtools/testcase.py", line 498, in assertThat
      raise mismatch_error
  testtools.matchers._impl.MismatchError: 'DOWN' != u'BUILD'

  The strange thing is that BUILD is not a valid state for a floating
  IP, only ACTIVE, DOWN and ERROR are.

  I believe this is due to this test using the compute API to get the
  floating IP state, it should instead use the neutron API if possible,
  for example get_floatingip(), so that a valid object is returned.
  I'll investigate changing the code.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1792472/+subscriptions