As part of the "Openshift pre-flights check", can we explore possible solutions to check if the installer can verify the ignition configs.

The intention behind this request is to explore options to reduce no of cases, improve error message, or something that can help probably customers troubleshoot the to issue themselves.

See the section "Ignition and HTTP server validator" in doc [1].

We have seen scenarios where the installation gets failed due to bad ignition configs.
Here is the article [2] where you can see the list of cases due to such issues.

We can also see there are some ongoing customization work with related to ignition configs[3] so verifying ignitions or including validation will surely help the customers.

What we want is, if the installer can first verify the ignition and report an error in case if it is incorrectly configured and the installation must not proceed and throw the error.

Such error improvisation messages would help customers identifying the issues themselves and fix it, prior reaching out to Red Hat technical support.

Benefits:

a, Reporting failure with user-friendly would save a lot of time for the customer and for the CEE.
b, Reduce no of cases coming to Red Hat.
b, Improve product installer behavior.
c, Customers do not blame the product for the failure.

[1] https://docs.google.com/document/d/1shd5FZGF2twOuxM_G0wkViAvtFyQJZCY4xBQgDo-qRw/edit?usp=sharing
[2] https://access.redhat.com/solutions/4316771
[3] https://issues.redhat.com/browse/KNIP-1531