boot-initrd from maas images do not have bcache modules
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
maas-images |
Fix Released
|
Medium
|
Scott Moser |
Bug Description
I tried to do the following, and saw failure to install.
$ NAME=maas-1-10; NODE=node-
$ maas smoser node set-storage-layout $NODE storage_
$ maas smoser nodes acquire name=$NAME
$ maas smoser node start $NODE hwe_kernel=hwe-v
The failure looks lilke this: http://
specifically, you see the hwe-v kernel booted and then:
....
The operation has completed successfully.
Warning: The resulting partition is not properly aligned for best performance.
The operation has completed successfully.
modprobe: FATAL: Module bcache not found.
An error occured handling 'bcache32': ProcessExecutio
Command: ['modprobe', 'bcache']
Exit code: 1
Reason: -
Stdout: ''
Stderr: ''
Unexpected error while running command.
Command: ['modprobe', 'bcache']
Exit code: 1
Reason: -
Stdout: ''
Stderr: ''
Related branches
Changed in maas-images: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in maas-images: | |
status: | Confirmed → Fix Committed |
Changed in maas-images: | |
assignee: | nobody → Scott Moser (smoser) |
Changed in maas-images: | |
status: | Fix Committed → Fix Released |
I've pushed the fix for this to maas-images. The initramfs built after revno 245 will have bcache module installed. I only added the module, did not install the bcache-tools package into the trusty->vivid images.
Also tested that the install above actually worked.