Actions
Bug #23330
closedmon command "mgr metadata $name" has inconsistent argument naming
% Done:
0%
Source:
Tags:
Backport:
luminous
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
When running the following mon command:
std::ostringstream oss;
auto c = new MetadataUpdate(daemon_state, key);
oss << "{\"prefix\": \"mgr metadata\", \"who\": \""
<< key.second << "\"}";
monc->start_mon_command({oss.str()}, {}, &c->outbl, &c->outs, c);
MetadataUpdate::finish tries to decode an object but receives an array with one element.
Updated by Jan Fajerski about 6 years ago
- Subject changed from mon command "mgr metadata $name return json array (object expected) to mon command "mgr metadata $name" returns json array (object expected)
Updated by John Spray about 6 years ago
- Subject changed from mon command "mgr metadata $name" returns json array (object expected) to mon command "mgr metadata $name" has inconsistent argument naming
- Status changed from New to Fix Under Review
This command was using `id` where all the other metadata commands were using `who`, so anyone passing `who` is getting the list.
Updated by John Spray about 6 years ago
- Category set to MgrMonitor
- Assignee set to Jan Fajerski
- Backport set to luminous
Marking for backport because will want to take it along with fix for 23286 when that's done
Updated by John Spray about 6 years ago
- Related to Bug #23286: mgr: ActivePyModules::list_servers_python() returns mgr with empty hostname added
Updated by Sage Weil about 6 years ago
- Status changed from Fix Under Review to Resolved
Updated by Nathan Cutler about 6 years ago
- Status changed from Resolved to Pending Backport
Updated by Nathan Cutler about 6 years ago
- Copied to Backport #23722: luminous: mon command "mgr metadata $name" has inconsistent argument naming added
Updated by Nathan Cutler about 6 years ago
Preparing for backport on the assumption that Sage didn't mean to override #23330-3
Updated by Nathan Cutler about 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