[
https://issues.apache.org/jira/browse/AMBARI-20924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15995820#comment-15995820
]
Hudson commented on AMBARI-20924:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1498 (See
[https://builds.apache.org/job/Ambari-branch-2.5/1498/])
AMBARI-20924 - Old Status Command Structured Output is Returned on Every
(jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=3f5ea585f5c150428a0ee80f95558c3668d4a75c])
* (edit)
ambari-common/src/main/python/resource_management/libraries/script/script.py
* (edit) ambari-agent/src/test/python/resource_management/TestScript.py
> Old Status Command Structured Output is Returned on Every Status Command
> Causing Upgrades to Fail
> -------------------------------------------------------------------------------------------------
>
> Key: AMBARI-20924
> URL: https://issues.apache.org/jira/browse/AMBARI-20924
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.5.1
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Priority: Blocker
> Fix For: 2.5.1
>
> Attachments: AMBARI-20924.patch
>
>
> Possibly caused by AMBARI-20750:
> Upgrades are failing because of a {{VERSION_MISMATCH}} between all components
> of the upgrade. Initially, on restart, the version comes back correct and the
> host component transitions into {{COMPLETED}}.
> However, the following status command returns the old version, forcing the
> component back into the {{VERSION_MISMATCH}} state.
> What's odd is that no status commands should be returning the component
> version. It seems like what's happening is that
> {{/var/lib/ambari-agent/data/structured-out-status.json}} is being read even
> if the status command did not update the file.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
