[ https://issues.apache.org/jira/browse/AMBARI-21839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16145381#comment-16145381 ]
Hadoop QA commented on AMBARI-21839: ------------------------------------ {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12884247/AMBARI-21839.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:red}-1 tests included{color}. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 core tests{color}. The patch passed unit tests in . Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/12090//console This message is automatically generated. > METRICS_MONITOR start is failing due to "ImportError: cannot import name > _common" > --------------------------------------------------------------------------------- > > Key: AMBARI-21839 > URL: https://issues.apache.org/jira/browse/AMBARI-21839 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics > Affects Versions: 2.4.0 > Reporter: Dmytro Sen > Assignee: Dmytro Sen > Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21839.patch > > > METRICS_MONITOR start is failing on one of the nodes of a cluster due to > "ImportError: cannot import name _common". > Ambari server version is 2.4.0.4.100. Seeing this error in 2.5.0.4.1 also. > Redirecting psutils build output to log file to investigate the issue. -- This message was sent by Atlassian JIRA (v6.4.14#64029)