mounting of writable paths should respect rootdelay=X

Bug #1465842 reported by Ben Howard
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Snappy
Status tracked in Trunk
15.04
Fix Released
Critical
Ricardo Salveti
Trunk
Invalid
High
Ricardo Salveti

Bug Description

The ubuntu-core-rootfs script in initial ramdsik initrd.img-3.19.0-16-generic report panic “cannot find writable partition”
Because the script only wait for %root% partition and /dev/sda5 partition is not ready.

I have added following code to the script, to confirm it’s a timing issue.
       echo $(ls /dev/disk/by-label) >/dev/kmsg || true
        path=$(get_partition_from_label "$writable_label")
        [ -n "$path" ] || sleep 3
        [ -n "$path" ] ||echo "retry wait 3 seconds" >/dev/kmsg || true
        [ -n "$path" ] || path=$(get_partition_from_label "$writable_label")
        [ -n "$path" ] || panic "cannot find '$writable_label' partition"

Logs,
[ 13.047190] initrd: mounting /dev/sda3
[ 13.050213] EXT4-fs (sda3): couldn't mount as ext3 due to feature incompatibilities
[ 13.053662] EXT4-fs (sda3): couldn't mount as ext2 due to feature incompatibilities
[ 13.192459] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)
[ 13.196587] initrd: mounting /run
[ 13.201201] Temporary\x20Storage system-a system-boot  don’t have ‘writable ‘
[ 16.208151] retry wait 3 seconds
[ 16.221709] initrd: checking filesystem for writable partition
[ 16.231462] random: nonblocking pool is initialized
[ 16.235143] EXT4-fs (sda5): couldn't mount as ext3 due to feature incompatibilities => after 3 seconds writable partition sda5 was discovered

Revision history for this message
Ben Howard (darkmuggle-deactivatedaccount) wrote :

In speaking with rsalveti, it looks like the cause here is rootdelay=X is not respected for the writable partition.

Changed in snappy:
status: New → Confirmed
importance: Undecided → Critical
Revision history for this message
Ricardo Salveti (rsalveti) wrote :

Can you give it a try with image 90? (15.04/edge)

Revision history for this message
Ben Howard (darkmuggle-deactivatedaccount) wrote :

Instance is still not finding /writable. Attached initrd from an instance.

Revision history for this message
Ricardo Salveti (rsalveti) wrote :

The attached initrd is still containing the old code (and the old kernel, 3.19.0-18-generic). The new kernel is 3.19.0-21-generic, so the new initrd would be called initrd.img-3.19.0-21-generic.

Revision history for this message
qingfuw (qingfuw) wrote :

I have checked the log scot attached, obviously writable partition /dev/sda5 is mounted, and cloud-init was started.
My guess is that , the user name provided in ovf.xml is not Ubuntu. I don't know how exactly what will happen if the user name is not Ubuntu , just my guess.

Revision history for this message
Ben Howard (darkmuggle-deactivatedaccount) wrote :

I'm closing this out as we haven't seen it on a recent launch of Snappy. Further, we are working torwards arbitrary users and expect that Cloud-init/WALinuxAgent might have the bits in place for 15.04.4.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.