Uploaded the fix to all series (after testing the fix on vivid).
Note that the problem is mostly visible on series which don't have
procps-instance.conf as those that do will not fail on upgrade (but
sysctl itself still fails).
To test the fix, it's best to run:
cat /etc/sysctl.d/*.conf /etc/sysctl.conf | sysctl -e -p - && echo pass
** Changed in: procps (Ubuntu Precise)
Assignee: (unassigned) => Stéphane Graber (stgraber)
** Changed in: procps (Ubuntu Utopic)
Assignee: (unassigned) => Stéphane Graber (stgraber)
** Changed in: procps (Ubuntu Vivid)
Assignee: (unassigned) => Stéphane Graber (stgraber)
** Changed in: procps (Ubuntu Trusty)
Assignee: (unassigned) => Stéphane Graber (stgraber)
** Changed in: procps (Ubuntu Precise)
Importance: Undecided => High
** Changed in: procps (Ubuntu Trusty)
Status: New => In Progress
** Changed in: procps (Ubuntu Utopic)
Status: New => In Progress
** Changed in: procps (Ubuntu Trusty)
Importance: Undecided => High
** Changed in: procps (Ubuntu Utopic)
Importance: Undecided => High
** Changed in: procps (Ubuntu Vivid)
Importance: Undecided => High
** Changed in: procps (Ubuntu Precise)
Status: New => In Progress
** Changed in: procps (Ubuntu Vivid)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1419554
Title:
Can't upgrade procps in LXC 1.1
Status in procps package in Ubuntu:
Fix Committed
Status in procps source package in Precise:
In Progress
Status in procps source package in Trusty:
In Progress
Status in procps source package in Utopic:
In Progress
Status in procps source package in Vivid:
Fix Committed
Bug description:
== SRU ==
Rationale:
sysctl now fails with current LXC as files which shouldn't be written to in
containers are read-only. A previous fix applied to the EACCESS case as
returned by apparmor.
Text case:
start procps
Regression potential:
All EROFS write failures will now be ignored (an error is still logged) but
I can't think of a case where that'd be a bad thing.
Original bug report:
LXC 1.1 on vivid has started giving privileged containers a read-only
/sys, which prevents Ubuntu's procps Upstart job from starting. This
isn't normally too problematic, except that the weekend's procps SRU's
postinst tries to start the job and causes the upgrade to fail.
Disabling the procps postinst makes apt usable again.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1419554/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
