Project

General

Profile

Actions

Bug #56486

closed

mgr/telemetry: reset health warning after re-opting-in

Added by Yaarit Hatuka almost 2 years ago. Updated over 1 year ago.

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

0%

Source:
Community (user)
Tags:
backport_processed
Backport:
pacific, quincy
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

When telemetry requires re-opting-in (either whenever new collections which require nagging are available, or on major upgrades) a health warning is set by the module.

This health warning should be reset once the user re-opts-in (with `ceph telemetry on`), but currently it might take longer.


Related issues 2 (0 open2 closed)

Copied to mgr - Backport #56719: quincy: mgr/telemetry: reset health warning after re-opting-inResolvedYaarit HatukaActions
Copied to mgr - Backport #56720: pacific: mgr/telemetry: reset health warning after re-opting-inResolvedYaarit HatukaActions
Actions #1

Updated by Yaarit Hatuka almost 2 years ago

  • Status changed from New to Fix Under Review
  • Pull request ID set to 47001
Actions #2

Updated by Yaarit Hatuka almost 2 years ago

  • Subject changed from reset telemetry health warning after re-opting-in to mgr/telemetry: reset health warning after re-opting-in
Actions #3

Updated by Patrick Donnelly almost 2 years ago

  • Target version deleted (v17.2.2)
Actions #4

Updated by Yaarit Hatuka almost 2 years ago

  • Copied to Backport #56719: quincy: mgr/telemetry: reset health warning after re-opting-in added
Actions #5

Updated by Yaarit Hatuka almost 2 years ago

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

Updated by Yaarit Hatuka almost 2 years ago

  • Copied to Backport #56720: pacific: mgr/telemetry: reset health warning after re-opting-in added
Actions #7

Updated by Backport Bot over 1 year ago

  • Tags set to backport_processed
Actions #8

Updated by Konstantin Shalygin over 1 year ago

  • Status changed from Pending Backport to Resolved
Actions

Also available in: Atom PDF