Open jlpedrosa opened 5 months ago
Hi! Thanks for filing this issue. I'm digging around and finding a few skeletons.
The workaround you need to apply here is to install the Helm chart and disable node configuration and conformance.
To apply hpe-csi-driver parameters to the TrueNAS CSP chart you prefix the values with hpe-csi-driver
, like --set hpe-csi-driver.disableNodeConformance --set hpe-csi-driver.disableNodeConfiguration
. Somehow I've missed to document this and I'm not in front of a computer to verify this.
There won't be a 2.4.1 of the TrueNAS CSP, we're working on 2.4.2 of the CSI driver as we uncovered an issue with 3PAR that needs immediate attention.
It won't include any fix for this issue so the workaround will be to manually install and configure iSCSI/multipath and disable node configuration/conformance.
Hi @datamattsson
Thanks for the help, now the errors are gone. Let me know if you need me to run any tests to solve it in a more permanent way or if the recommended way is to disable those, then probably there should be docs about the packages required?
Thanks again!
Let me know if you need me to run any tests to solve it in a more permanent way or if the recommended way is to disable those, then probably there should be docs about the packages required?
Here's the docs for the "disable" parameters: https://scod.hpedev.io/csi_driver/operations.html#manual_node_configuration
The permanent fix for this issue is that the error that is raised shouldn't be fatal. I'll file an internal JIRA for this.
I'm unable to boot correctly the CSI driver. More precisely on the HPE part.
The daemon set shows on the csi-node-driver-registrar container:
On the other container I see a lot of errors, that I don't know if they are fatal (last one feels like?):
I see multiple things that look wrong/ The distro is actually Ubuntu, but the log says:
"got OS details as [redhat 9 2 5.15.0-1049-raspi]\n
but later we getDistro section: Ubuntu , not present for deviceType: Nimble , using default config" file="config.go:247"
Indeed the path
/sys/firmware/dmi
/ does not existThe "server" is a raspberry pi, also BOOTED through ISCSI. I hope we can fix this before you actually release 2.4.1?
Also heads UP, i modified the kubelet path, the one created by default was incorrect, contained double slash
//
This is the deployment: