nvme-ebs-links sometimes "comes up short"

I've now seen a couple times where the nvme-ebs-links mdev script does a nvme id-ctrl ... to read the EBS volume name, but only gets part of the EBS volume name (i.e. 'x' instead of 'xvdb') -- almost as if whatever manages that value hadn't quite written it all there yet.

Seems to be most prevalent after partitioning a volume...