swift-init should check if binary exists before starting
Bug #1079075 reported by
Christian Berendt
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Object Storage (swift) |
Fix Released
|
Low
|
Michele Valsecchi |
Bug Description
At the moment swift-init simply tries start up all defined services and fails, because some configuration files are not existent.
Unable to locate config for proxy-server
Starting container-
Starting object-
Unable to locate config for object-expirer
I think swift-init should check if the needed binary (for example swift-proxy-server) exists on the system before proceeding.
Changed in swift: | |
assignee: | nobody → clayg (clay-gerrard) |
status: | New → In Progress |
Changed in swift: | |
importance: | Undecided → Low |
Changed in swift: | |
assignee: | clayg (clay-gerrard) → nobody |
status: | In Progress → Confirmed |
tags: | added: low-hanging-fruit |
Changed in swift: | |
assignee: | nobody → Madhuri Kumari (madhuri-rai07) |
Changed in swift: | |
assignee: | Madhuri Kumari (madhuri-rai07) → surbhi sarda (surbhisarda) |
Changed in swift: | |
assignee: | surbhi sarda (surbhisarda) → nobody |
Changed in swift: | |
assignee: | nobody → Michele Valsecchi (mvalsecc) |
Changed in swift: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
It seems like the simplest thing would be to check for the bin (something like distutils. spawn.find_ executable) when adding the Server's to the Manager.
For clarity, it seems like this applies to status, and stop as much as start. And the bug seems to be the printing of the warning "Unable to locate config for X-server" as it doesn't seem to effect the successful return code when you're starting multiple servers.