[Bug 728088] Re: iscsi root with or without auth fails to boot

[Colin Watson]

I've been debugging this on Amos' system (thanks!).

The problem isn't AppArmor as such.  In fact, the real problem is that
the network interface needed for iSCSI isn't being protected from later
modification as it should be, so, whenever the network-interface job
happens to fire for that interface in the real system, it effectively
takes down the root filesystem.  This tends to happen somewhere around
the time that AppArmor starts, but that's just a coincidence.

This is happening because we run configure_networking in a subshell to
avoid '. /tmp/net-*.conf' from killing the entirety of /scripts/local-
top/iscsi if no network devices are available yet, and then expect the
value of DEVICE from that subshell to be available later so that we can
write it to /dev/.initramfs/open-iscsi.interface (which /etc/init/iscsi-
network-interface.conf uses).  Moving the code that uses DEVICE into
that same subshell fixes the problem.  It also makes sense to wait for
udev to settle before doing any of this; I don't think that's vital, but
it should reduce noisy error messages and it's what I've tested.

I'm going to do a bit more testing of this, and then upload to oneiric
and natty-proposed.

** Package changed: debian-installer (Ubuntu) => open-iscsi (Ubuntu)

** Also affects: open-iscsi (Ubuntu Oneiric)
   Importance: High
     Assignee: Colin Watson (cjwatson)
       Status: In Progress

** Changed in: open-iscsi (Ubuntu Natty)
       Status: Confirmed => Triaged

** Changed in: open-iscsi (Ubuntu Oneiric)
    Milestone: None => oneiric-alpha-1

** Changed in: open-iscsi (Ubuntu Natty)
    Milestone: None => natty-updates

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to debian-installer in Ubuntu.
https://bugs.launchpad.net/bugs/728088

Title:
  iscsi root with or without auth fails to boot

Status in “open-iscsi” package in Ubuntu:
  In Progress
Status in “open-iscsi” source package in Natty:
  Triaged
Status in “open-iscsi” source package in Oneiric:
  In Progress

Bug description:
  Binary package hint: debian-installer

  Natty alpha3 test iso's for ubuntu-server amd64 (haven't tested i386
  yet).

  Running the iscsi auth and unauth tests.

  Installation is fine. Before reboot, I copy vmlinuz and initrd.img to
  tftp server.

  System boots ok, till it gets past apparmor, then it has issues, I
  assume something with bringing up networking is wiping out the iscsi
  config?

  Screen shows:

  fsck version ......
      /dev/sda1  clean, 52412,491526 files    262116/1965824 blocks
  * Starting AppArmor profiles     [ OK ]

  (long pause)

  [ 130.xxxxxx] end_request: I/O error, dev sda, sector 8653696
  [ 130.xxxxxx] end_request: I/O error, dev sda, sector 8653696
  /proc/self/fd/10: 30: telinit: Input/output error
  [ 130.xxxxxx] end_request: I/O error, dev sda, sector 838656
  [ 130.xxxxxx] end_request: I/O error, dev sda, sector 838656
  [ 130.xxxxxx] end_request: I/O error, dev sda, sector 352768
  [ 130.xxxxxx] end_request: I/O error, dev sda, sector 352768
  [ 130.xxxxxx] EXT4-fs error (device sda1) in ext4_reserve_inode_write:5620: Journal has aborted
  [ 130.xxxxxx] EXT4-fs (sda1): previous I/O error to superblock detected
  [ 130.xxxxxx] end_request: I/O error, dev sda, sector 2048
  [ 130.xxxxxx] end_request: I/O error, dev sda, sector 4724736
  [ 130.xxxxxx] end_request: I/O error, dev sda, sector 291584
  [ 130.xxxxxx] end_request: I/O error, dev sda, sector 8669024
  [ 130.xxxxxx] end_request: I/O error, dev sda, sector 8669024
  [ 130.xxxxxx] end_request: I/O error, dev sda, sector 8669024
  [ 130.xxxxxx] end_request: I/O error, dev sda, sector 1305064
  [ 130.xxxxxx] end_request: I/O error, dev sda, sector 1305064
  [ 130.xxxxxx] end_request: I/O error, dev sda, sector 1305064
  [ 130.xxxxxx] end_request: I/O error, dev sda, sector 1300856
  [ 130.xxxxxx] end_request: I/O error, dev sda, sector 1300856