Fix vSphere host UUID discovery #15
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When upgrading the vSphere hardware from 5.5 -> 6.5 no more PVCs can be created. This happens because of a bug on the SEABIOS virtual hardware that swap the endianness of the content of '/sys/class/dmi/id/pro on the new virtual hardware versions and now it differs from '/sys/class/dmi/id/product_serial'. So, the content in product_uuid is: F5132842-20D4-6171-5DB0-7B96440CCF54 While the product_serial (actually correct and understood by vSphere API) is:422813f5-d420-7161-5db0-7b96440ccf54 So, we need to use the product_serial instead of product_uuid
sombrafam
force-pushed
the
fix-vsphere-6.5-pvcs
branch
from
6f26efc
to
ab43e2c
Compare
chris-sanders
pushed a commit
that referenced
this pull request
Nov 11, 2020
When upgrading the vSphere hardware from 5.5 -> 6.5 no more PVCs can be created. This happens because of a bug on the SEABIOS virtual hardware that swap the endianness of the content of '/sys/class/dmi/id/pro on the new virtual hardware versions and now it differs from '/sys/class/dmi/id/product_serial'. So, the content in product_uuid is: F5132842-20D4-6171-5DB0-7B96440CCF54 While the product_serial (actually correct and understood by vSphere API) is:422813f5-d420-7161-5db0-7b96440ccf54 So, we need to use the product_serial instead of product_uuid
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When upgrading the vSphere hardware from 5.5 -> 6.5 no more PVCs
can be created. This happens because of a bug on the SEABIOS virtual
hardware that swap the endianness of the content of '/sys/class/dmi/id/pro
on the new virtual hardware versions and now it differs from
'/sys/class/dmi/id/product_serial'.
So, the content in product_uuid is: F5132842-20D4-6171-5DB0-7B96440CCF54
While the product_serial (actually correct and understood by vSphere API)
is:422813f5-d420-7161-5db0-7b96440ccf54
So, we need to use the product_serial instead of product_uuid
Edit to note: this is needed by charmed-kubernetes/charm-kubernetes-control-plane#102 and charmed-kubernetes/charm-kubernetes-worker#64