New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mgr: fixing dashboard configuration handling #13604
Conversation
ddfe93a
to
e0d45f0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch!!! LGTM.
Just review we are not "getting" dashboard options in other operator places.
167c5f3
to
f0d638b
Compare
This is the active mgr configuration? |
This the general mgr configuration and it affects to ALL the mgr daemons. Previously we were having the config per-daemon which could lead to some inconsistencies in the conf and is different from what cephadm based deployments (where all the config is at manager level) |
previously, the dashboard parameters supported by Rook were stored in the daemon configuration section (mgr.X, for example). This differs from Cephadm-based deployments, where all configurations are stored in the global mgr configuration section. This variance could result in configuration mismatches between the active and standby dashboards. Furthermore, all Ceph dashboard documentation exclusively points to the global mgr configuration section and makes no use of individual daemons sections. Fixes: rook#13577 Signed-off-by: Redouane Kachach <rkachach@redhat.com>
d5be6ba
to
29565d5
Compare
we dont set removeMgrDaemonConfiguration to true unless all the delete operations went successfull. Signed-off-by: Redouane Kachach <rkachach@redhat.com>
cf48562
to
39c06d2
Compare
mgr: fixing dashboard configuration handling (backport #13604)
previously, the dashboard parameters supported by Rook were stored in the daemon configuration section (mgr.X, for example). This differs from Cephadm-based deployments, where all configurations are stored in the global mgr configuration section. This variance could result in configuration mismatches between the active and standby dashboards. Furthermore, all Ceph dashboard documentation exclusively points to the global mgr configuration section and makes no use of individual daemons sections.
Fixes: #13577
Upgrade test
Starting from previous vesion (
image: rook/ceph:master
) and using the following configuration:Let's get the status of the config once the cluster is up&running:
Mgr daemons configuration after the upgrade (no specific per-daemon configuration anymore). The configuration related to ssl now is part of the main mgr section.
Checklist: