Commit 3e7d9fac in the qemu-server.git repo added the message. There are some other printed messages printed to STDOUT however, so I don't think this is a new issue.
I guess the simplest solution would be to redirect STDOUT to STDERR in pvesh.pm during the API call. Something like this in sub...
@fabian, any update on this?
I could have a look myself, but last time I checked I couldn't quite figure out where the source code for the pvesh command is located. Would be great if you could point me to it.
For context, I came across this while implementing https://github.com/ansible-collections/community.general/pull/4027. It is much more convenient to use pvesh when you're already SSH'd into a node via Ansible rather than having to provide separate credentials, so it would be great if it was...
I'll try on another node, but all nodes are on the same version already.
Last time I know it worked was in February, so probably whichever 7.1 version was the latest in February would work.
The API documentation says that this request returns a string. It did previously, but it seems some update broke this.
It should return the Task ID as a JSON string. It now returns a plain text string before the JSON string, e.g. running
pvesh create /nodes/net2-pve/qemu -vmid 7777 -name yolo...
I also just tried setting up auth0 and am getting the same error:
OpenID login failed, please try again
authentication failure (401)
I am successfully authenticated and redirected back to PVE, but hitting the message above.
I have enabled “Autocreate Users” and I also tried with all three...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.