1. 16.04 kernel version = 4.4.0-42-generic is the result of uname -r
from the 5510 that already had 16.04 installed.

2. 4.4.0-47-generic is the kernel version used during commissioning
(when it drops to shell, this is what uname -r provides)

3. In /sys/class/net I see: enx847beb55c195 ->
../../devices/pci0000:00/0000:00:1d.6/0000:06:00.0/0000:07:02.0/0000:0a:00.0/usb4/4-1/4-1:1.0/net/enx847b4b55c195
( so the usb is present here)

4. lsbusb -vv output is attached.

5. We're using daily images... v3 is being used to download from
https://images.maas.io/ephemeral-v3/daily. Then it seems to use v1 to
import into the local rack controller (see below from maas.log).

Nov 30 07:07:32 servername maas.import-images: [INFO] Downloading image 
descriptions from http://images.maas.io/ephemeral-v3/daily/
Nov 30 07:07:33 servername maas.bootsources: [INFO] Updated boot sources cache.
Nov 30 07:07:33 servername maas.bootresources: [INFO] Started importing of boot 
images from 1 source(s).
Nov 30 07:07:33 servername maas.import-images: [INFO] Downloading image 
descriptions from http://images.maas.io/ephemeral-v3/daily/
Nov 30 07:07:34 servername maas.bootresources: [INFO] Importing images from 
source: http://images.maas.io/ephemeral-v3/daily/
Nov 30 07:07:36 servername maas.bootresources: [INFO] Finished importing of 
boot images from 1 source(s).
Nov 30 07:07:36 servername maas.import-images: [INFO] Started importing boot 
images.
Nov 30 07:07:36 servername maas.import-images: [INFO] Downloading image 
descriptions from http://localhost:5240/MAAS/images-stream/streams/v1/index.json
Nov 30 07:07:36 servername maas.import-images: [INFO] Finished importing boot 
images, the region does not have any new images.


** Attachment added: "lsusb -vv output from 5510 with 16.04 installed"
   
https://bugs.launchpad.net/maas/+bug/1639202/+attachment/4785173/+files/lsusbvv-output.txt

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

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