You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Hosted Rancher customer noticed a problem when trying to update the node groups on one of their downstream EKS clusters. We see in the upstream Rancher cluster that the eks-config-operator pod is crashing due to a go panic:
Is that failing due to it not being able to delete a Launch Template?
We checked the Launch Template for the cluster that's referenced in the ekscc object for the cluster. The LT version it lists exists in AWS.
There were a couple of old ekscc objects that were previously deleted but hanging on finalizers. We cleared those out and it didn't help.
His EKS cluster also had a node group he tried to create as a test that had a space in it. We removed the space from the name and that still didn't help.
Please let us know what else we can look into.
The text was updated successfully, but these errors were encountered:
SURE-9285
Issue description:
The Hosted Rancher customer noticed a problem when trying to update the node groups on one of their downstream EKS clusters. We see in the upstream Rancher cluster that the eks-config-operator pod is crashing due to a go panic:
Business impact:
Customer can't access their EKS cluster in Rancher
Troubleshooting steps:
It seems like the problem is coming from here: https://github.com/rancher/eks-operator/blob/release-v2.9/pkg/eks/create.go#L326
Is that failing due to it not being able to delete a Launch Template?
We checked the Launch Template for the cluster that's referenced in the ekscc object for the cluster. The LT version it lists exists in AWS.
There were a couple of old ekscc objects that were previously deleted but hanging on finalizers. We cleared those out and it didn't help.
His EKS cluster also had a node group he tried to create as a test that had a space in it. We removed the space from the name and that still didn't help.
Please let us know what else we can look into.
The text was updated successfully, but these errors were encountered: