swift-init reload/restart inconsistencies

Bug #920520 reported by Andrew Hale
10
This bug affects 2 people
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/automation it would be preferred if swift-init reload exited cleanly if it stop/starts each running process.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to swift (master)

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

Changed in swift:
status: New → In Progress
Changed in swift:
status: In Progress → Confirmed
Alex Yang (alexyang)
Changed in swift:
status: Confirmed → Invalid
clayg (clay-gerrard)
Changed in swift:
status: Invalid → Confirmed
importance: Undecided → Low
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.