[SOLVED] GUI add zfs storage: verification failed (400) config type check ('object') failed

M

Morphushka

Well-Known Member
Jun 25, 2019
49
7
48
35
Syberia
Hello.
Code: 
pve-manager/6.3-2/22f57405 (running kernel: 5.4.73-1-pve)
No update available.
When I try to add storage and hit "add" button then error occures (screenshot). Behind this dialog I see storage added in tree view successfully.
Close dialog. Storage works as usual.
Is it bug ?
 

Attachments

  • zfs-add-failed-gui.jpg
    zfs-add-failed-gui.jpg
    80.7 KB · Views: 113
Hi,
this should be fixed in pve-storage 6.2-11 and later, please upgrade.

EDIT: Hm, seems like not everything was fixed there. I can reproduce this here. Thanks for the report!
 
Last edited:
FYI, a fix for this is applied now in git and should be available with the next libpve-storage-perl version.
Luckily the issue is only cosmetic, i.e. the actual configuration for the storage should be fine.
 
Fabian_E said:
FYI, a fix for this is applied now in git and should be available with the next libpve-storage-perl version.
Luckily the issue is only cosmetic, i.e. the actual configuration for the storage should be fine.
Click to expand...
Just a heads up, I did this on a fresh system installed today and got the same message

1613190080418.png
 
Fabian_E said:
FYI, a fix for this is applied now in git and should be available with the next libpve-storage-perl version.
Luckily the issue is only cosmetic, i.e. the actual configuration for the storage should be fine.
Click to expand...

poldim said:
Just a heads up, I did this on a fresh system installed today and got the same message

View attachment 23601
Click to expand...

Funny, literally just encountered this issue and found this post as soon as you made it @poldim

Same issue here. Fresh install. Ran an apt update, installed dark theme, cleared disks, got the same error.

@Fabian_E More than happy to provide any information that would help address this if necessary.
1613191231232.png
1613191132347.png
 
@poldim @arjviii I personally (and not just I) recommend to work with zfs from console: it is clear what happening and flexible. Use proxmox for virtualization purpose only. Adding storage works well for me.

proxmox-ve: 6.3-1 (running kernel: 5.4.78-2-pve) pve-manager: 6.3-3 (running version: 6.3-3/eee5f901) pve-kernel-5.4: 6.3-3 pve-kernel-helper: 6.3-3 pve-kernel-5.4.78-2-pve: 5.4.78-2 pve-kernel-5.4.73-1-pve: 5.4.73-1 ceph-fuse: 12.2.11+dfsg1-2.1+b1 corosync: 3.0.4-pve1 criu: 3.11-3 glusterfs-client: 5.5-3 ifupdown: not correctly installed ifupdown2: 3.0.0-1+pve3 ksm-control-daemon: 1.3-1 libjs-extjs: 6.0.1-10 libknet1: 1.16-pve1 libproxmox-acme-perl: 1.0.7 libproxmox-backup-qemu0: 1.0.2-1 libpve-access-control: 6.1-3 libpve-apiclient-perl: 3.1-3 libpve-common-perl: 6.3-2 libpve-guest-common-perl: 3.1-3 libpve-http-server-perl: 3.1-1 libpve-storage-perl: 6.3-3 libqb0: 1.0.5-1 libspice-server1: 0.14.2-4~pve6+1 lvm2: 2.03.02-pve4 lxc-pve: 4.0.3-1 lxcfs: 4.0.3-pve3 novnc-pve: 1.1.0-1 proxmox-backup-client: 1.0.6-1 proxmox-mini-journalreader: 1.1-1 proxmox-widget-toolkit: 2.4-3 pve-cluster: 6.2-1 pve-container: 3.3-2 pve-docs: 6.3-1 pve-edk2-firmware: 2.20200531-1 pve-firewall: 4.1-3 pve-firmware: 3.1-3 pve-ha-manager: 3.1-1 pve-i18n: 2.2-2 pve-qemu-kvm: 5.1.0-7 pve-xtermjs: 4.7.0-3 qemu-server: 6.3-2 smartmontools: 7.1-pve2 spiceterm: 3.1-1 vncterm: 1.6-2 zfsutils-linux: 0.8.5-pve1
 
Hi,
poldim said:
Just a heads up, I did this on a fresh system installed today and got the same message

View attachment 23601
Click to expand...
yes, this issue is present with the version from the ISO. But it's only cosmetic, i.e. the storage will still get created.

arjviii said:
Funny, literally just encountered this issue and found this post as soon as you made it @poldim

Same issue here. Fresh install. Ran an apt update, installed dark theme, cleared disks, got the same error.

@Fabian_E More than happy to provide any information that would help address this if necessary.
Click to expand...
Did you also run apt full-upgrade to install the update for libpve-storage-perl? apt update will only fetch the package metadata (to see if there are new versions), but not the packages themselves.

Note that if you don't have a subscription key, you'll have to configure the no-subscription repository first.
 
Fabian_E said:
Did you also run apt full-upgrade to install the update for libpve-storage-perl? apt update will only fetch the package metadata (to see if there are new versions), but not the packages themselves.
Click to expand...
For your information:
I have the same error. I had run apt update and apt upgrade before and now apt full-upgrade to check. I still got the error.
ZFS drive also works fine.
 
Hi,
Zalatschenko said:
For your information:
I have the same error. I had run apt update and apt upgrade before and now apt full-upgrade to check. I still got the error.
ZFS drive also works fine.
Click to expand...
could you share the output of pveversion -v? Which APT repositories are configured?
 
Hi,
I have a similar problem. Fresh installation from latest Proxmox .iso, zfs pool created from cli and work fine, configured "No-Subscription Repository", apt update + apt full-upgrade didn't found any new updates.
When i try get information about pool status from web i get error "Result verification failed (400)":
1617360293457.png

Code: 
proxmox-ve: 6.3-1 (running kernel: 5.4.106-1-pve)
pve-manager: 6.3-6 (running version: 6.3-6/2184247e)
pve-kernel-5.4: 6.3-8
pve-kernel-helper: 6.3-8
pve-kernel-5.4.106-1-pve: 5.4.106-1
pve-kernel-5.4.73-1-pve: 5.4.73-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.1.0-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: residual config
ifupdown2: 3.0.0-1+pve3
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.20-pve1
libproxmox-acme-perl: 1.0.8
libproxmox-backup-qemu0: 1.0.3-1
libpve-access-control: 6.1-3
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.3-5
libpve-guest-common-perl: 3.1-5
libpve-http-server-perl: 3.1-1
libpve-storage-perl: 6.3-7
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.6-2
lxcfs: 4.0.6-pve1
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.0.12-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.4-9
pve-cluster: 6.2-1
pve-container: 3.3-4
pve-docs: 6.3-1
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-3
pve-firmware: 3.2-2
pve-ha-manager: 3.1-1
pve-i18n: 2.3-1
pve-qemu-kvm: 5.2.0-5
pve-xtermjs: 4.7.0-3
qemu-server: 6.3-10
smartmontools: 7.2-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 2.0.4-pve1
 
Hi,
alex.zt said:
Hi,
I have a similar problem. Fresh installation from latest Proxmox .iso, zfs pool created from cli and work fine, configured "No-Subscription Repository", apt update + apt full-upgrade didn't found any new updates.
When i try get information about pool status from web i get error "Result verification failed (400)":
View attachment 24939

Code: 
proxmox-ve: 6.3-1 (running kernel: 5.4.106-1-pve)
pve-manager: 6.3-6 (running version: 6.3-6/2184247e)
pve-kernel-5.4: 6.3-8
pve-kernel-helper: 6.3-8
pve-kernel-5.4.106-1-pve: 5.4.106-1
pve-kernel-5.4.73-1-pve: 5.4.73-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.1.0-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: residual config
ifupdown2: 3.0.0-1+pve3
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.20-pve1
libproxmox-acme-perl: 1.0.8
libproxmox-backup-qemu0: 1.0.3-1
libpve-access-control: 6.1-3
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.3-5
libpve-guest-common-perl: 3.1-5
libpve-http-server-perl: 3.1-1
libpve-storage-perl: 6.3-7
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.6-2
lxcfs: 4.0.6-pve1
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.0.12-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.4-9
pve-cluster: 6.2-1
pve-container: 3.3-4
pve-docs: 6.3-1
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-3
pve-firmware: 3.2-2
pve-ha-manager: 3.1-1
pve-i18n: 2.3-1
pve-qemu-kvm: 5.2.0-5
pve-xtermjs: 4.7.0-3
qemu-server: 6.3-10
smartmontools: 7.2-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 2.0.4-pve1
Click to expand...
I think this is a different issue, see here. We do have patches for this already, should be available with pve-manager >= 6.3-6 and libpve-storage-perl >= 6.3-8, but the latter package is not available yet (currently we are doing internal testing).
 
  • Like
Reactions: alex.zt
Zalatschenko said:
For your information:
I have the same error. I had run apt update and apt upgrade before and now apt full-upgrade to check. I still got the error.
ZFS drive also works fine.
Click to expand...
Same here. I'm using the latest ProxMox, apt-get upgrade to the latest, but still, I'm reiving "TASK ERROR: 400 Result verification failed config: type check ('object') failed".
 
Hi,
nedko said:
Same here. I'm using the latest ProxMox, apt-get upgrade to the latest, but still, I'm reiving "TASK ERROR: 400 Result verification failed config: type check ('object') failed".
Click to expand...
please share the output of pveversion -v. Where/when exactly does the error show up?
 
Hi @Fabian_E


Code: 
root@vortex:~# pveversion -v
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
    LANGUAGE = (unset),
    LC_ALL = (unset),
    LC_ADDRESS = "bg_BG.UTF-8",
    LC_NAME = "bg_BG.UTF-8",
    LC_MONETARY = "bg_BG.UTF-8",
    LC_PAPER = "bg_BG.UTF-8",
    LC_IDENTIFICATION = "bg_BG.UTF-8",
    LC_TELEPHONE = "bg_BG.UTF-8",
    LC_MEASUREMENT = "bg_BG.UTF-8",
    LC_TIME = "bg_BG.UTF-8",
    LC_NUMERIC = "bg_BG.UTF-8",
    LANG = "en_US.UTF-8"
    are supported and installed on your system.
perl: warning: Falling back to a fallback locale ("en_US.UTF-8").
proxmox-ve: 6.3-1 (running kernel: 5.4.73-1-pve)
pve-manager: 6.3-2 (running version: 6.3-2/22f57405)
pve-kernel-5.4: 6.3-1
pve-kernel-helper: 6.3-1
pve-kernel-5.4.73-1-pve: 5.4.73-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.4-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.16-pve1
libproxmox-acme-perl: 1.0.5
libproxmox-backup-qemu0: 1.0.2-1
libpve-access-control: 6.1-3
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.2-6
libpve-guest-common-perl: 3.1-3
libpve-http-server-perl: 3.0-6
libpve-storage-perl: 6.3-1
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.3-1
lxcfs: 4.0.3-pve3
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.0.5-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.4-3
pve-cluster: 6.2-1
pve-container: 3.3-1
pve-docs: 6.3-1
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-3
pve-firmware: 3.1-3
pve-ha-manager: 3.1-1
pve-i18n: 2.2-2
pve-qemu-kvm: 5.1.0-7
pve-xtermjs: 4.7.0-3
qemu-server: 6.3-1
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 0.8.5-pve1


Steps to reproduce
1. Log in as an administrative user;
2. Go to Datacenter - node that I would like to create my pool;
3. Open "ZFS" menu item and click "Create: ZFS";
4. Choose two drives in `mirror` and click "Create"

Result
I got TASK ERROR: 400 Result verification failed config: type check ('object') failed.

Notes
Note that the pool appears, but when I try to create new VM the "Resource pool" is empty.
 
nedko said:
Hi @Fabian_E


Code: 
root@vortex:~# pveversion -v
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
    LANGUAGE = (unset),
    LC_ALL = (unset),
    LC_ADDRESS = "bg_BG.UTF-8",
    LC_NAME = "bg_BG.UTF-8",
    LC_MONETARY = "bg_BG.UTF-8",
    LC_PAPER = "bg_BG.UTF-8",
    LC_IDENTIFICATION = "bg_BG.UTF-8",
    LC_TELEPHONE = "bg_BG.UTF-8",
    LC_MEASUREMENT = "bg_BG.UTF-8",
    LC_TIME = "bg_BG.UTF-8",
    LC_NUMERIC = "bg_BG.UTF-8",
    LANG = "en_US.UTF-8"
    are supported and installed on your system.
perl: warning: Falling back to a fallback locale ("en_US.UTF-8").
proxmox-ve: 6.3-1 (running kernel: 5.4.73-1-pve)
pve-manager: 6.3-2 (running version: 6.3-2/22f57405)
pve-kernel-5.4: 6.3-1
pve-kernel-helper: 6.3-1
pve-kernel-5.4.73-1-pve: 5.4.73-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.4-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.16-pve1
libproxmox-acme-perl: 1.0.5
libproxmox-backup-qemu0: 1.0.2-1
libpve-access-control: 6.1-3
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.2-6
libpve-guest-common-perl: 3.1-3
libpve-http-server-perl: 3.0-6
libpve-storage-perl: 6.3-1
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.3-1
lxcfs: 4.0.3-pve3
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.0.5-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.4-3
pve-cluster: 6.2-1
pve-container: 3.3-1
pve-docs: 6.3-1
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-3
pve-firmware: 3.1-3
pve-ha-manager: 3.1-1
pve-i18n: 2.2-2
pve-qemu-kvm: 5.1.0-7
pve-xtermjs: 4.7.0-3
qemu-server: 6.3-1
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 0.8.5-pve1
Click to expand...
The latest available version of pve-manager should be 6.3-6. Please see this earlier post for how to configure repositories and actually upgrade (you'll either need a subscription key or configure the no-subscription repository).

nedko said:
Steps to reproduce
1. Log in as an administrative user;
2. Go to Datacenter - node that I would like to create my pool;
3. Open "ZFS" menu item and click "Create: ZFS";
4. Choose two drives in `mirror` and click "Create"

Result
I got TASK ERROR: 400 Result verification failed config: type check ('object') failed.
Click to expand...


nedko said:
Notes
Note that the pool appears, but when I try to create new VM the "Resource pool" is empty.
Click to expand...
A resource pool is not the same as a storage in PVE. It can be used to create a logical group of VMs/storages with it's own set of access rights. You don't need to select a resource pool to create a VM. The storage for the VMs disk is selected during the Hard Disk step of the VM creation widget.
 
  • Like
Reactions: nedko
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back