[
https://issues.apache.org/jira/browse/AMBARI-12931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15147704#comment-15147704
]
Hadoop QA commented on AMBARI-12931:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12787940/AMBARI-12931_v3.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server ambari-web:
org.apache.ambari.server.stack.StackManagerTest
org.apache.ambari.server.stack.KerberosDescriptorTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/5377//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/5377//console
This message is automatically generated.
> Ambari shows "Corrupted Blocks" but it is "Corrupted replica"
> -------------------------------------------------------------
>
> Key: AMBARI-12931
> URL: https://issues.apache.org/jira/browse/AMBARI-12931
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.1.0
> Environment: CentOS-6
> HDP 2.1.15
> Ambari 2.1.0
> Reporter: Olivér Szabó
> Assignee: Olivér Szabó
> Priority: Minor
> Fix For: 2.4.0
>
> Attachments: AMBARI-12931_v3.patch, ambari-hdfs-screenshot.png,
> hdfs-dfsadmin-report.log, hdfs-fsck-02-Aug.log
>
>
> #hdfs dfsadmin -report shows "Blocks with corrupt replica : 20 "
> &
> #hdfs fsck / shows " Corrupt blocks : 0 "
> But on the UI "Corrupted block" shows as 20 from Ambari and Summary of HDFS
> services shows " Block 20 corrupt / 0 missing / ... "
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)