Destroying an envirnoment and creating it again doesn't work

[syed]

Hi,

I'm creating an environment by using the following command

ansible-playbook generate-cloudconfig.yml -i localhost --extra-vars "env_name=kvmtest-pga2 mgmt_os=7 
env_version=cs49 env_accounts=admin hvtype=k hv=1 pri=1 kvm_os=7"

it fails to deploy for some reason so I clean it up by doing

ansible-playbook destroyvms.yml -i ./hosts_kvmtest-pga2

Now ideally, it should have released all the resources. However, when I generate the config again using the same command, I get the following error

TASK [Fail if environment name exists] *****************************************
skipping: [localhost]

TASK [debug] *******************************************************************
ok: [localhost] => {
    "msg": {
        "ansible_facts": {
            "available_env_guestips_count": "", 
            "available_env_pods_count": "", 
            "available_env_pubips_count": "", 
            "env_retmsg": "WARNING !! There are currently not enough environments in the DB to create this environment right now.", 
            "env_return": "warning"
        }, 
        "changed": false
    }
}

Could it be that the DB is not being updated?

[syed]

It turns out that def_env_db_user and def_env_db_password are the credentials for the mysql and not the SSH details of the host as I had previously assumed. I have moved them to the same section in the all.sample in PR #25