yahoo-eng-team team mailing list archive

[Chad Smith <2007400@xxxxxxxxxxxxxxxxxx>]

Marking invalid as it seems this is unrelated to cloud-init. Please re-
open if this surfaces again.

** Changed in: cloud-init
       Status: Triaged => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/2007400

Title:
  eatmydata enabled by default results in apt packages not correctly
  installed

Status in cloud-init:
  Invalid

Bug description:
  I'm using LXD 5.0 (LTS) on Ubuntu 22.04 to launch containers and virtual machines. I am using cloud-init in LXD's user.user-data field to install some apt packages when the container or VM is launched. For example, I have the following cloud-config section:
      package_update: true
      packages:
        - openssh-server

  The server is launched as follows:
  lxc launch images:ubuntu/jammy/desktop myhostname --vm

  However, when the server is launched, the apt package is listed as successfully installed, but there are no files associated with it:
  util.py[DEBUG]: apt-install [eatmydata apt-get --option=Dpkg::Options::=--force-confold --option=Dpkg::options::=--force-unsafe-io --assume-yes --quiet install openssh-server ... took 25.031 seconds
  handlers.py[DEBUG]: finish: modules-final/config-package-update-upgrade-install: SUCCESS: config-package-update-upgrade-install ran successfully

  Yet "dpkg -L openssh-server" shows:
  Package 'openssh-server' does not contain any files (!)

  This results in an unusable system. I don't know what "eatmydata" is
  or why it is enabled by default, but does indeed appear to be eating
  this data and resulting in an unusable server.

  It looks like there's a sparsely documented option called apt_get_wrapper which seems to let you disable "eatmydata":
  https://cloudinit.readthedocs.io/en/18.5/topics/examples.html?highlight=eatmydata#additional-apt-configuration

  I configured this to disable "eatmydata" and sure enough, I am now
  able to successfully create a virtual machine. Is it possible to
  better document the use of eatmydata in cloud-init, and moreover maybe
  consider disabling it by default so you have to opt-in to get the
  performance benefits it provide (while accepting the risk of possible
  data corruption)?

  Thanks!

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