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

ceph: fix #6214 New node is not provisioned when useAllNodes: true #6768

Merged
merged 1 commit into from
Dec 4, 2020

Conversation

shaas
Copy link
Contributor

@shaas shaas commented Dec 4, 2020

When a new node got added rook checks if there is already an OSD running on that host via ceph osd crush ls
As this is a new node ceph returns with the error ENOENT. Rook handles this wrongly as a fatal error and aborts the addition of nodes.

The fix checks in case of an error if ENOENT is the reason and simply proceeds.

Signed-off-by: Stefan Haas shaas@suse.com

@mergify mergify bot added the ceph main ceph tag label Dec 4, 2020
pkg/daemon/ceph/client/crush.go Outdated Show resolved Hide resolved
@shaas shaas marked this pull request as draft December 4, 2020 14:05
Signed-off-by: Stefan Haas <shaas@suse.com>
@shaas shaas marked this pull request as ready for review December 4, 2020 15:27
@shaas shaas requested a review from leseb December 4, 2020 15:28
@leseb leseb requested a review from travisn December 4, 2020 15:34
Copy link
Member

@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.

Ah, is this why the addition of nodes has not been reliable for triggering a reconcile? This has been a long time bug, great to have the fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ceph main ceph tag
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants