Bug #65860: Upgrade test re-opts into new telemetry collections too late - mgr - Ceph

Actions

Copy link

Bug #65860

open

Upgrade test re-opts into new telemetry collections too late

Added by Laura Flores 12 days ago. Updated 11 days ago.

Status:

New

Priority:

Normal

Assignee:

Laura Flores

Category:

Target version:

% Done:

Source:

Tags:

Backport:

squid

Regression:

Severity:

3 - minor

Reviewed:

Affected Versions:

ceph-qa-suite:

Pull request ID:

Crash signature (v1):

Crash signature (v2):

Description

The test failed from:
/a/yuriw-2024-05-02_23:59:28-rados-wip-yuriw11-testing-20240501.200505-squid-distro-default-smithi/7686905

TELEMETRY_CHANGED: Telemetry requires re-opt-in

The health check later cleared after re-opting in:

2024-05-04T14:28:31.818066+0000 mon.a (mon.0) 5059 : cluster 1 Health check cleared: TELEMETRY_CHANGED (was: Telemetry requires re-opt-in)
2024-05-04T14:28:31.818092+0000 mon.a (mon.0) 5060 : cluster 1 Cluster is now healthy
2024-05-04T14:28:31.818066+0000 mon.a (mon.0) 5059 : cluster 1 Health check cleared: TELEMETRY_CHANGED (was: Telemetry requires re-opt-in)

In the test script, we don't re-opt in right away after upgrading, so this leads to the test failing from the warning despite it clearing up. The fix would likely be to move the opt in command up so it occurs right after the upgrade.