mirror of
https://github.com/proxmoxer/proxmoxer.git
synced 2026-04-25 07:06:00 +03:00
[GH-ISSUE #96] KeyError instead of adequate exception on try to delete a running virtual machine. #47
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#47
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 @ImHereByChance on GitHub (Mar 30, 2022).
Original GitHub issue: https://github.com/proxmoxer/proxmoxer/issues/96
Originally assigned to: @jhollowe on GitHub.
After update to 1.3.0, when I try to delete a running virtual machine using HTTP bacekend, I get a
KeyErrorexception instead ofproxmoxer.core.ResourceExceptionas it was in 1.2.0.it occurs here
because of
response.text == '{"data":null}'and there is no"errors"key in response payload.@meffie commented on GitHub (Apr 4, 2022):
I see the same after upgrading to 1.3.0. Going to pin versions to 1.2.0 for the time being.
@r3d07 commented on GitHub (Apr 26, 2022):
This is not unique to deleting a running VM. For example, I have this issue when issues a
qemu agent pingto a host that is not yet booted. Looking at the code, it appears that this is regression where theerrorfield was expected to be there if a command is not successful -- something that is not necessarily the case.@TimoteusRuotsalainen commented on GitHub (May 10, 2022):
The error message is stated in response.reason
Adding a print debug helped to show the actual error messages
@jhollowe commented on GitHub (May 14, 2022):
Version 1.3.1 is now available in PyPi