Possible race updating consumer's proj/user
Bug #1781008 reported by
Eric Fried
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
This is to track [1] so we don't lose sight of it. We first need to figure out a way to test this scenario to see if this is an issue at all.
[1] https:/
Changed in nova: | |
status: | New → Confirmed |
assignee: | Jay Pipes (jaypipes) → nobody |
importance: | Undecided → Low |
importance: | Low → Wishlist |
To post a comment you must log in.
From my comment in that review:
"I'm not super concerned about rolling this back if it happens and there is a failure creating one of the other allocations from the payload because (a) I'm not sure when this would really happen besides POSTing allocations during a nova server move operation and we're *correcting* latent sentinel project/user info and (b) if that is the case, then we've inadvertently healed the consumer record anyway."