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

Hadoop QA commented on AMBARI-9731:
-----------------------------------

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

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

    {color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
                        Please justify why no new tests are needed for this 
patch.
                        Also please list what manual steps were performed to 
verify this patch.

    {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:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-server.

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

This message is automatically generated.

> RU: Need a way to bypass failed service checks during upgrade
> -------------------------------------------------------------
>
>                 Key: AMBARI-9731
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9731
>             Project: Ambari
>          Issue Type: Task
>            Reporter: Tom Beerbower
>            Assignee: Tom Beerbower
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-9731.patch
>
>
> During the upgrade process my Oozie service check timeout after 300 seconds.  
> I've manually validated that the service is fine and can run the smoke test 
> script manually, but it completes in 410 seconds.  Either we increase the 
> service check, or we allow users to bypass failed service checks.
> If timeouts occur, and there is no way to bypass, you have to downgrade. 
> Providing users a way to "Proceed Anyway" to ship the check would be useful 
> to push forward.



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

Reply via email to