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

Bug #1883312 reported by Laurie Barry
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nvme-cli (Ubuntu)
Invalid
Undecided
Unassigned
Focal
Invalid
Undecided
Unassigned

Bug Description

[SUMMARY]

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

root@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@ubuntu2004:~# nvme version
nvme version 1.9

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

Jeff Lane  (bladernr)
description: updated
affects: linux (Ubuntu) → nvme-cli (Ubuntu)
Revision history for this message
Laurie Barry (laurie-barry-4) wrote :

We have a large enterprise customer planning to start their validation of NVMe FC on Ubuntu 20.04 starting in September.

Laurie

description: updated
Revision history for this message
Jeff Lane  (bladernr) wrote :

Hi Laurie,

Do you have a list of patches that would satisfy this?

Jeff Lane  (bladernr)
description: updated
summary: - NVMe FC Auto-connect is not working for Ubuntu 20.04
+ [SRU] NVMe FC Auto-connect is not working for Ubuntu 20.04
Revision history for this message
Jeff Lane  (bladernr) wrote :

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.

Revision history for this message
Laurie Barry (laurie-barry-4) wrote : Re: [Bug 1883312] Re: [SRU] NVMe FC Auto-connect is not working for Ubuntu 20.04

Thank you Jeff.

Yeah, at this point I think it sits until you naturally update your
userspace to the latest packages. We don't have the BW to prioritize doing
anything
special for this one.

*Laurie Barry*
Software Program Manager | Emulex Connectivity Division
office/soft phone: 978-719-1503 | mobile: 603-930-1771
200 Brickstone Square | Andover, MA 01810
<email address hidden> | broadcom.com

On Thu, Aug 27, 2020 at 11:15 AM Jeff Lane <email address hidden>
wrote:

> 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 subscribed to the bug
> report.
> 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@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@ubuntu2004:~# nvme version
> nvme version 1.9
>
> root@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
>

Revision history for this message
Jeff Lane  (bladernr) wrote :

If we get a customer with issues with this on Focal, we can revisit this, but now that 22.04 is out with a version of nvme-cli that is not affected, this is less likely to get sponsored otherwise.

Changed in nvme-cli (Ubuntu Focal):
status: New → Invalid
Changed in nvme-cli (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.