ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-16134) Force running service checks for services before upgrade
Date Thu, 28 Apr 2016 21:18:13 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-16134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15263026#comment-15263026
] 

Hudson commented on AMBARI-16134:
---------------------------------

FAILURE: Integrated in Ambari-trunk-Commit #4759 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4759/])
AMBARI-16134. Force running service checks for services before upgrade (dlysnichenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=1b49c6c97f3a38652b9b8231b7c65cec2c2a0a2e])
* ambari-server/src/main/java/org/apache/ambari/server/checks/CheckDescription.java
* ambari-server/src/main/java/org/apache/ambari/server/checks/HealthCheck.java
* ambari-server/src/test/java/org/apache/ambari/server/checks/ServiceCheckValidityCheckTest.java
* ambari-server/src/main/java/org/apache/ambari/server/checks/ServiceCheckValidityCheck.java


> 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)

Mime
View raw message