The nvme-firmware-updater tool is currently uploaded separately onto individual sleds to apply NVMe firmware updates. There is no version pinning nor linkage to a host OS or omicron version. The burden is on the person preparing the update tools or performing the update to know when/where to pick up the latest binaries.
Before NVMe firmware update is implemented in the reconfigurator-driven update process, perhaps we can mitigate human errors by requiring the pinning of nvme-firmware-updater version in omicron and automatically pulling the binaries into the TUF repo (which installinator and reconfigurator will ignore) so that the latest version can be found reliably in the zip file.
This request is meant to be a stop-gap with the expectation that the eventual solution may work in an entirely different way and it won't be expensive to do this work now and reap it out in the future.
The nvme-firmware-updater tool is currently uploaded separately onto individual sleds to apply NVMe firmware updates. There is no version pinning nor linkage to a host OS or omicron version. The burden is on the person preparing the update tools or performing the update to know when/where to pick up the latest binaries.
Before NVMe firmware update is implemented in the reconfigurator-driven update process, perhaps we can mitigate human errors by requiring the pinning of nvme-firmware-updater version in omicron and automatically pulling the binaries into the TUF repo (which installinator and reconfigurator will ignore) so that the latest version can be found reliably in the zip file.
This request is meant to be a stop-gap with the expectation that the eventual solution may work in an entirely different way and it won't be expensive to do this work now and reap it out in the future.