After QE discussion, though comment 2 and comment 4 seem to have different cause, though they indicate almost same errors as original bug. Will dig again.
So please ignore comment 2 and 4. Restoring original bug title ...
Though 120G minimal disk size is official recommendation, for testing purpose, actually usually QE did not need so big size, because QE's vsphere cluster only has limit storage, it is possible to make the minimal disk size checking not mandatory, but use a warning message to instead of it?
Continuing comment 6: after more digging, my AWS envs' failure symptom is as same as bug 1862957#c7 ~ 1862957#c9, the cause is as same as bug 1862957, so my AWS envs failure will be tracked by that bug.
I checked that disk checking is introduced from PR: https://github.com/openshift/machine-api-operator/commit/5229694cbb14e3cd79a6a4dc0069fa2129920a34.
It seems that other platform disk limitation checking does not use the default value of official recommendation. Take GCP for example, the checking is 16GB < GCP disksize < 65536GB, the official recommendation value is 128GB.
As Jianlin in Comment 7 described, QE's vsphere cluster has limit storage, if setting 120G disk for each vm in one cluster on QE vsphere env, only 1 cluster can be setup at the same time. It has serious impact for QE to test on vsphere platform.
So is it possible to check vsphere disksize like than on GCP? Or let disksize checking not mandatory on vsphere platform?
this should prevent this from happening https://github.com/openshift/release/pull/11534
Based on understanding that same change to size works for QA flexi envs templates moving this to VERIFIED
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 (OpenShift Container Platform 4.6 GA Images), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.