Bug 2034506 - Network operator changes ovnkube-config too early causing ovnkube-master pods to crashloop during cluster upgrade
Summary: Network operator changes ovnkube-config too early causing ovnkube-master pods...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.6
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.7.z
Assignee: Christoph Stäbler
QA Contact: Anurag saxena
Olivia Payne
Depends On: 2030465
Blocks: 2046009
TreeView+ depends on / blocked
Reported: 2021-12-21 07:41 UTC by OpenShift BugZilla Robot
Modified: 2022-07-29 09:08 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Release Note: Previously, the `ovnkube-node` and `-master` pods failed to start when the config file contained an unknown field or section. This caused failures on `ovn-kubernetes` updates. With this update, `ovn-kube` logs a warning in config files so `ovn-kube` updates do not fail if a config file contains an unknown field or section. Cause: ovnkube-node & -master pods fail to start, when the config file contains an unknown field or section. Consequence: Can lead to failures on ovn-kubernetes updates, if a new config field or section was introduced. Imagine the following scenario: 1. ConfigMap is updated 2. ovnkube-node rollout starts 3. somehow an ovnkube-master pod needs to be (re-)started (be it through eviction from a node or something else) 4. the newly started ovnkube-master pod isn't aware of the new config structure (as it is still on the old version) and fails to parse the config, resulting in a crashloop of the newly ovnkube-master. This can result in a stucking rollout. Fix: Make ovn-kube resilient for unknown field in config files and logs a warning instead of exiting if such a field was found. Result: ovn-kube updates do not fail if config file contains an unknown field or section.
Clone Of:
Last Closed: 2022-02-03 05:18:57 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift ovn-kubernetes pull 882 0 None Merged [release-4.7] Bug 2034506: Make config parsing more resilient for unknown fields 2022-01-14 07:30:12 UTC
Red Hat Product Errata RHSA-2022:0283 0 None None None 2022-02-03 05:19:15 UTC

Comment 6 errata-xmlrpc 2022-02-03 05:18:57 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 (Moderate: OpenShift Container Platform 4.7.42 security update), and where to find the updated
files, follow the link below.

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


Note You need to log in before you can comment on or make changes to this bug.