You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
when a loadbalancer is created by a non-admin tenant and no tenant_id is explicitly specified, but a subnet in another tenant is specified, the loadbalacner create call should complete with provisioning_status ACTIVE and operating_status 'ONLINE', but the loadbalancer tenant_id should not equal subnet tenant_id.
A non-admin tenant should not be able to create a loadbalancer on a another tenant's subnet. An admin should be able to create a loadbalancer on a tenant subnet, but it must specify the tenant id that matches the subnet. I will verify that this works in our driver.
Agent Version
9.2.0
Operating System
RHEL 7.3
OpenStack Release
Mitaka
Bug Severity
Severity: 5
Description
According to community BVT
when a loadbalancer is created by a non-admin tenant and no tenant_id is explicitly specified, but a subnet in another tenant is specified, the loadbalacner create call should complete with provisioning_status ACTIVE and operating_status 'ONLINE', but the loadbalancer tenant_id should not equal subnet tenant_id.
Deployment
Run
from /var/log/neutron/server.log
The text was updated successfully, but these errors were encountered: