USHIFT-6767: Validate GitOps RPM repo availability before using version

[agullon]

Summary

• Adds a repo_provides_pkg() check against gitops-{version}-for-rhel-9-{ARCH}-rpms to verify the package is actually available before returning the version
• Falls back to the next compatible version if the repo is not yet available

[openshift-ci-robot]

@agullon: This pull request references USHIFT-6767 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Summary

• Fixes bootc image build failures caused by get_gitops_version() returning a GitOps version (e.g., 1.20) whose RPM repo doesn't exist yet on cdn.redhat.com (403 Forbidden)
• Adds a repo_provides_pkg() check against gitops-{version}-for-rhel-9-{ARCH}-rpms to verify the package is actually available before returning the version
• Falls back to the next compatible version if the repo is not yet available

Test plan

• Run generate_common_versions.py on a RHEL machine with RHSM — verify it falls back to GitOps 1.19 instead of 1.20
• Verify bootc-periodic CI jobs pass with the regenerated common_versions.sh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@agullon: This pull request references USHIFT-6767 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Summary

• Adds a repo_provides_pkg() check against gitops-{version}-for-rhel-9-{ARCH}-rpms to verify the package is actually available before returning the version
• Falls back to the next compatible version if the repo is not yet available

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 1e479606-7d89-471e-855f-8cb7156efb6a

📥 Commits

Reviewing files that changed from the base of the PR and between 687d05e and d7d3199.

📒 Files selected for processing (1)

• test/bin/pyutils/generate_common_versions.py

---

Walkthrough

Modified get_gitops_version() to validate package availability in repositories before accepting a GitOps version match. The function now constructs repository identifiers, checks for the presence of the microshift-gitops package, and continues searching if the package is unavailable.

Changes

Cohort / File(s)	Summary
GitOps Version Validation test/bin/pyutils/generate_common_versions.py	Added package availability verification to get_gitops_version(). Now constructs repository identifiers and validates microshift-gitops package presence before returning a compatible GitOps version.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[pmtk]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: agullon, pmtk

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [agullon,pmtk]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[agullon]

/retest

[agullon]

/verified by CI

[openshift-ci-robot]

@agullon: This PR has been marked as verified by CI.

Details

In response to this:

/verified by CI

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[agullon]

/retest

[agullon]

/retest

[openshift-ci]

@agullon: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.