Project

General

Profile

Actions

Bug #57174

open

NFS dashboard requires orchestrator backend to be set, but python shared lib does not

Added by Blaine Gardner over 1 year ago. Updated over 1 year ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
orchestrator
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

The NFS shared library does not require the orchestrator backend to be set, but the `NFS` tab of the dashboard does. Without the orchestrator enabled, it would be preferable to rely on the namespaces present in the `.nfs` pool to define what NFS clusters/services exist and to disable functionality for creating new NFS clusters/services. Export management should still be possible.

NFS page outputs this:

NFS-Ganesha is not configured

Remote method threw exception: Traceback (most recent call last): File "/usr/share/ceph/mgr/nfs/module.py", line 154, in cluster_ls return available_clusters(self) File "/usr/share/ceph/mgr/nfs/utils.py", line 38, in available_clusters completion = mgr.describe_service(service_type='nfs') File "/usr/share/ceph/mgr/orchestrator/_interface.py", line 1447, in inner completion = self._oremote(method_name, args, kwargs) File "/usr/share/ceph/mgr/orchestrator/_interface.py", line 1514, in _oremote raise NoOrchestrator() orchestrator._interface.NoOrchestrator: No orchestrator configured (try `ceph orch set backend`)

Screenshot of dashboard issue


Files

image.png (119 KB) image.png Screenshot of dashboard issue Blaine Gardner, 08/17/2022 09:46 PM
Actions #1

Updated by Adam King over 1 year ago

is this something that needs to be fixed in the nfs module or in the dashboard?

Actions #2

Updated by Blaine Gardner over 1 year ago

I'm not sure which is the culprit.

Actions

Also available in: Atom PDF