-
Bug
-
Resolution: Done-Errata
-
Normal
-
None
-
4.16
-
Low
-
No
-
1
-
uShift Sprint 256
-
1
-
False
-
-
A mistake in validation allowed empty entries in the `listenAddress` configuration parameter. This prevented MicroShift from starting and also rendered a difficult-to-understand error message. Empty entries in the list are now filtered.
-
Bug Fix
-
In Progress
This is a clone of issue OCPBUGS-35468. The following is the description of the original issue:
—
Description of problem:
When you copy the config.yaml from defaults and do not configure ingress, the microshift will fail to start with error: Jun 13 20:43:24 node-0 microshift[8824]: ??? E0613 20:43:24.440185 8824 run.go:74] "command failed" err="invalid configuration: error validating ingress.listenAddress: interface not present in the host"
Version-Release number of selected component (if applicable):
4.16
How reproducible:
- copy the config.yaml from default, do not fill in "ingress.listenAddress.
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
- improvement should be that when config.yaml.defaults will be created, the listenAddress will be propagated from the current host - put this in the docs as requirement or set the microshift to ignore that value and take default interface (based on default route) as listenAddress
Additional info:
- clones
-
-
- Closed
-
- is blocked by
-
-
- Closed
-
- links to
-
RHBA-2024:4471
Red Hat build of MicroShift 4.16.z bug fix and enhancement update