[jira] [Resolved] (AMBARI-17607) Add localjceks support in ambari for Ranger and Ranger KMS services
[ https://issues.apache.org/jira/browse/AMBARI-17607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar resolved AMBARI-17607. -- Resolution: Information Provided > Add localjceks support in ambari for Ranger and Ranger KMS services > --- > > Key: AMBARI-17607 > URL: https://issues.apache.org/jira/browse/AMBARI-17607 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Major > Labels: pull-request-available > Attachments: AMBARI-17607.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Currently, localjceks scheme is not supported for ranger installation through > Ambari. Ambari should use localjecks scheme to store, retrieve and list its > alias and values while installing ranger through Ambari. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25183) Need a stack feature constant for add zoneName field in collection used for Ranger plugin audit
[
https://issues.apache.org/jira/browse/AMBARI-25183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-25183:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Need a stack feature constant for add zoneName field in collection used for
> Ranger plugin audit
> ---
>
> Key: AMBARI-25183
> URL: https://issues.apache.org/jira/browse/AMBARI-25183
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.4
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.4
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> As a part to add {{zoneName}} field in Ranger Solr collection during upgrade,
> need a stack feature constant to support this feature.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-25183) Need a stack feature constant for add zoneName field in collection used for Ranger plugin audit
[
https://issues.apache.org/jira/browse/AMBARI-25183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-25183:
-
Status: Patch Available (was: In Progress)
> Need a stack feature constant for add zoneName field in collection used for
> Ranger plugin audit
> ---
>
> Key: AMBARI-25183
> URL: https://issues.apache.org/jira/browse/AMBARI-25183
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.4
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.4
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> As a part to add {{zoneName}} field in Ranger Solr collection during upgrade,
> need a stack feature constant to support this feature.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-25183) Need a stack feature constant for add zoneName field in collection used for Ranger plugin audit
Mugdha Varadkar created AMBARI-25183:
Summary: Need a stack feature constant for add zoneName field in
collection used for Ranger plugin audit
Key: AMBARI-25183
URL: https://issues.apache.org/jira/browse/AMBARI-25183
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.4
Reporter: Mugdha Varadkar
Assignee: Mugdha Varadkar
Fix For: 2.7.4
As a part to add {{zoneName}} field in Ranger Solr collection during upgrade,
need a stack feature constant to support this feature.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24794) Adding Ranger Password configs in Admin Settings section under Advanced config
[ https://issues.apache.org/jira/browse/AMBARI-24794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-24794: - Resolution: Fixed Status: Resolved (was: Patch Available) > Adding Ranger Password configs in Admin Settings section under Advanced config > -- > > Key: AMBARI-24794 > URL: https://issues.apache.org/jira/browse/AMBARI-24794 > Project: Ambari > Issue Type: Bug >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Major > Labels: pull-request-available > Fix For: trunk, 2.7.3 > > Attachments: AMBARI-24794.patch > > Time Spent: 1h 20m > Remaining Estimate: 0h > > This jira is fixing the below password configs to be shown in 'Admin > Settings' section under Advanced Config section for Ranger service. > * rangerusersync_user_password > * rangertagsync_user_password > * keyadmin_user_password -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24794) Adding Ranger Password configs in Admin Settings section under Advanced config
[ https://issues.apache.org/jira/browse/AMBARI-24794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-24794: - Status: Patch Available (was: In Progress) > Adding Ranger Password configs in Admin Settings section under Advanced config > -- > > Key: AMBARI-24794 > URL: https://issues.apache.org/jira/browse/AMBARI-24794 > Project: Ambari > Issue Type: Bug >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Major > Labels: pull-request-available > Fix For: trunk, 2.7.3 > > Attachments: AMBARI-24794.patch > > Time Spent: 40m > Remaining Estimate: 0h > > This jira is fixing the below password configs to be shown in 'Admin > Settings' section under Advanced Config section for Ranger service. > * rangerusersync_user_password > * rangertagsync_user_password > * keyadmin_user_password -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24794) Adding Ranger Password configs in Admin Settings section under Advanced config
[ https://issues.apache.org/jira/browse/AMBARI-24794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-24794: - Fix Version/s: 2.7.3 > Adding Ranger Password configs in Admin Settings section under Advanced config > -- > > Key: AMBARI-24794 > URL: https://issues.apache.org/jira/browse/AMBARI-24794 > Project: Ambari > Issue Type: Bug >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Major > Labels: pull-request-available > Fix For: trunk, 2.7.3 > > Attachments: AMBARI-24794.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > > This jira is fixing the below password configs to be shown in 'Admin > Settings' section under Advanced Config section for Ranger service. > * rangerusersync_user_password > * rangertagsync_user_password > * keyadmin_user_password -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24794) Adding Ranger Password configs in Admin Settings section under Advanced config
[ https://issues.apache.org/jira/browse/AMBARI-24794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-24794: - Fix Version/s: trunk > Adding Ranger Password configs in Admin Settings section under Advanced config > -- > > Key: AMBARI-24794 > URL: https://issues.apache.org/jira/browse/AMBARI-24794 > Project: Ambari > Issue Type: Bug >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Major > Labels: pull-request-available > Fix For: trunk > > Attachments: AMBARI-24794.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > > This jira is fixing the below password configs to be shown in 'Admin > Settings' section under Advanced Config section for Ranger service. > * rangerusersync_user_password > * rangertagsync_user_password > * keyadmin_user_password -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (AMBARI-24794) Adding Ranger Password configs in Admin Settings section under Advanced config
[ https://issues.apache.org/jira/browse/AMBARI-24794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar reopened AMBARI-24794: -- > Adding Ranger Password configs in Admin Settings section under Advanced config > -- > > Key: AMBARI-24794 > URL: https://issues.apache.org/jira/browse/AMBARI-24794 > Project: Ambari > Issue Type: Bug >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Major > Labels: pull-request-available > Fix For: trunk > > Attachments: AMBARI-24794.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > > This jira is fixing the below password configs to be shown in 'Admin > Settings' section under Advanced Config section for Ranger service. > * rangerusersync_user_password > * rangertagsync_user_password > * keyadmin_user_password -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24794) Adding Ranger Password configs in Admin Settings section under Advanced config
[ https://issues.apache.org/jira/browse/AMBARI-24794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-24794: - Resolution: Fixed Status: Resolved (was: Patch Available) > Adding Ranger Password configs in Admin Settings section under Advanced config > -- > > Key: AMBARI-24794 > URL: https://issues.apache.org/jira/browse/AMBARI-24794 > Project: Ambari > Issue Type: Bug >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Major > Labels: pull-request-available > Attachments: AMBARI-24794.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > > This jira is fixing the below password configs to be shown in 'Admin > Settings' section under Advanced Config section for Ranger service. > * rangerusersync_user_password > * rangertagsync_user_password > * keyadmin_user_password -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24794) Adding Ranger Password configs in Admin Settings section under Advanced config
[ https://issues.apache.org/jira/browse/AMBARI-24794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-24794: - Attachment: AMBARI-24794.patch > Adding Ranger Password configs in Admin Settings section under Advanced config > -- > > Key: AMBARI-24794 > URL: https://issues.apache.org/jira/browse/AMBARI-24794 > Project: Ambari > Issue Type: Bug >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Major > Labels: pull-request-available > Attachments: AMBARI-24794.patch > > Time Spent: 10m > Remaining Estimate: 0h > > This jira is fixing the below password configs to be shown in 'Admin > Settings' section under Advanced Config section for Ranger service. > * rangerusersync_user_password > * rangertagsync_user_password > * keyadmin_user_password -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24794) Adding Ranger Password configs in Admin Settings section under Advanced config
[ https://issues.apache.org/jira/browse/AMBARI-24794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-24794: - Status: Patch Available (was: In Progress) > Adding Ranger Password configs in Admin Settings section under Advanced config > -- > > Key: AMBARI-24794 > URL: https://issues.apache.org/jira/browse/AMBARI-24794 > Project: Ambari > Issue Type: Bug >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Major > Labels: pull-request-available > Attachments: AMBARI-24794.patch > > Time Spent: 10m > Remaining Estimate: 0h > > This jira is fixing the below password configs to be shown in 'Admin > Settings' section under Advanced Config section for Ranger service. > * rangerusersync_user_password > * rangertagsync_user_password > * keyadmin_user_password -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24794) Adding Ranger Password configs in Admin Settings section under Advanced config
Mugdha Varadkar created AMBARI-24794: Summary: Adding Ranger Password configs in Admin Settings section under Advanced config Key: AMBARI-24794 URL: https://issues.apache.org/jira/browse/AMBARI-24794 Project: Ambari Issue Type: Bug Reporter: Mugdha Varadkar Assignee: Mugdha Varadkar This jira is fixing the below password configs to be shown in 'Admin Settings' section under Advanced Config section for Ranger service. * rangerusersync_user_password * rangertagsync_user_password * keyadmin_user_password -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22951) Export JAVA_HOME env variable in shell script for Ranger
[ https://issues.apache.org/jira/browse/AMBARI-22951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-22951: - Fix Version/s: (was: trunk) > Export JAVA_HOME env variable in shell script for Ranger > > > Key: AMBARI-22951 > URL: https://issues.apache.org/jira/browse/AMBARI-22951 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0, 2.5.1, 2.5.2, 2.5.3, 2.6.0, 2.6.1 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Major > Labels: pull-request-available > Fix For: 2.6.2, 2.7.1 > > Attachments: AMBARI-22951.patch > > Time Spent: 2h 20m > Remaining Estimate: 0h > > Need to export JAVA_HOME variable in ranger-admin-env.sh, so that > [ranger-admin-services.sh|https://github.com/apache/ranger/blob/master/embeddedwebserver/scripts/ranger-admin-services.sh] > knows which java to be used for processing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22951) Export JAVA_HOME env variable in shell script for Ranger
[ https://issues.apache.org/jira/browse/AMBARI-22951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-22951: - Resolution: Fixed Status: Resolved (was: Patch Available) > Export JAVA_HOME env variable in shell script for Ranger > > > Key: AMBARI-22951 > URL: https://issues.apache.org/jira/browse/AMBARI-22951 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0, 2.5.1, 2.5.2, 2.5.3, 2.6.0, 2.6.1 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Major > Labels: pull-request-available > Fix For: trunk, 2.6.2, 2.7.1 > > Attachments: AMBARI-22951.patch > > Time Spent: 2h 20m > Remaining Estimate: 0h > > Need to export JAVA_HOME variable in ranger-admin-env.sh, so that > [ranger-admin-services.sh|https://github.com/apache/ranger/blob/master/embeddedwebserver/scripts/ranger-admin-services.sh] > knows which java to be used for processing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22951) Export JAVA_HOME env variable in shell script for Ranger
[ https://issues.apache.org/jira/browse/AMBARI-22951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-22951: - Fix Version/s: 2.7.1 trunk > Export JAVA_HOME env variable in shell script for Ranger > > > Key: AMBARI-22951 > URL: https://issues.apache.org/jira/browse/AMBARI-22951 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0, 2.5.1, 2.5.2, 2.5.3, 2.6.0, 2.6.1 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Major > Labels: pull-request-available > Fix For: trunk, 2.6.2, 2.7.1 > > Attachments: AMBARI-22951.patch > > Time Spent: 1h 40m > Remaining Estimate: 0h > > Need to export JAVA_HOME variable in ranger-admin-env.sh, so that > [ranger-admin-services.sh|https://github.com/apache/ranger/blob/master/embeddedwebserver/scripts/ranger-admin-services.sh] > knows which java to be used for processing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22951) Export JAVA_HOME env variable in shell script for Ranger
[ https://issues.apache.org/jira/browse/AMBARI-22951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-22951: - Status: Patch Available (was: Reopened) > Export JAVA_HOME env variable in shell script for Ranger > > > Key: AMBARI-22951 > URL: https://issues.apache.org/jira/browse/AMBARI-22951 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0, 2.5.1, 2.5.2, 2.5.3, 2.6.0, 2.6.1 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Major > Labels: pull-request-available > Fix For: 2.6.2 > > Attachments: AMBARI-22951.patch > > Time Spent: 1h 40m > Remaining Estimate: 0h > > Need to export JAVA_HOME variable in ranger-admin-env.sh, so that > [ranger-admin-services.sh|https://github.com/apache/ranger/blob/master/embeddedwebserver/scripts/ranger-admin-services.sh] > knows which java to be used for processing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (AMBARI-22951) Export JAVA_HOME env variable in shell script for Ranger
[ https://issues.apache.org/jira/browse/AMBARI-22951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar reopened AMBARI-22951: -- Reopening the jira to provide the fix in trunk and branch-2.7 > Export JAVA_HOME env variable in shell script for Ranger > > > Key: AMBARI-22951 > URL: https://issues.apache.org/jira/browse/AMBARI-22951 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0, 2.5.1, 2.5.2, 2.5.3, 2.6.0, 2.6.1 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Major > Labels: pull-request-available > Fix For: 2.6.2 > > Attachments: AMBARI-22951.patch > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Need to export JAVA_HOME variable in ranger-admin-env.sh, so that > [ranger-admin-services.sh|https://github.com/apache/ranger/blob/master/embeddedwebserver/scripts/ranger-admin-services.sh] > knows which java to be used for processing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24378) Updating LDAPSettings section for Ranger in Advanced config section
[
https://issues.apache.org/jira/browse/AMBARI-24378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-24378:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Updating LDAPSettings section for Ranger in Advanced config section
> ---
>
> Key: AMBARI-24378
> URL: https://issues.apache.org/jira/browse/AMBARI-24378
> Project: Ambari
> Issue Type: Bug
> Components: ambari-sever
>Affects Versions: 2.7.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Adding {{ranger.ldap.group.searchbase}}, {{ranger.ldap.group.searchfilter}}
> configs in LDAP category.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24378) Updating LDAPSettings section for Ranger in Advanced config section
[
https://issues.apache.org/jira/browse/AMBARI-24378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-24378:
-
Status: Patch Available (was: In Progress)
> Updating LDAPSettings section for Ranger in Advanced config section
> ---
>
> Key: AMBARI-24378
> URL: https://issues.apache.org/jira/browse/AMBARI-24378
> Project: Ambari
> Issue Type: Bug
> Components: ambari-sever
>Affects Versions: 2.7.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Adding {{ranger.ldap.group.searchbase}}, {{ranger.ldap.group.searchfilter}}
> configs in LDAP category.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24378) Updating LDAPSettings section for Ranger in Advanced config section
Mugdha Varadkar created AMBARI-24378:
Summary: Updating LDAPSettings section for Ranger in Advanced
config section
Key: AMBARI-24378
URL: https://issues.apache.org/jira/browse/AMBARI-24378
Project: Ambari
Issue Type: Bug
Components: ambari-sever
Affects Versions: 2.7.0
Reporter: Mugdha Varadkar
Assignee: Mugdha Varadkar
Fix For: 2.7.1
Adding {{ranger.ldap.group.searchbase}}, {{ranger.ldap.group.searchfilter}}
configs in LDAP category.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24352) Updating Ranger and Ranger KMS configs during Ambari upgrade
[
https://issues.apache.org/jira/browse/AMBARI-24352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-24352:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Updating Ranger and Ranger KMS configs during Ambari upgrade
>
>
> Key: AMBARI-24352
> URL: https://issues.apache.org/jira/browse/AMBARI-24352
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.70
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Attachments: AMBARI-24352-UT.patch, AMBARI-24352.patch
>
> Time Spent: 3h 50m
> Remaining Estimate: 0h
>
> *For Ranger*
> Updating Ranger Admin: {{ranger.logs.base.dir/ranger-admin-site.xml}} and
> Ranger Usersync: {{ranger.usersync.logdir/ranger-ugsync-site.xml}} log
> directory configs in stack.
> *For Ranger KMS*
> Adding new config {{ranger_kms_privelege_user_jdbc_url/kms-env.xml}} to have
> Test Connection button for verify communication to selected database using
> database root credentials.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24352) Updating Ranger and Ranger KMS configs during Ambari upgrade
[
https://issues.apache.org/jira/browse/AMBARI-24352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-24352:
-
Attachment: AMBARI-24352-UT.patch
> Updating Ranger and Ranger KMS configs during Ambari upgrade
>
>
> Key: AMBARI-24352
> URL: https://issues.apache.org/jira/browse/AMBARI-24352
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.70
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Attachments: AMBARI-24352-UT.patch, AMBARI-24352.patch
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> *For Ranger*
> Updating Ranger Admin: {{ranger.logs.base.dir/ranger-admin-site.xml}} and
> Ranger Usersync: {{ranger.usersync.logdir/ranger-ugsync-site.xml}} log
> directory configs in stack.
> *For Ranger KMS*
> Adding new config {{ranger_kms_privelege_user_jdbc_url/kms-env.xml}} to have
> Test Connection button for verify communication to selected database using
> database root credentials.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24352) Updating Ranger and Ranger KMS configs during Ambari upgrade
[
https://issues.apache.org/jira/browse/AMBARI-24352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-24352:
-
Status: Patch Available (was: In Progress)
> Updating Ranger and Ranger KMS configs during Ambari upgrade
>
>
> Key: AMBARI-24352
> URL: https://issues.apache.org/jira/browse/AMBARI-24352
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.70
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Attachments: AMBARI-24352.patch
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> *For Ranger*
> Updating Ranger Admin: {{ranger.logs.base.dir/ranger-admin-site.xml}} and
> Ranger Usersync: {{ranger.usersync.logdir/ranger-ugsync-site.xml}} log
> directory configs in stack.
> *For Ranger KMS*
> Adding new config {{ranger_kms_privelege_user_jdbc_url/kms-env.xml}} to have
> Test Connection button for verify communication to selected database using
> database root credentials.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24352) Updating Ranger and Ranger KMS configs during Ambari upgrade
[
https://issues.apache.org/jira/browse/AMBARI-24352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-24352:
-
Attachment: AMBARI-24352.patch
> Updating Ranger and Ranger KMS configs during Ambari upgrade
>
>
> Key: AMBARI-24352
> URL: https://issues.apache.org/jira/browse/AMBARI-24352
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.70
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Critical
> Fix For: 2.7.1
>
> Attachments: AMBARI-24352.patch
>
>
> *For Ranger*
> Updating Ranger Admin: {{ranger.logs.base.dir/ranger-admin-site.xml}} and
> Ranger Usersync: {{ranger.usersync.logdir/ranger-ugsync-site.xml}} log
> directory configs in stack.
> *For Ranger KMS*
> Adding new config {{ranger_kms_privelege_user_jdbc_url/kms-env.xml}} to have
> Test Connection button for verify communication to selected database using
> database root credentials.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24352) Updating Ranger and Ranger KMS configs during Ambari upgrade
[
https://issues.apache.org/jira/browse/AMBARI-24352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-24352:
-
Affects Version/s: 2.70
> Updating Ranger and Ranger KMS configs during Ambari upgrade
>
>
> Key: AMBARI-24352
> URL: https://issues.apache.org/jira/browse/AMBARI-24352
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.70
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Critical
> Fix For: 2.7.1
>
>
> *For Ranger*
> Updating Ranger Admin: {{ranger.logs.base.dir/ranger-admin-site.xml}} and
> Ranger Usersync: {{ranger.usersync.logdir/ranger-ugsync-site.xml}} log
> directory configs in stack.
> *For Ranger KMS*
> Adding new config {{ranger_kms_privelege_user_jdbc_url/kms-env.xml}} to have
> Test Connection button for verify communication to selected database using
> database root credentials.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24352) Updating Ranger and Ranger KMS configs during Ambari upgrade
Mugdha Varadkar created AMBARI-24352:
Summary: Updating Ranger and Ranger KMS configs during Ambari
upgrade
Key: AMBARI-24352
URL: https://issues.apache.org/jira/browse/AMBARI-24352
Project: Ambari
Issue Type: Bug
Components: ambari-server
Reporter: Mugdha Varadkar
Assignee: Mugdha Varadkar
Fix For: 2.7.1
*For Ranger*
Updating Ranger Admin: {{ranger.logs.base.dir/ranger-admin-site.xml}} and
Ranger Usersync: {{ranger.usersync.logdir/ranger-ugsync-site.xml}} log
directory configs in stack.
*For Ranger KMS*
Adding new config {{ranger_kms_privelege_user_jdbc_url/kms-env.xml}} to have
Test Connection button for verify communication to selected database using
database root credentials.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24216) Updating admin user password field value for Ranger and Atlas
[
https://issues.apache.org/jira/browse/AMBARI-24216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-24216:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Updating admin user password field value for Ranger and Atlas
> -
>
> Key: AMBARI-24216
> URL: https://issues.apache.org/jira/browse/AMBARI-24216
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Major
> Labels: pull-request-available
> Fix For: trunk
>
> Attachments: AMBARI-24216.patch
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Updating below admin user password configs in stack.
> Ranger: {{admin_password/ranger-env}}
> Atlas: {{atlas.admin.password/atlas-env}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24216) Updating admin user password field value for Ranger and Atlas
[
https://issues.apache.org/jira/browse/AMBARI-24216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-24216:
-
Attachment: AMBARI-24216.patch
> Updating admin user password field value for Ranger and Atlas
> -
>
> Key: AMBARI-24216
> URL: https://issues.apache.org/jira/browse/AMBARI-24216
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Major
> Labels: pull-request-available
> Fix For: trunk
>
> Attachments: AMBARI-24216.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Updating below admin user password configs in stack.
> Ranger: {{admin_password/ranger-env}}
> Atlas: {{atlas.admin.password/atlas-env}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24216) Updating admin user password field value for Ranger and Atlas
[
https://issues.apache.org/jira/browse/AMBARI-24216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-24216:
-
Status: Patch Available (was: In Progress)
> Updating admin user password field value for Ranger and Atlas
> -
>
> Key: AMBARI-24216
> URL: https://issues.apache.org/jira/browse/AMBARI-24216
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Major
> Labels: pull-request-available
> Fix For: trunk
>
> Attachments: AMBARI-24216.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Updating below admin user password configs in stack.
> Ranger: {{admin_password/ranger-env}}
> Atlas: {{atlas.admin.password/atlas-env}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24216) Updating admin user password field value for Ranger and Atlas
[
https://issues.apache.org/jira/browse/AMBARI-24216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-24216:
-
Description:
Updating below admin user password configs in stack.
Ranger: {{admin_password/ranger-env}}
Atlas: {{atlas.admin.password/atlas-env}}
was:
Setting below admin user password configs in stack.
Ranger: {{admin_password/ranger-env}}
Atlas: {{atlas.admin.password/atlas-env}}
> Updating admin user password field value for Ranger and Atlas
> -
>
> Key: AMBARI-24216
> URL: https://issues.apache.org/jira/browse/AMBARI-24216
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Major
> Fix For: trunk
>
>
> Updating below admin user password configs in stack.
> Ranger: {{admin_password/ranger-env}}
> Atlas: {{atlas.admin.password/atlas-env}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24216) Updating admin user password field value for Ranger and Atlas
Mugdha Varadkar created AMBARI-24216:
Summary: Updating admin user password field value for Ranger and
Atlas
Key: AMBARI-24216
URL: https://issues.apache.org/jira/browse/AMBARI-24216
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: trunk
Reporter: Mugdha Varadkar
Assignee: Mugdha Varadkar
Fix For: trunk
Setting below admin user password configs in stack.
Ranger: {{admin_password/ranger-env}}
Atlas: {{atlas.admin.password/atlas-env}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23979) Updating ownership and permission of .crc file for Ranger service and Ranger plugin supported services
[ https://issues.apache.org/jira/browse/AMBARI-23979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-23979: - Resolution: Fixed Status: Resolved (was: Patch Available) > Updating ownership and permission of .crc file for Ranger service and Ranger > plugin supported services > -- > > Key: AMBARI-23979 > URL: https://issues.apache.org/jira/browse/AMBARI-23979 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Major > Labels: pull-request-available > Fix For: trunk > > Attachments: AMBARI-23979.patch > > Time Spent: 1h > Remaining Estimate: 0h > > Setting up appropriate permission and ownership on .crc file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23979) Updating ownership and permission of .crc file for Ranger service and Ranger plugin supported services
[ https://issues.apache.org/jira/browse/AMBARI-23979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-23979: - Attachment: (was: AMBARI-17607.patch) > Updating ownership and permission of .crc file for Ranger service and Ranger > plugin supported services > -- > > Key: AMBARI-23979 > URL: https://issues.apache.org/jira/browse/AMBARI-23979 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Major > Fix For: trunk > > Attachments: AMBARI-23979.patch > > > Setting up appropriate permission and ownership on .crc file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23979) Updating ownership and permission of .crc file for Ranger service and Ranger plugin supported services
[ https://issues.apache.org/jira/browse/AMBARI-23979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-23979: - Attachment: AMBARI-23979.patch > Updating ownership and permission of .crc file for Ranger service and Ranger > plugin supported services > -- > > Key: AMBARI-23979 > URL: https://issues.apache.org/jira/browse/AMBARI-23979 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Major > Fix For: trunk > > Attachments: AMBARI-23979.patch > > > Setting up appropriate permission and ownership on .crc file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23979) Updating ownership and permission of .crc file for Ranger service and Ranger plugin supported services
[ https://issues.apache.org/jira/browse/AMBARI-23979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-23979: - Status: Patch Available (was: In Progress) > Updating ownership and permission of .crc file for Ranger service and Ranger > plugin supported services > -- > > Key: AMBARI-23979 > URL: https://issues.apache.org/jira/browse/AMBARI-23979 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Major > Fix For: trunk > > Attachments: AMBARI-17607.patch > > > Setting up appropriate permission and ownership on .crc file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23979) Updating ownership and permission of .crc file for Ranger service and Ranger plugin supported services
Mugdha Varadkar created AMBARI-23979: Summary: Updating ownership and permission of .crc file for Ranger service and Ranger plugin supported services Key: AMBARI-23979 URL: https://issues.apache.org/jira/browse/AMBARI-23979 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Mugdha Varadkar Assignee: Mugdha Varadkar Fix For: trunk Setting up appropriate permission and ownership on .crc file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23762) Updating default Ranger Hdfs service name for NN Federation enabled cluster
[ https://issues.apache.org/jira/browse/AMBARI-23762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-23762: - Resolution: Fixed Status: Resolved (was: Patch Available) > Updating default Ranger Hdfs service name for NN Federation enabled cluster > --- > > Key: AMBARI-23762 > URL: https://issues.apache.org/jira/browse/AMBARI-23762 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Major > Labels: pull-request-available > Fix For: trunk > > Attachments: AMBARI-23762.patch > > Time Spent: 50m > Remaining Estimate: 0h > > Adding code logic in [ranger function > file|https://github.com/apache/ambari/blob/trunk/ambari-common/src/main/python/resource_management/libraries/functions/ranger_functions_v2.py] > for updating service name on Ranger Admin using Ranger REST API. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23738) Need to add pre-upgrade check for Atlas service during stack upgrade
[
https://issues.apache.org/jira/browse/AMBARI-23738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-23738:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Need to add pre-upgrade check for Atlas service during stack upgrade
>
>
> Key: AMBARI-23738
> URL: https://issues.apache.org/jira/browse/AMBARI-23738
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Vishal Suvagia
>Assignee: Mugdha Varadkar
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 3h
> Remaining Estimate: 0h
>
> While upgrading to stack 3.0, Atlas needs to migrate data from existing
> version to upgraded versions. To migrate the data we need to provide
> {{atlas.migration.data.filename}} property in the application-properties
> before upgrading the stack.
> Hence prior to upgrading from existing stack to 3.0 stack we will need to
> check if the property {{atlas.migration.data.filename}} exists or not.
> Reference ATLAS-2460.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23738) Need to add pre-upgrade check for Atlas service during stack upgrade
[
https://issues.apache.org/jira/browse/AMBARI-23738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-23738:
-
Status: Patch Available (was: In Progress)
> Need to add pre-upgrade check for Atlas service during stack upgrade
>
>
> Key: AMBARI-23738
> URL: https://issues.apache.org/jira/browse/AMBARI-23738
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Vishal Suvagia
>Assignee: Mugdha Varadkar
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> While upgrading to stack 3.0, Atlas needs to migrate data from existing
> version to upgraded versions. To migrate the data we need to provide
> {{atlas.migration.data.filename}} property in the application-properties
> before upgrading the stack.
> Hence prior to upgrading from existing stack to 3.0 stack we will need to
> check if the property {{atlas.migration.data.filename}} exists or not.
> Reference ATLAS-2460.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (AMBARI-23738) Need to add pre-upgrade check for Atlas service during stack upgrade
[
https://issues.apache.org/jira/browse/AMBARI-23738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar reassigned AMBARI-23738:
Assignee: Mugdha Varadkar (was: Vishal Suvagia)
> Need to add pre-upgrade check for Atlas service during stack upgrade
>
>
> Key: AMBARI-23738
> URL: https://issues.apache.org/jira/browse/AMBARI-23738
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Vishal Suvagia
>Assignee: Mugdha Varadkar
>Priority: Major
> Fix For: 2.7.0
>
>
> While upgrading to stack 3.0, Atlas needs to migrate data from existing
> version to upgraded versions. To migrate the data we need to provide
> {{atlas.migration.data.filename}} property in the application-properties
> before upgrading the stack.
> Hence prior to upgrading from existing stack to 3.0 stack we will need to
> check if the property {{atlas.migration.data.filename}} exists or not.
> Reference ATLAS-2460.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23762) Updating default Ranger Hdfs service name for NN Federation enabled cluster
[ https://issues.apache.org/jira/browse/AMBARI-23762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-23762: - Status: Patch Available (was: In Progress) > Updating default Ranger Hdfs service name for NN Federation enabled cluster > --- > > Key: AMBARI-23762 > URL: https://issues.apache.org/jira/browse/AMBARI-23762 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Major > Labels: pull-request-available > Fix For: trunk > > Attachments: AMBARI-23762.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Adding code logic in [ranger function > file|https://github.com/apache/ambari/blob/trunk/ambari-common/src/main/python/resource_management/libraries/functions/ranger_functions_v2.py] > for updating service name on Ranger Admin using Ranger REST API. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23762) Updating default Ranger Hdfs service name for NN Federation enabled cluster
[ https://issues.apache.org/jira/browse/AMBARI-23762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-23762: - Attachment: AMBARI-23762.patch > Updating default Ranger Hdfs service name for NN Federation enabled cluster > --- > > Key: AMBARI-23762 > URL: https://issues.apache.org/jira/browse/AMBARI-23762 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Major > Labels: pull-request-available > Fix For: trunk > > Attachments: AMBARI-23762.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Adding code logic in [ranger function > file|https://github.com/apache/ambari/blob/trunk/ambari-common/src/main/python/resource_management/libraries/functions/ranger_functions_v2.py] > for updating service name on Ranger Admin using Ranger REST API. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23762) Updating default Ranger Hdfs service name for NN Federation enabled cluster
Mugdha Varadkar created AMBARI-23762: Summary: Updating default Ranger Hdfs service name for NN Federation enabled cluster Key: AMBARI-23762 URL: https://issues.apache.org/jira/browse/AMBARI-23762 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: trunk Reporter: Mugdha Varadkar Assignee: Mugdha Varadkar Fix For: trunk Adding code logic in [ranger function file|https://github.com/apache/ambari/blob/trunk/ambari-common/src/main/python/resource_management/libraries/functions/ranger_functions_v2.py] for updating service name on Ranger Admin using Ranger REST API. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23103) Adding Stack feature constant for Ranger and Ranger KMS services
[
https://issues.apache.org/jira/browse/AMBARI-23103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-23103:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Adding Stack feature constant for Ranger and Ranger KMS services
>
>
> Key: AMBARI-23103
> URL: https://issues.apache.org/jira/browse/AMBARI-23103
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Major
> Labels: pull-request-available
> Fix For: trunk
>
> Attachments: AMBARI-23103.patch
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Need to add a constant in Stack feature for {{RANGER}} and {{RANGER_KMS}}
> services. This constant will be used during upgrade of stack 2.6 to 3.0.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23103) Adding Stack feature constant for Ranger and Ranger KMS services
[
https://issues.apache.org/jira/browse/AMBARI-23103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-23103:
-
Status: Patch Available (was: In Progress)
> Adding Stack feature constant for Ranger and Ranger KMS services
>
>
> Key: AMBARI-23103
> URL: https://issues.apache.org/jira/browse/AMBARI-23103
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Major
> Labels: pull-request-available
> Fix For: trunk
>
> Attachments: AMBARI-23103.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Need to add a constant in Stack feature for {{RANGER}} and {{RANGER_KMS}}
> services. This constant will be used during upgrade of stack 2.6 to 3.0.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23103) Adding Stack feature constant for Ranger and Ranger KMS services
[
https://issues.apache.org/jira/browse/AMBARI-23103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-23103:
-
Attachment: AMBARI-23103.patch
> Adding Stack feature constant for Ranger and Ranger KMS services
>
>
> Key: AMBARI-23103
> URL: https://issues.apache.org/jira/browse/AMBARI-23103
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Major
> Fix For: trunk
>
> Attachments: AMBARI-23103.patch
>
>
> Need to add a constant in Stack feature for {{RANGER}} and {{RANGER_KMS}}
> services. This constant will be used during upgrade of stack 2.6 to 3.0.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23103) Adding Stack feature constant for Ranger and Ranger KMS services
Mugdha Varadkar created AMBARI-23103:
Summary: Adding Stack feature constant for Ranger and Ranger KMS
services
Key: AMBARI-23103
URL: https://issues.apache.org/jira/browse/AMBARI-23103
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: trunk
Reporter: Mugdha Varadkar
Assignee: Mugdha Varadkar
Fix For: trunk
Need to add a constant in Stack feature for {{RANGER}} and {{RANGER_KMS}}
services. This constant will be used during upgrade of stack 2.6 to 3.0.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22350) Updating Ranger & Atlas stack features for stack 3.0
[ https://issues.apache.org/jira/browse/AMBARI-22350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-22350: - Resolution: Not A Bug Status: Resolved (was: Patch Available) > Updating Ranger & Atlas stack features for stack 3.0 > > > Key: AMBARI-22350 > URL: https://issues.apache.org/jira/browse/AMBARI-22350 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Major > Fix For: 3.0.0 > > Attachments: AMBARI-22350.patch > > > Adding missing Ranger & Atlas stack features for stack 3.0 and also adding > AMBARI-21227 fix for Ranger & Ranger Kms stack 3.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22951) Export JAVA_HOME env variable in shell script for Ranger
[ https://issues.apache.org/jira/browse/AMBARI-22951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-22951: - Resolution: Fixed Status: Resolved (was: Patch Available) > Export JAVA_HOME env variable in shell script for Ranger > > > Key: AMBARI-22951 > URL: https://issues.apache.org/jira/browse/AMBARI-22951 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0, 2.5.1, 2.5.2, 2.5.3, 2.6.0, 2.6.1 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Major > Labels: pull-request-available > Fix For: 2.6.2 > > Attachments: AMBARI-22951.patch > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Need to export JAVA_HOME variable in ranger-admin-env.sh, so that > [ranger-admin-services.sh|https://github.com/apache/ranger/blob/master/embeddedwebserver/scripts/ranger-admin-services.sh] > knows which java to be used for processing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22951) Export JAVA_HOME env variable in shell script for Ranger
[ https://issues.apache.org/jira/browse/AMBARI-22951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-22951: - Status: Patch Available (was: In Progress) > Export JAVA_HOME env variable in shell script for Ranger > > > Key: AMBARI-22951 > URL: https://issues.apache.org/jira/browse/AMBARI-22951 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0, 2.5.1, 2.5.2, 2.5.3, 2.6.0, 2.6.1 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Major > Labels: pull-request-available > Fix For: 2.6.2 > > Attachments: AMBARI-22951.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Need to export JAVA_HOME variable in ranger-admin-env.sh, so that > [ranger-admin-services.sh|https://github.com/apache/ranger/blob/master/embeddedwebserver/scripts/ranger-admin-services.sh] > knows which java to be used for processing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22951) Export JAVA_HOME env variable in shell script for Ranger
[ https://issues.apache.org/jira/browse/AMBARI-22951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-22951: - Attachment: AMBARI-22951.patch > Export JAVA_HOME env variable in shell script for Ranger > > > Key: AMBARI-22951 > URL: https://issues.apache.org/jira/browse/AMBARI-22951 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0, 2.5.1, 2.5.2, 2.5.3, 2.6.0, 2.6.1 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Major > Fix For: 2.6.2 > > Attachments: AMBARI-22951.patch > > > Need to export JAVA_HOME variable in ranger-admin-env.sh, so that > [ranger-admin-services.sh|https://github.com/apache/ranger/blob/master/embeddedwebserver/scripts/ranger-admin-services.sh] > knows which java to be used for processing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-22951) Export JAVA_HOME env variable in shell script for Ranger
Mugdha Varadkar created AMBARI-22951: Summary: Export JAVA_HOME env variable in shell script for Ranger Key: AMBARI-22951 URL: https://issues.apache.org/jira/browse/AMBARI-22951 Project: Ambari Issue Type: Bug Affects Versions: 2.5.0, 2.5.1, 2.5.2, 2.5.3, 2.6.0, 2.6.1 Reporter: Mugdha Varadkar Assignee: Mugdha Varadkar Fix For: 2.6.2 Need to export JAVA_HOME variable in ranger-admin-env.sh, so that [ranger-admin-services.sh|https://github.com/apache/ranger/blob/master/embeddedwebserver/scripts/ranger-admin-services.sh] knows which java to be used for processing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22669) Ranger stack script changes to fix missing directory failure for blueprint installation
[
https://issues.apache.org/jira/browse/AMBARI-22669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-22669:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk: 9c7f1b7aa9d04bea2f7e68a64fd242f20c86b521
> Ranger stack script changes to fix missing directory failure for blueprint
> installation
> ---
>
> Key: AMBARI-22669
> URL: https://issues.apache.org/jira/browse/AMBARI-22669
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
> Fix For: 3.0.0
>
> Attachments: AMBARI-22669.patch
>
>
> Updating stack scripts code to remove use of {{commandParams/version}} to
> build system path. For upgrade, using upgrade_summary module to get
> upgrade-to version ie (target version).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22669) Ranger stack script changes to fix missing directory failure for blueprint installation
[
https://issues.apache.org/jira/browse/AMBARI-22669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-22669:
-
Attachment: AMBARI-22669.patch
> Ranger stack script changes to fix missing directory failure for blueprint
> installation
> ---
>
> Key: AMBARI-22669
> URL: https://issues.apache.org/jira/browse/AMBARI-22669
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
> Fix For: 3.0.0
>
> Attachments: AMBARI-22669.patch
>
>
> Updating stack scripts code to remove use of {{commandParams/version}} to
> build system path. For upgrade, using upgrade_summary module to get
> upgrade-to version ie (target version).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22669) Ranger stack script changes to fix missing directory failure for blueprint installation
[
https://issues.apache.org/jira/browse/AMBARI-22669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-22669:
-
Status: Patch Available (was: Open)
> Ranger stack script changes to fix missing directory failure for blueprint
> installation
> ---
>
> Key: AMBARI-22669
> URL: https://issues.apache.org/jira/browse/AMBARI-22669
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
> Fix For: 3.0.0
>
> Attachments: AMBARI-22669.patch
>
>
> Updating stack scripts code to remove use of {{commandParams/version}} to
> build system path. For upgrade, using upgrade_summary module to get
> upgrade-to version ie (target version).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22669) Ranger stack script changes to fix missing directory failure for blueprint installation
Mugdha Varadkar created AMBARI-22669:
Summary: Ranger stack script changes to fix missing directory
failure for blueprint installation
Key: AMBARI-22669
URL: https://issues.apache.org/jira/browse/AMBARI-22669
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.6.0
Reporter: Mugdha Varadkar
Assignee: Mugdha Varadkar
Fix For: 3.0.0
Updating stack scripts code to remove use of {{commandParams/version}} to build
system path. For upgrade, using upgrade_summary module to get upgrade-to
version ie (target version).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22635) Ambari should create a dummy core-site.xml for Ranger plugins when namenode is not installed
[ https://issues.apache.org/jira/browse/AMBARI-22635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16290824#comment-16290824 ] Mugdha Varadkar commented on AMBARI-22635: -- +1 for attached [^AMBARI-22635-trunk.1-addendum.patch] > Ambari should create a dummy core-site.xml for Ranger plugins when namenode > is not installed > > > Key: AMBARI-22635 > URL: https://issues.apache.org/jira/browse/AMBARI-22635 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.0, 2.6.1 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: trunk, 2.6.2 > > Attachments: AMBARI-22635-branch-2.6.1.patch, > AMBARI-22635-branch-2.6.2.patch, AMBARI-22635-branch-2.6.patch, > AMBARI-22635-trunk.1-addendum.patch, AMBARI-22635-trunk.1.patch, > AMBARI-22635-trunk.patch > > > For Ranger plugins to work properly in kerberised environments where HDFS is > not installed. We need to create a core-site.xml for Storm and Kafka plugins > so that the plugins can work to fetch latest policies from with kerberised > calls from Ranger. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22463) Removing secure reference configs entries from stack for Ranger KMS service
[
https://issues.apache.org/jira/browse/AMBARI-22463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-22463:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk: 8b820346ca2902016ee2d5d7d5d3ff5d60126933
> Removing secure reference configs entries from stack for Ranger KMS service
> ---
>
> Key: AMBARI-22463
> URL: https://issues.apache.org/jira/browse/AMBARI-22463
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-22463.patch
>
>
> Removing below properties entries from stack.
> {noformat}
> hadoop.kms.authentication.kerberos.keytab
> hadoop.kms.authentication.kerberos.principal
> hadoop.kms.authentication.signer.secret.provider.zookeeper.kerberos.keytab
> hadoop.kms.authentication.signer.secret.provider.zookeeper.kerberos.principal
> {noformat}
> These properties will be added in secure cluster using Ranger KMS Kerberos
> descriptor.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22463) Removing secure reference configs entries from stack for Ranger KMS service
[
https://issues.apache.org/jira/browse/AMBARI-22463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-22463:
-
Status: Patch Available (was: In Progress)
> Removing secure reference configs entries from stack for Ranger KMS service
> ---
>
> Key: AMBARI-22463
> URL: https://issues.apache.org/jira/browse/AMBARI-22463
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-22463.patch
>
>
> Removing below properties entries from stack.
> {noformat}
> hadoop.kms.authentication.kerberos.keytab
> hadoop.kms.authentication.kerberos.principal
> hadoop.kms.authentication.signer.secret.provider.zookeeper.kerberos.keytab
> hadoop.kms.authentication.signer.secret.provider.zookeeper.kerberos.principal
> {noformat}
> These properties will be added in secure cluster using Ranger KMS Kerberos
> descriptor.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22463) Removing secure reference configs entries from stack for Ranger KMS service
[
https://issues.apache.org/jira/browse/AMBARI-22463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-22463:
-
Attachment: AMBARI-22463.patch
> Removing secure reference configs entries from stack for Ranger KMS service
> ---
>
> Key: AMBARI-22463
> URL: https://issues.apache.org/jira/browse/AMBARI-22463
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-22463.patch
>
>
> Removing below properties entries from stack.
> {noformat}
> hadoop.kms.authentication.kerberos.keytab
> hadoop.kms.authentication.kerberos.principal
> hadoop.kms.authentication.signer.secret.provider.zookeeper.kerberos.keytab
> hadoop.kms.authentication.signer.secret.provider.zookeeper.kerberos.principal
> {noformat}
> These properties will be added in secure cluster using Ranger KMS Kerberos
> descriptor.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22463) Removing secure reference configs entries from stack for Ranger KMS service
Mugdha Varadkar created AMBARI-22463:
Summary: Removing secure reference configs entries from stack for
Ranger KMS service
Key: AMBARI-22463
URL: https://issues.apache.org/jira/browse/AMBARI-22463
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: trunk
Reporter: Mugdha Varadkar
Assignee: Mugdha Varadkar
Priority: Critical
Fix For: trunk
Removing below properties entries from stack.
{noformat}
hadoop.kms.authentication.kerberos.keytab
hadoop.kms.authentication.kerberos.principal
hadoop.kms.authentication.signer.secret.provider.zookeeper.kerberos.keytab
hadoop.kms.authentication.signer.secret.provider.zookeeper.kerberos.principal
{noformat}
These properties will be added in secure cluster using Ranger KMS Kerberos
descriptor.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22350) Updating Ranger & Atlas stack features for stack 3.0
[ https://issues.apache.org/jira/browse/AMBARI-22350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-22350: - Status: Patch Available (was: In Progress) > Updating Ranger & Atlas stack features for stack 3.0 > > > Key: AMBARI-22350 > URL: https://issues.apache.org/jira/browse/AMBARI-22350 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Major > Fix For: 3.0.0 > > Attachments: AMBARI-22350.patch > > > Adding missing Ranger & Atlas stack features for stack 3.0 and also adding > AMBARI-21227 fix for Ranger & Ranger Kms stack 3.0. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22350) Updating Ranger & Atlas stack features for stack 3.0
[ https://issues.apache.org/jira/browse/AMBARI-22350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-22350: - Attachment: AMBARI-22350.patch > Updating Ranger & Atlas stack features for stack 3.0 > > > Key: AMBARI-22350 > URL: https://issues.apache.org/jira/browse/AMBARI-22350 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Major > Fix For: 3.0.0 > > Attachments: AMBARI-22350.patch > > > Adding missing Ranger & Atlas stack features for stack 3.0 and also adding > AMBARI-21227 fix for Ranger & Ranger Kms stack 3.0. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22350) Updating Ranger & Atlas stack features for stack 3.0
Mugdha Varadkar created AMBARI-22350: Summary: Updating Ranger & Atlas stack features for stack 3.0 Key: AMBARI-22350 URL: https://issues.apache.org/jira/browse/AMBARI-22350 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 3.0.0 Reporter: Mugdha Varadkar Assignee: Mugdha Varadkar Priority: Major Fix For: 3.0.0 Adding missing Ranger & Atlas stack features for stack 3.0 and also adding AMBARI-21227 fix for Ranger & Ranger Kms stack 3.0. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22234) Optimizing Ranger KMS imports
[ https://issues.apache.org/jira/browse/AMBARI-22234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-22234: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk: d6cd303d0207ac6ffcdbc16d129758bba9494423 > Optimizing Ranger KMS imports > - > > Key: AMBARI-22234 > URL: https://issues.apache.org/jira/browse/AMBARI-22234 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar > Fix For: trunk > > Attachments: AMBARI-22234.patch > > > Updating Ranger Kms script file and using proper methods for importing > modules. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22232) Need to add a new property to support proxy users property for Atlas service
[
https://issues.apache.org/jira/browse/AMBARI-22232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16205647#comment-16205647
]
Mugdha Varadkar commented on AMBARI-22232:
--
+1 for [^AMBARI-22232_Addendum.patch]
> Need to add a new property to support proxy users property for Atlas service
>
>
> Key: AMBARI-22232
> URL: https://issues.apache.org/jira/browse/AMBARI-22232
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
>Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: AMBARI-22232_Addendum.patch,
> AMBARI-22232_branch-2.6.1.patch, AMBARI-22232_branch-2.6.patch,
> AMBARI-22232_trunk.1.patch, AMBARI-22232_trunk.patch
>
>
> When Atlas is enabled via proxy needs to know the proxy-users to authorize
> them while accessing the Atlas service via proxy support using property
> {{atlas.proxyusers}} with default value knox. Additional details on ATLAS-2166
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22234) Optimizing Ranger KMS imports
[ https://issues.apache.org/jira/browse/AMBARI-22234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-22234: - Status: Patch Available (was: In Progress) > Optimizing Ranger KMS imports > - > > Key: AMBARI-22234 > URL: https://issues.apache.org/jira/browse/AMBARI-22234 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar > Fix For: trunk > > Attachments: AMBARI-22234.patch > > > Updating Ranger Kms script file and using proper methods for importing > modules. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22234) Optimizing Ranger KMS imports
[ https://issues.apache.org/jira/browse/AMBARI-22234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-22234: - Attachment: AMBARI-22234.patch > Optimizing Ranger KMS imports > - > > Key: AMBARI-22234 > URL: https://issues.apache.org/jira/browse/AMBARI-22234 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar > Fix For: trunk > > Attachments: AMBARI-22234.patch > > > Updating Ranger Kms script file and using proper methods for importing > modules. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22234) Optimizing Ranger KMS imports
Mugdha Varadkar created AMBARI-22234: Summary: Optimizing Ranger KMS imports Key: AMBARI-22234 URL: https://issues.apache.org/jira/browse/AMBARI-22234 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: trunk Reporter: Mugdha Varadkar Assignee: Mugdha Varadkar Fix For: trunk Updating Ranger Kms script file and using proper methods for importing modules. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22204) Updating Ranger Admin pre-upgrade task
[ https://issues.apache.org/jira/browse/AMBARI-22204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-22204: - Attachment: AMBARI-22204.1.patch AMBARI-22204-1-trunk.patch > Updating Ranger Admin pre-upgrade task > -- > > Key: AMBARI-22204 > URL: https://issues.apache.org/jira/browse/AMBARI-22204 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.0 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Blocker > Fix For: 2.6.0 > > Attachments: AMBARI-22204-1-trunk.patch, AMBARI-22204.1.patch, > AMBARI-22204.patch > > > After AMBARI-21581 changes, need to update Ranger Admin pre-upgrade task. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22204) Updating Ranger Admin pre-upgrade task
[ https://issues.apache.org/jira/browse/AMBARI-22204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-22204: - Status: Patch Available (was: In Progress) > Updating Ranger Admin pre-upgrade task > -- > > Key: AMBARI-22204 > URL: https://issues.apache.org/jira/browse/AMBARI-22204 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.0 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Blocker > Fix For: 2.6.0 > > Attachments: AMBARI-22204.patch > > > After AMBARI-21581 changes, need to update Ranger Admin pre-upgrade task. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22204) Updating Ranger Admin pre-upgrade task
[ https://issues.apache.org/jira/browse/AMBARI-22204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-22204: - Attachment: AMBARI-22204.patch > Updating Ranger Admin pre-upgrade task > -- > > Key: AMBARI-22204 > URL: https://issues.apache.org/jira/browse/AMBARI-22204 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.0 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Blocker > Fix For: 2.6.0 > > Attachments: AMBARI-22204.patch > > > After AMBARI-21581 changes, need to update Ranger Admin pre-upgrade task. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22204) Updating Ranger Admin pre-upgrade task
Mugdha Varadkar created AMBARI-22204: Summary: Updating Ranger Admin pre-upgrade task Key: AMBARI-22204 URL: https://issues.apache.org/jira/browse/AMBARI-22204 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.6.0 Reporter: Mugdha Varadkar Assignee: Mugdha Varadkar Priority: Blocker Fix For: 2.6.0 After AMBARI-21581 changes, need to update Ranger Admin pre-upgrade task. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22102) Ranger KMS should add proxy user for Spark2 user
[ https://issues.apache.org/jira/browse/AMBARI-22102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-22102: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.6: 1ef5b391f529c5dd58556f55211e3735f1e9ace5 trunk: 03696f16607dc84723b608a66c476ea0706bf525 > Ranger KMS should add proxy user for Spark2 user > > > Key: AMBARI-22102 > URL: https://issues.apache.org/jira/browse/AMBARI-22102 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.0 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar > Fix For: 2.6.0 > > Attachments: AMBARI-22102.patch, AMBARI-22102-trunk.patch > > > Spark2 user needs to be added to Ranger KMS proxy users in cluster. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22102) Ranger KMS should add proxy user for Spark2 user
[ https://issues.apache.org/jira/browse/AMBARI-22102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-22102: - Attachment: AMBARI-22102-trunk.patch > Ranger KMS should add proxy user for Spark2 user > > > Key: AMBARI-22102 > URL: https://issues.apache.org/jira/browse/AMBARI-22102 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.0 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar > Fix For: 2.6.0 > > Attachments: AMBARI-22102.patch, AMBARI-22102-trunk.patch > > > Spark2 user needs to be added to Ranger KMS proxy users in cluster. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22102) Ranger KMS should add proxy user for Spark2 user
[ https://issues.apache.org/jira/browse/AMBARI-22102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-22102: - Status: Patch Available (was: In Progress) > Ranger KMS should add proxy user for Spark2 user > > > Key: AMBARI-22102 > URL: https://issues.apache.org/jira/browse/AMBARI-22102 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.0 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar > Fix For: 2.6.0 > > Attachments: AMBARI-22102.patch > > > Spark2 user needs to be added to Ranger KMS proxy users in cluster. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22102) Ranger KMS should add proxy user for Spark2 user
[ https://issues.apache.org/jira/browse/AMBARI-22102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-22102: - Attachment: AMBARI-22102.patch > Ranger KMS should add proxy user for Spark2 user > > > Key: AMBARI-22102 > URL: https://issues.apache.org/jira/browse/AMBARI-22102 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.0 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar > Fix For: 2.6.0 > > Attachments: AMBARI-22102.patch > > > Spark2 user needs to be added to Ranger KMS proxy users in cluster. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22102) Ranger KMS should add proxy user for Spark2 user
[ https://issues.apache.org/jira/browse/AMBARI-22102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-22102: - Summary: Ranger KMS should add proxy user for Spark2 user (was: Ranger KMS should add proxy users for Spark2 user) > Ranger KMS should add proxy user for Spark2 user > > > Key: AMBARI-22102 > URL: https://issues.apache.org/jira/browse/AMBARI-22102 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.0 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar > Fix For: 2.6.0 > > > Spark2 user needs to be added to Ranger KMS proxy users in cluster. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22102) Ranger KMS should add proxy users for Spark2 user
[ https://issues.apache.org/jira/browse/AMBARI-22102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-22102: - Component/s: ambari-server > Ranger KMS should add proxy users for Spark2 user > - > > Key: AMBARI-22102 > URL: https://issues.apache.org/jira/browse/AMBARI-22102 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.0 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar > Fix For: 2.6.0 > > > Spark2 user needs to be added to Ranger KMS proxy users in cluster. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22102) Ranger KMS should add proxy users for Spark2 user
Mugdha Varadkar created AMBARI-22102: Summary: Ranger KMS should add proxy users for Spark2 user Key: AMBARI-22102 URL: https://issues.apache.org/jira/browse/AMBARI-22102 Project: Ambari Issue Type: Bug Affects Versions: 2.6.0 Reporter: Mugdha Varadkar Assignee: Mugdha Varadkar Fix For: 2.6.0 Spark2 user needs to be added to Ranger KMS proxy users in cluster. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21910) Ranger Usersync config to support nested group evaluation for LDAP Sync source property
[ https://issues.apache.org/jira/browse/AMBARI-21910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-21910: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.6: f5ec3291215aae8320f99b542be7648fec1b7fd1 trunk: ea892443513fa730dad2ef3af06069ef618e0225 > Ranger Usersync config to support nested group evaluation for LDAP Sync > source property > --- > > Key: AMBARI-21910 > URL: https://issues.apache.org/jira/browse/AMBARI-21910 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.0 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-21910-01-branch-2.6.patch, > AMBARI-21910-01-trunk.patch, AMBARI-21910-02-branch-2.6.patch, > AMBARI-21910-02-trunk.patch, AMBARI-21910.patch > > > As part of RANGER-1735, we are supporting nested groups in ranger usersync. > For this, introduced one new property > "ranger.usersync.ldap.grouphierarchylevels". The value should be an integer > with default value as 0. This property should be under Ranger --> Configs --> > Ranger User Info --> Group Configs tab. > This property can be enabled with a flag labelled as "Sync Nested Groups". > 1. Default value for this flag is "No" > 2. This flag is always shown under Group Configs (even when "Enable group > Sync" is set to "No") > 3. If this flag is set to "No", then the value for > ranger.usersync.ldap.grouphierarchylevels is hidden and is set to "0". > 4. If this flag is set to "Yes", then > ranger.usersync.ldap.grouphierarchylevels is shown and allowed to set any > integer greater than 0. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21910) Ranger Usersync config to support nested group evaluation for LDAP Sync source property
[ https://issues.apache.org/jira/browse/AMBARI-21910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-21910: - Attachment: AMBARI-21910-02-branch-2.6.patch AMBARI-21910-02-trunk.patch > Ranger Usersync config to support nested group evaluation for LDAP Sync > source property > --- > > Key: AMBARI-21910 > URL: https://issues.apache.org/jira/browse/AMBARI-21910 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.0 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-21910-01-branch-2.6.patch, > AMBARI-21910-01-trunk.patch, AMBARI-21910-02-branch-2.6.patch, > AMBARI-21910-02-trunk.patch, AMBARI-21910.patch > > > As part of RANGER-1735, we are supporting nested groups in ranger usersync. > For this, introduced one new property > "ranger.usersync.ldap.grouphierarchylevels". The value should be an integer > with default value as 0. This property should be under Ranger --> Configs --> > Ranger User Info --> Group Configs tab. > This property can be enabled with a flag labelled as "Sync Nested Groups". > 1. Default value for this flag is "No" > 2. This flag is always shown under Group Configs (even when "Enable group > Sync" is set to "No") > 3. If this flag is set to "No", then the value for > ranger.usersync.ldap.grouphierarchylevels is hidden and is set to "0". > 4. If this flag is set to "Yes", then > ranger.usersync.ldap.grouphierarchylevels is shown and allowed to set any > integer greater than 0. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21910) Ranger Usersync config to support nested group evaluation for LDAP Sync source property
[ https://issues.apache.org/jira/browse/AMBARI-21910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-21910: - Attachment: AMBARI-21910-01-branch-2.6.patch AMBARI-21910-01-trunk.patch > Ranger Usersync config to support nested group evaluation for LDAP Sync > source property > --- > > Key: AMBARI-21910 > URL: https://issues.apache.org/jira/browse/AMBARI-21910 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.0 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-21910-01-branch-2.6.patch, > AMBARI-21910-01-trunk.patch, AMBARI-21910.patch > > > As part of RANGER-1735, we are supporting nested groups in ranger usersync. > For this, introduced one new property > "ranger.usersync.ldap.grouphierarchylevels". The value should be an integer > with default value as 0. This property should be under Ranger --> Configs --> > Ranger User Info --> Group Configs tab. > This property can be enabled with a flag labelled as "Sync Nested Groups". > 1. Default value for this flag is "No" > 2. This flag is always shown under Group Configs (even when "Enable group > Sync" is set to "No") > 3. If this flag is set to "No", then the value for > ranger.usersync.ldap.grouphierarchylevels is hidden and is set to "0". > 4. If this flag is set to "Yes", then > ranger.usersync.ldap.grouphierarchylevels is shown and allowed to set any > integer greater than 0. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21910) Ranger Usersync config to support nested group evaluation for LDAP Sync source property
[ https://issues.apache.org/jira/browse/AMBARI-21910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-21910: - Status: Patch Available (was: In Progress) > Ranger Usersync config to support nested group evaluation for LDAP Sync > source property > --- > > Key: AMBARI-21910 > URL: https://issues.apache.org/jira/browse/AMBARI-21910 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.0 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-21910.patch > > > As part of RANGER-1735, we are supporting nested groups in ranger usersync. > For this, introduced one new property > "ranger.usersync.ldap.grouphierarchylevels". The value should be an integer > with default value as 0. This property should be under Ranger --> Configs --> > Ranger User Info --> Group Configs tab. > This property can be enabled with a flag labelled as "Sync Nested Groups". > 1. Default value for this flag is "No" > 2. This flag is always shown under Group Configs (even when "Enable group > Sync" is set to "No") > 3. If this flag is set to "No", then the value for > ranger.usersync.ldap.grouphierarchylevels is hidden and is set to "0". > 4. If this flag is set to "Yes", then > ranger.usersync.ldap.grouphierarchylevels is shown and allowed to set any > integer greater than 0. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21910) Ranger Usersync config to support nested group evaluation for LDAP Sync source property
[ https://issues.apache.org/jira/browse/AMBARI-21910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-21910: - Description: As part of RANGER-1735, we are supporting nested groups in ranger usersync. For this, introduced one new property "ranger.usersync.ldap.grouphierarchylevels". The value should be an integer with default value as 0. This property should be under Ranger --> Configs --> Ranger User Info --> Group Configs tab. This property can be enabled with a flag labelled as "Sync Nested Groups". 1. Default value for this flag is "No" 2. This flag is always shown under Group Configs (even when "Enable group Sync" is set to "No") 3. If this flag is set to "No", then the value for ranger.usersync.ldap.grouphierarchylevels is hidden and is set to "0". 4. If this flag is set to "Yes", then ranger.usersync.ldap.grouphierarchylevels is shown and allowed to set any integer greater than 0. was: As part of RANGER-1735, we are supporting nested groups in ranger usersync. For this I introduced one new property "ranger.usersync.ldap.grouphierarchylevels". The value should be an integer with default value as 0. This property should be under Ranger --> Configs --> Ranger User Info --> Group Configs tab. This property can be enabled with a flag labelled as "Sync Nested Groups". 1. Default value for this flag is "No" 2. This flag is always shown under Group Configs (even when "Enable group Sync" is set to "No") 3. If this flag is set to "No", then the value for ranger.usersync.ldap.grouphierarchylevels is hidden and is set to "0". 4. If this flag is set to "Yes", then ranger.usersync.ldap.grouphierarchylevels is shown and allowed to set any integer greater than 0. > Ranger Usersync config to support nested group evaluation for LDAP Sync > source property > --- > > Key: AMBARI-21910 > URL: https://issues.apache.org/jira/browse/AMBARI-21910 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.0 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-21910.patch > > > As part of RANGER-1735, we are supporting nested groups in ranger usersync. > For this, introduced one new property > "ranger.usersync.ldap.grouphierarchylevels". The value should be an integer > with default value as 0. This property should be under Ranger --> Configs --> > Ranger User Info --> Group Configs tab. > This property can be enabled with a flag labelled as "Sync Nested Groups". > 1. Default value for this flag is "No" > 2. This flag is always shown under Group Configs (even when "Enable group > Sync" is set to "No") > 3. If this flag is set to "No", then the value for > ranger.usersync.ldap.grouphierarchylevels is hidden and is set to "0". > 4. If this flag is set to "Yes", then > ranger.usersync.ldap.grouphierarchylevels is shown and allowed to set any > integer greater than 0. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21910) Ranger Usersync config to support nested group evaluation for LDAP Sync source property
[ https://issues.apache.org/jira/browse/AMBARI-21910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-21910: - Attachment: AMBARI-21910.patch > Ranger Usersync config to support nested group evaluation for LDAP Sync > source property > --- > > Key: AMBARI-21910 > URL: https://issues.apache.org/jira/browse/AMBARI-21910 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.0 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-21910.patch > > > As part of RANGER-1735, we are supporting nested groups in ranger usersync. > For this I introduced one new property > "ranger.usersync.ldap.grouphierarchylevels". The value should be an integer > with default value as 0. This property should be under Ranger --> Configs --> > Ranger User Info --> Group Configs tab. > This property can be enabled with a flag labelled as "Sync Nested Groups". > 1. Default value for this flag is "No" > 2. This flag is always shown under Group Configs (even when "Enable group > Sync" is set to "No") > 3. If this flag is set to "No", then the value for > ranger.usersync.ldap.grouphierarchylevels is hidden and is set to "0". > 4. If this flag is set to "Yes", then > ranger.usersync.ldap.grouphierarchylevels is shown and allowed to set any > integer greater than 0. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21904) Remove redundant smokeuser entry from Ranger KMS Kerberos descriptor
[ https://issues.apache.org/jira/browse/AMBARI-21904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-21904: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.6: 77786e4c74b1d43fc1449a1eb93262ef45ff757d and trunk: a05947873b39d646575e6568e9b7cd086a10fac3 > Remove redundant smokeuser entry from Ranger KMS Kerberos descriptor > > > Key: AMBARI-21904 > URL: https://issues.apache.org/jira/browse/AMBARI-21904 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.1.0 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Critical > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-21904-branch-2.6.patch, AMBARI-21904-trunk.patch > > > /smokeuser entry in RANGER_KMS_SERVER component section is not needed. It > wont break anything, but it is redundant and should eventually be removed. > (Feedback from review request - https://reviews.apache.org/r/34561/) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21889) MaxBackupIndex does not work with DailyRollingFileAppender in Ranger
[ https://issues.apache.org/jira/browse/AMBARI-21889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-21889: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.6: af16726a920ec2d540e817d7c11546ebe824ac2d and trunk: b7f53dc8c516ba148cdb59577baf3db9b29d538b > MaxBackupIndex does not work with DailyRollingFileAppender in Ranger > > > Key: AMBARI-21889 > URL: https://issues.apache.org/jira/browse/AMBARI-21889 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar > Fix For: 2.6.0 > > Attachments: AMBARI-21889.patch, AMBARI-21889-trunk.patch > > > Ranger uses DailyRollingFileAppender and "maxbackupindex" is not in that > class so need to remove the same from admin-log4j config. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21889) MaxBackupIndex does not work with DailyRollingFileAppender in Ranger
[ https://issues.apache.org/jira/browse/AMBARI-21889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-21889: - Attachment: AMBARI-21889-trunk.patch > MaxBackupIndex does not work with DailyRollingFileAppender in Ranger > > > Key: AMBARI-21889 > URL: https://issues.apache.org/jira/browse/AMBARI-21889 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar > Fix For: 2.6.0 > > Attachments: AMBARI-21889.patch, AMBARI-21889-trunk.patch > > > Ranger uses DailyRollingFileAppender and "maxbackupindex" is not in that > class so need to remove the same from admin-log4j config. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21904) Remove redundant smokeuser entry from Ranger KMS Kerberos descriptor
[ https://issues.apache.org/jira/browse/AMBARI-21904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-21904: - Status: Patch Available (was: In Progress) > Remove redundant smokeuser entry from Ranger KMS Kerberos descriptor > > > Key: AMBARI-21904 > URL: https://issues.apache.org/jira/browse/AMBARI-21904 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.1.0 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Critical > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-21904-branch-2.6.patch, AMBARI-21904-trunk.patch > > > /smokeuser entry in RANGER_KMS_SERVER component section is not needed. It > wont break anything, but it is redundant and should eventually be removed. > (Feedback from review request - https://reviews.apache.org/r/34561/) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21904) Remove redundant smokeuser entry from Ranger KMS Kerberos descriptor
[ https://issues.apache.org/jira/browse/AMBARI-21904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-21904: - Fix Version/s: trunk > Remove redundant smokeuser entry from Ranger KMS Kerberos descriptor > > > Key: AMBARI-21904 > URL: https://issues.apache.org/jira/browse/AMBARI-21904 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.1.0 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Critical > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-21904-branch-2.6.patch, AMBARI-21904-trunk.patch > > > /smokeuser entry in RANGER_KMS_SERVER component section is not needed. It > wont break anything, but it is redundant and should eventually be removed. > (Feedback from review request - https://reviews.apache.org/r/34561/) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21904) Remove redundant smokeuser entry from Ranger KMS Kerberos descriptor
[ https://issues.apache.org/jira/browse/AMBARI-21904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-21904: - Attachment: AMBARI-21904-branch-2.6.patch AMBARI-21904-trunk.patch > Remove redundant smokeuser entry from Ranger KMS Kerberos descriptor > > > Key: AMBARI-21904 > URL: https://issues.apache.org/jira/browse/AMBARI-21904 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.1.0 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21904-branch-2.6.patch, AMBARI-21904-trunk.patch > > > /smokeuser entry in RANGER_KMS_SERVER component section is not needed. It > wont break anything, but it is redundant and should eventually be removed. > (Feedback from review request - https://reviews.apache.org/r/34561/) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21904) Remove redundant smokeuser entry from Ranger KMS Kerberos descriptor
[ https://issues.apache.org/jira/browse/AMBARI-21904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-21904: - Attachment: (was: AMBARI-21904-branch-2.6.patch) > Remove redundant smokeuser entry from Ranger KMS Kerberos descriptor > > > Key: AMBARI-21904 > URL: https://issues.apache.org/jira/browse/AMBARI-21904 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.1.0 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Critical > Fix For: 2.6.0 > > > /smokeuser entry in RANGER_KMS_SERVER component section is not needed. It > wont break anything, but it is redundant and should eventually be removed. > (Feedback from review request - https://reviews.apache.org/r/34561/) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21910) Ranger Usersync config to support nested group evaluation for LDAP Sync source property
[ https://issues.apache.org/jira/browse/AMBARI-21910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-21910: - Fix Version/s: 2.6.0 trunk > Ranger Usersync config to support nested group evaluation for LDAP Sync > source property > --- > > Key: AMBARI-21910 > URL: https://issues.apache.org/jira/browse/AMBARI-21910 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.0 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar > Fix For: trunk, 2.6.0 > > > As part of RANGER-1735, we are supporting nested groups in ranger usersync. > For this I introduced one new property > "ranger.usersync.ldap.grouphierarchylevels". The value should be an integer > with default value as 0. This property should be under Ranger --> Configs --> > Ranger User Info --> Group Configs tab. > This property can be enabled with a flag labelled as "Sync Nested Groups". > 1. Default value for this flag is "No" > 2. This flag is always shown under Group Configs (even when "Enable group > Sync" is set to "No") > 3. If this flag is set to "No", then the value for > ranger.usersync.ldap.grouphierarchylevels is hidden and is set to "0". > 4. If this flag is set to "Yes", then > ranger.usersync.ldap.grouphierarchylevels is shown and allowed to set any > integer greater than 0. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21910) Ranger Usersync config to support nested group evaluation for LDAP Sync source property
[ https://issues.apache.org/jira/browse/AMBARI-21910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-21910: - Affects Version/s: (was: trunk) > Ranger Usersync config to support nested group evaluation for LDAP Sync > source property > --- > > Key: AMBARI-21910 > URL: https://issues.apache.org/jira/browse/AMBARI-21910 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.0 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar > Fix For: trunk, 2.6.0 > > > As part of RANGER-1735, we are supporting nested groups in ranger usersync. > For this I introduced one new property > "ranger.usersync.ldap.grouphierarchylevels". The value should be an integer > with default value as 0. This property should be under Ranger --> Configs --> > Ranger User Info --> Group Configs tab. > This property can be enabled with a flag labelled as "Sync Nested Groups". > 1. Default value for this flag is "No" > 2. This flag is always shown under Group Configs (even when "Enable group > Sync" is set to "No") > 3. If this flag is set to "No", then the value for > ranger.usersync.ldap.grouphierarchylevels is hidden and is set to "0". > 4. If this flag is set to "Yes", then > ranger.usersync.ldap.grouphierarchylevels is shown and allowed to set any > integer greater than 0. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21910) Ranger Usersync config to support nested group evaluation for LDAP Sync source property
Mugdha Varadkar created AMBARI-21910: Summary: Ranger Usersync config to support nested group evaluation for LDAP Sync source property Key: AMBARI-21910 URL: https://issues.apache.org/jira/browse/AMBARI-21910 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: trunk, 2.6.0 Reporter: Mugdha Varadkar Assignee: Mugdha Varadkar As part of RANGER-1735, we are supporting nested groups in ranger usersync. For this I introduced one new property "ranger.usersync.ldap.grouphierarchylevels". The value should be an integer with default value as 0. This property should be under Ranger --> Configs --> Ranger User Info --> Group Configs tab. This property can be enabled with a flag labelled as "Sync Nested Groups". 1. Default value for this flag is "No" 2. This flag is always shown under Group Configs (even when "Enable group Sync" is set to "No") 3. If this flag is set to "No", then the value for ranger.usersync.ldap.grouphierarchylevels is hidden and is set to "0". 4. If this flag is set to "Yes", then ranger.usersync.ldap.grouphierarchylevels is shown and allowed to set any integer greater than 0. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21904) Remove redundant smokeuser entry from Ranger KMS Kerberos descriptor
[ https://issues.apache.org/jira/browse/AMBARI-21904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-21904: - Status: In Progress (was: Patch Available) > Remove redundant smokeuser entry from Ranger KMS Kerberos descriptor > > > Key: AMBARI-21904 > URL: https://issues.apache.org/jira/browse/AMBARI-21904 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.1.0 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21904-branch-2.6.patch > > > /smokeuser entry in RANGER_KMS_SERVER component section is not needed. It > wont break anything, but it is redundant and should eventually be removed. > (Feedback from review request - https://reviews.apache.org/r/34561/) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21904) Remove redundant smokeuser entry from Ranger KMS Kerberos descriptor
[ https://issues.apache.org/jira/browse/AMBARI-21904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-21904: - Attachment: AMBARI-21904-branch-2.6.patch > Remove redundant smokeuser entry from Ranger KMS Kerberos descriptor > > > Key: AMBARI-21904 > URL: https://issues.apache.org/jira/browse/AMBARI-21904 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.1.0 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21904-branch-2.6.patch > > > /smokeuser entry in RANGER_KMS_SERVER component section is not needed. It > wont break anything, but it is redundant and should eventually be removed. > (Feedback from review request - https://reviews.apache.org/r/34561/) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21904) Remove redundant smokeuser entry from Ranger KMS Kerberos descriptor
[ https://issues.apache.org/jira/browse/AMBARI-21904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-21904: - Attachment: (was: AMBARI-21904-branch_2.6.patch) > Remove redundant smokeuser entry from Ranger KMS Kerberos descriptor > > > Key: AMBARI-21904 > URL: https://issues.apache.org/jira/browse/AMBARI-21904 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.1.0 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21904-branch-2.6.patch > > > /smokeuser entry in RANGER_KMS_SERVER component section is not needed. It > wont break anything, but it is redundant and should eventually be removed. > (Feedback from review request - https://reviews.apache.org/r/34561/) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
