Loading...

XML

Word

Printable

Type: Bug
Resolution: Unresolved
Priority: Normal
Fix Version/s: None
Affects Version/s: 4.20
Component/s: Networking / cluster-network-operator
Labels:
None

Activity Type:
None
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Story Points:
None
Severity:
None
Regression:
None

Target Backport Versions:
None
Target Version:
None
Release Blocker:
None
Sprint:
None

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

PX Impact Score:

Release Note Status:
None
Release Note Type:
None
Release Note Text:
None

Escape Reason:
None
Escape Impact:
None
Corrective Measures:
None
SDLC stage when should've been found:
None

Description of problem:

CNO updates ovnkube-node DaemonSet before MCO completes node configuration during 4.19→4.20 upgrade, causing Dynamic OVS Pinning to fail due to missing management annotation on pods

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

    4.20

How reproducible:

Steps to Reproduce:

    1.Deploy PerformanceProfile with userLevelNetworking=true on OCP 4.19
    2. Upgrade cluster to OCP 4.20
3. Verify ovnkube-node pods have incorrect CPU affinity missing management annotation

Actual results:

ovnkube-node pods does not have target.workload.openshift.io/management annotation

Expected results:

 ovnkube-node pods should have target.workload.openshift.io/management annotation

Additional info:

Assignee:: Einat Glottmann

Reporter:: SARGUN NARULA

Need Info From:: None

Contributors:: None

QA Contact:: Anurag Saxena

Doc Contact:: None

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Created:: 2025/12/31 12:02 PM

Updated:: 2026/01/05 2:50 PM