-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.20.z
-
None
-
None
-
False
-
-
None
-
Low
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
There is incorrect mention of machine config in the docs in MicroShift. MicroShift doesn't use machine config. https://docs.redhat.com/en/documentation/red_hat_build_of_microshift/4.20/html/configuring/microshift-nw-ipv6-config#nw-ovn-kubernetes-limitations_microshift-nw-ipv6-config Last bullet point says: """" If you set the ipv6.disable parameter to 1 in the kernelArgument section of the MachineConfig custom resource (CR) for your cluster, OVN-Kubernetes pods enter a CrashLoopBackOff state. Additionally, updating your cluster to a later version of Red Hat build of MicroShift fails because the Network Operator remains on a Degraded state. Red Hat does not support disabling IPv6 addresses for your cluster so do not set the ipv6.disable parameter to 1. """" The part "If you set the ipv6.disable parameter to 1 in the kernelArgument section of the MachineConfig custom resource (CR)..." is wrong. As MicroShift runs on RHEL, there could be better wording. """ If you set the ipv6.disable parameter to 1 in the Kernel in RHEL, the OVN-Kubernetes pods .... """
Version-Release number of selected component (if applicable):
MicroShift docs 4.20, 4.21
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info: