Failed to create backend - media is not ready or Auth is not passed #15
Comments
|
Please use the NAS's account and password, not CHAP A/P. Thanks. |
|
Thank you. Based on above I managed to make progress, however I am now hitting now another issue which looks very similar to pvc is created but pod is unable to mount the volume (#13). I am also running Talos Linux single node cluster. |
|
I made some progress and can configure backend with previously defined TridentBackEnd configuration. Now facing issue where pod is not able to consume PVC and is getting stuck in status ContainerCreating. I am having following StorageClass following PVC and following Deployment I see following event in pod and following logged in trident-node-linux pod. Do I have configuration problem or is this fault? |
|
hi @louhisuo, Talos is a minimal Linux OS, and it lacks some basic utilities (like dd and others) that are typically found in most Linux systems. Our service assumes that these tools are available on the node, so if they are missing, attempting to use them could lead to errors. We are aware that Talos might support Linux utility extensions, which could potentially help you install the required utilities. Thank you. Ref : https://github.com/siderolabs/extensions?tab=readme-ov-file https://github.com/siderolabs/extensions/tree/main/tools/util-linux |
|
I have added util-linux-tools talos extension to the cluster (see below) The issue still remains (logs from trident-node-linux pod) Are you expecting some specific linux tool to be available on node? If it is |
|
Is this issue Support for Talos (#806) perhaps a reason why QNAP CSI Plugin does not work with Talos Linux? |
|
@louhisuo looks like you arrived at the same point I did. The next thing I was going to do was build a talos extension for |
Yes, this issue has the same root cause as ours. You can reference the document we provided earlier for Linux utility extension or seek help from Talos. |
|
Yes, it looks like we both are hitting same issue @brunnels. Looking forward to have |
|
@davidcheng0716, if QNAP is serious to position their NAS products as Kubernetes storage QNAP needs to consider to make to investments in this area. (1) Refactor QNAP CSI Driver as OS agnostic by including all needed tools into CSI driver. With this approach it will be easier for QNAP support wide range of operating systems and kubernetes distributions with minimal effort. QNAP is way behind Synology regarding this (see below). And to be very direct it is very hard to recommend QNAP as Kubernetes storage when comparing what Synology can offer. |
|
@louhisuo , your concern seems very well founded in this case. I hacked together a coreutils extension , so now the QNAP CSI Plugin can tell that the disk isn't formatted, so now it wants mkfs.ext4. I might play whack a mole with this a bit and see if I can turn that into a proper qnap support extension. |
|
A few rounds of whack-a-mole later... It seems to be getting past the dd issue, and several others, and I don't see any more obvious missing executables in the logs, but it's still not working. It says "Mount information not found", but I can't tell what command it's trying to use to do that. This part looks like maybe it's missing something, but it's unclear what: More log context here: |
|
Hi, michelle when you get this running, would you consider checking in with siderolabs to maybe get this as an official extension and part of the talos factory? |
|
@sempex I highly doubt they will. Their reply will be just add the packages to the container. Which is the right answer and something we could do ourselves if this project source were open. It's based on the open source trident driver so probably should be. I sent an email to qnap requesting the source a few months back but no reply. |
|
@brunnels ahh that sucks, It should not be that hard to get this running but why do you think that they won't add it as an available system extension like linux-utils for example? I mean that would probably help a lot of people... |
|
@michelle-avery Actually, now that I think more about it, we might be able to build a new container based on the old one and specify that in the helm chart or operator. What is the image name of the If that image is defined in the helm values.yaml it should be possible to use it as a base image and install whatever packages are missing. @michelle-avery one other thing to check is talos default security policy is to not allow privileged pods. Do you have this label on the trident namespace? |
|
@brunnels - I did have the namespace labeled correctly. The image, defined here, is |
|
@michelle-avery I don't think they are necessary on the host. I was able to use talos-debug-tools pod on the same node in the qnap trident namespace and run the same dd commands on the iscsi device that the |
|
@brunnels @louhisuo @michelle-avery @sempex |
|
@JimmyTanMPM Any updates? I have time to test this weekend if you have an alpha or similar available. |
|
@JimmyTanMPM @davidcheng0716 @qnap-dennisyang Any updates or perhaps a beta we could look at? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Having QNAP TS-673A running QuTS hero h5.2.0.2860. QNAP CSI Plugin version is 1.3.0. Kubernetes version is 1.30.3 (Talos Linux).
Trying to initialize qnap csi plugin against following backend
using this trident backend configuration.
When describing
TridentBackendConfigseeing following errors and also errors in in trident-controller podstorage-api-serverandtrident-maincontainer logs... and ip address of kubernetes cluster gets added to IP block list.
Note also that Talos Linux has has implemented some kubernetes security hardening by default and I get following type of warnings when deploying plugin as well as when restarting deployments and daemonset
Please advice if this is fault or configuration mistake.
The text was updated successfully, but these errors were encountered: