Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2026111

Summary: Altering the Schedule Profile configurations doesn't affect the placement of the pods
Product: OpenShift Container Platform Reporter: Mike Dame <mdame>
Component: kube-schedulerAssignee: Maciej Szulik <maszulik>
Status: CLOSED EOL QA Contact: RamaKasturi <knarra>
Severity: medium Docs Contact:
Priority: low    
Version: 4.7CC: aos-bugs, knarra, mfojtik, yhe
Target Milestone: ---Flags: mfojtik: needinfo?
Target Release: 4.7.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: LifecycleStale
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2026110 Environment:
Last Closed: 2022-05-25 11:00:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2002300, 2026109, 2026110    
Bug Blocks:    

Comment 2 Michal Fojtik 2022-01-05 19:22:28 UTC 
This bug hasn't had any activity in the last 30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're marking this bug as "LifecycleStale" and decreasing the severity/priority. If you have further information on the current state of the bug, please update it, otherwise this bug can be closed in about 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. Additionally, you can add LifecycleFrozen into Whiteboard if you think this bug should never be marked as stale. Please consult with bug assignee before you do that.
Comment 4 Maciej Szulik 2022-05-25 11:00:44 UTC 
Given the priority and the current time frame I don't think we'll be able to address this issue in 4.7.