Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Mon, 30 May 2016 13:30:12 +0000 (UTC)
From: "Dmitry Lysnichenko (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.12973981.1464614976000.331582.1464615012942@Atlassian.JIRA>
In-Reply-To: <JIRA.12973981.1464614976000@Atlassian.JIRA>
References: <JIRA.12973981.1464614976000@Atlassian.JIRA> <JIRA.12973981.1464614976845@arcas>
Subject: [jira] [Updated] (AMBARI-16954) SERVICE_CHECK Upgrade pre-check
 does not throw error when its expected to
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 30 May 2016 13:30:14 -0000


     [ https://issues.apache.org/jira/browse/AMBARI-16954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dmitry Lysnichenko updated AMBARI-16954:
----------------------------------------
    Attachment: AMBARI-16954.patch

> SERVICE_CHECK Upgrade pre-check does not throw error when its expected to
> -------------------------------------------------------------------------
>
>                 Key: AMBARI-16954
>                 URL: https://issues.apache.org/jira/browse/AMBARI-16954
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Dmitry Lysnichenko
>            Assignee: Dmitry Lysnichenko
>         Attachments: AMBARI-16954.patch
>
>
> *Steps*
> # Deploy HDP-2.4.0.0 cluster with Ambari 2.2.2
> # Upgrade Ambari to 2.4.0.0
> # Register HDP-2.5.0.0 version and install the bits
> # Modify configs for some of the service like HDFS, ZK, YARN
> # Start EU
> *Result*:
> EU pre-check does *not* report below error for the three services whose config was modified in step 4
> "The following service configurations have been updated and their Service Checks should be run again:"
> Upon further investigation found that the pre-check does not work if a service check has never been run for a service at all AND reports success in such cases
> In other words, the comparison between last config modification time and last service check time succeeds if service check never ran at all and the output of below query returns empty:
> {code}
> SELECT start_time FROM host_role_command where role = 'HDFS_SERVICE_CHECK' AND status = 'COMPLETED' ORDER BY start_time DESC;
> {code}
> In this case when I manually ran a service check for HDFS and retried EU, the pre-check caught the mismatch and reported error
> *Note*: I believe we do run service check as part of cluster install, but looks like it does not get updated in the DB tables for all services.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)