Butane config in example cannot be translated: error parsing version; must be a valid semver
scrool opened this issue · 4 comments
Which section(s) is the issue in?
Disk partitioning found under:
OKD Installing / Installing on any platform / Installing a cluster on any platform
What needs fixing?
Butane config examples aren't parsable by Butane 0.20.0:
$ butane --check $HOME/clusterconfig/98-var-partition.bu
Error translating config: error parsing version; must be a valid semver
The issue is in:
version: 4.0
which should be changed to current version of the OpenShift - e.g.:
version: 4.14.0
A one-liner change might help here. For more explanation there could be also a link to https://coreos.github.io/butane/upgrading-openshift which explains differences between various OpenShift Butane Configs.
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle rotten
/remove-lifecycle stale
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.
/close
@openshift-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting
/reopen.
Mark the issue as fresh by commenting/remove-lifecycle rotten.
Exclude this issue from closing again by commenting/lifecycle frozen./close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.