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
I have a pipeline that works fine in 0.12.1 but fails on 0.13.0.
Actual Behavior
Pod for pipeline fails with:
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal NotTriggerScaleUp 72s cluster-autoscaler pod didn't trigger scale-up (it wouldn't fit if a new node is added): 1 node(s) didn't match pod affinity/anti-affinity, 1 node(s) didn't match pod affinity rules, 1 node(s) didn't match node selector
Warning FailedScheduling 70s (x4 over 75s) default-scheduler 0/1 nodes are available: 1 node(s) didn't match node selector.
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning FailedScheduling 11s (x3 over 15s) default-scheduler 0/1 nodes are available: 1 node(s) didn't match node selector.
Normal TriggeredScaleUp 11s cluster-autoscaler pod triggered scale-up: [{https://content.googleapis.com/compute/v1/projects/project-jklasdfk334/zones/us-west1-a/instanceGroups/gke-test-regression-test-pool-48f4fc0a-grp 0->1 (max: 1)}]
Additional Info
Kubernetes version: 1.16.8-gke.15
Tekton Pipeline version: 0.13.0
The text was updated successfully, but these errors were encountered:
1 node(s) didn't match pod affinity/anti-affinity, 1 node(s) didn't match pod affinity rules
Hi, yes, this is a known bug.
Unfortunately the name of PipelineRun + Workspace, can only be up to 34 chars long. In your case, it is 35 chars. You can use shorter PipelineRun Name or Workspace Name, or disable the affinity assistant
Expected Behavior
I have a pipeline that works fine in 0.12.1 but fails on 0.13.0.
Actual Behavior
Pod for pipeline fails with:
Steps to Reproduce the Problem
Pod fails to start with above error.
Remove 0.13.0.
Install 0.12.1
Apply above pipeline.
Autoscaling succeeds:
Additional Info
Kubernetes version: 1.16.8-gke.15
Tekton Pipeline version: 0.13.0
The text was updated successfully, but these errors were encountered: