test_dualnet_multi_prefix_slaac fails on the gate

[Ken'ichi Ohmichi]

test_dualnet_multi_prefix_slaac fails like

Traceback (most recent call last):
  File "tempest/test.py", line 127, in wrapper
    return f(self, *func_args, **func_kwargs)
  File "tempest/scenario/test_network_v6.py", line 253, in test_dualnet_multi_prefix_slaac
    dualnet=True)
  File "tempest/scenario/test_network_v6.py", line 165, in _prepare_and_test
    self.turn_nic6_on(sshv4_2, sid2)
  File "tempest/scenario/test_network_v6.py", line 147, in turn_nic6_on
    % self.network_v6)
  File "/opt/stack/new/tempest/.tox/full/local/lib/python2.7/site-packages/testtools/testcase.py", line 350, in assertEqual
    self.assertThat(observed, matcher, message)
  File "/opt/stack/new/tempest/.tox/full/local/lib/python2.7/site-packages/testtools/testcase.py", line 435, in assertThat
    raise mismatch_error
testtools.matchers._impl.MismatchError: 1 != 2: Multiple IPv6 ports found on network <DeletableNetwork id="a0278487-1e79-4be7-993a-b8344de431b4" name="tempest-network-smoke--1409573709">

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: master
Review: https://review.openstack.org/233920

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/233920
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=695ac5cdeddf5d66408219c64edb233f50fafe72
Submitter: Jenkins
Branch: master

commit 695ac5cdeddf5d66408219c64edb233f50fafe72
Author: Ken'ichi Ohmichi <email address hidden>
Date: Tue Oct 13 03:07:17 2015 +0000

    Add failure ports to error message

    On the gate, test_dualnet_multi_prefix_slaac fails due to duplicated
    ports on the test. However, the error message doesn't contain actual
    ports information. This patch adds it for debugging.

    Change-Id: I198ae97b954c01581a037923494949527fed8efa
    Related-Bug: #1505478

[Castulo J. Martinez (castulo-martinez)]

Hey Kenichi, I am doing some cleanup in bugs, I see you already submitted a patch for this bug, but I see you added Related-Bug to your commit message instead of Closes-Bug, does that mean another patch is needed to close this bug? Or it was an oversight?

[Ken'ichi Ohmichi (oomichi)]

Thanks for working here Castulo.
Yeah, now we are not facing this problem.
and it is enough to add the debugging message for current situation.
I will change the status to "Fixed" at this time for the cleanup.