due to capacity constraints we will be revisiting this bug in the upcoming sprint
We are working on higher priority feature development and bug fixes. Hence moving this to next sprint.
We can't validate against the 0 value since when the field is empty (meaning equal to zero) we use the default value.
To avoid turning this bug into a huge change I added a validation for a nonnegative value, this is what other platforms are doing as well.
1. prepare install-config.yaml
2. set wrong string on vm_type
3. set negative value on memoryMB
Installation validation accuses wrong values as expected
to be added to errata
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.