[ https://issues.apache.org/jira/browse/AMBARI-18899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15670331#comment-15670331 ]
Hudson commented on AMBARI-18899: --------------------------------- FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #336 (See [https://builds.apache.org/job/Ambari-branch-2.5/336/]) AMBARI-18899. Post Upgrade to Ambari 2.4.1 from 2.2.2 --> All stack (dlysnichenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=ce4c0cd6407eab01112e77024f034f0539bb89da]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.2/services/HDFS/configuration/hdfs-site.xml * (edit) ambari-server/src/main/resources/stacks/PHD/3.0/services/HDFS/configuration/core-site.xml * (edit) ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/configuration/hadoop-env.xml * (edit) ambari-server/src/main/resources/stacks/PHD/3.0/services/HDFS/configuration/hdfs-site.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.2/services/HDFS/configuration/core-site.xml > Post Upgrade to Ambari 2.4.1 from 2.2.2 --> All stack component prompted for > restart > ------------------------------------------------------------------------------------ > > Key: AMBARI-18899 > URL: https://issues.apache.org/jira/browse/AMBARI-18899 > Project: Ambari > Issue Type: Bug > Components: ambari-server > Affects Versions: 2.4.2 > Reporter: Dmitry Lysnichenko > Assignee: Dmitry Lysnichenko > Fix For: 2.5.0 > > Attachments: AMBARI-18899.patch > > > I think not marking HDFS as restart required when Ambari upgrades is a good > goal. > In general its a difficult to get it right for all services. > * hadoop.security.key.provider.path > * dfs.encryption.key.provider.uri > These two are removed by stack advisor when RANGER KMS does not exist. We > should find out why it got added on Ambari upgrade. This seems like a bug to > me. > * namenode_backup_dir -- This message was sent by Atlassian JIRA (v6.3.4#6332)