So in the context of MAAS, the previously mentioned binary will read the local database from the commissioning OS image specifically. A possible workaround for this issue is to add a custom commissioning script to update the database, and name said script such that it has higher priority over machine resources (i.e prefix with a higher number than the machine-resources script).
Marking as triaged as updating the pci.ids is something MAAS could do as part of commissioning, though the workaround should suffice.
So in the context of MAAS, the previously mentioned binary will read the local database from the commissioning OS image specifically. A possible workaround for this issue is to add a custom commissioning script to update the database, and name said script such that it has higher priority over machine resources (i.e prefix with a higher number than the machine-resources script).
Marking as triaged as updating the pci.ids is something MAAS could do as part of commissioning, though the workaround should suffice.