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

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

GitHub user anandsubbu opened a pull request:

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

    METRON-1451: On Centos full dev, Metron Indexing shows up as stopped

    ## Contributor Comments
    
    **Root Cause**
    The python-requests module introduced a VendorAlias import machinery in 
v2.5.2 and caused the sys.modules to break. This issue was later fixed in 
v2.6.1 of python-requests (see [here](https://pypi.python.org/pypi/requests)). 
    
    The solution is to use this version of python-requests, which fixed the 
issue.
    
    **Testing Done**
    
    On CentOS 6 full dev
    - Validated python-requests v2.6.1 is installed 
    - Checked for the Metron Indexing service state to be up. 
    - Checked ambari-agent.log and the error was not seen.
    
    On Ubuntu 14 full dev
    - Repeated the same steps as on CentOS 6 
    
    **Verification Steps**
    - Spin up full dev. 
    - Verify Metron Indexing service is shown as up and running.
    
    ## Pull Request Checklist
    
    Thank you for submitting a contribution to Apache Metron.  
    Please refer to our [Development 
Guidelines](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61332235)
 for the complete guide to follow for contributions.  
    Please refer also to our [Build Verification 
Guidelines](https://cwiki.apache.org/confluence/display/METRON/Verifying+Builds?show-miniview)
 for complete smoke testing guides.  
    
    
    In order to streamline the review of the contribution we ask you follow 
these guidelines and ask you to double check the following:
    
    ### For all changes:
    - [x] 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).
    - [x] 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.
    - [x] Has your PR been rebased against the latest commit within the target 
branch (typically master)?
    
    
    ### For code changes:
    - [x] Have you included steps to reproduce the behavior or problem that is 
being changed or addressed?
    - [x] 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 folder via:
      ```
      mvn -q clean integration-test install && 
dev-utilities/build-utils/verify_licenses.sh 
      ```
    
    - [ ] 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)?
    - [x] Have you verified the basic functionality of the build by building 
and running locally with Vagrant full-dev environment or the equivalent?
    
    ### For documentation related changes:
    - [ ] Have you ensured that format looks appropriate for the output in 
which it is rendered by building and verifying the site-book? If not then run 
the following commands and the verify changes via 
`site-book/target/site/index.html`:
    
      ```
      cd site-book
      mvn site
      ```
    
    #### Note:
    Please ensure that once the PR is submitted, you check travis-ci for build 
issues and submit an update to your PR as soon as possible.
    It is also recommended that [travis-ci](https://travis-ci.org) is set up 
for your personal repository such that your branches are built there before 
submitting a pull request.


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

    $ git pull https://github.com/anandsubbu/incubator-metron METRON-1451

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

    https://github.com/apache/metron/pull/932.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 #932
    
----
commit f3821ec78708c0122ba7d3ed8057907c8e7a224e
Author: Anand Subramanian <asubramanian@...>
Date:   2018-02-08T11:12:50Z

    Install the right version of python-requests

----


> On Centos full dev, Metron Indexing shows up as stopped
> -------------------------------------------------------
>
>                 Key: METRON-1451
>                 URL: https://issues.apache.org/jira/browse/METRON-1451
>             Project: Metron
>          Issue Type: Bug
>    Affects Versions: 0.4.3
>            Reporter: Anand Subramanian
>            Assignee: Anand Subramanian
>            Priority: Major
>             Fix For: Next + 1
>
>
> In Ambari, the Metron Indexing status is shown as 'stopped'. The agent log 
> shows the following error:
> {code:java}
> INFO 2018-02-05 22:21:39,990 PythonReflectiveExecutor.py:67 - Reflective 
> command failed with exception:
> Traceback (most recent call last):
>   File 
> "/usr/lib/python2.6/site-packages/ambari_agent/PythonReflectiveExecutor.py", 
> line 59, in run_file
>     imp.load_source('__main__', script)
>   File 
> "/var/lib/ambari-agent/cache/common-services/METRON/0.4.3/package/scripts/indexing_master.py",
>  line 18, in <module>
>     import requests
>   File "/usr/lib/python2.6/site-packages/requests/__init__.py", line 53, in 
> <module>
>     from .packages.urllib3.contrib import pyopenssl
>   File "/usr/lib/python2.6/site-packages/requests/packages/__init__.py", line 
> 61, in load_module
>     if name in sys.modules:
> AttributeError: 'NoneType' object has no attribute 'modules'{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to