[Bug 1639202] Re: Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

[Dave Chiluk]

Do you know where the 9c-eb-e8-3c-52-cc originates from?  There is
nothing we can do so long as the request to maas originates from the 9c-
eb-e8-3c-52-cc mac address.  If the firmware is somehow masking the
actual mac address with the above then that needs to be fixed in the
firmware, or via a firmware setting.

Please attempt to figure out where the 9c-eb-e8-3c-52-cc is.
If it helps a mac search on 9c-eb-e8 yeilds: BizLink (Kunshan) Co. Ltd.
A mac search of 84-7b-eb yeilds Dell Inc.

I suspect they are really the same device.  I have a feeling the usb-c
adapter or docking station you are using is really just Bizlink device
that Dell has rebranded.

This really looks like a firmware bug, where the firmware uses the non-
rebranded mac of the device for pxe while in efi, and the rebranded mac
address in the OS after boot.

Have you tried updating the firmware on your machine, and possibly also
the firmware of the usb-c device?

Thanks,
Dave Chiluk

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1639202

Title:
  Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

Status in MAAS:
  Invalid
Status in maas-images:
  New
Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  After upgrade from MAAS 2.0 to MAAS 2.1:

  Cannot enlist/commission client machines via network boot (or pre-
  staging machine) when using usb-c network adapter D59GG (e.g.
  Precision 5510). This was working ok with MAAS 2.0.

  Using the Xenial 16.04 base image for enlist/commission (no minimum
  kernel set).

  Enlist/Commission/Deploy works fine with other laptop and desktop
  models which have a built in NIC.

  From an already deployed Precision 5510 system (16.04.1) I can see the
  following module is loaded when the usb-c adapter is connected (and
  working):

  $ lsmod
  usbnet	45056 1 cdc_ether

  
  Errors received on client during enlisting with MAAS:

  no /run/net-bootif.conf
  lvmetad is not activated
  ...invalid path for logical volume.
  gave up waiting for root device
  common problems: boot args (cat /proc/cmdline)
  check rootdelay = (did system wait long enough)
  check root = (did the system wait for the right device?)
  missing modules (cat /proc/modules)
  ALERT!  /dev/disk/by-path/ip-<ipaddress>:3260-iscsi-iqn,2004.05.com.ubuntu:maas:ephemeral-ubuntu-amd64-generic-xenial-daily-lun-1 does not exist. Dropping to shell!
  usbcore: registered new interface driver usbhid
  usbhid: USB HID core driver

  - cat /proc/cmdline shows mac address that of usb-c network adapter.
  - cat /proc/modules includes “usbnet 45056 cdc_ether, Live 0xffffffffc009c000”
  - cat /proc/modules | grep usb … includes “ usbnet 45056 and usbhid 49152”

  
  I've tried enlisting with older boot image and different kernel versions (14.04 and 16.04 with ga-16.04, hwe-16.04 set) but get the same problem.

  It seems like the usb-c network adapter isn't loading properly or
  maybe just not quickly enough?

  Please let me know if you require any more info. I can provide info
  from /var/log/maas/* and dpkg -l '*maas*'|cat if need be.

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