https://rancher.com/ logo
#amazon
Title
# amazon
c

curved-lifeguard-39360

09/15/2022, 8:18 PM
I have a downstream cluster that I created using rancher console. I recently deleted a node group, but I did it from the AWS Console. Don’t know if it matters, but I also added a node group to that cluster using eksctl instead of rancher. Now that cluster is showing this error: _*InvalidParameterException: You cannot specify an AMI Type other than CUSTOM, when specifying an image id in your launch template. { RespMetadata: { StatusCode: 400, RequestID: “c5a5bfb7-70ae-476f-8548-94858b1aa765” }, ClusterName: “pano-prod”, Message_: “You cannot specify an AMI Type other than CUSTOM, when specifying an image id in your launch template.“, NodegroupName: “pool-pvt” }*_
pool-pvt is the node group I removed
I try to remove it, and I get this: Validation failed in API: nodegroup [pool-pvt-new] version cannot be empty string
the node group pool-pvt-new does not actually show up in the rancher console at all. What can I do?
BTW running rancher 2.6.1 and eks k8s 1.20
What would happen if I deleted it from rancher and then imported it again?
I just found out that rancher is trying to recreate the pool-pvt node group and is sending api calls to cloudformation every 7 seconds. How can I stop it?
Please help! Anybody? At this point it looks like I am going to have to rebuild the cluster…
c

clever-analyst-23771

09/19/2022, 1:10 PM
I haven't run Rancher with AWS, let's see if someone else here has and might have some insights on this.
c

curved-lifeguard-39360

09/19/2022, 1:47 PM
I ended up having to rebuild the cluster. This time I built it with eskctl and then imported it into rancher. I really think thats a better strategy anyway.
5 Views