'%' (value) s in the execution SQL statement of alter_enum_add_value
should be decorated with ' '
Ralated commit I4767222ba97d9c35c011adfc187b2977975f981a
Change-Id: I24138e5b4ec8b3c3126ae5ff79e26ecb91a65d69
API often times pass tenant_id to all objects irrespective whether they
have the field. It's better to support both filters.
Change-Id: I8f7ff04c6d9d2237d89e82849cfdb6578f2c3313
neutron-lib now contains the API definitions for neutron's core
resources. This patch removes the constant core resource and collection
variables and uses them from lib. Subsequent patches will consume the
actual core resource attribute definitions.
NeutronLibImpact
Change-Id: Ia9afdf620cd538b2aa420593277d6403a45c996b
This adjusts the l2pop DB queries that leverage the port relationship
on the PortBinding and DistributedPortBinding models to ensure that the
port gets loaded from the DB as part of the initial query.
Without this the number of DB queries will increase with the number
of ports since the port wasn't being loaded until the 'port' attribute
was referenced on its corresponding binding object.
Closes-Bug: #1701288
Change-Id: I7c3b08d525b2c90100c9fe4efaee973cf3a076f3
In tempest, alias 'admin_manager' has been moved to 'os_admin'
'alt_manager' to 'os_alt' and 'manager' to 'os_primary' in
version Pike, and it will be removed in version Queens[1].
[1]I5f7164f7a7ec5d4380ca22885000caa0183a0bf7
Closes-bug: 1697588
Change-Id: Ib41a1bcff70cc7323b90a222c9f64d66e0203e53
The well known service type constants are in
neutron_lib.plugins.constants, but for legacy reasons a few still exist
and are referenced from neutron_lib.constants that we'd like to remove.
This patch switches references over to neutron_lib's plugin constants.
Change-Id: I1861448cec303725b30cef8f42029f467f9e03a3
Catch delete port extension failures like we do with normal port
removal to avoid interrupting the deletion processing for other
ports.
Related-Bug: #1697937
Change-Id: I42d86a86965d30e14c85ce975681a6b82be41ecc
Test was wrong because it was only checking if each of
expected rule types is in list returned from Neutron server.
As list of expected rule types was wrong, it didn't check anything.
This test was also dependent on deployment because it was checking
available rule types returned by neutron-server.
Now it is changed that it's checking only returned keys in each
rule_type and it's not checking returned values.
Change-Id: I467672cc0ba1e579cddfff6020658c82e80fa5af
Add to QoS devref document missing description about how
egress bandwidth limit rules are implemented by Linuxbridge
agent driver.
Change-Id: I1ce44aba14d54179e64f8d0516e0a60605b2add1
Some of the available checks are disabled by default, like:
[H106] Don’t put vim configuration in source files
[H203] Use assertIs(Not)None to check for None
Change-Id: Ie38ec248651b57f2f2886cf90366cbf13673ffaf