Skip to content

DFBUGS-5272: [release-4.21] Fix authenticated endpoint (ux-backend-server) #722

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
openshift-merge-bot merged 1 commit into from
Jan 16, 2026
Merged

DFBUGS-5272: [release-4.21] Fix authenticated endpoint (ux-backend-server) #722

openshift-merge-bot merged 1 commit into from
Jan 16, 2026

Conversation

@openshift-cherrypick-robot
Copy link

@openshift-cherrypick-robot openshift-cherrypick-robot commented Jan 16, 2026

This is an automated cherry-pick of #721

/assign SanjalKatiyar

@SanjalKatiyar
console: Fix authenticated endpoint (ux-backend-server)
154b19a 
A new authenticated endpoint was added for the non-admin ODF user
to ux-backend-server (behind kube-rbac-proxy). But seems like we
migrated the server deployment from OCS to ODF and this new path
was missed from the `-openshift-delegate-urls` allowlist.

Signed-off-by: SanjalKatiyar <[email protected]>
@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Jan 16, 2026
Merged
@SanjalKatiyar
Copy link
Contributor

SanjalKatiyar commented Jan 16, 2026 •
edited by openshift-ci bot
Loading

/retitle DFBUGS-5272: [release-4.21] Fix authenticated endpoint (ux-backend-server)

@openshift-ci openshift-ci bot changed the title [release-4.21] Fix authenticated endpoint (ux-backend-server) DFBUGS-5272: [release-4.21] Fix authenticated endpoint (ux-backend-server) Jan 16, 2026
@openshift-ci-robot openshift-ci-robot added jira/severity-critical Referenced Jira bug's severity is critical 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 Jan 16, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 16, 2026 •
edited by openshift-ci bot
Loading

@openshift-cherrypick-robot: This pull request references [Jira Issue DFBUGS-5272](https://issues.redhat.com//browse/DFBUGS-5272), 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 #721

/assign SanjalKatiyar

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 Indicates that a PR is ready to be merged. label Jan 16, 2026
@malayparida2000 malayparida2000 added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 16, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 16, 2026

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

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

@SanjalKatiyar
Copy link
Contributor

SanjalKatiyar commented Jan 16, 2026

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

openshift-ci-robot commented Jan 16, 2026 •
edited by openshift-ci bot
Loading

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

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (odf-4.21) matches configured target version for branch (odf-4.21)
  • 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 ([email protected]), 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-merge-bot openshift-merge-bot bot merged commit 5d83353 into red-hat-storage:release-4.21 Jan 16, 2026
16 checks passed
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 16, 2026 •
edited by openshift-ci bot
Loading

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

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

Details

In response to this:

This is an automated cherry-pick of #721

/assign SanjalKatiyar

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

@malayparida2000 malayparida2000 malayparida2000 approved these changes

Assignees

@SanjalKatiyar SanjalKatiyar

@malayparida2000 malayparida2000

Labels

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

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@openshift-cherrypick-robot @SanjalKatiyar @openshift-ci-robot @malayparida2000