RDS Module "promote" function not working. Reporting "ok", but not making a change.

[Sena Heydari]

The role play:

- name: Promote Read-Replica to New Standalone RDS Instance

  rds:

    command: promote

    instance_name: new-db

    aws_access_key: "{{ some-key }}"

    aws_secret_key: "{{ some-secret }}"

    region: us-east-1

Output from -vvvv (anonymized):

<127.0.0.1> REMOTE_MODULE rds region=us-east-1 command=promote aws_access_key=some-key aws_secret_key=some-secret instance_name=new-db

<127.0.0.1> EXEC ['/bin/sh', '-l', '-c', 'mkdir -p $HOME/.ansible/tmp/ansible-tmp-1435075726.85-46917134810376 && chmod a+rx $HOME/.ansible/tmp/ansible-tmp-1435075726.85-46917134810376 && echo $HOME/.ansible/tmp/ansible-tmp-1435075726.85-46917134810376']

<127.0.0.1> PUT /tmp/tmpvipCL4 TO /home/dir/.ansible/tmp/ansible-tmp-1435075726.85-46917134810376/rds

<127.0.0.1> EXEC ['/bin/sh', '-l', '-c', u'LANG=en_US.UTF-8 LC_CTYPE=en_US.UTF-8 /usr/bin/python /home/dir/.ansible/tmp/ansible-tmp-1435075726.85-46917134810376/rds; rm -rf /home/dir/.ansible/tmp/ansible-tmp-1435075726.85-46917134810376/ >/dev/null 2>&1']

ok: [127.0.0.1] => {"changed": false, "instance": {"availability_zone": "us-east-1d", "backup_retention": 0, "create_time": 1435073003.518, "endpoint": "new-db.account-num.us-east-1.rds.amazonaws.com", "id": "new-db", "instance_type": "db.m3.large", "iops": null, "maintenance_window": "mon:03:00-mon:03:30", "multi_zone": false, "port": 3306, "replication_source": "source-db", "status": "available", "username": "someroot", "vpc_security_groups": "sg-something"}}

Testing run with full RDS rights for user with access-key/secret. 

Boto Version also up to date:

Type "help", "copyright", "credits" or "license" for more information.

>>> import boto

>>> boto.Version

'2.38.0'

Play runs as "ok", but I confirmed the DB is still read-replica in AWS console. 

Anything obvious I'm missing, or is this a bug?

[MB]

Same problem here. No relevant output or error, but slave is not promoted.

We use Ansible 1.9.2 and Boto 2.37.0.

Should a Github issue be opened?

[Greg DeKoenigsberg]

I would recommend opening an issue, yes.

--g

> --
> 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 ansible-proje...@googlegroups.com.
> To post to this group, send email to ansible...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ansible-project/ba5e5349-574e-4b53-acd4-816d8d0c9dc9%40googlegroups.com.
>
> For more options, visit https://groups.google.com/d/optout.



--
Greg DeKoenigsberg
Ansible Community Guy

Find out why SD Times named Ansible
their #1 Company to Watch in 2015:
http://sdtimes.com/companies-watch-2015/