Bug 2103586 - [4.10] nmstate operator cannot be upgraded on SNO
Summary: [4.10] nmstate operator cannot be upgraded on SNO
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.10
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: ---
: 4.10.z
Assignee: Christoph Stäbler
QA Contact: Aleksandra Malykhin
URL:
Whiteboard:
Depends On: 2075491 2104938
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-04 07:31 UTC by Christoph Stäbler
Modified: 2022-07-20 07:46 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2075491
Environment:
Last Closed: 2022-07-20 07:46:10 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift kubernetes-nmstate pull 284 0 None open [release-4.10] Bug 2103586: Set operator replica & minReplica numbers depending on cluster topology 2022-07-04 07:43:01 UTC
Red Hat Product Errata RHBA-2022:5568 0 None None None 2022-07-20 07:46:27 UTC

Comment 6 Aleksandra Malykhin 2022-07-18 06:28:24 UTC 
Verified on
SNO Cluster version is 4.10.22
kubernetes-nmstate-operator.4.10.0-202207140916


Only one webhook pod started, no problems with update/upgrade. 


# oc get pods
NAME                                    READY   STATUS    RESTARTS   AGE
nmstate-cert-manager-8587fbb95d-x7f9r   1/1     Running   0          90s
nmstate-handler-7jk28                   1/1     Running   0          90s
nmstate-operator-d8dc5d96d-9hfpt        1/1     Running   0          99s
nmstate-webhook-8c4fdfcdb-njrjx         1/1     Running   0          90s
Comment 9 errata-xmlrpc 2022-07-20 07:46:10 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 (OpenShift Container Platform 4.10.23 bug fix 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/RHBA-2022:5568
Note You need to log in before you can comment on or make changes to this bug.