You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
built from commit f4f5d0ee0f7591fd9ddf03ac337c804608102919
release image quay.io/openshift-release-dev/ocp-release@sha256:5c82cea5931996af509231c7a5a1611bcfd927dca4e362e6443d1f8a77a517c2
release architecture amd64
Platform: vSphere
What happened?
Installer complains that the install-config.yaml is not valid
What you expected to happen?
that the installer accept the yaml
How to reproduce it (as minimally and precisely as possible)?
install-config.yaml
storage:
files:
- path: /etc/chrony.conf
mode: 0644
overwrite: true
contents:
inline: |
pool timesrv1.ourdomain.tld iburst
pool timesrv2.ourdomain.tld iburst
pool timesrv3.ourdomain.tld iburst
driftfile /var/lib/chrony/drift
makestep 1.0 3
rtcsync
logdir /var/log/chrony
[osadmin@osdemo ~]$ ./openshift-install create cluster
WARNING failed to parse first occurrence of unknown field: failed to unmarshal install-config.yaml: error unmarshaling JSON: while decoding JSON: json: unknown field "storage"
INFO Attempting to unmarshal while ignoring unknown keys because strict unmarshaling failed
INFO Consuming Install Config from target directory
INFO Creating infrastructure resources...
INFO Waiting up to 20m0s (until 1:36AM EDT) for the Kubernetes API at https://api.osctest.ourdomain.tld:6443...
INFO API v1.28.7+c1f5b34 up
INFO Waiting up to 1h0m0s (until 2:19AM EDT) for bootstrapping to complete...
How to fix the chrony config in install-config.yaml ?
The text was updated successfully, but these errors were encountered:
Version
Platform: vSphere
What happened?
Installer complains that the install-config.yaml is not valid
What you expected to happen?
that the installer accept the yaml
How to reproduce it (as minimally and precisely as possible)?
install-config.yaml
How to fix the chrony config in install-config.yaml ?
The text was updated successfully, but these errors were encountered: