OCPBUGS-29070: Add feature annotations to CSV

[jsafrane]

Add all required feature annotations to the operator. See the bug for our internal test report.

I am skipping the optional ones (cnv, cnf), I think false is implied there.

@openshift/storage

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jsafrane

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [jsafrane]

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

[openshift-ci-robot]

@jsafrane: This pull request references Jira Issue OCPBUGS-29070, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.16.0) matches configured target version for branch (4.16.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (wduan@redhat.com), skipping review request.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Add all required feature annotations to the operator. See the bug for our internal test report.

I am skipping the optional ones (cnv, cnf), I think false is implied there.

@openshift/storage

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.

[dobsonj]

/retest-required
/lgtm

[openshift-ci]

@jsafrane: all tests passed!

Full PR test history. Your PR dashboard.

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/test-infra repository. I understand the commands that are listed here.

[openshift-ci-robot]

@jsafrane: Jira Issue OCPBUGS-29070: All pull requests linked via external trackers have merged:

• openshift/aws-efs-csi-driver-operator#127

Jira Issue OCPBUGS-29070 has been moved to the MODIFIED state.

In response to this:

Add all required feature annotations to the operator. See the bug for our internal test report.

I am skipping the optional ones (cnv, cnf), I think false is implied there.

@openshift/storage

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-bot]

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-aws-efs-csi-driver-operator-container-v4.16.0-202402130109.p0.g35fa995.assembly.stream.el9 for distgit ose-aws-efs-csi-driver-operator.
All builds following this will include this PR.

[jsafrane]

/cherry-pick release-4.15

[openshift-cherrypick-robot]

@jsafrane: #127 failed to apply on top of branch "release-4.15":

Applying: Add feature annotations to CSV
Using index info to reconstruct a base tree...
M	config/manifests/stable/aws-efs-csi-driver-operator.clusterserviceversion.yaml
Falling back to patching base and 3-way merge...
Auto-merging config/manifests/stable/aws-efs-csi-driver-operator.clusterserviceversion.yaml
CONFLICT (content): Merge conflict in config/manifests/stable/aws-efs-csi-driver-operator.clusterserviceversion.yaml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Add feature annotations to CSV
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-4.15

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/test-infra repository.