Actions
Bug #42958
closedmgr/PyModule.cc: set_config with an empty value doesn't remove the config option
% Done:
0%
Source:
Tags:
Backport:
nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Description
PyModuleConfig::set_config() is meant to set a configuration option if a value is provided, and remove the option if no value is passed. The setting part works fine, the removing part, not so much. For example, if you run `ceph orchestrator set backend ''` to unset the orchestrator backend, the mgr/orchestrator_cli/orchestrator config option remains present, and the mgr log says:
2019-11-22T04:18:55.840+0100 7f2807c67700 0 mgr[py] `config set mgrmgr/orchestrator_cli/orchestrator --` failed: (22) Invalid argument 2019-11-22T04:18:55.840+0100 7f2807c67700 0 mgr[py] mon returned -22: unrecognized config target ''
Updated by Tim Serong over 4 years ago
- Status changed from New to Fix Under Review
- Pull request ID set to 31807
Updated by Sage Weil over 4 years ago
- Status changed from Fix Under Review to Resolved
Updated by Jason Dillaman over 3 years ago
- Status changed from Resolved to Pending Backport
- Backport set to nautilus
This bug still exists in the Nautilus branch
Updated by Backport Bot over 3 years ago
- Copied to Backport #48768: nautilus: mgr/PyModule.cc: set_config with an empty value doesn't remove the config option added
Updated by Nathan Cutler over 3 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