[Bug 1871611] Re: multipath nvme, failed to install with multipath disabled install failed crashed with CalledProcessError

[🤖 prod-kernel-team-janitor]

The task "linux (Ubuntu)" has expired because it has had no new comments
or updates for more than three years.

If this issue is still present in an Ubuntu LTS kernel still under
active support, please reopen the bug and provide updated details. If
this issue was reported against an Ubuntu kernel no longer under active
support but the issue still exists in a currently supported Ubuntu
kernel, please open a new bug against that kernel version and provide
the updated details, with a reference link to the original bug.

This action was performed by an automated process maintained by the
Ubuntu Kernel Team.

** Tags added: kernel-autoclosed kernel-autoclosed-expired

** Changed in: linux (Ubuntu)
       Status: Confirmed => Expired

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

Title:
  multipath nvme, failed to install with multipath disabled install
  failed crashed with CalledProcessError

Status in curtin:
  Invalid
Status in subiquity:
  Incomplete
Status in linux package in Ubuntu:
  Expired

Bug description:
  multipath nvme, failed to install with multipath disabled install
  failed crashed with CalledProcessError

  
  so trying to install with nvme_core.multipath=0 set on the cmdline, and that fails.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: subiquity (1641)
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic ppc64le
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: ppc64el
  CasperVersion: 1.443
  CrashDB:
   {
          "impl": "launchpad",
          "project": "subiquity",
          "bug_pattern_url": "http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml"
       }
  Date: Wed Apr  8 11:35:20 2020
  ExecutablePath: /snap/subiquity/1638/usr/bin/subiquity
  InstallerLog: Error: [Errno 2] No such file or directory: 'logfile'
  InterpreterPath: /snap/subiquity/1638/usr/bin/python3.6
  LiveMediaBuild: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta ppc64el (20200408)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 1d6b:0107 Linux Foundation USB Virtual Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcAttrCurrent: snap.subiquity.subiquity (complain)
  ProcCmdline: /snap/subiquity/1638/usr/bin/python3 /snap/subiquity/1638/usr/bin/subiquity
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: ip=dhcp url=http://cdimage.ubuntu.com/hostname/daily-live/pending/focal-live-server-ppc64el.iso subiquity-channel=latest/edge nvme_core.multipath=0 http_proxy=http://91.189.89.11:3128 --- quiet
  ProcLoadAvg: 0.11 1.05 0.96 1/1380 14592
  ProcLocks:
   1: FLOCK  ADVISORY  WRITE 5503 00:18:751 0 EOF
   2: POSIX  ADVISORY  WRITE 5198 00:18:647 0 EOF
   3: POSIX  ADVISORY  WRITE 5520 00:18:760 0 EOF
  ProcSwaps: Filename				Type		Size	Used	Priority
  ProcVersion: Linux version 5.4.0-21-generic (buildd at bos02-ppc64el-028) (gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1)) #25-Ubuntu SMP Sat Mar 28 13:10:37 UTC 2020
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2
  PythonDetails: N/A
  SnapChannel:
   
  SnapRevision: 1638
  SnapUpdated: False
  SnapVersion: 20.03.3+git132.a0dae13d
  SourcePackage: subiquity
  Title: install failed crashed with CalledProcessError
  UpgradeStatus: No upgrade log present (probably fresh install)
  UsingAnswers: False
  VarLogDump_list: total 0
  cpu_cores: Number of cores present = 32
  cpu_coreson: Number of cores online = 32
  cpu_smt: SMT=4

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