-
Bug
-
Resolution: Done
-
Critical
-
4.14
-
None
-
Important
-
No
-
5
-
uShift Sprint 236, uShift Sprint 237
-
2
-
False
-
This is a clone of issue OCPBUGS-11967. The following is the description of the original issue:
—
Description of problem:
When OS doesn't have default route, ovnk is experiencing problems and causing cluster to not become fully functional
Version-Release number of selected component (if applicable):
main
How reproducible:
100%
Steps to Reproduce:
Personally, I built an RHEL4Edge ISO with container images embedded, installed and started the VM with libvirt network configured per instructions in https://github.com/openshift/microshift/blob/main/docs/rhel4edge_iso.md#offline-mode But I think it might just work on regular RHEL by: starting MicroShift to obtain the images, stopping VM, disconnecting network, and starting it again (without running microshift-cleanup to keep the images after boot)
Actual results:
ovn-k doesn't fully start, blocking start of the cluster NAMESPACE NAME READY STATUS RESTARTS AGE openshift-ovn-kubernetes ovnkube-master-22mqb 3/4 Running 4 (2m39s ago) 23m openshift-ovn-kubernetes ovnkube-node-xtghg 1/1 Running 0 23m
Expected results:
ovn-k handles "no default route" correctly and cluster proceeds to start to become fully functional
Additional info:
Slack thread with the discussion after I noticed the issue
https://redhat-internal.slack.com/archives/C03CJTNLKAT/p1681828117473549
- clones
-
-
- Closed
-
- is blocked by
-
-
- Closed
-
- links to
