ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jayush Luniya (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-13872) Rolling Upgrade: Configuration Groups not applied for upgrades across stack versions
Date Fri, 13 Nov 2015 19:26:11 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-13872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15004554#comment-15004554
] 

Jayush Luniya commented on AMBARI-13872:
----------------------------------------

No new test cases required. Failures are not related to this change.


Trunk:
commit 3a84d5f4a87b8de68685fdfde242e782c9e1e07f
Author: Jayush Luniya <jluniya@hortonworks.com>
Date:   Fri Nov 13 11:23:15 2015 -0800

    AMBARI-13872: Rolling Upgrade: Configuration Groups not applied for upgrades across stack
versions (jluniya)

Branch-2.1:
commit a4bab22df39f4d790d955055a08c9fe72082ca71
Author: Jayush Luniya <jluniya@hortonworks.com>
Date:   Fri Nov 13 11:23:15 2015 -0800

    AMBARI-13872: Rolling Upgrade: Configuration Groups not applied for upgrades across stack
versions (jluniya)



> Rolling Upgrade: Configuration Groups not applied for upgrades across stack versions
> ------------------------------------------------------------------------------------
>
>                 Key: AMBARI-13872
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13872
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Jayush Luniya
>            Assignee: Jayush Luniya
>            Priority: Critical
>         Attachments: AMBARI-13872.patch
>
>
> 1. RU is underway
> 2. Datanodes are upgraded.
> 3 When DN is started, it comes online with default config group , thereby losing its
other data mount points.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message