Skip to content

Bug 1896558: Balance nodes in scheduling e2e#547

Merged
openshift-merge-robot merged 1 commit intoopenshift:masterfrom
damemi:openshift-balance-nodes-scheduling-ubernetes-lite
Feb 7, 2021
Merged

Bug 1896558: Balance nodes in scheduling e2e#547
openshift-merge-robot merged 1 commit intoopenshift:masterfrom
damemi:openshift-balance-nodes-scheduling-ubernetes-lite

Conversation

@damemi
Copy link

@damemi damemi commented Feb 2, 2021

/kind flake

This pulls changes from kubernetes#98699 to attempt to fix these flaking tests

@openshift-ci-robot openshift-ci-robot added kind/flake Categorizes issue or PR as related to a flaky test. backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. bugzilla/severity-medium Referenced Bugzilla bug's severity is medium for the branch this PR is targeting. labels Feb 2, 2021
@openshift-ci-robot
Copy link

@damemi: This pull request references Bugzilla bug 1896558, which is valid. The bug has been updated to refer to the pull request using the external bug tracker.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.7.0) matches configured target release for branch (4.7.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
Details

In response to this:

Bug 1896558: Balance nodes in scheduling e2e

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-ci-robot openshift-ci-robot added the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label Feb 2, 2021
@openshift-ci-robot
Copy link

@damemi: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

@damemi
Copy link
Author

damemi commented Feb 2, 2021

Might be worth adding in some actual failures so we can get usage logs to confirm this would help the cause

@openshift-ci-robot
Copy link

@damemi: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

@damemi
Copy link
Author

damemi commented Feb 2, 2021

/retest

@damemi
Copy link
Author

damemi commented Feb 3, 2021

I added intentional fails into these tests to try to get some log output from them, but all of CI is green. I think that means we need to merge openshift/origin#25848 to unskip the tests in CI @deads2k can you approve that PR?

@damemi
Copy link
Author

damemi commented Feb 3, 2021

I ran this on a stock aws cluster and was able to see the following output for the test.

Relevant snippets (showing unbalanced cpuFractions of 0.57, 0.42, 0.35. memFractions .58, .55, .53):

Node: ip-10-0-179-181.us-west-1.compute.internal, totalRequestedCPUResource: 855, cpuAllocatableMil: 1500, cpuFraction: 0.57
INFO: Node: ip-10-0-179-181.us-west-1.compute.internal, totalRequestedMemResource: 4020240384, memAllocatableVal: 6858436608, memFraction: 0.5861744612920391
...
 INFO: Node: ip-10-0-187-51.us-west-1.compute.internal, totalRequestedCPUResource: 632, cpuAllocatableMil: 1500, cpuFraction: 0.42133333333333334
Feb  3 10:54:31.441: INFO: Node: ip-10-0-187-51.us-west-1.compute.internal, totalRequestedMemResource: 3809476608, memAllocatableVal: 6858665984, memFraction: 0.5554252994513518
...
INFO: Node: ip-10-0-200-155.us-west-1.compute.internal, totalRequestedCPUResource: 538, cpuAllocatableMil: 1500, cpuFraction: 0.3586666666666667
Feb  3 10:54:31.829: INFO: Node: ip-10-0-200-155.us-west-1.compute.internal, totalRequestedMemResource: 3693084672, memAllocatableVal: 6858452992, memFraction: 0.5384719668280552

So I'm removing the intentional failures and this is will be ready for review (pending upstream lgtm)

Full usage output:

Feb  3 10:54:30.667: INFO: ComputeCPUMemFraction for node: ip-10-0-179-181.us-west-1.compute.internal
Feb  3 10:54:31.061: INFO: Pod for on the node: aws-ebs-csi-driver-node-t7f5s, Cpu: 30, Mem: 157286400
Feb  3 10:54:31.061: INFO: Pod for on the node: tuned-xzssv, Cpu: 10, Mem: 52428800
Feb  3 10:54:31.061: INFO: Pod for on the node: dns-default-xjgkb, Cpu: 65, Mem: 137363456
Feb  3 10:54:31.061: INFO: Pod for on the node: image-registry-7cffc74f65-cfr29, Cpu: 100, Mem: 268435456
Feb  3 10:54:31.061: INFO: Pod for on the node: image-registry-7cffc74f65-jx6nv, Cpu: 100, Mem: 268435456
Feb  3 10:54:31.061: INFO: Pod for on the node: node-ca-4lf44, Cpu: 10, Mem: 10485760
Feb  3 10:54:31.061: INFO: Pod for on the node: ingress-canary-9bcfc, Cpu: 10, Mem: 20971520
Feb  3 10:54:31.062: INFO: Pod for on the node: router-default-694589fd47-2d2mp, Cpu: 100, Mem: 268435456
Feb  3 10:54:31.062: INFO: Pod for on the node: migrator-5c8598ddf7-fxxcl, Cpu: 10, Mem: 209715200
Feb  3 10:54:31.062: INFO: Pod for on the node: machine-config-daemon-crw5g, Cpu: 40, Mem: 104857600
Feb  3 10:54:31.062: INFO: Pod for on the node: certified-operators-g68pq, Cpu: 10, Mem: 52428800
Feb  3 10:54:31.062: INFO: Pod for on the node: certified-operators-gp8b5, Cpu: 10, Mem: 52428800
Feb  3 10:54:31.062: INFO: Pod for on the node: community-operators-csrg9, Cpu: 10, Mem: 52428800
Feb  3 10:54:31.062: INFO: Pod for on the node: community-operators-rvw7b, Cpu: 10, Mem: 52428800
Feb  3 10:54:31.062: INFO: Pod for on the node: redhat-marketplace-8k76g, Cpu: 10, Mem: 52428800
Feb  3 10:54:31.062: INFO: Pod for on the node: redhat-marketplace-f22lg, Cpu: 10, Mem: 52428800
Feb  3 10:54:31.062: INFO: Pod for on the node: redhat-operators-4mp9d, Cpu: 10, Mem: 52428800
Feb  3 10:54:31.062: INFO: Pod for on the node: redhat-operators-lf75w, Cpu: 10, Mem: 52428800
Feb  3 10:54:31.062: INFO: Pod for on the node: alertmanager-main-2, Cpu: 8, Mem: 283115520
Feb  3 10:54:31.062: INFO: Pod for on the node: kube-state-metrics-6df878b7c-s47m8, Cpu: 4, Mem: 125829120
Feb  3 10:54:31.062: INFO: Pod for on the node: node-exporter-bz9qd, Cpu: 9, Mem: 220200960
Feb  3 10:54:31.062: INFO: Pod for on the node: openshift-state-metrics-5dbc4f96cc-xr5ng, Cpu: 3, Mem: 199229440
Feb  3 10:54:31.062: INFO: Pod for on the node: prometheus-adapter-fb6c7c7f4-78hdh, Cpu: 1, Mem: 26214400
Feb  3 10:54:31.062: INFO: Pod for on the node: multus-rpgrk, Cpu: 10, Mem: 157286400
Feb  3 10:54:31.062: INFO: Pod for on the node: network-metrics-daemon-26mpg, Cpu: 20, Mem: 125829120
Feb  3 10:54:31.062: INFO: Pod for on the node: network-check-source-87c46d7f8-9lkvg, Cpu: 10, Mem: 52428800
Feb  3 10:54:31.062: INFO: Pod for on the node: network-check-target-h7xtk, Cpu: 10, Mem: 157286400
Feb  3 10:54:31.062: INFO: Pod for on the node: ovs-tmntr, Cpu: 15, Mem: 419430400
Feb  3 10:54:31.062: INFO: Pod for on the node: sdn-xtx6p, Cpu: 110, Mem: 230686720
Feb  3 10:54:31.062: INFO: Node: ip-10-0-179-181.us-west-1.compute.internal, totalRequestedCPUResource: 855, cpuAllocatableMil: 1500, cpuFraction: 0.57
Feb  3 10:54:31.062: INFO: Node: ip-10-0-179-181.us-west-1.compute.internal, totalRequestedMemResource: 4020240384, memAllocatableVal: 6858436608, memFraction: 0.5861744612920391
Feb  3 10:54:31.062: INFO: ComputeCPUMemFraction for node: ip-10-0-187-51.us-west-1.compute.internal
Feb  3 10:54:31.441: INFO: Pod for on the node: aws-ebs-csi-driver-node-847r8, Cpu: 30, Mem: 157286400
Feb  3 10:54:31.441: INFO: Pod for on the node: tuned-8z5gc, Cpu: 10, Mem: 52428800
Feb  3 10:54:31.441: INFO: Pod for on the node: dns-default-6lzhr, Cpu: 65, Mem: 137363456
Feb  3 10:54:31.441: INFO: Pod for on the node: node-ca-4vxkn, Cpu: 10, Mem: 10485760
Feb  3 10:54:31.441: INFO: Pod for on the node: ingress-canary-pq4sb, Cpu: 10, Mem: 20971520
Feb  3 10:54:31.441: INFO: Pod for on the node: router-default-694589fd47-ncp85, Cpu: 100, Mem: 268435456
Feb  3 10:54:31.441: INFO: Pod for on the node: machine-config-daemon-dtk49, Cpu: 40, Mem: 104857600
Feb  3 10:54:31.441: INFO: Pod for on the node: alertmanager-main-1, Cpu: 8, Mem: 283115520
Feb  3 10:54:31.441: INFO: Pod for on the node: node-exporter-g8b5z, Cpu: 9, Mem: 220200960
Feb  3 10:54:31.441: INFO: Pod for on the node: prometheus-k8s-1, Cpu: 76, Mem: 1262485504
Feb  3 10:54:31.441: INFO: Pod for on the node: thanos-querier-645fd8f7df-tzs72, Cpu: 9, Mem: 96468992
Feb  3 10:54:31.441: INFO: Pod for on the node: multus-wm6kq, Cpu: 10, Mem: 157286400
Feb  3 10:54:31.441: INFO: Pod for on the node: network-metrics-daemon-82r26, Cpu: 20, Mem: 125829120
Feb  3 10:54:31.441: INFO: Pod for on the node: network-check-target-6hxm2, Cpu: 10, Mem: 157286400
Feb  3 10:54:31.441: INFO: Pod for on the node: ovs-l84dj, Cpu: 15, Mem: 419430400
Feb  3 10:54:31.441: INFO: Pod for on the node: sdn-gm9jz, Cpu: 110, Mem: 230686720
Feb  3 10:54:31.441: INFO: Node: ip-10-0-187-51.us-west-1.compute.internal, totalRequestedCPUResource: 632, cpuAllocatableMil: 1500, cpuFraction: 0.42133333333333334
Feb  3 10:54:31.441: INFO: Node: ip-10-0-187-51.us-west-1.compute.internal, totalRequestedMemResource: 3809476608, memAllocatableVal: 6858665984, memFraction: 0.5554252994513518
Feb  3 10:54:31.441: INFO: ComputeCPUMemFraction for node: ip-10-0-200-155.us-west-1.compute.internal
Feb  3 10:54:31.829: INFO: Pod for on the node: aws-ebs-csi-driver-node-hvtms, Cpu: 30, Mem: 157286400
Feb  3 10:54:31.829: INFO: Pod for on the node: tuned-vw9d7, Cpu: 10, Mem: 52428800
Feb  3 10:54:31.829: INFO: Pod for on the node: dns-default-gj8vb, Cpu: 65, Mem: 137363456
Feb  3 10:54:31.829: INFO: Pod for on the node: node-ca-29qp8, Cpu: 10, Mem: 10485760
Feb  3 10:54:31.829: INFO: Pod for on the node: ingress-canary-j7rnn, Cpu: 10, Mem: 20971520
Feb  3 10:54:31.829: INFO: Pod for on the node: machine-config-daemon-pfch2, Cpu: 40, Mem: 104857600
Feb  3 10:54:31.829: INFO: Pod for on the node: alertmanager-main-0, Cpu: 8, Mem: 283115520
Feb  3 10:54:31.829: INFO: Pod for on the node: grafana-7864bffbf8-kjzz8, Cpu: 5, Mem: 125829120
Feb  3 10:54:31.829: INFO: Pod for on the node: node-exporter-hjvzw, Cpu: 9, Mem: 220200960
Feb  3 10:54:31.829: INFO: Pod for on the node: prometheus-adapter-fb6c7c7f4-xb5j9, Cpu: 1, Mem: 26214400
Feb  3 10:54:31.829: INFO: Pod for on the node: prometheus-k8s-0, Cpu: 76, Mem: 1262485504
Feb  3 10:54:31.829: INFO: Pod for on the node: thanos-querier-645fd8f7df-7n82z, Cpu: 9, Mem: 96468992
Feb  3 10:54:31.829: INFO: Pod for on the node: multus-5fz48, Cpu: 10, Mem: 157286400
Feb  3 10:54:31.829: INFO: Pod for on the node: network-metrics-daemon-2srhr, Cpu: 20, Mem: 125829120
Feb  3 10:54:31.829: INFO: Pod for on the node: network-check-target-fl4xm, Cpu: 10, Mem: 157286400
Feb  3 10:54:31.829: INFO: Pod for on the node: ovs-zp748, Cpu: 15, Mem: 419430400
Feb  3 10:54:31.829: INFO: Pod for on the node: sdn-66dlh, Cpu: 110, Mem: 230686720
Feb  3 10:54:31.829: INFO: Node: ip-10-0-200-155.us-west-1.compute.internal, totalRequestedCPUResource: 538, cpuAllocatableMil: 1500, cpuFraction: 0.3586666666666667
Feb  3 10:54:31.829: INFO: Node: ip-10-0-200-155.us-west-1.compute.internal, totalRequestedMemResource: 3693084672, memAllocatableVal: 6858452992, memFraction: 0.5384719668280552
Feb  3 10:54:31.946: INFO: Waiting for running...
Feb  3 10:54:47.164: INFO: Waiting for running...
Feb  3 10:54:57.380: INFO: Waiting for running...
STEP: Compute Cpu, Mem Fraction after create balanced pods.
Feb  3 10:55:07.487: INFO: ComputeCPUMemFraction for node: ip-10-0-179-181.us-west-1.compute.internal
Feb  3 10:55:07.966: INFO: Pod for on the node: 822b708a-3e1c-4a33-b354-3667a4353013-0, Cpu: 45, Mem: 94821580
Feb  3 10:55:07.966: INFO: Pod for on the node: aws-ebs-csi-driver-node-t7f5s, Cpu: 30, Mem: 157286400
Feb  3 10:55:07.966: INFO: Pod for on the node: tuned-xzssv, Cpu: 10, Mem: 52428800
Feb  3 10:55:07.966: INFO: Pod for on the node: dns-default-xjgkb, Cpu: 65, Mem: 137363456
Feb  3 10:55:07.966: INFO: Pod for on the node: image-registry-7cffc74f65-cfr29, Cpu: 100, Mem: 268435456
Feb  3 10:55:07.966: INFO: Pod for on the node: image-registry-7cffc74f65-jx6nv, Cpu: 100, Mem: 268435456
Feb  3 10:55:07.966: INFO: Pod for on the node: node-ca-4lf44, Cpu: 10, Mem: 10485760
Feb  3 10:55:07.966: INFO: Pod for on the node: ingress-canary-9bcfc, Cpu: 10, Mem: 20971520
Feb  3 10:55:07.966: INFO: Pod for on the node: router-default-694589fd47-2d2mp, Cpu: 100, Mem: 268435456
Feb  3 10:55:07.966: INFO: Pod for on the node: migrator-5c8598ddf7-fxxcl, Cpu: 10, Mem: 209715200
Feb  3 10:55:07.966: INFO: Pod for on the node: machine-config-daemon-crw5g, Cpu: 40, Mem: 104857600
Feb  3 10:55:07.966: INFO: Pod for on the node: certified-operators-g68pq, Cpu: 10, Mem: 52428800
Feb  3 10:55:07.966: INFO: Pod for on the node: certified-operators-gp8b5, Cpu: 10, Mem: 52428800
Feb  3 10:55:07.966: INFO: Pod for on the node: community-operators-csrg9, Cpu: 10, Mem: 52428800
Feb  3 10:55:07.967: INFO: Pod for on the node: community-operators-rvw7b, Cpu: 10, Mem: 52428800
Feb  3 10:55:07.967: INFO: Pod for on the node: redhat-marketplace-8k76g, Cpu: 10, Mem: 52428800
Feb  3 10:55:07.967: INFO: Pod for on the node: redhat-marketplace-f22lg, Cpu: 10, Mem: 52428800
Feb  3 10:55:07.967: INFO: Pod for on the node: redhat-operators-4mp9d, Cpu: 10, Mem: 52428800
Feb  3 10:55:07.967: INFO: Pod for on the node: redhat-operators-lf75w, Cpu: 10, Mem: 52428800
Feb  3 10:55:07.967: INFO: Pod for on the node: alertmanager-main-2, Cpu: 8, Mem: 283115520
Feb  3 10:55:07.967: INFO: Pod for on the node: kube-state-metrics-6df878b7c-s47m8, Cpu: 4, Mem: 125829120
Feb  3 10:55:07.967: INFO: Pod for on the node: node-exporter-bz9qd, Cpu: 9, Mem: 220200960
Feb  3 10:55:07.967: INFO: Pod for on the node: openshift-state-metrics-5dbc4f96cc-xr5ng, Cpu: 3, Mem: 199229440
Feb  3 10:55:07.967: INFO: Pod for on the node: prometheus-adapter-fb6c7c7f4-78hdh, Cpu: 1, Mem: 26214400
Feb  3 10:55:07.967: INFO: Pod for on the node: multus-rpgrk, Cpu: 10, Mem: 157286400
Feb  3 10:55:07.967: INFO: Pod for on the node: network-metrics-daemon-26mpg, Cpu: 20, Mem: 125829120
Feb  3 10:55:07.967: INFO: Pod for on the node: network-check-source-87c46d7f8-9lkvg, Cpu: 10, Mem: 52428800
Feb  3 10:55:07.967: INFO: Pod for on the node: network-check-target-h7xtk, Cpu: 10, Mem: 157286400
Feb  3 10:55:07.967: INFO: Pod for on the node: ovs-tmntr, Cpu: 15, Mem: 419430400
Feb  3 10:55:07.967: INFO: Pod for on the node: sdn-xtx6p, Cpu: 110, Mem: 230686720
Feb  3 10:55:07.967: INFO: Node: ip-10-0-179-181.us-west-1.compute.internal, totalRequestedCPUResource: 900, cpuAllocatableMil: 1500, cpuFraction: 0.6
Feb  3 10:55:07.967: INFO: Node: ip-10-0-179-181.us-west-1.compute.internal, totalRequestedMemResource: 4115061964, memAllocatableVal: 6858436608, memFraction: 0.5999999998833554
STEP: Compute Cpu, Mem Fraction after create balanced pods.
Feb  3 10:55:07.967: INFO: ComputeCPUMemFraction for node: ip-10-0-187-51.us-west-1.compute.internal
Feb  3 10:55:08.337: INFO: Pod for on the node: 4395b6c6-9c39-4346-ac7e-ddf601913d6f-0, Cpu: 267, Mem: 305722982
Feb  3 10:55:08.337: INFO: Pod for on the node: aws-ebs-csi-driver-node-847r8, Cpu: 30, Mem: 157286400
Feb  3 10:55:08.337: INFO: Pod for on the node: tuned-8z5gc, Cpu: 10, Mem: 52428800
Feb  3 10:55:08.337: INFO: Pod for on the node: dns-default-6lzhr, Cpu: 65, Mem: 137363456
Feb  3 10:55:08.337: INFO: Pod for on the node: node-ca-4vxkn, Cpu: 10, Mem: 10485760
Feb  3 10:55:08.337: INFO: Pod for on the node: ingress-canary-pq4sb, Cpu: 10, Mem: 20971520
Feb  3 10:55:08.337: INFO: Pod for on the node: router-default-694589fd47-ncp85, Cpu: 100, Mem: 268435456
Feb  3 10:55:08.337: INFO: Pod for on the node: machine-config-daemon-dtk49, Cpu: 40, Mem: 104857600
Feb  3 10:55:08.337: INFO: Pod for on the node: alertmanager-main-1, Cpu: 8, Mem: 283115520
Feb  3 10:55:08.337: INFO: Pod for on the node: node-exporter-g8b5z, Cpu: 9, Mem: 220200960
Feb  3 10:55:08.337: INFO: Pod for on the node: prometheus-k8s-1, Cpu: 76, Mem: 1262485504
Feb  3 10:55:08.337: INFO: Pod for on the node: thanos-querier-645fd8f7df-tzs72, Cpu: 9, Mem: 96468992
Feb  3 10:55:08.337: INFO: Pod for on the node: multus-wm6kq, Cpu: 10, Mem: 157286400
Feb  3 10:55:08.337: INFO: Pod for on the node: network-metrics-daemon-82r26, Cpu: 20, Mem: 125829120
Feb  3 10:55:08.337: INFO: Pod for on the node: network-check-target-6hxm2, Cpu: 10, Mem: 157286400
Feb  3 10:55:08.337: INFO: Pod for on the node: ovs-l84dj, Cpu: 15, Mem: 419430400
Feb  3 10:55:08.337: INFO: Pod for on the node: sdn-gm9jz, Cpu: 110, Mem: 230686720
Feb  3 10:55:08.337: INFO: Node: ip-10-0-187-51.us-west-1.compute.internal, totalRequestedCPUResource: 899, cpuAllocatableMil: 1500, cpuFraction: 0.5993333333333334
Feb  3 10:55:08.337: INFO: Node: ip-10-0-187-51.us-west-1.compute.internal, totalRequestedMemResource: 4115199590, memAllocatableVal: 6858665984, memFraction: 0.5999999999416796
STEP: Compute Cpu, Mem Fraction after create balanced pods.
Feb  3 10:55:08.337: INFO: ComputeCPUMemFraction for node: ip-10-0-200-155.us-west-1.compute.internal
Feb  3 10:55:08.638: INFO: Pod for on the node: c5ab9bca-843b-4cd4-816a-d78557d49ea7-0, Cpu: 361, Mem: 421987123
Feb  3 10:55:08.638: INFO: Pod for on the node: aws-ebs-csi-driver-node-hvtms, Cpu: 30, Mem: 157286400
Feb  3 10:55:08.638: INFO: Pod for on the node: tuned-vw9d7, Cpu: 10, Mem: 52428800
Feb  3 10:55:08.638: INFO: Pod for on the node: dns-default-gj8vb, Cpu: 65, Mem: 137363456
Feb  3 10:55:08.638: INFO: Pod for on the node: node-ca-29qp8, Cpu: 10, Mem: 10485760
Feb  3 10:55:08.638: INFO: Pod for on the node: ingress-canary-j7rnn, Cpu: 10, Mem: 20971520
Feb  3 10:55:08.638: INFO: Pod for on the node: machine-config-daemon-pfch2, Cpu: 40, Mem: 104857600
Feb  3 10:55:08.638: INFO: Pod for on the node: alertmanager-main-0, Cpu: 8, Mem: 283115520
Feb  3 10:55:08.638: INFO: Pod for on the node: grafana-7864bffbf8-kjzz8, Cpu: 5, Mem: 125829120
Feb  3 10:55:08.638: INFO: Pod for on the node: node-exporter-hjvzw, Cpu: 9, Mem: 220200960
Feb  3 10:55:08.638: INFO: Pod for on the node: prometheus-adapter-fb6c7c7f4-xb5j9, Cpu: 1, Mem: 26214400
Feb  3 10:55:08.638: INFO: Pod for on the node: prometheus-k8s-0, Cpu: 76, Mem: 1262485504
Feb  3 10:55:08.638: INFO: Pod for on the node: thanos-querier-645fd8f7df-7n82z, Cpu: 9, Mem: 96468992
Feb  3 10:55:08.638: INFO: Pod for on the node: multus-5fz48, Cpu: 10, Mem: 157286400
Feb  3 10:55:08.638: INFO: Pod for on the node: network-metrics-daemon-2srhr, Cpu: 20, Mem: 125829120
Feb  3 10:55:08.638: INFO: Pod for on the node: network-check-target-fl4xm, Cpu: 10, Mem: 157286400
Feb  3 10:55:08.638: INFO: Pod for on the node: ovs-zp748, Cpu: 15, Mem: 419430400
Feb  3 10:55:08.638: INFO: Pod for on the node: sdn-66dlh, Cpu: 110, Mem: 230686720
Feb  3 10:55:08.638: INFO: Node: ip-10-0-200-155.us-west-1.compute.internal, totalRequestedCPUResource: 899, cpuAllocatableMil: 1500, cpuFraction: 0.5993333333333334
Feb  3 10:55:08.638: INFO: Node: ip-10-0-200-155.us-west-1.compute.internal, totalRequestedMemResource: 4115071795, memAllocatableVal: 6858452992, memFraction: 0.5999999999708389

@damemi damemi force-pushed the openshift-balance-nodes-scheduling-ubernetes-lite branch from 50bee39 to 98180e4 Compare February 3, 2021 16:04
@openshift-ci-robot
Copy link

@damemi: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

This adds a call to createBalancedPods during the ubernetes_lite scheduling e2es,
which are prone to improper score balancing due to unbalanced utilization.
@damemi damemi force-pushed the openshift-balance-nodes-scheduling-ubernetes-lite branch from 98180e4 to 05b10ad Compare February 5, 2021 16:00
@openshift-ci-robot openshift-ci-robot added the backports/validated-commits Indicates that all commits come to merged upstream PRs. label Feb 5, 2021
@openshift-ci-robot
Copy link

@damemi: the contents of this pull request could be automatically validated.

The following commits are valid:

@openshift-ci-robot openshift-ci-robot removed the backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. label Feb 5, 2021
Copy link

@soltysh soltysh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve

@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: damemi, soltysh

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot openshift-ci-robot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Feb 5, 2021
@damemi
Copy link
Author

damemi commented Feb 5, 2021

/cherry-pick release-4.7

@openshift-cherrypick-robot

@damemi: once the present PR merges, I will cherry-pick it on top of release-4.7 in a new PR and assign it to you.

Details

In response to this:

/cherry-pick release-4.7

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-bot
Copy link

/retest

Please review the full test history for this PR and help us cut down flakes.

24 similar comments
@openshift-bot
Copy link

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot openshift-merge-robot merged commit c3cfb81 into openshift:master Feb 7, 2021
@openshift-ci-robot
Copy link

@damemi: Some pull requests linked via external trackers have merged:

The following pull requests linked via external trackers have not merged:

These pull request must merge or be unlinked from the Bugzilla bug in order for it to move to the next state. Once unlinked, request a bug refresh with /bugzilla refresh.

Bugzilla bug 1896558 has not been moved to the MODIFIED state.

Details

In response to this:

Bug 1896558: Balance nodes in scheduling e2e

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-cherrypick-robot

@damemi: new pull request created: #554

Details

In response to this:

/cherry-pick release-4.7

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. backports/validated-commits Indicates that all commits come to merged upstream PRs. bugzilla/severity-medium Referenced Bugzilla bug's severity is medium for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. kind/flake Categorizes issue or PR as related to a flaky test. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants