Skip to content

DFBUGS-5629: [release-4.21] cephclients: expand cephfs cephclient permission for multiple fs#3709

Merged
openshift-merge-bot[bot] merged 1 commit intored-hat-storage:release-4.21from
openshift-cherrypick-robot:cherry-pick-3708-to-release-4.21
Mar 16, 2026
Merged

DFBUGS-5629: [release-4.21] cephclients: expand cephfs cephclient permission for multiple fs#3709
openshift-merge-bot[bot] merged 1 commit intored-hat-storage:release-4.21from
openshift-cherrypick-robot:cherry-pick-3708-to-release-4.21

Conversation

@openshift-cherrypick-robot
Copy link
Copy Markdown

This is an automated cherry-pick of #3708

/assign rewantsoni

expand cephclient permission to be able to access multiple ceph
filesystems

Signed-off-by: Rewant Soni <resoni@redhat.com>
@rewantsoni
Copy link
Copy Markdown
Member

rewantsoni commented Feb 19, 2026

/retitle DFBUGS-5629: [release-4.21] cephclients: expand cephfs cephclient permission for multiple fs

@openshift-ci openshift-ci bot changed the title [release-4.21] cephclients: expand cephfs cephclient permission for multiple fs DFBUGS-5629: [release-4.21] cephclients: expand cephfs cephclient permission for multiple fs Feb 19, 2026
@openshift-ci-robot openshift-ci-robot added jira/severity-important jira/valid-reference Indicates that this PR references a valid jira ticket of any type labels Feb 19, 2026
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Feb 19, 2026

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

  • expected the bug to target the "odf-4.21" 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 #3708

/assign rewantsoni

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-robot openshift-ci-robot added the jira/invalid-bug Indicates that the referenced jira bug is invalid for the branch this PR is targeting label Feb 19, 2026
@rewantsoni
Copy link
Copy Markdown
Member

/jira refresh

@openshift-ci-robot
Copy link
Copy Markdown

@rewantsoni: An error was encountered searching for bug DFBUGS-5629 on the Jira server at https://issues.redhat.com. No known errors were detected, please see the full error message for details.

Full error message. request failed. Please analyze the request body for more details. Status code: 403:

Please contact an administrator to resolve this issue, then request a bug refresh with /jira refresh.

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.

@rewantsoni
Copy link
Copy Markdown
Member

/jira refresh

@openshift-ci-robot
Copy link
Copy Markdown

@rewantsoni: An error was encountered searching for bug DFBUGS-5629 on the Jira server at https://issues.redhat.com. No known errors were detected, please see the full error message for details.

Full error message. request failed. Please analyze the request body for more details. Status code: 403:

Please contact an administrator to resolve this issue, then request a bug refresh with /jira refresh.

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.

@Nikhil-Ladha
Copy link
Copy Markdown
Member

/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 Mar 16, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@Nikhil-Ladha: This pull request references Jira Issue DFBUGS-5629, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (odf-4.21.1) matches configured target version for branch (odf-4.21.1)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @tchaitan-web

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
Copy Markdown
Contributor

openshift-ci bot commented Mar 16, 2026

@openshift-ci-robot: GitHub didn't allow me to request PR reviews from the following users: tchaitan-web.

Note that only red-hat-storage members and repo collaborators can review this PR, and authors cannot review their own PRs.

Details

In response to this:

@Nikhil-Ladha: This pull request references Jira Issue DFBUGS-5629, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (odf-4.21.1) matches configured target version for branch (odf-4.21.1)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @tchaitan-web

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.

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.

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 16, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Mar 16, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: malayparida2000, 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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 16, 2026
@openshift-merge-bot openshift-merge-bot bot merged commit cb5ac9a into red-hat-storage:release-4.21 Mar 16, 2026
11 checks passed
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Mar 16, 2026

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

[Jira Issue DFBUGS-5629](https://redhat.atlassian.net/browse/DFBUGS-5629) has been moved to the MODIFIED state.

Details

In response to this:

This is an automated cherry-pick of #3708

/assign rewantsoni

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 Indicates a PR has been approved by an approver from all required OWNERS files. jira/severity-important 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 Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants