iscsi root: iscsi not started in initramfs

[Dave Gilbert]

Ubuntu server daily disk; 20120908 (amd64)

I have a kvm guest which is diskless, I've done an install (off CD image) onto an iscsi disk (that's provided by another VM running tgt).
But it won't boot after install (maybe related to 881388?)
(Host is Quantal as of today but with 3.5.2-030502 to get around bug 1045027)

The install goes apparently fine; I tell it the IP of the target, pick the (only) target, and there's no auth.
I just pick openssh-server as the only item of task to install.

I boot, bring up iPXE's command prompt (with ctrl-b) and enter:
dhcp net0
sanboot iscsi:192.168.122.10:::1:iqn.2008-09.com.example:server1.share1

and it brings up grub and starts to boot and eventually lands at the initramfs prompt saying it can't find the root volume.

Using rescue mode I can see a lot of

ipconfig: no devices to configure
and
/scripts/local-top/iscsi: .: line 505: can't open '/run/net-*.conf'
(it's right there isn't any)
and *then* I see the messages about the networking coming up and finding a link.

If I manually ifconfig the interface and run /scripts/local-top/iscsi it brings it up and I can continue the boot and it boots OK.

This happens with the network interface configured as e1000 and hypervisor default (8139 something)

I'll attach the VM config from the host.

Dave

[Colin Watson (cjwatson)]

Moving to partman-iscsi for now as my initial guess is that the configuration created by the installer is wrong, but it's also possible that this needs to be fixed in open-iscsi.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Nick Maslov (azpekt)]

Hi,

I`m having the same issue. After manually (or via GRUB parameters) setting up the IP, I need to run the iscsi script again to continue the booting process.

Anyone have any luck dealing with it?

Regards,
NM

[Mike Pontillo (mpontillo)]

I dusted off an old [x86 32-bit] laptop with an e100 card and observed this issue in conjunction with MAAS 1.9.

Oddly enough, when I auto-enlist the node for the first time, I see this bug. But commissioning and deployment work perfectly.

[Mike Pontillo (mpontillo)]

(Note: I saw this with each of the Trusty, Utopic, and Vivid kernels.)

[Andres Rodriguez (andreserl)]

Hi!

**This is an automated message**

We believe this is no longer an issue in the latest MAAS releases. As such, we are marking this bug report as invalid. If you believe this is still an issue, please re-open this bug report.

Thanks