You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ambari.apache.org by "Viraj Jasani (JIRA)" <ji...@apache.org> on 2019/07/11 10:55:00 UTC

[jira] [Resolved] (AMBARI-25309) Desired stack id is not updated for Rolling Upgrade

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

Viraj Jasani resolved AMBARI-25309.
-----------------------------------
    Resolution: Duplicate

> Desired stack id is not updated for Rolling Upgrade
> ---------------------------------------------------
>
>                 Key: AMBARI-25309
>                 URL: https://issues.apache.org/jira/browse/AMBARI-25309
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.7.4
>            Reporter: Viraj Jasani
>            Assignee: Viraj Jasani
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 2.7.4
>
>          Time Spent: 2h
>  Remaining Estimate: 0h
>
> After Rolling Upgrade is performed, Desired Stack id is not updated in clusters table. We should update it otherwise many subsequent operations present undesired behavior e.g. if desired stack id is not updated after successful upgrade from stack 2.2 to 2.3, any new service onboarding to stack 2.3 fails since Ambari tries to onboard new service to stack 2.2(old desired stack id, where new service code might not be present)



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)