Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: None
Affects Version/s: 4.13.z, 4.13.0, 4.14.0
Component/s: Machine Config Operator
Labels:
- coreos
- updateRemotingTeam

Severity:
Important
Regression:
No
Sprint:
Sprint 237 - Update&Remoting
sprint_count:
1
Release Blocker:
Rejected
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Target Version:

4.13.z

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

Description of problem:

Upgrade to OCP 4.13.0 stuck due to machine-config error 'failed to run- nmstatectl: exit status 1'

Version-Release number of selected component (if applicable)

How reproducible:

Upgrading from 4.12.17 to 4.13.0

Steps to Reproduce:

1.
2.
3.

Actual results:

Expected results:

Additional info:

relates to

OCPBUGS-15924 Scale-up of OpenShift Container Platform 4 - Node is stuck post OpenShift Container Platform 4.13.4 update

Closed

links to

https://github.com/nmstate/nmstate/pull/2361

openshift/machine-config-operator#3716: OCPBUGS-13404,OCPBUGS-14298: Dockerfile: pin to nmstate-2.2.9-6.rhaos4.13.el8

Upgrade to OCP 4.13.0 stuck due to machine-config error 'failed to run- nmstatectl: exit status 1'

Assignee:: Colin Walters

Reporter:: Vered Berenstein Paz (Inactive)

QA Contact:: Sergio Regidor de la Rosa

Votes:: 0 Vote for this issue

Watchers:: 19 Start watching this issue

Created:: 2023/05/30 4:51 PM

Updated:: 2023/07/07 7:37 AM

Resolved:: 2023/06/22 12:16 PM