question Re: Metron vagrant up failing at ansible step - Amabari client in Archives of Support Questions (Read Only)

Metron vagrant up failing at ansible step - Amabari client

codesagar — Wed, 27 Apr 2016 05:39:11 GMT

Here is the error o/p start

TASK [httplib2 : Install python httplib2 dependency] ***************************

changed: [node1]

TASK [ambari_config : include_vars] ********************************************

ok: [node1]

TASK [ambari_config : Install python-requests] *********************************

changed: [node1]

TASK [ambari_config : Deploy cluster with Ambari; http://node1:8080] ***********

fatal: [node1]: FAILED! => {"changed": false, "failed": true, "msg": "Ambari client exception occurred: Coud not get blueprint list: request code 404,

Re: Metron vagrant up failing at ansible step - Amabari client

jsirota — Wed, 27 Apr 2016 07:47:30 GMT

Hi Sagar, can you please attach your ansible.log whenever you get a chance?

Re: Metron vagrant up failing at ansible step - Amabari client

codesagar — Wed, 27 Apr 2016 21:04:40 GMT

ansible.txt

Re: Metron vagrant up failing at ansible step - Amabari client

cstella — Wed, 27 Apr 2016 21:23:56 GMT

Wow, so, looking at that log, it looks like it's trying to go to node1:8080 and it's getting redirected to google (you can see from the logs, the response looks like google results).

What version of vagrant is being used here?

Re: Metron vagrant up failing at ansible step - Amabari client

codesagar — Wed, 27 Apr 2016 21:51:56 GMT

Version: Vagrant 1.7.4

I also noticed that when I try to open node1:8080 via browser is re-routes to googles and opens up www.node1.com

Re: Metron vagrant up failing at ansible step - Amabari client

cstella — Wed, 27 Apr 2016 21:52:26 GMT

Yeah, I'm running 1.8.1. I would consider upgrading vagrant; looks like it's not setting up that hostname properly.

Re: Metron vagrant up failing at ansible step - Amabari client

nallen — Thu, 28 Apr 2016 01:42:46 GMT

Sagar is running behind a corporate proxy. He had configured the proxy in both his Mac system settings and global Vagrant settings. When he issued a web request to "node1:8080" or "192.168.x.x:8080" it was going to the proxy server which then redirected him to the "node1.com" web address.

We updated the Mac and Vagrant settings to bypass the proxy for that specific IP address. This resolved the immediate issue. As a follow-on, we need to update those same settings to bypass the proxy for any IP address in the private subnets of 10.0.0.0/8 and 192.168.0.0/16. This should help avoid problems with future deployments of Metron should it choose to grab a different IP address.

He is attempting a fresh deployment with these proxy settings. We are not out of the woods yet, but that's progress at least. @sagar gaikwad, please update us on how the deployment goes.

Re: Metron vagrant up failing at ansible step - Amabari client

codesagar — Tue, 03 May 2016 00:16:42 GMT

I modified proxies in vagrant.d folder and was able to get past the initial error. I am now failing for some other error at Elasticsearch step

TASK [elasticsearch : Add Elasticsearch GPG key.] ******************************

fatal: [node1]: FAILED! => {"changed": false, "failed": true, "msg": "Failed to validate the SSL certificate for packages.elastic.co: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. You can use validate_certs=False if you do not need to confirm the server\\s 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"}

Re: Metron vagrant up failing at ansible step - Amabari client

andrewg — Tue, 03 May 2016 02:30:04 GMT

I had a single-node vagrant step completely lock up my macbook pro, had to reboot it. Vagrant 1.8.1. Froze on the ambari deploy step.

Re: Metron vagrant up failing at ansible step - Amabari client

dlyle — Tue, 03 May 2016 18:08:48 GMT

A few days back, Homebrew updated their Ansible version. This version exhibits this defect. Please verify you're running a version > 2.0.0.2 by running ansible -version. If you are, please install Ansible 2.0.0.2 using the following instructions:

Uninstall brew-installed Ansible -
```
brew uninstall ansible
```
Install PIP (if not already installed)
```
brew install brew-pip
```

Install Ansible 2.0.0.2
```
pip install ansible==2.0.0.2
```

Re: Metron vagrant up failing at ansible step - Amabari client

dlyle — Tue, 03 May 2016 18:11:19 GMT

For reference, here's the current version list:

Ansible 2.0.0.2
Vagrant 1.8.1
Virtualbox 5.0.16
Python 2.7.11
Maven 3.3.9

@nallen has a PR up with a more complete readme for the Singlenode Vagrant install. Until it gets merged in, you can see it here:

Singlenode Vagrant Readme

Re: Metron vagrant up failing at ansible step - Amabari client

rgarcia — Tue, 03 May 2016 21:22:47 GMT

I'm getting this error trying the vagrant install. This comes after running 'vagrant up' command.

TASK [ambari_config : Start All Hadoop Services node1] *************************
failed: [node1] (item=HDFS) => {"connection": "close", "content": "", "content_type": "text/plain;charset=ISO-8859-1", "failed": true, "item": "HDFS", "msg": "Status code was not [200, 202]: HTTP Error 500: Server Error", "redirected": false, "server": "Jetty(8.1.17.v20150415)", "set_cookie": "AMBARISESSIONID=1sgn1chrad41b1qw1kj03dd9kg;Path=/;HttpOnly", "status": 500, "url": "http://node1:8080/api/v1/clusters/metron_cluster/services/HDFS", "user": "admin"}
failed: [node1] (item=YARN) => {"connection": "close", "content": "", "content_type": "text/plain;charset=ISO-8859-1", "failed": true, "item": "YARN", "msg": "Status code was not [200, 202]: HTTP Error 500: Server Error", "redirected": false, "server": "Jetty(8.1.17.v20150415)", "set_cookie": "AMBARISESSIONID=1is6xyjxvpccqyba2f46le9sl;Path=/;HttpOnly", "status": 500, "url": "http://node1:8080/api/v1/clusters/metron_cluster/services/YARN", "user": "admin"}
failed: [node1] (item=MAPREDUCE2) => {"connection": "close", "content": "", "content_type": "text/plain;charset=ISO-8859-1", "failed": true, "item": "MAPREDUCE2", "msg": "Status code was not [200, 202]: HTTP Error 500: Server Error", "redirected": false, "server": "Jetty(8.1.17.v20150415)", "set_cookie": "AMBARISESSIONID=1nvb5mwkf1a0r19a051px2z1da;Path=/;HttpOnly", "status": 500, "url": "http://node1:8080/api/v1/clusters/metron_cluster/services/MAPREDUCE2", "user": "admin"}
failed: [node1] (item=ZOOKEEPER) => {"connection": "close", "content": "", "content_type": "text/plain;charset=ISO-8859-1", "failed": true, "item": "ZOOKEEPER", "msg": "Status code was not [200, 202]: HTTP Error 500: Server Error", "redirected": false, "server": "Jetty(8.1.17.v20150415)", "set_cookie": "AMBARISESSIONID=1t0e24juqq5be1oneug42xd9fy;Path=/;HttpOnly", "status": 500, "url": "http://node1:8080/api/v1/clusters/metron_cluster/services/ZOOKEEPER", "user": "admin"}
failed: [node1] (item=HBASE) => {"connection": "close", "content": "", "content_type": "text/plain;charset=ISO-8859-1", "failed": true, "item": "HBASE", "msg": "Status code was not [200, 202]: HTTP Error 500: Server Error", "redirected": false, "server": "Jetty(8.1.17.v20150415)", "set_cookie": "AMBARISESSIONID=1v10mm1sa85tj1jd0cxg53kmfr;Path=/;HttpOnly", "status": 500, "url": "http://node1:8080/api/v1/clusters/metron_cluster/services/HBASE", "user": "admin"}
failed: [node1] (item=STORM) => {"connection": "close", "content": "", "content_type": "text/plain;charset=ISO-8859-1", "failed": true, "item": "STORM", "msg": "Status code was not [200, 202]: HTTP Error 500: Server Error", "redirected": false, "server": "Jetty(8.1.17.v20150415)", "set_cookie": "AMBARISESSIONID=1xso3y6yntj86150i2ne8ixqdl;Path=/;HttpOnly", "status": 500, "url": "http://node1:8080/api/v1/clusters/metron_cluster/services/STORM", "user": "admin"}
failed: [node1] (item=KAFKA) => {"connection": "close", "content": "", "content_type": "text/plain;charset=ISO-8859-1", "failed": true, "item": "KAFKA", "msg": "Status code was not [200, 202]: HTTP Error 500: Server Error", "redirected": false, "server": "Jetty(8.1.17.v20150415)", "set_cookie": "AMBARISESSIONID=1e2nei5aurn69eq1lcnvfcnna;Path=/;HttpOnly", "status": 500, "url": "http://node1:8080/api/v1/clusters/metron_cluster/services/KAFKA", "user": "admin"}
	to retry, use: --limit @../../playbooks/metron_full_install.retry


PLAY RECAP *********************************************************************
node1                      : ok=38   changed=28   unreachable=0    failed=1


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

Re: Metron vagrant up failing at ansible step - Amabari client

rgarcia — Tue, 03 May 2016 21:23:35 GMT

Breaking my comment prior since its over the character limit.

I checked my ansible version and it's using ansible 2.0.2. Uninstalled it and re-install 2.0.0.2 but getting this message.

$ pip install ansible==2.0.0.2
Requirement already satisfied (use --upgrade to upgrade): ansible==2.0.0.2 in /usr/local/lib/python2.7/site-packages
Requirement already satisfied (use --upgrade to upgrade): paramiko in /usr/local/lib/python2.7/site-packages (from ansible==2.0.0.2)
Requirement already satisfied (use --upgrade to upgrade): setuptools in /usr/local/lib/python2.7/site-packages (from ansible==2.0.0.2)
Requirement already satisfied (use --upgrade to upgrade): PyYAML in /usr/local/lib/python2.7/site-packages (from ansible==2.0.0.2)
Requirement already satisfied (use --upgrade to upgrade): pycrypto>=2.6 in /usr/local/lib/python2.7/site-packages (from ansible==2.0.0.2)
Requirement already satisfied (use --upgrade to upgrade): jinja2 in /usr/local/lib/python2.7/site-packages (from ansible==2.0.0.2)
Requirement already satisfied (use --upgrade to upgrade): pyasn1>=0.1.7 in /usr/local/lib/python2.7/site-packages (from paramiko->ansible==2.0.0.2)
Requirement already satisfied (use --upgrade to upgrade): cryptography>=1.1 in /usr/local/lib/python2.7/site-packages (from paramiko->ansible==2.0.0.2)
Requirement already satisfied (use --upgrade to upgrade): MarkupSafe in /usr/local/lib/python2.7/site-packages (from jinja2->ansible==2.0.0.2)
Requirement already satisfied (use --upgrade to upgrade): enum34 in /usr/local/lib/python2.7/site-packages (from cryptography>=1.1->paramiko->ansible==2.0.0.2)
Requirement already satisfied (use --upgrade to upgrade): ipaddress in /usr/local/lib/python2.7/site-packages (from cryptography>=1.1->paramiko->ansible==2.0.0.2)
Requirement already satisfied (use --upgrade to upgrade): six>=1.4.1 in /usr/local/lib/python2.7/site-packages (from cryptography>=1.1->paramiko->ansible==2.0.0.2)
Requirement already satisfied (use --upgrade to upgrade): idna>=2.0 in /usr/local/lib/python2.7/site-packages (from cryptography>=1.1->paramiko->ansible==2.0.0.2)
Requirement already satisfied (use --upgrade to upgrade): cffi>=1.4.1 in /usr/local/lib/python2.7/site-packages (from cryptography>=1.1->paramiko->ansible==2.0.0.2)
Requirement already satisfied (use --upgrade to upgrade): pycparser in /usr/local/lib/python2.7/site-packages (from cffi>=1.4.1->cryptography>=1.1->paramiko->ansible==2.0.0.2)

Re: Metron vagrant up failing at ansible step - Amabari client

rgarcia — Tue, 03 May 2016 21:32:36 GMT

'pip uninstall ansible' did the trick to remove ansible 2.0.2. Successfully installed ansible 2.0.0.2. Will re-run 'vagrant up'.

Re: Metron vagrant up failing at ansible step - Amabari client

alizadeh_uut — Wed, 04 May 2016 17:33:45 GMT

I have the exact same issue. And it is not a proxy thing. I checked "node1:8080" in browser and It was not re-directed to google.

Re: Metron vagrant up failing at ansible step - Amabari client

tejaswi_palacha — Wed, 13 Jul 2016 22:07:33 GMT

Can anyone tell me how to solve the same issue?

Re: Metron vagrant up failing at ansible step - Amabari client

tejaswi_palacha — Wed, 13 Jul 2016 22:08:34 GMT

Did u get the required output?what steps did u follow for that?