Bug 2165443 - Upgrade guide - provide information about the warning TELEMETRY_CHANGED: Telemetry requires re-opt-in after the upgrade from 5.x to 6.x
Summary: Upgrade guide - provide information about the warning TELEMETRY_CHANGED: Tele...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Documentation
Version: 6.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 6.1z2
Assignee: Anjana Suparna Sriram
QA Contact: Aditya Ramteke
ceph-docs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-01-30 04:28 UTC by Vasishta
Modified: 2023-07-25 18:12 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHCEPH-6260 0 None None None 2023-03-14 05:56:47 UTC

Description Vasishta 2023-01-30 04:28:41 UTC
Describe the issue:
After upgrading a cluster from 5.x to 6.0 cluster displayed a warning - 

>> [WRN] TELEMETRY_CHANGED: Telemetry requires re-opt-in
>>     telemetry module includes new collections; please re-opt-in to new collections with `ceph telemetry on`

Checked with cephadm dev team regarding the same, Adam mentioned 
>> this just means they likely updated what information telemetry collects so we ask the user to re-opt-in to having that information collected and reported. That's not surprising across a major >> release upgrade.

Please consult Dashboard, orchestrator SMEs to get more detailed precised content on what are the implications and why user will have to act upon it.


Describe the task you were trying to accomplish:
Upgrade cluster from 5.x to 6.0

Suggestions for improvement:
Mentioned above.


Chapter/Section Number and Title:
End of chapter 1 and 2

Product Version:
6.x

Environment Details:
NA

Any other versions of this document that also needs this update:
Doesn't seem like it for now

Additional information:

Comment 7 Yaarit Hatuka 2023-07-10 14:10:11 UTC
Hi Vasishta,

The telemetry module is an "always-on" module, but the user is never opted-in to the service by default. 

The user needs to actively opt-in to the service, whether by running the `ceph telemetry on` CLI command along with the license parameter, or by using the Dashboard wizard.

If the user was prompted after the upgrade to re-opt-in to the service it means that they opted-in to the service at some point before the upgrade happened. 

Can you please provide the output of the following commands?

`ceph telemetry status`

`ceph telemetry collection ls`

Thanks,
Yaarit


Note You need to log in before you can comment on or make changes to this bug.