redpanda-25.2/25.2.6 package update

[octo-sts]

[octo-sts]

📡 Build Failed: Network

GET https://index.docker.io/v2/redpandadata/redpanda/manifests/v25.2.6: MANIFEST_UNKNOWN: manifest unknown; unknown tag=v25.2.6

Build Details

Category	Details
Build System	melange
Failure Point	crane digest redpandadata/redpanda:${tag} command in redpanda-25.2-compat subpackage

Root Cause Analysis 🔍

The Docker registry request failed because the specified tag 'v25.2.6' does not exist in the redpandadata/redpanda repository. The build process is trying to fetch a Docker image manifest for a non-existent tag during the redpanda-25.2-compat subpackage build phase.

---

🔍 Build failure fix suggestions

Found similar build failures that have been fixed in the past and analyzed them to suggest a fix:

Similar PRs with fixes

• redpanda-25.1/25.2.1 package update #61100
• redpanda-25.1/25.2.1 package update #61100
• redpanda-25.1/25.2.1 package update #61100

Suggested Changes

File: redpanda-25.2.yaml

• version_verification at line 3 (package.version field)
  Original:

version: "25.2.6"

Replacement:

Need to verify if v25.2.6 tag exists in redpandadata/redpanda Docker registry

Content:

Check Docker Hub or use 'crane ls redpandadata/redpanda' to list available tags and find the correct version

• commit_hash_update at line 57 (git-checkout expected-commit)
  Original:

expected-commit: "e75d1e288b1463eee93a60157c168979ed865c47"

Replacement:

expected-commit: "[commit hash for correct v25.2.x tag]"

Content:

Update to the commit hash that corresponds to the actual available Docker tag version

• version_downgrade_option at line 3 (package.version field)
  Original:

version: "25.2.6"

Replacement:

version: "25.2.1"

Content:

If v25.2.6 doesn't exist, downgrade to v25.2.1 which was confirmed working in the similar fixes

Click to expand fix analysis

Analysis

The similar fixes show a consistent pattern: when Docker registry requests fail for non-existent tags (v25.2.1), the solution was to update the package version from an older version (25.1.9) to the failing version (25.2.1) and update the corresponding git commit hash. All three examples show the exact same fix - updating the version in the package definition and updating the expected-commit to match the new version's commit hash. The pattern indicates that the Docker tag exists, but the package configuration was referencing an outdated version/commit combination.

Click to expand fix explanation

Explanation

The build failure occurs because the crane tool cannot find the Docker tag 'v25.2.6' in the redpandadata/redpanda repository. Based on the similar fixes, this typically happens when the package version doesn't correspond to an actual Docker tag release. The similar fixes show that v25.2.1 exists and works correctly. The solution requires either: 1) Verifying that v25.2.6 actually exists as a Docker tag and updating the git commit hash to match, or 2) Downgrading to a known working version like v25.2.1. The git commit hash must be updated to match whichever version is used, as the current commit hash (e75d1e288b1463eee93a60157c168979ed865c47) likely corresponds to v25.2.6 which may not have a corresponding Docker image release yet.

Click to expand alternative approaches

Alternative Approaches

• Wait for the v25.2.6 Docker image to be published by the upstream maintainers before updating the package
• Use a different method to obtain the entrypoint.sh file that doesn't rely on the Docker image, such as extracting it from the source repository
• Implement a fallback mechanism in the subpackage that tries multiple version tags in descending order until one is found
• Contact the upstream Redpanda maintainers to confirm the release status of v25.2.6

---

Was this comment helpful? Please use 👍 or 👎 reactions on this comment.

[octo-sts]

superseded by #67820