Skip to content
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.

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

STOR-1167: Enable extra-create-metadata to tag snapshots #223

Merged

Conversation

jsafrane
Copy link
Contributor

This is required by the new driver feature "Interpolated tags in VolumeSnapshotClass".

cc @openshift/storage

This is required by the new driver feature "Interpolated tags in
VolumeSnapshotClass".
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 18, 2023
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented May 18, 2023

@jsafrane: This pull request references STOR-1167 which is a valid jira issue.

In response to this:

This is required by the new driver feature "Interpolated tags in VolumeSnapshotClass".

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

@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 18, 2023

[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:

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 18, 2023
@jsafrane
Copy link
Contributor Author

/label docs-approved
/label px-approved

@openshift-ci openshift-ci bot added docs-approved Signifies that Docs has signed off on this PR px-approved Signifies that Product Support has signed off on this PR labels May 18, 2023
@jsafrane
Copy link
Contributor Author

All snapshot tests failed
/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 18, 2023
@jsafrane
Copy link
Contributor Author

E0518 13:07:47.230657 1 snapshot_controller.go:124] checkandUpdateContentStatus [snapcontent-a467cef2-493b-48bb-b358-98f1f267af4b]: error occurred failed to take snapshot of the volume vol-0d503ba85f0ac069e: "rpc error: code = InvalidArgument desc = Invalid parameter key csi.storage.k8s.io/volumesnapshot/namespace for CreateSnapshot"

So, --extra-create-metadata needs the new CSI driver, openshift/aws-ebs-csi-driver#222

I think that a cluster with both this PR and the new CSI driver PR should work. The CSI driver rebase needs to be merged first.

@Phaow
Copy link
Contributor

Phaow commented May 25, 2023

@jsafrane Pre merge test passed with job build openshift/aws-ebs-csi-driver#222,openshift/cluster-storage-operator#369,openshift/aws-ebs-csi-driver-operator#223 succeeded
With the fix patch, the "Interpolated tags in VolumeSnapshotClass" new feature works as expected. BTW, when I go through upstream docs, there's another Interpolated tags in storageClass provision pv with tags feature, do we also want to enbale it(add --extra-create-metadata flag to our csi-provisioner sidecar) by default?

Ref:

To allow for PV-level granularity, the CSI driver support runtime string interpolation on the tag values. You can specify placeholders for PVC namespace, PVC name and PV name, which will then be dynamically computed at runtime.

NOTE: This requires the --extra-create-metadata flag to be enabled on the external-provisioner sidecar.

@jsafrane
Copy link
Contributor Author

jsafrane commented Jun 2, 2023

/hold cancel
we need to merge openshift/aws-ebs-csi-driver#222 first, but that does not block testing of the rebase

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 2, 2023
@RomanBednar
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 2, 2023
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 5756b4d and 2 for PR HEAD ecb3e28 in total

@jsafrane
Copy link
Contributor Author

/retest

4 similar comments
@jsafrane
Copy link
Contributor Author

/retest

@jsafrane
Copy link
Contributor Author

/retest

@jsafrane
Copy link
Contributor Author

/retest

@jsafrane
Copy link
Contributor Author

/retest

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 4eef5db and 1 for PR HEAD ecb3e28 in total

@mpatlasov
Copy link
Contributor

/test hypershift-aws-e2e-external

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 21, 2023

@jsafrane: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-hypershift-conformance ecb3e28 link false /test e2e-hypershift-conformance

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.

@jsafrane
Copy link
Contributor Author

/retest

@openshift-merge-robot openshift-merge-robot merged commit 61ffef6 into openshift:master Jun 22, 2023
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. docs-approved Signifies that Docs has signed off on this PR jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. px-approved Signifies that Product Support has signed off on this PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants