[jira] [Commented] (AMBARI-18899) Post Upgrade to Ambari 2.4.1 from 2.2.2 --> All stack component prompted for restart
[ https://issues.apache.org/jira/browse/AMBARI-18899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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=commit=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)
[jira] [Commented] (AMBARI-18899) Post Upgrade to Ambari 2.4.1 from 2.2.2 --> All stack component prompted for restart
[ https://issues.apache.org/jira/browse/AMBARI-18899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15670343#comment-15670343 ] Hudson commented on AMBARI-18899: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6025 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6025/]) 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=commit=61942e55a8fd09b90f320fb2bf7dcc68eee0eeca]) * (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/HDP/2.2/services/HDFS/configuration/hdfs-site.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.2/services/HDFS/configuration/core-site.xml * (edit) ambari-server/src/main/resources/stacks/PHD/3.0/services/HDFS/configuration/core-site.xml * (edit) ambari-server/src/main/resources/stacks/PHD/3.0/services/HDFS/configuration/hdfs-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)
[jira] [Commented] (AMBARI-18899) Post Upgrade to Ambari 2.4.1 from 2.2.2 --> All stack component prompted for restart
[
https://issues.apache.org/jira/browse/AMBARI-18899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668809#comment-15668809
]
Hadoop QA commented on AMBARI-18899:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12839012/AMBARI-18899.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9290//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9290//console
This message is automatically generated.
> 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)
