What we're seeing is a failed provisioning error when adding volumes, we hit this closed issue:
https://github.com/kubernetes/kubernetes/issues/58927 Kubernetes behaviour changed to fix this issue by switching to the */product_serial file as the source of truth. But for our case the product_serial was incorrect, and the product_uuid was the source of truth, this meant when Kubernetes went to get the node it failed to find the VM: https://github.com/kubernetes/kubernetes/blob/103e926604de6f79161b78af3e792d0ed282bc06/staging/src/k8s.io/legacy-cloud-providers/vsphere/vsphere_util.go#L656 ** Bug watch added: github.com/kubernetes/kubernetes/issues #58927 https://github.com/kubernetes/kubernetes/issues/58927 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851676 Title: dmidecode decodes /sys/class/dmi/id/product_serial incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1851676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
