tempest.scenario.test_network_v6.TestGettingAddress fails with dualnet=True and custom images

[Slawek Kaplonski]

Tests from tempest.scenario.test_network_v6.TestGettingAddress are failing when dualnet=True and with some custom images (e.g. RHEL 7) used for tests.
It is like that because "ip link" tool will not enable IPv6 on interface by default when interface is bring up. Instead of ip link, network manager (nmcli) should be used in such case.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/607958

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/607958
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=c5c7ba997eb194e8428bfcb802bfabfdfb5ef5fe
Submitter: Zuul
Branch: master

commit c5c7ba997eb194e8428bfcb802bfabfdfb5ef5fe
Author: Slawek Kaplonski <email address hidden>
Date: Thu Oct 4 15:21:45 2018 +0200

    Change way how second NIC in guest OS is configured

    In case of RHEL based operating system used in guest vm in
    test_network_v6 module, there is need to prepare

        /etc/sysconfig/network-scripts/ifcfg-%(nic)s

    file with "IPV6INIT=yes" to enable IPv6 on it.
    Otherwise IPv6 will not be configured on this NIC when:

        ip link set up dev %(nic)s

    will be executed and tests with dualnet=False will fail.
    This isn't necessary on systems like Ubuntu or Cirros.

    Change-Id: I397b1c3584a045f9ca4f47b4e691385628d35efa
    Closes-Bug: #1795891

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tempest 20.0.0 release.