Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rds_instance reports changed despite no changes to the database #240

Closed
skoranda opened this issue Sep 24, 2020 · 2 comments
Closed

rds_instance reports changed despite no changes to the database #240

skoranda opened this issue Sep 24, 2020 · 2 comments
Labels
affects_2.10 bug This issue/PR relates to a bug waiting_on_contributor Needs help. Feel free to engage to get things unblocked

Comments

@skoranda
Copy link

SUMMARY

community.aws.rds_instance reports changed despite no changes to the database

ISSUE TYPE
  • Bug Report
COMPONENT NAME

community.aws.rds_instance

ANSIBLE VERSION
ansible 2.9.6
CONFIGURATION
ANSIBLE_SSH_ARGS(env: ANSIBLE_SSH_ARGS) = -F /home/skoranda/CILogon2/comanage-registry-ansible/ssh_config -C -o ControlMaster=auto -o ControlPersist=3600s
ANSIBLE_SSH_CONTROL_PATH(/home/skoranda/CILogon2/comanage-registry-ansible/ansible.cfg) = ssh_mux_%%h_%%p
DEFAULT_HOST_LIST(env: ANSIBLE_INVENTORY) = ['/home/skoranda/CILogon2/comanage-registry-ansible/aws_ec2.yml']
DEFAULT_TIMEOUT(/home/skoranda/CILogon2/comanage-registry-ansible/ansible.cfg) = 60
DEFAULT_VAULT_PASSWORD_FILE(env: ANSIBLE_VAULT_PASSWORD_FILE) = /home/skoranda/.vault_pass.txt
INTERPRETER_PYTHON(/home/skoranda/CILogon2/comanage-registry-ansible/ansible.cfg) = auto_silent
OS / ENVIRONMENT

Debian 10.5

STEPS TO REPRODUCE

Run a playbook with the following task:

    - name: Provision DB 
      community.aws.rds_instance:
        availability_zone: us-east-2a
        engine: aurora
        engine_version: 5.6.10a
        allow_major_version_upgrade: no
        auto_minor_version_upgrade: yes
        db_cluster_identifier: cilogon-registry-cluster-01-dev
        db_instance_class: db.t3.small
        db_instance_identifier: cilogon-registry-dev
        db_parameter_group_name: cilogon-aurora-mysql-5-6-parameter-group-dev
        state: present
        region: us-east-2

Wait for the database to be created.

Run the same playbook with the same task. The task shows

TASK [Provision DB] *********************************************************************
[WARNING]: Module did not set no_log for force_update_password
changed: [localhost]

even though nothing has changed.

EXPECTED RESULTS

After the database is created and no changes are made to the task I expect running the task to show

ok: [localhost]
ACTUAL RESULTS
TASK [Provision DB] *********************************************************************
[WARNING]: Module did not set no_log for force_update_password
changed: [localhost]
@skoranda
Copy link
Author

I also verified that the issue happens with 2.10.0 and 2.11.0.dev0

@ansibullbot ansibullbot added affects_2.10 bug This issue/PR relates to a bug needs_triage labels Nov 16, 2020
@goneri goneri added waiting_on_contributor Needs help. Feel free to engage to get things unblocked and removed needs_triage labels Feb 19, 2021
@markuman markuman mentioned this issue Feb 1, 2022
1 task
alinabuzachis pushed a commit to alinabuzachis/community.aws that referenced this issue May 25, 2022
@tremble
Copy link
Contributor

tremble commented Jul 9, 2022

This issue should have been fixed by #1002 which is available in release 3.3.0

@tremble tremble closed this as completed Jul 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects_2.10 bug This issue/PR relates to a bug waiting_on_contributor Needs help. Feel free to engage to get things unblocked
Projects
None yet
Development

No branches or pull requests

4 participants