Bug #23330
closed
mon command "mgr metadata $name" has inconsistent argument naming
Added by Jan Fajerski about 6 years ago.
Updated over 3 years ago.
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.
- Subject changed from mon command "mgr metadata $name return json array (object expected) to mon command "mgr metadata $name" returns json array (object expected)
- 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
- 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
- Related to Bug #23286: mgr: ActivePyModules::list_servers_python() returns mgr with empty hostname added
- Status changed from Fix Under Review to Resolved
- Status changed from Resolved to Pending Backport
- Copied to Backport #23722: luminous: mon command "mgr metadata $name" has inconsistent argument naming added
Preparing for backport on the assumption that Sage didn't mean to override #23330-3
- 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".
Also available in: Atom
PDF