Repository navigation
Drop allowlist entries for now-pinned kolla images - #2817
Merged
Merged
Conversation
kolla_version_chain_upstream flags a kolla docker/ service with no versions['<key>'] line in container-image-kolla-ansible's template. httpd was allowlisted as "apache supporting image, not independently pinned". That reason was wrong for releases. kolla-ansible runs httpd for keystone-httpd, ironic-http and the Let's Encrypt webserver, and without a pin of its own their tags fell back to the series or to the parent service's version. OSISM 11.0.0 requests three httpd tags that do not exist; the build pushed httpd:2.4.58.20261008. container-image-kolla-ansible now renders kolla_httpd_version from versions['httpd'], so the plugin no longer reports httpd and the entry would fail the run as stale. Remove it. Land this together with the container-image-kolla-ansible change: before it, httpd is reported as unpinned; after it without this change, the entry is reported as stale. Checked locally with check-drift.py --group kolla over the container-images-kolla, container-image-kolla-ansible, osism/defaults and osism/release changes: no actionable findings and no stale entries. Assisted-by: Claude:claude-opus-5-5 Signed-off-by: Roger Luethi <luethi@osism.tech>
kolla_version_chain_upstream allowlisted ovsdpdk as "openvswitch dpdk variant, no distinct version key". That was wrong for releases: osism/defaults reads kolla_ovsdpdk_version, which nothing defined, so the ovsdpdk-db and ovsdpdk-vswitchd tags fell back to the series. On OSISM 11.0.0 both request 2026.1, which does not exist; the build pushed 3.7.1.20261008. container-image-kolla-ansible now renders kolla_ovsdpdk_version from versions['ovsdpdk'], so the plugin no longer reports ovsdpdk and the entry would fail the run as stale. Remove it, together with the container-image-kolla-ansible change. Assisted-by: Claude:claude-opus-5-5 Signed-off-by: Roger Luethi <luethi@osism.tech>
kolla_version_chain_upstream allowlisted hacluster as "pacemaker/ corosync variant, no distinct version key". That was wrong for releases: osism/defaults reads kolla_hacluster_version, which nothing defined, so the corosync, pacemaker and pacemaker-remote tags fell back to the series. On OSISM 11.0.0 all three request 2026.1, which does not exist. container-image-kolla-ansible now renders kolla_hacluster_version and kolla_hacluster_corosync_version, so the plugin no longer reports hacluster and the entry would fail the run as stale. Remove it, together with the container-image-kolla-ansible change. Assisted-by: Claude:claude-opus-5-5 Signed-off-by: Roger Luethi <luethi@osism.tech>
This was referenced Oct 10, 2026
ideaship
marked this pull request as ready for review
October 10, 2026 08:10
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.
Important
Part of a four-repo change. Start with osism/issues#1462: it explains why four repos are involved, what each PR fixes, and the merge order.
kolla_version_chain_upstreamallowlistedhttpd,haclusterandovsdpdkas having no version of their own. That was wrong for releases: on OSISM 11.0.0 their containers request tags that do not exist. The container-image-kolla-ansible PR adds a version variable for each, so the plugin no longer reports them and the entries would fail the drift run as stale. One commit per entry.Merge together with the container-image-kolla-ansible PR. Either one alone turns the kolla drift group red: the images reported as unpinned, or the entries reported as stale. Checked locally with
check-drift.py --group kollaover all four branches: no actionable findings, no stale entries.Related:
🤖 Generated with Claude Code