Loading...

XML

Word

Printable

Type: Bug
Resolution: Unresolved
Priority: Major
Fix Version/s: None
Affects Version/s: 4.14
Component/s: Networking / multus
Labels:
None

Activity Type:
Quality / Stability / Reliability
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Story Points:
None
Severity:
Important
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

A node in vSphere ESXi cluster was replaced.
Afterwards the OCP cluster became inaccessible.
oc commands were intermittent, unable to login

During troubleshooting noticed that there were pending multus csr's
After approving the csr's the cluster was healthy.

Why did the replacement of a node (not an Openshift node) in the vSphere ESXi cluster cause multus csr's to be generated.

Assignee:: sdn-team bot

Reporter:: Daniel Seals

Need Info From:: None

Contributors:: None

QA Contact:: Weibin Liang

Doc Contact:: None

Votes:: 1 Vote for this issue

Watchers:: 4 Start watching this issue

Created:: 2025/01/31 10:14 PM

Updated:: 2025/10/15 2:47 PM