Unknown value in default_store causes startup to repeatedly fail without exiting if workers > 0

Bug #1065197 reported by Brian Waldon
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Glance
Fix Released
Medium
Brian Waldon
Grizzly
Fix Released
Medium
Brian Waldon

Bug Description

If you set the 'default_store' key to a scheme for which no store driver is registered, attempting to start the glance-api process will result in children being repeatedly created and killed. This only affects servers that are using the built-in multiprocessing (workers > 0) as the children are being respawned upon death. The following lines are logged at the end of each failed child spawn:

2012-10-10 18:51:37 ERROR glance.api.v1.images [311347f6-d9e6-4bd8-95de-ddd4dd28ab43 None None] Store for scheme unknown not found
2012-10-10 18:51:37 11753 ERROR eventlet.wsgi.server [-] Removing dead child 11758

Brian Waldon (bcwaldon)
Changed in glance:
assignee: nobody → Brian Waldon (bcwaldon)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to glance (master)

Fix proposed to branch: master
Review: https://review.openstack.org/15783

Changed in glance:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to glance (master)

Reviewed: https://review.openstack.org/15783
Committed: http://github.com/openstack/glance/commit/9669067e91ceffcd462f9177d1e2c446dfb347ea
Submitter: Jenkins
Branch: master

commit 9669067e91ceffcd462f9177d1e2c446dfb347ea
Author: Brian Waldon <email address hidden>
Date: Fri Nov 9 13:40:35 2012 -0800

    Prevent infinite respawn of child processes

    Rather than looking for an exit code of 2 to prevent child processes
    from respawning, we look for any non-zero status.

    Fixes bug 1074132.
    Fixes bug 1065197.

    Change-Id: I74ac13737d8a9b8710a8268eb1d67fbe5e75d491

Changed in glance:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in glance:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.