nvmeof connector: log messages suck in create_hostnqn
Bug #1961270 reported by
Brian Rosmaita
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| os-brick |
Triaged
|
Low
|
Unassigned | ||
Bug Description
In create_hostnqn() in os_brick/
LOG.debug('Version too old cannot check current hostnqn.')
- this needs some context ... version of what (nvme-cli)
LOG.debug('No nqn could be formed from dmi or systemd.')
- we're calling 'nvme show-hostnqn', which should give us a nqn that was previously set by dmi or systemd, but this message seems really misleading
LOG.debug('Unknown error from nvme show-hostnqn: %s', err_msg)
- this one is actually pretty good
| Changed in os-brick: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
To post a comment you must log in.
