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.

Sign up for GitHub

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

Jump to bottom

the discovery service did not discover my disk and ignored it #9501

Closed
1998729 opened this issue Dec 28, 2021 · 5 comments · Fixed by #9512
Closed

the discovery service did not discover my disk and ignored it #9501

1998729 opened this issue Dec 28, 2021 · 5 comments · Fixed by #9512
Labels
bug

Comments

@1998729
Copy link

1998729 commented Dec 28, 2021

I have enabled the daemonset function according to the disk discovery mechanism, and the service is running normally, but there is obviously a new disk on my current machine and it has not been initialized, but he always does not mount it for me

image
@1998729 1998729 added the bug label Dec 28, 2021
@1998729
Copy link
Author

1998729 commented Dec 28, 2021

image

@1998729
Copy link
Author

1998729 commented Dec 28, 2021

image

@1998729
Copy link
Author

1998729 commented Dec 28, 2021

image

@leseb
Copy link
Member

leseb commented Jan 3, 2022

This is probably a duplicate of #9493.

@leseb
Copy link
Member

leseb commented Jan 3, 2022

Which Rook version are you running on?

@leseb leseb linked a pull request Jan 3, 2022 that will close this issue
core: run discover daemonset as root uid #9512
Merged
10 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

core: run discover daemonset as root uid leseb/rook
2 participants
@leseb @1998729