Bug 1313542

Summary: ospd 7 poodle failing tempest.scenario.test_network_basic_ops.TestNetworkBasicOps.test_network_basic_ops
Product: Red Hat OpenStack Reporter: Steve Linabery <slinaber>
Component: rhosp-directorAssignee: Angus Thomas <athomas>
Status: CLOSED WORKSFORME QA Contact: Arik Chernetsky <achernet>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0 (Kilo)CC: dbecker, jcoufal, mburns, morazi, rhel-osp-director-maint, slinaber
Target Milestone: ---Keywords: Automation, AutomationBlocker
Target Release: 10.0 (Newton)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-10-13 14:04:17 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Steve Linabery 2016-03-01 20:29:34 UTC
Description of problem:
Traceback (most recent call last):
  File "/home/stack/tempest/tempest/test.py", line 126, in wrapper
    return f(self, *func_args, **func_kwargs)
  File "/home/stack/tempest/tempest/scenario/test_network_basic_ops.py", line 395, in test_network_basic_ops
    self.check_public_network_connectivity(should_connect=True)
  File "/home/stack/tempest/tempest/scenario/test_network_basic_ops.py", line 203, in check_public_network_connectivity
    self.check_floating_ip_status(floating_ip, floatingip_status)
  File "/home/stack/tempest/tempest/scenario/manager.py", line 733, in check_floating_ip_status
    st=status))
  File "/usr/lib/python2.7/site-packages/testtools/testcase.py", line 348, in assertEqual
    self.assertThat(observed, matcher, message)
  File "/usr/lib/python2.7/site-packages/testtools/testcase.py", line 433, in assertThat
    raise mismatch_error
MismatchError: 'ACTIVE' != u'ERROR': FloatingIP: <"FloatingIP" addr="2001:db8:fd00:1000:dead:beef:cafe:f14" id="e71a4b25-d447-46a8-91a7-d469865f7a47"> is at status: ERROR. failed  to reach status: ACTIVE

Comment 3 Mike Burns 2016-04-07 21:11:06 UTC
This bug did not make the OSP 8.0 release.  It is being deferred to OSP 10.

Comment 5 Jaromir Coufal 2016-10-11 13:33:46 UTC
Seems like Networking or Tempest issue.

Comment 6 Steve Linabery 2016-10-13 14:04:17 UTC
It's passing on latest RHOS7 virthost ha runs, and this was filed against a poodle. Seems safe to close this.