Can't access NFS shares after upgrade from 4.0 to 4.1

H

hefferbub

Renowned Member
Sep 11, 2010
28
0
66
I have a test server which I installed from scratch using the PVE 4.0 ISO installer a few days ago. It was all working great. I linked to some existing NFS shares to access my iso images and backups and was able to install some VMs.

After I updated to 4.1 on Friday (via apt-get), I started getting the following message when trying to start a VM that references one of those NFS shares for its CD-ROM image:

TASK ERROR: Undefined subroutine &PVE::ProcFSTools::parse_proc_mounts called at /usr/share/perl5/PVE/Storage/NFSPlugin.pm line 120.

The VM fails to start. If I remove the media from the CD-ROM config it starts OK.

I also get this same message when I try to display the content of this NFS storage item.

I removed and recreated the storage item, but that had no effect. I can still access these identical NFS mountpoints from my other PVE servers running 3.x versions.

Is there something different about 4.1 and NFS? Please advise. Thanks!
 
I just updated from 4.0 to 4.1 and attempted to mount old NFS share on FreeNAS 9.3 and got the same error. I attempted to create a new share and got the same error. it shows as mounted at the CLI level and and I can create files on the mounted file system. Perhaps it's a bug?

hefferbub said:
I have a test server which I installed from scratch using the PVE 4.0 ISO installer a few days ago. It was all working great. I linked to some existing NFS shares to access my iso images and backups and was able to install some VMs.

After I updated to 4.1 on Friday (via apt-get), I started getting the following message when trying to start a VM that references one of those NFS shares for its CD-ROM image:

TASK ERROR: Undefined subroutine &PVE::ProcFSTools::parse_proc_mounts called at /usr/share/perl5/PVE/Storage/NFSPlugin.pm line 120.

The VM fails to start. If I remove the media from the CD-ROM config it starts OK.

I also get this same message when I try to display the content of this NFS storage item.

I removed and recreated the storage item, but that had no effect. I can still access these identical NFS mountpoints from my other PVE servers running 3.x versions.

Is there something different about 4.1 and NFS? Please advise. Thanks!
Click to expand...
 
Last edited:
I see the problem.

when I ran apt at the CLI i saw the following


QUOTED TEXT:
The following packages have been kept back:
libpve-common-perl proxmox-ve




spirit said:
seem to be a bug in nfs plugin , introduced in this commit:



#are you sure that all packages has been updated ? (#pveversion -v ) ?

you can check in /usr/share/perl5/PVE/ProcFSTools.pm , if you have parse_proc_mounts()
Click to expand...
 
Here is the pveversion -v output from my system:

root@superserver:~# pveversion -v
proxmox-ve: 4.0-16 (running kernel: 4.2.2-1-pve)
pve-manager: 4.1-1 (running version: 4.1-1/2f9650d4)
pve-kernel-4.2.2-1-pve: 4.2.2-16
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 0.17.2-1
pve-cluster: 4.0-29
qemu-server: 4.0-41
pve-firmware: 1.1-7
libpve-common-perl: 4.0-29
libpve-access-control: 4.0-10
libpve-storage-perl: 4.0-38
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.4-17
pve-container: 1.0-32
pve-firewall: 2.0-14
pve-ha-manager: 1.0-14
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u1
lxc-pve: 1.1.5-5
lxcfs: 0.13-pve1
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5-pve6~jessie
Click to expand...

When I do an apt-get update/upgrade, it shows:

root@superserver:~# apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
libpve-common-perl proxmox-ve
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
Click to expand...

Not sure why those are held back.

When I search /usr/share/perl5/PVE/ProcFSTools.pm, I don't see parse_proc_mounts.

Jeff
 
Sorry, my bad. Doing a "dist-upgrade" instead of the "upgrade" fixed the problem.

Thanks for the quick reminder.

Jeff
 
You must log in or register to reply here.
Top Bottom