[
https://issues.apache.org/jira/browse/AMBARI-9731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14329401#comment-14329401
]
Hudson commented on AMBARI-9731:
--------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #1824 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/1824/])
AMBARI-9731 - RU: Need a way to bypass failed service checks during upgrade
(tbeerbower) (tbeerbower:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=1eeaf523cb25263796387ead560b3e29e873ea9b)
* ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.2.xml
> 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)
