Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
This project is now read‑only. Starting Monday, February 2, please use Jira Cloud for all bug tracking management.

Bug 1792222

Summary: unable to disable the dashboard redirect mechanism
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Giulio Fidente <gfidente>
Component: Ceph-DashboardAssignee: Ernesto Puerta <epuertat>
Status: CLOSED ERRATA QA Contact: Sunil Angadi <sangadi>
Severity: high Docs Contact: Anjana Suparna Sriram <asriram>
Priority: high    
Version: 4.0CC: ceph-eng-bugs, epuertat, flucifre, fpantano, nweinber, pasik, sangadi
Target Milestone: rc   
Target Release: 4.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: openstack
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-05-19 17:32:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1760354, 1806495    

Description Giulio Fidente 2020-01-17 10:29:22 UTC
when deploying the dahsboard module behind a proxy/balancer it's necessary to disable the internal mechanism as described in [1]

this doesn't seem to work with ceph-mgr-14.2.4-69.el8cp.x86_64

[root@controller-0 ~]# podman exec e6b92f668a86 ceph config set mgr mgr/dashboard/standby_behaviour "error"
Error EINVAL: unrecognized config option 'mgr/dashboard/standby_behaviour'
Error: exit status 22

when passing --force the key is created but the redirect continues


1. https://docs.ceph.com/docs/master/mgr/dashboard/#disable-the-redirection

Comment 1 Ernesto Puerta 2020-01-17 11:48:36 UTC
Moved to 4.1, as commit is already available in upstream release (14.2.5) for downstream cherry-picking.

Comment 5 Federico Lucifredi 2020-03-10 05:26:28 UTC
this is tagged 4.0, but is still ON_QA... should it be 4.1, or should it be CLOSED CURRENTRELEASE?

Comment 12 errata-xmlrpc 2020-05-19 17:32:06 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:2231