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

Hadoop QA commented on AMBARI-16134:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12800973/AMBARI-16134.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

    {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:red}-1 core tests{color}.  The test build failed in ambari-server 

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/6683//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/6683//console

This message is automatically generated.

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

Reply via email to