[ 
https://issues.apache.org/jira/browse/METRON-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15531754#comment-15531754
 ] 

ASF GitHub Bot commented on METRON-472:
---------------------------------------

GitHub user ottobackwards opened a pull request:

    https://github.com/apache/incubator-metron/pull/283

    METRON-472: add runAgain.sh to handle a proper vagrant provision

    When you fail after running run.sh in quickdev you will be told to run 
vagrant provision... but what you really want to do is run vagrant provision 
with the same parameters that you used for vagrant up inside run.sh.
    
    runAgain.sh has that.
    


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/ottobackwards/incubator-metron METRON-472

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-metron/pull/283.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #283
    
----
commit 820045a68bf8ff7c020fbe3986cbbe45cdaf803b
Author: Otto Fowler <[email protected]>
Date:   2016-09-29T04:26:22Z

    METRON-472: add runAgain.sh to handle a proper vagrant provision after a 
run.sh failure

----


> Vagrant Quick Dev should have both run.sh and runAgain.sh
> ---------------------------------------------------------
>
>                 Key: METRON-472
>                 URL: https://issues.apache.org/jira/browse/METRON-472
>             Project: Metron
>          Issue Type: Improvement
>    Affects Versions: 0.2.1BETA
>         Environment: Vagrant Quick Dev
>            Reporter: Otto Fowler
>
> The vagrant quick dev is executed by running run.sh ( as opposed to just 
> doing vagrant up in the full dev ).  run.sh does the vagrant up, with the 
> correct tags declared and the skip solr flag.
> Often the vagrant up does not finish execution, and as recommended you have 
> to do a vagrant provision to continue. 
> Depending on where in the process you have failed however, you will not 
> succeed because you have not declared the same tags and skips.
> There should be another script to be run in the provision/retry case.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to