question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Provisioning fails with error field not expected when provisioning with truenas

See original GitHub issue

I’m getting the below error when setting up democratic-csi to provision over nfs on my truenas core server.

failed to provision volume with StorageClass "csi-truenas-nfs": rpc error: code = Internal desc = Error: {"create_ancestors":
[{"message":"Field was not expected","errno":22}]} Error: {"create_ancestors":[{"message":"Field was not expected","errno":22}]} at 
Api.DatasetCreate (/home/csi/app/src/driver/freenas/http/api.js:392:11) at runMicrotasks (<anonymous>) at 
processTicksAndRejections (node:internal/process/task_queues:96:5) at async FreeNASApiDriver.CreateVolume 
(/home/csi/app/src/driver/freenas/api.js:2623:7) at async requestHandlerProxy (/home/csi/app/bin/democratic-csi:177:18)

here is my helm release: https://github.com/funkel1989/k3s-gitops/blob/main/cluster/core/democratic-csi/nfs/helm-release.yaml my test claim used to provision to see if this works: https://github.com/funkel1989/k3s-gitops/blob/main/cluster/core/democratic-csi/test-nfs-1.yaml

truenas version: TrueNAS-12.0-U7

if someone could point me to exactly what the error means so I can resolve it that would be the most helpful thing here for me.

Thanks all. sorry ahead of time if this is not the right place for this.

EDIT: Relized I forgot to post my driver.

apiVersion: v1
kind: Secret
type: Opaque
metadata:
    annotations:
        meta.helm.sh/release-name: nfs-democratic-csi
        meta.helm.sh/release-namespace: democratic-csi
    name: secret-democratic-csi-driver-config-nfs
    namespace: democratic-csi
stringData:
    driver-config-file.yaml: |
        driver: freenas-api-nfs 
        instance_id: B8712266-C1B5-4DCD-9DFD-C6646C0AD3A4 
        sshConnection:   
            host: 192.168.0.22   
            port: 22   
            username: root   
            privateKey: |     
            -----BEGIN OPENSSH PRIVATE KEY-----     
            
            -----END OPENSSH PRIVATE KEY----- 
        zfs:   
            cli:     
                sudoEnabled: true   
                datasetProperties: "org.freenas:description": "flux-{{ parameters.[csi.storage.k8s.io/pvc/namespace] }}-{{ parameters.[csi.storage.k8s.io/pvc/name] }}"   
                datasetParentName: /mnt/data/k8s/nfs/v   
                detachedSnapshotsDatasetParentName: /mnt/data/k8s/nfs/s   
                datasetEnableQuotas: true   
                datasetEnableReservation: false   
                datasetPermissionsMode: "0777"   
                datasetPermissionsUser: root    
                datasetPermissionsGroup: wheel 
        nfs:   
            shareCommentTemplate: "flux-{{ parameters.[csi.storage.k8s.io/pvc/namespace] }}-{{ parameters.[csi.storage.k8s.io/pvc/name] }}"   
            shareHost: 192.168.0.22   
            shareAlldirs: false   
            shareAllowedHosts: []   
            shareAllowedNetworks: []   
            shareMaprootUser: root   
            shareMaprootGroup: "wheel"   
            shareMapallUser: ""   
            shareMapallGroup: """

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:16 (9 by maintainers)

github_iconTop GitHub Comments

1reaction
funkel1989commented, May 30, 2022

I tried with permit Sudo also and got the same error. I switched to the root account and it worked.

I was not able to get the ssh key auth to work for any account FYI. it kept telling me invalid key format (similar error I don’t remember the wording) which is why I’m using password auth.

this is a local lab so I’m going to keep going with the root user for now and will have to figure that out later. My guess is there is some type of configuration stuff inside of truenas that I’m unaware of.

You can consider this resolved! Thanks for all the time you put in to help me!

0reactions
travisghansencommented, May 30, 2022

Yeah to enable passwordless sudo you have to do some stuff from the cli.

Read more comments on GitHub >

github_iconTop Results From Across the Web

SOLVED - When creating VM, [vm_type] Field was not expected
Hello I'm running a freshly updated 11.3-U5 and am trying to create a FreeBSD virtual machine, not a jail. When I finally press...
Read more >
Multi_node_multi_Writer Error with iscsi claim · Issue #2 - GitHub
I'm guessing you created the pvc as ReadWriteMany which at a fundamental level is not supported by iscsi. The other modes should work...
Read more >
8. Storage — TrueNAS®11.3-U2.2 User Guide Table of ...
The Available column shows the estimated storage space before compression. ... TrueNAS® encrypts disks and pools, not individual filesystems.
Read more >
[NAS-110846] Cant create Pool on TrueNAS Scale (it does ...
I had the same issue (my drive did not have the security bits set), and creating the pool manually on the commandline then...
Read more >
Failed to power on virtual machine (82542) | VMware KB
Microsoft Cluster VM won't power on after disk provisioning change, Wrong disk provisioning, such as, not using Thick, eager-zeroed ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found