[jira] [Updated] (RANGER-1552) Ranger usersync or ranger kms not able to communicate to ranger admin and no exception or error seen in the ranger user sync or kms logs.

2019-07-02 Thread Velmurugan Periasamy (JIRA)


 [ 
https://issues.apache.org/jira/browse/RANGER-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Velmurugan Periasamy updated RANGER-1552:
-
Fix Version/s: (was: 2.0.0)

> Ranger usersync or ranger kms not able to communicate to ranger admin and no 
> exception or error seen in the ranger user sync or kms logs.
> -
>
> Key: RANGER-1552
> URL: https://issues.apache.org/jira/browse/RANGER-1552
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Affects Versions: 0.7.0, 0.6.2
>Reporter: Madhavi Amirneni
>Assignee: Madhavi Amirneni
>Priority: Minor
> Attachments: RANGER-1552-handle-create-keystore-error.patch
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> Ranger usersync or ranger kms not able to communicate to ranger admin because 
> there was an error during the keystore creation and information was logged or 
> exception thrown for the error. This occurred because the default 
> communication between ranger admin and Ranger usersync or ranger kms is SSL 
> enabled.  
> When ranger is installed through ambari, a connection failed alert is 
> displayed regarding this. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (RANGER-1552) Ranger usersync or ranger kms not able to communicate to ranger admin and no exception or error seen in the ranger user sync or kms logs.

2018-07-02 Thread Velmurugan Periasamy (JIRA)


 [ 
https://issues.apache.org/jira/browse/RANGER-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Velmurugan Periasamy updated RANGER-1552:
-
Fix Version/s: (was: master)
   2.0.0

> Ranger usersync or ranger kms not able to communicate to ranger admin and no 
> exception or error seen in the ranger user sync or kms logs.
> -
>
> Key: RANGER-1552
> URL: https://issues.apache.org/jira/browse/RANGER-1552
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Affects Versions: 0.7.0, 0.6.2
>Reporter: Madhavi Amirneni
>Assignee: Madhavi Amirneni
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: RANGER-1552-handle-create-keystore-error.patch
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> Ranger usersync or ranger kms not able to communicate to ranger admin because 
> there was an error during the keystore creation and information was logged or 
> exception thrown for the error. This occurred because the default 
> communication between ranger admin and Ranger usersync or ranger kms is SSL 
> enabled.  
> When ranger is installed through ambari, a connection failed alert is 
> displayed regarding this. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (RANGER-1552) Ranger usersync or ranger kms not able to communicate to ranger admin and no exception or error seen in the ranger user sync or kms logs.

2017-05-02 Thread Madhavi Amirneni (JIRA)

 [ 
https://issues.apache.org/jira/browse/RANGER-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Madhavi Amirneni updated RANGER-1552:
-
Attachment: RANGER-1552-handle-create-keystore-error.patch

> Ranger usersync or ranger kms not able to communicate to ranger admin and no 
> exception or error seen in the ranger user sync or kms logs.
> -
>
> Key: RANGER-1552
> URL: https://issues.apache.org/jira/browse/RANGER-1552
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Affects Versions: 0.7.0, 0.6.2
>Reporter: Madhavi Amirneni
>Assignee: Madhavi Amirneni
>Priority: Minor
> Attachments: RANGER-1552-handle-create-keystore-error.patch
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> Ranger usersync or ranger kms not able to communicate to ranger admin because 
> there was an error during the keystore creation and information was logged or 
> exception thrown for the error. This occurred because the default 
> communication between ranger admin and Ranger usersync or ranger kms is SSL 
> enabled.  
> When ranger is installed through ambari, a connection failed alert is 
> displayed regarding this. 



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


[jira] [Updated] (RANGER-1552) Ranger usersync or ranger kms not able to communicate to ranger admin and no exception or error seen in the ranger user sync or kms logs.

2017-05-01 Thread Madhavi Amirneni (JIRA)

 [ 
https://issues.apache.org/jira/browse/RANGER-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Madhavi Amirneni updated RANGER-1552:
-
Request participants:   (was: )
  Remaining Estimate: 2h
   Original Estimate: 2h

> Ranger usersync or ranger kms not able to communicate to ranger admin and no 
> exception or error seen in the ranger user sync or kms logs.
> -
>
> Key: RANGER-1552
> URL: https://issues.apache.org/jira/browse/RANGER-1552
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Affects Versions: 0.7.0, 0.6.2
>Reporter: Madhavi Amirneni
>Priority: Minor
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> Ranger usersync or ranger kms not able to communicate to ranger admin because 
> there was an error during the keystore creation and information was logged or 
> exception thrown for the error. This occurred because the default 
> communication between ranger admin and Ranger usersync or ranger kms is SSL 
> enabled.  
> When ranger is installed through ambari, a connection failed alert is 
> displayed regarding this. 



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