Bug 1767579

Summary: Openshift 3.11 CI is broken because of SDN pod crash looping
Product: OpenShift Container Platform Reporter: Hemant Kumar <hekumar>
Component: InstallerAssignee: Joseph Callen <jcallen>
Installer sub component: openshift-ansible QA Contact: Gaoyun Pei <gpei>
Status: CLOSED ERRATA Docs Contact:
Severity: urgent    
Priority: urgent CC: cdc, jialiu, maszulik, rmeggins
Version: 3.11.0   
Target Milestone: ---   
Target Release: 3.11.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-12-16 11:57:11 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Comment 2 Casey Callendrello 2019-11-05 13:05:00 UTC
*** Bug 1768854 has been marked as a duplicate of this bug. ***

Comment 6 Aniket Bhat 2019-11-05 16:49:08 UTC
We have been talking with the test-platform team to get us a cluster to pause rather than get deprovisioned on node failing to come up.

Comment 8 Rich Megginson 2019-11-14 23:26:49 UTC
Update: this seems to fix the problem for logging: https://github.com/openshift/aos-cd-jobs/pull/2040

For some reason, setting l_os_non_standard_reg_url causes the tasks in openshift-node/private/restart.yml to be executed.  When you omit this setting, it will skip those tasks.

For the reasons why we were doing this in the first place, see the discussion in

Comment 10 Gaoyun Pei 2019-12-02 10:36:51 UTC
Verify this bug with openshift-ansible-3.11.156-1.git.0.5f2cfa4.el7.noarch.rpm.

Proposed PR already merged in. No node restart step would be executed there.

Comment 12 errata-xmlrpc 2019-12-16 11:57:11 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:4050