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-21626) Configs For Target Stack Are Not Created During Upgrade
Date Wed, 02 Aug 2017 15:05:01 GMT

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

Jonathan Hurley updated AMBARI-21626:
-------------------------------------
    Status: Patch Available  (was: Open)

> Configs For Target Stack Are Not Created During Upgrade
> -------------------------------------------------------
>
>                 Key: AMBARI-21626
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21626
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 2.6.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Blocker
>             Fix For: 2.6.0
>
>         Attachments: AMBARI-21626.patch
>
>
> During an upgrade from HDP 2.5 to HDP 2.6, the new configurations are not created in
HDP 2.6 - they're created in HDP 2.5 which causes services to fail on restart.
> STR:
> - Create an HDP 2.5 cluster with ZK + HDFS
> - Do an EU to HDP 2.6
> The EU will fail right after the "move stack version" step.
> It looks like the bug is in {{ConfigHelper}} where it ignores the passed-in {{StackId}}
and uses the Cluster's stack:
> {code}
>   Config createConfig(Cluster cluster, StackId stackId, AmbariManagementController controller,
>       String type, String tag, Map<String, String> properties,
>       Map<String, Map<String, String>> propertyAttributes) throws AmbariException
{
>         ...
>     return controller.createConfig(cluster, type, properties, tag, propertyAttributes);
>   }
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message