You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@metron.apache.org by nickwallen <gi...@git.apache.org> on 2017/10/30 16:55:20 UTC

[GitHub] metron pull request #820: METRON-1287 Full Dev Fails When Installing EPEL Re...

GitHub user nickwallen opened a pull request:

    https://github.com/apache/metron/pull/820

    METRON-1287 Full Dev Fails When Installing EPEL Repository

    This fixes a change in the EPEL repository that is causing deployments of Full Dev to fail.
    
    ```
    TASK [epel : Get epel-repo rpm] ************************************************
    fatal: [node1]: FAILED! => {"changed": false, "dest": "/tmp/epel-release.rpm", "failed": true, "msg": "Request failed", "response": "HTTP Error 404: Not Found", "state": "absent", "status_code": 404, "url": "http://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm"}
    	to retry, use: --limit @/Users/nallen/Development/metron/metron-deployment/playbooks/metron_full_install.retry
    ```
    
    This has fixed the immediate issue for me, but I still want to run a full deployment before this gets merged.
    
    ## Pull Request Checklist
    
    - [ ] Is there a JIRA ticket associated with this PR? If not one needs to be created at [Metron Jira](https://issues.apache.org/jira/browse/METRON/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel). 
    - [ ] Does your PR title start with METRON-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
    - [ ] Has your PR been rebased against the latest commit within the target branch (typically master)?
    - [ ] Have you included steps to reproduce the behavior or problem that is being changed or addressed?
    - [ ] Have you included steps or a guide to how the change may be verified and tested manually?
    - [ ] Have you ensured that the full suite of tests and checks have been executed in the root metron 
    - [ ] Have you written or updated unit tests and or integration tests to verify your changes?
    - [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? 
    - [ ] Have you verified the basic functionality of the build by building and running locally with Vagrant full-dev environment or the equivalent?
    


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

    $ git pull https://github.com/nickwallen/metron METRON-1287

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

    https://github.com/apache/metron/pull/820.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 #820
    
----
commit e11bb430a5960f7f87c0aebce0dbe90cb05f2e45
Author: Nick Allen <ni...@nickallen.org>
Date:   2017-10-30T16:50:47Z

    METRON-1287 Full Dev Fails When Installing EPEL Repository

----


---

[GitHub] metron pull request #820: METRON-1287 Full Dev Fails When Installing EPEL Re...

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:

    https://github.com/apache/metron/pull/820


---

[GitHub] metron issue #820: METRON-1287 Full Dev Fails When Installing EPEL Repositor...

Posted by merrimanr <gi...@git.apache.org>.
Github user merrimanr commented on the issue:

    https://github.com/apache/metron/pull/820
  
    I was able to successfully build full dev with this change.  +1


---