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: 

** Bug watch added: github.com/kubernetes/kubernetes/issues #58927

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dmidecode in Ubuntu.

  dmidecode decodes /sys/class/dmi/id/product_serial incorrectly

Status in dmidecode package in Ubuntu:

Bug description:

  On VMWare 6.5 and higher (HW version 13 and higher) when decoding
  /sys/class/dmi/id/product_serial dmidecode produces an output whereby
  the first 16 characters have been reversed in comparison to

  This manifests itself by breaking provisioning in Kubernetes and could
  cause other issues down the line. Other OS such as redhat have already
  patched this in their releases.

  A demonstration of the issue can be found in this pastebin:


  VMWare Issue: https://kb.vmware.com/s/article/53609


To manage notifications about this bug go to:

Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to