Between openshift-install create manifests and openshift-install create cluster, users can edit manifests.

    When editing manifests related to each other, notably the control-plane-machine-set and the master machines (either openshift/99_...master-machines...yaml or cluster-api/machines/10_inframachine...yaml), if the resulting set of manifests has differing providerSpec sections, unexpected/weird things can happen during/after cluster install. See below for more.

    All, really

    100%

    1. openshift-install create manifests with a minimal AWS install-config
    2. Edit the providerSpec for the master-machines manifests but not the CPMS (or vice versa)
    3. opesnhift-install create cluster
    

    Master machines are created by installer according to the master-machines providerSpec; then after install completes they are replaced according to the CMPS.

    I mean, yeah, that's the expected result. But it's almost certainly not what the user wanted. Fail `create cluster` with an appropriate message.