-
Bug
-
Resolution: Done-Errata
-
Critical
-
None
-
4.14
-
Critical
-
No
-
SDN Sprint 240, SDN Sprint 241
-
2
-
Approved
-
False
-
Description of problem:
Nodes for the HyperShift/KubeVirt platform fail to become ready due to the ovnkube-node pods crashlooping.
Version-Release number of selected component (if applicable):
4.14 nightly starting August 9th
How reproducible:
100%
Steps to Reproduce:
1. Start a HyperShift/KubeVirt guest cluster.https://hypershift-docs.netlify.app/how-to/kubevirt/create-kubevirt-cluster/
Actual results:
* The nodes get stuck in a NotReady status * The ovnkube-node pods crash loop
Expected results:
Nodes join the hypershift kubevirt hosted cluster successfully.
Additional info:
ovnkube-node log F0811 17:33:40.857584 62938 ovnkube.go:136] failed to start node network manager: failed to start default node network controller: unable to find encap uuid to set geneve port for chassis e4b75a28-fa33-423a-a93e-0aefc4c499b9
- blocks
-
CNV-25888 [GA] Self-managed Hosted Control Planes support for the OpenShift Virtualization Provider
- Closed
- links to
-
RHEA-2023:5006 rpm
- mentioned in
-
Page Loading...