Open ghost opened 3 years ago
Files identified in the description:
If these files are inaccurate, please update the component name
section of the description or use the !component
bot command.
cc @Aversiste @Thulium-Drake @helldorado @joshainglis @karmab click here for bot help
cc @Ajpantuso click here for bot help
I took a bit deeper look in that issue. As far as I could see this is a actual issue with the api of proxmox. To get this working the API must change or some workaround needs to be introduced into the ansible module. As the information can be retrieved in different ways.
Files identified in the description:
If these files are incorrect, please update the component name
section of the description or use the !component
bot command.
cc @UnderGreen click here for bot help
cc @krauthosting click here for bot help
One workaround would probably be to get the current config beforehand and then compare it with the settings provided to the update call
IMHO, update: true
shouldn't be required in the first place.
A single proxmox_kvm
task should be sufficient.
It feels like it violates both design conventions:
Summary
If
update: true
the task is always reported as "changed"Issue Type
Bug Report
Component Name
proxmox_kvm
Ansible Version
Configuration
No response
OS / Environment
No response
Steps To Reproduce
Expected Results
Task should only change if anything got actually changed on the proxmox side. It should not report a change all the time.
Actual Results