Description of problem:
The customized items defined in Manifests files by users did not take effect when create cluster with existed customized Manifests.
Changes made to Manifests files:
[root@preserve-installer 080]# cat demo/manifests/cvo-overrides.yaml|grep channel
[root@preserve-installer 080]# cat demo/openshift/99_openshift-cluster-api_master-machines.yaml|grep Zone
After creating cluster succeed, checked above items.
2. Master was in zone us-east-1a
Version-Release number of the following components:
# ./openshift-install version
Steps to Reproduce:
1.Run "./openshift-install create manifests --dir demo" to generate default Manifests files.
# ls -la demo/
drwxr-xr-x. 4 root root 4096 Dec 26 08:31 .
drwxr-xr-x. 3 root root 4096 Dec 26 08:28 ..
drwxr-xr-x. 2 root root 4096 Dec 26 08:31 manifests
drwxr-xr-x. 2 root root 4096 Dec 26 08:31 openshift
2. Edit cvo-overrides.yaml and 99_openshift-cluster-api_master-machines.yaml
3. Run "./openshift-install create cluster --dir demo" to create cluster with above customized manifests
Customized items did not take effect.
User can create expected cluster with customized manifests.
 will fix this. I'd hoped to land it this week, but there was a lot of install-config churn and it slipped through.
Oops, I'd meant to link https://github.com/openshift/installer/pull/792
https://github.com/openshift/installer/pull/890 fixes preserving changes to the manifests.
https://github.com/openshift/installer/pull/1121 fixes specifying the availability zone to use for masters.
https://github.com/openshift/installer/pull/1211 fixes panic when reading in the master machines manifest file in later stages.
Some of these changes went out in v0.13.0 , but  is still in flight.
https://github.com/openshift/installer/pull/1121 just landed and will go out in the next release.
$ ./openshift-install version
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, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.