Storage NFS template and Upload button greyed out

Et192

New Member
Mar 2, 2017
3
0
1
39
Hello everyone,

i am having a problem with a proxmox installation, i am a newbie with proxmox, it is possible i have messed something up.
I have installed proxmox on three servers and i have created a cluster. After that i added a NFS storage model NAS NX3220 with Windows Storage Server. On the nas i have created the volumes which i shared with NFS, and on the NFS share i have enabled the IP of each server with writing and root permission (shares.png).

After that i have added the storage NFS from the Proxmox Gui Cluster (cluster.png). But the problem is that when i go the the storage the template dhe upload button are greyed out, when i click at first they are enabled for a couple of seconds (clusterclick.png) than after that they become greyed out (clusterafter.png).

I i click template before it becomes greyed out it gives me the template windows and when i click downlod it says: Storage 'Name' does not support templates (500) (template.png).

Also i tried to create a machine on that storage, it created the disk for the machine but it did not add the machine, also the options for removing the disk that it added are greyed out (remove.png).

I tried also to click fast also on the upload button and it gives the upload window, and after upload finished it show nothing.


On syslog i have some kind of warnign: cat /var/log/syslog

Mar 2 15:14:13 srv2 pveproxy[153750]: unable to open file '/var/lib/pve-manager/apl-info/releases.turnkeylinux.org' - No such file or directory
Mar 2 15:14:19 srv2 pvedaemon[2303]: unable to open file '/var/lib/pve-manager/apl-info/releases.turnkeylinux.org' - No such file or directory

Here are the output of some pve commands on the cluster of the machines:

root@srv1:~# pveversion -v
proxmox-ve: 4.4-76 (running kernel: 4.4.35-1-pve)
pve-manager: 4.4-1 (running version: 4.4-1/eb2d6f1e)
pve-kernel-4.4.35-1-pve: 4.4.35-76
lvm2: 2.02.116-pve3
corosync-pve: 2.4.0-1
libqb0: 1.0-1
pve-cluster: 4.0-48
qemu-server: 4.0-101
pve-firmware: 1.1-10
libpve-common-perl: 4.0-83
libpve-access-control: 4.0-19
libpve-storage-perl: 4.0-70
pve-libspice-server1: 0.12.8-1
vncterm: 1.2-1
pve-docs: 4.4-1
pve-qemu-kvm: 2.7.0-9
pve-container: 1.0-88
pve-firewall: 2.0-33
pve-ha-manager: 1.0-38
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u2
lxc-pve: 2.0.6-2
lxcfs: 2.0.5-pve1
criu: 1.6.0-1
novnc-pve: 0.5-8
smartmontools: 6.5+svn4324-1~pve80
zfsutils: 0.6.5.8-pve13~bpo80


root@srv2:~# pveversion -v
proxmox-ve: 4.4-76 (running kernel: 4.4.35-1-pve)
pve-manager: 4.4-1 (running version: 4.4-1/eb2d6f1e)
pve-kernel-4.4.35-1-pve: 4.4.35-76
lvm2: 2.02.116-pve3
corosync-pve: 2.4.0-1
libqb0: 1.0-1
pve-cluster: 4.0-48
qemu-server: 4.0-101
pve-firmware: 1.1-10
libpve-common-perl: 4.0-83
libpve-access-control: 4.0-19
libpve-storage-perl: 4.0-70
pve-libspice-server1: 0.12.8-1
vncterm: 1.2-1
pve-docs: 4.4-1
pve-qemu-kvm: 2.7.0-9
pve-container: 1.0-88
pve-firewall: 2.0-33
pve-ha-manager: 1.0-38
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u2
lxc-pve: 2.0.6-2
lxcfs: 2.0.5-pve1
criu: 1.6.0-1
novnc-pve: 0.5-8
smartmontools: 6.5+svn4324-1~pve80
zfsutils: 0.6.5.8-pve13~bpo80

root@srv4:~# pveversion -v
proxmox-ve: 4.4-76 (running kernel: 4.4.35-1-pve)
pve-manager: 4.4-1 (running version: 4.4-1/eb2d6f1e)
pve-kernel-4.4.35-1-pve: 4.4.35-76
lvm2: 2.02.116-pve3
corosync-pve: 2.4.0-1
libqb0: 1.0-1
pve-cluster: 4.0-48
qemu-server: 4.0-101
pve-firmware: 1.1-10
libpve-common-perl: 4.0-83
libpve-access-control: 4.0-19
libpve-storage-perl: 4.0-70
pve-libspice-server1: 0.12.8-1
vncterm: 1.2-1
pve-docs: 4.4-1
pve-qemu-kvm: 2.7.0-9
pve-container: 1.0-88
pve-firewall: 2.0-33
pve-ha-manager: 1.0-38
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u2
lxc-pve: 2.0.6-2
lxcfs: 2.0.5-pve1
criu: 1.6.0-1
novnc-pve: 0.5-8
smartmontools: 6.5+svn4324-1~pve80
zfsutils: 0.6.5.8-pve13~bpo80


root@srv1:~# cat /etc/pve/storage.cfg
dir: local
path /var/lib/vz
content backup,vztmpl,iso

lvmthin: local-lvm
thinpool data
vgname pve
content rootdir,images

nfs: SAS11TB
export /11TBNASNXRG9
path /mnt/pve/SAS11TB
server 192.168.10.201
maxfiles 1
options vers=3
content images

nfs: SATA8TB
export /SATA8TB
path /mnt/pve/SATA8TB
server 192.168.10.201
maxfiles 1
options vers=3
content images

root@srv1:~# pvs
PV VG Fmt Attr PSize PFree
/dev/sda3 pve lvm2 a-- 59.51g 7.31g

root@srv1:~# vgs
VG #PV #LV #SN Attr VSize VFree
pve 1 3 0 wz--n- 59.51g 7.31g

root@srv1:~# lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
data pve twi-a-tz-- 30.02g 0.00 0.48
root pve -wi-ao---- 14.75g
swap pve -wi-ao---- 7.38g

root@srv1:~# df -h
Filesystem Size Used Avail Use% Mounted on
udev 10M 0 10M 0% /dev
tmpfs 26G 9.1M 26G 1% /run
/dev/dm-0 15G 8.4G 5.4G 61% /
tmpfs 63G 69M 63G 1% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 63G 0 63G 0% /sys/fs/cgroup
/dev/fuse 30M 24K 30M 1% /etc/pve
192.168.10.201:/11TBNASNXRG9 11T 41G 11T 1% /mnt/pve/SAS11TB
192.168.10.201:/SATA8TB 7.3T 928M 7.3T 1% /mnt/pve/SATA8TB

Does any of you guys have any idea on what it could be the problem?

Thank you in advance.
 

Attachments

  • shares.png
    shares.png
    44.8 KB · Views: 17
  • cluster.png
    cluster.png
    181.6 KB · Views: 16
  • clusterafter.png
    clusterafter.png
    108.7 KB · Views: 15
  • clusterclick.png
    clusterclick.png
    107 KB · Views: 12
  • remove.png
    remove.png
    104.6 KB · Views: 12
  • template.png
    template.png
    150 KB · Views: 13
nfs: SATA8TB
export /SATA8TB
path /mnt/pve/SATA8TB
server 192.168.10.201
maxfiles 1
options vers=3
content images

This storage is only for the content type "images".

If you want to store templates on this storage, you need to enables this (Datacenter/Storage/SATA8TB: add "Container template")

In order to force a download of available TKL container templates, run via CLI:

> pveam update
 
  • Like
Reactions: GazB and Et192
This storage is only for the content type "images".

If you want to store templates on this storage, you need to enables this (Datacenter/Storage/SATA8TB: add "Container template")

In order to force a download of available TKL container templates, run via CLI:

> pveam update
Thank you very much, everything is working now, as you said i had set the storage as Image only, i made the modification to allow also the templates.
:)
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!