Return-Path: X-Original-To: apmail-ambari-dev-archive@www.apache.org Delivered-To: apmail-ambari-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0537518DF4 for ; Wed, 24 Feb 2016 15:54:25 +0000 (UTC) Received: (qmail 10552 invoked by uid 500); 24 Feb 2016 15:54:18 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 10454 invoked by uid 500); 24 Feb 2016 15:54:18 -0000 Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list dev@ambari.apache.org Received: (qmail 10391 invoked by uid 99); 24 Feb 2016 15:54:18 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Feb 2016 15:54:18 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 2E9A62C1F57 for ; Wed, 24 Feb 2016 15:54:18 +0000 (UTC) Date: Wed, 24 Feb 2016 15:54:18 +0000 (UTC) From: "Dmitry Lysnichenko (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-15161) VERSION_MISMATCH Doesn't Change Back When Component Is Corrected MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBARI-15161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-15161: ---------------------------------------- Component/s: ambari-server > 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 > Reporter: Dmitry Lysnichenko > Assignee: Dmitry Lysnichenko > 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)