Skip to content

metalbox: drop the 2024.2 registry tarball - #1098

Merged
berendt merged 1 commit into
mainfrom
metalbox-drop-2024.2
Oct 9, 2026
Merged

berendt merged 1 commit into
mainfrom
metalbox-drop-2024.2

Conversation

@ideaship

@ideaship ideaship commented Oct 2, 2026

Copy link
Copy Markdown
Contributor

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. 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.

Companion to:

Merge together with, or after, that PR. Until then the row describes a tarball that is still built.

🤖 Generated with Claude Code

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
ideaship force-pushed the metalbox-drop-2024.2 branch from dec409e to 5da45eb Compare October 2, 2026 11:17
@github-actions

github-actions Bot commented Oct 2, 2026 •

Copy link
Copy Markdown

✅MegaLinter analysis: Success

Descriptor Linter Files Fixed Errors Max errors Warnings Elapsed time
✅ ACTION actionlint 5 0 0 0.03s
✅ JSON jsonlint 4 0 0 0.08s
✅ JSON prettier 4 0 0 0.22s
✅ JSON v8r 4 0 0 7.55s
✅ MARKDOWN markdownlint 171 0 0 1.87s
✅ MARKDOWN markdown-table-formatter 171 0 0 0.3s
✅ REPOSITORY betterleaks yes no no 0.59s
✅ REPOSITORY checkov yes no no 13.22s
✅ REPOSITORY git_diff yes no no 0.06s
✅ REPOSITORY secretlint yes no no 1.13s
✅ REPOSITORY trufflehog yes no no 3.56s
✅ SPELL codespell 181 0 0 0.39s
✅ SPELL lychee 181 0 0 11.1s
✅ YAML prettier 6 0 0 0.26s
✅ YAML v8r 6 0 0 5.51s
✅ YAML yamllint 6 0 0 0.34s

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 FLAVOR_SUGGESTIONS: false)

  • Documentation: Custom Flavors
  • Command: npx mega-linter-runner@10.1.0 --custom-flavor-setup --custom-flavor-linters ACTION_ACTIONLINT,JSON_JSONLINT,JSON_V8R,JSON_PRETTIER,MARKDOWN_MARKDOWNLINT,MARKDOWN_MARKDOWN_TABLE_FORMATTER,REPOSITORY_CHECKOV,REPOSITORY_GIT_DIFF,REPOSITORY_BETTERLEAKS,REPOSITORY_SECRETLINT,REPOSITORY_TRUFFLEHOG,SPELL_LYCHEE,SPELL_CODESPELL,YAML_PRETTIER,YAML_YAMLLINT,YAML_V8R

MegaLinter is provided by OX Security
Show us your support by starring ⭐ the repository

@ideaship ideaship self-assigned this Oct 2, 2026
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
ideaship marked this pull request as ready for review October 9, 2026 16:33
@ideaship
ideaship requested a review from berendt October 9, 2026 16:33
@berendt
berendt merged commit a2b3b76 into main Oct 9, 2026
3 checks passed
@berendt
berendt deleted the metalbox-drop-2024.2 branch October 9, 2026 17:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

3 participants