Controller ID report to console shows ctrlid as hex with no 0x in front to denote this
Bug #1847382 reported by
William Sprouse
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| nvme-cli (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
| Xenial |
New
|
Undecided
|
Unassigned | ||
| Bionic |
New
|
Undecided
|
Unassigned | ||
| Focal |
Fix Released
|
Undecided
|
Unassigned | ||
| Groovy |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
The controller ID shown in output from id-ctrl option going to the console gives a hex value without typical hex delineation. If it has no a-f digits it looks like a decimal value as it does not start with 0x like other fields that give hex values. If JSON output is requested, then the value is given as a correct decimal value in the JSON. The console should either give a true decimal value or have the 0x prefix added.
| Changed in nvme-cli (Ubuntu Groovy): | |
| status: | New → Fix Released |
| Changed in nvme-cli (Ubuntu Focal): | |
| status: | New → Fix Released |
Revision history for this message
| Dan Streetman (ddstreet) wrote | #1 |
To post a comment you must log in.
I think it's unlikely this will be changed in Xenial or Bionic, since it's a minor issue and could potentially break any scripting in those releases that's expecting the values to be printed without the leading 0x. This is fixed in Focal and later.