-
Notifications
You must be signed in to change notification settings - Fork 80
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
NooBaa nsfs service showing Error No disk candidates found at generate entropy due to unsupported /dev/nvme0 devices #8598
Comments
@romayalon , this is similar to the #7982 |
@ramya-c3 , could you work with Romy and if needed check the fix, as we have tried manually patching in the 5.15.6 on ECE cluster yday w/r/t nvme disks. @romayalon , please let Ramya know about the upstream if needs to be tested. However as mentioned over slack there is no ECE cluster we have at hand with nvme drives. |
@romayalon This issue is not resolved please add /dev/nvme0n1 should be added instead of nvme0 alone. Is there a way that we can have wildcard character so we can have any number of characters post nvme? |
IMO, we need to understand what is the role of this, can @romayalon explain the same.. @ramya-c3 if possible can you post the lsblk command of ECE cluster for her reference |
@rkomandu @ramya-c3 this code was written 8 years ago and its purpose is to make sure we generate highly random encryption keys. Attaching here a link to a detailed github issue that Guy opened for explaining the purpose. @guymguym might be able to share more details. |
@guymguym Do you know if this part of the code must be hard-coded? |
@romayalon After discussion with the internal team we got to know that the nvme drives path will have namespace attached and it will be different each time so we need to have the regex supported along with nvme* suffix. |
@ramya-c3 would you attach a couple of examples? Anyway as it is written today we go over an array (as you can see currently with 4 items) and iterate over them. noobaa-core/src/util/nb_native.js Line 123 in e3bbfa1
A regex expression would not fit in this context, could you pass it as env (environment variable)? By the way in the flow, it comes from the function noobaa-core/src/util/nb_native.js Lines 33 to 35 in e3bbfa1
|
No it is not possible it will be automatically picked up by the system. |
Hi @ramya-c3 ,
Could you describe the way it picked and where is it saved? |
lsblk command will provide the output you can take alook at it lsblkNAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS |
HI @ramya-c3, I tried running the command in Linux terminal (I don't have a Linux machine, so I used this link): $ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
nvme0n1 259:0 0 3.5T 0 disk
nvme1n1 259:1 0 3.5T 0 disk
|-nvme1n1p1 259:2 0 4G 0 part [SWAP]
|-nvme1n1p2 259:3 0 1G 0 part
|-nvme1n1p3 259:4 0 2T 0 part /etc/hosts
| /etc/hostname
| /etc/resolv.conf
| /usr/sbin/docker-init
|-nvme1n1p4 259:5 0 1.5T 0 part /home/cg/root
`-nvme1n1p5 259:6 0 1M 0 part So if I understand correctly from what I run I should add the following disks: $ lsblk | grep disk
nvme0n1 259:0 0 3.5T 0 disk
nvme1n1 259:1 0 3.5T 0 disk |
/dev/nvme1n1,/dev/nvme0n1,/dev/nvme0n1p1,/dev/nvme0n1p2,/dev/nvme0,/dev/nvme1 |
Hi,
Do you want to add the whole list? (copied from Slack thread). |
Environment info
Actual behavior
[nsfs/465779] [LOG] CONSOLE:: generate_entropy: error
Error: No disk candidates found at generate_entropy (/usr/local/noobaa-core/src/util/nb_native.js:138:27) at async init_rand_seed (/usr/local/noobaa-core/src/util/nb_native.js:63:5)
Dec 12 19:00:24 stor107.ete14.res.ibm.com node[465779]: Dec-12 19:00:24.636 [nsfs/465779] [LOG] CONSOLE:: generate_entropy: error Error: No disk candidates found
Expected behavior
1.generate_entropy should be able to handle nvme devices, so that NooBaa nsfs service starts without error.
Steps to reproduce
The problem can be mitigated by adding /dev/dasda to
line 122 in /usr/local/noobaa-core/src/util/nb_native.js
" for (disk of ['/dev/sda', '/dev/vda', '/dev/xvda', '/dev/dasda','/dev/nvme0']) {"
and restart NooBaa nsfs service
More information - Screenshots / Logs / Other output
The text was updated successfully, but these errors were encountered: