Project

General

Profile

Actions

Bug #49349

closed

mgr/telemetry: check if 'ident' channel is active before compiling reports

Added by Yaarit Hatuka about 3 years ago. Updated about 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
telemetry module
Target version:
% Done:

0%

Source:
Development
Tags:
Backport:
pacific, octopus, nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

When compiling the telemetry reports we check for active channels.
The 'ident' channel check was missing, hence even if users turned this channel on, its content could not be appended to the report.


Related issues 3 (0 open3 closed)

Copied to mgr - Backport #49635: pacific: mgr/telemetry: check if 'ident' channel is active before compiling reportsResolvedSage WeilActions
Copied to mgr - Backport #49636: octopus: mgr/telemetry: check if 'ident' channel is active before compiling reportsResolvedNathan CutlerActions
Copied to mgr - Backport #49637: nautilus: mgr/telemetry: check if 'ident' channel is active before compiling reportsResolvedNathan CutlerActions
Actions #1

Updated by Yaarit Hatuka about 3 years ago

  • Pull request ID set to 39538
Actions #2

Updated by Kefu Chai about 3 years ago

  • Status changed from In Progress to Fix Under Review
Actions #3

Updated by Neha Ojha about 3 years ago

  • Status changed from Fix Under Review to Pending Backport
Actions #4

Updated by Backport Bot about 3 years ago

  • Copied to Backport #49635: pacific: mgr/telemetry: check if 'ident' channel is active before compiling reports added
Actions #5

Updated by Backport Bot about 3 years ago

  • Copied to Backport #49636: octopus: mgr/telemetry: check if 'ident' channel is active before compiling reports added
Actions #6

Updated by Backport Bot about 3 years ago

  • Copied to Backport #49637: nautilus: mgr/telemetry: check if 'ident' channel is active before compiling reports added
Actions #7

Updated by Loïc Dachary 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

Also available in: Atom PDF