metron-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From JonZeolla <>
Subject [GitHub] incubator-metron issue #411: METRON-635: Vagrant provisioning fails on CentO...
Date Wed, 04 Jan 2017 17:28:46 GMT
Github user JonZeolla commented on the issue:
    @nickwallen Right.  So more granular details about how I tested:
    1. Installed [CentOS 6.8 minimal](
    1. `yum install -f git`
    1. `git clone`
    1. `cd development/Bash && chmod 755`
    1. `./ -fvs full`
        * This should not show an issue.
    1. Destroy the vagrant instance (see `/usr/local/metron/*/metron-deployment/vagrant/full-dev-platform`)
    1. `./ -fvst full`
        * You should get the issue.
            * Adding `-t` prevents `` from adding `scp_if_ssh` to `ansible.cfg`,
and you will see the error.  For the most pristine testing, I reinstalled the OS fresh for
each run of `` (hence why testing this was a bit of a pain).  Finally:
    1. Kill the vagrant instance again
    1. `./ -fvst -p 411 full`
        * This runs the setup process without adding scp_if_ssh, but it merges in this PR
before building Metron and starting vagrant.  You should not see the issue.
    * `full` can be substituted with `quick`, `fastcapa`, or `codelab` for testing the different
vagrant deploy methods.  As you're aware, for a good fastcapa build, this requires `-p 410`.
    * Obviously it's probably worth reviewing `` to see exactly what's happening,
but the `-v` provides some amount of feedback.
    * There is a `-d` flag which adds `ansible.verbose = "vvvv"` to the Vagrantfile prior
to doing `vagrant up` and then removes it after completion for additional troubleshooting.
    * All the script really does is setup up all the dependencies.  From time to time, running
`` will fail because something upstream is being sync'd or performing maintenance/having
issues, and a rerun usually fixes the issue.
    * The script is currently super inefficient and doesn't check to see if something's already
installed before attempting to install it.
    Happy to help provide any additional detail as would be helpful.  I wasn't able to pin
this down exactly, but I have seen 3 others independently report this issue and the fix worked
for them.

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message