pvesh error - API issue?

[starnetwork]

Hi,
after I could not to connect to some server via api I logged-in to the server and did
# pvesh
pve:/> help
and got the error:
Use of uninitialized value in string comparison (cmp) at /usr/bin/pvesh line 326.

this was for about 40 lines with same line and than:

Use of uninitialized value $path in substitution (s///) at /usr/bin/pvesh line 333.
Use of uninitialized value $path in concatenation (.) or string at /usr/bin/pvesh line 337.
create -storage <string> -type <string> [OPTIONS]
Use of uninitialized value $path in substitution (s///) at /usr/bin/pvesh line 333.
Use of uninitialized value $path in concatenation (.) or string at /usr/bin/pvesh line 337.
create -poolid <string> [OPTIONS]
Use of uninitialized value $path in substitution (s///) at /usr/bin/pvesh line 333.
Use of uninitialized value $path in concatenation (.) or string at /usr/bin/pvesh line 337.
get

anyway know what to do?

best regards,
Star Network.

 

[dietmar]

anyway know what to do?

This is already fixed in git, so the fix is included with the next release.

 

[starnetwork]

This is already fixed in git, so the fix is included with the next release.

Hi, just did update to 2.6.32-30, didn't work yet...

 

[tom]

a new kernel does not update the api, so I assume you need to wait a bit more here (or apply the git fixes by yourself).

 

[joelserrano]

a new kernel does not update the api, so I assume you need to wait a bit more here (or apply the git fixes by yourself).

Hi,

When the pve-manager package (where pvesh comes from) gets updated, will a server reboot be required?

I mean, do pve-manager updates come together with kernel updates and therefor require server reboot?

Best regards,
Joel.

 

[tom]

no reboot needed (for a new pve-manager package)

 

[joelserrano]

Thank you Tom!

I will wait until de updated package is released then...

Best regards,
Joel.

 

[Martin Cleaver]

Hi,

When's the updated package likely to be released?
I found the commit from May here: https://github.com/proxmox/pve-manager/commit/1a0a454209aac73fe1d6fa4a09650cb1d4df64fd
Looks from https://github.com/proxmox/pve-manager/commits/master/bin/pvesh that the previous was back in October so it's relatively stable.

But it's not sufficient to pull only that one file - from reading the above (and trying the updated file locally) I gather it's not just that file that changed: it is dependent on the kernel update as well.

Thanks,
Martin.

 

[Martin Cleaver]

This seems to be fixed in 3.3