Bcache on raid won't deploy for hwe > hwe-t on Trusty

[José Pekkarinen]

Hi,

Deploying a trusty server which has configured 2 raid devices(one for the system, and one for storage), I try to cache the storage raid with bcache on MaaS. The deployment proceed correctly if I select the hwe-t kernel before deploying, however, for any newer kernel it will fail. For hwe-u and hwe-v, maas reports the following output:

Creating new GPT entries.
The operation has completed successfully.
Error: /dev/nvme0n1: unrecognised disk label
Error: /dev/nvme0n1: unrecognised disk label
Error: /dev/md1: unrecognised disk label
Error: /dev/md1: unrecognised disk label
Error: /dev/nvme0n1: unrecognised disk label
Invalid number 0 of holding devices: "[]"
An error occured handling 'bcache0': ValueError - Invalid number 0 of holding devices: "[]"
Invalid number 0 of holding devices: "[]"
Installation failed with exception: Unexpected error while running command.
Command: ['curtin', 'block-meta', 'custom']
Exit code: 3
Reason: -
Stdout: 'Creating new GPT entries.\nThe operation has completed successfully.\nError: /dev/nvme0n1: unrecognised disk label\nError: /dev/nvme0n1: unrecognised disk label\nError: /dev/md1: unrecognised disk label\nError: /dev/md1: unrecognised disk label\nError: /dev/nvme0n1: unrecognised disk label\nInvalid number 0 of holding devices: "[]"\nAn error occured handling \'bcache0\': ValueError - Invalid number 0 of holding devices: "[]"\nInvalid number 0 of holding devices: "[]"\n'
Stderr: ''

For hwe-w and hwe-x it shows:

Creating new GPT entries.
The operation has completed successfully.
Error: Could not stat device /dev/nvme0n1 - No such file or directory.
An error occured handling 'nvme0n1': OSError - [Errno Failed to find device at path: %s] /dev/nvme0n1
[Errno Failed to find device at path: %s] /dev/nvme0n1
Installation failed with exception: Unexpected error while running command.
Command: ['curtin', 'block-meta', 'custom']
Exit code: 3
Reason: -
Stdout: "Creating new GPT entries.\nThe operation has completed successfully.\nError: Could not stat device /dev/nvme0n1 - No such file or directory.\nAn error occured handling 'nvme0n1': OSError - [Errno Failed to find device at path: %s] /dev/nvme0n1\n[Errno Failed to find device at path: %s] /dev/nvme0n1\n"
Stderr: ''

Thanks!

José.
---
AlsaDevices:
 total 0
 crw-rw---- 1 root audio 116, 1 Oct 11 19:44 seq
 crw-rw---- 1 root audio 116, 33 Oct 11 19:44 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 14.04
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
Package: linux (not installed)
PciMultimedia:

ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 cirrusdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-93-generic root=UUID=6872cb1e-3766-4ff3-9de5-11ffd99c3fc9 ro console=tty1 console=ttyS0
ProcVersionSignature: Ubuntu 3.13.0-93.140-generic 3.13.11-ckt39
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-93-generic N/A
 linux-backports-modules-3.13.0-93-generic N/A
 linux-firmware 1.127.22
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty uec-images
Uname: Linux 3.13.0-93-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

WifiSyslog:

_MarkForUpload: True
dmi.bios.date: 01/01/2011
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2011:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-trusty:cvnBochs:ct1:cvr:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-trusty
dmi.sys.vendor: QEMU

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1635725

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[José Pekkarinen (koalinux)]

apport information

[José Pekkarinen (koalinux)]

apport information

[José Pekkarinen (koalinux)]

apport information

[José Pekkarinen (koalinux)]

apport information

[José Pekkarinen (koalinux)]

apport information

[José Pekkarinen (koalinux)]

apport information

[José Pekkarinen (koalinux)]

apport information

[José Pekkarinen (koalinux)]

apport information

[José Pekkarinen (koalinux)]

apport information

[José Pekkarinen (koalinux)]

Hi,

I took the summary just now, so here you are.

Thanks!

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.9 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9-rc2

[José Pekkarinen (koalinux)]

I'm afraid that unless there is a way to list that kernel on MaaS to let it try to commission/deploy with it, this version is not testable for this problem. As stated a few comments before, the only kernel which deploys well in this setup is hwe-t, the rest always yield a failed deployment status.