yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #31980
[Bug 1444753] Re: Tenant_Id needs valiation for Neutron-LBaas-API
I happened to have some investigate about this kind of issues. From the
bug history, this issue will be close as invalid. tenant_id can only be
passed in by admin. Neutron would think admin knows what he is doing,
and would allow admin to do anything.
Pls see the following bugs as reference.
https://bugs.launchpad.net/neutron/+bug/1200585
https://bugs.launchpad.net/neutron/+bug/1185206
https://bugs.launchpad.net/neutron/+bug/1067620
https://bugs.launchpad.net/neutron/+bug/1290408
https://bugs.launchpad.net/neutron/+bug/1338885
https://bugs.launchpad.net/neutron/+bug/1398992
https://bugs.launchpad.net/neutron/+bug/1440705
https://bugs.launchpad.net/neutron/+bug/1441373
https://bugs.launchpad.net/neutron/+bug/1440700
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1444753
Title:
Tenant_Id needs valiation for Neutron-LBaas-API
Status in OpenStack Neutron (virtual network service):
Invalid
Bug description:
Based on the description in the following link
https://wiki.openstack.org/wiki/Neutron/LBaaS/API_2.0#Create_a_Health_Monitor
tenant_id: only required if the caller has an admin role and wants to
create a Health Monitor for another tenant.
while in the tempest Admin API test, we found that when we pass an
empty tenant id or an invalid tenant id , we are still able to create
services like health monitor,etc. We believe that this is a bug,
since tenantid is a UUID, it should not be invalid or empty.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1444753/+subscriptions
References