Bug 2165443

Summary:	Upgrade guide - provide information about the warning TELEMETRY_CHANGED: Telemetry requires re-opt-in after the upgrade from 5.x to 6.x
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Vasishta <vashastr>
Component:	Documentation	Assignee:	Anjana Suparna Sriram <asriram>
Documentation sub component:	Upgrade Guide	QA Contact:	Aditya Ramteke <aramteke>
Status:	NEW ---	Docs Contact:	ceph-docs <ceph-docs>
Severity:	high
Priority:	unspecified	CC:	adking, asriram, cephqe-warriors, epuertat, lflores, rmandyam, yhatuka
Version:	6.0
Target Milestone:	---
Target Release:	6.1z2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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