when I give a specified tenant access to the specified private flavor, I use it like this :
POST /v2/{tenant_id}/flavors/{flavor_id}/action
{
"addTenantAccess": {
"tenant": "fake_tenant"
}
}
tenant: The name of the tenant to which to give access.
The response is:
{
"flavor_access": [
{
"flavor_id": "10",
#here is "tenant_id"
"tenant_id": "fake_tenant"
},
{
"flavor_id": "10",
"tenant_id": "openstack"
}
]
}
when I use the private flavor to create VM in the specified tenant,it failed. But if I add the tenant access by using the tenant id,it can create VM successfully in the specified tenant .
POST /v2/{tenant_id}/flavors/{flavor_id}/action
{
"addTenantAccess": {
"tenant": "{tenant_id}"
}
}
I check the code, It also uses the "tenant" information as the "project id".
So we should change the api guides in the add Tenant Access to private flavor action,
change "tenant: The name of the tenant to which to give access." to
"tenant: The uuid of the tenant to which to give access."
This is just a temporary modification method，we can not let the user to ensure the correctness of parameters, so we should verify the validation of tenant id.