The commit in curtin (54db5d071bdc56fcba03ac30233533f3e98999e2) says:
[...]
The presence of a "nvme_controller" object in the config will trigger
installation of nvme-cli and nvme-stas during curthooks, even if the
controller specifies transport = "pcie" or if the controller is actually
unused for the installation. For now, we will recommend not having
any "nvme_controller" objects in the config if we don't install to a
drive connected using NVMe over TCP.
[...]
So I guess something has gone wrong that there is an nvme_controller object in the config? We should definitely not be installing nvme-stas as part of a desktop install.
The commit in curtin (54db5d071bdc56 fcba03ac3023353 3f3e98999e2) says:
[...]
The presence of a "nvme_controller" object in the config will trigger
installation of nvme-cli and nvme-stas during curthooks, even if the
controller specifies transport = "pcie" or if the controller is actually
unused for the installation. For now, we will recommend not having
any "nvme_controller" objects in the config if we don't install to a
drive connected using NVMe over TCP.
[...]
So I guess something has gone wrong that there is an nvme_controller object in the config? We should definitely not be installing nvme-stas as part of a desktop install.