Catalog update [alloydb-omni-operator] [v4.14,v4.12,v4.18,v4.17,v4.13,v4.16,v4.15]

[jahnavi2k]

Thanks for submitting your Operator. Please check the below list before you create your Pull Request.

New Submissions

• Are you familiar with our contribution guidelines?
• Are you familiar with our operator pipeline?
• Have you tested your Operator with all Custom Resource Definitions packaging?
• Have you tested your Operator in all supported installation modes?
• Have you considered whether you want to use semantic versioning order?
• Is your submission signed?
• Is operator icon set?

Your submission should not

• Add more than one operator bundle per PR
• Modify any operator
• Rename an operator
• Modify any files outside the above-mentioned folders
• Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

1. Description of the managed Application and where to find more information
2. Features and capabilities of your Operator and how to use it
3. Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

• Human-readable name and 1-liner description about your Operator
• Valid category name ¹
• One of the pre-defined capability levels²
• Links to the maintainer, source code and documentation
• Example templates for all Custom Resource Definitions intended to be used
• A quadratic logo

Remember that you can preview your CSV here.

--

¹ If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need

² For more information see here

[jahnavi2k]

Hi @Allda
Could you please review this?

[rh-operator-bundle-bot]

Pipeline Summary

Pipeline: operator-hosted-pipeline
PipelineRun: operator-hosted-pipeline-rundk89n
Start Time: 2025-01-03 12:41:37+00:00

Tasks

Status	Task	Start Time	Duration
✔️	get-pr-number	2025-01-03 12:41:37+00:00	7 seconds
✔️	acquire-lease	2025-01-03 12:41:50+00:00	6 seconds
✔️	set-github-started-label	2025-01-03 12:42:01+00:00	10 seconds
✔️	set-github-status-pending	2025-01-03 12:42:13+00:00	8 seconds
✔️	set-env	2025-01-03 12:42:27+00:00	8 seconds
✔️	clone-repository-base	2025-01-03 12:42:38+00:00	42 seconds
✔️	clone-repository	2025-01-03 12:42:38+00:00	36 seconds
✔️	detect-changes	2025-01-03 12:43:23+00:00	54 seconds
✔️	check-permissions	2025-01-03 12:44:19+00:00	47 seconds
✔️	set-github-pr-title	2025-01-03 12:45:09+00:00	9 seconds
✔️	read-config	2025-01-03 12:45:24+00:00	45 seconds
✔️	resolve-pr-type	2025-01-03 12:46:15+00:00	7 seconds
✔️	validate-catalog-format	2025-01-03 12:46:27+00:00	a minute
✔️	build-fragment-images	2025-01-03 12:47:35+00:00	38 seconds
✔️	content-hash	2025-01-03 12:48:23+00:00	45 seconds
✔️	certification-project-check	2025-01-03 12:49:15+00:00	47 seconds
✔️	get-organization	2025-01-03 12:50:04+00:00	49 seconds
✔️	get-pyxis-certification-data	2025-01-03 12:50:55+00:00	39 seconds
❌	static-tests	2025-01-03 12:51:39+00:00	45 seconds

Pipeline logs: https://gist.github.com/rh-operator-bundle-bot/3e05a38266eb0db9b86b490432749d61

Troubleshooting

Please refer to the troubleshooting guide.

Run /pipeline restart operator-hosted-pipeline in case of pipeline failure to restart a pipeline.

[jahnavi2k]

@Allda can you please help with the error. why does it say 'alloydb-omni-operator' is an invalid operator

[jahnavi2k]

/pipeline restart operator-hosted-pipeline

[rh-operator-bundle-bot]

Pipeline Summary

Pipeline: operator-hosted-pipeline
PipelineRun: operator-hosted-pipeline-runkxsrm
Start Time: 2025-01-03 12:59:08+00:00

Tasks

Status	Task	Start Time	Duration
✔️	get-pr-number	2025-01-03 12:59:09+00:00	9 seconds
✔️	acquire-lease	2025-01-03 12:59:26+00:00	7 seconds
✔️	set-github-started-label	2025-01-03 12:59:39+00:00	10 seconds
✔️	set-github-status-pending	2025-01-03 12:59:51+00:00	9 seconds
✔️	set-env	2025-01-03 13:00:02+00:00	17 seconds
✔️	clone-repository-base	2025-01-03 13:00:22+00:00	49 seconds
✔️	clone-repository	2025-01-03 13:00:22+00:00	45 seconds
✔️	detect-changes	2025-01-03 13:01:14+00:00	51 seconds
✔️	check-permissions	2025-01-03 13:02:07+00:00	40 seconds
✔️	set-github-pr-title	2025-01-03 13:02:50+00:00	8 seconds
✔️	read-config	2025-01-03 13:03:01+00:00	43 seconds
✔️	resolve-pr-type	2025-01-03 13:03:47+00:00	8 seconds
✔️	validate-catalog-format	2025-01-03 13:03:58+00:00	a minute
✔️	build-fragment-images	2025-01-03 13:05:11+00:00	13 seconds
✔️	content-hash	2025-01-03 13:05:26+00:00	49 seconds
✔️	certification-project-check	2025-01-03 13:06:17+00:00	38 seconds
✔️	get-organization	2025-01-03 13:06:58+00:00	38 seconds
✔️	get-pyxis-certification-data	2025-01-03 13:07:38+00:00	40 seconds
❌	static-tests	2025-01-03 13:08:19+00:00	14 seconds

Pipeline logs: https://gist.github.com/rh-operator-bundle-bot/2e7dff2d5d959bc5e563b83eba8d0801

Troubleshooting

Please refer to the troubleshooting guide.

Run /pipeline restart operator-hosted-pipeline in case of pipeline failure to restart a pipeline.

[Allda]

@jahnavi2k There seems to be some bug in the bundle removal code. Could you please keep files inside the operators and only delete files inside the catalogs directory? It will still remove the operator from OpenShift indexes as you wish.

[jahnavi2k]

Hi @Allda
can you please check it now?

[rh-operator-bundle-bot]

Static test results

Status	Check	Message
⚠️	check_ci_upgrade_graph	The 'updateGraph' option is missing in ci.yaml. The default upgrade graph 'replaces-mode' will be used.

[Allda]

Looks good. Let's wait for the automated pipeline to merge it and remove it from OpenShift.

[rh-operator-bundle-bot]

Pipeline Summary

Pipeline: operator-hosted-pipeline
PipelineRun: operator-hosted-pipeline-run75pkz
Start Time: 2025-01-03 13:20:56+00:00

Tasks

Status	Task	Start Time	Duration
✔️	get-pr-number	2025-01-03 13:20:56+00:00	7 seconds
✔️	acquire-lease	2025-01-03 13:21:08+00:00	7 seconds
✔️	set-github-started-label	2025-01-03 13:21:19+00:00	9 seconds
✔️	set-github-status-pending	2025-01-03 13:21:30+00:00	9 seconds
✔️	set-env	2025-01-03 13:21:43+00:00	10 seconds
✔️	clone-repository-base	2025-01-03 13:21:57+00:00	47 seconds
✔️	clone-repository	2025-01-03 13:21:57+00:00	48 seconds
✔️	detect-changes	2025-01-03 13:22:48+00:00	54 seconds
✔️	check-permissions	2025-01-03 13:23:43+00:00	42 seconds
✔️	set-github-pr-title	2025-01-03 13:24:26+00:00	9 seconds
✔️	read-config	2025-01-03 13:24:38+00:00	49 seconds
✔️	resolve-pr-type	2025-01-03 13:25:30+00:00	8 seconds
✔️	validate-catalog-format	2025-01-03 13:25:41+00:00	a minute
✔️	build-fragment-images	2025-01-03 13:26:56+00:00	12 seconds
✔️	content-hash	2025-01-03 13:27:12+00:00	47 seconds
✔️	certification-project-check	2025-01-03 13:28:02+00:00	48 seconds
✔️	get-organization	2025-01-03 13:28:53+00:00	48 seconds
✔️	get-pyxis-certification-data	2025-01-03 13:29:43+00:00	40 seconds
✔️	static-tests	2025-01-03 13:30:24+00:00	13 seconds
✔️	static-tests-results	2025-01-03 13:30:39+00:00	20 seconds
✔️	merge-registry-credentials	2025-01-03 13:31:01+00:00	16 seconds
✔️	digest-pinning	2025-01-03 13:31:19+00:00	49 seconds
✔️	verify-pinned-digest	2025-01-03 13:32:10+00:00	7 seconds
✔️	dockerfile-creation	2025-01-03 13:32:20+00:00	45 seconds
✔️	build-bundle	2025-01-03 13:33:06+00:00	13 seconds
✔️	get-supported-versions	2025-01-03 13:33:20+00:00	14 seconds
✔️	build-fbc-index-images	2025-01-03 13:33:34+00:00	14 minutes
✔️	get-ci-results-attempt	2025-01-03 13:47:56+00:00	9 seconds
✔️	preflight-trigger	2025-01-03 13:48:06+00:00	24 seconds
✔️	get-ci-results	2025-01-03 13:48:31+00:00	20 seconds
✔️	link-pull-request-with-open-status	2025-01-03 13:48:52+00:00	6 seconds
✔️	merge-pr	2025-01-03 13:49:00+00:00	51 seconds
✔️	link-pull-request-with-merged-status	2025-01-03 13:49:52+00:00	7 seconds

Pipeline logs: https://gist.github.com/rh-operator-bundle-bot/ea5544b5f9e94ca898e8d56205b32474

Troubleshooting

Please refer to the troubleshooting guide.

Run /pipeline restart operator-hosted-pipeline in case of pipeline failure to restart a pipeline.

[rh-operator-bundle-bot]

Pipeline Summary

Pipeline: operator-release-pipeline
PipelineRun: operator-release-pipeline-run6vnsv
Start Time: 2025-01-03 13:49:55+00:00

Tasks

Status	Task	Start Time	Duration
✔️	set-github-started-label	2025-01-03 13:50:02+00:00	8 seconds
✔️	set-github-status-pending	2025-01-03 13:50:16+00:00	9 seconds
✔️	set-env	2025-01-03 13:50:26+00:00	13 seconds
✔️	clone-repository	2025-01-03 13:50:40+00:00	37 seconds
✔️	clone-repository-base	2025-01-03 13:50:41+00:00	40 seconds
✔️	detect-changes	2025-01-03 13:51:22+00:00	58 seconds
✔️	read-config	2025-01-03 13:52:20+00:00	12 seconds
✔️	resolve-pr-type	2025-01-03 13:52:32+00:00	8 seconds
✔️	content-hash	2025-01-03 13:52:41+00:00	46 seconds
✔️	certification-project-check	2025-01-03 13:53:28+00:00	11 seconds
✔️	get-organization	2025-01-03 13:53:39+00:00	11 seconds
✔️	get-pyxis-certification-data	2025-01-03 13:53:50+00:00	13 seconds
✔️	copy-bundle-image-to-released-registry	2025-01-03 13:54:04+00:00	8 seconds
✔️	get-supported-versions	2025-01-03 13:54:12+00:00	38 seconds
✔️	build-fragment-images	2025-01-03 13:54:50+00:00	11 seconds
✔️	acquire-lease	2025-01-03 13:55:01+00:00	8 seconds
✔️	build-fbc-index-images	2025-01-03 13:55:09+00:00	9 minutes
✔️	decide-index-paths	2025-01-03 14:04:11+00:00	9 seconds
✔️	get-manifest-digests	2025-01-03 14:04:20+00:00	14 seconds
✔️	request-signature	2025-01-03 14:04:34+00:00	44 seconds
✔️	upload-signature	2025-01-03 14:05:18+00:00	15 seconds
✔️	publish-to-index	2025-01-03 14:05:33+00:00	7 minutes

Pipeline logs: https://gist.github.com/rh-operator-bundle-bot/9c293adaa69ec5330d54676cdf16430f

Release info

Updated indices:

• registry.redhat.io/redhat/community-operator-index:v4.12
• registry.redhat.io/redhat/community-operator-index:v4.13
• registry.redhat.io/redhat/community-operator-index:v4.14
• registry.redhat.io/redhat/community-operator-index:v4.15
• registry.redhat.io/redhat/community-operator-index:v4.16
• registry.redhat.io/redhat/community-operator-index:v4.17
• registry.redhat.io/redhat/community-operator-index:v4.18

Troubleshooting

Please refer to the troubleshooting guide.

Run /pipeline restart operator-release-pipeline in case of pipeline failure to restart a pipeline.

[jahnavi2k]

Hi @Allda
We have to make a few changes to the CSV before the final release. Does the following procedure look good to you:

1. Raise a PR containing the changes in the CSV.
2. Raise another PR adding our operator back to the catalogs to release it.
   This should re-release our operator on OpenShift, right?