Project

General

Profile

Bug #20568

the dashboard uses absolute links for filesystems and clients

Added by Vladimir Pouzanov 5 months ago. Updated about 1 month ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
07/11/2017
Due date:
% Done:

0%

Source:
Tags:
Backport:
luminous
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Release:
Needs Doc:
No

Description

If ceph dashboard is accessed under a subpath (e.g. via kubernetes proxy), then some links are being rewritten correctly, but some are not.

Given ceph dashboard is served from `http://127.0.0.1:8001/api/v1/namespaces/ceph/services/ceph-mgr/proxy/health`,

cluster health points to: http://127.0.0.1:8001/api/v1/namespaces/ceph/services/ceph-mgr/proxy/health
servers points to http://127.0.0.1:8001/api/v1/namespaces/ceph/services/ceph-mgr/proxy/servers
but cephfs filesystem link points to http://127.0.0.1:8001/filesystem/1/ (incorrect absolute link)

within the filesystems page, client details points to http://127.0.0.1:8001/clients/1/ (incorrect absolute link)


Related issues

Copied to mgr - Backport #21549: luminous: the dashboard uses absolute links for filesystems and clients Resolved

History

#1 Updated by John Spray 4 months ago

The ones that aren't being rewritten are the ones that are populated dynamically (i.e. 'url' attributes of JSON objects coming from the backend). I suspect to make this work we'd need to make the module itself aware of it's prefix (which shouldn't be hard)

#2 Updated by John Spray 4 months ago

  • Status changed from New to Need Review

#3 Updated by John Spray 3 months ago

  • Status changed from Need Review to Pending Backport
  • Backport set to luminous

#4 Updated by Nathan Cutler 3 months ago

  • Copied to Backport #21549: luminous: the dashboard uses absolute links for filesystems and clients added

#5 Updated by Kefu Chai about 1 month ago

  • Status changed from Pending Backport to Resolved

Also available in: Atom PDF