Skip to content

DFBUGS-4154: [release-4.20] subvolume: hide subvolume delete command for now#203

Merged
subhamkrai merged 1 commit intored-hat-storage:release-4.20from
openshift-cherrypick-robot:cherry-pick-202-to-release-4.20
Oct 6, 2025
Merged

DFBUGS-4154: [release-4.20] subvolume: hide subvolume delete command for now#203
subhamkrai merged 1 commit intored-hat-storage:release-4.20from
openshift-cherrypick-robot:cherry-pick-202-to-release-4.20

Conversation

@openshift-cherrypick-robot
Copy link
Copy Markdown

This is an automated cherry-pick of #202

/assign subhamkrai

subvolume delete command has some know issue, so till
it is fixed let's hide that until we have a fix.

Signed-off-by: subhamkrai <srai@redhat.com>
@subhamkrai subhamkrai changed the title [release-4.20] subvolume: hide subvolume delete command for now DFBUGS-4154: [release-4.20] subvolume: hide subvolume delete command for now Oct 6, 2025
@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid jira ticket of any type jira/valid-bug Indicates that the referenced jira bug is valid for the branch this PR is targeting labels Oct 6, 2025
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Oct 6, 2025

@openshift-cherrypick-robot: This pull request references [Jira Issue DFBUGS-4154](https://issues.redhat.com//browse/DFBUGS-4154), which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (odf-4.20) matches configured target version for branch (odf-4.20)
  • bug is in the state POST, 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 (posharma@redhat.com), skipping review request.

Details

In response to this:

This is an automated cherry-pick of #202

/assign subhamkrai

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-ci openshift-ci Bot added the lgtm label Oct 6, 2025
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Oct 6, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: openshift-cherrypick-robot, subhamkrai

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

The pull request process is described here

Details 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 label Oct 6, 2025
@subhamkrai subhamkrai merged commit 053234c into red-hat-storage:release-4.20 Oct 6, 2025
1 check passed
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Oct 6, 2025

@openshift-cherrypick-robot: [Jira Issue DFBUGS-4154](https://issues.redhat.com//browse/DFBUGS-4154): All pull requests linked via external trackers have merged:

[Jira Issue DFBUGS-4154](https://issues.redhat.com//browse/DFBUGS-4154) has been moved to the MODIFIED state.

Details

In response to this:

This is an automated cherry-pick of #202

/assign subhamkrai

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-bug Indicates that the referenced jira bug is valid for the branch this PR is targeting jira/valid-reference Indicates that this PR references a valid jira ticket of any type lgtm

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants