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

[BUG] rancher2_cluster_v2 resources intermittently fail to provision downstream clusters with cluster_v1_id is empty error #1453

Open
Josh-Diamond opened this issue Dec 6, 2024 · 0 comments
Assignees
Labels

Comments

@Josh-Diamond
Copy link
Contributor

Josh-Diamond commented Dec 6, 2024

Rancher Server Setup

  • Rancher version: v2.9, v2.10
  • Installation option (Docker install/Helm Chart): Helm

Information about the Cluster

  • Kubernetes version: 1.30.6+rke2r1 + v1.31.2+rke2r1
  • Cluster Type (Local/Downstream): Downstream - affects RKE2 + K3s

User Information

  • What is the role of the user logged in? Admin

Provider Information

  • What is the version of the Rancher v2 Terraform Provider in use? v5.2.0 and v6.0.0

Describe the bug

Intermittently, downstream clusters fail to come up when attempting to provision downstream rancher2_cluster_v2 resource

To Reproduce

  1. Intermittently hit when provisioning rancher2_cluster_v2 resource - (hit more commonly with RKE2)

Actual Result

Setting cluster V2 legacy data: cluster_v1_id is empty

Screenshots:

Screenshot 2024-12-06 at 4 10 04 PM Screenshot 2024-12-06 at 4 10 27 PM

Expected Result

Cluster provisions successfully and doesn't error out due to a computed resource being empty

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants