ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Hurley (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-20924) Old Status Command Structured Output is Returned on Every Status Command Causing Upgrades to Fail
Date Wed, 03 May 2017 21:49:04 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-20924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Hurley updated AMBARI-20924:
-------------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

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

Mime
View raw message