Table creation race between glance-api and registry services

Bug #1000304 reported by Eoghan Glynn on 2012-05-16
This bug affects 1 person
Affects Status Importance Assigned to Milestone
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.

Eoghan Glynn (eglynn) on 2012-05-16
Changed in glance:
status: New → Confirmed
importance: Undecided → Medium
assignee: nobody → Eoghan Glynn (eglynn)
milestone: none → folsom-1

Fix proposed to branch: master

Changed in glance:
status: Confirmed → In Progress
Thierry Carrez (ttx) wrote :

I think that was fixed by , reopen if you disagree.

Changed in glance:
status: In Progress → Fix Committed
Thierry Carrez (ttx) on 2012-05-23
Changed in glance:
status: Fix Committed → Fix Released
Eoghan Glynn (eglynn) wrote :

> I think that was fixed by , reopen if you disagree.

Yes, Thierry, that is correct.

Thierry Carrez (ttx) on 2012-09-27
Changed in glance:
milestone: folsom-1 → 2012.2
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers