Bug 2027982

Summary: nncp stucked at ConfigurationProgressing
Product: OpenShift Container Platform Reporter: Vinya Nema <vnema>
Component: NetworkingAssignee: Ben Nemec <bnemec>
Networking sub component: kubernetes-nmstate QA Contact: Aleksandra Malykhin <amalykhi>
Status: CLOSED ERRATA Docs Contact:
Severity: unspecified    
Priority: unspecified CC: aos-bugs, bnemec, cnv-qe-bugs, danken, ellorent, phoracek, vjaypurk, vpickard, yboaron
Version: 4.8   
Target Milestone: ---   
Target Release: 4.10.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-03-10 16:31:07 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:

Description Vinya Nema 2021-12-01 08:15:41 UTC 
Description of problem:

- some nncp stucked at ConfigurationProgressing
- The nmstate operator, nmstate and nncp are created. 
- For each new cluster installation in a cluster with 3 masters and 19 workers, around 2 nodes every time get stucked in ConfigurationProgressing.
- Every time this happens in different workers.

Cu followed the below steps to resolve the issue:-

1. Delete pending nncp
2. Delete nmstate handler pod for the node with pending nncp
3. Wait for handler to be up again
4. Create the nncp again

It would be great to know why nncps get stuck.

Version-Release number of selected component (if applicable): openshift 4.8



How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

After reinstalling the cluster i reproduced again the issue.

In the mcp called standard with 15 nodes, we changed the parameter maxunavailable to 14 so the installation process goes faster as it is a fresh installation.
So 14 nodes are restarted at the same time. However, this issue has also been seen in another pool with only 1 node, is it a correct configuration or needs some modifications?
Comment 2 Quique Llorente 2021-12-01 09:19:31 UTC 
@
Comment 9 Dan Kenigsberg 2021-12-07 20:08:24 UTC 
@vpickard@vpickard please note that this customer is using the stand-alone Tech Preview. Does kubernetes-nmstate-operator.4.8.0-202111191337 include the fix to bug 1967887?
Comment 16 errata-xmlrpc 2022-03-10 16:31:07 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.10.3 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:0056