I've inherited a CentOS 7.9 EFI with a kickstart and been tasked with updating it for security controls and newer PC hardware. Specifically our new laptops are coming in with NVMe drives and no SSDs to which our kickstart fails because it was hard coded to install on sda. I've updated it and in ESXi when I add a NVMe controller and hdd to that cntr my kickstart will see the nvme labeling and install to it. On our physical hdw though it won't. As a test I commented out the ks.cfg in the efi grub.cfg and verified that on a stock install with the same media it does see and install to the NVMe drive. I poured over the anaconda-ks.cfg that the manual install generated and I'm going crazy because there is nothing in that file that I don't already have or missing either.

Please tell me there's something simple that I'm just blind and overlooking. There's got to be someone that's run into this before. I've already spent a few hours on the 'overflows and a couple other blog hits but nothing seems to match my use case.