John, the difference between those two that I can see is that now the
image was creating with cgroupsv2 present when preseeding (which was the
expected change), but the runtime image does not use cgroupsv2 and thus
things need to be regenerated.

This is sort of expected since the runtime kernel is focal, which is not
configured by default to use cgroupsv2.

In general, I'm not sure we can solve this problem if we expect to
produce one image that when launched everywhere will always be
preseeded, since as shown by this output we would need to somehow
simultaneously both the runtime system using cgroupsv1 and the runtime
system using cgroupsv2.

The change you landed is correct in that it will ensure a system using
cgroupsv2 (i.e. impish server) will get the best speed, but a system
using cgroupsv1 (i.e. focal server) will not get the best possible
speed. I'm not sure which case CPC wants to optimize for.

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

Title:
  snapd.seeded.service never finishes on non-amd64

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1944004/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to