SRU of LXCFS 2.0.6 (upstream bugfix release)

Bug #1660850 reported by Stéphane Graber
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lxcfs (Ubuntu)
Fix Released
Undecided
Unassigned
Trusty
Fix Released
Medium
Stéphane Graber
Xenial
Fix Released
Medium
Stéphane Graber
Yakkety
Fix Released
Medium
Stéphane Graber

Bug Description

LXCFS upstream released LXCFS 2.0.6 as a bugfix release with following changelog:
 - Fix swap values with nested cgroups
 - tests: Fix run on ppc64el
 - Fix wrong scanning of memory.stat

Just like Ubuntu itself, upstream releases long term support releases, as is 2.0 and then periodic point releases including all the accumulated bugfixes.

Only the latest upstream release gets full support from the upstream developers, everyone else is expected to first update to it before receiving any kind of support.

This bugfix release has already been uploaded to Zesty and automatically backported in the upstream PPAs for all Ubuntu releases. So far without any reported regression.

This should qualify under the minor upstream bugfix release allowance of the SRU policy, letting us SRU this without paperwork for every single change included in this upstream release.

Once the SRU hits -updates, we will be backporting this to trusty-backports as well, making sure we have the same version everywhere.

Changed in lxcfs (Ubuntu):
status: New → Fix Released
Changed in lxcfs (Ubuntu Yakkety):
status: New → In Progress
Changed in lxcfs (Ubuntu Xenial):
status: New → In Progress
Changed in lxcfs (Ubuntu Trusty):
status: New → Triaged
importance: Undecided → Medium
Changed in lxcfs (Ubuntu Xenial):
importance: Undecided → Medium
Changed in lxcfs (Ubuntu Yakkety):
importance: Undecided → Medium
Changed in lxcfs (Ubuntu Trusty):
assignee: nobody → Stéphane Graber (stgraber)
Changed in lxcfs (Ubuntu Xenial):
assignee: nobody → Stéphane Graber (stgraber)
Changed in lxcfs (Ubuntu Yakkety):
assignee: nobody → Stéphane Graber (stgraber)
Revision history for this message
Stéphane Graber (stgraber) wrote :

We have autopkgtest coverage for this, combined with manual testing of it prior to release and we also look very closely at bug reports we get upstream from users of distributions which are already shipping this release.

Same thing we've been doing for the past 8 point releases, so far with all issues found before it hit -updates.

Revision history for this message
Stéphane Graber (stgraber) wrote :

Additionally, this package is in Zesty already and has been automatically pushed to thousands of users of the upstream LXCFS stable PPA and we monitor new bug reports for 2.0.6 very closely.

Revision history for this message
Stéphane Graber (stgraber) wrote :

Oops, bad copy/paste in the first comment, LXCFS has only had 5 previous point releases.

Revision history for this message
Brian Murray (brian-murray) wrote : Please test proposed package

Hello Stéphane, or anyone else affected,

Accepted lxcfs into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lxcfs/2.0.6-0ubuntu1~16.10.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in lxcfs (Ubuntu Yakkety):
status: In Progress → Fix Committed
tags: added: verification-needed
Changed in lxcfs (Ubuntu Xenial):
status: In Progress → Fix Committed
Revision history for this message
Brian Murray (brian-murray) wrote :

Hello Stéphane, or anyone else affected,

Accepted lxcfs into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lxcfs/2.0.6-0ubuntu1~16.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote : [lxcfs/yakkety] possible regression found

As a part of the Stable Release Updates quality process a search for Launchpad bug reports using the version of lxcfs from yakkety-proposed was performed and bug 1661991 was found. Please investigate this bug report to ensure that a regression will not be created by this SRU. In the event that this is not a regression remove the "verification-failed" tag from this bug report and add the tag "bot-stop-nagging" to bug 1661991 (not this bug). Thanks!

tags: added: verification-failed
Revision history for this message
Stéphane Graber (stgraber) wrote :

That bug report was invalid, it was caused by the reporter's system running out of memory during the package upgrade as can trivially be seen in the kernel log. Resetting SRU status.

tags: removed: verification-failed
Revision history for this message
Stéphane Graber (stgraber) wrote :

All tests pass, haven't seen any bug report for existing users and haven't seen any problem while using this for a week myself. Mark as verification-done.

tags: added: verification-done
removed: verification-needed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package lxcfs - 2.0.6-0ubuntu1~16.04.1

---------------
lxcfs (2.0.6-0ubuntu1~16.04.1) xenial; urgency=medium

  * New upstream bugfix release (2.0.6) (LP: #1660850):
    - Fix swap values with nested cgroups
    - tests: Fix run on ppc64el
    - Fix wrong scanning of memory.stat

  * Sync packaging with Zesty/Debian.

 -- Stéphane Graber <email address hidden> Tue, 31 Jan 2017 18:47:20 -0500

Changed in lxcfs (Ubuntu Xenial):
status: Fix Committed → Fix Released
Revision history for this message
Stéphane Graber (stgraber) wrote : Update Released

The verification of the Stable Release Update for lxcfs has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package lxcfs - 2.0.6-0ubuntu1~16.10.1

---------------
lxcfs (2.0.6-0ubuntu1~16.10.1) yakkety; urgency=medium

  * New upstream bugfix release (2.0.6) (LP: #1660850):
    - Fix swap values with nested cgroups
    - tests: Fix run on ppc64el
    - Fix wrong scanning of memory.stat

  * Sync packaging with Zesty/Debian.

 -- Stéphane Graber <email address hidden> Tue, 31 Jan 2017 18:50:16 -0500

Changed in lxcfs (Ubuntu Yakkety):
status: Fix Committed → Fix Released
Changed in lxcfs (Ubuntu Trusty):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.