Skip to content
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

disabling rook mgr module in CephCluster #2776

Merged

Conversation

ShravaniVangur
Copy link
Contributor

Sometimes, during installation with ODF, the rook mgr module in ceph cluster is being enabled. This pr ensures that it is disabled during installation.

For example:
sh-4.4$ ceph mgr module ls | grep rook
rook on

With this change:
sh-4.4$ ceph mgr module ls | grep rook
rook -

@ShravaniVangur ShravaniVangur force-pushed the disable-rook-module branch 2 times, most recently from ca22af7 to ebd7b00 Compare September 2, 2024 12:49
Disable rook mgr module during installation with ODF.

Signed-off-by: ShravaniVangur <shravanivangur@gmail.com>
@@ -1101,6 +1101,7 @@ func generateMgrSpec(sc *ocsv1.StorageCluster) rookCephv1.MgrSpec {
Modules: []rookCephv1.Module{
{Name: "pg_autoscaler", Enabled: true},
{Name: "balancer", Enabled: true},
{Name: "rook", Enabled: false},
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are we planning to keep it disabled permanently? I doubt 🤔

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Technically it is supposed to be disabled when it is installed. But due to some issues as observed in this bz: https://bugzilla.redhat.com/show_bug.cgi?id=2300312#add_comment the rook mgr module is enabled initially. This just makes sure that on installation it remains disabled. Can be enabled through the rook toolbox post installation.

Are we planning to keep it disabled permanently? I doubt 🤔

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Understood, but what if in future we would want to enable the module for some case? By disabling it this way, there would be clash between a user manually enabling it through toolbox and the operator reconciling it to disable.
@travisn is it guaranteed that in future as well we don't see any use case for rook-mgr module in ODF d/s?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The rook mgr module is really only used by the upstream dashboard, which we don't use downstream. There is not currently a scenario to enable this module in the downstream. When it is enabled (though we are not sure the cause), it causes errors as we have seen in a couple customer clusters.

Copy link
Contributor

@travisn travisn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 3, 2024
Copy link
Contributor

openshift-ci bot commented Sep 3, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ShravaniVangur, travisn

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 3, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit 3162642 into red-hat-storage:main Sep 3, 2024
11 checks passed
@ShravaniVangur
Copy link
Contributor Author

/cherry-pick release-4.17

@openshift-cherrypick-robot

@ShravaniVangur: new pull request created: #2786

In response to this:

/cherry-pick release-4.17

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants