Project

General

Profile

Actions
Copy link

Bug #50858

closed

mgr/nfs: skipping conf file or passing empty file throws traceback

Added by Varsha Rao almost 3 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Varsha Rao
Category:
-
Target version:
Ceph - v17.0.0
% Done:

0%

Source:
Development
Tags:
Backport:
pacific
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
mgr/nfs
Labels (FS):
NFS-cluster
Pull request ID:
41378
Crash signature (v1):
Crash signature (v2):

Description

It should print helpful error message instead of throwing traceback

# ./bin/ceph nfs cluster config set vstart
*** DEVELOPER MODE: setting PATH, PYTHONPATH and LD_LIBRARY_PATH ***
2021-05-11T13:01:19.837+0530 7fc489b1a640 -1 WARNING: all dangerous and experimental features are enabled.
2021-05-11T13:01:19.857+0530 7fc489b1a640 -1 WARNING: all dangerous and experimental features are enabled.
Error EINVAL: Traceback (most recent call last):
  File "/home/varsha/ceph/src/pybind/mgr/mgr_module.py", line 1337, in _handle_command
    return CLICommand.COMMANDS[cmd['prefix']].call(self, cmd, inbuf)
  File "/home/varsha/ceph/src/pybind/mgr/mgr_module.py", line 389, in call
    return self.func(mgr, **kwargs)
TypeError: _cmd_nfs_cluster_config_set() missing 1 required positional argument: 'inbuf'

Related issues 1 (0 open — 1 closed)

Copied to CephFS - Backport #50991: pacific: mgr/nfs: skipping conf file or passing empty file throws tracebackResolvedVarsha RaoActions
Actions
Copy link
 #1

Updated by Varsha Rao almost 3 years ago

  • Status changed from New to Fix Under Review
  • Pull request ID set to 41378
Actions
Copy link
 #2

Updated by Kefu Chai almost 3 years ago

  • Status changed from Fix Under Review to Pending Backport
Actions
Copy link
 #3

Updated by Backport Bot almost 3 years ago

  • Copied to Backport #50991: pacific: mgr/nfs: skipping conf file or passing empty file throws traceback added
Actions
Copy link
 #4

Updated by Loïc Dachary over 2 years ago

  • Status changed from Pending Backport to Resolved

While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".

Actions
Copy link

Also available in: Atom PDF