Repository navigation
metalbox: drop the 2024.2 registry tarball - #1098
Merged
Merged
Conversation
ideaship
added a commit
to osism/metalbox
that referenced
this pull request
Oct 2, 2026
Stop building and publishing registry-2024.2-full.tar.bz2. This removes the check and publish jobs, their semaphore, their entries in the check, periodic-daily and post pipelines, and the vars file zuul/vars/container-images-openstack-2024.2.yml with its entry in the abstract job's files list. The tarball serves pods that run manager_version: latest with OpenStack 2024.2. 2024.2 is EOL upstream and is not offered as a fresh install. OSISM still backports security fixes to existing 2024.2 deployments, but the release variants in the MetalBox deploy guide offer only 2025.1 (latest) and stable. A nightly latest tarball for a series nobody can install fresh costs a CI slot every night, and it invites operators to pick it. Consequences, and what is deliberately left alone: - The published object registry-2024.2-full.tar.bz2 stops being refreshed and becomes an orphan. Deleting it is a separate maintainer action. - The MetalBox's own undercloud still runs 2024.2 (environments/manager/configuration.yml, images_kolla_metalbox). That is the box itself, not a pod, and is not touched. - The 2024.2 octavia export image (metalbox-mirror-octavia-image) is a separate artifact with its own consumers, and is not touched. - The artifact table in the MetalBox guide is updated in the companion change osism/osism.github.io#1098. Assisted-by: Claude:claude-opus-5.5 Signed-off-by: Roger Luethi <luethi@osism.tech>
Remove the registry-2024.2-full.tar.bz2 row from the artifact table in the MetalBox guide. osism/metalbox stops building and publishing that tarball (osism/metalbox#389): it served pods running manager_version: latest with OpenStack 2024.2, which is EOL upstream and not offered as a fresh install. The guide's release variants already offer only 2025.1 (latest) and stable. Assisted-by: Claude:claude-opus-5.5 Signed-off-by: Roger Luethi <luethi@osism.tech>
ideaship
force-pushed
the
metalbox-drop-2024.2
branch
from
October 2, 2026 11:17
dec409e to
5da45eb
Compare
✅MegaLinter analysis: Success
See detailed reports in MegaLinter artifacts Your project could benefit from a custom flavor, which would allow you to run only the linters you need, and thus improve runtime performances. (Skip this info by defining
|
berendt
pushed a commit
to osism/metalbox
that referenced
this pull request
Oct 2, 2026
Stop building and publishing registry-2024.2-full.tar.bz2. This removes the check and publish jobs, their semaphore, their entries in the check, periodic-daily and post pipelines, and the vars file zuul/vars/container-images-openstack-2024.2.yml with its entry in the abstract job's files list. The tarball serves pods that run manager_version: latest with OpenStack 2024.2. 2024.2 is EOL upstream and is not offered as a fresh install. OSISM still backports security fixes to existing 2024.2 deployments, but the release variants in the MetalBox deploy guide offer only 2025.1 (latest) and stable. A nightly latest tarball for a series nobody can install fresh costs a CI slot every night, and it invites operators to pick it. Consequences, and what is deliberately left alone: - The published object registry-2024.2-full.tar.bz2 stops being refreshed and becomes an orphan. Deleting it is a separate maintainer action. - The MetalBox's own undercloud still runs 2024.2 (environments/manager/configuration.yml, images_kolla_metalbox). That is the box itself, not a pod, and is not touched. - The 2024.2 octavia export image (metalbox-mirror-octavia-image) is a separate artifact with its own consumers, and is not touched. - The artifact table in the MetalBox guide is updated in the companion change osism/osism.github.io#1098. Assisted-by: Claude:claude-opus-5.5 Signed-off-by: Roger Luethi <luethi@osism.tech>
ideaship
marked this pull request as ready for review
October 9, 2026 16:33
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Remove the
registry-2024.2-full.tar.bz2row from the artifact table in the MetalBox guide.osism/metalbox stops building and publishing that tarball. It served pods running
manager_version: latestwith OpenStack 2024.2, which is EOL upstream and not offered as a fresh install. The guide's release variants already offer only 2025.1 (latest) and stable.Companion to:
Merge together with, or after, that PR. Until then the row describes a tarball that is still built.
🤖 Generated with Claude Code