[Yahoo-eng-team] [Bug 1968343] [NEW] Security Group Rule create with forged integer security_group_id causes exceptions

Public bug reported: Assuming a project xyz has Security Groups, following POST requests fails with HTTP 500 ValueError: /v2.0/security-group-rules { "security_group_rule": { "direction": "egress", "ethertype": "IPv4", "port_range_max": 443,

[Yahoo-eng-team] [Bug 1941537] [NEW] Neutron Policy Engine issues with PUT/Update

Public bug reported: We are using a policy that looks like that: "network_device": "field:port:device_owner=~^network:", "update_port:fixed_ips": "not rule:network_device", Idea is to protect special ports (by device_owner) from being updated but still allow users to create custom ports.

[Yahoo-eng-team] [Bug 1829261] [NEW] duplicate quota entry for project_id/resource causes inconsisten behaviour

Public bug reported: We experienced in one of our cluster an inconsisten behaviour when setting quota for a tenant (setting security_group to 3 but still returned always 2: $ curl -g -i -X PUT http://127.0.0.1:9696/v2.0/quotas/3e0fd3f8e9ec449686ef26a16a284265 "X-Auth-Token: $OS_AUTH_TOKEN" -d '

[Yahoo-eng-team] [Bug 1811873] [NEW] get_l3_agent_with_min_routers fails with postgresql backend

Public bug reported: We have our own L3 agent that uses the generic neutron function get_l3_agent_with_min_routers, rendering following exception if using a postgresql backend: 2019-01-15 16:34:33,091.091 59 ERROR neutron.api.v2.resource File "/var/lib/openstack/local/lib/python2.7/site-packag