casper: qemu instances too small during autopkgtest (potential OOM failures)

Bug #1976287 reported by Andrea Righi
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
casper (Ubuntu)
Fix Released
Undecided
Unassigned
Focal
Fix Released
Undecided
Unassigned
Jammy
Fix Released
Undecided
Unassigned
Kinetic
Fix Released
Undecided
Unassigned

Bug Description

[Impact]

During autopkgtest we are creating VMs with 768MB of RAM, that used to be enough in the past, but nowdays we typically require more memory and we may trigger some sporadic out-of-memory failures during autopkgtest.

[Test case]

Run autopkgtest with a recent kernel (e.g., 5.15 or above).

[Fix]

Bump up the memory size to 1G.

[Regression potential]

We may see regressions in test systems with a small amount of memory (in the host / hypervisor), because after this change we need more RAM in order to run and complete autopkgtest successfully.

Related branches

Revision history for this message
Andrea Righi (arighi) wrote :

Fix for focal (where we are experiencing regressions with hwe-5.15) in the attached debdiff.

Andrea Righi (arighi)
summary: - casper: qemu image too small in autopkgtest
+ casper: qemu instances too small during autopkgtest (potential OOM
+ failures)
tags: added: patch
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

Although this is autopkgtest change only, it affects testing of kernels, thus it would be nice to publish this SRU without keeping it in -proposed only.

Changed in casper (Ubuntu Focal):
status: New → In Progress
Changed in casper (Ubuntu Jammy):
status: New → In Progress
Changed in casper (Ubuntu Kinetic):
status: New → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package casper - 1.471

---------------
casper (1.471) kinetic; urgency=medium

  * Increase memory for qemu autopkgtest instances to 1G (LP: #1976287)

 -- Andrea Righi <email address hidden> Mon, 30 May 2022 14:40:38 +0000

Changed in casper (Ubuntu Kinetic):
status: Fix Committed → Fix Released
Revision history for this message
Steve Langasek (vorlon) wrote :

casper should have no runtime impact on users as it should only be used on live images and not on installed systems, so I'm fine with this being released to -updates.

However, in general the expectation is that test-only fixes stay in -proposed in order to not needlessly impact users with downloads of updates, and that related packages re-test as necessary with all-proposed=1 for SRUs. The fact that the kernel can't do this is a gap that would be good to address.

Changed in casper (Ubuntu Jammy):
status: In Progress → Fix Committed
tags: added: verification-needed verification-needed-jammy
Revision history for this message
Steve Langasek (vorlon) wrote : Please test proposed package

Hello Andrea, or anyone else affected,

Accepted casper into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/casper/1.470.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. To properly test it you will need to obtain and boot a daily build of a Live CD for jammy. 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, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Revision history for this message
Steve Langasek (vorlon) wrote :

Hello Andrea, or anyone else affected,

Accepted casper into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/casper/1.445.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. To properly test it you will need to obtain and boot a daily build of a Live CD for focal. 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, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in casper (Ubuntu Focal):
status: In Progress → Fix Committed
tags: added: verification-needed-focal
Revision history for this message
Łukasz Zemczak (sil2100) wrote :

Hello Andrea, or anyone else affected,

Accepted casper into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/casper/1.445.3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. To properly test it you will need to obtain and boot a daily build of a Live CD for focal. 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, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Revision history for this message
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (casper/1.445.2)

All autopkgtests for the newly accepted casper (1.445.2) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

casper/1.445.2 (amd64)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/focal/update_excuses.html#casper

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

Revision history for this message
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (casper/1.445.3)

All autopkgtests for the newly accepted casper (1.445.3) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

casper/1.445.3 (amd64)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/focal/update_excuses.html#casper

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

This bug was fixed in the package casper - 1.445.3

---------------
casper (1.445.3) focal; urgency=medium

  * casper-md5check: correctly detect fsck.mode=skip if last
    in /proc/cmdline, and add a hint for users (LP: #1892369)

casper (1.445.2) focal; urgency=medium

  * Increase memory for qemu autopkgtest instances to 1G (LP: #1976287)

 -- Mauricio Faria de Oliveira <email address hidden> Sat, 27 Aug 2022 19:37:43 -0300

Changed in casper (Ubuntu Focal):
status: Fix Committed → Fix Released
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

the jammy autopkgtests with this change pass, thus we want to release this update.

this will ensure that future adt tests for jammy casper are good without without OOM kills.

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

This bug was fixed in the package casper - 1.470.1

---------------
casper (1.470.1) jammy; urgency=medium

  * Increase memory for qemu autopkgtest instances to 1G (LP: #1976287)

 -- Andrea Righi <email address hidden> Mon, 30 May 2022 14:40:38 +0000

Changed in casper (Ubuntu Jammy):
status: Fix Committed → Fix Released
Revision history for this message
Łukasz Zemczak (sil2100) wrote : Update Released

The verification of the Stable Release Update for casper has completed successfully and the package is now being 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.

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.