When running action `reboot_soft` or `reboot_hard`, it always outputs ok, after checking how the module works, I found state checking logic for actions contradicts to openstack compute api.
In the compute API, soft reboot is only available when instance status is `ACTIVE`, but in the ansible module, if the instance status is `ACTIVE` for action `reboot_soft` when checking `_action_map`, the module will exit without changes before executing actions.
When running action `reboot_soft` or `reboot_hard`, it always outputs ok, after checking how the module works, I found state checking logic for actions contradicts to openstack compute api.
In the compute API, soft reboot is only available when instance status is `ACTIVE`, but in the ansible module, if the instance status is `ACTIVE` for action `reboot_soft` when checking `_action_map`, the module will exit without changes before executing actions.
refs:
https:/ /opendev. org/openstack/ ansible- collections- openstack/ src/branch/ master/ plugins/ modules/ server_ action. py
https:/ /docs.openstack .org/api- ref/compute/ #reboot- server- reboot- action