Skip to content

Add 4.9.7-rc.1 version #393

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
sachaudh wants to merge 2 commits into
base: master
Choose a base branch
from
Draft

Add 4.9.7-rc.1 version #393

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ed27ae5
Add 4.9.7-rc.1-0-g53da76af8b version
sachaudh May 19, 2026
7cffc68
fix: use clean 4.9.7-rc.1 tag for operator-bundle image
sachaudh May 20, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions bundles.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -268,6 +268,8 @@ images:
version: 4.9.5
- image: registry.redhat.io/advanced-cluster-security/rhacs-operator-bundle@sha256:8f2b6efc9e8be5db2e175daef5d0f95ab2bd585dc20df56d844366946dd60057
version: 4.9.6
- image: quay.io/rhacs-eng/release-operator-bundle@sha256:48a6345e40eefb7ea31bbe74cf33c8d607078e95d62eb4c0fabb433eb9ea8055
version: 4.9.7-rc.1-0-g53da76af8b
Copy link
Copy Markdown
Contributor Author

@sachaudh sachaudh May 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was a little confused why we ended up having to use4.9.7-rc.1 instead of 4.9.7-rc.1-0-g53da76af8b. The other PRs all use the shorthand 4.9.7-rc.1.

My own investigation led me to discover that a different build trigger (branch push vs tag push) causes the task to use git describe --long to avoid image tag collisions. Is that correct and is this valid?

Copy link
Copy Markdown
Contributor Author

@sachaudh sachaudh May 20, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See thread for more information: https://redhat-internal.slack.com/archives/C09KTSM25LZ/p1779216202591649

Copy link
Copy Markdown
Contributor Author

@sachaudh sachaudh May 20, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated to use the clean 4.9.7-rc.1 tag. The original long-form version (4.9.7-rc.1-0-g53da76af8b) was caused by the tag push main-on-push build failing with a SIGPIPE infra error, which cascaded into operator-bundle-on-push timing out on wait-for-main-image. The snapshot ended up being built from branch push builds instead. I re-triggered the tag push pipelines (main-on-push, operator-bundle-on-push, create-custom-snapshot) and they all succeeded, so this is now using the clean snapshot (acs-4-9--4-9-7-rc-1--20260520t175949z) and make valid-catalogs passes.

- image: registry.redhat.io/advanced-cluster-security/rhacs-operator-bundle@sha256:1b1480e72310d6ec17c4dd4368214cd940a4da230b13304f4621c5ae560f9e9e
version: 4.10.0
- image: registry.redhat.io/advanced-cluster-security/rhacs-operator-bundle@sha256:aa1984fa95a56acef9828b273563c3a552b192a5eb97f79daacd036d734a4d36
Expand Down
144 changes: 142 additions & 2 deletions catalog-bundle-object/rhacs-operator/catalog.json
View file
Open in desktop

Large diffs are not rendered by default.

Loading