swift config doesn't match upstart expectations, required upstart configurations not installed.
Bug #954477 reported by
Greg Althaus
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
swift (Ubuntu) |
Fix Released
|
High
|
James Page | ||
Precise |
Fix Released
|
High
|
James Page |
Bug Description
In precise beta-1, the swift-object packages put the config files in /etc/swift/
Also, the object, container, and account packages are missing replicator, updater, and reaper upstart configs.
Related branches
lp:~james-page/swift/essex-fixup-upstart
- Ubuntu Server Developers: Pending requested
-
Diff: 200 lines (+26/-17)14 files modifieddebian/changelog (+9/-0)
debian/rules (+5/-5)
debian/swift-account.swift-account-auditor.upstart.in (+1/-1)
debian/swift-account.swift-account-reaper.upstart.in (+1/-1)
debian/swift-account.swift-account-replicator.upstart.in (+1/-1)
debian/swift-account.upstart.in (+1/-1)
debian/swift-container.swift-container-auditor.upstart.in (+1/-1)
debian/swift-container.swift-container-replicator.upstart.in (+1/-1)
debian/swift-container.swift-container-updater.upstart.in (+1/-1)
debian/swift-container.upstart.in (+1/-1)
debian/swift-object.swift-object-auditor.upstart.in (+1/-1)
debian/swift-object.swift-object-replicator.upstart.in (+1/-1)
debian/swift-object.swift-object-updater.upstart.in (+1/-1)
debian/swift-object.upstart.in (+1/-1)
summary: |
- swift config doens't match upstart expectations + swift config doesn't match upstart expectations |
Changed in swift (Ubuntu): | |
importance: | Undecided → Medium |
Changed in swift (Ubuntu Precise): | |
status: | Confirmed → In Progress |
To post a comment you must log in.
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/954477/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]