Skip to content
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

Creating a 'vcf_cluster' resource requires parameters which are marked as optional in the vcf-terraform document #134

Closed
2 of 4 tasks
cmsriram opened this issue Mar 1, 2024 · 2 comments
Labels
bug Bug needs-triage Needs Triage pending-review Pending Review

Comments

@cmsriram
Copy link

cmsriram commented Mar 1, 2024

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.7

Terraform Provider

VCF provider

VMware Cloud Foundation

5.1

Description

While trying to create a VCF cluster with only the mandatory fields as per the VCF terraform document: https://registry.terraform.io/providers/vmware/vcf/latest/docs/resources/cluster,
the cluster creation kept failing with a "internal server error:500".
But after following this particular blog exactly with all the fields mentioned here: https://cybernils.net/2024/01/11/using-terraform-to-commission-hosts-and-creating-clusters-in-vcf/, then the VCF cluster creation was successful.
So logging this issue so that it could be fixed in the VCF terraform provider document.

Affected Resources or Data Sources

Resource affected is "vcf_cluster"

Terraform Configuration

Attaching the word doc file which contains the main.tf and variables.tf terraform code copied.

VCF_Cluster-Creation-TerraformCode.docx

Debug Output

Dont have access to the debug output now as the lab instance is deleted.
But the exact error was " Internal server error 500" and the API was failing to start executing.

Panic Output

No response

Expected Behavior

Expected Behavior: The vcf_cluster creation should have been successful with only the required mandatory fields as mentioned in the VCF terraform doc link: https://registry.terraform.io/providers/vmware/vcf/latest/docs/resources/cluster

Actual Behavior

Actual: The vcf_cluster creation fails when we give only the required fields as per the VCF terraform doc link.

Steps to Reproduce

  1. Create the main.tf and variables.tf file strcitly following the VCF terraform doc link: https://registry.terraform.io/providers/vmware/vcf/latest/docs/resources/cluster providing only the mandatory fields and omitting all the fields mentioned as 'optional' in the above doc link.
  2. ON executing the 'terraform apply' command, the vcf_cluster creation errors out on the console with "internal server error code 500" and the API execution fails to start. There is no logging in the logs.

Environment Details

No response

Screenshots

No response

References

No response

@cmsriram cmsriram added bug Bug needs-triage Needs Triage labels Mar 1, 2024
@github-actions github-actions bot added the pending-review Pending Review label Mar 1, 2024
@cmsriram cmsriram changed the title Creating a 'vcf_cluster' resource mandatorily requires parameters which are marked as optional in the vcf-terraform document Creating a 'vcf_cluster' resource requires parameters which are marked as optional in the vcf-terraform document Mar 1, 2024
@spacegospod
Copy link
Contributor

@cmsriram I replicated the scenario using the configuration you uploaded. I only modified the entity identifiers and names.
My cluster was created successfully. I'm attaching the console output for reference.

If you manage to reproduce the issue again please share the log bundle from your SDDC manager appliance. It will help us identify the issue.

Copy link

github-actions bot commented Apr 5, 2024

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 5, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Bug needs-triage Needs Triage pending-review Pending Review
Projects
None yet
Development

No branches or pull requests

2 participants