Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Butane release container tag not yet updated to 0.23.0 #1848

Closed
Nemric opened this issue Dec 5, 2024 · 8 comments
Closed

Butane release container tag not yet updated to 0.23.0 #1848

Nemric opened this issue Dec 5, 2024 · 8 comments

Comments

@Nemric
Copy link

Nemric commented Dec 5, 2024

I was "wilfing" (What Was I Looking For?) today when I saw the latest Butane spec v1.6.0
Well, I did the update as fast as possible : https://github.com/Relativ-IT/Butane-Schemas
And did upgrade my butane configs to latest spec ... but it looks like the config transpiler quay.io/coreos/butane:release is not yet up to date ^^
Error translating config: No translator exists for variant fcos with version 1.6.0

regards :)

@jbtrystram
Copy link
Contributor

It looks like it's WIP :) coreos/butane#550

@Nemric
Copy link
Author

Nemric commented Dec 5, 2024

I'm using the latest (vs release) images now, it works ^^
Will close the issue when release will be out ;)

@Nemric
Copy link
Author

Nemric commented Dec 5, 2024

As my ign files are now on v3.5.0 specs, and as next week a new Fcos should come (stable, testing and next) will new ignition be included in them ?

@hrismarin
Copy link

As my ign files are now on v3.5.0 specs, and as next week a new Fcos should come (stable, testing and next) will new ignition be included in them ?

Since I was recently asking relatively the same questions, I'll bring what I (hopefully) learned here. Please correct me if I'm wrong.

Ignition v2.20.0 has now been released and the 3.5.0 config specs have been marked as stable, see https://github.com/coreos/ignition/releases/tag/v2.20.0. Because Ignition needs to go first, there is a window between where Ignition got stabilized but not yet Butane. It looks like the Butane docs page has now been updated to match the latest specs (if that's what @Nemric means) and Butane has been stabilized but not yet released.

@travier travier changed the title Am I faster than light ? Butane release container tag not yet updated to 0.23.0 Dec 5, 2024
@travier
Copy link
Member

travier commented Dec 5, 2024

Thanks for the report. The releases and stabilisation is indeed still in progress.

Unless if you are using an s390x system (unlikely given our usage numbers), there are no changes in this release for other architectures so there is no urgency to update: https://coreos.github.io/butane/upgrading-fcos/#from-version-150-to-version-160

Current FCOS stable already has ignition 2.20.0: https://fedoraproject.org/coreos/release-notes?arch=x86_64&stream=stable

@travier travier added the status/pending-upstream-release Fixed upstream. Waiting on an upstream component source code release. label Dec 5, 2024
@Nemric
Copy link
Author

Nemric commented Dec 5, 2024

Ignition v2.20.0 has now been released and the 3.5.0 config specs have been marked as stable, see https://github.com/coreos/ignition/releases/tag/v2.20.0. Because Ignition needs to go first, there is a window between where Ignition got stabilized but not yet Butane. It looks like the Butane docs page has now been updated to match the latest specs (if that's what @Nemric means) and Butane has been stabilized but not yet released.

Yes that's what I meant ^^
Well, your IDE (like vscode or sublime) that use the json schema store for bu/yaml files is up to date for v1.6.0 ;)

@Nemric
Copy link
Author

Nemric commented Dec 12, 2024

Well... release tag is now up to date :)
Did build, push, use 3.5 ignition artefacts without errors
Thanks :)

@Nemric
Copy link
Author

Nemric commented Dec 12, 2024

then close ...

@Nemric Nemric closed this as completed Dec 12, 2024
@dustymabe dustymabe removed the status/pending-upstream-release Fixed upstream. Waiting on an upstream component source code release. label Dec 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants