yahoo-eng-team team mailing list archive

[Jay Pipes <1779717@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Even though in Placement API microversion 1.12, we began requiring
project and user ID in the PUT /allocations request payload, the project
ID and user ID for an *existing* consumer are never actually updated.

What this means is that if you created an allocation for consumer X
before 1.12, like so:

```
PUT /allocations/X
{
  "allocations": ...
}
```

a consumer record will be created for the allocation and the project and
user ID for that consumer record will be the
CONF.placement.incomplete_consumer_project_id value (or user ID value).
If I want to set the project and user ID of the allocation's consumer to
some other value, there's no way I can do that.

If I do the following:

```
OpenStack-API-Version: placement 1.28
PUT /allocations/X
{
  "allocations": ...
  "consumer_generation": 1,
  "project_id": $NEW_PROJECT_ID,
  "user_id": $NEW_USER_ID
}
```

The $NEW_PROJECT_ID and $NEW_USER_ID values are merely ignored.

** Affects: nova
     Importance: Medium
     Assignee: Jay Pipes (jaypipes)
         Status: Triaged


** Tags: placement

-- 
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/1779717

Title:
  No ability to update consumer's project and/or user external ID

Status in OpenStack Compute (nova):
  Triaged

Bug description:
  Even though in Placement API microversion 1.12, we began requiring
  project and user ID in the PUT /allocations request payload, the
  project ID and user ID for an *existing* consumer are never actually
  updated.

  What this means is that if you created an allocation for consumer X
  before 1.12, like so:

  ```
  PUT /allocations/X
  {
    "allocations": ...
  }
  ```

  a consumer record will be created for the allocation and the project
  and user ID for that consumer record will be the
  CONF.placement.incomplete_consumer_project_id value (or user ID
  value). If I want to set the project and user ID of the allocation's
  consumer to some other value, there's no way I can do that.

  If I do the following:

  ```
  OpenStack-API-Version: placement 1.28
  PUT /allocations/X
  {
    "allocations": ...
    "consumer_generation": 1,
    "project_id": $NEW_PROJECT_ID,
    "user_id": $NEW_USER_ID
  }
  ```

  The $NEW_PROJECT_ID and $NEW_USER_ID values are merely ignored.

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