Please document in a "known issues" section that installing OKD v4.16/v4.17 in UPI+ABI/AI on baremetal fails

[titou10titou10]

So OKD v4.16/4.17 is officially out: https://github.com/okd-project/okd/releases/tag/4.17.0-okd-scos.0
Good work!

Could you add somewhere that installing those version in UPI with the agent based installer (ABI) or agent installer (AI) on baremetal does not work .
The problem and possible workaround is described here and in many other discussions (#2035, #2015, #1983 ...)

@JaimeMagiera suggested this in a comment here: #2019 (reply in thread)

IMHO it could spare some time for people that use this method to install OKD in UPI with ABI/AI on baremetal

[GingerGeek]

I've created okd-project/okd-web#47 and will read through these discussions and form an additional page for the update notes section. If you have time to contribute and could write something yourself please let me know!

[titou10titou10]

OK
I'll try to write something.
If the issues are the same as before with this release, it will be the synthesis of #2015 (FCOS bootstrap "read-only") and #2035 (issue with PostgreSQL used by the agent installer not starting..)
I'll install v4.17 only, not v4.16 . I will "move" the workload from v4.15 to v4.17, taking the opportunity to start a fresh new cluster.
It is written elsewhere that v4.16 is not meant to be installed "straight", but only used as a migration step from v4.15 to v4.17, so it is useless to document v4.16 ABI/AI UPI baremetal install problems

[GingerGeek]

Yes, thank you. I have seen your response on the issue and will get that up shortly.

Correct that we don't see reasons why 4.16 would need to be freshly installed as it's just pass-thru from existing 4.15 clusters. New clusters should be 4.17.

Thank you for the contributions :)