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.
** Also affects: nvme-cli (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1847382
Title:
Controller ID report to console shows ctrlid as hex with no 0x in
front to denote this
Status in nvme-cli package in Ubuntu:
Fix Released
Status in nvme-cli source package in Xenial:
New
Status in nvme-cli source package in Bionic:
New
Status in nvme-cli source package in Focal:
Fix Released
Status in nvme-cli source package in Groovy:
Fix Released
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvme-cli/+bug/1847382/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
