[ https://issues.apache.org/jira/browse/AMBARI-13872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15004876#comment-15004876 ]
Hudson commented on AMBARI-13872: --------------------------------- ABORTED: Integrated in Ambari-trunk-Commit #3833 (See [https://builds.apache.org/job/Ambari-trunk-Commit/3833/]) AMBARI-13872: Rolling Upgrade: Configuration Groups not applied for (jluniya: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=3a84d5f4a87b8de68685fdfde242e782c9e1e07f]) * ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ExecutionCommandWrapper.java > 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)