Marc,

Does changing the path from .ova to .vmdk help at all? Also, is it a data
volume or a ROOT volume?

Thanks,
-Syed

On Thu, May 4, 2017 at 6:44 AM, Marc Poll Garcia <marc.poll.gar...@upcnet.es
> wrote:

> Hi all,
>
> i'm not able to download a "volume" on cloudstack 4.6, having a 403
> forbidden instead.
>
> I've just upgraded our cloudstack version to 4.6, so i'm performing a list
> of tests to confirm the usage is ok.
>
> My setup is the following one:
>
> - 1 x cloudstack managment server
> - 1 x bbdd server cloudstack database on it
> - 2 x Vmware Hipervisors (hosts)
>
> Everything went well until i tried:
>
> I'm having problems when i try to download a volume, cloudstack creates a
> link like this:
>
> Status
> Please click
> http://147.xxx.xxx.xxx/userdata/f7da105d-627d-473d-868d-bc33fa50777e.ova
> to
> download volume
>
>
> But it points to a directory instead of an "OVA" file, so it shows me a 403
> forbidden on the browser instead of letting me download the file.
>
> That's what i see directly on the system VM:
>
> Symbolik link to the files:
> root@s-210-VM:/var/www/html/userdata# ls -lstha
> 4.0K lrwxrwxrwx 1 root root   99 May  4 10:12
> f7da105d-627d-473d-868d-bc33fa50777e.ova ->
> /mnt/SecStorage/14fbc3c2-3302-3e50-b64e-71737bad431c/volumes/2/354/
> 0c1f6612bee9482a8144276be07d317f
>
>
> As you can see, the path does not contain any OVA file, it's vmdk & .ovf
> stored instead:
> /mnt/SecStorage/14fbc3c2-3302-3e50-b64e-71737bad431c/volumes/2/354/
> 0c1f6612bee9482a8144276be07d317f#
> ls -lstha
> total 84K
> 8.0K -rwxrwxrwx 1 root root 6.3K May  4 10:12
> 0c1f6612bee9482a8144276be07d317f.ovf
> 4.0K drwxrwxrwx 1 root root  168 May  4 10:12 .
>  68K -rwxrwxrwx 1 root root  67K May  4 10:12
> 0c1f6612bee9482a8144276be07d317f-disk0.vmdk
>
> Why is it happening?
> It does not happen on our old 4.5.2 version.
>
> Is there any way to fix it? changing any global parameter or permissions
> issue?
>
> We need a clue with that because if affecting to our production
> environment.
>
> Thanks in advance.
>
> Kind regards.
>

Reply via email to