Bug 2048756 - Static Pods are not starting in certain scenarios
Summary: Static Pods are not starting in certain scenarios
Keywords:
Status: CLOSED DUPLICATE of bug 2040533
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 4.9
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: 4.11.0
Assignee: Ryan Phillips
QA Contact: Sunil Choudhary
URL:
Whiteboard:
: 2049488 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-31 18:40 UTC by Ryan Phillips
Modified: 2022-02-03 17:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-02-03 14:25:05 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift kubernetes pull 1157 0 None open Bug 2048756: UPSTREAM: 107900: Pods that have terminated before starting should not block startup 2022-02-03 14:20:21 UTC

Description Ryan Phillips 2022-01-31 18:40:41 UTC 
Description of problem:
After a discussion, we are reverting upstream https://github.com/kubernetes/kubernetes/pull/104743

"Ensure there is one running static pod with the same full name"

Version-Release number of selected component (if applicable):
4.10 and 4.9

How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Ryan Phillips 2022-02-03 14:21:48 UTC 
*** Bug 2049488 has been marked as a duplicate of this bug. ***
Comment 2 Ryan Phillips 2022-02-03 14:25:05 UTC 

*** This bug has been marked as a duplicate of bug 2040533 ***
Note You need to log in before you can comment on or make changes to this bug.