ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-18899) Post Upgrade to Ambari 2.4.1 from 2.2.2 --> All stack component prompted for restart
Date Wed, 16 Nov 2016 00:05:58 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-18899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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)

Mime
View raw message