https://tracker.ceph.com/https://tracker.ceph.com/favicon.ico2019-12-14T02:49:49ZCeph mgr - Bug #43313: telemetry module can crash on entity name with multiple '.' separatorshttps://tracker.ceph.com/issues/43313?journal_id=1544032019-12-14T02:49:49ZDan Mickdmick@redhat.com
<ul><li><strong>Project</strong> changed from <i>Ceph</i> to <i>mgr</i></li></ul> mgr - Bug #43313: telemetry module can crash on entity name with multiple '.' separatorshttps://tracker.ceph.com/issues/43313?journal_id=1557462020-01-14T23:46:57ZAlexandre Marangonea.marangone@gmail.com
<ul></ul><p>Dan, I'm looking into this. I'm not certain on how you expect the crash to look on the server side.<br />It would be easy to specify a maxsplit of 1 but then the reported entity_name in the crash would be client.$hash. Would it be more useful to get client.<client_type>.$hash?</p>
<p>Also it looks like any radosgw crash would trigger this since the expectation is that there's only 1 dot in the name and the default naming convention for rgw is client.rgw.`hostname -s`</p> mgr - Bug #43313: telemetry module can crash on entity name with multiple '.' separatorshttps://tracker.ceph.com/issues/43313?journal_id=1557562020-01-15T04:15:54ZDan Mickdmick@redhat.com
<ul></ul><p>with maxsplit 1:<br /><pre>
>>> s='client.rgw.stage2-rgw02-object02.s2r6'
>>> s.split('.', 1)
['client', 'rgw.stage2-rgw02-object02.s2r6']
</pre><br />which is what you want, I think. As for the hash, the point of the hash is to obscure any customer identifiers like hostname or zone name or whatever is stuffed into the name.</p> mgr - Bug #43313: telemetry module can crash on entity name with multiple '.' separatorshttps://tracker.ceph.com/issues/43313?journal_id=1557612020-01-15T04:49:47ZAlexandre Marangonea.marangone@gmail.com
<ul></ul><p>Gotcha. I thought it could have been important to identify client type (i.e. rgw) in the entity name</p> mgr - Bug #43313: telemetry module can crash on entity name with multiple '.' separatorshttps://tracker.ceph.com/issues/43313?journal_id=1578882020-02-06T03:21:32ZSage Weilsage@newdream.net
<ul><li><strong>Priority</strong> changed from <i>Normal</i> to <i>Urgent</i></li><li><strong>Backport</strong> set to <i>nautilus,mimic</i></li></ul> mgr - Bug #43313: telemetry module can crash on entity name with multiple '.' separatorshttps://tracker.ceph.com/issues/43313?journal_id=1579992020-02-07T04:53:44ZDan Mickdmick@redhat.com
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Fix Under Review</i></li><li><strong>Pull request ID</strong> set to <i>33094</i></li></ul> mgr - Bug #43313: telemetry module can crash on entity name with multiple '.' separatorshttps://tracker.ceph.com/issues/43313?journal_id=1580952020-02-08T14:08:19ZSage Weilsage@newdream.net
<ul><li><strong>Status</strong> changed from <i>Fix Under Review</i> to <i>Pending Backport</i></li></ul> mgr - Bug #43313: telemetry module can crash on entity name with multiple '.' separatorshttps://tracker.ceph.com/issues/43313?journal_id=1581472020-02-10T05:48:24ZKonstantin Shalygink0ste@k0ste.ru
<ul><li><strong>Copied to</strong> <i><a class="issue tracker-9 status-3 priority-4 priority-default closed" href="/issues/44057">Backport #44057</a>: nautilus: telemetry module can crash on entity name with multiple '.' separators</i> added</li></ul> mgr - Bug #43313: telemetry module can crash on entity name with multiple '.' separatorshttps://tracker.ceph.com/issues/43313?journal_id=1581492020-02-10T05:48:32ZKonstantin Shalygink0ste@k0ste.ru
<ul><li><strong>Copied to</strong> <i><a class="issue tracker-9 status-6 priority-4 priority-default closed" href="/issues/44058">Backport #44058</a>: mimic: telemetry module can crash on entity name with multiple '.' separators</i> added</li></ul> mgr - Bug #43313: telemetry module can crash on entity name with multiple '.' separatorshttps://tracker.ceph.com/issues/43313?journal_id=1837122021-01-27T20:03:39ZNathan Cutlerncutler@suse.cz
<ul><li><strong>Status</strong> changed from <i>Pending Backport</i> to <i>Resolved</i></li></ul><p>While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".</p>