[Bug 1976287] Re: casper: qemu instances too small during autopkgtest (potential OOM failures)

[Steve Langasek]

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

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to casper in Ubuntu.
https://bugs.launchpad.net/bugs/1976287

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

Status in casper package in Ubuntu:
  Fix Released
Status in casper source package in Focal:
  In Progress
Status in casper source package in Jammy:
  Fix Committed
Status in casper source package in Kinetic:
  Fix Released

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1976287/+subscriptions