Skip to content

bug: crash on vm_stop|start|etc routes when vm_id does not exist #31

@hyde-repo

Description

@hyde-repo

Handle the case where vm_id does not exist before proceeding with vm_start|stop|resume etc.

TASK [range42-ansible_roles-proxmox_controller : VM STOP - FORCE POWER OFF - FETCH STATUS] ***
[ERROR]: Task failed: Module failed: Status code was 500 and not [200]: HTTP Error 500: Configuration file 'nodes/px-testing/qemu-server/4001.conf' does not exist
Origin: /redacted/range42-ansible_roles-proxmox_controller/roles/range42-ansible_roles-proxmox_controller/tasks/include/vm/vm_stop_force.yaml:24:7

22     ####
23
24     - name: VM STOP - FORCE POWER OFF - FETCH STATUS
         ^ column 7
fatal: [px-testing]: FAILED! => {"cache_control": "max-age=0", "changed": false, "connection": "close", "content_length": "13", "content_type": "application/json;charset=UTF-8", "date": "Mon, 22 Sep 2025 13:09:02 GMT", "elapsed": 0, "expires": "Mon, 22 Sep 2025 13:09:02 GMT", "json": {"data": null}, "msg": "Status code was 500 and not [200]: HTTP Error 500: Configuration file 'nodes/px-testing/qemu-server/4001.conf' does not exist", "pragma": "no-cache", "redirected": false, "server": "pve-api-daemon/3.0", "status": 500, "url": "https://127.0.0.1:18007/api2/json/nodes/px-testing/qemu/4001/status/current"}

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions