-
Bug
-
Resolution: Unresolved
-
Normal
-
4.17
-
Moderate
-
No
-
1
-
uShift Sprint 268, uShift Sprint 269, uShift Sprint 270
-
3
-
False
-
This is a clone of issue OCPBUGS-52206. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-51366. The following is the description of the original issue:
—
Description of problem:
MicroShift is left to default configuration for node ip, service and cluster networks. This is also a disconnected environment, hence no default routes are configured in the host because there is no need. When starting or showing configuration (with microshift show-config), an ipv6 configuration can be seen for the values mentioned above.
Version-Release number of selected component (if applicable):
4.17.3
How reproducible:
Steps to Reproduce:
1. 2. 3.
Actual results:
MicroShift gets configured with ipv6 addresses.
Expected results:
MicroShift should get configured with ipv4 addresses.
Additional info:
- clones
-
OCPBUGS-52206 MicroShift defaults configuration to IPv6 in IPv4-first environment
-
- Verified
-
- is blocked by
-
OCPBUGS-52206 MicroShift defaults configuration to IPv6 in IPv4-first environment
-
- Verified
-
- is duplicated by
-
OCPBUGS-52860 MicroShift defaults configuration to IPv6 in IPv4-first environment
-
- Closed
-
- links to
-
RHBA-2025:4217 Red Hat build of MicroShift 4.17.z bug fix and enhancement update