Boot from Ubuntu volume on baremetal node incomplete

Bug #1716794 reported by Ramamani Yeleswarapu on 2017-09-12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Michael Turek
Nguyen Van Trung

Bug Description

Spawning an instance on baremetal node to boot from a cinder volume doesn't find the root device and drops to shell with <initramfs> prompt:

Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Gave up waiting for root device. Common problems:
 - Boot args (cat /proc/cmdline)
   - Check rootdelay= (did the system wait long enough?)
   - Check root= (did the system wait for the right device?)
 - Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/disk/by-label/cloudimg-rootfs does not exist. Dropping to a shell!

BusyBox v1.21.1 (Ubuntu 1:1.21.0-1ubuntu1) built-in shell (ash)
Enter 'help' for a list of built-in commands.


Same outcome for pre-built or Disk Image Builder created image of Ubuntu.

$ sudo wget
$ glance image-create --name trusty-server-cloudimg-amd64 --visibility public --disk-format qcow2 --container-format bare < trusty-server-cloudimg-amd64-disk1.img
$ openstack volume create --size 10 --image d1bd7d56-2888-44ae-93e8-7ddb0c8b7643 --bootable trustyimg
$ openstack server create --flavor baremetal --nic $net_id --volume trustyimg --key-name default trustyserver

Console output:

A workaround is creating an image manually[1] with the following setup before shutting down the instance.

apt-get install open-iscsi -y
echo "ISCSI_AUTO=true" > /etc/iscsi/iscsi.initramfs
update-initramfs -u


Discussion from the ironic boot from volume meeting last week indicated that mjturek would work on a dib element to help automate this for users.

Changed in ironic:
status: New → In Progress
importance: Undecided → High
assignee: nobody → Michael Turek (mjturek)
Ruby Loo (rloo) wrote :

No patch has been submitted for this yet, so changing status to 'Triaged'.

Changed in ironic:
status: In Progress → Triaged
Michael Turek (mjturek) wrote :

Hey Ruby,

So I think we're solving this solely through a diskimage-builder patch [0] though there may be some work needed on the ironic side to properly test the element. I'm going to set it to 'In Progress' but please revert if you disagree!


Changed in ironic:
status: Triaged → In Progress
Dmitry Tantsur (divius) on 2018-02-19
Changed in diskimage-builder:
status: New → In Progress
Changed in ironic:
status: In Progress → Incomplete
Changed in diskimage-builder:
assignee: nobody → Nguyen Van Trung (trungnv)

Submitter: Zuul
Branch: master

commit 91e3b72a23a4bde3c811cedf2224f682aa4d99b7
Author: Michael Turek <email address hidden>
Date: Thu Oct 12 10:38:23 2017 -0400

    Add iscsi-boot element

    This patch adds an element that handles the configuration for
    creating a disk capable of being a remote root filesystem through
    iSCSI on Ubuntu and Debian images.

    Change-Id: Ibf9e39d2bdab530106015f156d23d28029d12b0d
    Closes-bug: #1716794

Changed in diskimage-builder:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers