This message was deleted.
# harvester
a
This message was deleted.
s
I figured this out! The issue was caused when following the linked instructions through the Rancher integration rather than while logged in directly through Harvester. Enabling the PCI device while logged in through the Rancher integration caused the PCIDeviceClaim to be created with a userName of "", which would never match any of the selectors for available devices. Enabling the PCIDevice while accessing harvester directly (logged in through my harvester VIP) created a PCIDevice with a userName of "admin" which I can now attach to a VM.
I think this is caused by the github oauth integration I'm using. I created an issue in the harvester github here: https://github.com/harvester/harvester/issues/4650
👍 1