[Bug 1419554] Re: Can't upgrade procps in LXC 1.1
Launchpad Bug Tracker
1419554 at bugs.launchpad.net
Tue Feb 10 23:24:02 UTC 2015
This bug was fixed in the package procps - 1:3.3.9-1ubuntu2.2
---------------
procps (1:3.3.9-1ubuntu2.2) trusty; urgency=medium
* ignore_erofs.patch: Same as ignore_eaccess but for the case where
part of /proc is read/only. (LP: #1419554)
-- Stephane Graber <stgraber at ubuntu.com> Tue, 10 Feb 2015 13:51:14 -0500
** Changed in: procps (Ubuntu Trusty)
Status: Fix Committed => Fix Released
** Changed in: procps (Ubuntu Utopic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, 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 Released
Status in procps source package in Precise:
Fix Released
Status in procps source package in Trusty:
Fix Released
Status in procps source package in Utopic:
Fix Released
Status in procps source package in Vivid:
Fix Released
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
More information about the foundations-bugs
mailing list