yahoo-eng-team team mailing list archive

[KaiLin <linkai3@xxxxxxxxxx>]

Public bug reported:

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 "tenant" to "tenant_id" in the API of  the add Tenant Access to private flavor action.

** Affects: nova
     Importance: Undecided
     Assignee: KaiLin (linkai3)
         Status: New

** Changed in: nova
     Assignee: (unassigned) => KaiLin (linkai3)

** Description changed:

  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"
-     }
+     "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"
-         }
-     ]
+     "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}"
-     }
+     "addTenantAccess": {
+         "tenant": "{tenant_id}"
+     }
  }
  
- I check the code, It also use the "tenant" information as the "project id".
+ I check the code, It also uses the "tenant" information as the "project id".
  So we should change "tenant" to "tenant_id" in the API of  the add Tenant Access to private flavor action.

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1358805

Title:
  Incorrect API in the add Tenant Access to private flavor action

Status in OpenStack Compute (Nova):
  New

Bug description:
  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 "tenant" to "tenant_id" in the API of  the add Tenant Access to private flavor action.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1358805/+subscriptions