Table creation race between glance-api and registry services
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Glance |
Fix Released
|
Medium
|
Eoghan Glynn |
Bug Description
I'm seeing functional tests fail intermittently on Fedora-16, with the registry service failing to launch.
Examination of /var/log/messages reveals that the problem occurs when table creation is attempted for a table that already exists in the DB, presumably because it was just created by the newly launched glance-api service.
This appears to be a side-effect of the new v2 API direct usage of the registry DB (as opposed to always going through the REST API exposed by the glance-registry service, as was previously the case), which leads to a race condition when the two services are launched near simultaneously.
Though I've only seen this manifest in the tests, it could also conceivably occur for a fresh glance installation, if the services are launched in quick succession.
Changed in glance: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
assignee: | nobody → Eoghan Glynn (eglynn) |
milestone: | none → folsom-1 |
Changed in glance: | |
status: | Fix Committed → Fix Released |
Changed in glance: | |
milestone: | folsom-1 → 2012.2 |
Fix proposed to branch: master /review. openstack. org/7495
Review: https:/