Bug 1927358 - p&f: add auto update for priority & fairness bootstrap configuration objects [NEEDINFO]
Summary: p&f: add auto update for priority & fairness bootstrap configuration objects
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: kube-apiserver
Version: 4.7
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: ---
: 4.6.z
Assignee: Abu Kashem
QA Contact: Xingxing Xia
URL:
Whiteboard: LifecycleStale
: 1930005 (view as bug list)
Depends On: 1926724 1930005
Blocks: 1927363
TreeView+ depends on / blocked
 
Reported: 2021-02-10 15:43 UTC by Abu Kashem
Modified: 2021-09-20 16:29 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1926724
: 1927363 (view as bug list)
Environment:
Last Closed: 2021-09-20 16:29:53 UTC
Target Upstream Version:
Embargoed:
mfojtik: needinfo?

Attachments (Terms of Use)

Comment 1 Ke Wang 2021-02-18 07:19:32 UTC 
*** Bug 1930005 has been marked as a duplicate of this bug. ***
Comment 2 Michal Fojtik 2021-03-20 07:20:38 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 Keywords if you think this bug should never be marked as stale. Please consult with bug assignee before you do that.
Comment 3 Abu Kashem 2021-09-20 16:25:26 UTC 
the dependent BZ is still in progress - https://github.com/openshift/kubernetes/pull/563
Comment 4 Abu Kashem 2021-09-20 16:29:53 UTC 
4.6 is 'v1alpha1' and the original upstream fix was done on 'v1beta1' - https://github.com/kubernetes/kubernetes/pull/98028. The severity of this BZ is low that it does not warrant a back-port from 'v1beta1' to 'v1alpha1'. Also, upstream will not back port this, so closing the BZ.
Note You need to log in before you can comment on or make changes to this bug.