Right now you must pre-generate your own UUID and set it as the ClusterID if you are using your own install-config.yml, otherwise the install fails. UUID is set when generating an install config and the rest of the code assumes it's set, but this is not the case if you're using a config file generated by other means. (i.e. Hive)
In past discussions the plan was to remove this from install-config as it was not meant to be something users could set.
Alternatively, we could keep it as an override and update the code to realize no UUID is set, and generate one. (we've requested being able to generate our own UUIDs as this would give us all info needed to cleanup a cluster in the event of install failure, without having to wrap install and upload metadata files, however this did not appear popular with install team in past discussions.)
Right now you must pre-generate your own UUID and set it as the ClusterID if you are using your own install-config.yml, otherwise the install fails. UUID is set when generating an install config and the rest of the code assumes it's set, but this is not the case if you're using a config file generated by other means. (i.e. Hive)
In past discussions the plan was to remove this from install-config as it was not meant to be something users could set.
Alternatively, we could keep it as an override and update the code to realize no UUID is set, and generate one. (we've requested being able to generate our own UUIDs as this would give us all info needed to cleanup a cluster in the event of install failure, without having to wrap install and upload metadata files, however this did not appear popular with install team in past discussions.)