Although this issue appears as a regression in nvme-stas 2.3-1, it looks like
it was already
affecting the usability of the nvme-stas version in testing (i.e., 2.2.2-2) -
outside of autopkgtests.
Here with nvme-stas 2.2.2-2 (after configuring a controller in
/etc/stas/stafd.conf):
Nov 17 11:14:05 usable-whippet systemd[1]: Reloaded stafd.service - STorage
Appliance Finder (STAF).
Nov 17 11:14:07 usable-whippet stafd[1268]: Error reading mandatory Host NQN
(see stasadm --help): [Errno 2] No such file or directory: '/etc/nvme/hostnqn'
Nov 17 11:14:07 usable-whippet systemd[1]: stafd.service: Main process exited,
code=exited, status=1/FAILURE
Nov 17 11:14:07 usable-whippet systemd[1]: stafd.service: Failed with result
'exit-code'.
To make the autopkgtest pass, I believe we can either:
* add a Test-Depends on nvme-cli; or
* running those commands as part of the autopkgtest:
* mkdir --parents /etc/nvme
* systemctl start stas-config@hostnqn
* systemctl start stas-config@hostid
That said, I suggest we look for a solution that also resolves the issue
outside of autopkgtests.
Would introducing a Depends on nvme-cli be a bad thing?
Kind regards,
Olivier
