<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: Failure during ansible-playbook run using vagrant up single node Metron in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Failure-during-ansible-playbook-run-using-vagrant-up-single/m-p/151411#M24143</link>
    <description>&lt;P&gt;HI Tom,&lt;/P&gt;&lt;P&gt;I have a couple of questions- can you give me your ansible --version from your Mac and the top hash from the git log?&lt;/P&gt;&lt;P&gt;Also - after it gives the error, was anything left in /tmp/keys?&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;-David...&lt;/P&gt;</description>
    <pubDate>Mon, 04 Apr 2016 23:20:36 GMT</pubDate>
    <dc:creator>dlyle</dc:creator>
    <dc:date>2016-04-04T23:20:36Z</dc:date>
    <item>
      <title>Failure during ansible-playbook run using vagrant up single node Metron</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Failure-during-ansible-playbook-run-using-vagrant-up-single/m-p/151407#M24139</link>
      <description>&lt;P&gt;I am seeing the following error message when performing the single node Metron setup using Vagrant. I've repeated the process and can confirm the issue happens each time.&lt;/P&gt;&lt;PRE&gt;TASK: [ambari_common | Add key pairs to existing authorized_keys] *************
fatal: [node1] =&amp;gt; could not locate file in lookup: /tmp/keys/{{ item }}.pub


FATAL: all hosts have already failed -- aborting


PLAY RECAP ********************************************************************
           to retry, use: --limit @/Users/tbenton/metron_full_install.retry


node1                      : ok=9    changed=8    unreachable=1    failed=0


Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.
&lt;/PRE&gt;</description>
      <pubDate>Thu, 31 Mar 2016 20:00:45 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Failure-during-ansible-playbook-run-using-vagrant-up-single/m-p/151407#M24139</guid>
      <dc:creator>tbenton</dc:creator>
      <dc:date>2016-03-31T20:00:45Z</dc:date>
    </item>
    <item>
      <title>Re: Failure during ansible-playbook run using vagrant up single node Metron</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Failure-during-ansible-playbook-run-using-vagrant-up-single/m-p/151408#M24140</link>
      <description>&lt;P&gt;Hey Tom,&lt;/P&gt;&lt;P&gt;Thanks for trying out metron, first off &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;  Anything going on before that log?  Also, what's your platform and version of vagrant installed?&lt;/P&gt;</description>
      <pubDate>Thu, 31 Mar 2016 20:08:03 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Failure-during-ansible-playbook-run-using-vagrant-up-single/m-p/151408#M24140</guid>
      <dc:creator>cstella</dc:creator>
      <dc:date>2016-03-31T20:08:03Z</dc:date>
    </item>
    <item>
      <title>Re: Failure during ansible-playbook run using vagrant up single node Metron</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Failure-during-ansible-playbook-run-using-vagrant-up-single/m-p/151409#M24141</link>
      <description>&lt;P&gt;Everything else is showing success through the mvn apache-rat and integration-test. I only get an error at this point.&lt;/P&gt;&lt;P&gt;Mac OS X 10.11.4 &lt;/P&gt;&lt;P&gt;Vagrant 1.8.1&lt;/P&gt;&lt;P&gt;VirtualBox 5.0.16&lt;/P&gt;</description>
      <pubDate>Fri, 01 Apr 2016 19:21:29 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Failure-during-ansible-playbook-run-using-vagrant-up-single/m-p/151409#M24141</guid>
      <dc:creator>tbenton</dc:creator>
      <dc:date>2016-04-01T19:21:29Z</dc:date>
    </item>
    <item>
      <title>Re: Failure during ansible-playbook run using vagrant up single node Metron</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Failure-during-ansible-playbook-run-using-vagrant-up-single/m-p/151410#M24142</link>
      <description>&lt;A rel="user" href="https://community.cloudera.com/users/597/cstella.html" nodeid="597"&gt;@cstella&lt;/A&gt;&lt;P&gt;Log output from ansible-playbook run&lt;/P&gt;&lt;PRE&gt;==&amp;gt; node1: Running provisioner: ansible...
    node1: Running ansible-playbook...


PLAY [ec2] ********************************************************************
skipping: no hosts matched


PLAY [ambari_*] ***************************************************************


GATHERING FACTS ***************************************************************
ok: [node1]


TASK: [libselinux-python | Install libselinux-python] *************************
changed: [node1]


TASK: [yum-update | Yum Update Packages] **************************************
changed: [node1]


TASK: [epel | Get epel-repo rpm] **********************************************
changed: [node1]


TASK: [epel | Install epel-repo rpm] ******************************************
changed: [node1]


TASK: [ntp | Install ntp] *****************************************************
changed: [node1]


TASK: [ntp | Ensure ntp is running and enabled] *******************************
changed: [node1]


TASK: [ambari_common | Check OS Version] **************************************
skipping: [node1]


TASK: [ambari_common | Generate ssh key pair for "root"] **********************
changed: [node1]


TASK: [ambari_common | Fetch the generated public key] ************************
changed: [node1]


TASK: [ambari_common | Add key pairs to existing authorized_keys] *************
fatal: [node1] =&amp;gt; could not locate file in lookup: /tmp/keys/{{ item }}.pub


FATAL: all hosts have already failed -- aborting


PLAY RECAP ********************************************************************
           to retry, use: --limit @/Users/tbenton/metron_full_install.retry


node1                      : ok=9    changed=8    unreachable=1    failed=0


Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.

&lt;/PRE&gt;</description>
      <pubDate>Fri, 01 Apr 2016 22:02:12 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Failure-during-ansible-playbook-run-using-vagrant-up-single/m-p/151410#M24142</guid>
      <dc:creator>tbenton</dc:creator>
      <dc:date>2016-04-01T22:02:12Z</dc:date>
    </item>
    <item>
      <title>Re: Failure during ansible-playbook run using vagrant up single node Metron</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Failure-during-ansible-playbook-run-using-vagrant-up-single/m-p/151411#M24143</link>
      <description>&lt;P&gt;HI Tom,&lt;/P&gt;&lt;P&gt;I have a couple of questions- can you give me your ansible --version from your Mac and the top hash from the git log?&lt;/P&gt;&lt;P&gt;Also - after it gives the error, was anything left in /tmp/keys?&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;-David...&lt;/P&gt;</description>
      <pubDate>Mon, 04 Apr 2016 23:20:36 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Failure-during-ansible-playbook-run-using-vagrant-up-single/m-p/151411#M24143</guid>
      <dc:creator>dlyle</dc:creator>
      <dc:date>2016-04-04T23:20:36Z</dc:date>
    </item>
    <item>
      <title>Re: Failure during ansible-playbook run using vagrant up single node Metron</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Failure-during-ansible-playbook-run-using-vagrant-up-single/m-p/151412#M24144</link>
      <description>&lt;P&gt;tbenton$ ansible --version &lt;/P&gt;&lt;P&gt;ansible 1.9.0.1 &lt;/P&gt;&lt;P&gt;  configured module search path = None&lt;/P&gt;&lt;P&gt;
&lt;/P&gt;&lt;P&gt;[vagrant@node1 ~]$ ls /tmp &lt;/P&gt;&lt;P&gt;epel-release.rpm  hosts  ks-script-u_G5MN  ks-script-u_G5MN.log  vboxguest-Module.symvers  yum.log&lt;/P&gt;&lt;P&gt;
which git log did you want the hash from?&lt;/P&gt;</description>
      <pubDate>Thu, 07 Apr 2016 06:01:07 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Failure-during-ansible-playbook-run-using-vagrant-up-single/m-p/151412#M24144</guid>
      <dc:creator>tbenton</dc:creator>
      <dc:date>2016-04-07T06:01:07Z</dc:date>
    </item>
    <item>
      <title>Re: Failure during ansible-playbook run using vagrant up single node Metron</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Failure-during-ansible-playbook-run-using-vagrant-up-single/m-p/151413#M24145</link>
      <description>&lt;P&gt;Upgrading to Ansible 2.0+ fixed the issue here. I am able to continue the build now after upgrading. It was likely due to an older version of Ansible that I had installed.&lt;/P&gt;</description>
      <pubDate>Wed, 13 Apr 2016 03:36:53 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Failure-during-ansible-playbook-run-using-vagrant-up-single/m-p/151413#M24145</guid>
      <dc:creator>tbenton</dc:creator>
      <dc:date>2016-04-13T03:36:53Z</dc:date>
    </item>
  </channel>
</rss>

