curtin-dev team mailing list archive

[Ryan Harper <1876626@xxxxxxxxxxxxxxxxxx>]

This bug is believed to be fixed in curtin in version 20.1. If this is
still a problem for you, please make a comment and set the state back to
New

Thank you.

** Changed in: curtin
       Status: Fix Committed => Fix Released

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

Title:
  'toram' kernel parameter does not work with subiquity

Status in curtin:
  Fix Released
Status in subiquity:
  Fix Released

Bug description:
  When starting the installer with the 'toram' kernel parameter, the installation fails on probing multipath for /dev/shm with curtin command curthooks at curtin/util.py:141:
  Unknown device "/dev/shm": Inappropriate ioctl for device 

  Working 'toram' autoinstallations are handy for servers that do not
  have netboot, IPMI nor USB, but can boot from the same storage as
  normally and that storage can be written to out of band. In other
  words, installation starts from the same device as will be installed
  to.

  Since d-i is no longer available, netboot images that were suited for
  this can no longer be used.

  Use cases know to me include at least rented servers with hosting-
  provided rescue. There are a few other approaches such as manual
  bootstrapping, kexec and imaging that work. However, the toram
  approach would allow the same install method as with other types of
  servers and requires less manual effort.

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1876626/+subscriptions