Skip to content

DFBUGS-4238: subvolume: hide subvolume delete command for now #204

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.

Sign up for GitHub

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

Jump to bottom
Merged
subhamkrai merged 1 commit into from
Nov 20, 2025
Merged

DFBUGS-4238: subvolume: hide subvolume delete command for now #204

subhamkrai merged 1 commit into from
Nov 20, 2025

Conversation

@openshift-cherrypick-robot
Copy link

@openshift-cherrypick-robot openshift-cherrypick-robot commented Oct 6, 2025

This is an automated cherry-pick of #202

/assign subhamkrai

@subhamkrai
subvolume: hide subvolume delete command for now
9d34b21 
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>
@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Oct 6, 2025
Merged
@subhamkrai subhamkrai changed the title [release-4.19] subvolume: hide subvolume delete command for now DFBUGS-4238: subvolume: hide subvolume delete command for now Oct 17, 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/invalid-bug Indicates that the referenced jira bug is invalid for the branch this PR is targeting labels Oct 17, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 17, 2025 •
edited by openshift-ci bot
Loading

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

  • expected the bug to target the "odf-4.19.6" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

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.

@subhamkrai
Copy link
Contributor

subhamkrai commented Nov 17, 2025

/jira refresh

@openshift-ci-robot
Copy link

openshift-ci-robot commented Nov 17, 2025 •
edited by openshift-ci bot
Loading

@subhamkrai: This pull request references [Jira Issue DFBUGS-4238](https://issues.redhat.com//browse/DFBUGS-4238), which is invalid:

  • expected the bug to target either version "odf-4.19.7." or "openshift-odf-4.19.7.", but it targets "odf-4.19.8" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

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.

@subhamkrai
Copy link
Contributor

subhamkrai commented Nov 20, 2025

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that the referenced jira bug is valid for the branch this PR is targeting and removed jira/invalid-bug Indicates that the referenced jira bug is invalid for the branch this PR is targeting labels Nov 20, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Nov 20, 2025 •
edited by openshift-ci bot
Loading

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

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (odf-4.19.8) matches configured target version for branch (odf-4.19.8)
  • 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:

/jira refresh

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
Copy link

openshift-ci bot commented Nov 20, 2025

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

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

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

@subhamkrai subhamkrai merged commit 2b3474a into red-hat-storage:release-4.19 Nov 20, 2025
1 check passed
@openshift-ci-robot
Copy link

openshift-ci-robot commented Nov 20, 2025 •
edited by openshift-ci bot
Loading

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

[Jira Issue DFBUGS-4238](https://issues.redhat.com//browse/DFBUGS-4238) 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

Reviewers

No reviews

Assignees

@subhamkrai subhamkrai

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

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@openshift-cherrypick-robot @openshift-ci-robot @subhamkrai