Swift race condition on AIO
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cisco Openstack |
Fix Released
|
Medium
|
Chris Ricker |
Bug Description
A few folks have reported seeing this on h.1 (though it appears to be inconsistent, suggesting a race condition that only sometimes manifests). It appears to become more prevalent with newer updates from StackForge pulled in after h.1. If this condition is encountered, the requite services can generally be restarted manually (or a second puppet run performed) to rectify the condition ("service swift-container
Error: Could not start Service[
Error: /Stage[
Error: Could not start Service[
Error: /Stage[
Error: Could not start Service[
Error: /Stage[
The root cause appears to be a race condition in which services may be started before the ringsync is complete, as evidenced by the messages like the following in the upstart logs for the failed services:
IOError: [Errno 2] No such file or directory: '/etc/swift/
Changed in openstack-cisco: | |
assignee: | Chip (cbaesema) → Chris Ricker (chris-ricker) |
importance: | High → Medium |
Changed in openstack-cisco: | |
status: | In Progress → New |
status: | New → Confirmed |
Changed in openstack-cisco: | |
status: | In Progress → Fix Committed |
Changed in openstack-cisco: | |
status: | Fix Committed → Fix Released |
Looks like we won't have time for this in h.2, but there is a simple workaround (either do a second puppet run or restart the three services manually) and therefore this isn't a showstopper.