OS X 10.10.5
Python 2.7.11
Ansible 2.0.2.0
boto 2.40.0
boto3 1.3.1
botocore 1.4.24
Using the following tasks in a play:
- name: db | rds | create RDS instance
become: no
local_action: rds
args:
command: create
instance_name: "{{ rds_instance_name }}"
instance_type: "{{ rds_instance_class }}"
vpc_security_groups: "{{ rds_instance_vpc_security_groups }}"
multi_zone: "{{ rds_instance_multi_zone }}"
subnet: "{{ rds_instance_subnet_group }}"
db_engine: "{{ rds_instance_engine }}"
publicly_accessible: "{{ rds_instance_public }}"
db_name: "{{ mysql_app_db_name }}"
size: "{{ mysql_app_db_size }}"
username: "{{ mysql_admin_user }}"
password: "{{ mysql_admin_pass }}"
async: 600
poll: 60
register: rds
tags: [db, rds]
- name: db | rds | output db info
debug:
msg: "The new MySQL DB endpoint is {{ rds.instance.endpoint }}"
#var: rds
tags: [db, rds]
The result is that data in rds.instance is not populated completely at
the time the module returns successfully (changed status in this
case). Importantly, the 'endpoint' value is not missing. In the AWS
RDS console, it can be seen that the RDS instance is continuing to be
deployed (in "modifying" status for several minutes) and has not
populated a number of attributes. This is the result in Ansible when
it returns "early":
TASK [app : db | rds | create RDS instance] **********************************
changed: [example.com -> localhost]
TASK [app : db | rds | output db info] ****************************************
ok: [example.com] => {
"msg": "The new MySQL DB endpoint is "
}
Though above, the debug 'msg' attribute shows in this case that
rd.instance.endpoint is empty, on a previous run I dumped the rds
variable and it shows many fields unpopulated:
TASK [app : db | rds | output db info] ****************************************
ok: [example.com] => {
"rds": {
"ansible_job_id": "34553352208.25036",
"changed": false,
"finished": 1,
"instance": {
"availability_zone": "us-west-2b",
"backup_retention": 1,
"create_time": 1464425508.477,
"endpoint": null,
"id": "database",
"instance_type": "db.m4.large",
"iops": null,
"maintenance_window": "sun:10:23-sun:10:53",
"multi_zone": false,
"port": null,
"replication_source": null,
"status": "modifying",
"username": "mysqladmin",
"vpc_security_groups": "sg-4f02f029"
}
}
}
In the examples [1] for the Ansible rds module, the task uses
wait/wait_timeout before returning and shows that the registered
variable has a full set of fields. I assumed that since the RDS
instance creation can take a great deal of time on AWS side, it may be
better to use asynchronous calls to avoid any long waits/timeouts.
Should this work properly using async/poll? Any reason why the module
returns but is not able to supply a complete instance dictionary? Is
there a better approach for this case?
[1] http://docs.ansible.com/ansible/rds_module.html
Regards,
--
Darren Spruell
[email protected]
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/CAKVSOJW2Rvywbt%3Dm-fPGABsGzdmZRszLL_09nBQJ3qNz%2BFJSXw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
