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

[Richard Lovell]

Hi Dave,

The following output appears. I don't see an error relating to "no net-
BOOTIF.conf" now...just what's below...

ipconfig: BOOTIF: SIOCGIFINDEX: no such device
ipconfig: no devices to configure
/scripts/local-top/scsi: line 515: can't open '/run/net-BOOTIF.conf'
lvmetad is not active yet, using direct activation during sysinit


ip a # gives:
1: lo <LOOPBACK> mtu 65536 qdisc noop qlen 1
	link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enx847beb55c195: <BROADCAST, MULTICAST> mtu 1500 qdisc noop qlen 1000
	link/ether 84:7b:eb:55:c1:95 brd ff:ff:ff:ff:ff:ff


cat /proc/cmdline gives the mac of the usb-c network adapter (different mac to the previous command - above):

BOOT_IMAGE=ubuntu/amd64/generic/xenial/daily/boot-kernel nomodeset
isci_target_name=iqn.2004-05.com.ubuntu:maas:ephermeral-ubuntu-amd64
-generic-xenial-daily iscsi_target_ip=<ip of maas server>
iscsi_target_port=3260 iscsi_initiator=maas-enlist ip=::::maas-
enlist:BOOTIF ro root=/dev/disk/by-path/ip-<ip of maaas server>:3260
-iscsi-iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-amd64-generic-
xenial-daily-lun-1 overlayroot=tmpfs cloud-config-url=http://<ip of maas
serrver>:5420/MAAS/metadata/latest/enlist-preseed/?op=get_enlist_preseed
log_host=<ip of maas server> log_port=514
initrd=ubuntu/amd64/generic/xenial/daily/boot-initrd BOOTIF=01-9c-
eb-e8-3c-52-cc


lsmod gives:

/bin/sh: lsmod: not found


ipconfig:

ipconfig: no devices to configure


Other info:
Gave up waiting for root device. Common problems:
- Boot args (cat /proc/cmdline)
  - Check rootdelay = ( did the system wait long enough)
  - Check root= (did the system wait for the right device?)
- Missing modules (cat /proc/modules; ls /dev)
ALERT ..dropping to shell.

regards
Richard

-- 
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