swift-init reload/restart inconsistencies
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Object Storage (swift) |
Confirmed
|
Low
|
Unassigned |
Bug Description
There are a few inconsistencies in swift-init reload and swift-init restart, the only difference between the two should be the graceful argument present in a reload and not in a restart.
- reload will try to stop/start each service in turn while restart will stop all then start all. reloads behaviour is preferred here since with restart there can be a large delay between a service being signalled to stop and being restarted.
- on a node where not all services are running (ie. no proxy-server) then 'swift-init reload all' returns an error exit code while restart returns a 0 exit code.
It would be better if restart used the same ordering that reload currently performs. Likewise, for ease of scripting/
Changed in swift: | |
status: | In Progress → Confirmed |
Changed in swift: | |
status: | Confirmed → Invalid |
Changed in swift: | |
status: | Invalid → Confirmed |
importance: | Undecided → Low |
Fix proposed to branch: master /review. openstack. org/3310
Review: https:/