Bug 1698629

Summary: OCP 4.1: pods end up in CrashLoopBackOff state after a rolling reboot of the node
Product: OpenShift Container Platform Reporter: Phil Cameron <pcameron>
Component: NetworkingAssignee: Phil Cameron <pcameron>
Status: CLOSED ERRATA QA Contact: Meng Bo <bmeng>
Severity: high Docs Contact:
Priority: high    
Version: 4.1.0CC: ansverma, aos-bugs, arghosh, bbennett, bleanhar, bmeng, cdc, dbecker, dcbw, isanchez, jupittma, knakayam, ltomasbo, magnus.heino, m.andre, mburns, mcornea, mhayashi, mmichels, mnoguera, morazi, ocasalsa, pcameron, pdwyer, rhowe, sauchter, sponnaga, weliang, wsun, zhiwang
Target Milestone: ---Keywords: NeedsTestCase
Target Release: 4.1.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: See 1654044 Consequence: Fix: Result:
Story Points: ---
Clone Of: 1654044 Environment:
Last Closed: 2019-06-04 10:47:22 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: 1654044, 1723924, 1744077, 1748032    
Bug Blocks:    

Comment 2 Weibin Liang 2019-04-16 19:23:43 UTC
Tested and verified on v4.1.0-0.okd-2019-04-16-174206

There are no pods end up in CrashLoopBackOff state after a rolling reboot of the node.

Comment 4 errata-xmlrpc 2019-06-04 10:47:22 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:0758