mirror of
https://github.com/proxmoxer/proxmoxer.git
synced 2026-04-25 07:06:00 +03:00
[GH-ISSUE #72] Python3 export pve-cluster info 400 Bad Request #37
Labels
No labels
backend:https
backend:local
backend:openssh
backend:ssh_paramiko
pull-request
status:ansible-issue
status:help-wanted
status:info-needed
status:proxmox-issue
status:review-needed
type:bug 🐞
type:dependency ⛓️
type:docs 📝
type:enhancement ⏫
type:maintenance 🛠️
type:meta
type:question ❓
type:request ✋
type:testing 🧪
version:1.x
version:latest
version:py2
version:py3
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/proxmoxer#37
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @uranus829 on GitHub (Nov 4, 2021).
Original GitHub issue: https://github.com/proxmoxer/proxmoxer/issues/72
Originally assigned to: @jhollowe on GitHub.
I wrote a python script to export the pve cluster cluster information, but this script can be exported before, but now it can’t be executed, please help me take a look?I did not find any exceptions in this sentence, because this script is in another version with the same pve It can be executed under the cluster. Please help, thanks.
python3 list-pool.py
@jhollowe commented on GitHub (Nov 5, 2021):
Just to confirm, you can run the script with proxmoxer<1.2.0 and it works but running proxmoxer==1.2.0 on the exact same PVE causes the above error?
@jhollowe commented on GitHub (Nov 5, 2021):
Are you able to determine what VMID the script is failing on? try adding a
print(vm['vmid'])right before the failing call.Once you have the ID that it crashes on, please run
qm config <the_vm_id>on the node. From some Google-ing, it looks like this is not a problem with proxmoxer but is an error that PVE is throwing due to a problem with a VM config.@uranus829 commented on GitHub (Nov 5, 2021):
@jhollowe Hi,This problem has been solved, the script can be executed by adding the print statement and deleting it. It is not a problem with proxmoxer, thanks!