[Kernel-packages] [Bug 1916610] Re: MAAS booting with ga-20.04 kernel results in nvme bcache device can't be registered

2021-07-07 Thread Bill Wear
what version of MAAS?  there was a very similar nvme bcache issue
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910201) that was
Fix Released for MAAS around 2021-01-05, but i don't see it listed in
releases since then.  can you tell me what version of MAAS you're using?
i'd like to chase this back.

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

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

Title:
  MAAS booting with ga-20.04 kernel results in nvme bcache device can't
  be registered

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

Bug description:
  [  274.743265] cloud-init[3738]: Traceback (most recent call last):
  [  274.759256] cloud-init[3738]:   File 
"/curtin/curtin/commands/main.py", line 202, in main
  [  274.779262] cloud-init[3738]: ret = args.func(args)
  [  274.795270] cloud-init[3738]:   File "/curtin/curtin/log.py", line 
97, in wrapper
  [  274.811254] cloud-init[3738]: return log_time("TIMED %s: " % 
msg, func, *args, **kwargs)
  [  274.831256] cloud-init[3738]:   File "/curtin/curtin/log.py", line 
79, in log_time
  [  274.847264] cloud-init[3738]: return func(*args, **kwargs)
  [  274.863256] cloud-init[3738]:   File 
"/curtin/curtin/commands/block_meta.py", line 111, in block_meta
  [  274.883256] cloud-init[3738]: return meta_custom(args)
  [  274.899263] cloud-init[3738]:   File 
"/curtin/curtin/commands/block_meta.py", line 1911, in meta_custom
  [  274.919265] cloud-init[3738]: handler(command, 
storage_config_dict)
  [  274.935255] cloud-init[3738]:   File 
"/curtin/curtin/commands/block_meta.py", line 1652, in bcache_handler
  [  274.955255] cloud-init[3738]: bcache_dev = 
bcache.create_backing_device(backing_device, cache_device,
  [  274.975255] cloud-init[3738]:   File 
"/curtin/curtin/block/bcache.py", line 479, in create_backing_device
  [  274.995261] cloud-init[3738]: 
ensure_bcache_is_registered(backing_device, target_sysfs_path)
  [  275.015257] cloud-init[3738]:   File 
"/curtin/curtin/block/bcache.py", line 436, in ensure_bcache_is_registered
  [  275.035254] cloud-init[3738]: raise RuntimeError("bcache 
device %s can't be registered" %
  [  275.055257] cloud-init[3738]: RuntimeError: bcache device 
/dev/nvme1n1 can't be registered
  [  275.075255] cloud-init[3738]: bcache device /dev/nvme1n1 can't be 
registered

  Full log of the boot/error:
  https://pastebin.canonical.com/p/ggNDCwCtGq/

  Booting with hwe-20.04 works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1916610/+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


[Kernel-packages] [Bug 1918970] Re: Unable to netboot Ubuntu 18.04 and older on an IBM Z DPM Partition - no manual nor automatic qeth device configuration

2021-07-06 Thread Bill Wear
** Changed in: maas
   Status: New => Triaged

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

Title:
  Unable to netboot Ubuntu 18.04 and older on an IBM Z DPM Partition -
  no manual nor automatic qeth device configuration

Status in MAAS:
  Triaged
Status in Ubuntu on IBM z Systems:
  Triaged
Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in s390-tools package in Ubuntu:
  New

Bug description:
  I tried to deploy Ubuntu 18.04 with the GA-18.04 kernel on an IBM Z14
  DPM Partition.  The initrd fails to bring up network and thus fails to
  boot in MAAS. I haven't tried older versions of Ubuntu but suspect
  they also have the same bug.

  mount: mounting /dev on /root/dev failed: No such file or directory
  done.
  mount: mounting /run on /root/run failed: No such file or directory
  run-init: current directory on the same filesystem as the root: error 0
  Target filesystem doesn't have requested /sbin/init.
  run-init: current directory on the same filesystem as the root: error 0
  run-init: current directory on the same filesystem as the root: error 0
  run-init: current directory on the same filesystem as the root: error 0
  run-init: current directory on the same filesystem as the root: error 0
  run-init: current directory on the same filesystem as the root: error 0
  chvt: can't open console
  No init found. Try passing init= bootarg.
  Couldn't get a file descriptor referring to the console
  /scripts/panic/console_setup: line 133: can't create /dev/tty1: No such 
device o
  r address
  /scripts/panic/console_setup: line 1: can't open /dev/tty1: No such device or 
ad
  dress
  /scripts/panic/console_setup: line 1: can't create /dev/tty2: No such device 
or
  address
  /scripts/panic/console_setup: line 1: can't open /dev/tty2: No such device or 
ad
  dress
  /scripts/panic/console_setup: line 1: can't create /dev/tty3: No such device 
or
  address
  /scripts/panic/console_setup: line 1: can't open /dev/tty3: No such device or 
ad
  dress
  /scripts/panic/console_setup: line 1: can't create /dev/tty4: No such device 
or
  address
  /scripts/panic/console_setup: line 1: can't open /dev/tty4: No such device or 
ad
  dress
  /scripts/panic/console_setup: line 1: can't create /dev/tty5: No such device 
or
  address
  /scripts/panic/console_setup: line 1: can't open /dev/tty5: No such device or 
ad
  dress
  /scripts/panic/console_setup: line 1: can't create /dev/tty6: No such device 
or
  address
  /scripts/panic/console_setup: line 1: can't open /dev/tty6: No such device or 
ad
  dress
   
   
  BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu3.3) built-in shell (ash)
  Enter 'help' for a list of built-in commands.
   
  (initramfs) [6n
  [   78.114530] random: crng init done
  [   78.114538] random: 7 urandom warning(s) missed due to ratelimiting

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1918970/+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