What were you trying to do that didn't work?

The output of nvme list changes with nvme-cli 2.11 (brought in by RHEL-67144) 

What is the impact of this issue to you?

This change in output breaks nvme serviceability logic we've built around the nvme-cli tooling, where we use the JSON output to programmatically work with NVMe-enabled systems.

This has been reported upstream here: https://github.com/linux-nvme/nvme-cli/issues/2749

And the offending commit was reverted with this PR here:

https://github.com/linux-nvme/nvme-cli/pull/2762 

Revert commit is present in v2.13 and up, here:

https://github.com/linux-nvme/nvme-cli/commit/4064edc4b67b49f3966290387c1f79de2c50b6ad 

v2.13 looks like it is targetted for RHEL 9.7 (RHEL-89037), but we'd need this fix in 9.6.z

Please provide the package NVR for which the bug is seen:

nvme-cli-2.11-5

How reproducible is this bug?:

100%

Steps to reproduce

1. compare nvme list -o json before and after v2.11

Expected results

JSON output (effectively an ABI) should not radically change in between versions

Actual results

output changes, causing us to feel the regression in our automation