operator ibm-block-csi-operator-community (1.11.2)

[kasserater]

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

[rh-operator-bundle-bot]

Author of the PR is not listed as one of the reviewers in ci.yaml.
Please review the PR and approve it with `/lgtm` comment.
@ArbelNathan, @oriyarde, @matancarmeli7

Consider adding author of the PR to the ci.yaml file if you want automated approval for a followup submissions.

[rh-operator-bundle-bot]

Static test results

Status	Check	Message
❌	check_api_version_constraints	OCP version(s) 4.13 conflict with minKubeVersion=1.27.0
⚠️	check_osdk_bundle_validate_operator_framework	Warning: Value ibm-block-csi-operator.v1.11.2: CSV contains permissions to create CRD. An Operator shouldn't deploy or manage other operators (such patterns are known as meta or super operators or include CRDs in its Operands). It's the Operator Lifecycle Manager's job to manage the deployment and lifecycle of operators. Please, review the design of your solution and if you should not be using Dependency Resolution from OLM instead. More info: https://sdk.operatorframework.io/docs/best-practices/common-recommendation/
❌	check_replaces_availability	Replaces bundle Bundle(ibm-block-csi-operator-community/1.11.1) ['4.12', '4.13'] does not support the same OCP versions as bundle Bundle(ibm-block-csi-operator-community/1.11.2) ['4.13', '4.14', '4.15']. In order to fix this issue, align the OCP version range to match the range of the replaced bundle. This can be done by setting the com.redhat.openshift.versions annotation in the metadata/annotations.yaml file. Bundle(ibm-block-csi-operator-community/1.11.2) - v4.13-v4.15 Bundle(ibm-block-csi-operator-community/1.11.1) - v4.10-v4.13
⚠️	check_operator_name	Bundle package annotation is set to 'ibm-block-csi-operator-community'. Expected value is 'ibm-block-csi-operator' based on the CSV name. To fix this issue define the annotation in 'metadata/annotations.yaml' file that matches the CSV name.

[rh-operator-bundle-bot]

Pipeline Summary

Pipeline: operator-hosted-pipeline
PipelineRun: operator-hosted-pipeline-runvgscv
Start Time: 2024-05-15 09:30:46+00:00

Tasks

Status	Task	Start Time	Duration
✔️	get-pr-number	2024-05-15 09:30:46+00:00	7 seconds
✔️	acquire-lease	2024-05-15 09:30:57+00:00	7 seconds
✔️	set-github-started-label	2024-05-15 09:31:08+00:00	9 seconds
✔️	set-github-status-pending	2024-05-15 09:31:18+00:00	9 seconds
✔️	set-env	2024-05-15 09:31:31+00:00	7 seconds
✔️	clone-repository	2024-05-15 09:31:41+00:00	37 seconds
✔️	clone-repository-base	2024-05-15 09:31:42+00:00	37 seconds
✔️	detect-changes	2024-05-15 09:32:22+00:00	54 seconds
✔️	check-permissions	2024-05-15 09:33:19+00:00	34 seconds
✔️	set-github-pr-title	2024-05-15 09:33:55+00:00	8 seconds
✔️	read-config	2024-05-15 09:34:04+00:00	44 seconds
✔️	apply-test-waivers	2024-05-15 09:34:50+00:00	12 seconds
✔️	content-hash	2024-05-15 09:35:03+00:00	10 seconds
✔️	certification-project-check	2024-05-15 09:35:16+00:00	38 seconds
✔️	get-organization	2024-05-15 09:35:58+00:00	38 seconds
✔️	get-pyxis-certification-data	2024-05-15 09:36:38+00:00	40 seconds
✔️	static-tests	2024-05-15 09:37:21+00:00	44 seconds
✔️	yaml-lint	2024-05-15 09:37:21+00:00	37 seconds
✔️	merge-registry-credentials	2024-05-15 09:37:22+00:00	16 seconds
✔️	digest-pinning	2024-05-15 09:37:40+00:00	29 seconds
❌	static-tests-results	2024-05-15 09:38:08+00:00	22 seconds
✔️	verify-pinned-digest	2024-05-15 09:38:12+00:00	6 seconds

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

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]

Author of the PR is not listed as one of the reviewers in ci.yaml.
Please review the PR and approve it with `/lgtm` comment.
@ArbelNathan, @oriyarde, @matancarmeli7

Consider adding author of the PR to the ci.yaml file if you want automated approval for a followup submissions.

[ArbelNathan]

/lgtm

[openshift-ci]

@ArbelNathan: changing LGTM is restricted to collaborators

In response to this:

/lgtm

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.

[rh-operator-bundle-bot]

Static test results

Status	Check	Message
❌	check_api_version_constraints	OCP version(s) 4.13 conflict with minKubeVersion=1.27.0
⚠️	check_osdk_bundle_validate_operator_framework	Warning: Value ibm-block-csi-operator.v1.11.2: CSV contains permissions to create CRD. An Operator shouldn't deploy or manage other operators (such patterns are known as meta or super operators or include CRDs in its Operands). It's the Operator Lifecycle Manager's job to manage the deployment and lifecycle of operators. Please, review the design of your solution and if you should not be using Dependency Resolution from OLM instead. More info: https://sdk.operatorframework.io/docs/best-practices/common-recommendation/
❌	check_replaces_availability	Replaces bundle Bundle(ibm-block-csi-operator-community/1.11.1) ['4.12', '4.13'] does not support the same OCP versions as bundle Bundle(ibm-block-csi-operator-community/1.11.2) ['4.13', '4.14', '4.15']. In order to fix this issue, align the OCP version range to match the range of the replaced bundle. This can be done by setting the com.redhat.openshift.versions annotation in the metadata/annotations.yaml file. Bundle(ibm-block-csi-operator-community/1.11.2) - v4.13-v4.15 Bundle(ibm-block-csi-operator-community/1.11.1) - v4.10-v4.13
⚠️	check_operator_name	Bundle package annotation is set to 'ibm-block-csi-operator-community'. Expected value is 'ibm-block-csi-operator' based on the CSV name. To fix this issue define the annotation in 'metadata/annotations.yaml' file that matches the CSV name.

[rh-operator-bundle-bot]

Pipeline Summary

Pipeline: operator-hosted-pipeline
PipelineRun: operator-hosted-pipeline-runnxmv4
Start Time: 2024-05-15 09:31:54+00:00

Tasks

Status	Task	Start Time	Duration
✔️	get-pr-number	2024-05-15 09:31:55+00:00	7 seconds
✔️	acquire-lease	2024-05-15 09:32:09+00:00	6 minutes
✔️	set-github-started-label	2024-05-15 09:38:44+00:00	9 seconds
✔️	set-github-status-pending	2024-05-15 09:38:55+00:00	8 seconds
✔️	set-env	2024-05-15 09:39:09+00:00	8 seconds
✔️	clone-repository-base	2024-05-15 09:39:25+00:00	34 seconds
✔️	clone-repository	2024-05-15 09:39:25+00:00	34 seconds
✔️	detect-changes	2024-05-15 09:40:01+00:00	54 seconds
✔️	check-permissions	2024-05-15 09:40:58+00:00	35 seconds
✔️	set-github-pr-title	2024-05-15 09:41:36+00:00	7 seconds
✔️	read-config	2024-05-15 09:41:47+00:00	35 seconds
✔️	apply-test-waivers	2024-05-15 09:42:25+00:00	40 seconds
✔️	content-hash	2024-05-15 09:43:07+00:00	35 seconds
✔️	certification-project-check	2024-05-15 09:43:46+00:00	37 seconds
✔️	get-organization	2024-05-15 09:44:27+00:00	37 seconds
✔️	get-pyxis-certification-data	2024-05-15 09:45:07+00:00	40 seconds
✔️	static-tests	2024-05-15 09:45:50+00:00	47 seconds
✔️	yaml-lint	2024-05-15 09:45:50+00:00	37 seconds
✔️	merge-registry-credentials	2024-05-15 09:45:51+00:00	15 seconds
✔️	digest-pinning	2024-05-15 09:46:08+00:00	26 seconds
✔️	verify-pinned-digest	2024-05-15 09:46:37+00:00	7 seconds
❌	static-tests-results	2024-05-15 09:46:39+00:00	19 seconds

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

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]

Author of the PR is not listed as one of the reviewers in ci.yaml.
Please review the PR and approve it with `/lgtm` comment.
@ArbelNathan, @oriyarde, @matancarmeli7

Consider adding author of the PR to the ci.yaml file if you want automated approval for a followup submissions.

[kasserater]

/lgtm

[openshift-ci]

@kasserater: you cannot LGTM your own PR.

In response to this:

/lgtm

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.

[csiblock]

/lgtm

[openshift-ci]

@csiblock: changing LGTM is restricted to collaborators

In response to this:

/lgtm

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.

[rh-operator-bundle-bot]

Static test results

Status	Check	Message
⚠️	check_osdk_bundle_validate_operator_framework	Warning: Value ibm-block-csi-operator.v1.11.2: CSV contains permissions to create CRD. An Operator shouldn't deploy or manage other operators (such patterns are known as meta or super operators or include CRDs in its Operands). It's the Operator Lifecycle Manager's job to manage the deployment and lifecycle of operators. Please, review the design of your solution and if you should not be using Dependency Resolution from OLM instead. More info: https://sdk.operatorframework.io/docs/best-practices/common-recommendation/
❌	check_replaces_availability	Replaces bundle Bundle(ibm-block-csi-operator-community/1.11.1) ['4.12', '4.13'] does not support the same OCP versions as bundle Bundle(ibm-block-csi-operator-community/1.11.2) ['4.13', '4.14', '4.15']. In order to fix this issue, align the OCP version range to match the range of the replaced bundle. This can be done by setting the com.redhat.openshift.versions annotation in the metadata/annotations.yaml file. Bundle(ibm-block-csi-operator-community/1.11.2) - v4.13-v4.15 Bundle(ibm-block-csi-operator-community/1.11.1) - v4.10-v4.13
⚠️	check_operator_name	Bundle package annotation is set to 'ibm-block-csi-operator-community'. Expected value is 'ibm-block-csi-operator' based on the CSV name. To fix this issue define the annotation in 'metadata/annotations.yaml' file that matches the CSV name.

[rh-operator-bundle-bot]

Author of the PR is not listed as one of the reviewers in ci.yaml.
Please review the PR and approve it with `/lgtm` comment.
@ArbelNathan, @oriyarde, @matancarmeli7

Consider adding author of the PR to the ci.yaml file if you want automated approval for a followup submissions.

[kasserater]

@jfrancin please note that @ArbelNathan already attempted to mark with /lgtm flag last week
#4542 (comment)

[rh-operator-bundle-bot]

Static test results

Status	Check	Message
⚠️	check_osdk_bundle_validate_operator_framework	Warning: Value ibm-block-csi-operator.v1.11.2: CSV contains permissions to create CRD. An Operator shouldn't deploy or manage other operators (such patterns are known as meta or super operators or include CRDs in its Operands). It's the Operator Lifecycle Manager's job to manage the deployment and lifecycle of operators. Please, review the design of your solution and if you should not be using Dependency Resolution from OLM instead. More info: https://sdk.operatorframework.io/docs/best-practices/common-recommendation/

[rh-operator-bundle-bot]

Pipeline Summary

Pipeline: operator-hosted-pipeline
PipelineRun: operator-hosted-pipeline-rung9b67
Start Time: 2024-05-22 18:44:30+00:00

Tasks

Status	Task	Start Time	Duration
✔️	get-pr-number	2024-05-22 18:44:31+00:00	7 seconds
✔️	acquire-lease	2024-05-22 18:44:42+00:00	7 seconds
✔️	set-github-started-label	2024-05-22 18:44:53+00:00	11 seconds
✔️	set-github-status-pending	2024-05-22 18:45:06+00:00	8 seconds
✔️	set-env	2024-05-22 18:45:16+00:00	6 seconds
✔️	clone-repository	2024-05-22 18:45:26+00:00	30 seconds
✔️	clone-repository-base	2024-05-22 18:45:27+00:00	26 seconds
✔️	detect-changes	2024-05-22 18:45:59+00:00	33 seconds
✔️	check-permissions	2024-05-22 18:46:36+00:00	36 seconds
✔️	set-github-pr-title	2024-05-22 18:47:15+00:00	6 seconds
✔️	read-config	2024-05-22 18:47:24+00:00	36 seconds
✔️	apply-test-waivers	2024-05-22 18:48:03+00:00	28 seconds
✔️	content-hash	2024-05-22 18:48:35+00:00	37 seconds
✔️	certification-project-check	2024-05-22 18:49:15+00:00	38 seconds
✔️	get-organization	2024-05-22 18:49:56+00:00	36 seconds
✔️	get-pyxis-certification-data	2024-05-22 18:50:35+00:00	31 seconds
✔️	yaml-lint	2024-05-22 18:51:09+00:00	38 seconds
✔️	static-tests	2024-05-22 18:51:09+00:00	40 seconds
✔️	merge-registry-credentials	2024-05-22 18:51:10+00:00	15 seconds
✔️	digest-pinning	2024-05-22 18:51:27+00:00	45 seconds
✔️	static-tests-results	2024-05-22 18:51:52+00:00	24 seconds
✔️	verify-pinned-digest	2024-05-22 18:52:14+00:00	7 seconds
✔️	dockerfile-creation	2024-05-22 18:52:22+00:00	40 seconds
✔️	build-bundle	2024-05-22 18:53:03+00:00	39 seconds
✔️	make-bundle-repo-public	2024-05-22 18:53:42+00:00	8 seconds
✔️	get-supported-versions	2024-05-22 18:53:51+00:00	40 seconds
❌	add-bundle-to-index	2024-05-22 18:54:31+00:00	2 minutes

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

Troubleshooting

Please refer to the troubleshooting guide.

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

[kasserater]

i don't understand the error now

[add-bundle-to-index : add-bundle-to-index] 2024-05-22 18:56:52,888 [operator-cert] ERROR IIB build failed: 732773
[add-bundle-to-index : add-bundle-to-index] 2024-05-22 18:56:52,889 [operator-cert] INFO Reason: Failed to add the bundles to the index image: Invalid bundle ibm-block-csi-operator.v1.11.2, replaces nonexistent bundle ibm-block-csi-operator.v1.11.1

but 1.11.1 indeed exists, as per #2588

[jfrancin]

1.11.1 does indeed exist. But only in the v4.13 bundle index. It doesn't exist in the OperatorHubs for RHOCP 4.14 and 4.15.

The 1.11.1 version's annotations.yaml file contains: com.redhat.openshift.versions="v4.10-v4.13".
The 1.11.2 version's annotations.yaml file contains: com.redhat.openshift.versions="v4.13-v4.15".

Since the 1.11.1, the version being replaced, does not exist in 4.14 or 4.15, the replaces directive cannot be satisfied, as the precursor version must exist in every version's operatorHub/bundle index. You cannot use replaces in an operator bundle which supports a wider range of versions than the one being replaced.

Instead, change the replaces: ibm-block-csi-operator.v1.11.1 to: a skips block:

spec:
  [...]
  version: 1.11.2
  skips: 
     - ibm-block-csi-operator.v1.11.1
  [...]

and then run /pipeline restart operator-hosted-pipeline in a comment by itself.

[rh-operator-bundle-bot]

Author of the PR is not listed as one of the reviewers in ci.yaml.
Please review the PR and approve it with `/lgtm` comment.
@ArbelNathan, @oriyarde, @matancarmeli7

Consider adding author of the PR to the ci.yaml file if you want automated approval for a followup submissions.

[rh-operator-bundle-bot]

Static test results

Status	Check	Message
⚠️	check_osdk_bundle_validate_operator_framework	Warning: Value ibm-block-csi-operator.v1.11.2: CSV contains permissions to create CRD. An Operator shouldn't deploy or manage other operators (such patterns are known as meta or super operators or include CRDs in its Operands). It's the Operator Lifecycle Manager's job to manage the deployment and lifecycle of operators. Please, review the design of your solution and if you should not be using Dependency Resolution from OLM instead. More info: https://sdk.operatorframework.io/docs/best-practices/common-recommendation/

[rh-operator-bundle-bot]

Test artifacts: https://gist.github.com/rh-operator-bundle-bot/136c965cb5530210a7b5c83a8dff0873

[rh-operator-bundle-bot]

Operator bundle PR has been approved!

[rh-operator-bundle-bot]

Pipeline Summary

Pipeline: operator-hosted-pipeline
PipelineRun: operator-hosted-pipeline-runvcb25
Start Time: 2024-05-23 11:43:36+00:00

Tasks

Status	Task	Start Time	Duration
✔️	get-pr-number	2024-05-23 11:43:38+00:00	7 seconds
✔️	acquire-lease	2024-05-23 11:43:48+00:00	8 seconds
✔️	set-github-started-label	2024-05-23 11:43:59+00:00	10 seconds
✔️	set-github-status-pending	2024-05-23 11:44:12+00:00	8 seconds
✔️	set-env	2024-05-23 11:44:24+00:00	7 seconds
✔️	clone-repository-base	2024-05-23 11:44:34+00:00	33 seconds
✔️	clone-repository	2024-05-23 11:44:34+00:00	32 seconds
✔️	detect-changes	2024-05-23 11:45:10+00:00	40 seconds
✔️	check-permissions	2024-05-23 11:45:53+00:00	37 seconds
✔️	set-github-pr-title	2024-05-23 11:46:33+00:00	8 seconds
✔️	read-config	2024-05-23 11:46:44+00:00	35 seconds
✔️	apply-test-waivers	2024-05-23 11:47:22+00:00	39 seconds
✔️	content-hash	2024-05-23 11:48:03+00:00	37 seconds
✔️	certification-project-check	2024-05-23 11:48:43+00:00	38 seconds
✔️	get-organization	2024-05-23 11:49:24+00:00	37 seconds
✔️	get-pyxis-certification-data	2024-05-23 11:50:05+00:00	41 seconds
✔️	yaml-lint	2024-05-23 11:50:48+00:00	41 seconds
✔️	static-tests	2024-05-23 11:50:48+00:00	41 seconds
✔️	merge-registry-credentials	2024-05-23 11:50:49+00:00	16 seconds
✔️	digest-pinning	2024-05-23 11:51:07+00:00	27 seconds
✔️	static-tests-results	2024-05-23 11:51:30+00:00	13 seconds
✔️	verify-pinned-digest	2024-05-23 11:51:37+00:00	7 seconds
✔️	dockerfile-creation	2024-05-23 11:51:47+00:00	44 seconds
✔️	build-bundle	2024-05-23 11:52:31+00:00	15 seconds
✔️	make-bundle-repo-public	2024-05-23 11:52:46+00:00	7 seconds
✔️	get-supported-versions	2024-05-23 11:52:54+00:00	34 seconds
✔️	add-bundle-to-index	2024-05-23 11:53:28+00:00	7 minutes
✔️	make-index-repo-public	2024-05-23 12:01:03+00:00	6 seconds
✔️	get-ci-results-attempt	2024-05-23 12:01:10+00:00	15 seconds
✔️	preflight-trigger	2024-05-23 12:01:25+00:00	14 minutes
✔️	evaluate-preflight-result	2024-05-23 12:15:54+00:00	34 seconds
✔️	get-ci-results	2024-05-23 12:16:29+00:00	9 seconds
✔️	link-pull-request-with-open-status	2024-05-23 12:16:38+00:00	5 seconds
✔️	merge-pr	2024-05-23 12:16:44+00:00	37 seconds
✔️	link-pull-request-with-merged-status	2024-05-23 12:17:22+00:00	6 seconds

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

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-runwctkn
Start Time: 2024-05-23 12:17:24+00:00

Tasks

Status	Task	Start Time	Duration
✔️	set-github-started-label	2024-05-23 12:17:29+00:00	9 seconds
✔️	set-github-status-pending	2024-05-23 12:17:43+00:00	8 seconds
✔️	set-env	2024-05-23 12:17:52+00:00	7 seconds
✔️	clone-repository-base	2024-05-23 12:18:00+00:00	28 seconds
✔️	clone-repository	2024-05-23 12:18:00+00:00	33 seconds
✔️	detect-changes	2024-05-23 12:18:33+00:00	57 seconds
✔️	read-config	2024-05-23 12:19:30+00:00	55 seconds
✔️	content-hash	2024-05-23 12:20:28+00:00	44 seconds
✔️	certification-project-check	2024-05-23 12:21:14+00:00	35 seconds
✔️	get-organization	2024-05-23 12:21:52+00:00	37 seconds
✔️	get-pyxis-certification-data	2024-05-23 12:22:33+00:00	40 seconds
✔️	copy-bundle-image-to-released-registry	2024-05-23 12:23:15+00:00	7 seconds
✔️	get-supported-versions	2024-05-23 12:23:22+00:00	42 seconds
✔️	acquire-lease	2024-05-23 12:24:06+00:00	8 seconds
✔️	add-bundle-to-index	2024-05-23 12:24:16+00:00	20 minutes
✔️	get-manifest-digests	2024-05-23 12:44:35+00:00	7 seconds
✔️	request-signature	2024-05-23 12:44:43+00:00	43 seconds
✔️	upload-signature	2024-05-23 12:45:26+00:00	16 seconds
✔️	publish-to-index	2024-05-23 12:45:42+00:00	2 minutes

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

Troubleshooting

Please refer to the troubleshooting guide.

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