Bug 2103680 - Setting disableNetworkDiagnostics: true does not persist when network-operator pod gets re-created
Summary: Setting disableNetworkDiagnostics: true does not persist when network-operato...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.11
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.12.0
Assignee: Jaime Caamaño Ruiz
QA Contact: Anurag saxena
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-04 13:36 UTC by Marius Cornea
Modified: 2023-01-17 19:51 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previously, the network Operator configuration `disableNetworkDiagnostics` stalls on Operator restart or reboot. As a result, network diagnostics deployment is present in the cluster after network Operator restarts or reboots even if it had been previously disabled with the `disableNetworkDiagnostics` configuration setting. With this update, network Operator configuration `disableNetworkDiagnostics` preserves on Operator restart or reboot. As a result, network diagnostics deployment is no longer present in the cluster after network Operator restarts or reboots if disabled with the `disableNetworkDiagnostics` configuration setting. (link:https://bugzilla.redhat.com/show_bug.cgi?id=2103680[*BZ#2103680*])
Clone Of:
Environment:
Last Closed: 2023-01-17 19:51:19 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-network-operator pull 1527 0 None open Bug 2103680: avoid overrriding disableNetworkDiagnostics on reconciliation 2022-08-17 17:41:48 UTC
Red Hat Product Errata RHSA-2022:7399 0 None None None 2023-01-17 19:51:37 UTC

Description Marius Cornea 2022-07-04 13:36:04 UTC 
Description of problem:

Setting disableNetworkDiagnostics: true does not persist when network-operator pod gets re-created.

Version-Release number of selected component (if applicable):
4.11.0-rc.0

How reproducible:
100%

Steps to Reproduce:

1. $ oc patch network.operator.openshift.io/cluster  --patch '{"spec":{"disableNetworkDiagnostics":true}}' --type=merge
network.operator.openshift.io/cluster patched

2. $  oc -n openshift-network-operator delete pods network-operator-9b68954c6-bclx6
pod "network-operator-9b68954c6-bclx6" deleted


3. $ oc get network.operator.openshift.io cluster  -o json | jq .spec.disableNetworkDiagnostics
false


Actual results:
disableNetworkDiagnostics set to false, not set to true as configured in step 1

Expected results:
disableNetworkDiagnostics set to true

Additional info:

Attaching must-gather.
Comment 5 Marius Cornea 2022-08-23 09:44:15 UTC 
Verified on 4.12.0-0.nightly-2022-08-23-031342:
Comment 8 errata-xmlrpc 2023-01-17 19:51:19 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.12.0 bug fix and 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.

https://access.redhat.com/errata/RHSA-2022:7399
Note You need to log in before you can comment on or make changes to this bug.