You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2016/02/24 19:02:18 UTC
[jira] [Commented] (AMBARI-15161) VERSION_MISMATCH Doesn't Change
Back When Component Is Corrected
[ https://issues.apache.org/jira/browse/AMBARI-15161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15163429#comment-15163429 ]
Hadoop QA commented on AMBARI-15161:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12789584/AMBARI-15161.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 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:green}+1 core tests{color}. The patch passed unit tests in ambari-server.
Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/5544//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/5544//console
This message is automatically generated.
> VERSION_MISMATCH Doesn't Change Back When Component Is Corrected
> ----------------------------------------------------------------
>
> Key: AMBARI-15161
> URL: https://issues.apache.org/jira/browse/AMBARI-15161
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.4.0
> Reporter: Dmitry Lysnichenko
> Assignee: Dmitry Lysnichenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-15161.patch
>
>
> If the database shows a {{VERSION_MISMATCH}} for a host component, correcting this component doesn't set the data back:
> {code:title=hostcomponentstate}
> 1 2 ZOOKEEPER_CLIENT 2.4.0.0-86 3 INSTALLED 1 ZOOKEEPER NONE UNKNOWN
> 2 2 ZOOKEEPER_SERVER 2.4.0.0-86 4 STARTED 1 ZOOKEEPER NONE UNSECURED
> 3 2 ZOOKEEPER_SERVER 2.4.0.0-86 4 STARTED 2 ZOOKEEPER NONE UNSECURED
> 4 2 ZOOKEEPER_CLIENT 2.4.0.0-86 3 INSTALLED 2 ZOOKEEPER NONE UNKNOWN
> 5 2 ZOOKEEPER_SERVER 2.4.0.0-86 4 STARTED 3 ZOOKEEPER VERSION_MISMATCH UNSECURED
> {code}
> Notice that there is a {{ZOOKEEPER_SERVER}} which has had it's version corrected back to {{2.4.0.0-86}} but still shows as {{VERSION_MISMATCH}}
> STR:
> 1) Stop ZK on a host
> 2) {{hdp-select}} to another version
> 3) Start ZK
> 4) After {{VERSION_MISMATCH}}, stop it again, flip it back, and start it
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)