You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Matt Rauch <mr...@simnet.ca> on 2025/05/01 17:50:19 UTC
SSVM to NFS Secondary Storage on Pure = "Symbolic link not allowed or link target not accessible" when attempting download of ISO
Hello,
As the subject says, we have a new install of Cloudstack and are attempting to use a NFS share in a Pure Storage array for secondary storage. Uploads seem to work OK, as I was able to upload ISO files bia the CloudStack GUI. However, when I attempt to download the same ISO, Cloudstack correctly generates the link, however I get a Forbidden error in the browser:
[cid:image001.png@01DBBA9C.08B4C210]
Looking at the error log on the SSVM, I see Symbolic link not allowed or link target not accessible:
[cid:image002.png@01DBBA9F.FA585160]
File permissions should be good, with 777 on the symlink and the mounted file has 666. Not sure if there are any known issues with using Pure Storage array as backend. It should be standard NFS 4. The fact that we can upload without issue is odd to me, unless it's a different source that writes to the secondary storage then the once that reads from it?
Any help would be appreciated. I'm not working in this issue directly, so if further details are required, I can reach out to our team.
Thank you,
Matt
RE: [EXTERNAL] Re: SSVM to NFS Secondary Storage on Pure = "Symbolic link not allowed or link target not accessible" when attempting download of ISO
Posted by Matt Rauch <mr...@simnet.ca>.
Hello,
This is CloudStack 4.20 with KVM as the hypervisor. We are running our KVM hosts and MGMT Server on Ubuntu 24.024.2 LTS
Thanks,
Matt
-----Original Message-----
From: Wei ZHOU <us...@gmail.com>
Sent: May 1, 2025 2:03 PM
To: users@cloudstack.apache.org
Subject: [EXTERNAL] Re: SSVM to NFS Secondary Storage on Pure = "Symbolic link not allowed or link target not accessible" when attempting download of ISO
What is the ACS version and os distribution ?
We are facing the same issue in our dev for xcpng8.3 and xenserver 8.4 support.
On Thursday, May 1, 2025, Matt Rauch <mr...@simnet.ca> wrote:
> Hello,
>
> As the subject says, we have a new install of Cloudstack and are
> attempting to use a NFS share in a Pure Storage array for secondary
> storage. Uploads seem to work OK, as I was able to upload ISO files
> bia the CloudStack GUI. However, when I attempt to download the same
> ISO, Cloudstack correctly generates the link, however I get a
> Forbidden error in the browser:
>
>
>
> Looking at the error log on the SSVM, I see Symbolic link not allowed
> or link target not accessible:
>
>
>
> File permissions should be good, with 777 on the symlink and the
> mounted file has 666. Not sure if there are any known issues with
> using Pure Storage array as backend. It should be standard NFS 4. The
> fact that we can upload without issue is odd to me, unless it’s a
> different source that writes to the secondary storage then the once that reads from it?
>
>
>
> Any help would be appreciated. I’m not working in this issue directly,
> so if further details are required, I can reach out to our team.
>
>
>
> Thank you,
>
>
>
> Matt
>
Re: SSVM to NFS Secondary Storage on Pure = "Symbolic link not allowed or link target not accessible" when attempting download of ISO
Posted by Wei ZHOU <us...@gmail.com>.
What is the ACS version and os distribution ?
We are facing the same issue in our dev for xcpng8.3 and xenserver 8.4
support.
On Thursday, May 1, 2025, Matt Rauch <mr...@simnet.ca> wrote:
> Hello,
>
> As the subject says, we have a new install of Cloudstack and are
> attempting to use a NFS share in a Pure Storage array for secondary
> storage. Uploads seem to work OK, as I was able to upload ISO files bia the
> CloudStack GUI. However, when I attempt to download the same ISO,
> Cloudstack correctly generates the link, however I get a Forbidden error in
> the browser:
>
>
>
> Looking at the error log on the SSVM, I see Symbolic link not allowed or
> link target not accessible:
>
>
>
> File permissions should be good, with 777 on the symlink and the mounted
> file has 666. Not sure if there are any known issues with using Pure
> Storage array as backend. It should be standard NFS 4. The fact that we can
> upload without issue is odd to me, unless it’s a different source that
> writes to the secondary storage then the once that reads from it?
>
>
>
> Any help would be appreciated. I’m not working in this issue directly, so
> if further details are required, I can reach out to our team.
>
>
>
> Thank you,
>
>
>
> Matt
>