[Bug 1883312] Re: [SRU] NVMe FC Auto-connect is not working for Ubuntu 20.04

[Jeff Lane]

Hi Laurie,
This has sat a while, I wanted to check up on it.  In general, we will not upgrade userspace packages in a released version of Ubuntu, however, we can certainly backport patches to fix bugs.

Alternately, if your customer has an Ubuntu Advantage agreement with us,
they can file a support case that way and our Sustaining Engineering
team would take a look and do what is necessary.

I'm happy to continue working on this to push bug fixes, but to do so,
I'd need to have access to the upstream git tree and a list of patches
needed to resolve the issue.  From there, I can work on an SRU to the
version of nvme-cli in Focal.

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

Title:
  [SRU] NVMe FC Auto-connect is not working for Ubuntu 20.04

Status in nvme-cli package in Ubuntu:
  New
Status in nvme-cli source package in Focal:
  New

Bug description:
  [SUMMARY]

  Auto-connect is not working for Ubuntu 20.04. However manual nvme
  discover and connect commands works.

  root at ubuntu2004:~# uname -a
  Linux ubuntu2004 5.4.0-25-generic #29-Ubuntu SMP Fri Apr 17 15:06:57 UTC 2020
  x86_64 x86_64 x86_64 GNU/Linux

  root at ubuntu2004:~# nvme version
  nvme version 1.9

  root at ubuntu2004:~# cat /sys/module/lpfc/version
  0:12.6.0.4

  The fix is to update nvme-cli to version 1.10.1 or later.  Groovy
  currently contains version 1.12-1 so it would seem the easiest would
  be to update nvme-cli in Focal to the version in Groovy.


  [IMPACT]

  Connectivity to NVMe Namespaces are lost after an link bounce or after
  a server reboot.

  [FIXES]

  Update nvme-cli to 1.10.1

  [TESTING]

  [REGRESSION RISK]

  No

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvme-cli/+bug/1883312/+subscriptions