Bug 1765736 - [sig-scheduling] SchedulerPriorities [Serial] Pod should avoid nodes that have avoidPod annotation
Summary: [sig-scheduling] SchedulerPriorities [Serial] Pod should avoid nodes that hav...
Keywords:
Status: CLOSED DUPLICATE of bug 1764412
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: kube-scheduler
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.3.0
Assignee: Jan Chaloupka
QA Contact: ge liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-10-25 20:18 UTC by Anurag saxena
Modified: 2019-10-29 09:33 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-29 09:33:16 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Anurag saxena 2019-10-25 20:18:25 UTC
Description of problem:
fail [k8s.io/kubernetes/test/e2e/framework/util.go:1167]: Expected
    <string>: ci-op-iy1d56dh-09f59-48f9h-worker-centralus1-97pgd
not to equal
    <string>: ci-op-iy1d56dh-09f59-48f9h-worker-centralus1-97pgd

Additional info:
https://testgrid.k8s.io/redhat-openshift-release-4.3-informing-ocp#release-openshift-ocp-installer-e2e-azure-serial-4.3
https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-azure-serial-4.3/246

Comment 1 Jan Chaloupka 2019-10-29 09:33:16 UTC
From the scheduler logs:

```
I1025 17:59:40.275354       1 scheduler.go:667] pod e2e-sched-priority-6657/scheduler-priority-avoid-pod-6ztcb is bound successfully on node "ci-op-iy1d56dh-09f59-48f9h-worker-centralus2-tk9vl", 6 nodes evaluated, 2 nodes were found feasible. Bound node resource: "Capacity: CPU<2>|Memory<8140500Ki>|Pods<250>|StorageEphemeral<133682156Ki>; Allocatable: CPU<1500m>|Memory<7526100Ki>|Pods<250>|StorageEphemeral<123201474766>.".
I1025 17:59:40.302038       1 scheduler.go:667] pod e2e-sched-priority-6657/scheduler-priority-avoid-pod-ztvr2 is bound successfully on node "ci-op-iy1d56dh-09f59-48f9h-worker-centralus1-97pgd", 6 nodes evaluated, 1 nodes were found feasible. Bound node resource: "Capacity: CPU<2>|Memory<8140492Ki>|Pods<250>|StorageEphemeral<133682156Ki>; Allocatable: CPU<1500m>|Memory<7526092Ki>|Pods<250>|StorageEphemeral<123201474766>.".
```

From the test logs:

```
Oct 25 17:58:50.525: INFO: Node: ci-op-iy1d56dh-09f59-48f9h-worker-centralus1-97pgd, totalRequestedCPUResource: 690, cpuAllocatableMil: 1500, cpuFraction: 0.46
Oct 25 17:58:50.525: INFO: Node: ci-op-iy1d56dh-09f59-48f9h-worker-centralus1-97pgd, totalRequestedMemResource: 1572864000, memAllocatableVal: 7706718208, memFraction: 0.2040899845497504
Oct 25 17:58:50.616: INFO: Node: ci-op-iy1d56dh-09f59-48f9h-worker-centralus2-tk9vl, totalRequestedCPUResource: 2240, cpuAllocatableMil: 1500, cpuFraction: 1
Oct 25 17:58:50.616: INFO: Node: ci-op-iy1d56dh-09f59-48f9h-worker-centralus2-tk9vl, totalRequestedMemResource: 4861198336, memAllocatableVal: 7706726400, memFraction: 0.6307734417560223
Oct 25 17:58:50.686: INFO: Node: ci-op-iy1d56dh-09f59-48f9h-worker-centralus3-qtjpz, totalRequestedCPUResource: 2010, cpuAllocatableMil: 1500, cpuFraction: 1
Oct 25 17:58:50.686: INFO: Node: ci-op-iy1d56dh-09f59-48f9h-worker-centralus3-qtjpz, totalRequestedMemResource: 4660920320, memAllocatableVal: 7706718208, memFraction: 0.6047866542157603
```

Total requested cpu is more than there is allocatable on "ci-op-iy1d56dh-09f59-48f9h-worker-centralus2-tk9vl" and "ci-op-iy1d56dh-09f59-48f9h-worker-centralus3-qtjpz" nodes.

*** This bug has been marked as a duplicate of bug 1764412 ***


Note You need to log in before you can comment on or make changes to this bug.