-
Notifications
You must be signed in to change notification settings - Fork 455
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: issue gh-2005 #2009
fix: issue gh-2005 #2009
Conversation
Customizing VMs ( customize{} block in the spec) with a hardware version less than 10 fails due to formatting error of the version string passed in the API. Changed the formatting code to format the version to 2 digit integer, left padded with 0 when it's less than 10. That way version 9 becomes vmx-09 instead of vmx-9 and version 10 remains vmx-10.
Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement Learn more about why HashiCorp requires a CLA and what the CLA includes Have you signed the CLA already but the status is still pending? Recheck it. |
I will run the VM resource tests on your branch, great job this has been a bug forever. UPDATE: no regressions for existing VM tests |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@nklinkachevAtVMware Can you ensure that the commit is signed and that you have signed the CLA?
replacing with #2011 due some unfortunate timeline limitations. |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Customizing VMs ( customize{} block in the spec) with a hardware version less than 10 fails due to formatting error of the version string passed in the API. Changed the formatting code to format the version to 2 digit integer, left padded with 0 when it's less than 10. That way version 9 becomes vmx-09 instead of vmx-9 and version 10 remains vmx-10.
Description
Fix:
r/vsphere_virtual_machine
Customization fails with when the hardware version of the machine is less than 10."Error: cannot find OS family for guest ID "": ServerFaultCode: A specified parameter was not correct: key"
Acceptance tests
Output from acceptance testing:
Release Note
Release note for CHANGELOG:
References