Peter, Pedro, thanks for the extra detail. After reading
https://github.com/kubernetes/kubernetes/issues/58927, I agree that we
won't be able to fix this in Charmed Kubernetes directly.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dmide
We could potentially patch Charmed Kubernetes against this by not
reading /sys/class/dmi/id/product_uuid (https://github.com/charmed-
kubernetes/charm-kubernetes-
master/blob/master/reactive/kubernetes_master.py#L2244), but instead
using the workaround published by vmware at
https://kb.vmware.com/s
Hi Peter, can you elaborate on this part please: "manifests itself by
breaking provisioning in Kubernetes."
Can you describe the behavior you're seeing?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dmidecode in Ubuntu.
https://bugs.lau
3 matches
Mail list logo