Comment 18 for bug 1753209

Reviewed: https://review.openstack.org/571675
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=d9de2233d5edb7f978ed72e2ea8c4dc42a399e3d
Submitter: Zuul
Branch: stable/queens

commit d9de2233d5edb7f978ed72e2ea8c4dc42a399e3d
Author: Ihar Hrachyshka <email address hidden>
Date: Thu Mar 15 10:13:14 2018 -0700

    tests: port test_port_presence_prevents_network_rbac_policy_deletion

    The test was originally implemented in this form as a tempest api test
    case, but there is a problem with it being part of tempest suite,
    because the suite should be safe to execute on a running cloud and
    shouldn't affect other tenants. But sharing a network with everyone (*)
    briefly impacts other tenants because they see a new shared network
    popping up for a second in their net-list. It is also an issue because
    if we are unlucky enough, some other tenant may start an instance
    without specifying a particular port or network to use, in which case
    there is a chance that nova allocates a port in this shared network and
    attach it to the instance. When the rbac test case then tries to delete
    the policy and the network, it fails because it's still in use.

    The solution is to stop testing this scenario in tempest suite, instead
    moving it into unit test suite.

    A follow-up patch in neutron-tempest-plugin will clean up the bad test
    case.

    Change-Id: I199f639c95e8ae884ede46404370d7b64da3b309
    Needed-By: Iba89a53b2715cf3a9c7485f2089f27d547fea308
    Related-Bug: #1753209
    (cherry picked from commit 6c772de103e469ad17cdbc6a86ed15655aa6b9cc)