Azure-Samples / ansible-playbooks

Ansible Playbook Samples for Azure
MIT License
224 stars 349 forks source link

playbook MySQLDatabaseCreate.yml failed #10

Closed yungezz closed 5 years ago

yungezz commented 6 years ago

Please provide us with the following information:

the playbook failed with below error:

Still running (2 of 50): ansible-playbook ./MySQLDatabaseCreate.yml --extra-vars {"azure_subscription_id":[secure],"azure_tenant":[secure],"azure_client_id":[secure]}
The command ansible-playbook ./MySQLDatabaseCreate.yml --extra-vars {"azure_subscription_id":[secure],"azure_tenant":[secure],"azure_client_id":[secure]} exited with 2.
Log:
[WARNING]: Unable to parse /etc/ansible/hosts as an inventory source
[WARNING]: No inventory was parsed, only implicit localhost is available
[WARNING]: provided hosts list is empty, only localhost is available. Note
that the implicit localhost does not match 'all'
PLAY [localhost] ***************************************************************
TASK [Gathering Facts] *********************************************************
ok: [localhost]
TASK [Azure.azure_preview_modules : debug] *************************************
skipping: [localhost]
TASK [Create a resource group] *************************************************
changed: [localhost]
TASK [Create MySQL Server] *****************************************************
[WARNING]: Azure API profile latest does not define an entry for
MySQLManagementClient
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Error creating the MySQL Server instance: Azure Error: InvalidEditionSloCombination\nMessage: The edition Basic does not support the service objective MYSQLB50"}
to retry, use: --limit @/home/travis/build/Azure-Samples/ansible-playbooks/MySQLDatabaseCreate.retry
PLAY RECAP *********************************************************************
localhost                  : ok=2    changed=1    unreachable=0    failed=1   

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Any log messages given by the failure

Expected/desired behavior

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)

Versions

Mention any other details that might be useful


Thanks! We'll be in touch soon.

zikalino commented 6 years ago

this issue should be fixed now

yungezz commented 6 years ago

@zikalino have you run the playbook against latest ansible 2.5 released version? if passed, pls close the issue.