Hi Ashley,

Marking this incomplete for MAAS (although I think it is invalid).
Opening a task for curtin and for the kernel team. The error in curtin
implies is the same issue as [1]. Judging from [2], it seems that it
should already be fixed:

May 21 10:57:03 geodude cloud-init[1643]: Processing triggers for libc-bin 
(2.27-3ubuntu1) ...
May 21 10:57:04 geodude cloud-init[1643]: curtin: Installation started. 
(18.1-623-gae48e86-0ubuntu1~ubuntu16.04.1)
May 21 10:57:04 geodude cloud-init[1643]: third party drivers not installed or 
necessary.
May 21 10:57:05 geodude kernel: [   49.126408] bcache: register_bcache() error 
/dev/sda3: device already registered (emitting change event)
May 21 10:57:05 geodude kernel: [   49.166935] bcache: register_bcache() error 
/dev/sda3: device already registered (emitting change event)
May 21 10:57:05 geodude kernel: [   49.209233] bcache: register_bcache() error 
/dev/sda3: device already registered (emitting change event)
May 21 10:57:05 geodude kernel: [   49.254763] bcache: register_bcache() error 
/dev/sda3: device already registered (emitting change event)
May 21 10:57:05 geodude kernel: [   49.319986] bcache: register_bcache() error 
/dev/sda3: device already registered (emitting change event)


The ephemeral environment kernel seems to be:

May 21 10:56:43 geodude kernel: [    0.000000] Linux version
4.15.0-20-generic (buildd@lgw01-amd64-039) (gcc version 7.3.0 (Ubuntu
7.3.0-16ubuntu3)) #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 (Ubuntu
4.15.0-20.21-generic 4.15.17)


[1]: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729145
[2]: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729145/comments/54

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1772490

Title:
  bcache: register_bcache() error

Status in curtin:
  New
Status in MAAS:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  We have a few runs over the weekend failed to deploy with maas 2.3.3.

  May 21 11:33:50 swoobat maas.node: [info] geodude: Status transition from 
DEPLOYING to FAILED_DEPLOYMENT
  May 21 11:33:50 swoobat maas.node: [error] geodude: Marking node failed: Node 
operation 'Deploying' timed out after 40 minutes.

  https://solutions.qa.canonical.com/#/qa/testRun/67dae845-b22e-
  4de1-9b30-0ecb28eb3c35

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1772490/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to