Issue with setting master log position about ansible-role-mysql HOT 7 CLOSED

I've same problem. I don't found how script handle master log_pos and log_file variables.

from ansible-role-mysql.

It looks like this may have been a result of some of the changes added to the role for replication. I'll try to take a look, but this error looks like it might be a little bit difficult to reproduce (unless it's just printing a var directly instead of in quotes—as you said, it could just be that a string is being placed somewhere rather than an integer).

from ansible-role-mysql.

This is annoying to reproduce in a test environment, since it requires setting up a master and slave, getting them out of sync intentionally, then trying to set up the slave again (as happened in the above issue).

But a possible fix might be making sure replication is stopped on the slave prior to running the CHANGE MASTER command:

- name: Stop replication on the slave.
  mysql_replication: mode=stopslave
  ignore_errors: True
  when: >
    slave|failed
    and (mysql_replication_role == 'slave')
    and (mysql_replication_master != '')

from ansible-role-mysql.

"failed": true, 
"msg": "the field 'args' has an invalid value, which appears to include a variable that is undefined. The error was: 'dict object' has no attribute 'File'.

The error appears to have been in 'roles/mysql/tasks/replication.yml': line 31, column 3, 
but maybe elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:

- name: Configure replication on the slave.
  ^ here

My Ansible got this error.
Where should I set master.File and master.Position?

from ansible-role-mysql.

I had commented:

master_log_pos = "{{ master.Position}}"
master_log_file = "{{ master.File }}"

The seems not be used.

from ansible-role-mysql.

This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark issues as stale.

from ansible-role-mysql.

This issue has been closed due to inactivity. If you feel this is in error, please reopen the issue or file a new issue with the relevant details.

from ansible-role-mysql.