[integration tests] Exception: Can't set same ids for pings for test "Check connectivity between vms with the same internal ips in different tenants with equal id for connections"

Bug #1584757 reported by Georgy Dyuldin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
Confirmed
High
MOS QA Team

Bug Description

Test result:

https://mirantis.testrail.com/index.php?/tests/view/6068692

Trace:

self = <mos_tests.neutron.python_tests.test_conntrack.TestConntrackZones object at 0x7f8300b45490>
env = <mos_tests.environment.fuel_client.Environment object at 0x7f8300f016d0>
servers = [<Server: server01>, <Server: server02>, <Server: server03>, <Server: server04>]
os_clients = [<mos_tests.environment.os_actions.OpenStackActions object at 0x7f8300b6d290>, <mos_tests.environment.os_actions.OpenStackActions object at 0x7f8300f06910>]

    @pytest.mark.testrail_id('542629')
    def test_connectivity_between_vms_with_same_internal_ips(
            self, env, servers, os_clients):
        """Check connectivity between vms with the same internal ips in
            different tenants

            Scenario:
                1. Create tenants A and B
                2. In tenant A create net1 and subnet1 with CIDR 10.0.0.0/24
                3. In tenant A create security group sec1 and add rule that allows
                    ingress icmp traffic
                4. In tenant B create net2 and subnet2 with CIDR 10.0.0.0/24
                5. In tenant B create security group sec2
                6. In tenant A boot 2 VMs in net1 specifying sec1 as security
                    group: test1 with ip 10.0.0.4 and test2 with ip 10.0.0.5
                7. In tenant B boot 2 VMs: test3 with ip 10.0.0.4 and test4 with
                    ip 10.0.0.5
                8. Check that all vms are on the same compute node
                    (in another situation migrate them to the one compute)
                9. Go to test1 and ping test2 (don't stop ping)
                10. Go to compute node and run "conntrack -L | grep 10.0.0.4"
                11. Go to test3 and ping test4 (don't stop ping)
                12. Go to compute node and run "conntrack -L | grep 10.0.0.4 again"
                13. If ids is'n equal, go to the step 13. Else go to 16
                14. On test1 stop and start ping. Check that id for non UNREPLIED
                    connection is equal to UNREPLIED (if not repeat this step some
                    times)
                15. Check ping between test3 and test 4
                16. Run "conntrack -L | grep 10.0.0.4"
                17. On compute node run "iptables -L -t raw"
                18. Check that ouput contain rules that assign zones for tap and
                    qvb devices
            """

        compute_fqdn = getattr(servers[0], 'OS-EXT-SRV-ATTR:host')
        compute = env.find_node_by_fqdn(compute_fqdn)

        restart_ping(os_clients, env, servers)
        for i in range(6):
            if is_ping_has_same_id(compute):
                break
            logger.info('Restart pings to make conntrack ids equal')
            restart_ping(os_clients, env, servers, i)
            time.sleep(30)
        else:
> raise Exception("Can't set same ids for pings")
E Exception: Can't set same ids for pings

mos_tests/neutron/python_tests/test_conntrack.py:288: Exception

Tags: area-qa
Changed in mos:
milestone: 10.0 → 9.0
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.