Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1433702

Summary: tempest.scenario.test_network_v6.TestGettingAddress.test_multi_prefix_slaac failed
Product: Red Hat OpenStack Reporter: Eran Kuris <ekuris>
Component: openstack-neutronAssignee: Assaf Muller <amuller>
Status: CLOSED DUPLICATE QA Contact: Toni Freger <tfreger>
Severity: high Docs Contact:
Priority: unspecified    
Version: 11.0 (Ocata)CC: amuller, chrisw, nyechiel, srevivo
Target Milestone: ---Keywords: Automation
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-04-04 06:02:39 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:
Embargoed:
Attachments:
Description Flags
log none

Description Eran Kuris 2017-03-19 12:14:09 UTC
Created attachment 1264607 [details]
log

Description of problem:
Running tempest tempest.scenario.test_network_v6.TestGettingAddress.test_multi_prefix_slaac 
the tests failed.

attached log
attached log file
Version-Release number of selected component (if applicable):
python-neutron-lib-1.1.0-0.20170213120052.9b3ea8f.el7ost.noarch
openstack-neutron-ml2-10.0.0-5.el7ost.noarch
openstack-neutron-lbaas-10.0.1-0.20170222151526.c6011fb.el7ost.noarch
python-neutronclient-6.1.0-0.20170208193918.1a2820d.el7ost.noarch
openstack-neutron-common-10.0.0-5.el7ost.noarch
openstack-neutron-10.0.0-5.el7ost.noarch
openstack-neutron-openvswitch-10.0.0-5.el7ost.noarch
puppet-neutron-10.3.0-1.el7ost.noarch
python-neutron-10.0.0-5.el7ost.noarch
python-neutron-lbaas-10.0.1-0.20170222151526.c6011fb.el7ost.noarch

How reproducible:
 Failed 1 times in the last 6 runs. Stability: 83 %

Steps to Reproduce:
1.Run tempest Neutron DFG CI job 
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Eran Kuris 2017-04-04 06:02:39 UTC

*** This bug has been marked as a duplicate of bug 1438662 ***