Fail to vagrant up bmo-vagrant, showing error in [add some extra repos] task

RESOLVED FIXED

Status

()

RESOLVED FIXED
2 years ago
2 years ago

People

(Reporter: xidorn, Unassigned)

Tracking

Production

Details

(Reporter)

Description

2 years ago
Log following:

Bringing machine 'db' up with 'virtualbox' provider...
Bringing machine 'web' up with 'virtualbox' provider...
==> db: Checking if box 'centos/6' is up to date...
==> db: Machine already provisioned. Run `vagrant provision` or use the `--provision`
==> db: flag to force provisioning. Provisioners marked to run always will still run.
==> db: Running provisioner: ansible...
    db: Running ansible-playbook...

PLAY [all] *********************************************************************

TASK [setup] *******************************************************************
ok: [db]

TASK [check for non-link localtime] ********************************************
ok: [db]

TASK [remove localtime] ********************************************************
skipping: [db]

TASK [set timezone to same as production] **************************************
ok: [db]

TASK [install epel-release] ****************************************************
ok: [db]

TASK [install common packages] *************************************************
ok: [db] => (item=[u'libselinux-python', u'policycoreutils-python', u'python-urllib3', u'python-pyasn1', u'python2-ndg_httpsclient', u'pyOpenSSL', u'htop'])

TASK [permissive selinux] ******************************************************
changed: [db]

TASK [disable selinux on reboot] ***********************************************
changed: [db]

TASK [lineinfile] **************************************************************
ok: [db]

TASK [lineinfile] **************************************************************
ok: [db]

PLAY [db] **********************************************************************

TASK [setup] *******************************************************************
ok: [db]

TASK [add some extra repos] ****************************************************
failed: [db] (item=[u'https://dev.mysql.com/get/mysql-community-release-el6-5.noarch.rpm', u'https://rhel6.iuscommunity.org/ius-release.rpm']) => {"failed": true, "item": ["https://dev.mysql.com/get/mysql-community-release-el6-5.noarch.rpm", "https://rhel6.iuscommunity.org/ius-release.rpm"], "msg": "Failed to validate the SSL certificate for dev.mysql.com:443. Make sure your managed systems have a valid CA certificate installed. If the website serving the url uses SNI you need python >= 2.7.9 on your managed machine to perform SNI verification in python >= 2.6. You can use validate_certs=False if you do not need to confirm the servers identity but this is unsafe and not recommended. Paths checked for this platform: /etc/ssl/certs, /etc/pki/ca-trust/extracted/pem, /etc/pki/tls/certs, /usr/share/ca-certificates/cacert.org, /etc/ansible"}
	to retry, use: --limit @/Users/upsuper/Sources/bmo-vagrant/vagrant_support/playbook.retry

PLAY RECAP *********************************************************************
db                         : ok=10   changed=2    unreachable=0    failed=1   

Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.

Comment 1

2 years ago
I've been seeing that kind of error recently in MozReview's docker setup.  What version of Python do you have installed?  You could try upgrading to the latest 2.7 (2.7.13).
(Reporter)

Comment 2

2 years ago
I had successfully run this several days ago (after I initially saw that email), but failed this time... The Python installed on the host machine is exactly 2.7.13.
what version of ansible?
Flags: needinfo?(xidorn+moz)
(Reporter)

Comment 4

2 years ago
It's 2.2.0.0. I don't think the version of ansible installed changed since last successful run.

And btw, it seems to work now, and I have no idea why...
Flags: needinfo?(xidorn+moz)
(Reporter)

Comment 5

2 years ago
Well, it still doesn't work, but failed with a different failure...
Okay, I made the ansible playbook download the rpms with get_url, so that maybe fixes it?
Flags: needinfo?(xidorn+moz)
(Reporter)

Comment 7

2 years ago
It seems to work now, with a non-fatal error, though:

TASK [check bmo config] ********************************************************
fatal: [web]: FAILED! => {"changed": true, "cmd": "/usr/local/bin/bmo-configured", "delta": "0:00:00.006436", "end": "2017-01-13 15:57:04.789301", "failed": true, "rc": 1, "start": "2017-01-13 15:57:04.782865", "stderr": "", "stdout": "wrong file owner: vagrant.vagrant /vagrant/index.cgi", "stdout_lines": ["wrong file owner: vagrant.vagrant /vagrant/index.cgi"], "warnings": []}
...ignoring

Thanks for fixing it.
Flags: needinfo?(xidorn+moz)
I think this is fixed.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.