Actions
Bug #54120
closedmgr/dashboard: dashboard turns telemetry off when configuring report
% Done:
0%
Source:
Development
Tags:
Backport:
octopus, pacific, quincy
Regression:
No
Severity:
3 - minor
Reviewed:
Description
Description of problem¶
The Telemetry wizard on the Dashboard turns telemetry off when user explores various channels in the report (while being opted-in).
Environment¶
ceph version
vstart cluster (pacific / quincy / master). Saw that also on the gibba cluster.- Platform (OS/distro/release): centos8
- Cluster details (nodes, monitors, OSDs): vstart cluster / gibba cluster
- Did it happen on a stable environment or after a migration/upgrade?: both
- Browser used (e.g.:
Version 86.0.4240.198 (Official Build) (64-bit)
): firefox 78.13.Oesr 64-bit
How reproducible¶
Steps:
- Start a vstart cluster (pacific / quincy / master)
- Opt-in to telemetry either via:
- CLI with `ceph telemetry on`
- Dashboard wizard:
- Go to Telemetry Configuration page (Step 1 of 2: Telemetry report configuration) at https://127.0.0.1:<port>/#/telemetry
- Click “Next” at the bottom of the page
- On the next page (Step 2 of 2: Telemetry report preview) check the license box (I agree…).
- Click “Update”
- In the CLI, run `ceph telemetry status` to see that `"enabled": true`.
- Go back to the Telemetry Configuration page (Step 1 of 2: Telemetry report configuration).
- Uncheck one of the checked boxed of the available channels (e.g. uncheck Crash channel checkbox).
- Click “Next”.
- Now a popup window should appear with the text:
"Your settings have been applied successfully. Due to privacy/legal reasons the Telemetry module is now disabled until you complete the next step and accept the license." - Go back to CLI and run `ceph telemetry status` (which shows that “enabled”: false)
Actual results¶
The telemetry module is being disabled when the user just explores the report, which is wrong.
Expected results¶
The wizard should not turn telemetry off, unless the user explicitly clicked the "Deactivate" button.
The user should be able to explore the report details without setting any new configuration.
Additional info¶
This might happen also in Octopus, need to check.
Actions