Target storage button disabled

[ioanv]

Hi all

I'm using proxmox for about an year for hosting linux VM's on top un a 4 node cluster with nfs shares on synology NAS. However this is the first time tu see the following behaviour:

Right clink on a virtual machine --> Clone --> Target storage and format grayed out.

Also Create VM stops in the forth tab Hard Disk as the item storage is grayed out and i cannot select any value.

Until few days ago everything worked fine, I have avout 20 VM's running in the cluster.

Any thoughts?

Best regards
Vlad

PS PVE Version 3.1-21

 

[spirit]

Hi, is it from the menu in the left tree ? or from the grid ?

this last one has been fixed in proxmox 3.2 if I remember.

 

[ioanv]

Hi, thanks for the quick reply.

Clone is done through right click on machine in left hand side tree.
Create VM is done through button right side upper corner.

Interesting enough, i have observed the following:

1. Also restoring a VM from backup had the storage section grayed out

2. I added a new nfs storage in order to do some recovery tests.
So:
- the nfs shares for each server (nfs_vm1, nfs_vm2, etc) are on syno1.
- the backup is on syno2 (also a nfs share).
- the new nfs share where i was trying to restore a VM was on syno2 (nfs_vm1recovery).

As soon as i have removed the new share for recovery tests (nfs_vm1recovery), the clone and New VM became possible again (no grayed out button).
What can be the meaning of this?

 

[spirit]

Seem that the gui is hanging when trying to get infos from storages.

Are all yours storage reachables from each node ?

If no, do you have defined the nodes on which the storage is reachable ?

 

[ioanv]

That was my thought too however the backup folder which also resides on syno2 is perfectlly accessible. As soon as I delete the nfs_vm1recovery i am able again to declare VM, to clone VMs and to restore backups.

Today i've tried to make the recovery nfs share o a third syno and I had no problem using it (create, clone, restore VM in it). So apparently the only problem is when I declare a new nfs share from the second syno.