Bug 1433702 - tempest.scenario.test_network_v6.TestGettingAddress.test_multi_prefix_slaac failed
Summary: tempest.scenario.test_network_v6.TestGettingAddress.test_multi_prefix_slaac f...
Keywords:
Status: CLOSED DUPLICATE of bug 1438662
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron
Version: 11.0 (Ocata)
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Assaf Muller
QA Contact: Toni Freger
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-19 12:14 UTC by Eran Kuris
Modified: 2017-04-04 06:02 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-04-04 06:02:39 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
log (177.94 KB, text/plain)
2017-03-19 12:14 UTC, Eran Kuris
no flags Details

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 ***


Note You need to log in before you can comment on or make changes to this bug.