•Users skip the preparation of the storage (e.g. not seeding the System VM to the NFS export or seeding the wrong version for the hypervisor)
•NFS v4 is used which causes errors during Secondary Storage preparation (Solution: mount the storage and force NFS v3 before preparing the Storage: mount -v -t nfs -o vers=3 servername:/nfs/share /mnt/secondary)
•The /etc/export file on the NFS does not contain ‘no_root_squash’
•The /etc/export file on the NFS blocks the host/Management Network CIDR
•Users add Secondary Storage before Primary Storage
•Users enter wrong NFS share path (no validation by CloudStack)

  • No labels