-
Notifications
You must be signed in to change notification settings - Fork 36
Labels
kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.
Description
What happened?
When do e2e test, sometimes node can be unready, then we will restart a new node. From log, I can see that it won't apply labels to the new node.
2026-01-29T04:54:44.023Z INFO setup/k8s_clusters.go:783 WARN: ✅ Successfully replaced not ready node: k3d-shared-e2e-test-cluster-agent-1
2026-01-29T04:54:55.353Z INFO tests/topology_test.go:47 Get all pods once for verification
2026-01-29T04:54:55.359Z INFO tests/topology_test.go:390 3. Verify all 4 pods in same zone (PCS zone constraint)
topology_test.go:392: Failed to verify pods in same zone: node k3d-shared-e2e-test-cluster-agent-1 does not have topology label kubernetes.io/zone
What did you expect to happen?
Replaced node should also have the label with the previous one
Environment
- Kubernetes version
- Grove version
- Scheduler details
- Cloud provider or hardware configuration
- Tools that you are using Grove together with
- Anything else that is relevant
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.