[jira] [Updated] (AMBARI-24403) [Ambari metrics][grafana] grafana is not showing any datapoints if the queue name contains special characters
[
https://issues.apache.org/jira/browse/AMBARI-24403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akhil S Naik updated AMBARI-24403:
--
Status: Patch Available (was: In Progress)
> [Ambari metrics][grafana] grafana is not showing any datapoints if the queue
> name contains special characters
> -
>
> Key: AMBARI-24403
> URL: https://issues.apache.org/jira/browse/AMBARI-24403
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.6.2
>Reporter: Akhil S Naik
>Assignee: Akhil S Naik
>Priority: Major
> Labels: pull-request-available
> Fix For: trunk, 2.7.1
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> grafana is not showing any data points if the queue name contains special
> characters
> I have a queue named 'A' , in Yarn queues dashboard if I select this queue
> name I am getting empty data showing no data points.
> The issue is reproducible
> Analysis :
> In grafana UI we are sending the request to fetch the data by encoding the
> URI.
> for which the server is interpreting it as separate parameters
> http://mygrafanaserver.com:3000/api/datasources/proxy/1/ws/v1/timeline/metrics?metricNames=yarn.QueueMetrics.Queue=root.{color:red}A{color}.AppsRunning._max=resourcemanager=1533181180=1533202780
> Which should ideally be :
> http://mygrafanaserver.com:3000/api/datasources/proxy/1/ws/v1/timeline/metrics?metricNames=yarn.QueueMetrics.Queue=root.{color:red}A%26B{color}.AppsRunning._max=resourcemanager
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24403) [Ambari metrics][grafana] grafana is not showing any datapoints if the queue name contains special characters
[
https://issues.apache.org/jira/browse/AMBARI-24403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akhil S Naik updated AMBARI-24403:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
> [Ambari metrics][grafana] grafana is not showing any datapoints if the queue
> name contains special characters
> -
>
> Key: AMBARI-24403
> URL: https://issues.apache.org/jira/browse/AMBARI-24403
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.6.2
>Reporter: Akhil S Naik
>Assignee: Akhil S Naik
>Priority: Major
> Labels: pull-request-available
> Fix For: trunk, 2.7.1
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> grafana is not showing any data points if the queue name contains special
> characters
> I have a queue named 'A' , in Yarn queues dashboard if I select this queue
> name I am getting empty data showing no data points.
> The issue is reproducible
> Analysis :
> In grafana UI we are sending the request to fetch the data by encoding the
> URI.
> for which the server is interpreting it as separate parameters
> http://mygrafanaserver.com:3000/api/datasources/proxy/1/ws/v1/timeline/metrics?metricNames=yarn.QueueMetrics.Queue=root.{color:red}A{color}.AppsRunning._max=resourcemanager=1533181180=1533202780
> Which should ideally be :
> http://mygrafanaserver.com:3000/api/datasources/proxy/1/ws/v1/timeline/metrics?metricNames=yarn.QueueMetrics.Queue=root.{color:red}A%26B{color}.AppsRunning._max=resourcemanager
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24406) Fix validate single sign-in support information to look for ssoEnabledTest
[
https://issues.apache.org/jira/browse/AMBARI-24406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16568756#comment-16568756
]
Hudson commented on AMBARI-24406:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.7 #107 (See
[https://builds.apache.org/job/Ambari-branch-2.7/107/])
[AMBARI-24406] Fix validate single sign-in support information to look (rlevas:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=cd75cf8003684bde4d7783db28446571a3ebd10f])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/ServiceInfo.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/stack/ServiceModuleTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/state/ServiceInfoTest.java
> Fix validate single sign-in support information to look for ssoEnabledTest
> --
>
> Key: AMBARI-24406
> URL: https://issues.apache.org/jira/browse/AMBARI-24406
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.1
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Fix validate single sign-in support information to look for
> {{ssoEnabledTest}}.
> The current test looks for the old {{enabledConfiguration}} value only.
> However {{ssoEnabledTest}} is the new way, leaving {{enabledConfiguration}}
> for backward compatibility.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24187) Ambari Server Setup LDAP Label Updates
[
https://issues.apache.org/jira/browse/AMBARI-24187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16568714#comment-16568714
]
Hudson commented on AMBARI-24187:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #106 (See
[https://builds.apache.org/job/Ambari-branch-2.7/106/])
AMBARI-24187 - Ambari Server Setup LDAP Label Updates (#1961) (github:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=abeba0a09df248212cb33bb61757782270f262f3])
* (edit) ambari-server/src/main/python/ambari_server/setupSecurity.py
* (edit) ambari-server/src/test/python/TestAmbariServer.py
* (edit) ambari-server/src/main/python/ambari_server/userInput.py
> Ambari Server Setup LDAP Label Updates
> --
>
> Key: AMBARI-24187
> URL: https://issues.apache.org/jira/browse/AMBARI-24187
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 3h 10m
> Remaining Estimate: 0h
>
> Ask users to select ldap type ( AD, IPA, generic ldap) and provide inteligent
> defaults based on their choice:
> Active Directory
> {code:java}
> # ambari-server setup-ldap
> Using python /usr/bin/python
> Currently 'no auth method' is configured, do you wish to use LDAP instead
> [y/n] (y)?
> Primary LDAP Host:
> Primary LDAP Port:
> Secondary LDAP Host :
> Secondary LDAP Port :
> Use SSL [true/false] (false):
> User object class (user):
> User ID attribute (sAMAccountName):
> Group object class (group):
> Group name attribute (cn):
> Group member attribute (member):
> Distinguished name attribute (distinguishedName):
> Search Base (dc=ambari,dc=apache,dc=org):
> User Search Base (ou=users,dc=ambari,dc=apache,dc=org):
> Group Search Base (ou=groups,dc=ambari,dc=apache,dc=org):
> Referral method [follow/ignore] (follow):
> Bind anonymously [true/false] (false):
> Bind DN (cn=ldapbind,dc=ambari,dc=apache,dc=org):
> Enter Bind DN Password:
> Confirm Bind DN Password:
> Handling behavior for username collisions [convert/skip] for LDAP sync
> (skip):
> Force lower-case user names [true/false] (true):
> Results from LDAP are paginated when requested [true/false] (false):
> {code}
> IPA (very similar to generic ldap, but needs explicit search customization
> into cn=accounts (or cn=compat) else it returns 2 search results which tends
> to cause problems)
> {code:java}
> {code:java}
> # ambari-server setup-ldap
> Using python /usr/bin/python
> Currently 'no auth method' is configured, do you wish to use LDAP instead
> [y/n] (y)?
> Primary LDAP Host (ipa.ambari.apache.org):
> Primary LDAP Port (636):
> Secondary LDAP Host :
> Secondary LDAP Port :
> Use SSL [true/false] (true):
> Do you want to provide custom TrustStore for Ambari [y/n] (y)?
> TrustStore type [jks/jceks/pkcs12] (jks):
> Path to TrustStore file (/etc/pki/java/cacerts):
> Password for TrustStore (changeit):
> User object class (posixUser):
> User ID attribute (uid):
> Group object class (posixGroup):
> Group name attribute (cn):
> Group member attribute (memberUid):
> Distinguished name attribute (dn):
> Search Base (dc=ambari,dc=apache,dc=org):
> User Search Base (cn=users,cn=accounts,dc=ambari,dc=apache,dc=org):
> Group Search Base (cn=groups,cn=accounts,dc=ambari,dc=apache,dc=org):
> Referral method [follow/ignore] (follow):
> Bind anonymously [true/false] (false):
> Bind DN ( uid=ldapbind,cn=users,cn=accounts,dc=ambari,dc=apache,dc=org):
> Enter Bind DN Password:
> Confirm Bind DN Password:
> Handling behavior for username collisions [convert/skip] for LDAP sync
> (skip):
> {code}
> Generic LDAP (defaults here need validation, i'm not as familiar with this
> one)
> {code:java}
> # ambari-server setup-ldap
> Using python /usr/bin/python
> Currently 'no auth method' is configured, do you wish to use LDAP instead
> [y/n] (y)?
> Primary LDAP Host (ldap.ambari.apache.org):
> Primary LDAP Port (389):
> Secondary LDAP Host :
> Secondary LDAP Port :
> Use SSL [true/false] (false):
> Do you want to provide custom TrustStore for Ambari [y/n] (n)?
> User object class (posixUser):
> User ID attribute (uid):
> Group object class (posixGroup):
> Group name attribute (cn):
> Group member attribute (memberUid):
> Distinguished name attribute (dn):
> Search Base (dc=ambari,dc=apache,dc=org):
> User Search Base (cn=users,dc=ambari,dc=apache,dc=org):
> Group Search Base (cn=groups,dc=ambari,dc=apache,dc=org):
> Referral method [follow/ignore] (follow):
> Bind anonymously [true/false] (false):
> Bind DN ( uid=ldapbind,cn=users,dc=ambari,dc=apache,dc=org):
> Enter Bind DN Password:
> Confirm Bind DN Password:
> Handling behavior for username collisions
[jira] [Resolved] (AMBARI-24406) Fix validate single sign-in support information to look for ssoEnabledTest
[
https://issues.apache.org/jira/browse/AMBARI-24406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas resolved AMBARI-24406.
---
Resolution: Fixed
> Fix validate single sign-in support information to look for ssoEnabledTest
> --
>
> Key: AMBARI-24406
> URL: https://issues.apache.org/jira/browse/AMBARI-24406
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.1
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Fix validate single sign-in support information to look for
> {{ssoEnabledTest}}.
> The current test looks for the old {{enabledConfiguration}} value only.
> However {{ssoEnabledTest}} is the new way, leaving {{enabledConfiguration}}
> for backward compatibility.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24401) Ambari doesn't replace Timeline Reader localhost address with corresponding host in fresh and upgrade installation
[ https://issues.apache.org/jira/browse/AMBARI-24401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Magyar resolved AMBARI-24401. Resolution: Fixed > Ambari doesn't replace Timeline Reader localhost address with corresponding > host in fresh and upgrade installation > -- > > Key: AMBARI-24401 > URL: https://issues.apache.org/jira/browse/AMBARI-24401 > Project: Ambari > Issue Type: Bug > Components: ambari-server, service-advisor >Affects Versions: 2.7.1 >Reporter: Attila Magyar >Assignee: Attila Magyar >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 1h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24406) Fix validate single sign-in support information to look for ssoEnabledTest
[
https://issues.apache.org/jira/browse/AMBARI-24406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16568594#comment-16568594
]
Hudson commented on AMBARI-24406:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9726 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/9726/])
[AMBARI-24406] Fix validate single sign-in support information to look (rlevas:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=e15850f8b21ff0eab3439488171d04424a5a0936])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/ServiceInfo.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/state/ServiceInfoTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/stack/ServiceModuleTest.java
> Fix validate single sign-in support information to look for ssoEnabledTest
> --
>
> Key: AMBARI-24406
> URL: https://issues.apache.org/jira/browse/AMBARI-24406
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.1
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Fix validate single sign-in support information to look for
> {{ssoEnabledTest}}.
> The current test looks for the old {{enabledConfiguration}} value only.
> However {{ssoEnabledTest}} is the new way, leaving {{enabledConfiguration}}
> for backward compatibility.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24403) [Ambari metrics][grafana] grafana is not showing any datapoints if the queue name contains special characters
[
https://issues.apache.org/jira/browse/AMBARI-24403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16568524#comment-16568524
]
Hudson commented on AMBARI-24403:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9725 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/9725/])
AMBARI-24403 grafana is not showing any datapoints if the queue name (avijayan:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=06266815fe8b18ac72a2b63d042d8ad603d9f40d])
* (edit) ambari-metrics/ambari-metrics-grafana/ambari-metrics/datasource.js
> [Ambari metrics][grafana] grafana is not showing any datapoints if the queue
> name contains special characters
> -
>
> Key: AMBARI-24403
> URL: https://issues.apache.org/jira/browse/AMBARI-24403
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.6.2
>Reporter: Akhil S Naik
>Assignee: Akhil S Naik
>Priority: Major
> Labels: pull-request-available
> Fix For: trunk, 2.7.1
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> grafana is not showing any data points if the queue name contains special
> characters
> I have a queue named 'A' , in Yarn queues dashboard if I select this queue
> name I am getting empty data showing no data points.
> The issue is reproducible
> Analysis :
> In grafana UI we are sending the request to fetch the data by encoding the
> URI.
> for which the server is interpreting it as separate parameters
> http://mygrafanaserver.com:3000/api/datasources/proxy/1/ws/v1/timeline/metrics?metricNames=yarn.QueueMetrics.Queue=root.{color:red}A{color}.AppsRunning._max=resourcemanager=1533181180=1533202780
> Which should ideally be :
> http://mygrafanaserver.com:3000/api/datasources/proxy/1/ws/v1/timeline/metrics?metricNames=yarn.QueueMetrics.Queue=root.{color:red}A%26B{color}.AppsRunning._max=resourcemanager
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24403) [Ambari metrics][grafana] grafana is not showing any datapoints if the queue name contains special characters
[
https://issues.apache.org/jira/browse/AMBARI-24403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16568507#comment-16568507
]
Hudson commented on AMBARI-24403:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #105 (See
[https://builds.apache.org/job/Ambari-branch-2.7/105/])
AMBARI-24403 grafana is not showing any datapoints if the queue name (avijayan:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=a822a365c35b51146f8d08b15180bb7ccd6a5979])
* (edit) ambari-metrics/ambari-metrics-grafana/ambari-metrics/datasource.js
> [Ambari metrics][grafana] grafana is not showing any datapoints if the queue
> name contains special characters
> -
>
> Key: AMBARI-24403
> URL: https://issues.apache.org/jira/browse/AMBARI-24403
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.6.2
>Reporter: Akhil S Naik
>Assignee: Akhil S Naik
>Priority: Major
> Labels: pull-request-available
> Fix For: trunk, 2.7.1
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> grafana is not showing any data points if the queue name contains special
> characters
> I have a queue named 'A' , in Yarn queues dashboard if I select this queue
> name I am getting empty data showing no data points.
> The issue is reproducible
> Analysis :
> In grafana UI we are sending the request to fetch the data by encoding the
> URI.
> for which the server is interpreting it as separate parameters
> http://mygrafanaserver.com:3000/api/datasources/proxy/1/ws/v1/timeline/metrics?metricNames=yarn.QueueMetrics.Queue=root.{color:red}A{color}.AppsRunning._max=resourcemanager=1533181180=1533202780
> Which should ideally be :
> http://mygrafanaserver.com:3000/api/datasources/proxy/1/ws/v1/timeline/metrics?metricNames=yarn.QueueMetrics.Queue=root.{color:red}A%26B{color}.AppsRunning._max=resourcemanager
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24403) [Ambari metrics][grafana] grafana is not showing any datapoints if the queue name contains special characters
[
https://issues.apache.org/jira/browse/AMBARI-24403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-24403:
---
Fix Version/s: 2.7.1
> [Ambari metrics][grafana] grafana is not showing any datapoints if the queue
> name contains special characters
> -
>
> Key: AMBARI-24403
> URL: https://issues.apache.org/jira/browse/AMBARI-24403
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.6.2
>Reporter: Akhil S Naik
>Assignee: Akhil S Naik
>Priority: Major
> Labels: pull-request-available
> Fix For: trunk, 2.7.1
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> grafana is not showing any data points if the queue name contains special
> characters
> I have a queue named 'A' , in Yarn queues dashboard if I select this queue
> name I am getting empty data showing no data points.
> The issue is reproducible
> Analysis :
> In grafana UI we are sending the request to fetch the data by encoding the
> URI.
> for which the server is interpreting it as separate parameters
> http://mygrafanaserver.com:3000/api/datasources/proxy/1/ws/v1/timeline/metrics?metricNames=yarn.QueueMetrics.Queue=root.{color:red}A{color}.AppsRunning._max=resourcemanager=1533181180=1533202780
> Which should ideally be :
> http://mygrafanaserver.com:3000/api/datasources/proxy/1/ws/v1/timeline/metrics?metricNames=yarn.QueueMetrics.Queue=root.{color:red}A%26B{color}.AppsRunning._max=resourcemanager
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24403) [Ambari metrics][grafana] grafana is not showing any datapoints if the queue name contains special characters
[
https://issues.apache.org/jira/browse/AMBARI-24403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-24403:
---
Fix Version/s: trunk
> [Ambari metrics][grafana] grafana is not showing any datapoints if the queue
> name contains special characters
> -
>
> Key: AMBARI-24403
> URL: https://issues.apache.org/jira/browse/AMBARI-24403
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.6.2
>Reporter: Akhil S Naik
>Assignee: Akhil S Naik
>Priority: Major
> Labels: pull-request-available
> Fix For: trunk
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> grafana is not showing any data points if the queue name contains special
> characters
> I have a queue named 'A' , in Yarn queues dashboard if I select this queue
> name I am getting empty data showing no data points.
> The issue is reproducible
> Analysis :
> In grafana UI we are sending the request to fetch the data by encoding the
> URI.
> for which the server is interpreting it as separate parameters
> http://mygrafanaserver.com:3000/api/datasources/proxy/1/ws/v1/timeline/metrics?metricNames=yarn.QueueMetrics.Queue=root.{color:red}A{color}.AppsRunning._max=resourcemanager=1533181180=1533202780
> Which should ideally be :
> http://mygrafanaserver.com:3000/api/datasources/proxy/1/ws/v1/timeline/metrics?metricNames=yarn.QueueMetrics.Queue=root.{color:red}A%26B{color}.AppsRunning._max=resourcemanager
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24406) Fix validate single sign-in support information to look for ssoEnabledTest
[
https://issues.apache.org/jira/browse/AMBARI-24406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-24406:
Labels: pull-request-available (was: )
> Fix validate single sign-in support information to look for ssoEnabledTest
> --
>
> Key: AMBARI-24406
> URL: https://issues.apache.org/jira/browse/AMBARI-24406
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.1
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.1
>
>
> Fix validate single sign-in support information to look for
> {{ssoEnabledTest}}.
> The current test looks for the old {{enabledConfiguration}} value only.
> However {{ssoEnabledTest}} is the new way, leaving {{enabledConfiguration}}
> for backward compatibility.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24187) Ambari Server Setup LDAP Label Updates
[
https://issues.apache.org/jira/browse/AMBARI-24187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16568308#comment-16568308
]
Hudson commented on AMBARI-24187:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9724 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/9724/])
AMBARI-24187 - Ambari Server Setup LDAP Label Updates (#1950) (github:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=d066e970207c9e3774b15df448b30291625bde7e])
* (edit) ambari-server/src/main/python/ambari_server/userInput.py
* (edit) ambari-server/src/main/python/ambari_server/setupSecurity.py
* (edit) ambari-server/src/test/python/TestAmbariServer.py
> Ambari Server Setup LDAP Label Updates
> --
>
> Key: AMBARI-24187
> URL: https://issues.apache.org/jira/browse/AMBARI-24187
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> Ask users to select ldap type ( AD, IPA, generic ldap) and provide inteligent
> defaults based on their choice:
> Active Directory
> {code:java}
> # ambari-server setup-ldap
> Using python /usr/bin/python
> Currently 'no auth method' is configured, do you wish to use LDAP instead
> [y/n] (y)?
> Primary LDAP Host:
> Primary LDAP Port:
> Secondary LDAP Host :
> Secondary LDAP Port :
> Use SSL [true/false] (false):
> User object class (user):
> User ID attribute (sAMAccountName):
> Group object class (group):
> Group name attribute (cn):
> Group member attribute (member):
> Distinguished name attribute (distinguishedName):
> Search Base (dc=ambari,dc=apache,dc=org):
> User Search Base (ou=users,dc=ambari,dc=apache,dc=org):
> Group Search Base (ou=groups,dc=ambari,dc=apache,dc=org):
> Referral method [follow/ignore] (follow):
> Bind anonymously [true/false] (false):
> Bind DN (cn=ldapbind,dc=ambari,dc=apache,dc=org):
> Enter Bind DN Password:
> Confirm Bind DN Password:
> Handling behavior for username collisions [convert/skip] for LDAP sync
> (skip):
> Force lower-case user names [true/false] (true):
> Results from LDAP are paginated when requested [true/false] (false):
> {code}
> IPA (very similar to generic ldap, but needs explicit search customization
> into cn=accounts (or cn=compat) else it returns 2 search results which tends
> to cause problems)
> {code:java}
> {code:java}
> # ambari-server setup-ldap
> Using python /usr/bin/python
> Currently 'no auth method' is configured, do you wish to use LDAP instead
> [y/n] (y)?
> Primary LDAP Host (ipa.ambari.apache.org):
> Primary LDAP Port (636):
> Secondary LDAP Host :
> Secondary LDAP Port :
> Use SSL [true/false] (true):
> Do you want to provide custom TrustStore for Ambari [y/n] (y)?
> TrustStore type [jks/jceks/pkcs12] (jks):
> Path to TrustStore file (/etc/pki/java/cacerts):
> Password for TrustStore (changeit):
> User object class (posixUser):
> User ID attribute (uid):
> Group object class (posixGroup):
> Group name attribute (cn):
> Group member attribute (memberUid):
> Distinguished name attribute (dn):
> Search Base (dc=ambari,dc=apache,dc=org):
> User Search Base (cn=users,cn=accounts,dc=ambari,dc=apache,dc=org):
> Group Search Base (cn=groups,cn=accounts,dc=ambari,dc=apache,dc=org):
> Referral method [follow/ignore] (follow):
> Bind anonymously [true/false] (false):
> Bind DN ( uid=ldapbind,cn=users,cn=accounts,dc=ambari,dc=apache,dc=org):
> Enter Bind DN Password:
> Confirm Bind DN Password:
> Handling behavior for username collisions [convert/skip] for LDAP sync
> (skip):
> {code}
> Generic LDAP (defaults here need validation, i'm not as familiar with this
> one)
> {code:java}
> # ambari-server setup-ldap
> Using python /usr/bin/python
> Currently 'no auth method' is configured, do you wish to use LDAP instead
> [y/n] (y)?
> Primary LDAP Host (ldap.ambari.apache.org):
> Primary LDAP Port (389):
> Secondary LDAP Host :
> Secondary LDAP Port :
> Use SSL [true/false] (false):
> Do you want to provide custom TrustStore for Ambari [y/n] (n)?
> User object class (posixUser):
> User ID attribute (uid):
> Group object class (posixGroup):
> Group name attribute (cn):
> Group member attribute (memberUid):
> Distinguished name attribute (dn):
> Search Base (dc=ambari,dc=apache,dc=org):
> User Search Base (cn=users,dc=ambari,dc=apache,dc=org):
> Group Search Base (cn=groups,dc=ambari,dc=apache,dc=org):
> Referral method [follow/ignore] (follow):
> Bind anonymously [true/false] (false):
> Bind DN ( uid=ldapbind,cn=users,dc=ambari,dc=apache,dc=org):
> Enter Bind DN Password:
> Confirm Bind DN Password:
> Handling behavior for username collisions
[jira] [Commented] (AMBARI-24401) Ambari doesn't replace Timeline Reader localhost address with corresponding host in fresh and upgrade installation
[ https://issues.apache.org/jira/browse/AMBARI-24401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16568302#comment-16568302 ] Hudson commented on AMBARI-24401: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #104 (See [https://builds.apache.org/job/Ambari-branch-2.7/104/]) AMBARI-24401. Ambari doesn't replace Timeline Reader localhost address (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=1661b4e07ba0c37c608f8ef2c5f0e4e8028824a9]) * (add) ambari-server/src/main/java/org/apache/ambari/server/serveraction/upgrades/FixTimelineReaderAddress.java * (add) ambari-server/src/test/java/org/apache/ambari/server/serveraction/upgrades/FixTimelineReaderAddressTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/serveraction/upgrades/AbstractUpgradeServerAction.java > Ambari doesn't replace Timeline Reader localhost address with corresponding > host in fresh and upgrade installation > -- > > Key: AMBARI-24401 > URL: https://issues.apache.org/jira/browse/AMBARI-24401 > Project: Ambari > Issue Type: Bug > Components: ambari-server, service-advisor >Affects Versions: 2.7.1 >Reporter: Attila Magyar >Assignee: Attila Magyar >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 1h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24343) [LogSearch] Wrong (error) response format
[
https://issues.apache.org/jira/browse/AMBARI-24343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-24343:
Labels: pull-request-available (was: )
> [LogSearch] Wrong (error) response format
> -
>
> Key: AMBARI-24343
> URL: https://issues.apache.org/jira/browse/AMBARI-24343
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.7.1
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
>
> When I call the
> {noformat}
> /shipper/input/\{clusterName}/services/\{serviceName}
> {noformat}
> api endpoint with wrong json schema the backend responses with plain text
> body instead of json or empty body.
> For example:
> {code:json}
> {
> "input": [
> {
> "type": "zookeeper",
> "rowtype": "service",
> "path": "/var/log/zookeeper/zookeeper*.log"
> }
> ],
> "filter": [
> {
> "filter": "grok",
> "conditions": {
> "fieldss": {
> "type": [
> "zookeeper"
> ]
> }
> },
> "skipOnError": false,
> "deepExtract": false,
> "post_map_values": {
> "logtime": [
> {
> "map_date": {
> "target_date_pattern": "-MM-dd HH:mm:ss,SSS"
> }
> }
> ]
> },
> "log4j_format": "%d\{ISO8601} - %-5p [%t:%C\{1}@%L] - %m%n",
> "multiline_pattern": "^(%\{TIMESTAMP_ISO8601:logtime})",
> "message_pattern":
> "(?m)^%\{TIMESTAMP_ISO8601:logtime}%\{SPACE}-%\{SPACE}%\{LOGLEVEL:level}%\{SPACE}\\[%\{DATA:thread_name}\\@%\{INT:line_number}\\]%\{SPACE}-%\{SPACE}%\{GREEDYDATA:log_message}"
> }
> ]
> }
> {code}
> Where the `fieldss` is not a valid JSON key.
> The response plain text body:
> {code:javascript}
> Unrecognized field "fieldss" (class
> org.apache.ambari.logsearch.model.common.LSServerConditions), not marked as
> ignorable (one known property: "fields"])
> at [Source: UNKNOWN; line: -1, column: -1] (through reference chain:
> org.apache.ambari.logsearch.model.common.LSServerInputConfig["filter"]->org.apache.ambari.logsearch.model.common.LSServerFilterGrok["conditions"]->org.apache.ambari.logsearch.model.common.LSServerConditions["fieldss"])
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24406) Fix validate single sign-in support information to look for ssoEnabledTest
Robert Levas created AMBARI-24406:
-
Summary: Fix validate single sign-in support information to look
for ssoEnabledTest
Key: AMBARI-24406
URL: https://issues.apache.org/jira/browse/AMBARI-24406
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.1
Reporter: Robert Levas
Assignee: Robert Levas
Fix For: 2.7.1
Fix validate single sign-in support information to look for {{ssoEnabledTest}}.
The current test looks for the old {{enabledConfiguration}} value only. However
{{ssoEnabledTest}} is the new way, leaving {{enabledConfiguration}} for
backward compatibility.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24401) Ambari doesn't replace Timeline Reader localhost address with corresponding host in fresh and upgrade installation
[ https://issues.apache.org/jira/browse/AMBARI-24401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16568209#comment-16568209 ] Hudson commented on AMBARI-24401: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9720 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9720/]) AMBARI-24401. Ambari doesn't replace Timeline Reader localhost address (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=1a2b115b8f693dcda4df3e6d97d67547e801baa3]) * (add) ambari-server/src/main/java/org/apache/ambari/server/serveraction/upgrades/FixTimelineReaderAddress.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/serveraction/upgrades/AbstractUpgradeServerAction.java * (add) ambari-server/src/test/java/org/apache/ambari/server/serveraction/upgrades/FixTimelineReaderAddressTest.java > Ambari doesn't replace Timeline Reader localhost address with corresponding > host in fresh and upgrade installation > -- > > Key: AMBARI-24401 > URL: https://issues.apache.org/jira/browse/AMBARI-24401 > Project: Ambari > Issue Type: Bug > Components: ambari-server, service-advisor >Affects Versions: 2.7.1 >Reporter: Attila Magyar >Assignee: Attila Magyar >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24187) Ambari Server Setup LDAP Label Updates
[
https://issues.apache.org/jira/browse/AMBARI-24187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Krisztian Kasa updated AMBARI-24187:
Status: Patch Available (was: In Progress)
> Ambari Server Setup LDAP Label Updates
> --
>
> Key: AMBARI-24187
> URL: https://issues.apache.org/jira/browse/AMBARI-24187
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Ask users to select ldap type ( AD, IPA, generic ldap) and provide inteligent
> defaults based on their choice:
> Active Directory
> {code:java}
> # ambari-server setup-ldap
> Using python /usr/bin/python
> Currently 'no auth method' is configured, do you wish to use LDAP instead
> [y/n] (y)?
> Primary LDAP Host:
> Primary LDAP Port:
> Secondary LDAP Host :
> Secondary LDAP Port :
> Use SSL [true/false] (false):
> User object class (user):
> User ID attribute (sAMAccountName):
> Group object class (group):
> Group name attribute (cn):
> Group member attribute (member):
> Distinguished name attribute (distinguishedName):
> Search Base (dc=ambari,dc=apache,dc=org):
> User Search Base (ou=users,dc=ambari,dc=apache,dc=org):
> Group Search Base (ou=groups,dc=ambari,dc=apache,dc=org):
> Referral method [follow/ignore] (follow):
> Bind anonymously [true/false] (false):
> Bind DN (cn=ldapbind,dc=ambari,dc=apache,dc=org):
> Enter Bind DN Password:
> Confirm Bind DN Password:
> Handling behavior for username collisions [convert/skip] for LDAP sync
> (skip):
> Force lower-case user names [true/false] (true):
> Results from LDAP are paginated when requested [true/false] (false):
> {code}
> IPA (very similar to generic ldap, but needs explicit search customization
> into cn=accounts (or cn=compat) else it returns 2 search results which tends
> to cause problems)
> {code:java}
> {code:java}
> # ambari-server setup-ldap
> Using python /usr/bin/python
> Currently 'no auth method' is configured, do you wish to use LDAP instead
> [y/n] (y)?
> Primary LDAP Host (ipa.ambari.apache.org):
> Primary LDAP Port (636):
> Secondary LDAP Host :
> Secondary LDAP Port :
> Use SSL [true/false] (true):
> Do you want to provide custom TrustStore for Ambari [y/n] (y)?
> TrustStore type [jks/jceks/pkcs12] (jks):
> Path to TrustStore file (/etc/pki/java/cacerts):
> Password for TrustStore (changeit):
> User object class (posixUser):
> User ID attribute (uid):
> Group object class (posixGroup):
> Group name attribute (cn):
> Group member attribute (memberUid):
> Distinguished name attribute (dn):
> Search Base (dc=ambari,dc=apache,dc=org):
> User Search Base (cn=users,cn=accounts,dc=ambari,dc=apache,dc=org):
> Group Search Base (cn=groups,cn=accounts,dc=ambari,dc=apache,dc=org):
> Referral method [follow/ignore] (follow):
> Bind anonymously [true/false] (false):
> Bind DN ( uid=ldapbind,cn=users,cn=accounts,dc=ambari,dc=apache,dc=org):
> Enter Bind DN Password:
> Confirm Bind DN Password:
> Handling behavior for username collisions [convert/skip] for LDAP sync
> (skip):
> {code}
> Generic LDAP (defaults here need validation, i'm not as familiar with this
> one)
> {code:java}
> # ambari-server setup-ldap
> Using python /usr/bin/python
> Currently 'no auth method' is configured, do you wish to use LDAP instead
> [y/n] (y)?
> Primary LDAP Host (ldap.ambari.apache.org):
> Primary LDAP Port (389):
> Secondary LDAP Host :
> Secondary LDAP Port :
> Use SSL [true/false] (false):
> Do you want to provide custom TrustStore for Ambari [y/n] (n)?
> User object class (posixUser):
> User ID attribute (uid):
> Group object class (posixGroup):
> Group name attribute (cn):
> Group member attribute (memberUid):
> Distinguished name attribute (dn):
> Search Base (dc=ambari,dc=apache,dc=org):
> User Search Base (cn=users,dc=ambari,dc=apache,dc=org):
> Group Search Base (cn=groups,dc=ambari,dc=apache,dc=org):
> Referral method [follow/ignore] (follow):
> Bind anonymously [true/false] (false):
> Bind DN ( uid=ldapbind,cn=users,dc=ambari,dc=apache,dc=org):
> Enter Bind DN Password:
> Confirm Bind DN Password:
> Handling behavior for username collisions [convert/skip] for LDAP sync
> (skip):
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24299) [Yarn Queue Manager] Yarn Queue manager View is resetting value some properties that are not defined UI
[ https://issues.apache.org/jira/browse/AMBARI-24299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16568101#comment-16568101 ] Hudson commented on AMBARI-24299: - FAILURE: Integrated in Jenkins build Ambari-branch-2.7 #103 (See [https://builds.apache.org/job/Ambari-branch-2.7/103/]) AMBARI-24299 [Yarn Queue Manager] Yarn Queue manager View is resetting (venkatasairam.lanka: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=0af78ffee08e824822e7c46453bc7675358c5565]) * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/models/queue.js * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/templates/queue.hbs * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/serializers.js > [Yarn Queue Manager] Yarn Queue manager View is resetting value some > properties that are not defined UI > --- > > Key: AMBARI-24299 > URL: https://issues.apache.org/jira/browse/AMBARI-24299 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.6.2 >Reporter: Akhil S Naik >Assignee: Akhil S Naik >Priority: Major > Labels: pull-request-available > Time Spent: 1h 10m > Remaining Estimate: 0h > > Whene I add this properly in yarn scheduler > >>> yarn.scheduler.capacity.root.default.maximum-allocation-mb=2048 > >>> yarn.scheduler.capacity.root.default.maximum-allocation-vcores=4 > then restarting the required services and refreshing the queue scheduler at > this time properties are present. > But when I want to do some changes in YARN queue manager like adding a Child > Node, At this time it'll ask for saving and refresh, after that, I cannot see > this 2 properties. > So Ambari-Yarn-queue-manager view is resetting this configs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24403) [Ambari metrics][grafana] grafana is not showing any datapoints if the queue name contains special characters
[
https://issues.apache.org/jira/browse/AMBARI-24403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-24403:
Labels: pull-request-available (was: )
> [Ambari metrics][grafana] grafana is not showing any datapoints if the queue
> name contains special characters
> -
>
> Key: AMBARI-24403
> URL: https://issues.apache.org/jira/browse/AMBARI-24403
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.6.2
>Reporter: Akhil S Naik
>Assignee: Akhil S Naik
>Priority: Major
> Labels: pull-request-available
>
> grafana is not showing any data points if the queue name contains special
> characters
> I have a queue named 'A' , in Yarn queues dashboard if I select this queue
> name I am getting empty data showing no data points.
> The issue is reproducible
> Analysis :
> In grafana UI we are sending the request to fetch the data by encoding the
> URI.
> for which the server is interpreting it as separate parameters
> http://mygrafanaserver.com:3000/api/datasources/proxy/1/ws/v1/timeline/metrics?metricNames=yarn.QueueMetrics.Queue=root.{color:red}A{color}.AppsRunning._max=resourcemanager=1533181180=1533202780
> Which should ideally be :
> http://mygrafanaserver.com:3000/api/datasources/proxy/1/ws/v1/timeline/metrics?metricNames=yarn.QueueMetrics.Queue=root.{color:red}A%26B{color}.AppsRunning._max=resourcemanager
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24380) Ambari HBase Rolling Restart failed to check RegionServers restarted successfully, continued to take down rest of RegionServers!
[
https://issues.apache.org/jira/browse/AMBARI-24380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16567837#comment-16567837
]
Akhil S Naik commented on AMBARI-24380:
---
Hi,
I had a similar issue where In Ambari HBase configuration option I accidentally
changed HBASE_REGIONSERVER_OPTS to have -Xmn option of -Xmn4096mm - note the
extra m.
I then asked ambari to do rolling HBase restarts with 2 servers at a time and
tolerate upto 2 failures. But ambari did take down all of my servers stating
each operation of restarting region servers are successfully restarted but
actually it dont, I see alerts on ambari saying region servers not up.
additionaly i tried mannually i found its not keeping up and below is error
messsage
{code:java}
[root@aanaik4 ambari-metrics-monitor]#
/usr/hdp/current/hbase-regionserver/bin/hbase-daemon.sh --config
/usr/hdp/current/hbase-regionserver/conf start regionserver
starting regionserver, logging to
/var/log/hbase/hbase-root-regionserver-aanaik4.openstacklocal.out
Error: VM option 'G1NewSizePercent' is experimental and must be enabled via
-XX:+UnlockExperimentalVMOptions.
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. The program will exit.
{code}
Root cause :
Ambari is not checking whether PID is created or not . its just sending execute
command ( start region server) and making the task success.
code reference:
https://github.com/apache/ambari/blob/79cca1c7184f1661236971dac70d85a83fab6c11/ambari-server/src/main/resources/common-services/HBASE/2.0.0.3.0/package/scripts/hbase_service.py#L42
{code:java}
try:
Execute ( daemon_cmd,
not_if = no_op_test,
user = params.hbase_user
)
except:
show_logs(params.log_dir, params.hbase_user)
raise
{code}
I hope my issue and yours are same.
Both will be fixed if there is some tweak in this part of code.
> Ambari HBase Rolling Restart failed to check RegionServers restarted
> successfully, continued to take down rest of RegionServers!
>
>
> Key: AMBARI-24380
> URL: https://issues.apache.org/jira/browse/AMBARI-24380
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Hari Sekhon
>Priority: Critical
>
> Ambari rolling-restart of HBase RegionServers failed to detect that
> RegionServers were not coming back online, continued to take down the rest of
> the RegionServers in the cluster.
> Adding the following JVM tuning setting to HBASE_OPTS in hbase-env.sh
> template near the start of the options:
> {code:java}
> -XX:G1NewSizePercent=3{code}
> before the following option (which was set a couple options further along, it
> needs to go after this option):
> {code:java}
> -XX:+UnlockExperimentalVMOptions{code}
> This resulted in both HMaster and RegionServer startup failures, but Ambari
> did not detect that the RegionServers were not coming back online, and
> proceeded to take down the rest of the RegionServers.
> Ambari should have checked that the first RegionServer restarted successfully
> and stayed up for the default 120 second rolling window before moving on to
> the second RegionServer.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
