vLCM Workload Domain - Create Cluster Spec does not include 'cluster_image_id' when posted to SDDC Manager.

[stevet312]

Code of Conduct

• I have read and agree to the Code of Conduct.
• Vote on this issue by adding a 👍 reaction to the original issue initial description to help the maintainers prioritize.
• Do not leave "+1" or other comments that do not add relevant information or questions.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Terraform

1.6

Terraform Provider

0.8.1

VMware Cloud Foundation

5.1

Description

When adding additional clusters to an existing Management Workload Domain, the CreateClusterSpec appears to not be passing the 'cluster_image_id' parameter as part of the JSON spec to SDDC Manager.

I can be reached out to internally at VMware on Slack or GChat to reproduce live!

Affected Resources or Data Sources

resource/vcf_cluster

Terraform Configuration

https://gist.github.com/stevet312/772728ab2fcaaab51744f431afd7e346

Debug Output

Panic Output

No response

Expected Behavior

Cluster specs should be posted to SDDC Manager, pass validation and begin creation.,

Actual Behavior

SDDC Manager fails to validate cluster creation spec due to missing vLCM image id in the POST.

Steps to Reproduce

1. Available SDDC Manager, completed VCF Bring UP
2. Host commissioning and network pool creation
3. Add UUIDs to TFVARS
4. Attempt to add one or more clusters through the module config

Environment Details

3 Racks of servers, 12 total hosts
3 Network pools (1 per rack)

VCF 5.1

Screenshots

No response

References

No response

[dimitarproynov]

Hi,

Please see #148

Issue has already been addressed and will be released with next release.

[pradeep17j]

Is this fix already available in this repo ?
If we pick this repo and do a dev override , we will be able to get this fix ?

[dimitarproynov]

Hi @pradeep17j

Yep, if you pull the current code from "main" and build the provider and setup the dev overrides then the issue should be fixed.

Regards,
_Proynov

[github-actions]

I'm going to lock this issue 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 similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.