`pvenode acme plugin list` fails with “400 Result verification failed”

R

reitermarkus

Member
Nov 6, 2021
10
1
8
On one of my nodes, running pvenode acme plugin list results in

Code: 
400 Result verification failed
[0].digest: property is not defined in schema and the schema does not allow additional properties
[1].id: property is missing and it is not optional
[1].plugin: property is not defined in schema and the schema does not allow additional properties
[0].id: property is missing and it is not optional
[0].plugin: property is not defined in schema and the schema does not allow additional properties
[1].digest: property is not defined in schema and the schema does not allow additional properties
pvenode acme plugin list  [OPTIONS] [FORMAT_OPTIONS]

/etc/pve/priv/acme/plugins.cfg contains

Code: 
dns: cloudflare
    api cf
    data ***REDACTED***

standalone: standalone

Not sure where the wrong schema is located or if there is a way to reset the ACME configuration completely.
 
What's the output of pvesh get /cluster/acme/plugins --output-format json-pretty
What's the output of pveversion -v?
 
pvesh get /cluster/acme/plugins --output-format json-pretty

JSON: 
[
   {
      "digest" : "b717647fa8433038c067ac8ed2665daae8a411a3",
      "plugin" : "standalone",
      "type" : "standalone"
   },
   {
      "api" : "cf",
      "data" : "CF_Token=***\n\n",
      "digest" : "b717647fa8433038c067ac8ed2665daae8a411a3",
      "plugin" : "cloudflare",
      "type" : "dns"
   }
]

pveversion -v

Code: 
proxmox-ve: 9.0.0 (running kernel: 6.14.11-4-pve)
pve-manager: 9.0.11 (running version: 9.0.11/3bf5476b8a4699e2)
proxmox-kernel-helper: 9.0.4
pve-kernel-5.19: 7.2-15
proxmox-kernel-6.14.11-4-pve-signed: 6.14.11-4
proxmox-kernel-6.14: 6.14.11-4
proxmox-kernel-6.14.11-2-pve-signed: 6.14.11-2
proxmox-kernel-6.8.12-14-pve-signed: 6.8.12-14
proxmox-kernel-6.8: 6.8.12-14
pve-kernel-5.19.17-2-pve: 5.19.17-2
pve-kernel-5.15.35-1-pve: 5.15.35-3
pve-kernel-5.13.19-1-pve: 5.13.19-3
amd64-microcode: 3.20250311.1
ceph: 19.2.3-pve2
ceph-fuse: 19.2.3-pve2
corosync: 3.1.9-pve2
criu: 4.1.1-1
frr-pythontools: 10.3.1-1+pve4
ifupdown2: 3.3.0-1+pmx10
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libproxmox-acme-perl: 1.7.0
libproxmox-backup-qemu0: 2.0.1
libproxmox-rs-perl: 0.4.1
libpve-access-control: 9.0.3
libpve-apiclient-perl: 3.4.0
libpve-cluster-api-perl: 9.0.6
libpve-cluster-perl: 9.0.6
libpve-common-perl: 9.0.11
libpve-guest-common-perl: 6.0.2
libpve-http-server-perl: 6.0.4
libpve-network-perl: 1.1.8
libpve-rs-perl: 0.10.10
libpve-storage-perl: 9.0.13
libspice-server1: 0.15.2-1+b1
lvm2: 2.03.31-2+pmx1
lxc-pve: 6.0.5-1
lxcfs: 6.0.4-pve1
novnc-pve: 1.6.0-3
proxmox-backup-client: 4.0.16-1
proxmox-backup-file-restore: 4.0.16-1
proxmox-backup-restore-image: 1.0.0
proxmox-firewall: 1.2.0
proxmox-kernel-helper: 9.0.4
proxmox-mail-forward: 1.0.2
proxmox-mini-journalreader: 1.6
proxmox-offline-mirror-helper: 0.7.2
proxmox-widget-toolkit: 5.0.6
pve-cluster: 9.0.6
pve-container: 6.0.13
pve-docs: 9.0.8
pve-edk2-firmware: 4.2025.02-4
pve-esxi-import-tools: 1.0.1
pve-firewall: 6.0.3
pve-firmware: 3.17-2
pve-ha-manager: 5.0.5
pve-i18n: 3.6.1
pve-qemu-kvm: 10.0.2-4
pve-xtermjs: 5.5.0-2
qemu-server: 9.0.23
smartmontools: 7.4-pve1
spiceterm: 3.4.1
swtpm: 0.8.0+pve2
vncterm: 1.9.1
zfsutils-linux: 2.3.4-pve1
 
As the API is working, the issue might be in pvenode.
The pve packages seem recent to me, but you might try an apt update && apt full-upgrade anyway.
If it doesn't help, you can either use eventually booked support or file a bug at https://bugzilla.proxmox.com
 
Okay,

I tried apt update && apt full-upgrade, but there was nothing to upgrade.

I then did the same on another node, and pvenode acme plugin list was broken in the same way afterwards.

I downgraded some packages, and it looks like pve-manager 9.0.11 is broken. Downgrading with apt install pve-manager=9.0.10 fixes the problem.
 
  • Like
Reactions: fba
  • Like
Reactions: fba
You must log in or register to reply here.
Top Bottom