default access_ip_* race condition
Bug #1152328 reported by
Chris Behrens
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Chris Behrens |
Bug Description
When spawning a new instance, if a user doesn't specify access_ip_v[4|6], defaults are set according to CONF.default_
The access_ip_* values should be set when an instance goes ACTIVE... However, the code does 2 DB calls. 1 to update to ACTIVE. Then 1 to set access_ips. These should be 1 update. If someone times a query just right, they'll see their instance is ACTIVE but with no access_ip_* data.
Changed in nova: | |
importance: | Undecided → Medium |
status: | New → In Progress |
assignee: | nobody → Chris Behrens (cbehrens) |
Changed in nova: | |
milestone: | none → grizzly-rc1 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | grizzly-rc1 → 2013.1 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/23855
Review: https:/