Glad to hear it. If you haven't, would you mind accepting the answer that helped? Thanks! -D... ... View more

Glad to hear it worked. If you haven't, would you mind accepting the above answer? Thanks! -David... ... View more

Hi Matthew, I think the instances are being created in the us-west-2 (Oregon) region. I've had those types of connection issues because I'm using OSX 10.10.5 and the version of OpenSSH that it uses doesn't support control_path that we use by default in Metron. If you change your control path to : [ssh_connection] control_path = ~/.ssh/ansible-ssh-%%h-%%p-%%r and re-run, it may connect. ... View more

Hi Sai, Can you tell me what version of Metron, Ansible, Python and Vagrant you are running? Thanks! -D... ... View more

Thanks for that. It looks like there is a version mismatch in your Python environment. If you do a python --version, what do you get? ... View more

Looks like you're right about that. Would you like to open the JIRA, or should I do it? Thanks for pointing it out. ... View more

Hi @drussell - agreed. It's in current Master: METRON-97 Pull Request. Please let me know if we missed something. Thanks! -David... ... View more

Thanks! I need 'em. ... View more

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 ... View more

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 ... View more

Could you add: ansible.verbose = "vvv" to /Users/smanjee/Documents/Hortonworks/Products/incubator-metron-Metron_0.1BETA_rc7/deployment/vagrant/singlenode-vagrant/Vagrantfile between lines 61-62, re-run and re-attach ansible.log? Also, please run the following from /Users/smanjee/Documents/Hortonworks/Products/incubator-metron-Metron_0.1BETA_rc7/deployment/vagrant/singlenode-vagrant and attach the output. # is this a git repo? IS_GIT_REPO=`git rev-parse --is-inside-work-tree` if [ "$IS_GIT_REPO" == "true" ]; then # current branch echo "--" git branch | grep "*" # last commit echo "--" git log -n 1 # local changes since last commit echo "--" git diff --stat fi # ansible echo "--" ansible --version # vagrant echo "--" vagrant --version # python echo "--" python --version 2>&1 # maven echo "--" mvn --version # operating system echo "--" uname -a Thanks! -David... ... View more

Could you elaborate on what you meant by creating the ec2.py file? That is a file that ships with Ansible which it uses to dynamically populate the host names for the roles in the play. ... View more

HI Tom, I have a couple of questions- can you give me your ansible --version from your Mac and the top hash from the git log? Also - after it gives the error, was anything left in /tmp/keys? Thanks! -David... ... View more

You may also see those types of errors present as: SSH Error: unix_listener: "/really/long/path/hostname.tempcharacters" too long for Unix domain socket Same fix as above, shorten the path to your deployment scripts or modify the control_path in ansible.cfg as @George Vetticaden indicated above. in ... View more