Production install fails in Ubuntu 14.04 with MySQL Error

Hello ,
I am trying to do a production setup with a clean install on Ubuntu 14.04 and got the following error.

TASK [restart mysql linux] *****************************************************
fatal: [localhost]: FAILED! => {“changed”: false, “failed”: true, “msg”: “Failed to issue method call: Unit mysql.service not loaded.\nFailed to issue method call: Unit mysql.service failed to load: No such file or directory. See system logs and ‘systemctl status mysql.service’ for details.\n”}
to retry, use: --limit @production/install.retry

PLAY RECAP *********************************************************************
localhost : ok=23 changed=16 unreachable=0 failed=1

Traceback (most recent call last):
File “install.py”, line 355, in
install_bench(args)
File “install.py”, line 111, in install_bench
run_playbook(‘production/install.yml’, sudo=True, extra_vars=extra_vars)
File “install.py”, line 301, in run_playbook
success = subprocess.check_call(args, cwd=os.path.join(cwd, ‘playbooks’))
File “/usr/lib/python2.7/subprocess.py”, line 540, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command ‘[‘ansible-playbook’, ‘-c’, ‘local’, ‘production/install.yml’, ‘-e’, ‘@/tmp/extra_vars.json’, ‘–become’, ‘–become-user=frappe’]’ returned non-zero exit status 2

On checking the status of mysql service I got the following;
frappe@scw-ae3348:~$ systemctl status mysql.service
mysql.service
Loaded: error (Reason: No such file or directory)
Active: inactive (dead)

Hi,
Try to install Mysql manually.

Was this issue resolved? It seems replicable on Ubuntu 14.04 for new production install

TASK [restart mysql linux] *****************************************************
fatal: [localhost]: FAILED! => {“changed”: false, “failed”: true, “msg”: “Failed to issue method call: Unit mysql.service not loaded.\nFailed to issue method call: Unit mysql.service failed to load: No such file or directory. See system logs and ‘systemctl status mysql.service’ for details.\n”}
to retry, use: --limit @production/install.retry

PLAY RECAP *********************************************************************
localhost : ok=23 changed=2 unreachable=0 failed=1

Traceback (most recent call last):
File “install.py”, line 355, in
install_bench(args)
File “install.py”, line 111, in install_bench
run_playbook(‘production/install.yml’, sudo=True, extra_vars=extra_vars)
File “install.py”, line 301, in run_playbook
success = subprocess.check_call(args, cwd=os.path.join(cwd, ‘playbooks’))
File “/usr/lib/python2.7/subprocess.py”, line 540, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command ‘[‘ansible-playbook’, ‘-c’, ‘local’, ‘production/install.yml’, ‘-e’, ‘@/tmp/extra_vars.json’, ‘–become’, ‘–become-user=frappe’]’ returned non-zero exit status 2

No, it was not.
I finally did a Centos install, since I was in a hurry and did not have time to dig deeper.