swift-ring-builder exit status confusing
Bug #836922 reported by
Mark Gius
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Object Storage (swift) |
Fix Released
|
Undecided
|
Mark Gius | ||
| swift (Ubuntu) |
Fix Released
|
Medium
|
Adam Gandelman | ||
| Oneiric |
Fix Released
|
Medium
|
Adam Gandelman | ||
Bug Description
The swift-ring-builder should return the standard exit codes of 0 for success and non-zero for error.
https:/
Current exit codes meaning
> Exit codes: 0 = ring changed, 1 = ring did not change, 2 = error
Related branches
lp:~gandelman-a/ubuntu/oneiric/swift/lp836922
- Chuck Short: Pending requested
-
Diff: 278 lines (+261/-0)3 files modifieddebian/changelog (+7/-0)
debian/patches/backport-change-swift-ring-builder-exit-codes (+253/-0)
debian/patches/series (+1/-0)
| Changed in swift: | |
| assignee: | nobody → Mark Gius (markgius) |
Revision history for this message
| Openstack Gerrit (openstack-gerrit) wrote A change has been merged to openstack/swift | #1 |
| Changed in swift: | |
| status: | New → Fix Committed |
| tags: | added: server-o-rs |
| Changed in swift (Ubuntu): | |
| assignee: | nobody → Adam Gandelman (gandelman-a) |
| Changed in swift (Ubuntu Oneiric): | |
| milestone: | none → ubuntu-11.10 |
| importance: | Undecided → Medium |
| status: | New → Confirmed |
| status: | Confirmed → Triaged |
| Changed in swift (Ubuntu Oneiric): | |
| status: | Triaged → In Progress |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in swift (Ubuntu Oneiric): | |
| status: | In Progress → Fix Released |
| Changed in swift: | |
| milestone: | none → 1.4.4 |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Reviewed: https:/
Committed: http://
Submitter: Jenkins
Branch: master
status fixcommitted
done
commit 1ad31af887cd6cd
Author: Mark Gius <email address hidden>
Date: Tue Sep 20 14:53:53 2011 -0700
Changes swift-ring-builder exit codes
swift-
non-zero for operations that have errored or need attention.
Fixes bug 836922
Change-Id: I8d18a49fcf239f