user password generated by role is not been hashed correctly into the user table about ansible-role-mysql

[mnothic]

I have to do this workaround:

file: mysql/tasks/users.yml

- name: MySQL | Make sure the MySQL users are present
  mysql_user:
    name: "{{item.name}}"
    password: "{{item.pass | default('pass')}}"
    priv: "{{item.priv | default('*.*:ALL')}}"
    state: present
    host: "{{item.host | default('localhost')}}"
  with_items: mysql_users
  when: mysql_users|length > 0

- name: Reset remote users password (this is a workaround)
  shell: echo "UPDATE mysql.user SET password=PASSWORD('{{ mysql_root_password }}') WHERE host='%';" | mysql

- name: restart mysql (because handler don't work)
  shell: service mysql restart

- name: Show hash password to compare
  shell: echo "SELECT user, password FROM mysql.user WHERE host='%';" |mysql

[geerlingguy]

@mnothic - Drupal VM uses a custom user/password to connect to MySQL locally, and I just tested on fresh CentOS 6, Ubuntu 12.04, and Ubuntu 14.04 VMs with this role and the following playbook:

---
- hosts: all
  sudo: yes

  vars:
    mysql_users:
      - name: geerling
        host: '%'
        password: 'secret'
        priv: '*.*:ALL'

  roles:
    - geerlingguy.mysql

I was able to connect within the VM using mysql -u geerling -p then entering the password. I tried a couple different combinations as well, and it had no issue.

I wonder if maybe the version of Ansible you're using is having trouble setting the password. I've been pinned to Ansible 1.9.0.1 since there are a couple other strange MySQL bugs with Ansible's MySQL module in 1.9.1 (which I believe are fixed in 1.9.2).

If you're still having this issue, can you please post what OS you're running, what version of MySQL you're running (mysql --version), and what version of Ansible you're running on the host (ansible --version)?

[mnothic]

Use ansible 1.9.1 os used is Ubuntu 14.04.2 LT and mysql Ver 14.14 Distrib 5.5.43, for debian-linux-gnu (x86_64) using readline 6.
and this is not a drupalvm is a fresh install from 'ubuntu/trusty64' with vagrant

[geerlingguy]

@mnothic - Can you try installing Ansible 1.9.0.1 instead to see if that fixes the issue? I have a feeling that this issue (and a few others that are cropping up) are related to some changes made in Ansible 1.9.1 and/or 1.9.2.

If you used pip to install Ansible, you can run:

sudo pip uninstall ansible
sudo pip install ansible==1.9.0.1

Then run the playbook again and see if the hashes/passwords are correct.

[geerlingguy]

I'm still unable to reproduce when running Ansible 1.9.2 on Mac OS X to install on either Ubuntu 12/14, or CentOS 6/7... The only time I had any strange issues was when running 1.9.1 :(

[mnothic]

OK Thanks I will upgrade it ASAP to test it.