-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Regression in 0.55.0: --spot is only valid with managed nodegroups
#3929
Comments
I can reproduce this with |
The EKS workflows suddenly started failing with: Error: couldn't create node group filter from command line options: --spot is only valid with managed nodegroups (--managed) On Jul 2 at around 15 CEST (https://github.com/cilium/cilium-cli/actions/runs/992727965). The release of eksctl 0.55.0 coincides with this time frame. As we pin the EKS workflows to the latest eksctl release, it is likely that this caused the failures. Pin the eksctl to 0.54.0 for now which doesn't seem to exhibit this behavior. Ref: eksctl-io/eksctl#3929 Signed-off-by: Tobias Klauser <tobias@cilium.io>
The EKS workflows suddenly started failing with: Error: couldn't create node group filter from command line options: --spot is only valid with managed nodegroups (--managed) On Jul 2 at around 15 CEST (https://github.com/cilium/cilium-cli/actions/runs/992727965). The release of eksctl 0.55.0 coincides with this time frame. As we pin the EKS workflows to the latest eksctl release, it is likely that this caused the failures. Pin the eksctl to 0.54.0 for now which doesn't seem to exhibit this behavior. Ref: eksctl-io/eksctl#3929 Signed-off-by: Tobias Klauser <tobias@cilium.io>
Thanks for reporting @nbusseneau, after a quick bisect I found the change came with #3887. Fix will be along shortly 👍 |
The EKS workflows suddenly started failing with: Error: couldn't create node group filter from command line options: --spot is only valid with managed nodegroups (--managed) On Jul 2 at around 15 CEST (https://github.com/cilium/cilium-cli/actions/runs/992727965). The release of eksctl 0.55.0 coincides with this time frame. As we pin the EKS workflows to the latest eksctl release, it is likely that this caused the failures. Pin the eksctl to 0.54.0 for now which doesn't seem to exhibit this behavior. Ref: eksctl-io/eksctl#3929 Signed-off-by: Tobias Klauser <tobias@cilium.io>
Can confirm I don't reproduce the issue with 0.54.0, but do with 0.55.0. Editing title. EDIT: ah sorry, GitHub did not refresh the comment list so I had missed the previous comment 🙈 Thanks! |
--spot is only valid with managed nodegroups
--spot is only valid with managed nodegroups
Closed by #3930. The fix is out in https://github.com/weaveworks/eksctl/releases/tag/0.56.0-rc.1 |
Commit 59785a9 (".github/workflows: use eksctl 0.54.0") pinnned eksctl to v0.54.0 to work around an issue in eksctl v0.55.0. That issue was fixed upstream and v0.56.0 released, so revert back to using the latest eksctl version. Ref: eksctl-io/eksctl#3929 Signed-off-by: Tobias Klauser <tobias@cilium.io>
Commit 59785a9 (".github/workflows: use eksctl 0.54.0") pinnned eksctl to v0.54.0 to work around an issue in eksctl v0.55.0. That issue was fixed upstream and v0.56.0 released, so revert back to using the latest eksctl version. Ref: eksctl-io/eksctl#3929 Signed-off-by: Tobias Klauser <tobias@cilium.io>
The EKS workflows suddenly started failing with: Error: couldn't create node group filter from command line options: --spot is only valid with managed nodegroups (--managed) On Jul 2 at around 15 CEST (https://github.com/cilium/cilium-cli/actions/runs/992727965). The release of eksctl 0.55.0 coincides with this time frame. As we pin the EKS workflows to the latest eksctl release, it is likely that this caused the failures. Pin the eksctl to 0.54.0 for now which doesn't seem to exhibit this behavior. Ref: eksctl-io/eksctl#3929 Signed-off-by: Tobias Klauser <tobias@cilium.io>
Commit 59785a9 (".github/workflows: use eksctl 0.54.0") pinnned eksctl to v0.54.0 to work around an issue in eksctl v0.55.0. That issue was fixed upstream and v0.56.0 released, so revert back to using the latest eksctl version. Ref: eksctl-io/eksctl#3929 Signed-off-by: Tobias Klauser <tobias@cilium.io>
The EKS workflows suddenly started failing with: Error: couldn't create node group filter from command line options: --spot is only valid with managed nodegroups (--managed) On Jul 2 at around 15 CEST (https://github.com/cilium/cilium-cli/actions/runs/992727965). The release of eksctl 0.55.0 coincides with this time frame. As we pin the EKS workflows to the latest eksctl release, it is likely that this caused the failures. Pin the eksctl to 0.54.0 for now which doesn't seem to exhibit this behavior. Ref: eksctl-io/eksctl#3929 Signed-off-by: Tobias Klauser <tobias@cilium.io>
Commit 59785a9f9c7c (".github/workflows: use eksctl 0.54.0") pinnned eksctl to v0.54.0 to work around an issue in eksctl v0.55.0. That issue was fixed upstream and v0.56.0 released, so revert back to using the latest eksctl version. Ref: eksctl-io/eksctl#3929 Signed-off-by: Tobias Klauser <tobias@cilium.io>
Hi,
We use
eksctl
oncilium/cilium-cli
for deploying an EKS cluster and running tests on it via GitHub Actions (link).First, we download the
latest
release:Then, we deploy a cluster without a nodegroup:
And finally, we setup a spot managed nodegroup:
Looking at the list of scheduled runs (running every 6 hours) we can see that the last working run was on Jul 2 around 9 CEST, with the next run around 15 CEST failing at the managed spot nodegroup creation step, along with all subsequent runs:
Nothing changed in how we setup EKS clusters between the last working and first failing runs mentioned above.
0.55.0 was released on Jul 2 at 14:27 CEST. I strongly suspect a regression in 0.55.0 introducing the issue. Looking at the list of changes, I feel like #3895 might be related?
I don't have access to my work machine at present but will try the following reproduction steps on Monday:
eksctl
0.54.0 and try to setup a spot managed nodegroup: I expect it will work.eksctl
0.55.0 and try to setup a spot managed nodegroup: I expect it will not work.The text was updated successfully, but these errors were encountered: