cloud-bulldozer/e2e-benchmarking

unknown field "spec.tolerations[0].Effect" node-density lite

paigerube14 opened this issue · 4 comments

In node density lite run I am getting a lot of "spec.tolerations[0].Effect" warnings. I'm not sure where it is coming from, could be on the kube-burner side

NOTE: this is not stopping/failing the workload just lots of warnings

10-04 14:01:46.820  ###############################################
10-04 14:01:46.820  Workload: node-density
10-04 14:01:46.820  Workload template: workloads/node-pod-density/node-pod-density.yml
10-04 14:01:46.820  Metrics profile: metrics-profiles/metrics.yaml
10-04 14:01:46.820  Alerts profile: 
10-04 14:01:46.820  QPS: 20
10-04 14:01:46.820  Burst: 20
10-04 14:01:46.820  UUID: 2e802d59-797e-4e5e-8304-919534e32429
10-04 14:01:46.820  Node count: 3
10-04 14:01:46.820  Pods per node: 200
10-04 14:01:46.820  ###############################################
10-04 14:01:48.248  �[1mTue Oct  4 18:01:48 UTC 2022 Indexing enabled, using metrics from metrics-profiles/metrics.yaml�[0m
10-04 14:01:48.248  ~/ws/workspace/aige-e2e-multibranch_kube-burner/workloads/kube-burner/workloads/node-pod-density ~/ws/workspace/aige-e2e-multibranch_kube-burner/workloads/kube-burner
10-04 14:01:48.248  time="2022-10-04 18:01:48" level=info msg="🔥 Starting kube-burner (0.17.0@3115dcfee072a253b2255bdf585b4dafbc4f2dc2) with UUID 2e802d59-797e-4e5e-8304-919534e32429"
10-04 14:01:48.248  time="2022-10-04 18:01:48" level=info msg="👽 Initializing prometheus client"
10-04 14:01:48.248  time="2022-10-04 18:01:48" level=info msg="📁 Creating indexer: elastic"
10-04 14:01:48.843  time="2022-10-04 18:01:48" level=info msg="📈 Creating measurement factory"
10-04 14:01:48.843  time="2022-10-04 18:01:48" level=info msg="Registered measurement: podLatency"
10-04 14:01:48.843  time="2022-10-04 18:01:48" level=info msg="Preparing create job: node-density"
10-04 14:01:48.843  time="2022-10-04 18:01:48" level=info msg="Job node-density: 536 iterations with 1 Pod replicas"
10-04 14:01:48.843  time="2022-10-04 18:01:48" level=info msg="Pre-load: images from job node-density"
10-04 14:01:48.843  time="2022-10-04 18:01:48" level=info msg="Pre-load: Creating DaemonSet using image gcr.io/google_containers/pause:3.1 in namespace preload-kube-burner"
10-04 14:01:48.843  time="2022-10-04 18:01:48" level=info msg="Pre-load: Sleeping for 2m0s"
10-04 14:03:55.293  time="2022-10-04 18:03:48" level=info msg="Pre-load: Deleting namespace preload-kube-burner"
10-04 14:03:55.293  time="2022-10-04 18:03:48" level=info msg="Deleting namespaces with label kube-burner-preload=true"
10-04 14:03:55.293  time="2022-10-04 18:03:48" level=info msg="Waiting for namespaces to be definitely deleted"
10-04 14:04:03.417  time="2022-10-04 18:04:01" level=info msg="Triggering job: node-density"
10-04 14:04:03.417  time="2022-10-04 18:04:01" level=info msg="Creating Pod latency watcher for node-density"
10-04 14:04:03.417  time="2022-10-04 18:04:02" level=info msg="QPS: 20"
10-04 14:04:03.417  time="2022-10-04 18:04:02" level=info msg="Burst: 20"
10-04 14:04:03.417  time="2022-10-04 18:04:02" level=info msg="Running job node-density"
10-04 14:04:03.417  W1004 18:04:02.317410    9263 warnings.go:70] unknown field "spec.tolerations[0].Effect"
10-04 14:04:03.417  W1004 18:04:02.399581    9263 warnings.go:70] unknown field "spec.tolerations[0].Effect"
10-04 14:04:03.417  W1004 18:04:02.452348    9263 warnings.go:70] unknown field "spec.tolerations[0].Effect"
.....

@afcollins I see you added tolerations section to the pod.yaml file in PR any ideas on this?

Hmm, yes it does look like "Effect" should be "effect". Does that remove the warning?

@afcollins yes sorry somehow I completely missed that Effect was in that yaml file. Opened pr with fix if you can review! Thanks

As we discussed, maybe the warning shows up for you but not for me is some change between the 4.12 ec.3 (where I didn't see it) and the latest nightly (where you see it).
Thank you for fixing