Return-Path: X-Original-To: apmail-ambari-issues-archive@minotaur.apache.org Delivered-To: apmail-ambari-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 68F2E199D2 for ; Wed, 27 Apr 2016 09:02:13 +0000 (UTC) Received: (qmail 14232 invoked by uid 500); 27 Apr 2016 09:02:13 -0000 Delivered-To: apmail-ambari-issues-archive@ambari.apache.org Received: (qmail 14197 invoked by uid 500); 27 Apr 2016 09:02:13 -0000 Mailing-List: contact issues-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 issues@ambari.apache.org Received: (qmail 14185 invoked by uid 99); 27 Apr 2016 09:02:13 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Apr 2016 09:02:13 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id DB85C2C044E for ; Wed, 27 Apr 2016 09:02:12 +0000 (UTC) Date: Wed, 27 Apr 2016 09:02:12 +0000 (UTC) From: "Dmitry Lysnichenko (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-16134) Force running service checks for services before upgrade 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-16134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-16134: ---------------------------------------- Affects Version/s: 2.4.0 > Force running service checks for services before upgrade > -------------------------------------------------------- > > Key: AMBARI-16134 > URL: https://issues.apache.org/jira/browse/AMBARI-16134 > Project: Ambari > Issue Type: Task > Components: ambari-server > Affects Versions: 2.4.0 > Reporter: Dmitry Lysnichenko > Assignee: Dmitry Lysnichenko > Fix For: 2.4.0 > > Attachments: AMBARI-16134.patch > > > Just checking for service checks that were run within the last hour does not seem to be a warranty of anything. For example, user could install cluster, run service checks once, and then enable security/LDAP/change configuration as required by some pre-upgrade check/whatever, and still have Health Check passing. > So the current idea is to check configuration change history and compare config change timestamps with last time the service check for related service was run. > Also log to Ambari log timestamps of latest service checks for services, and timestamps of latest service config changes (INFO level) -- This message was sent by Atlassian JIRA (v6.3.4#6332)