The instance-config-mgt Ansible is not idempotent
Problem/Opportunity Statement
You have an Exosphere instance on Cloud A, you want to migrate it to Cloud B. You take a snapshot image, download it from A, upload it to B, and using Exosphere, you launch a new instance from the image on cloud B.
This won't work well, particularly the Guacamole setup will complain because you already have a container listening on a network port that the Ansible is trying to create a new container to listen on.
What would success / a fix look like?
The above activity results in a fully working, error-free instance on cloud B.