qos tempest tests should not try to use unsupported rule types

[YAMAMOTO Takashi]

qos tempest tests should not try to use unsupported rule types on the deployment.
currently they seem to assume all rule types are available, regardless of whatever
list_qos_rule_types returns.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/406610
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=9f19b3e7e16d946b0770710a428606462cf217f9
Submitter: Jenkins
Branch: master

commit 9f19b3e7e16d946b0770710a428606462cf217f9
Author: Sławek Kapłoński <email address hidden>
Date: Sun Dec 4 15:00:54 2016 +0000

    Tempest tests uses only supported QoS rule types

    If rule type required for QoS tempest test is not supported by current
    configuration of Neutron then such test will be skipped.
    For example if neutron-server is running with ML2 plugin only with openvswitch
    mechanism driver loaded then tests related to MINIMUM_BANDWIDTH rule type will
    be skipped because openvswitch mechanism driver don't support this kind of rule.

    Change-Id: I88e59cdbd79afb5337052ba3e5aecb96c7c8ea1c
    Closes-Bug: 1644097

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/neutron 10.0.0.0b2 development milestone.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/newton
Review: https://review.openstack.org/422168

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/422168
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=8ee8082806e3804a8020762bccd7c24a4a4a6e11
Submitter: Jenkins
Branch: stable/newton

commit 8ee8082806e3804a8020762bccd7c24a4a4a6e11
Author: Sławek Kapłoński <email address hidden>
Date: Sun Dec 4 15:00:54 2016 +0000

    Tempest tests uses only supported QoS rule types

    If rule type required for QoS tempest test is not supported by current
    configuration of Neutron then such test will be skipped.
    For example if neutron-server is running with ML2 plugin only with openvswitch
    mechanism driver loaded then tests related to MINIMUM_BANDWIDTH rule type will
    be skipped because openvswitch mechanism driver don't support this kind of rule.

    Change-Id: I88e59cdbd79afb5337052ba3e5aecb96c7c8ea1c
    Closes-Bug: 1644097
    (cherry picked from commit 9f19b3e7e16d946b0770710a428606462cf217f9)

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/neutron 9.3.0 release.