in the LXC host mongodb server will not start if mongodb is already running in an LXC guest
Bug #1417229 reported by
Jay R. Wren
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mongodb (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Trusty |
New
|
Undecided
|
Unassigned | ||
Utopic |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
This is a specific instance of this bug. https:/
Related branches
lp://staging/~evarlast/ubuntu/utopic/mongodb/upstart-workaround-debian-bug-718702
- Robie Basak: Needs Fixing
-
Diff: 42 lines (+10/-3)2 files modifieddebian/changelog (+6/-0)
debian/mongodb-server.mongodb.upstart (+4/-3)
lp://staging/~evarlast/ubuntu/trusty/mongodb/upstart-workaround-debian-bug-718702
- Robie Basak: Needs Fixing
-
Diff: 33 lines (+10/-1)2 files modifieddebian/changelog (+6/-0)
debian/mongodb-server.mongodb.upstart (+4/-1)
Changed in mongodb (Ubuntu Utopic): | |
status: | New → Won't Fix |
To post a comment you must log in.
Thanks. Assuming the patch is correct this looks good, but needs to be done in Vivid first, and the SRU paperwork done for SRUs to Trusty and Utopic. See https:/ /wiki.ubuntu. com/StableRelea seUpdates# Procedure for the steps needed.
A couple of potential minor improvements:
Try to say _why_ in the changelog, as well as _what_. How about "d/mongodb- server. mongodb. upstart: use pidfile to fix incorrect init script interaction between LXC host and guests (LP: #1417229)."
You shouldn't really use 1:2.6.3-0ubuntu6 for the SRU to Utopic since that version number is still free for use in Vivid, and will cause confusion in case of a future Vivid upload, as well as not really being clear that it's an SRU. See https:/ /wiki.ubuntu. com/SecurityTea m/UpdatePrepara tion#Update_ the_packaging for a suitable version number scheme for SRUs. You should use this scheme for both the Trusty and Utopic SRUs.