yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1933793] Re: Can't enlist/commission with large number of bcache devices

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Launchpad Bug Tracker <1933793@xxxxxxxxxxxxxxxxxx>
Date: Tue, 31 Aug 2021 04:17:21 -0000
Reply-to: Bug 1933793 <1933793@xxxxxxxxxxxxxxxxxx>
Sender: noreply@xxxxxxxxxxxxx

[Expired for MAAS because there has been no activity for 60 days.]

** Changed in: maas
       Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1933793

Title:
  Can't enlist/commission with large number of bcache devices

Status in cloud-init:
  Expired
Status in MAAS:
  Expired

Bug description:
  MAAS 2.9 or 3.0, commissioning image 18.04 or 20.04

  Registered a number of servers with 24 drives, created 20 bcache devices.
  Provisioned servers and then released them.
  Now I can only enlist or commission them one time of of 10 at max.
  The server start booting from PXE, gets the address, downloads kernel and initramfs, starts mounting rootfs (remote) but going through the list of bcache devices takes too long so the server can't reach the point of activating network adapters so the rootfs mount fails and the server falls into rootfs console.

  This bug is somewhat similar to the one forcing to use wipe-bcache
  commissioning script from FE, but it is not applicable here as
  commissioning can't complete either.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1933793/+subscriptions