[jira] [Assigned] (AMBARI-18099) Ranger policies not syncing when Hive-server-Hive2 is installed on a seperate host.
[ https://issues.apache.org/jira/browse/AMBARI-18099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia reassigned AMBARI-18099: --- Assignee: Vishal Suvagia > Ranger policies not syncing when Hive-server-Hive2 is installed on a seperate > host. > --- > > Key: AMBARI-18099 > URL: https://issues.apache.org/jira/browse/AMBARI-18099 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.4.0 > > > Ranger policies not syncing when Hive-server-Hive2 is installed on a seperate > host and is SSL enabled -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18099) Ranger policies not syncing when Hive-server-Hive2 is installed on a seperate host.
[ https://issues.apache.org/jira/browse/AMBARI-18099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-18099: Attachment: (was: AMBARI-18099.patch) > Ranger policies not syncing when Hive-server-Hive2 is installed on a seperate > host. > --- > > Key: AMBARI-18099 > URL: https://issues.apache.org/jira/browse/AMBARI-18099 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.4.0 > > Attachments: AMBARI-18099.patch > > > Ranger policies not syncing when Hive-server-Hive2 is installed on a seperate > host and is SSL enabled -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18099) Ranger policies not syncing when Hive-server-Hive2 is installed on a seperate host.
[ https://issues.apache.org/jira/browse/AMBARI-18099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-18099: Status: Patch Available (was: In Progress) > Ranger policies not syncing when Hive-server-Hive2 is installed on a seperate > host. > --- > > Key: AMBARI-18099 > URL: https://issues.apache.org/jira/browse/AMBARI-18099 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.4.0 > > Attachments: AMBARI-18099.patch > > > Ranger policies not syncing when Hive-server-Hive2 is installed on a seperate > host and is SSL enabled -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18099) Ranger policies not syncing when Hive-server-Hive2 is installed on a seperate host.
[ https://issues.apache.org/jira/browse/AMBARI-18099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-18099: Attachment: AMBARI-18099.patch > Ranger policies not syncing when Hive-server-Hive2 is installed on a seperate > host. > --- > > Key: AMBARI-18099 > URL: https://issues.apache.org/jira/browse/AMBARI-18099 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.4.0 > > Attachments: AMBARI-18099.patch > > > Ranger policies not syncing when Hive-server-Hive2 is installed on a seperate > host and is SSL enabled -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18099) Ranger policies not syncing when Hive-server-Hive2 is installed on a seperate host.
Vishal Suvagia created AMBARI-18099: --- Summary: Ranger policies not syncing when Hive-server-Hive2 is installed on a seperate host. Key: AMBARI-18099 URL: https://issues.apache.org/jira/browse/AMBARI-18099 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.4.0 Reporter: Vishal Suvagia Fix For: 2.4.0 Ranger policies not syncing when Hive-server-Hive2 is installed on a seperate host and is SSL enabled -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18099) Ranger policies not syncing when Hive-server-Hive2 is installed on a seperate host.
[ https://issues.apache.org/jira/browse/AMBARI-18099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-18099: Attachment: AMBARI-18099.2.patch > Ranger policies not syncing when Hive-server-Hive2 is installed on a seperate > host. > --- > > Key: AMBARI-18099 > URL: https://issues.apache.org/jira/browse/AMBARI-18099 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-18099.1.patch, AMBARI-18099.2.patch, > AMBARI-18099.patch > > > Ranger policies not syncing when Hive-server-Hive2 is installed on a seperate > host and is SSL enabled -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18099) Ranger policies not syncing when Hive-server-Hive2 is installed on a seperate host.
[ https://issues.apache.org/jira/browse/AMBARI-18099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-18099: Attachment: AMBARI-18099.1.patch > Ranger policies not syncing when Hive-server-Hive2 is installed on a seperate > host. > --- > > Key: AMBARI-18099 > URL: https://issues.apache.org/jira/browse/AMBARI-18099 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.4.0 > > Attachments: AMBARI-18099.1.patch, AMBARI-18099.patch > > > Ranger policies not syncing when Hive-server-Hive2 is installed on a seperate > host and is SSL enabled -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18099) Ranger policies not syncing when Hive-server-Hive2 is installed on a seperate host.
[ https://issues.apache.org/jira/browse/AMBARI-18099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-18099: Resolution: Fixed Status: Resolved (was: Patch Available) committed to trunk : [bf80a34ee1f5c8d4854053e29c6ebefa2f6a9fa5|https://github.com/apache/ambari/commit/bf80a34ee1f5c8d4854053e29c6ebefa2f6a9fa5] > Ranger policies not syncing when Hive-server-Hive2 is installed on a seperate > host. > --- > > Key: AMBARI-18099 > URL: https://issues.apache.org/jira/browse/AMBARI-18099 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-18099.1.patch, AMBARI-18099.2.patch, > AMBARI-18099.patch > > > Ranger policies not syncing when Hive-server-Hive2 is installed on a seperate > host and is SSL enabled -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19864) Zookeeper namespace for Hive service should be taken from hive-interactive-site, when only Hive-server Interactive is installed.
[ https://issues.apache.org/jira/browse/AMBARI-19864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-19864: Resolution: Fixed Status: Resolved (was: Patch Available) > Zookeeper namespace for Hive service should be taken from > hive-interactive-site, when only Hive-server Interactive is installed. > > > Key: AMBARI-19864 > URL: https://issues.apache.org/jira/browse/AMBARI-19864 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19864.1.patch, AMBARI-19864.patch > > > If Hive-Server Interactive is installed independently, then zoo-keeper name > space for hive service configured for Ranger should be taken from > hive-interactive-site. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19864) Zookeeper namespace for Hive service should be taken from hive-interactive-site, when only Hive-server Interactive is installed.
[ https://issues.apache.org/jira/browse/AMBARI-19864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15853878#comment-15853878 ] Vishal Suvagia commented on AMBARI-19864: - Committed on [branch-2.5:|https://github.com/apache/ambari/commit/c7d6f27fd4b17258de181ad6c9bec726f3030a18] and [trunk:|https://github.com/apache/ambari/commit/95693516ca5ea9f44b6c04e38b3024fce06050a8] > Zookeeper namespace for Hive service should be taken from > hive-interactive-site, when only Hive-server Interactive is installed. > > > Key: AMBARI-19864 > URL: https://issues.apache.org/jira/browse/AMBARI-19864 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19864.1.patch, AMBARI-19864.patch > > > If Hive-Server Interactive is installed independently, then zoo-keeper name > space for hive service configured for Ranger should be taken from > hive-interactive-site. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19897) Provide user-warning while upgrading clusters to move certificates/keystores/truststores out of conf folder
[ https://issues.apache.org/jira/browse/AMBARI-19897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-19897: Attachment: (was: AMBARI-19897.patch) > Provide user-warning while upgrading clusters to move > certificates/keystores/truststores out of conf folder > --- > > Key: AMBARI-19897 > URL: https://issues.apache.org/jira/browse/AMBARI-19897 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > > As certificates/ keystores/ truststores present in /etc/ranger/*/conf path, > this may affect the upgrade scenarios, where user needs to manually move the > files to new conf directories. > Hence users upgrading to new stacks should be warned on prior basis to do the > same manually (i.e move certificates/keystores/truststores out of conf > folder). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19897) Provide user-warning while upgrading clusters to move certificates/keystores/truststores out of conf folder
[ https://issues.apache.org/jira/browse/AMBARI-19897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-19897: Attachment: AMBARI-19897.patch > Provide user-warning while upgrading clusters to move > certificates/keystores/truststores out of conf folder > --- > > Key: AMBARI-19897 > URL: https://issues.apache.org/jira/browse/AMBARI-19897 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19897.patch > > > As certificates/ keystores/ truststores present in /etc/ranger/*/conf path, > this may affect the upgrade scenarios, where user needs to manually move the > files to new conf directories. > Hence users upgrading to new stacks should be warned on prior basis to do the > same manually (i.e move certificates/keystores/truststores out of conf > folder). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19897) Provide user-warning while upgrading clusters to move certificates/keystores/truststores out of conf folder
[ https://issues.apache.org/jira/browse/AMBARI-19897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-19897: Status: Patch Available (was: Open) > Provide user-warning while upgrading clusters to move > certificates/keystores/truststores out of conf folder > --- > > Key: AMBARI-19897 > URL: https://issues.apache.org/jira/browse/AMBARI-19897 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19897.patch > > > As certificates/ keystores/ truststores present in /etc/ranger/*/conf path, > this may affect the upgrade scenarios, where user needs to manually move the > files to new conf directories. > Hence users upgrading to new stacks should be warned on prior basis to do the > same manually (i.e move certificates/keystores/truststores out of conf > folder). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19897) Provide user-warning while upgrading clusters to move certificates/keystores/truststores out of conf folder
[ https://issues.apache.org/jira/browse/AMBARI-19897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-19897: Attachment: AMBARI-19897.patch > Provide user-warning while upgrading clusters to move > certificates/keystores/truststores out of conf folder > --- > > Key: AMBARI-19897 > URL: https://issues.apache.org/jira/browse/AMBARI-19897 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19897.patch > > > As certificates/ keystores/ truststores present in /etc/ranger/*/conf path, > this may affect the upgrade scenarios, where user needs to manually move the > files to new conf directories. > Hence users upgrading to new stacks should be warned on prior basis to do the > same manually (i.e move certificates/keystores/truststores out of conf > folder). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-19897) Provide user-warning while upgrading clusters to move certificates/keystores/truststores out of conf folder
Vishal Suvagia created AMBARI-19897: --- Summary: Provide user-warning while upgrading clusters to move certificates/keystores/truststores out of conf folder Key: AMBARI-19897 URL: https://issues.apache.org/jira/browse/AMBARI-19897 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.5.0 Reporter: Vishal Suvagia Assignee: Vishal Suvagia Fix For: 2.5.0 As certificates/ keystores/ truststores present in /etc/ranger/*/conf path, this may affect the upgrade scenarios, where user needs to manually move the files to new conf directories. Hence users upgrading to new stacks should be warned on prior basis to do the same manually (i.e move certificates/keystores/truststores out of conf folder). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19864) Zookeeper namespace for Hive service should be taken from hive-interactive-site, when only Hive-server Interactive is installed.
[ https://issues.apache.org/jira/browse/AMBARI-19864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-19864: Attachment: AMBARI-19864.1.patch > Zookeeper namespace for Hive service should be taken from > hive-interactive-site, when only Hive-server Interactive is installed. > > > Key: AMBARI-19864 > URL: https://issues.apache.org/jira/browse/AMBARI-19864 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19864.1.patch, AMBARI-19864.patch > > > If Hive-Server Interactive is installed independently, then zoo-keeper name > space for hive service configured for Ranger should be taken from > hive-interactive-site. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-19864) Zookeeper namespace for Hive service should be taken from hive-interactive-site, when only Hive-server Interactive is installed.
Vishal Suvagia created AMBARI-19864: --- Summary: Zookeeper namespace for Hive service should be taken from hive-interactive-site, when only Hive-server Interactive is installed. Key: AMBARI-19864 URL: https://issues.apache.org/jira/browse/AMBARI-19864 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.5.0 Reporter: Vishal Suvagia Assignee: Vishal Suvagia Fix For: 2.5.0 If Hive-Server Interactive is installed independently, then zoo-keeper name space for hive service configured for Ranger should be taken from hive-interactive-site. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19864) Zookeeper namespace for Hive service should be taken from hive-interactive-site, when only Hive-server Interactive is installed.
[ https://issues.apache.org/jira/browse/AMBARI-19864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-19864: Status: Patch Available (was: In Progress) adding fix for the issue > Zookeeper namespace for Hive service should be taken from > hive-interactive-site, when only Hive-server Interactive is installed. > > > Key: AMBARI-19864 > URL: https://issues.apache.org/jira/browse/AMBARI-19864 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19864.patch > > > If Hive-Server Interactive is installed independently, then zoo-keeper name > space for hive service configured for Ranger should be taken from > hive-interactive-site. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19864) Zookeeper namespace for Hive service should be taken from hive-interactive-site, when only Hive-server Interactive is installed.
[ https://issues.apache.org/jira/browse/AMBARI-19864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-19864: Attachment: AMBARI-19864.patch > Zookeeper namespace for Hive service should be taken from > hive-interactive-site, when only Hive-server Interactive is installed. > > > Key: AMBARI-19864 > URL: https://issues.apache.org/jira/browse/AMBARI-19864 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19864.patch > > > If Hive-Server Interactive is installed independently, then zoo-keeper name > space for hive service configured for Ranger should be taken from > hive-interactive-site. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] (AMBARI-19524) Use stack-level Atlas conf directory instead of hard-coded /etc/atlas/conf path
Title: Message Title Vishal Suvagia updated AMBARI-19524 Committed to trunk and branch-2.5 Ambari / AMBARI-19524 Use stack-level Atlas conf directory instead of hard-coded /etc/atlas/conf path Change By: Vishal Suvagia Resolution: Fixed Status: Patch Available Resolved Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
[jira] [Updated] (AMBARI-19524) Use stack-level Atlas conf directory instead of hard-coded /etc/atlas/conf path
[
https://issues.apache.org/jira/browse/AMBARI-19524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Suvagia updated AMBARI-19524:
Attachment: AMBARI-19524.1.patch
> Use stack-level Atlas conf directory instead of hard-coded /etc/atlas/conf
> path
> ---
>
> Key: AMBARI-19524
> URL: https://issues.apache.org/jira/browse/AMBARI-19524
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
> Environment: All
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
> Fix For: 2.5.0
>
> Attachments: AMBARI-19524.1.patch, AMBARI-19524_branch-2.5.patch,
> AMBARI-19524_trunk.patch
>
>
> This is a bug that should have been fixed in Ambari 2.4 but showed up too
> late in the release and has repercussions to test it.
> Basically, status_params.py for Atlas service in Ambari sets
> {code}
> conf_dir = os.environ['METADATA_CONF'] if 'METADATA_CONF' in os.environ else
> '/etc/atlas/conf'
> {code}
> This is technically incorrect since /etc/atlas/conf is a symlink to
> /usr/hdp/current/atlas-client/conf, which is then a symlink to
> /etc/atlas/$some_version/0
> During Rolling Upgrade,
> 1. Atlas Server is stopped, new configs are written to
> /etc/atlas/$new_version/0, then symlink is changed so that
> /usr/hdp/current/atlas-server points to new version, and Atlas Server is
> started
> At this point, /etc/atlas/conf -> /usr/hdp/current/atlas-client/conf (which
> is still using the old version) since the client has not yet been updated.
> 2. Atlas Client has new configs written to /etc/atlas/$new_version/0, then
> symlink is changed so that /usr/hdp/current/atlas-client points to new version
> Basically, we need to look at the usages of conf_dir and make sure it is
> correct during all scenarios.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-20116) Stack Recommendation for Atlas not working on change of Kafka broker port.
Vishal Suvagia created AMBARI-20116: --- Summary: Stack Recommendation for Atlas not working on change of Kafka broker port. Key: AMBARI-20116 URL: https://issues.apache.org/jira/browse/AMBARI-20116 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.5.0 Reporter: Vishal Suvagia Assignee: Vishal Suvagia Fix For: 2.5.0 When Kafka-broker port is changed, appropriate change should be made for Atlas Kafla broker servers, this does not happen as stack-dependency for the same is missing. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20116) Stack Recommendation for Atlas not working on change of Kafka broker port.
[ https://issues.apache.org/jira/browse/AMBARI-20116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-20116: Attachment: AMBARI-20116.patch > Stack Recommendation for Atlas not working on change of Kafka broker port. > -- > > Key: AMBARI-20116 > URL: https://issues.apache.org/jira/browse/AMBARI-20116 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-20116.patch > > > When Kafka-broker port is changed, appropriate change should be made for > Atlas Kafla broker servers, this does not happen as stack-dependency for the > same is missing. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20116) Stack Recommendation for Atlas not working on change of Kafka broker port.
[ https://issues.apache.org/jira/browse/AMBARI-20116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-20116: Status: Patch Available (was: In Progress) > Stack Recommendation for Atlas not working on change of Kafka broker port. > -- > > Key: AMBARI-20116 > URL: https://issues.apache.org/jira/browse/AMBARI-20116 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-20116.patch > > > When Kafka-broker port is changed, appropriate change should be made for > Atlas Kafla broker servers, this does not happen as stack-dependency for the > same is missing. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20047) Repository config user needs to set customized service user in Ranger when service plugin is enabled
[
https://issues.apache.org/jira/browse/AMBARI-20047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Suvagia updated AMBARI-20047:
Attachment: AMBARI-20047.1.patch
revised code to optimize logic.
> Repository config user needs to set customized service user in Ranger when
> service plugin is enabled
>
>
> Key: AMBARI-20047
> URL: https://issues.apache.org/jira/browse/AMBARI-20047
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
> Fix For: 2.5.0
>
> Attachments: AMBARI-20047.1.patch, AMBARI-20047.patch
>
>
> The property {{REPOSITORY_CONFIG_USERNAME}} in Advanced
> ranger-*-plugin-properties is not updated to the custom user-name when
> services are using custom users.
> This causes issues especially in cases of Test connection, and policy user
> which is given default permissions in Ranger.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20116) Stack Recommendation for Atlas not working on change of Kafka broker port.
[ https://issues.apache.org/jira/browse/AMBARI-20116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-20116: Resolution: Fixed Status: Resolved (was: Patch Available) Commited on [branch-2.5|https://github.com/apache/ambari/commit/7ee057287fad43b3269199310709dd7c6331a2e6] and [trunk|https://github.com/apache/ambari/commit/7d1e04b39709df51a94343b1ee699a4b002ac3d3] > Stack Recommendation for Atlas not working on change of Kafka broker port. > -- > > Key: AMBARI-20116 > URL: https://issues.apache.org/jira/browse/AMBARI-20116 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-20116.patch > > > When Kafka-broker port is changed, appropriate change should be made for > Atlas Kafla broker servers, this does not happen as stack-dependency for the > same is missing. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20047) Repository config user needs to set customized service user in Ranger when service plugin is enabled
[
https://issues.apache.org/jira/browse/AMBARI-20047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Suvagia updated AMBARI-20047:
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed on
[branch-2.5|https://github.com/apache/ambari/commit/e2c92d5f6b5d0ba8c7d749266fa7b44235f7810f]
and
[trunk|https://github.com/apache/ambari/commit/14a99627bae2eeb108cfd1b45b953d3c667e8006]
> Repository config user needs to set customized service user in Ranger when
> service plugin is enabled
>
>
> Key: AMBARI-20047
> URL: https://issues.apache.org/jira/browse/AMBARI-20047
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
> Fix For: 2.5.0
>
> Attachments: AMBARI-20047.1.patch, AMBARI-20047.2_trunk.patch,
> AMBARI-20047_branch_2.5.patch, AMBARI-20047.patch
>
>
> The property {{REPOSITORY_CONFIG_USERNAME}} in Advanced
> ranger-*-plugin-properties is not updated to the custom user-name when
> services are using custom users.
> This causes issues especially in cases of Test connection, and policy user
> which is given default permissions in Ranger.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-19993) Update atlas log-4j.xml configurations in ambari
Vishal Suvagia created AMBARI-19993: --- Summary: Update atlas log-4j.xml configurations in ambari Key: AMBARI-19993 URL: https://issues.apache.org/jira/browse/AMBARI-19993 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.5.0 Reporter: Vishal Suvagia Assignee: Vishal Suvagia Fix For: 2.5.0 Need to update atlas-log4j configurations in ambari to reflect latest in atlas. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19993) Update atlas log-4j.xml configurations in ambari
[ https://issues.apache.org/jira/browse/AMBARI-19993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-19993: Attachment: AMBARI-19993.patch > Update atlas log-4j.xml configurations in ambari > > > Key: AMBARI-19993 > URL: https://issues.apache.org/jira/browse/AMBARI-19993 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19993.patch > > > Need to update atlas-log4j configurations in ambari to reflect latest in > atlas. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19897) Provide user-warning while upgrading clusters to move certificates/keystores/truststores out of conf folder
[ https://issues.apache.org/jira/browse/AMBARI-19897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-19897: Resolution: Fixed Status: Resolved (was: Patch Available) committed to [branch-2.5|https://github.com/apache/ambari/commit/0392cabdab5ad6469e08f404370f35cd14cfd0bf] and [trunk|https://github.com/apache/ambari/commit/31944e382019482ee40e8ec4c691b6aea7fce230] > Provide user-warning while upgrading clusters to move > certificates/keystores/truststores out of conf folder > --- > > Key: AMBARI-19897 > URL: https://issues.apache.org/jira/browse/AMBARI-19897 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19897.1.patch, AMBARI-19897.patch > > > As certificates/ keystores/ truststores present in /etc/ranger/*/conf path, > this may affect the upgrade scenarios, where user needs to manually move the > files to new conf directories. > Hence users upgrading to new stacks should be warned on prior basis to do the > same manually (i.e move certificates/keystores/truststores out of conf > folder). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-19993) Update atlas log-4j.xml configurations in ambari
[ https://issues.apache.org/jira/browse/AMBARI-19993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia resolved AMBARI-19993. - Resolution: Fixed committed on [trunk|https://github.com/apache/ambari/commit/e52fbc3a88f814f9731cb6a4e404ed4ffd608897] and [branch-2.5|https://github.com/apache/ambari/commit/baae985a69a55a5e72b49922c578ba8da810383f] > Update atlas log-4j.xml configurations in ambari > > > Key: AMBARI-19993 > URL: https://issues.apache.org/jira/browse/AMBARI-19993 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19993.patch > > > Need to update atlas-log4j configurations in ambari to reflect latest in > atlas. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19897) Provide user-warning while upgrading clusters to move certificates/keystores/truststores out of conf folder
[ https://issues.apache.org/jira/browse/AMBARI-19897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-19897: Attachment: AMBARI-19897.1.patch > Provide user-warning while upgrading clusters to move > certificates/keystores/truststores out of conf folder > --- > > Key: AMBARI-19897 > URL: https://issues.apache.org/jira/browse/AMBARI-19897 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19897.1.patch, AMBARI-19897.patch > > > As certificates/ keystores/ truststores present in /etc/ranger/*/conf path, > this may affect the upgrade scenarios, where user needs to manually move the > files to new conf directories. > Hence users upgrading to new stacks should be warned on prior basis to do the > same manually (i.e move certificates/keystores/truststores out of conf > folder). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-20047) Repository config user needs to set customized service user in Ranger when service plugin is enabled
[
https://issues.apache.org/jira/browse/AMBARI-20047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Suvagia reassigned AMBARI-20047:
---
Assignee: Vishal Suvagia
> Repository config user needs to set customized service user in Ranger when
> service plugin is enabled
>
>
> Key: AMBARI-20047
> URL: https://issues.apache.org/jira/browse/AMBARI-20047
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
> Fix For: 2.5.0
>
>
> The property {{REPOSITORY_CONFIG_USERNAME}} in Advanced
> ranger-*-plugin-properties is not updated to the custom user-name when
> services are using custom users.
> This causes issues especially in cases of Test connection, and policy user
> which is given default permissions in Ranger.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20047) Repository config user needs to set customized service user in Ranger when service plugin is enabled
Vishal Suvagia created AMBARI-20047:
---
Summary: Repository config user needs to set customized service
user in Ranger when service plugin is enabled
Key: AMBARI-20047
URL: https://issues.apache.org/jira/browse/AMBARI-20047
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.5.0
Reporter: Vishal Suvagia
Fix For: 2.5.0
The property {{REPOSITORY_CONFIG_USERNAME}} in Advanced
ranger-*-plugin-properties is not updated to the custom user-name when services
are using custom users.
This causes issues especially in cases of Test connection, and policy user
which is given default permissions in Ranger.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20047) Repository config user needs to set customized service user in Ranger when service plugin is enabled
[
https://issues.apache.org/jira/browse/AMBARI-20047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Suvagia updated AMBARI-20047:
Status: Patch Available (was: In Progress)
> Repository config user needs to set customized service user in Ranger when
> service plugin is enabled
>
>
> Key: AMBARI-20047
> URL: https://issues.apache.org/jira/browse/AMBARI-20047
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
> Fix For: 2.5.0
>
> Attachments: AMBARI-20047.patch
>
>
> The property {{REPOSITORY_CONFIG_USERNAME}} in Advanced
> ranger-*-plugin-properties is not updated to the custom user-name when
> services are using custom users.
> This causes issues especially in cases of Test connection, and policy user
> which is given default permissions in Ranger.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20047) Repository config user needs to set customized service user in Ranger when service plugin is enabled
[
https://issues.apache.org/jira/browse/AMBARI-20047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Suvagia updated AMBARI-20047:
Attachment: AMBARI-20047.patch
> Repository config user needs to set customized service user in Ranger when
> service plugin is enabled
>
>
> Key: AMBARI-20047
> URL: https://issues.apache.org/jira/browse/AMBARI-20047
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
> Fix For: 2.5.0
>
> Attachments: AMBARI-20047.patch
>
>
> The property {{REPOSITORY_CONFIG_USERNAME}} in Advanced
> ranger-*-plugin-properties is not updated to the custom user-name when
> services are using custom users.
> This causes issues especially in cases of Test connection, and policy user
> which is given default permissions in Ranger.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20208) Atlas kafka servers should be configured using kafka listeners.
Vishal Suvagia created AMBARI-20208: --- Summary: Atlas kafka servers should be configured using kafka listeners. Key: AMBARI-20208 URL: https://issues.apache.org/jira/browse/AMBARI-20208 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.5.0 Reporter: Vishal Suvagia Assignee: Vishal Suvagia Fix For: 2.5.0 Atlas kafka listeners should be configured to use the port value configured in kafka-broker listeners, instead of the port property. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20208) Atlas kafka servers should be configured using kafka listeners.
[ https://issues.apache.org/jira/browse/AMBARI-20208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-20208: Status: Patch Available (was: In Progress) > Atlas kafka servers should be configured using kafka listeners. > --- > > Key: AMBARI-20208 > URL: https://issues.apache.org/jira/browse/AMBARI-20208 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-20208.patch > > > Atlas kafka listeners should be configured to use the port value configured > in kafka-broker listeners, instead of the port property. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20208) Atlas kafka servers should be configured using kafka listeners.
[ https://issues.apache.org/jira/browse/AMBARI-20208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-20208: Attachment: AMBARI-20208.patch > Atlas kafka servers should be configured using kafka listeners. > --- > > Key: AMBARI-20208 > URL: https://issues.apache.org/jira/browse/AMBARI-20208 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-20208.patch > > > Atlas kafka listeners should be configured to use the port value configured > in kafka-broker listeners, instead of the port property. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20208) Atlas kafka servers should be configured using kafka listeners.
[ https://issues.apache.org/jira/browse/AMBARI-20208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-20208: Attachment: AMBARI-20208.2.patch > Atlas kafka servers should be configured using kafka listeners. > --- > > Key: AMBARI-20208 > URL: https://issues.apache.org/jira/browse/AMBARI-20208 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-20208_1.patch, AMBARI-20208.2.patch, > AMBARI-20208.patch > > > Atlas kafka listeners should be configured to use the port value configured > in kafka-broker listeners, instead of the port property. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20208) Atlas kafka servers should be configured using kafka listeners.
[ https://issues.apache.org/jira/browse/AMBARI-20208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-20208: Attachment: AMBARI-20208_1.patch > Atlas kafka servers should be configured using kafka listeners. > --- > > Key: AMBARI-20208 > URL: https://issues.apache.org/jira/browse/AMBARI-20208 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-20208_1.patch, AMBARI-20208.patch > > > Atlas kafka listeners should be configured to use the port value configured > in kafka-broker listeners, instead of the port property. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-18874) Provide SSL related configurations for Ranger-Tagsync.
[ https://issues.apache.org/jira/browse/AMBARI-18874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-18874: Attachment: AMBARI-18874.patch > Provide SSL related configurations for Ranger-Tagsync. > -- > > Key: AMBARI-18874 > URL: https://issues.apache.org/jira/browse/AMBARI-18874 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.5.0 > Environment: Need to provide ssl related configurations for > Ranger-Tagsync service. >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-18874.patch > > > Need to provide ssl related configurations for Ranger-Tagsync service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18874) Provide SSL related configurations for Ranger-Tagsync.
Vishal Suvagia created AMBARI-18874: --- Summary: Provide SSL related configurations for Ranger-Tagsync. Key: AMBARI-18874 URL: https://issues.apache.org/jira/browse/AMBARI-18874 Project: Ambari Issue Type: Improvement Affects Versions: 2.5.0 Environment: Need to provide ssl related configurations for Ranger-Tagsync service. Reporter: Vishal Suvagia Assignee: Vishal Suvagia Fix For: 2.5.0 Need to provide ssl related configurations for Ranger-Tagsync service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18874) Provide SSL related configurations for Ranger-Tagsync.
[ https://issues.apache.org/jira/browse/AMBARI-18874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-18874: Status: Patch Available (was: In Progress) > Provide SSL related configurations for Ranger-Tagsync. > -- > > Key: AMBARI-18874 > URL: https://issues.apache.org/jira/browse/AMBARI-18874 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.5.0 > Environment: Need to provide ssl related configurations for > Ranger-Tagsync service. >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-18874.1.patch, AMBARI-18874.2.patch, > AMBARI-18874.patch > > > Need to provide ssl related configurations for Ranger-Tagsync service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18874) Provide SSL related configurations for Ranger-Tagsync.
[ https://issues.apache.org/jira/browse/AMBARI-18874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-18874: Attachment: AMBARI-18874.1.patch > Provide SSL related configurations for Ranger-Tagsync. > -- > > Key: AMBARI-18874 > URL: https://issues.apache.org/jira/browse/AMBARI-18874 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.5.0 > Environment: Need to provide ssl related configurations for > Ranger-Tagsync service. >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-18874.1.patch, AMBARI-18874.patch > > > Need to provide ssl related configurations for Ranger-Tagsync service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18874) Provide SSL related configurations for Ranger-Tagsync.
[ https://issues.apache.org/jira/browse/AMBARI-18874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-18874: Attachment: AMBARI-18874.2.patch > Provide SSL related configurations for Ranger-Tagsync. > -- > > Key: AMBARI-18874 > URL: https://issues.apache.org/jira/browse/AMBARI-18874 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.5.0 > Environment: Need to provide ssl related configurations for > Ranger-Tagsync service. >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-18874.1.patch, AMBARI-18874.2.patch, > AMBARI-18874.patch > > > Need to provide ssl related configurations for Ranger-Tagsync service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18874) Provide SSL related configurations for Ranger-Tagsync.
[ https://issues.apache.org/jira/browse/AMBARI-18874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-18874: Attachment: AMBARI-18874.4.patch > Provide SSL related configurations for Ranger-Tagsync. > -- > > Key: AMBARI-18874 > URL: https://issues.apache.org/jira/browse/AMBARI-18874 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.5.0 > Environment: Need to provide ssl related configurations for > Ranger-Tagsync service. >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-18874.1.patch, AMBARI-18874.2.patch, > AMBARI-18874.3.patch, AMBARI-18874.4.patch, AMBARI-18874.patch > > > Need to provide ssl related configurations for Ranger-Tagsync service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18874) Provide SSL related configurations for Ranger-Tagsync.
[ https://issues.apache.org/jira/browse/AMBARI-18874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-18874: Attachment: AMBARI-18874.3.patch > Provide SSL related configurations for Ranger-Tagsync. > -- > > Key: AMBARI-18874 > URL: https://issues.apache.org/jira/browse/AMBARI-18874 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.5.0 > Environment: Need to provide ssl related configurations for > Ranger-Tagsync service. >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-18874.1.patch, AMBARI-18874.2.patch, > AMBARI-18874.3.patch, AMBARI-18874.patch > > > Need to provide ssl related configurations for Ranger-Tagsync service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18874) Provide SSL related configurations for Ranger-Tagsync.
[ https://issues.apache.org/jira/browse/AMBARI-18874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-18874: Attachment: AMBARI-18874.5_branch-2.5.patch > Provide SSL related configurations for Ranger-Tagsync. > -- > > Key: AMBARI-18874 > URL: https://issues.apache.org/jira/browse/AMBARI-18874 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.5.0 > Environment: Need to provide ssl related configurations for > Ranger-Tagsync service. >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-18874.1.patch, AMBARI-18874.2.patch, > AMBARI-18874.3.patch, AMBARI-18874.4.patch, AMBARI-18874.5.patch, > AMBARI-18874.5_branch-2.5.patch, AMBARI-18874.patch > > > Need to provide ssl related configurations for Ranger-Tagsync service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18874) Provide SSL related configurations for Ranger-Tagsync.
[ https://issues.apache.org/jira/browse/AMBARI-18874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-18874: Resolution: Fixed Status: Resolved (was: Patch Available) Committed on [trunk|https://github.com/apache/ambari/commit/646cfc681f9438ac56f4e3b864c0fd2402091082] and [branch-2.5|https://github.com/apache/ambari/commit/61477b9bd59a84f3e3e1486bd4b6dd7520e1400b] > Provide SSL related configurations for Ranger-Tagsync. > -- > > Key: AMBARI-18874 > URL: https://issues.apache.org/jira/browse/AMBARI-18874 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.5.0 > Environment: Need to provide ssl related configurations for > Ranger-Tagsync service. >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-18874.1.patch, AMBARI-18874.2.patch, > AMBARI-18874.3.patch, AMBARI-18874.4.patch, AMBARI-18874.5.patch, > AMBARI-18874.5_branch-2.5.patch, AMBARI-18874.patch > > > Need to provide ssl related configurations for Ranger-Tagsync service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19188) Provide Atlas Hook support for Hive2
[ https://issues.apache.org/jira/browse/AMBARI-19188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-19188: Attachment: AMBARI-19188.1.patch > Provide Atlas Hook support for Hive2 > > > Key: AMBARI-19188 > URL: https://issues.apache.org/jira/browse/AMBARI-19188 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19188.1.patch, AMBARI-19188.patch > > > Need to provide Atlas hook configuration support for HiveServer-Interactive. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19188) Provide Atlas Hook support for Hive2
Vishal Suvagia created AMBARI-19188: --- Summary: Provide Atlas Hook support for Hive2 Key: AMBARI-19188 URL: https://issues.apache.org/jira/browse/AMBARI-19188 Project: Ambari Issue Type: Bug Affects Versions: 2.5.0 Reporter: Vishal Suvagia Assignee: Vishal Suvagia Fix For: 2.5.0 Need to provide Atlas hook configuration for HiveServer-Interactive. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19188) Provide Atlas Hook support for Hive2
[ https://issues.apache.org/jira/browse/AMBARI-19188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-19188: Description: Need to provide Atlas hook configuration support for HiveServer-Interactive. (was: Need to provide Atlas hook configuration for HiveServer-Interactive.) > Provide Atlas Hook support for Hive2 > > > Key: AMBARI-19188 > URL: https://issues.apache.org/jira/browse/AMBARI-19188 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > > Need to provide Atlas hook configuration support for HiveServer-Interactive. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19188) Provide Atlas Hook support for Hive2
[ https://issues.apache.org/jira/browse/AMBARI-19188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-19188: Attachment: AMBARI-19188.patch > Provide Atlas Hook support for Hive2 > > > Key: AMBARI-19188 > URL: https://issues.apache.org/jira/browse/AMBARI-19188 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19188.patch > > > Need to provide Atlas hook configuration support for HiveServer-Interactive. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19188) Provide Atlas Hook support for Hive2
[ https://issues.apache.org/jira/browse/AMBARI-19188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-19188: Status: Patch Available (was: Open) Added fix for providing Atlas Hook for HiveServer2-Interactive > Provide Atlas Hook support for Hive2 > > > Key: AMBARI-19188 > URL: https://issues.apache.org/jira/browse/AMBARI-19188 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19188.patch > > > Need to provide Atlas hook configuration support for HiveServer-Interactive. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19227) Provide support to show Ranger solr-configs in Ambari
Vishal Suvagia created AMBARI-19227: --- Summary: Provide support to show Ranger solr-configs in Ambari Key: AMBARI-19227 URL: https://issues.apache.org/jira/browse/AMBARI-19227 Project: Ambari Issue Type: Improvement Affects Versions: 2.5.0 Reporter: Vishal Suvagia Assignee: Vishal Suvagia Fix For: 2.5.0 Need to provide feature for Ranger and update Ambari stacks to show solrconfig.xml on Ambari, so that user can update solr related configs directly from Ambari. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19227) Provide support to show Ranger solr-configs in Ambari
[ https://issues.apache.org/jira/browse/AMBARI-19227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-19227: Attachment: AMBARI-19227.patch > Provide support to show Ranger solr-configs in Ambari > - > > Key: AMBARI-19227 > URL: https://issues.apache.org/jira/browse/AMBARI-19227 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19227.patch > > > Need to provide feature for Ranger and update Ambari stacks to show > solrconfig.xml on Ambari, so that user can update solr related configs > directly from Ambari. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19228) Knox doesn't redirect to Atlas after entering correct credentials, when Atlas is setup with Knox-SSO
Vishal Suvagia created AMBARI-19228: --- Summary: Knox doesn't redirect to Atlas after entering correct credentials, when Atlas is setup with Knox-SSO Key: AMBARI-19228 URL: https://issues.apache.org/jira/browse/AMBARI-19228 Project: Ambari Issue Type: Improvement Components: ambari-server Affects Versions: 2.5.0 Reporter: Vishal Suvagia Assignee: Vishal Suvagia Fix For: 2.5.0 After enabling Atlas with Knox-SSO, user is not able to sign-in. but lands back on the login page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19228) Knox doesn't redirect to Atlas after entering correct credentials, when Atlas is setup with Knox-SSO
[ https://issues.apache.org/jira/browse/AMBARI-19228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-19228: Status: Patch Available (was: In Progress) > Knox doesn't redirect to Atlas after entering correct credentials, when Atlas > is setup with Knox-SSO > > > Key: AMBARI-19228 > URL: https://issues.apache.org/jira/browse/AMBARI-19228 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19228.patch > > > After enabling Atlas with Knox-SSO, user is not able to sign-in. but lands > back on the login page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19227) Provide support to show Ranger solr-configs in Ambari
[ https://issues.apache.org/jira/browse/AMBARI-19227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-19227: Component/s: ambari-server > Provide support to show Ranger solr-configs in Ambari > - > > Key: AMBARI-19227 > URL: https://issues.apache.org/jira/browse/AMBARI-19227 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19227.patch > > > Need to provide feature for Ranger and update Ambari stacks to show > solrconfig.xml on Ambari, so that user can update solr related configs > directly from Ambari. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19228) Knox doesn't redirect to Atlas after entering correct credentials, when Atlas is setup with Knox-SSO
[ https://issues.apache.org/jira/browse/AMBARI-19228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-19228: Attachment: AMBARI-19228.patch > Knox doesn't redirect to Atlas after entering correct credentials, when Atlas > is setup with Knox-SSO > > > Key: AMBARI-19228 > URL: https://issues.apache.org/jira/browse/AMBARI-19228 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19228.patch > > > After enabling Atlas with Knox-SSO, user is not able to sign-in. but lands > back on the login page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19386) ATLAS service check should run against metadata server host
[ https://issues.apache.org/jira/browse/AMBARI-19386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-19386: Attachment: AMBARI-19386.patch > ATLAS service check should run against metadata server host > --- > > Key: AMBARI-19386 > URL: https://issues.apache.org/jira/browse/AMBARI-19386 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19386.patch > > > Atlas service check fails as its hard coded to run check against the same > host where service check is running. It should instead run check against > ATLAS metadata server host. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19524) Use stack-level Atlas conf directory instead of hard-coded /etc/atlas/conf path
[
https://issues.apache.org/jira/browse/AMBARI-19524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Suvagia updated AMBARI-19524:
Attachment: AMBARI-19524_trunk.patch
AMBARI-19524_branch-2.5.patch
> Use stack-level Atlas conf directory instead of hard-coded /etc/atlas/conf
> path
> ---
>
> Key: AMBARI-19524
> URL: https://issues.apache.org/jira/browse/AMBARI-19524
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
> Environment: All
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
> Fix For: 2.5.0
>
> Attachments: AMBARI-19524_branch-2.5.patch, AMBARI-19524_trunk.patch
>
>
> This is a bug that should have been fixed in Ambari 2.4 but showed up too
> late in the release and has repercussions to test it.
> Basically, status_params.py for Atlas service in Ambari sets
> {code}
> conf_dir = os.environ['METADATA_CONF'] if 'METADATA_CONF' in os.environ else
> '/etc/atlas/conf'
> {code}
> This is technically incorrect since /etc/atlas/conf is a symlink to
> /usr/hdp/current/atlas-client/conf, which is then a symlink to
> /etc/atlas/$some_version/0
> During Rolling Upgrade,
> 1. Atlas Server is stopped, new configs are written to
> /etc/atlas/$new_version/0, then symlink is changed so that
> /usr/hdp/current/atlas-server points to new version, and Atlas Server is
> started
> At this point, /etc/atlas/conf -> /usr/hdp/current/atlas-client/conf (which
> is still using the old version) since the client has not yet been updated.
> 2. Atlas Client has new configs written to /etc/atlas/$new_version/0, then
> symlink is changed so that /usr/hdp/current/atlas-client points to new version
> Basically, we need to look at the usages of conf_dir and make sure it is
> correct during all scenarios.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19524) Use stack-level Atlas conf directory instead of hard-coded /etc/atlas/conf path
[
https://issues.apache.org/jira/browse/AMBARI-19524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Suvagia updated AMBARI-19524:
Status: Patch Available (was: In Progress)
> Use stack-level Atlas conf directory instead of hard-coded /etc/atlas/conf
> path
> ---
>
> Key: AMBARI-19524
> URL: https://issues.apache.org/jira/browse/AMBARI-19524
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
> Environment: All
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
> Fix For: 2.5.0
>
> Attachments: AMBARI-19524_branch-2.5.patch, AMBARI-19524_trunk.patch
>
>
> This is a bug that should have been fixed in Ambari 2.4 but showed up too
> late in the release and has repercussions to test it.
> Basically, status_params.py for Atlas service in Ambari sets
> {code}
> conf_dir = os.environ['METADATA_CONF'] if 'METADATA_CONF' in os.environ else
> '/etc/atlas/conf'
> {code}
> This is technically incorrect since /etc/atlas/conf is a symlink to
> /usr/hdp/current/atlas-client/conf, which is then a symlink to
> /etc/atlas/$some_version/0
> During Rolling Upgrade,
> 1. Atlas Server is stopped, new configs are written to
> /etc/atlas/$new_version/0, then symlink is changed so that
> /usr/hdp/current/atlas-server points to new version, and Atlas Server is
> started
> At this point, /etc/atlas/conf -> /usr/hdp/current/atlas-client/conf (which
> is still using the old version) since the client has not yet been updated.
> 2. Atlas Client has new configs written to /etc/atlas/$new_version/0, then
> symlink is changed so that /usr/hdp/current/atlas-client points to new version
> Basically, we need to look at the usages of conf_dir and make sure it is
> correct during all scenarios.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19529) Atlas service check should fail only if all metadata servers are down.
[ https://issues.apache.org/jira/browse/AMBARI-19529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-19529: Attachment: AMBARI-19529_trunk.patch AMBARI-19529_branch-2.5 .patch > Atlas service check should fail only if all metadata servers are down. > -- > > Key: AMBARI-19529 > URL: https://issues.apache.org/jira/browse/AMBARI-19529 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19529_branch-2.5 .patch, AMBARI-19529_trunk.patch > > > On Atlas-HA environments, Atlas service check fails even if one of the hosts > is down, the service check should only fail when All the Atlas metadata > servers are down. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19529) Atlas service check should fail only if all metadata servers are down.
[ https://issues.apache.org/jira/browse/AMBARI-19529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-19529: Status: Patch Available (was: In Progress) > Atlas service check should fail only if all metadata servers are down. > -- > > Key: AMBARI-19529 > URL: https://issues.apache.org/jira/browse/AMBARI-19529 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19529_branch-2.5 .patch, AMBARI-19529_trunk.patch > > > On Atlas-HA environments, Atlas service check fails even if one of the hosts > is down, the service check should only fail when All the Atlas metadata > servers are down. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19529) Atlas service check should fail only if all metadata servers are down.
Vishal Suvagia created AMBARI-19529: --- Summary: Atlas service check should fail only if all metadata servers are down. Key: AMBARI-19529 URL: https://issues.apache.org/jira/browse/AMBARI-19529 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.5.0 Reporter: Vishal Suvagia Assignee: Vishal Suvagia Fix For: 2.5.0 On Atlas-HA environments, Atlas service check fails even if one of the hosts is down, the service check should only fail when All the Atlas metadata servers are down. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19526) Ambari should mark oozie servers to be restarted when atlas hook configs or jars change.
Vishal Suvagia created AMBARI-19526: --- Summary: Ambari should mark oozie servers to be restarted when atlas hook configs or jars change. Key: AMBARI-19526 URL: https://issues.apache.org/jira/browse/AMBARI-19526 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.4.0 Reporter: Vishal Suvagia Assignee: Vishal Suvagia Fix For: 2.5.0 When making atlas config or jars change, oozie sharelib needs to be updated for hive and Oozie should be marked for restart. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19386) ATLAS service check should run against metadata server host
[ https://issues.apache.org/jira/browse/AMBARI-19386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15821034#comment-15821034 ] Vishal Suvagia commented on AMBARI-19386: - committed on [branch-2.5|https://github.com/apache/ambari/commit/20380d69270ab64933855dd1668305b14f39e91c] and [trunk|https://github.com/apache/ambari/commit/4975864796b9a301f4e0ee0b36673f41cb0f1b21] > ATLAS service check should run against metadata server host > --- > > Key: AMBARI-19386 > URL: https://issues.apache.org/jira/browse/AMBARI-19386 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19386.patch > > > Atlas service check fails as its hard coded to run check against the same > host where service check is running. It should instead run check against > ATLAS metadata server host. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-19386) ATLAS service check should run against metadata server host
[ https://issues.apache.org/jira/browse/AMBARI-19386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia resolved AMBARI-19386. - Resolution: Fixed committed on [branch-2.5|https://github.com/apache/ambari/commit/20380d69270ab64933855dd1668305b14f39e91c] and [trunk|https://github.com/apache/ambari/commit/4975864796b9a301f4e0ee0b36673f41cb0f1b21] > ATLAS service check should run against metadata server host > --- > > Key: AMBARI-19386 > URL: https://issues.apache.org/jira/browse/AMBARI-19386 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19386.patch > > > Atlas service check fails as its hard coded to run check against the same > host where service check is running. It should instead run check against > ATLAS metadata server host. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19029) Atlas web UI inaccessible alert after enabling Namenode-HA
[
https://issues.apache.org/jira/browse/AMBARI-19029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Suvagia updated AMBARI-19029:
Summary: Atlas web UI inaccessible alert after enabling Namenode-HA (was:
Atlas web UI inaccessible alert after enabling security)
> Atlas web UI inaccessible alert after enabling Namenode-HA
> --
>
> Key: AMBARI-19029
> URL: https://issues.apache.org/jira/browse/AMBARI-19029
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Shreya Bhat
>Assignee: Vishal Suvagia
>Priority: Critical
> Labels: system_test
> Fix For: 2.5.0
>
> Attachments: AMBARI-19029.1.patch, AMBARI-19029.patch
>
>
> After kerberization, atlas had a critical alert that "This host-level alert
> is triggered if the Metadata Server Web UI is unreachable."
> From atlas logs I can see :
> {code}
> Exception in thread "main" java.lang.ExceptionInInitializerError
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at
> org.apache.atlas.ApplicationProperties.getClass(ApplicationProperties.java:115)
> at
> org.apache.atlas.util.AtlasRepositoryConfiguration.getDeleteHandlerImpl(AtlasRepositoryConfiguration.java:76)
> at
> org.apache.atlas.RepositoryMetadataModule.configure(RepositoryMetadataModule.java:104)
> at com.google.inject.AbstractModule.configure(AbstractModule.java:62)
> at
> com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:340)
> at com.google.inject.spi.Elements.getElements(Elements.java:110)
> at
> com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:138)
> at
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:104)
> at com.google.inject.Guice.createInjector(Guice.java:99)
> at com.google.inject.Guice.createInjector(Guice.java:84)
> at
> org.apache.atlas.web.listeners.GuiceServletConfig.getInjector(GuiceServletConfig.java:77)
> at
> com.google.inject.servlet.GuiceServletContextListener.contextInitialized(GuiceServletContextListener.java:47)
> at
> org.apache.atlas.web.listeners.GuiceServletConfig.contextInitialized(GuiceServletConfig.java:141)
> at
> org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:800)
> at
> org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:444)
> at
> org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:791)
> at
> org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:294)
> at
> org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1349)
> at
> org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1342)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:741)
> at
> org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:505)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
> at org.eclipse.jetty.server.Server.start(Server.java:387)
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
> at
> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
> at org.eclipse.jetty.server.Server.doStart(Server.java:354)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at
> org.apache.atlas.web.service.EmbeddedServer.start(EmbeddedServer.java:92)
> at org.apache.atlas.Atlas.main(Atlas.java:118)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19029) Atlas web UI inaccessible alert after enabling Namenode-HA
[
https://issues.apache.org/jira/browse/AMBARI-19029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Suvagia updated AMBARI-19029:
Attachment: AMBARI-19029.2.patch
> Atlas web UI inaccessible alert after enabling Namenode-HA
> --
>
> Key: AMBARI-19029
> URL: https://issues.apache.org/jira/browse/AMBARI-19029
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Shreya Bhat
>Assignee: Vishal Suvagia
>Priority: Critical
> Labels: system_test
> Fix For: 2.5.0
>
> Attachments: AMBARI-19029.1.patch, AMBARI-19029.2.patch,
> AMBARI-19029.patch
>
>
> After enabling Namenode-HA, atlas had a critical alert that "This host-level
> alert is triggered if the Metadata Server Web UI is unreachable."
> From atlas logs I can see :
> {code}
> Exception in thread "main" java.lang.ExceptionInInitializerError
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at
> org.apache.atlas.ApplicationProperties.getClass(ApplicationProperties.java:115)
> at
> org.apache.atlas.util.AtlasRepositoryConfiguration.getDeleteHandlerImpl(AtlasRepositoryConfiguration.java:76)
> at
> org.apache.atlas.RepositoryMetadataModule.configure(RepositoryMetadataModule.java:104)
> at com.google.inject.AbstractModule.configure(AbstractModule.java:62)
> at
> com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:340)
> at com.google.inject.spi.Elements.getElements(Elements.java:110)
> at
> com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:138)
> at
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:104)
> at com.google.inject.Guice.createInjector(Guice.java:99)
> at com.google.inject.Guice.createInjector(Guice.java:84)
> at
> org.apache.atlas.web.listeners.GuiceServletConfig.getInjector(GuiceServletConfig.java:77)
> at
> com.google.inject.servlet.GuiceServletContextListener.contextInitialized(GuiceServletContextListener.java:47)
> at
> org.apache.atlas.web.listeners.GuiceServletConfig.contextInitialized(GuiceServletConfig.java:141)
> at
> org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:800)
> at
> org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:444)
> at
> org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:791)
> at
> org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:294)
> at
> org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1349)
> at
> org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1342)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:741)
> at
> org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:505)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
> at org.eclipse.jetty.server.Server.start(Server.java:387)
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
> at
> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
> at org.eclipse.jetty.server.Server.doStart(Server.java:354)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at
> org.apache.atlas.web.service.EmbeddedServer.start(EmbeddedServer.java:92)
> at org.apache.atlas.Atlas.main(Atlas.java:118)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19360) Ranger policies not syncing for storm, kafka and knox
[ https://issues.apache.org/jira/browse/AMBARI-19360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-19360: Attachment: AMBARI-19360.2.patch > Ranger policies not syncing for storm, kafka and knox > - > > Key: AMBARI-19360 > URL: https://issues.apache.org/jira/browse/AMBARI-19360 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 > Environment: On enabling Namenode-HA and one-way SSL for Ranger, > plugins for storm kafka and knox are not able to communicate to Ranger. >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19360.1.patch, AMBARI-19360.2.patch, > AMBARI-19360.patch > > > On Enabling Namenode-HA, and One-way SSL for Ranger, plugins are not able to > fetch latest policies as authorization does not work for Storm, knox and > Kafka plugins. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19360) Ranger policies not syncing for storm, kafka and knox
[ https://issues.apache.org/jira/browse/AMBARI-19360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-19360: Resolution: Fixed Status: Resolved (was: Patch Available) committed to [branch-2.5|https://github.com/apache/ambari/commit/a8aa8ab174185f5ecd0859db187f57891bf84a8f] and [trunk|https://github.com/apache/ambari/commit/36f8a762936e7d5c8b6319b5fade9e9f9b974733] > Ranger policies not syncing for storm, kafka and knox > - > > Key: AMBARI-19360 > URL: https://issues.apache.org/jira/browse/AMBARI-19360 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 > Environment: On enabling Namenode-HA and one-way SSL for Ranger, > plugins for storm kafka and knox are not able to communicate to Ranger. >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19360.1.patch, AMBARI-19360.2.patch, > AMBARI-19360.patch > > > On Enabling Namenode-HA, and One-way SSL for Ranger, plugins are not able to > fetch latest policies as authorization does not work for Storm, knox and > Kafka plugins. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19288) Do not install hive-hook from Ambari if falcon client is installed
[ https://issues.apache.org/jira/browse/AMBARI-19288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-19288: Attachment: AMBARI-19288.1.patch > Do not install hive-hook from Ambari if falcon client is installed > -- > > Key: AMBARI-19288 > URL: https://issues.apache.org/jira/browse/AMBARI-19288 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19288.1.patch, AMBARI-19288.patch > > > Currently, for 2.5 and 2.6 stacks, there a call to install hive-hook if > Falcon client is installed. Remove that dependency as that is handled by > hive-hook changes already. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19188) Provide Atlas Hook support for Hive2
[ https://issues.apache.org/jira/browse/AMBARI-19188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-19188: Resolution: Fixed Status: Resolved (was: Patch Available) Committed to [trunk|https://github.com/apache/ambari/commit/cc302f7d3c79d12fef8873acd76e962218aaac65] and [branch-2.5|https://github.com/apache/ambari/commit/06e88d39d718ce02bd8559a1c52a7b62e9726275] > Provide Atlas Hook support for Hive2 > > > Key: AMBARI-19188 > URL: https://issues.apache.org/jira/browse/AMBARI-19188 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19188.1.patch, AMBARI-19188.patch > > > Need to provide Atlas hook configuration support for HiveServer-Interactive. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19524) Use stack-level Atlas conf directory instead of hard-coded /etc/atlas/conf path
Vishal Suvagia created AMBARI-19524:
---
Summary: Use stack-level Atlas conf directory instead of
hard-coded /etc/atlas/conf path
Key: AMBARI-19524
URL: https://issues.apache.org/jira/browse/AMBARI-19524
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.4.0
Environment: All
Reporter: Vishal Suvagia
Assignee: Vishal Suvagia
Fix For: 2.5.0
This is a bug that should have been fixed in Ambari 2.4 but showed up too late
in the release and has repercussions to test it.
Basically, status_params.py for Atlas service in Ambari sets
{code}
conf_dir = os.environ['METADATA_CONF'] if 'METADATA_CONF' in os.environ else
'/etc/atlas/conf'
{code}
This is technically incorrect since /etc/atlas/conf is a symlink to
/usr/hdp/current/atlas-client/conf, which is then a symlink to
/etc/atlas/$some_version/0
During Rolling Upgrade,
1. Atlas Server is stopped, new configs are written to
/etc/atlas/$new_version/0, then symlink is changed so that
/usr/hdp/current/atlas-server points to new version, and Atlas Server is started
At this point, /etc/atlas/conf -> /usr/hdp/current/atlas-client/conf (which is
still using the old version) since the client has not yet been updated.
2. Atlas Client has new configs written to /etc/atlas/$new_version/0, then
symlink is changed so that /usr/hdp/current/atlas-client points to new version
Basically, we need to look at the usages of conf_dir and make sure it is
correct during all scenarios.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19288) Do not install hive-hook from Ambari if falcon client is installed
[ https://issues.apache.org/jira/browse/AMBARI-19288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-19288: Resolution: Fixed Status: Resolved (was: Patch Available) Committed to [trunk|https://github.com/apache/ambari/commit/f0e829973158350b15f3be81944ba0a0e1ac0d25] > Do not install hive-hook from Ambari if falcon client is installed > -- > > Key: AMBARI-19288 > URL: https://issues.apache.org/jira/browse/AMBARI-19288 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19288.1.patch, AMBARI-19288.patch > > > Currently, for 2.5 and 2.6 stacks, there a call to install hive-hook if > Falcon client is installed. Remove that dependency as that is handled by > hive-hook changes already. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19029) Atlas web UI inaccessible alert after enabling Namenode-HA
[
https://issues.apache.org/jira/browse/AMBARI-19029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Suvagia updated AMBARI-19029:
Attachment: (was: AMBARI-19029.3.patch)
> Atlas web UI inaccessible alert after enabling Namenode-HA
> --
>
> Key: AMBARI-19029
> URL: https://issues.apache.org/jira/browse/AMBARI-19029
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Shreya Bhat
>Assignee: Vishal Suvagia
>Priority: Critical
> Labels: system_test
> Fix For: 2.5.0
>
> Attachments: AMBARI-19029.1.patch, AMBARI-19029.2.patch,
> AMBARI-19029.patch
>
>
> After enabling Namenode-HA, atlas had a critical alert that "This host-level
> alert is triggered if the Metadata Server Web UI is unreachable."
> From atlas logs I can see :
> {code}
> Exception in thread "main" java.lang.ExceptionInInitializerError
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at
> org.apache.atlas.ApplicationProperties.getClass(ApplicationProperties.java:115)
> at
> org.apache.atlas.util.AtlasRepositoryConfiguration.getDeleteHandlerImpl(AtlasRepositoryConfiguration.java:76)
> at
> org.apache.atlas.RepositoryMetadataModule.configure(RepositoryMetadataModule.java:104)
> at com.google.inject.AbstractModule.configure(AbstractModule.java:62)
> at
> com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:340)
> at com.google.inject.spi.Elements.getElements(Elements.java:110)
> at
> com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:138)
> at
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:104)
> at com.google.inject.Guice.createInjector(Guice.java:99)
> at com.google.inject.Guice.createInjector(Guice.java:84)
> at
> org.apache.atlas.web.listeners.GuiceServletConfig.getInjector(GuiceServletConfig.java:77)
> at
> com.google.inject.servlet.GuiceServletContextListener.contextInitialized(GuiceServletContextListener.java:47)
> at
> org.apache.atlas.web.listeners.GuiceServletConfig.contextInitialized(GuiceServletConfig.java:141)
> at
> org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:800)
> at
> org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:444)
> at
> org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:791)
> at
> org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:294)
> at
> org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1349)
> at
> org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1342)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:741)
> at
> org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:505)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
> at org.eclipse.jetty.server.Server.start(Server.java:387)
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
> at
> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
> at org.eclipse.jetty.server.Server.doStart(Server.java:354)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at
> org.apache.atlas.web.service.EmbeddedServer.start(EmbeddedServer.java:92)
> at org.apache.atlas.Atlas.main(Atlas.java:118)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19029) Atlas web UI inaccessible alert after enabling Namenode-HA
[
https://issues.apache.org/jira/browse/AMBARI-19029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Suvagia updated AMBARI-19029:
Attachment: AMBARI-19029.3.patch
> Atlas web UI inaccessible alert after enabling Namenode-HA
> --
>
> Key: AMBARI-19029
> URL: https://issues.apache.org/jira/browse/AMBARI-19029
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Shreya Bhat
>Assignee: Vishal Suvagia
>Priority: Critical
> Labels: system_test
> Fix For: 2.5.0
>
> Attachments: AMBARI-19029.1.patch, AMBARI-19029.2.patch,
> AMBARI-19029.3.patch, AMBARI-19029.patch
>
>
> After enabling Namenode-HA, atlas had a critical alert that "This host-level
> alert is triggered if the Metadata Server Web UI is unreachable."
> From atlas logs I can see :
> {code}
> Exception in thread "main" java.lang.ExceptionInInitializerError
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at
> org.apache.atlas.ApplicationProperties.getClass(ApplicationProperties.java:115)
> at
> org.apache.atlas.util.AtlasRepositoryConfiguration.getDeleteHandlerImpl(AtlasRepositoryConfiguration.java:76)
> at
> org.apache.atlas.RepositoryMetadataModule.configure(RepositoryMetadataModule.java:104)
> at com.google.inject.AbstractModule.configure(AbstractModule.java:62)
> at
> com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:340)
> at com.google.inject.spi.Elements.getElements(Elements.java:110)
> at
> com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:138)
> at
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:104)
> at com.google.inject.Guice.createInjector(Guice.java:99)
> at com.google.inject.Guice.createInjector(Guice.java:84)
> at
> org.apache.atlas.web.listeners.GuiceServletConfig.getInjector(GuiceServletConfig.java:77)
> at
> com.google.inject.servlet.GuiceServletContextListener.contextInitialized(GuiceServletContextListener.java:47)
> at
> org.apache.atlas.web.listeners.GuiceServletConfig.contextInitialized(GuiceServletConfig.java:141)
> at
> org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:800)
> at
> org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:444)
> at
> org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:791)
> at
> org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:294)
> at
> org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1349)
> at
> org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1342)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:741)
> at
> org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:505)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
> at org.eclipse.jetty.server.Server.start(Server.java:387)
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
> at
> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
> at org.eclipse.jetty.server.Server.doStart(Server.java:354)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at
> org.apache.atlas.web.service.EmbeddedServer.start(EmbeddedServer.java:92)
> at org.apache.atlas.Atlas.main(Atlas.java:118)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19526) Ambari should mark oozie servers to be restarted when atlas hook configs or jars change.
[ https://issues.apache.org/jira/browse/AMBARI-19526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-19526: Attachment: AMBARI-19526.patch > Ambari should mark oozie servers to be restarted when atlas hook configs or > jars change. > > > Key: AMBARI-19526 > URL: https://issues.apache.org/jira/browse/AMBARI-19526 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19526.patch > > > When making atlas config or jars change, oozie sharelib needs to be updated > for hive and Oozie should be marked for restart. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19526) Ambari should mark oozie servers to be restarted when atlas hook configs or jars change.
[ https://issues.apache.org/jira/browse/AMBARI-19526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-19526: Status: Patch Available (was: In Progress) > Ambari should mark oozie servers to be restarted when atlas hook configs or > jars change. > > > Key: AMBARI-19526 > URL: https://issues.apache.org/jira/browse/AMBARI-19526 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19526.patch > > > When making atlas config or jars change, oozie sharelib needs to be updated > for hive and Oozie should be marked for restart. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19360) Ranger policies not syncing for storm, kafka and knox
[ https://issues.apache.org/jira/browse/AMBARI-19360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-19360: Attachment: AMBARI-19360.patch > Ranger policies not syncing for storm, kafka and knox > - > > Key: AMBARI-19360 > URL: https://issues.apache.org/jira/browse/AMBARI-19360 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 > Environment: On enabling Namenode-HA and one-way SSL for Ranger, > plugins for storm kafka and knox are not able to communicate to Ranger. >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19360.patch > > > On Enabling Namenode-HA, and One-way SSL for Ranger, plugins are not able to > fetch latest policies as authorization does not work for Storm, knox and > Kafka plugins. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19360) Ranger policies not syncing for storm, kafka and knox
Vishal Suvagia created AMBARI-19360: --- Summary: Ranger policies not syncing for storm, kafka and knox Key: AMBARI-19360 URL: https://issues.apache.org/jira/browse/AMBARI-19360 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.5.0 Environment: On enabling Namenode-HA and one-way SSL for Ranger, plugins for storm kafka and knox are not able to communicate to Ranger. Reporter: Vishal Suvagia Assignee: Vishal Suvagia Fix For: 2.5.0 On Enabling Namenode-HA, and One-way SSL for Ranger, plugins are not able to fetch latest policies as authorization does not work for Storm, knox and Kafka plugins. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19314) Include Hadoop conf directory in Atlas class path
Vishal Suvagia created AMBARI-19314: --- Summary: Include Hadoop conf directory in Atlas class path Key: AMBARI-19314 URL: https://issues.apache.org/jira/browse/AMBARI-19314 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.5.0 Reporter: Vishal Suvagia Assignee: Vishal Suvagia Fix For: 2.5.0 Need to include Hadoop conf directory in Atlas environment classpath. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19360) Ranger policies not syncing for storm, kafka and knox
[ https://issues.apache.org/jira/browse/AMBARI-19360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-19360: Status: Patch Available (was: In Progress) > Ranger policies not syncing for storm, kafka and knox > - > > Key: AMBARI-19360 > URL: https://issues.apache.org/jira/browse/AMBARI-19360 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 > Environment: On enabling Namenode-HA and one-way SSL for Ranger, > plugins for storm kafka and knox are not able to communicate to Ranger. >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19360.patch > > > On Enabling Namenode-HA, and One-way SSL for Ranger, plugins are not able to > fetch latest policies as authorization does not work for Storm, knox and > Kafka plugins. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19386) ATLAS service check should run against metadata server host
Vishal Suvagia created AMBARI-19386: --- Summary: ATLAS service check should run against metadata server host Key: AMBARI-19386 URL: https://issues.apache.org/jira/browse/AMBARI-19386 Project: Ambari Issue Type: Bug Affects Versions: 2.5.0 Reporter: Vishal Suvagia Assignee: Vishal Suvagia Fix For: 2.5.0 Atlas service check fails as its hard coded to run check against the same host where service check is running. It should instead run check against ATLAS metadata server host. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19360) Ranger policies not syncing for storm, kafka and knox
[ https://issues.apache.org/jira/browse/AMBARI-19360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-19360: Attachment: AMBARI-19360.1.patch > Ranger policies not syncing for storm, kafka and knox > - > > Key: AMBARI-19360 > URL: https://issues.apache.org/jira/browse/AMBARI-19360 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 > Environment: On enabling Namenode-HA and one-way SSL for Ranger, > plugins for storm kafka and knox are not able to communicate to Ranger. >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19360.1.patch, AMBARI-19360.patch > > > On Enabling Namenode-HA, and One-way SSL for Ranger, plugins are not able to > fetch latest policies as authorization does not work for Storm, knox and > Kafka plugins. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19029) Atlas web UI inaccessible alert after enabling security
[
https://issues.apache.org/jira/browse/AMBARI-19029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Suvagia updated AMBARI-19029:
Attachment: AMBARI-19029.1.patch
> Atlas web UI inaccessible alert after enabling security
> ---
>
> Key: AMBARI-19029
> URL: https://issues.apache.org/jira/browse/AMBARI-19029
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Shreya Bhat
>Assignee: Vishal Suvagia
>Priority: Critical
> Labels: system_test
> Fix For: 2.5.0
>
> Attachments: AMBARI-19029.1.patch, AMBARI-19029.patch
>
>
> After kerberization, atlas had a critical alert that "This host-level alert
> is triggered if the Metadata Server Web UI is unreachable."
> From atlas logs I can see :
> {code}
> Exception in thread "main" java.lang.ExceptionInInitializerError
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at
> org.apache.atlas.ApplicationProperties.getClass(ApplicationProperties.java:115)
> at
> org.apache.atlas.util.AtlasRepositoryConfiguration.getDeleteHandlerImpl(AtlasRepositoryConfiguration.java:76)
> at
> org.apache.atlas.RepositoryMetadataModule.configure(RepositoryMetadataModule.java:104)
> at com.google.inject.AbstractModule.configure(AbstractModule.java:62)
> at
> com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:340)
> at com.google.inject.spi.Elements.getElements(Elements.java:110)
> at
> com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:138)
> at
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:104)
> at com.google.inject.Guice.createInjector(Guice.java:99)
> at com.google.inject.Guice.createInjector(Guice.java:84)
> at
> org.apache.atlas.web.listeners.GuiceServletConfig.getInjector(GuiceServletConfig.java:77)
> at
> com.google.inject.servlet.GuiceServletContextListener.contextInitialized(GuiceServletContextListener.java:47)
> at
> org.apache.atlas.web.listeners.GuiceServletConfig.contextInitialized(GuiceServletConfig.java:141)
> at
> org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:800)
> at
> org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:444)
> at
> org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:791)
> at
> org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:294)
> at
> org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1349)
> at
> org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1342)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:741)
> at
> org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:505)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
> at org.eclipse.jetty.server.Server.start(Server.java:387)
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
> at
> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
> at org.eclipse.jetty.server.Server.doStart(Server.java:354)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at
> org.apache.atlas.web.service.EmbeddedServer.start(EmbeddedServer.java:92)
> at org.apache.atlas.Atlas.main(Atlas.java:118)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19029) Atlas web UI inaccessible alert after enabling security
[
https://issues.apache.org/jira/browse/AMBARI-19029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Suvagia updated AMBARI-19029:
Status: Patch Available (was: In Progress)
> Atlas web UI inaccessible alert after enabling security
> ---
>
> Key: AMBARI-19029
> URL: https://issues.apache.org/jira/browse/AMBARI-19029
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Shreya Bhat
>Assignee: Vishal Suvagia
>Priority: Critical
> Labels: system_test
> Fix For: 2.5.0
>
> Attachments: AMBARI-19029.1.patch, AMBARI-19029.patch
>
>
> After kerberization, atlas had a critical alert that "This host-level alert
> is triggered if the Metadata Server Web UI is unreachable."
> From atlas logs I can see :
> {code}
> Exception in thread "main" java.lang.ExceptionInInitializerError
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at
> org.apache.atlas.ApplicationProperties.getClass(ApplicationProperties.java:115)
> at
> org.apache.atlas.util.AtlasRepositoryConfiguration.getDeleteHandlerImpl(AtlasRepositoryConfiguration.java:76)
> at
> org.apache.atlas.RepositoryMetadataModule.configure(RepositoryMetadataModule.java:104)
> at com.google.inject.AbstractModule.configure(AbstractModule.java:62)
> at
> com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:340)
> at com.google.inject.spi.Elements.getElements(Elements.java:110)
> at
> com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:138)
> at
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:104)
> at com.google.inject.Guice.createInjector(Guice.java:99)
> at com.google.inject.Guice.createInjector(Guice.java:84)
> at
> org.apache.atlas.web.listeners.GuiceServletConfig.getInjector(GuiceServletConfig.java:77)
> at
> com.google.inject.servlet.GuiceServletContextListener.contextInitialized(GuiceServletContextListener.java:47)
> at
> org.apache.atlas.web.listeners.GuiceServletConfig.contextInitialized(GuiceServletConfig.java:141)
> at
> org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:800)
> at
> org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:444)
> at
> org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:791)
> at
> org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:294)
> at
> org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1349)
> at
> org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1342)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:741)
> at
> org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:505)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
> at org.eclipse.jetty.server.Server.start(Server.java:387)
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
> at
> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
> at org.eclipse.jetty.server.Server.doStart(Server.java:354)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at
> org.apache.atlas.web.service.EmbeddedServer.start(EmbeddedServer.java:92)
> at org.apache.atlas.Atlas.main(Atlas.java:118)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (AMBARI-19314) Include Hadoop conf directory in Atlas class path
[ https://issues.apache.org/jira/browse/AMBARI-19314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia resolved AMBARI-19314. - Resolution: Duplicate Duplicate of AMBARI-19029 > Include Hadoop conf directory in Atlas class path > - > > Key: AMBARI-19314 > URL: https://issues.apache.org/jira/browse/AMBARI-19314 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > > Need to include Hadoop conf directory in Atlas environment classpath. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19227) Provide support to show Ranger solr-configs in Ambari
[ https://issues.apache.org/jira/browse/AMBARI-19227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-19227: Attachment: AMBARI-19227.1.patch > Provide support to show Ranger solr-configs in Ambari > - > > Key: AMBARI-19227 > URL: https://issues.apache.org/jira/browse/AMBARI-19227 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19227.1.patch, AMBARI-19227.patch > > > Need to provide feature for Ranger and update Ambari stacks to show > solrconfig.xml on Ambari, so that user can update solr related configs > directly from Ambari. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19288) Do not install hive-hook from Ambari if falcon client is installed
Vishal Suvagia created AMBARI-19288: --- Summary: Do not install hive-hook from Ambari if falcon client is installed Key: AMBARI-19288 URL: https://issues.apache.org/jira/browse/AMBARI-19288 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.5.0 Reporter: Vishal Suvagia Assignee: Vishal Suvagia Fix For: 2.5.0 Currently, for 2.5 and 2.6 stacks, there a call to install hive-hook if Falcon client is installed. Remove that dependency as that is handled by hive-hook changes already. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19288) Do not install hive-hook from Ambari if falcon client is installed
[ https://issues.apache.org/jira/browse/AMBARI-19288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-19288: Attachment: AMBARI-19288.patch > Do not install hive-hook from Ambari if falcon client is installed > -- > > Key: AMBARI-19288 > URL: https://issues.apache.org/jira/browse/AMBARI-19288 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19288.patch > > > Currently, for 2.5 and 2.6 stacks, there a call to install hive-hook if > Falcon client is installed. Remove that dependency as that is handled by > hive-hook changes already. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19288) Do not install hive-hook from Ambari if falcon client is installed
[ https://issues.apache.org/jira/browse/AMBARI-19288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-19288: Status: Patch Available (was: In Progress) > Do not install hive-hook from Ambari if falcon client is installed > -- > > Key: AMBARI-19288 > URL: https://issues.apache.org/jira/browse/AMBARI-19288 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19288.patch > > > Currently, for 2.5 and 2.6 stacks, there a call to install hive-hook if > Falcon client is installed. Remove that dependency as that is handled by > hive-hook changes already. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19227) Provide support to show Ranger solr-configs in Ambari
[ https://issues.apache.org/jira/browse/AMBARI-19227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-19227: Resolution: Fixed Status: Resolved (was: Patch Available) commited to [branch-2.5|https://github.com/apache/ambari/commit/238bbe58d7d7fe9fe6b3abf3ef68a78eab4c95b3] and [trunk|https://github.com/apache/ambari/commit/f77ba790cc7cbd4be9b33c23d1a85b0dd8638dd0] > Provide support to show Ranger solr-configs in Ambari > - > > Key: AMBARI-19227 > URL: https://issues.apache.org/jira/browse/AMBARI-19227 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19227.1.patch, AMBARI-19227.patch > > > Need to provide feature for Ranger and update Ambari stacks to show > solrconfig.xml on Ambari, so that user can update solr related configs > directly from Ambari. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AMBARI-19029) Atlas web UI inaccessible alert after enabling security
[
https://issues.apache.org/jira/browse/AMBARI-19029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Suvagia reassigned AMBARI-19029:
---
Assignee: Vishal Suvagia
> Atlas web UI inaccessible alert after enabling security
> ---
>
> Key: AMBARI-19029
> URL: https://issues.apache.org/jira/browse/AMBARI-19029
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Shreya Bhat
>Assignee: Vishal Suvagia
>Priority: Critical
> Labels: system_test
> Fix For: 2.5.0
>
>
> After kerberization, atlas had a critical alert that "This host-level alert
> is triggered if the Metadata Server Web UI is unreachable."
> From atlas logs I can see :
> {code}
> Exception in thread "main" java.lang.ExceptionInInitializerError
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at
> org.apache.atlas.ApplicationProperties.getClass(ApplicationProperties.java:115)
> at
> org.apache.atlas.util.AtlasRepositoryConfiguration.getDeleteHandlerImpl(AtlasRepositoryConfiguration.java:76)
> at
> org.apache.atlas.RepositoryMetadataModule.configure(RepositoryMetadataModule.java:104)
> at com.google.inject.AbstractModule.configure(AbstractModule.java:62)
> at
> com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:340)
> at com.google.inject.spi.Elements.getElements(Elements.java:110)
> at
> com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:138)
> at
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:104)
> at com.google.inject.Guice.createInjector(Guice.java:99)
> at com.google.inject.Guice.createInjector(Guice.java:84)
> at
> org.apache.atlas.web.listeners.GuiceServletConfig.getInjector(GuiceServletConfig.java:77)
> at
> com.google.inject.servlet.GuiceServletContextListener.contextInitialized(GuiceServletContextListener.java:47)
> at
> org.apache.atlas.web.listeners.GuiceServletConfig.contextInitialized(GuiceServletConfig.java:141)
> at
> org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:800)
> at
> org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:444)
> at
> org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:791)
> at
> org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:294)
> at
> org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1349)
> at
> org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1342)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:741)
> at
> org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:505)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
> at org.eclipse.jetty.server.Server.start(Server.java:387)
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
> at
> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
> at org.eclipse.jetty.server.Server.doStart(Server.java:354)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at
> org.apache.atlas.web.service.EmbeddedServer.start(EmbeddedServer.java:92)
> at org.apache.atlas.Atlas.main(Atlas.java:118)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19029) Atlas web UI inaccessible alert after enabling security
[
https://issues.apache.org/jira/browse/AMBARI-19029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Suvagia updated AMBARI-19029:
Attachment: AMBARI-19029.patch
> Atlas web UI inaccessible alert after enabling security
> ---
>
> Key: AMBARI-19029
> URL: https://issues.apache.org/jira/browse/AMBARI-19029
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Shreya Bhat
>Assignee: Vishal Suvagia
>Priority: Critical
> Labels: system_test
> Fix For: 2.5.0
>
> Attachments: AMBARI-19029.patch
>
>
> After kerberization, atlas had a critical alert that "This host-level alert
> is triggered if the Metadata Server Web UI is unreachable."
> From atlas logs I can see :
> {code}
> Exception in thread "main" java.lang.ExceptionInInitializerError
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at
> org.apache.atlas.ApplicationProperties.getClass(ApplicationProperties.java:115)
> at
> org.apache.atlas.util.AtlasRepositoryConfiguration.getDeleteHandlerImpl(AtlasRepositoryConfiguration.java:76)
> at
> org.apache.atlas.RepositoryMetadataModule.configure(RepositoryMetadataModule.java:104)
> at com.google.inject.AbstractModule.configure(AbstractModule.java:62)
> at
> com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:340)
> at com.google.inject.spi.Elements.getElements(Elements.java:110)
> at
> com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:138)
> at
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:104)
> at com.google.inject.Guice.createInjector(Guice.java:99)
> at com.google.inject.Guice.createInjector(Guice.java:84)
> at
> org.apache.atlas.web.listeners.GuiceServletConfig.getInjector(GuiceServletConfig.java:77)
> at
> com.google.inject.servlet.GuiceServletContextListener.contextInitialized(GuiceServletContextListener.java:47)
> at
> org.apache.atlas.web.listeners.GuiceServletConfig.contextInitialized(GuiceServletConfig.java:141)
> at
> org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:800)
> at
> org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:444)
> at
> org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:791)
> at
> org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:294)
> at
> org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1349)
> at
> org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1342)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:741)
> at
> org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:505)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
> at org.eclipse.jetty.server.Server.start(Server.java:387)
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
> at
> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
> at org.eclipse.jetty.server.Server.doStart(Server.java:354)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at
> org.apache.atlas.web.service.EmbeddedServer.start(EmbeddedServer.java:92)
> at org.apache.atlas.Atlas.main(Atlas.java:118)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19227) Provide support to show Ranger solr-configs in Ambari
[ https://issues.apache.org/jira/browse/AMBARI-19227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-19227: Status: Patch Available (was: In Progress) > Provide support to show Ranger solr-configs in Ambari > - > > Key: AMBARI-19227 > URL: https://issues.apache.org/jira/browse/AMBARI-19227 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19227.patch > > > Need to provide feature for Ranger and update Ambari stacks to show > solrconfig.xml on Ambari, so that user can update solr related configs > directly from Ambari. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-20555) Add Ambari cluster name for Ranger-Tagsync to sync generated atlas tags.
Vishal Suvagia created AMBARI-20555:
---
Summary: Add Ambari cluster name for Ranger-Tagsync to sync
generated atlas tags.
Key: AMBARI-20555
URL: https://issues.apache.org/jira/browse/AMBARI-20555
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.5.0
Reporter: Vishal Suvagia
Assignee: Vishal Suvagia
Fix For: 2.5.1
Need to add {{ranger.tagsync.atlas.default.cluster.name}} property to
{{ranger-tagsync-site.xml}} should be set to ambari cluster-name, to sync tags
from Atlas metadata to Ranger.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
