[jira] [Commented] (AMBARI-20346) Log Search Upgrade should modify keystore / truststore path if it wasn't used

2017-03-08 Thread Hudson (JIRA)

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

Hudson commented on AMBARI-20346:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1212 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/1212/])
AMBARI-20346 Log Search Upgrade should modify keystore / truststore path 
(mgergely: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=546225f326323a5d6e6013c8413a36180e0b0d32])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java
* (edit) 
ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/package/scripts/params.py


> Log Search Upgrade should modify keystore / truststore path if it wasn't used
> -
>
> Key: AMBARI-20346
> URL: https://issues.apache.org/jira/browse/AMBARI-20346
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch
>Affects Versions: 2.5.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
> Fix For: 2.5.0
>
> Attachments: AMBARI-20346.patch
>
>
> The default path for the truststore / keystore in 2.4 was under 
> /etc/security, which may cause permission problems. If the user haven't used 
> the keystore / truststore, and haven't altered the path yet it should be 
> modified upon upgrade to the new default value.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (AMBARI-20346) Log Search Upgrade should modify keystore / truststore path if it wasn't used

2017-03-08 Thread Hudson (JIRA)

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

Hudson commented on AMBARI-20346:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6975 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6975/])
AMBARI-20346 Log Search Upgrade should modify keystore / truststore path 
(mgergely: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=5700ecca4ac86ac66691929624d2cd4a6056b3aa])
* (edit) 
ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/package/scripts/params.py
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java


> Log Search Upgrade should modify keystore / truststore path if it wasn't used
> -
>
> Key: AMBARI-20346
> URL: https://issues.apache.org/jira/browse/AMBARI-20346
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch
>Affects Versions: 2.5.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
> Fix For: 2.5.0
>
> Attachments: AMBARI-20346.patch
>
>
> The default path for the truststore / keystore in 2.4 was under 
> /etc/security, which may cause permission problems. If the user haven't used 
> the keystore / truststore, and haven't altered the path yet it should be 
> modified upon upgrade to the new default value.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (AMBARI-20346) Log Search Upgrade should modify keystore / truststore path if it wasn't used

2017-03-08 Thread Miklos Gergely (JIRA)

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

Miklos Gergely commented on AMBARI-20346:
-

committed to trunk:
{code:java}
commit 5700ecca4ac86ac66691929624d2cd4a6056b3aa
Author: Miklos Gergely 
Date:   Wed Mar 8 16:31:26 2017 +0100

AMBARI-20346 Log Search Upgrade should modify keystore / truststore path if 
it wasn't used (mgergely)

Change-Id: I0ee470fba0ea7b28ca92d64e10e2dff90ac51d91
{code}

committed to branch-2.5:
{code:java}
commit 24242e7b3a34b1af8185a40e98d7d08d2e9f
Author: Miklos Gergely 
Date:   Wed Mar 8 16:32:28 2017 +0100

AMBARI-20346 Log Search Upgrade should modify keystore / truststore path if 
it wasn't used (mgergely)

Change-Id: Ib5614acea9667205b2eaecbd57e3d4ec3c560f5f
{code}

> Log Search Upgrade should modify keystore / truststore path if it wasn't used
> -
>
> Key: AMBARI-20346
> URL: https://issues.apache.org/jira/browse/AMBARI-20346
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch
>Affects Versions: 2.5.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
> Fix For: 2.5.0
>
> Attachments: AMBARI-20346.patch
>
>
> The default path for the truststore / keystore in 2.4 was under 
> /etc/security, which may cause permission problems. If the user haven't used 
> the keystore / truststore, and haven't altered the path yet it should be 
> modified upon upgrade to the new default value.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (AMBARI-20346) Log Search Upgrade should modify keystore / truststore path if it wasn't used

2017-03-07 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on AMBARI-20346:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12856637/AMBARI-20346.patch
  against trunk revision .

{color:red}-1 patch{color}.  Top-level trunk compilation may be broken.

Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/10918//console

This message is automatically generated.

> Log Search Upgrade should modify keystore / truststore path if it wasn't used
> -
>
> Key: AMBARI-20346
> URL: https://issues.apache.org/jira/browse/AMBARI-20346
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch
>Affects Versions: 2.5.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
> Fix For: 2.5.0
>
> Attachments: AMBARI-20346.patch
>
>
> The default path for the truststore / keystore in 2.4 was under 
> /etc/security, which may cause permission problems. If the user haven't used 
> the keystore / truststore, and haven't altered the path yet it should be 
> modified upon upgrade to the new default value.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)