deploy-ironic ramdisks do not boot: Failed to execute /init (error -28)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
devstack |
Fix Released
|
Undecided
|
Unassigned | ||
diskimage-builder |
Fix Released
|
Medium
|
Unassigned | ||
linux (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
The default ubuntu release for ramdisks was bumped to Trusty https:/
[ 23.154016] Failed to execute /init (error -28)
[ 23.154909] Starting init: /sbin/init exists but couldn't execute it (error -28)
[ 23.156388] Starting init: /bin/init exists but couldn't execute it (error -28)
[ 23.157490] Starting init: /bin/sh exists but couldn't execute it (error -28)
[ 23.160313] Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/
[ 23.164146] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.13.0-24-generic #46-Ubuntu
[ 23.164146] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
[ 23.164146] 0000000000000000 ffff88001a3a9ec0 ffffffff81715a64 ffffffff81a39f38
[ 23.164146] ffff88001a3a9f38 ffffffff8170ec65 0000000000000008 ffff88001a3a9f48
[ 23.164146] ffff88001a3a9ee8 ffffffff81a39a38 0000000013981396 0000000000001396
[ 23.164146] Call Trace:
[ 23.164146] [<ffffffff81715
[ 23.164146] [<ffffffff8170e
[ 23.164146] [<ffffffff81703
[ 23.164146] [<ffffffff81704
[ 23.164146] [<ffffffff81726
[ 23.164146] [<ffffffff81703
[ 23.164146] general protection fault: fff2 [#1] SMP
[ 23.164146] Modules linked in:
[ 23.164146] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.13.0-24-generic #46-Ubuntu
[ 23.164146] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
[ 23.164146] task: ffff88001a3a0000 ti: ffff88001a3a8000 task.ti: ffff88001a3a8000
[ 23.164146] RIP: 0010:[<
[ 23.164146] RSP: 0000:ffff88001a
[ 23.164146] RAX: 0000000014a814a8 RBX: ffffffff81a39f38 RCX: 0000000000000854
[ 23.164146] RDX: 00000000000014a8 RSI: 0000000000000000 RDI: 0000000000000046
#define ENOSPC 28 /* No space left on device */
Setting DIB_RELEASE=saucy fixes the issue. A saucy ramdisk is 83M compressed, 238M decompressed. trusty ramdisk is 87M compressed, 245M decompressed.
description: | updated |
description: | updated |
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
Changed in diskimage-builder: | |
status: | Triaged → Fix Released |
The trusty ramdisk fails to boot on a VM /w 512MB of RAM. Increasing that to 1GB fixes the issue, tho IMO the ramdisk release shouldn't impose such memory requirements.