community.general/changelogs/fragments/6773-proxmox_kvm-restarted-state-bug-fix.yaml

bugfixes:
  - proxmox_kvm - ``restarted`` state did not actually restart a VM in some VM configurations. The state now uses the Proxmox reboot endpoint instead of calling the ``stop_vm`` and ``start_vm`` functions (https://github.com/ansible-collections/community.general/pull/6773).
Module `proxmox_kvm` `restarted` state bug fix (#6773) * Change proxmox_kvm restart to use new method Previously, the `restarted` state used both stop and start vm functions to restart a vm. This change introduces the a new function that utilizes the proxmox reboot endpoint instead for a more reliable method of restarting a vm. * Create 6773-proxmox_kvm-restarted-state-bug-fix.yaml * Fix typo * Add link to PR * Chanel log fragment formatting changes * Move try/catch to `restart_vm` function * Update changelogs/fragments/6773-proxmox_kvm-restarted-state-bug-fix.yaml Co-authored-by: Felix Fontein <felix@fontein.de> --------- Co-authored-by: Felix Fontein <felix@fontein.de> 2023-06-26 23:31:18 +02:00			`bugfixes:`
			- proxmox_kvm - ``restarted`` state did not actually restart a VM in some VM configurations. The state now uses the Proxmox reboot endpoint instead of calling the ``stop_vm`` and ``start_vm`` functions (https://github.com/ansible-collections/community.general/pull/6773).