swift service scripts will not start unless /etc/swift/*-server/* exists

Bug #931893 reported by Dan Bode
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
swift (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

For the default case where a storage node only contains one server for each type (object, account, container), there does not have to be a /etc/swift/<type>-server/ directory with any files in it.

In this case, the server is configured with a single file:

/etc/swift/<type>-server.conf

The upstart scripts provided in the trunk ppa for swift:

  deb http://ppa.launchpad.net/swift-core/trunk/ubuntu oneiric main

will not start any of the server services unless files exist in these folders

  ...
  if [ $(find /etc/swift/object-server/ -type f 2>/dev/null | wc -l) -gt 0 ]; then
    exec /usr/bin/swift-init object-server start
  ...

This means that the services cannot be started with the default configuration

Revision history for this message
Thierry Carrez (ttx) wrote :

Moving to swift packaging, as this is not specific to OpenStack PPAs

affects: openstack-ppa → swift (Ubuntu)
Changed in swift (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in swift (Ubuntu):
status: New → Confirmed
Revision history for this message
Matt Kassawara (ionosphere80) wrote :

This bug is rather old and the Juno swift packages don't exhibit this issue.

Revision history for this message
Adam Vinsh (adam-vinsh) wrote :

Came across this bug in a comment in some puppet-swift work.
Confirmed that this is no longer an issue for Ubuntu since Juno.
Marking this as "Fix Released" because of that. Please adjust if I have this wrong!

Changed in swift (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Adam Vinsh (adam-vinsh) wrote :

Now, who can close this bug?

Revision history for this message
Matt Kassawara (ionosphere80) wrote :

LP considers fix-released as closed.

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.