group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1915571@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package livecd-rootfs - 2.525.54

---------------
livecd-rootfs (2.525.54) bionic; urgency=medium

  * Add grub config to produce console output to allow buildd vm images to
    produce console output in lxd vms (LP: #1915571)

 -- Cody Shepherd <cody.shepherd@xxxxxxxxxxxxx>  Fri, 21 May 2021
17:30:56 -0700

** Changed in: livecd-rootfs (Ubuntu Bionic)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1915571

Title:
  Cannot start bash session for buildd vm images in LXD vm

Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  Incomplete
Status in livecd-rootfs source package in Bionic:
  Fix Released
Status in livecd-rootfs source package in Focal:
  Fix Released
Status in livecd-rootfs source package in Groovy:
  Fix Released

Bug description:
  Ubuntu "bootable" buildd vm images, if imported into lxd and booted in
  a VM container, cannot produce an interactive bash session via, e.g.
  `lxd exec <name> bash`.

  This appears to be a problem of the buildd image lacking grub settings
  to produce console output on ttyS0. Lack of console output also
  prevents the required manual install of the lxd agent as detailed in
  this [1] Discourse post about booting Ubuntu in lxd vms.

  
  [Impact] 

   * This negatively impacts the user experience of Ubuntu buildd images
  in lxd, which is one of the target environments for the buildd images

  [Test Case]

   * create a metadata.yaml file for the buildd image (these will soon
  be downloadable from cloud-images.ubuntu.com/buildd):

  {                                                                                                                                                                       
      "architecture": "x86_64",                                                   
      "creation_date": <unix timestamp>,                                                
      "properties": {                                                             
          "architecture": "amd64",                                                
          "description": "Ubuntu buildd focal amd64",                             
          "os": "Ubuntu",                                                         
          "series": "focal"                                                       
      }                                                                           
  }

   * tar the metadata.yaml file into <name>.tar.xz
   * obtain the focal buildd image of your choice, e.g. from [2]
   * import the image into lxd: `lxd image import <name>.tar.xz <buildd-image>.img`
   * follow the "extra steps for official Ubuntu images" in [1] to init, configure, and start a lxd vm using the image by its fingerprint
   * Attempt console log in via `lxc console <vm name>` or a bash session via `lxc exec <vm name> bash`
   * Note that without console output it is not possible to log in via the lxc console to install the lxd agent, and therefore not possible to obtain a bash session via lxc exec

  [Where problems could occur]

   * Turning on console output requires changing grub configs; certain
  values of these configs could break current expectations about buildd
  image behavior

  [Other Info]
   
   * This issue affects buildd images from all suites, but the lxd-agent-loader package is only available for focal+

  [1] https://discuss.linuxcontainers.org/t/running-virtual-machines-with-lxd-4-0/7519
  [2] http://cloud-images.ubuntu.com/buildd/releases/focal/release/focal-server-cloudimg-amd64-disk.img

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1915571/+subscriptions