[jira] [Updated] (AMBARI-20381) User is not able to import workflows, coordinators and bundles
[
https://issues.apache.org/jira/browse/AMBARI-20381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Padma Priya Nagaraj updated AMBARI-20381:
-
Attachment: AMBARI-20381_trunk.patch
> User is not able to import workflows, coordinators and bundles
> --
>
> Key: AMBARI-20381
> URL: https://issues.apache.org/jira/browse/AMBARI-20381
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Supreeth Sharma
>Assignee: Padma Priya Nagaraj
>Priority: Blocker
> Labels: WFD, WFM
> Fix For: 2.5.0
>
> Attachments: AMBARI-20381_trunk.patch
>
>
> User is not able to import workflows, coordinators and bundles. Seeing below
> error in UI console.log
> {code}
> TypeError: Cannot read property 'workflow-app' of null
> at n.processWorkflowXml (oozie-designer-89dda89….js:9)
> at n.importWorkflow (oozie-designer-89dda89….js:9)
> at n.importWorkflowFromString (oozie-designer-89dda89….js:3)
> at n. (oozie-designer-89dda89….js:3)
> at y (vendor-b25c8db….js:19)
> at b (vendor-b25c8db….js:19)
> at g (vendor-b25c8db….js:19)
> at vendor-b25c8db….js:13
> at invoke (vendor-b25c8db….js:5)
> at n.flush (vendor-b25c8db….js:5)
> {code}
> Facing the same issue while importing the asset from hdfs as well.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20381) User is not able to import workflows, coordinators and bundles
[
https://issues.apache.org/jira/browse/AMBARI-20381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Padma Priya Nagaraj updated AMBARI-20381:
-
Status: Patch Available (was: Open)
> User is not able to import workflows, coordinators and bundles
> --
>
> Key: AMBARI-20381
> URL: https://issues.apache.org/jira/browse/AMBARI-20381
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Supreeth Sharma
>Assignee: Padma Priya Nagaraj
>Priority: Blocker
> Labels: WFD, WFM
> Fix For: 2.5.0
>
> Attachments: AMBARI-20381_trunk.patch
>
>
> User is not able to import workflows, coordinators and bundles. Seeing below
> error in UI console.log
> {code}
> TypeError: Cannot read property 'workflow-app' of null
> at n.processWorkflowXml (oozie-designer-89dda89….js:9)
> at n.importWorkflow (oozie-designer-89dda89….js:9)
> at n.importWorkflowFromString (oozie-designer-89dda89….js:3)
> at n. (oozie-designer-89dda89….js:3)
> at y (vendor-b25c8db….js:19)
> at b (vendor-b25c8db….js:19)
> at g (vendor-b25c8db….js:19)
> at vendor-b25c8db….js:13
> at invoke (vendor-b25c8db….js:5)
> at n.flush (vendor-b25c8db….js:5)
> {code}
> Facing the same issue while importing the asset from hdfs as well.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (AMBARI-20381) User is not able to import workflows, coordinators and bundles
[
https://issues.apache.org/jira/browse/AMBARI-20381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Padma Priya Nagaraj reassigned AMBARI-20381:
Assignee: Padma Priya Nagaraj
> User is not able to import workflows, coordinators and bundles
> --
>
> Key: AMBARI-20381
> URL: https://issues.apache.org/jira/browse/AMBARI-20381
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Supreeth Sharma
>Assignee: Padma Priya Nagaraj
>Priority: Blocker
> Labels: WFD, WFM
> Fix For: 2.5.0
>
>
> User is not able to import workflows, coordinators and bundles. Seeing below
> error in UI console.log
> {code}
> TypeError: Cannot read property 'workflow-app' of null
> at n.processWorkflowXml (oozie-designer-89dda89….js:9)
> at n.importWorkflow (oozie-designer-89dda89….js:9)
> at n.importWorkflowFromString (oozie-designer-89dda89….js:3)
> at n. (oozie-designer-89dda89….js:3)
> at y (vendor-b25c8db….js:19)
> at b (vendor-b25c8db….js:19)
> at g (vendor-b25c8db….js:19)
> at vendor-b25c8db….js:13
> at invoke (vendor-b25c8db….js:5)
> at n.flush (vendor-b25c8db….js:5)
> {code}
> Facing the same issue while importing the asset from hdfs as well.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20290) null in heapmap page
[
https://issues.apache.org/jira/browse/AMBARI-20290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangxiaolu updated AMBARI-20290:
-
Attachment: screenshot-3.png
> null in heapmap page
>
>
> Key: AMBARI-20290
> URL: https://issues.apache.org/jira/browse/AMBARI-20290
> Project: Ambari
> Issue Type: Bug
>Affects Versions: trunk, 2.4.0, 2.5.0
>Reporter: zhangxiaolu
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-20290.patch, screenshot-1.png, screenshot-2.png,
> screenshot-3.png
>
>
> drawWidget: function () {
> if (this.get('isLoaded')) {
> var hostToValueMap = this.calculateValues();
> var hostNames = [];
> if (this.get('racks').everyProperty('isLoaded', true)) {
> this.get('racks').forEach(function (rack) {
> hostNames = hostNames.concat(rack.hosts.mapProperty('hostName'));
> });
> }
> var metricObject = App.MainChartHeatmapMetric.create({
> name: this.get('content.displayName'),
> units: this.get('content.properties.display_unit'),
> maximumValue: this.get('controller.inputMaximum'),
> hostNames: hostNames,
> hostToValueMap: hostToValueMap
> });
> this.set('controller.selectedMetric', metricObject);
> App.loadTimer.finish('Heatmaps Page');
> App.loadTimer.finish('Service Heatmaps Page');
> }
> }.observes('racks.@each.isLoaded'),
> as loaded like top:
> this.get('content.displayName') is always null
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20290) null in heapmap page
[
https://issues.apache.org/jira/browse/AMBARI-20290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangxiaolu updated AMBARI-20290:
-
Affects Version/s: 2.5.0
2.4.0
Fix Version/s: 2.5.0
> null in heapmap page
>
>
> Key: AMBARI-20290
> URL: https://issues.apache.org/jira/browse/AMBARI-20290
> Project: Ambari
> Issue Type: Bug
>Affects Versions: trunk, 2.4.0, 2.5.0
>Reporter: zhangxiaolu
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-20290.patch, screenshot-1.png, screenshot-2.png
>
>
> drawWidget: function () {
> if (this.get('isLoaded')) {
> var hostToValueMap = this.calculateValues();
> var hostNames = [];
> if (this.get('racks').everyProperty('isLoaded', true)) {
> this.get('racks').forEach(function (rack) {
> hostNames = hostNames.concat(rack.hosts.mapProperty('hostName'));
> });
> }
> var metricObject = App.MainChartHeatmapMetric.create({
> name: this.get('content.displayName'),
> units: this.get('content.properties.display_unit'),
> maximumValue: this.get('controller.inputMaximum'),
> hostNames: hostNames,
> hostToValueMap: hostToValueMap
> });
> this.set('controller.selectedMetric', metricObject);
> App.loadTimer.finish('Heatmaps Page');
> App.loadTimer.finish('Service Heatmaps Page');
> }
> }.observes('racks.@each.isLoaded'),
> as loaded like top:
> this.get('content.displayName') is always null
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20369) Need hdfs-site for saving ranger audits to hdfs in namenode HA env
[
https://issues.apache.org/jira/browse/AMBARI-20369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-20369:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to branch-2.5:
[bf4edcd76b4e78e0a90455fc8d56c053683ad1ba|https://github.com/apache/ambari/commit/bf4edcd76b4e78e0a90455fc8d56c053683ad1ba]
and trunk:
[b4da19ea0b1bf87d5b91ad0520b822f00da26ab8|https://github.com/apache/ambari/commit/b4da19ea0b1bf87d5b91ad0520b822f00da26ab8]
> Need hdfs-site for saving ranger audits to hdfs in namenode HA env
> --
>
> Key: AMBARI-20369
> URL: https://issues.apache.org/jira/browse/AMBARI-20369
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
> Labels: Ambari
> Fix For: 2.5.0
>
> Attachments: AMBARI-20369.patch
>
>
> For {{KNOX}} and {{RANGER_KMS}} services which supports ranger plugin, need
> to have hdfs-site.xml available in respective services conf directory for
> saving ranger audits to hdfs in namenode HA env.
> Below error logs are found, if hdfs-site.xml is not available,
> {noformat}
> 2017-03-01 18:48:50,150 ERROR provider.BaseAuditHandler
> (BaseAuditHandler.java:logError(327)) - Error writing to log file.
> java.lang.IllegalArgumentException: java.net.UnknownHostException: mycluster
> at
> org.apache.hadoop.security.SecurityUtil.buildTokenService(SecurityUtil.java:438)
> at
> org.apache.hadoop.hdfs.NameNodeProxies.createNonHAProxy(NameNodeProxies.java:311)
> at
> org.apache.hadoop.hdfs.NameNodeProxies.createProxy(NameNodeProxies.java:176)
> at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:690)
> at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:631)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem.initialize(DistributedFileSystem.java:160)
> at
> org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2795)
> at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:99)
> at
> org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2829)
> at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:2811)
> at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:390)
> at
> org.apache.ranger.audit.destination.HDFSAuditDestination.getLogFileStream(HDFSAuditDestination.java:271)
> at
> org.apache.ranger.audit.destination.HDFSAuditDestination.access$000(HDFSAuditDestination.java:43)
> at
> org.apache.ranger.audit.destination.HDFSAuditDestination$1.run(HDFSAuditDestination.java:157)
> at
> org.apache.ranger.audit.destination.HDFSAuditDestination$1.run(HDFSAuditDestination.java:154)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1866)
> at
> org.apache.ranger.audit.provider.MiscUtil.executePrivilegedAction(MiscUtil.java:523)
> at
> org.apache.ranger.audit.destination.HDFSAuditDestination.logJSON(HDFSAuditDestination.java:154)
> at
> org.apache.ranger.audit.queue.AuditFileSpool.sendEvent(AuditFileSpool.java:880)
> at
> org.apache.ranger.audit.queue.AuditFileSpool.runLogAudit(AuditFileSpool.java:828)
> at
> org.apache.ranger.audit.queue.AuditFileSpool.run(AuditFileSpool.java:758)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.net.UnknownHostException: mycluster
> ... 24 more
> 2017-03-01 18:48:50,151 ERROR queue.AuditFileSpool
> (AuditFileSpool.java:logError(710)) - Error sending logs to consumer.
> provider=knox.async.multi_dest.batch,
> consumer=knox.async.multi_dest.batch.hdfs{{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20391) Ambari Metrics Grafana Datasource plugin does not work when configured with a reverse proxy with subpath
[ https://issues.apache.org/jira/browse/AMBARI-20391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-20391: - Status: Patch Available (was: Open) > Ambari Metrics Grafana Datasource plugin does not work when configured with a > reverse proxy with subpath > > > Key: AMBARI-20391 > URL: https://issues.apache.org/jira/browse/AMBARI-20391 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.2.2 >Reporter: Yusaku Sako >Assignee: Yusaku Sako >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20391.patch, duplicate-grafana-grafana.png > > > When Grafana is set up with a reverse proxy with sub path > (http://docs.grafana.org/installation/behind_proxy/), Ambari Metrics > datasource plugin does not work. > With the subpath "/grafana", Grafana is making calls with incorrect URLs to > the Metrics Collector. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20390) Inappropriate kafka log4j configuration results in too much kafka logs
[ https://issues.apache.org/jira/browse/AMBARI-20390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] WangJie updated AMBARI-20390: - Fix Version/s: trunk > Inappropriate kafka log4j configuration results in too much kafka logs > --- > > Key: AMBARI-20390 > URL: https://issues.apache.org/jira/browse/AMBARI-20390 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: trunk, 2.4.0 >Reporter: WangJie > Fix For: trunk > > Attachments: AMBARI-20390.patch, screenshot-1.png > > > Inappropriate kafka log4j configuration results in too much kafka logs which > are constantly increasing and never be removed. > Besides,DailyRollingFileAppender does not support property:maxBackupIndex and > maxFileSize, Only RollingFileAppender supports it. > Suggestion: > Change kafka log4j appender mode from DailyRollingFileAppender to > RollingFileAppender. > In this way, it will automatically remove the useless kafka log file. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20391) Ambari Metrics Grafana Datasource plugin does not work when configured with a reverse proxy with subpath
[ https://issues.apache.org/jira/browse/AMBARI-20391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15904306#comment-15904306 ] Yusaku Sako commented on AMBARI-20391: -- https://github.com/grafana/grafana/blob/v2.6.0/public/app/core/services/backend_srv.js#L68-L70 was adding extra subpath even though the URL already contains it. The fix was to use the backendSrv.datasourceRequest, and not use backendSrv.get directly. > Ambari Metrics Grafana Datasource plugin does not work when configured with a > reverse proxy with subpath > > > Key: AMBARI-20391 > URL: https://issues.apache.org/jira/browse/AMBARI-20391 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.2.2 >Reporter: Yusaku Sako >Assignee: Yusaku Sako >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20391.patch, duplicate-grafana-grafana.png > > > When Grafana is set up with a reverse proxy with sub path > (http://docs.grafana.org/installation/behind_proxy/), Ambari Metrics > datasource plugin does not work. > With the subpath "/grafana", Grafana is making calls with incorrect URLs to > the Metrics Collector. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20391) Ambari Metrics Grafana Datasource plugin does not work when configured with a reverse proxy with subpath
[ https://issues.apache.org/jira/browse/AMBARI-20391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-20391: - Attachment: AMBARI-20391.patch > Ambari Metrics Grafana Datasource plugin does not work when configured with a > reverse proxy with subpath > > > Key: AMBARI-20391 > URL: https://issues.apache.org/jira/browse/AMBARI-20391 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.2.2 >Reporter: Yusaku Sako >Assignee: Yusaku Sako >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20391.patch, duplicate-grafana-grafana.png > > > When Grafana is set up with a reverse proxy with sub path > (http://docs.grafana.org/installation/behind_proxy/), Ambari Metrics > datasource plugin does not work. > With the subpath "/grafana", Grafana is making calls with incorrect URLs to > the Metrics Collector. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20391) Ambari Metrics Grafana Datasource plugin does not work when configured with a reverse proxy with subpath
[ https://issues.apache.org/jira/browse/AMBARI-20391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-20391: - Attachment: duplicate-grafana-grafana.png > Ambari Metrics Grafana Datasource plugin does not work when configured with a > reverse proxy with subpath > > > Key: AMBARI-20391 > URL: https://issues.apache.org/jira/browse/AMBARI-20391 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.2.2 >Reporter: Yusaku Sako >Assignee: Yusaku Sako >Priority: Critical > Fix For: 2.5.0 > > Attachments: duplicate-grafana-grafana.png > > > When Grafana is set up with a reverse proxy with sub path > (http://docs.grafana.org/installation/behind_proxy/), Ambari Metrics > datasource plugin does not work. > With the subpath "/grafana", Grafana is making calls with incorrect URLs to > the Metrics Collector. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20391) Ambari Metrics Grafana Datasource plugin does not work when configured with a reverse proxy with subpath
Yusaku Sako created AMBARI-20391: Summary: Ambari Metrics Grafana Datasource plugin does not work when configured with a reverse proxy with subpath Key: AMBARI-20391 URL: https://issues.apache.org/jira/browse/AMBARI-20391 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: 2.2.2 Reporter: Yusaku Sako Assignee: Yusaku Sako Priority: Critical Fix For: 2.5.0 When Grafana is set up with a reverse proxy with sub path (http://docs.grafana.org/installation/behind_proxy/), Ambari Metrics datasource plugin does not work. With the subpath "/grafana", Grafana is making calls with incorrect URLs to the Metrics Collector. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20390) Inappropriate kafka log4j configuration results in too much kafka logs
[ https://issues.apache.org/jira/browse/AMBARI-20390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] WangJie updated AMBARI-20390: - Status: Patch Available (was: Open) > Inappropriate kafka log4j configuration results in too much kafka logs > --- > > Key: AMBARI-20390 > URL: https://issues.apache.org/jira/browse/AMBARI-20390 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: trunk, 2.4.0 >Reporter: WangJie > Attachments: AMBARI-20390.patch, screenshot-1.png > > > Inappropriate kafka log4j configuration results in too much kafka logs which > are constantly increasing and never be removed. > Besides,DailyRollingFileAppender does not support property:maxBackupIndex and > maxFileSize, Only RollingFileAppender supports it. > Suggestion: > Change kafka log4j appender mode from DailyRollingFileAppender to > RollingFileAppender. > In this way, it will automatically remove the useless kafka log file. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20390) Inappropriate kafka log4j configuration results in too much kafka logs
[ https://issues.apache.org/jira/browse/AMBARI-20390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] WangJie updated AMBARI-20390: - Attachment: screenshot-1.png > Inappropriate kafka log4j configuration results in too much kafka logs > --- > > Key: AMBARI-20390 > URL: https://issues.apache.org/jira/browse/AMBARI-20390 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: trunk, 2.4.0 >Reporter: WangJie > Attachments: AMBARI-20390.patch, screenshot-1.png > > > Inappropriate kafka log4j configuration results in too much kafka logs which > are constantly increasing and never be removed. > Besides,DailyRollingFileAppender does not support property:maxBackupIndex and > maxFileSize, Only RollingFileAppender supports it. > Suggestion: > Change kafka log4j appender mode from DailyRollingFileAppender to > RollingFileAppender. > In this way, it will automatically remove the useless kafka log file. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20390) Inappropriate kafka log4j configuration results in too much kafka logs
[ https://issues.apache.org/jira/browse/AMBARI-20390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] WangJie updated AMBARI-20390: - Attachment: AMBARI-20390.patch > Inappropriate kafka log4j configuration results in too much kafka logs > --- > > Key: AMBARI-20390 > URL: https://issues.apache.org/jira/browse/AMBARI-20390 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: trunk, 2.4.0 >Reporter: WangJie > Attachments: AMBARI-20390.patch > > > Inappropriate kafka log4j configuration results in too much kafka logs which > are constantly increasing and never be removed. > Besides,DailyRollingFileAppender does not support property:maxBackupIndex and > maxFileSize, Only RollingFileAppender supports it. > Suggestion: > Change kafka log4j appender mode from DailyRollingFileAppender to > RollingFileAppender. > In this way, it will automatically remove the useless kafka log file. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20390) Inappropriate kafka log4j configuration results in too much kafka logs
WangJie created AMBARI-20390: Summary: Inappropriate kafka log4j configuration results in too much kafka logs Key: AMBARI-20390 URL: https://issues.apache.org/jira/browse/AMBARI-20390 Project: Ambari Issue Type: Bug Components: ambari-sever Affects Versions: trunk, 2.4.0 Reporter: WangJie Inappropriate kafka log4j configuration results in too much kafka logs which are constantly increasing and never be removed. Besides,DailyRollingFileAppender does not support property:maxBackupIndex and maxFileSize, Only RollingFileAppender supports it. Suggestion: Change kafka log4j appender mode from DailyRollingFileAppender to RollingFileAppender. In this way, it will automatically remove the useless kafka log file. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-18892) storm DRPC_SERVER kerberos configs duplicate
[ https://issues.apache.org/jira/browse/AMBARI-18892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin resolved AMBARI-18892. - Resolution: Fixed > storm DRPC_SERVER kerberos configs duplicate > - > > Key: AMBARI-18892 > URL: https://issues.apache.org/jira/browse/AMBARI-18892 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk, 2.4.1 >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk, 3.0.0 > > Attachments: AMBARI-18892_01.patch, AMBARI-18892.patch, storm.png > > > when ambari enables kerberos, add storm service ,nimbus_keytab and > nimbus_principal_name will duplicate -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20368) Hbase-client installed failed when hdfs hasnot installed
[ https://issues.apache.org/jira/browse/AMBARI-20368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15904178#comment-15904178 ] zhangxiaolu commented on AMBARI-20368: -- [~afernandez],Thank you so much for reviewing my patch on reviewboard, and could you commit the patch ? Thanks a lot > Hbase-client installed failed when hdfs hasnot installed > > > Key: AMBARI-20368 > URL: https://issues.apache.org/jira/browse/AMBARI-20368 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.4.0, 2.4.1, 2.5.0, 2.4.2 >Reporter: zhangxiaolu > Attachments: AMBARI-20368.patch, screenshot-1.png > > > the problem is that the installing of hbase-client is before hdfs-client, and > the hdfs-client installed failed because the hadoop-conf-dir didn't exist. > so there are two ways to solve this problem. > the first method is that create the hadoop-conf-dir in hbase.py > the second method is that setting the orders in role_command_order.json. > I think that we can take the first method. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20385) Grafana is storing credentials in plain text in its configuration
[ https://issues.apache.org/jira/browse/AMBARI-20385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15904040#comment-15904040 ] Hudson commented on AMBARI-20385: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6994 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6994/]) AMBARI-20385 : Grafana is storing credentials in plain text in its (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=dde6583030ddf3b28d543942b8df0216f3bec826]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana_util.py * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-grafana-ini.xml * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java > Grafana is storing credentials in plain text in its configuration > - > > Key: AMBARI-20385 > URL: https://issues.apache.org/jira/browse/AMBARI-20385 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Blocker > Fix For: 2.5.0 > > Attachments: AMBARI-20385.patch > > > Grafana stores the cluster admin credentails in plain text form at > /etc/ambari-metrics-grafana/conf/ams-grafana.ini -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20385) Grafana is storing credentials in plain text in its configuration
[ https://issues.apache.org/jira/browse/AMBARI-20385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15904024#comment-15904024 ] Hudson commented on AMBARI-20385: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1226 (See [https://builds.apache.org/job/Ambari-branch-2.5/1226/]) AMBARI-20385 : Grafana is storing credentials in plain text in its (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=6e0b234e37aec4b9e0aaf8b325a168d7b477b98b]) * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana_util.py * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-grafana-ini.xml * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py * (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java > Grafana is storing credentials in plain text in its configuration > - > > Key: AMBARI-20385 > URL: https://issues.apache.org/jira/browse/AMBARI-20385 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Blocker > Fix For: 2.5.0 > > Attachments: AMBARI-20385.patch > > > Grafana stores the cluster admin credentails in plain text form at > /etc/ambari-metrics-grafana/conf/ams-grafana.ini -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20356) description incorrect for result class
[ https://issues.apache.org/jira/browse/AMBARI-20356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15904011#comment-15904011 ] Hudson commented on AMBARI-20356: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6993 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6993/]) AMBARI-20356. Description incorrect for result class (wangyaoxin via (afernandez: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=5f3038138f8431350ff3a8fe45fffd6c7e331983]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/api/services/Result.java > description incorrect for result class > --- > > Key: AMBARI-20356 > URL: https://issues.apache.org/jira/browse/AMBARI-20356 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk > > Attachments: AMBARI-20356.patch, ambari.png > > > ambari-server/src/main/java/org/apache/ambari/server/api/services/Result.java > > "the results of the request a a Tree structure" should be "the results of the > request as a Tree structure" -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20322) HDP 3.0 TP - create Service Advisor for Slider
[ https://issues.apache.org/jira/browse/AMBARI-20322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15904010#comment-15904010 ] Hudson commented on AMBARI-20322: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6993 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6993/]) Revert "AMBARI-20322 HDP 3.0 TP - create Service Advisor for Slider (jhurley: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4e864047de5028b634ace49de59579bed2a5212e]) * (delete) ambari-server/src/main/resources/common-services/SLIDER/0.91.0.3.0/service_advisor.py > HDP 3.0 TP - create Service Advisor for Slider > -- > > Key: AMBARI-20322 > URL: https://issues.apache.org/jira/browse/AMBARI-20322 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 3.0.0 >Reporter: Alejandro Fernandez >Assignee: Dmytro Sen > Fix For: 3.0.0 > > Attachments: AMBARI-20322.patch > > > Create a Service Advisor script for Slider in HDP 3.0 Tech Preview. > The Service Advisor must encapsulate all of the logic inherited/overwritten > from HDP 2.0.6 through HDP 2.6 > Slider is being added to the HDP 3.0 stack temporarily in order to unblock > Hive LLAP. Later in the HDP 3.0 release, Slider RPM will be part of YARN. We > may still keep Slider as a Service, but it may move as a component of YARN > instead. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-20389) Druid Superset fails to Start when special characters are present in user name
[
https://issues.apache.org/jira/browse/AMBARI-20389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sunitha reassigned AMBARI-20389:
Assignee: Nishant Bangarwa (was: Sunitha)
> Druid Superset fails to Start when special characters are present in user name
> --
>
> Key: AMBARI-20389
> URL: https://issues.apache.org/jira/browse/AMBARI-20389
> Project: Ambari
> Issue Type: Bug
>Reporter: Sunitha
>Assignee: Nishant Bangarwa
>Priority: Critical
> Fix For: 2.5.0
>
>
> Install Druid using ambari with special characters in First and Last name
> collected for superset admin details
> Observed:
> Superest fails to start
> {code}
> 2017-02-27 22:09:02,249 - Execute['source /etc/superset/conf/superset-env.sh
> ; /usr/hdp/current/druid-superset/bin/fabmanager create-admin --app superset
> --username admin --password --firstname @$#$$#% --lastname #$W%E$%E
> --email dfdf@bjfkdbv'] {'user': 'druid'}
> Hortonworks #
> This is MOTD message, added for testing in qe infra
> /usr/hdp/2.6.0.0-554/superset/lib/python3.4/importlib/_bootstrap.py:1161:
> ExtDeprecationWarning: Importing flask.ext.sqlalchemy is deprecated, use
> flask_sqlalchemy instead.
> spec.loader.load_module(spec.name)
> Error: --lastname option requires an argument
> 2017-02-27 22:09:03,651 - Command: /usr/bin/hdp-select status druid-superset
> > /tmp/tmpvGGiFl
> Output: druid-superset - 2.6.0.0-554
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20389) Druid Superset fails to Start when special characters are present in user name
Sunitha created AMBARI-20389:
Summary: Druid Superset fails to Start when special characters are
present in user name
Key: AMBARI-20389
URL: https://issues.apache.org/jira/browse/AMBARI-20389
Project: Ambari
Issue Type: Bug
Reporter: Sunitha
Priority: Critical
Fix For: 2.5.0
Install Druid using ambari with special characters in First and Last name
collected for superset admin details
Observed:
Superest fails to start
{code}
2017-02-27 22:09:02,249 - Execute['source /etc/superset/conf/superset-env.sh ;
/usr/hdp/current/druid-superset/bin/fabmanager create-admin --app superset
--username admin --password --firstname @$#$$#% --lastname #$W%E$%E
--email dfdf@bjfkdbv'] {'user': 'druid'}
Hortonworks #
This is MOTD message, added for testing in qe infra
/usr/hdp/2.6.0.0-554/superset/lib/python3.4/importlib/_bootstrap.py:1161:
ExtDeprecationWarning: Importing flask.ext.sqlalchemy is deprecated, use
flask_sqlalchemy instead.
spec.loader.load_module(spec.name)
Error: --lastname option requires an argument
2017-02-27 22:09:03,651 - Command: /usr/bin/hdp-select status druid-superset >
/tmp/tmpvGGiFl
Output: druid-superset - 2.6.0.0-554
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (AMBARI-20389) Druid Superset fails to Start when special characters are present in user name
[
https://issues.apache.org/jira/browse/AMBARI-20389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sunitha reassigned AMBARI-20389:
Assignee: Sunitha
> Druid Superset fails to Start when special characters are present in user name
> --
>
> Key: AMBARI-20389
> URL: https://issues.apache.org/jira/browse/AMBARI-20389
> Project: Ambari
> Issue Type: Bug
>Reporter: Sunitha
>Assignee: Sunitha
>Priority: Critical
> Fix For: 2.5.0
>
>
> Install Druid using ambari with special characters in First and Last name
> collected for superset admin details
> Observed:
> Superest fails to start
> {code}
> 2017-02-27 22:09:02,249 - Execute['source /etc/superset/conf/superset-env.sh
> ; /usr/hdp/current/druid-superset/bin/fabmanager create-admin --app superset
> --username admin --password --firstname @$#$$#% --lastname #$W%E$%E
> --email dfdf@bjfkdbv'] {'user': 'druid'}
> Hortonworks #
> This is MOTD message, added for testing in qe infra
> /usr/hdp/2.6.0.0-554/superset/lib/python3.4/importlib/_bootstrap.py:1161:
> ExtDeprecationWarning: Importing flask.ext.sqlalchemy is deprecated, use
> flask_sqlalchemy instead.
> spec.loader.load_module(spec.name)
> Error: --lastname option requires an argument
> 2017-02-27 22:09:03,651 - Command: /usr/bin/hdp-select status druid-superset
> > /tmp/tmpvGGiFl
> Output: druid-superset - 2.6.0.0-554
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20387) Upgrades on MySQL Should Also Drop Indexes With Foreign Key Names
[
https://issues.apache.org/jira/browse/AMBARI-20387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-20387:
-
Attachment: AMBARI-20387.patch
> Upgrades on MySQL Should Also Drop Indexes With Foreign Key Names
> -
>
> Key: AMBARI-20387
> URL: https://issues.apache.org/jira/browse/AMBARI-20387
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
> Fix For: 2.5.0
>
> Attachments: AMBARI-20387.patch
>
>
> There are some MySQL installations of Ambari which are correctly setup to use
> {{InnoDB}}, but still are missing foreign key relationships on certain
> tables. When the upgrade catalogs try to drop foreign keys by name, they are
> not found. However, when re-creating them, the existing {{INDEX}} constraints
> are named the same and prevent the new FKs from being created.
> {code}
> Error output from schema upgrade command:
> Exception in thread "main" org.apache.ambari.server.AmbariException:
> Duplicate key name 'hstcmpnntdesiredstatecmpnntnme'
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:210)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:350)
> Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException:
> Duplicate key name 'hstcmpnntdesiredstatecmpnntnme'
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> at com.mysql.jdbc.Util.handleNewInstance(Util.java:404)
> at com.mysql.jdbc.Util.getInstance(Util.java:387)
> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:942)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3966)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3902)
> at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2526)
> at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2673)
> at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2545)
> at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2503)
> at
> com.mysql.jdbc.StatementImpl.executeInternal(StatementImpl.java:839)
> at com.mysql.jdbc.StatementImpl.execute(StatementImpl.java:739)
> at
> org.apache.ambari.server.orm.DBAccessorImpl.executeQuery(DBAccessorImpl.java:827)
> at
> org.apache.ambari.server.orm.DBAccessorImpl.addFKConstraint(DBAccessorImpl.java:472)
> at
> org.apache.ambari.server.orm.DBAccessorImpl.addFKConstraint(DBAccessorImpl.java:456)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog240.updateServiceComponentDesiredStateTableDDL(UpgradeCatalog240.java:1621)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog240.executeDDLUpdates(UpgradeCatalog240.java:294)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeSchema(AbstractUpgradeCatalog.java:898)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:207)
> ... 1 more
> ERROR: Error executing schema upgrade, please check the server logs.
> {code}
> {code}
> mysql> show create table hostcomponentdesiredstate;
> --+
> | hostcomponentdesiredstate | CREATE TABLE `hostcomponentdesiredstate` (
> `cluster_id` bigint(20) NOT NULL,
> `component_name` varchar(255) NOT NULL,
> `desired_state` varchar(255) NOT NULL,
> `service_name` varchar(255) NOT NULL,
> `admin_state` varchar(32) DEFAULT NULL,
> `maintenance_state` varchar(32) NOT NULL DEFAULT 'ACTIVE',
> `security_state` varchar(32) NOT NULL DEFAULT 'UNSECURED',
> `restart_required` tinyint(1) NOT NULL DEFAULT '0',
> `host_id` bigint(20) NOT NULL,
> `desired_stack_id` bigint(20) NOT NULL,
> PRIMARY KEY (`cluster_id`,`component_name`,`host_id`,`service_name`),
> KEY `hstcmpnntdesiredstatecmpnntnme`
> (`component_name`,`cluster_id`,`service_name`),
> KEY `FK_hostcomponentdesiredstate_desired_stack_id` (`desired_stack_id`),
> KEY `FK_hostcomponentdesiredstate_host_id` (`host_id`),
> CONSTRAINT `FK_hcdesiredstate_host_id` FOREIGN KEY (`host_id`) REFERENCES
> `hosts` (`host_id`),
> CONSTRAINT `fk_hcds_desired_stack_id` FOREIGN KEY (`desired_stack_id`)
> REFERENCES `stack` (`stack_id`),
> CONSTRAINT
[jira] [Updated] (AMBARI-20385) Grafana is storing credentials in plain text in its configuration
[ https://issues.apache.org/jira/browse/AMBARI-20385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-20385: --- Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to branch-2.5 and trunk. > Grafana is storing credentials in plain text in its configuration > - > > Key: AMBARI-20385 > URL: https://issues.apache.org/jira/browse/AMBARI-20385 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Blocker > Fix For: 2.5.0 > > Attachments: AMBARI-20385.patch > > > Grafana stores the cluster admin credentails in plain text form at > /etc/ambari-metrics-grafana/conf/ams-grafana.ini -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20387) Upgrades on MySQL Should Also Drop Indexes With Foreign Key Names
[
https://issues.apache.org/jira/browse/AMBARI-20387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-20387:
-
Status: Patch Available (was: Open)
> Upgrades on MySQL Should Also Drop Indexes With Foreign Key Names
> -
>
> Key: AMBARI-20387
> URL: https://issues.apache.org/jira/browse/AMBARI-20387
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
> Fix For: 2.5.0
>
>
> There are some MySQL installations of Ambari which are correctly setup to use
> {{InnoDB}}, but still are missing foreign key relationships on certain
> tables. When the upgrade catalogs try to drop foreign keys by name, they are
> not found. However, when re-creating them, the existing {{INDEX}} constraints
> are named the same and prevent the new FKs from being created.
> {code}
> Error output from schema upgrade command:
> Exception in thread "main" org.apache.ambari.server.AmbariException:
> Duplicate key name 'hstcmpnntdesiredstatecmpnntnme'
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:210)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:350)
> Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException:
> Duplicate key name 'hstcmpnntdesiredstatecmpnntnme'
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> at com.mysql.jdbc.Util.handleNewInstance(Util.java:404)
> at com.mysql.jdbc.Util.getInstance(Util.java:387)
> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:942)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3966)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3902)
> at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2526)
> at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2673)
> at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2545)
> at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2503)
> at
> com.mysql.jdbc.StatementImpl.executeInternal(StatementImpl.java:839)
> at com.mysql.jdbc.StatementImpl.execute(StatementImpl.java:739)
> at
> org.apache.ambari.server.orm.DBAccessorImpl.executeQuery(DBAccessorImpl.java:827)
> at
> org.apache.ambari.server.orm.DBAccessorImpl.addFKConstraint(DBAccessorImpl.java:472)
> at
> org.apache.ambari.server.orm.DBAccessorImpl.addFKConstraint(DBAccessorImpl.java:456)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog240.updateServiceComponentDesiredStateTableDDL(UpgradeCatalog240.java:1621)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog240.executeDDLUpdates(UpgradeCatalog240.java:294)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeSchema(AbstractUpgradeCatalog.java:898)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:207)
> ... 1 more
> ERROR: Error executing schema upgrade, please check the server logs.
> {code}
> {code}
> mysql> show create table hostcomponentdesiredstate;
> --+
> | hostcomponentdesiredstate | CREATE TABLE `hostcomponentdesiredstate` (
> `cluster_id` bigint(20) NOT NULL,
> `component_name` varchar(255) NOT NULL,
> `desired_state` varchar(255) NOT NULL,
> `service_name` varchar(255) NOT NULL,
> `admin_state` varchar(32) DEFAULT NULL,
> `maintenance_state` varchar(32) NOT NULL DEFAULT 'ACTIVE',
> `security_state` varchar(32) NOT NULL DEFAULT 'UNSECURED',
> `restart_required` tinyint(1) NOT NULL DEFAULT '0',
> `host_id` bigint(20) NOT NULL,
> `desired_stack_id` bigint(20) NOT NULL,
> PRIMARY KEY (`cluster_id`,`component_name`,`host_id`,`service_name`),
> KEY `hstcmpnntdesiredstatecmpnntnme`
> (`component_name`,`cluster_id`,`service_name`),
> KEY `FK_hostcomponentdesiredstate_desired_stack_id` (`desired_stack_id`),
> KEY `FK_hostcomponentdesiredstate_host_id` (`host_id`),
> CONSTRAINT `FK_hcdesiredstate_host_id` FOREIGN KEY (`host_id`) REFERENCES
> `hosts` (`host_id`),
> CONSTRAINT `fk_hcds_desired_stack_id` FOREIGN KEY (`desired_stack_id`)
> REFERENCES `stack` (`stack_id`),
> CONSTRAINT `FK_hostcomponentdesiredstate_desired_stack_id` FOREIGN KEY
>
[jira] [Commented] (AMBARI-20364) UI labels for SPARK and SPARK2 users in Customize Service Misc page and Service accounts page
[ https://issues.apache.org/jira/browse/AMBARI-20364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903953#comment-15903953 ] Hudson commented on AMBARI-20364: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1225 (See [https://builds.apache.org/job/Ambari-branch-2.5/1225/]) AMBARI-20364. UI labels for SPARK and SPARK2 users in Customize Service (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7c76aeb24d081125672722f48708901f58d9abfc]) * (edit) ambari-server/src/main/resources/common-services/SPARK2/2.0.0/configuration/spark2-env.xml > UI labels for SPARK and SPARK2 users in Customize Service Misc page and > Service accounts page > - > > Key: AMBARI-20364 > URL: https://issues.apache.org/jira/browse/AMBARI-20364 > Project: Ambari > Issue Type: Bug >Reporter: Mingjie Tang >Assignee: Mingjie Tang > Fix For: 2.5.0 > > Attachments: AMBARI-20364.diff > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-20356) description incorrect for result class
[ https://issues.apache.org/jira/browse/AMBARI-20356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez resolved AMBARI-20356. -- Resolution: Fixed Pushed to trunk, commit 5f3038138f8431350ff3a8fe45fffd6c7e331983 > description incorrect for result class > --- > > Key: AMBARI-20356 > URL: https://issues.apache.org/jira/browse/AMBARI-20356 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk > > Attachments: AMBARI-20356.patch, ambari.png > > > ambari-server/src/main/java/org/apache/ambari/server/api/services/Result.java > > "the results of the request a a Tree structure" should be "the results of the > request as a Tree structure" -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20366) Tokenize kerberos principal name appearing in kerberos rules in exported blueprint
[ https://issues.apache.org/jira/browse/AMBARI-20366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20366: --- Status: Open (was: Patch Available) > Tokenize kerberos principal name appearing in kerberos rules in exported > blueprint > -- > > Key: AMBARI-20366 > URL: https://issues.apache.org/jira/browse/AMBARI-20366 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20366.patch > > > If blueprint is exported from a kerberos enabled cluster Kerberos rules > export principal names which contain cluster name and Realm, this exports > existing cluster name and realm name as tokens and replaces those tokens with > new values of cluster name and realm during successive cluster deployments. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20366) Tokenize kerberos principal name appearing in kerberos rules in exported blueprint
[ https://issues.apache.org/jira/browse/AMBARI-20366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20366: --- Status: Patch Available (was: Open) > Tokenize kerberos principal name appearing in kerberos rules in exported > blueprint > -- > > Key: AMBARI-20366 > URL: https://issues.apache.org/jira/browse/AMBARI-20366 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20366.patch > > > If blueprint is exported from a kerberos enabled cluster Kerberos rules > export principal names which contain cluster name and Realm, this exports > existing cluster name and realm name as tokens and replaces those tokens with > new values of cluster name and realm during successive cluster deployments. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20385) Grafana is storing credentials in plain text in its configuration
[ https://issues.apache.org/jira/browse/AMBARI-20385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-20385: --- Status: Patch Available (was: Open) > Grafana is storing credentials in plain text in its configuration > - > > Key: AMBARI-20385 > URL: https://issues.apache.org/jira/browse/AMBARI-20385 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Blocker > Fix For: 2.5.0 > > Attachments: AMBARI-20385.patch > > > Grafana stores the cluster admin credentails in plain text form at > /etc/ambari-metrics-grafana/conf/ams-grafana.ini -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20385) Grafana is storing credentials in plain text in its configuration
[ https://issues.apache.org/jira/browse/AMBARI-20385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-20385: --- Attachment: AMBARI-20385.patch > Grafana is storing credentials in plain text in its configuration > - > > Key: AMBARI-20385 > URL: https://issues.apache.org/jira/browse/AMBARI-20385 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Blocker > Fix For: 2.5.0 > > Attachments: AMBARI-20385.patch > > > Grafana stores the cluster admin credentails in plain text form at > /etc/ambari-metrics-grafana/conf/ams-grafana.ini -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20366) Tokenize kerberos principal name appearing in kerberos rules in exported blueprint
[ https://issues.apache.org/jira/browse/AMBARI-20366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20366: --- Attachment: AMBARI-20366.patch > Tokenize kerberos principal name appearing in kerberos rules in exported > blueprint > -- > > Key: AMBARI-20366 > URL: https://issues.apache.org/jira/browse/AMBARI-20366 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20366.patch > > > If blueprint is exported from a kerberos enabled cluster Kerberos rules > export principal names which contain cluster name and Realm, this exports > existing cluster name and realm name as tokens and replaces those tokens with > new values of cluster name and realm during successive cluster deployments. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Reopened] (AMBARI-20322) HDP 3.0 TP - create Service Advisor for Slider
[ https://issues.apache.org/jira/browse/AMBARI-20322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley reopened AMBARI-20322: -- Reverted as this prevented Ambari from starting up. > HDP 3.0 TP - create Service Advisor for Slider > -- > > Key: AMBARI-20322 > URL: https://issues.apache.org/jira/browse/AMBARI-20322 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 3.0.0 >Reporter: Alejandro Fernandez >Assignee: Dmytro Sen > Fix For: 3.0.0 > > Attachments: AMBARI-20322.patch > > > Create a Service Advisor script for Slider in HDP 3.0 Tech Preview. > The Service Advisor must encapsulate all of the logic inherited/overwritten > from HDP 2.0.6 through HDP 2.6 > Slider is being added to the HDP 3.0 stack temporarily in order to unblock > Hive LLAP. Later in the HDP 3.0 release, Slider RPM will be part of YARN. We > may still keep Slider as a Service, but it may move as a component of YARN > instead. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20388) Diff tool shows additional line when comparing configs from custom config group
Dhanya Balasundaran created AMBARI-20388: Summary: Diff tool shows additional line when comparing configs from custom config group Key: AMBARI-20388 URL: https://issues.apache.org/jira/browse/AMBARI-20388 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Dhanya Balasundaran Fix For: 2.5.0 - Create a custom config group for a service - Update few properties and save to get a version for this custom group - Add another property and save just to generate more config version - Compare these 2 versions. Usually diff shows only the values from compared versions - But looks like it shows the current value and the values in each version as well. - In default group we dont see that extra line with the current value. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20364) UI labels for SPARK and SPARK2 users in Customize Service Misc page and Service accounts page
[ https://issues.apache.org/jira/browse/AMBARI-20364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903887#comment-15903887 ] Hudson commented on AMBARI-20364: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6992 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6992/]) AMBARI-20364. UI labels for SPARK and SPARK2 users in Customize Service (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=6cfad94cc20631960b50454cc95b7e5f71ca461b]) * (edit) ambari-server/src/main/resources/common-services/SPARK2/2.0.0/configuration/spark2-env.xml > UI labels for SPARK and SPARK2 users in Customize Service Misc page and > Service accounts page > - > > Key: AMBARI-20364 > URL: https://issues.apache.org/jira/browse/AMBARI-20364 > Project: Ambari > Issue Type: Bug >Reporter: Mingjie Tang >Assignee: Mingjie Tang > Fix For: 2.5.0 > > Attachments: AMBARI-20364.diff > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20387) Upgrades on MySQL Should Also Drop Indexes With Foreign Key Names
Jonathan Hurley created AMBARI-20387:
Summary: Upgrades on MySQL Should Also Drop Indexes With Foreign
Key Names
Key: AMBARI-20387
URL: https://issues.apache.org/jira/browse/AMBARI-20387
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.5.0
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Fix For: 2.5.0
There are some MySQL installations of Ambari which are correctly setup to use
{{InnoDB}}, but still are missing foreign key relationships on certain tables.
When the upgrade catalogs try to drop foreign keys by name, they are not found.
However, when re-creating them, the existing {{INDEX}} constraints are named
the same and prevent the new FKs from being created.
{code}
Error output from schema upgrade command:
Exception in thread "main" org.apache.ambari.server.AmbariException: Duplicate
key name 'hstcmpnntdesiredstatecmpnntnme'
at
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:210)
at
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:350)
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Duplicate
key name 'hstcmpnntdesiredstatecmpnntnme'
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at com.mysql.jdbc.Util.handleNewInstance(Util.java:404)
at com.mysql.jdbc.Util.getInstance(Util.java:387)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:942)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3966)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3902)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2526)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2673)
at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2545)
at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2503)
at com.mysql.jdbc.StatementImpl.executeInternal(StatementImpl.java:839)
at com.mysql.jdbc.StatementImpl.execute(StatementImpl.java:739)
at
org.apache.ambari.server.orm.DBAccessorImpl.executeQuery(DBAccessorImpl.java:827)
at
org.apache.ambari.server.orm.DBAccessorImpl.addFKConstraint(DBAccessorImpl.java:472)
at
org.apache.ambari.server.orm.DBAccessorImpl.addFKConstraint(DBAccessorImpl.java:456)
at
org.apache.ambari.server.upgrade.UpgradeCatalog240.updateServiceComponentDesiredStateTableDDL(UpgradeCatalog240.java:1621)
at
org.apache.ambari.server.upgrade.UpgradeCatalog240.executeDDLUpdates(UpgradeCatalog240.java:294)
at
org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeSchema(AbstractUpgradeCatalog.java:898)
at
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:207)
... 1 more
ERROR: Error executing schema upgrade, please check the server logs.
{code}
{code}
mysql> show create table hostcomponentdesiredstate;
--+
| hostcomponentdesiredstate | CREATE TABLE `hostcomponentdesiredstate` (
`cluster_id` bigint(20) NOT NULL,
`component_name` varchar(255) NOT NULL,
`desired_state` varchar(255) NOT NULL,
`service_name` varchar(255) NOT NULL,
`admin_state` varchar(32) DEFAULT NULL,
`maintenance_state` varchar(32) NOT NULL DEFAULT 'ACTIVE',
`security_state` varchar(32) NOT NULL DEFAULT 'UNSECURED',
`restart_required` tinyint(1) NOT NULL DEFAULT '0',
`host_id` bigint(20) NOT NULL,
`desired_stack_id` bigint(20) NOT NULL,
PRIMARY KEY (`cluster_id`,`component_name`,`host_id`,`service_name`),
KEY `hstcmpnntdesiredstatecmpnntnme`
(`component_name`,`cluster_id`,`service_name`),
KEY `FK_hostcomponentdesiredstate_desired_stack_id` (`desired_stack_id`),
KEY `FK_hostcomponentdesiredstate_host_id` (`host_id`),
CONSTRAINT `FK_hcdesiredstate_host_id` FOREIGN KEY (`host_id`) REFERENCES
`hosts` (`host_id`),
CONSTRAINT `fk_hcds_desired_stack_id` FOREIGN KEY (`desired_stack_id`)
REFERENCES `stack` (`stack_id`),
CONSTRAINT `FK_hostcomponentdesiredstate_desired_stack_id` FOREIGN KEY
(`desired_stack_id`) REFERENCES `stack` (`stack_id`),
CONSTRAINT `FK_hostcomponentdesiredstate_host_id` FOREIGN KEY (`host_id`)
REFERENCES `hosts` (`host_id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 |
{code}
In this case, the {{INDEX}} {{hstcmpnntdesiredstatecmpnntnme}} prevents the new
FK creation.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20366) Tokenize kerberos principal name appearing in kerberos rules in exported blueprint
[ https://issues.apache.org/jira/browse/AMBARI-20366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20366: --- Attachment: (was: AMBARI-20366.patch) > Tokenize kerberos principal name appearing in kerberos rules in exported > blueprint > -- > > Key: AMBARI-20366 > URL: https://issues.apache.org/jira/browse/AMBARI-20366 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20366.patch > > > If blueprint is exported from a kerberos enabled cluster Kerberos rules > export principal names which contain cluster name and Realm, this exports > existing cluster name and realm name as tokens and replaces those tokens with > new values of cluster name and realm during successive cluster deployments. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20366) Tokenize kerberos principal name appearing in kerberos rules in exported blueprint
[
https://issues.apache.org/jira/browse/AMBARI-20366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903883#comment-15903883
]
Hadoop QA commented on AMBARI-20366:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12857091/AMBARI-20366.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10957//console
This message is automatically generated.
> Tokenize kerberos principal name appearing in kerberos rules in exported
> blueprint
> --
>
> Key: AMBARI-20366
> URL: https://issues.apache.org/jira/browse/AMBARI-20366
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, blueprints
>Affects Versions: trunk
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Fix For: trunk
>
> Attachments: AMBARI-20366.patch
>
>
> If blueprint is exported from a kerberos enabled cluster Kerberos rules
> export principal names which contain cluster name and Realm, this exports
> existing cluster name and realm name as tokens and replaces those tokens with
> new values of cluster name and realm during successive cluster deployments.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20386) Kerberos principal creation fails during blueprint install when kdc_hosts is not specified in blueprint
[ https://issues.apache.org/jira/browse/AMBARI-20386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20386: --- Attachment: AMBARI-20386.patch > Kerberos principal creation fails during blueprint install when kdc_hosts is > not specified in blueprint > --- > > Key: AMBARI-20386 > URL: https://issues.apache.org/jira/browse/AMBARI-20386 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20386.patch > > > Blueprint validation does not prompt if kdc_hosts is not specified in the > blueprint. After service installation, deployment fails during Create > Principal stage. As /etc/krb5.conf is overwritten with blank values. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20386) Kerberos principal creation fails during blueprint install when kdc_hosts is not specified in blueprint
Amruta Borkar created AMBARI-20386: -- Summary: Kerberos principal creation fails during blueprint install when kdc_hosts is not specified in blueprint Key: AMBARI-20386 URL: https://issues.apache.org/jira/browse/AMBARI-20386 Project: Ambari Issue Type: Bug Components: ambari-server, blueprints Affects Versions: trunk Reporter: Amruta Borkar Assignee: Amruta Borkar Fix For: trunk Blueprint validation does not prompt if kdc_hosts is not specified in the blueprint. After service installation, deployment fails during Create Principal stage. As /etc/krb5.conf is overwritten with blank values. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20384) Host Page filter doesn't work after sort by name
[
https://issues.apache.org/jira/browse/AMBARI-20384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903860#comment-15903860
]
Hadoop QA commented on AMBARI-20384:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12857068/AMBARI-20384.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10956//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10956//console
This message is automatically generated.
> Host Page filter doesn't work after sort by name
>
>
> Key: AMBARI-20384
> URL: https://issues.apache.org/jira/browse/AMBARI-20384
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20384_branch-2.5.patch, AMBARI-20384.patch
>
>
> *STR*:
> - Filter on say Infra SOLR Instance: All
> - Sort by Name
> - Clear filter
> - Again use filter for any Component
> Result: The value drop-down for the filter never appears.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20385) Grafana is storing credentials in plain text in its configuration
Aravindan Vijayan created AMBARI-20385: -- Summary: Grafana is storing credentials in plain text in its configuration Key: AMBARI-20385 URL: https://issues.apache.org/jira/browse/AMBARI-20385 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: 2.5.0 Reporter: Aravindan Vijayan Assignee: Aravindan Vijayan Priority: Blocker Fix For: 2.5.0 Grafana stores the cluster admin credentails in plain text form at /etc/ambari-metrics-grafana/conf/ams-grafana.ini -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20364) UI labels for SPARK and SPARK2 users in Customize Service Misc page and Service accounts page
[ https://issues.apache.org/jira/browse/AMBARI-20364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-20364: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.5 > UI labels for SPARK and SPARK2 users in Customize Service Misc page and > Service accounts page > - > > Key: AMBARI-20364 > URL: https://issues.apache.org/jira/browse/AMBARI-20364 > Project: Ambari > Issue Type: Bug >Reporter: Mingjie Tang >Assignee: Mingjie Tang > Fix For: 2.5.0 > > Attachments: AMBARI-20364.diff > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20364) UI labels for SPARK and SPARK2 users in Customize Service Misc page and Service accounts page
[ https://issues.apache.org/jira/browse/AMBARI-20364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-20364: --- Attachment: AMBARI-20364.diff > UI labels for SPARK and SPARK2 users in Customize Service Misc page and > Service accounts page > - > > Key: AMBARI-20364 > URL: https://issues.apache.org/jira/browse/AMBARI-20364 > Project: Ambari > Issue Type: Bug >Reporter: Mingjie Tang >Assignee: Mingjie Tang > Fix For: 2.5.0 > > Attachments: AMBARI-20364.diff > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20364) UI labels for SPARK and SPARK2 users in Customize Service Misc page and Service accounts page
[ https://issues.apache.org/jira/browse/AMBARI-20364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-20364: --- Status: Patch Available (was: Reopened) > UI labels for SPARK and SPARK2 users in Customize Service Misc page and > Service accounts page > - > > Key: AMBARI-20364 > URL: https://issues.apache.org/jira/browse/AMBARI-20364 > Project: Ambari > Issue Type: Bug >Reporter: Mingjie Tang >Assignee: Mingjie Tang > Fix For: 2.5.0 > > Attachments: AMBARI-20364.diff > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Reopened] (AMBARI-20364) UI labels for SPARK and SPARK2 users in Customize Service Misc page and Service accounts page
[ https://issues.apache.org/jira/browse/AMBARI-20364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty reopened AMBARI-20364: > UI labels for SPARK and SPARK2 users in Customize Service Misc page and > Service accounts page > - > > Key: AMBARI-20364 > URL: https://issues.apache.org/jira/browse/AMBARI-20364 > Project: Ambari > Issue Type: Bug >Reporter: Mingjie Tang >Assignee: Mingjie Tang > Fix For: 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20364) UI labels for SPARK and SPARK2 users in Customize Service Misc page and Service accounts page
[ https://issues.apache.org/jira/browse/AMBARI-20364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903852#comment-15903852 ] Mingjie Tang commented on AMBARI-20364: --- this is the review board for this patch. https://reviews.apache.org/r/57430/ > UI labels for SPARK and SPARK2 users in Customize Service Misc page and > Service accounts page > - > > Key: AMBARI-20364 > URL: https://issues.apache.org/jira/browse/AMBARI-20364 > Project: Ambari > Issue Type: Bug >Reporter: Mingjie Tang >Assignee: Mingjie Tang > Fix For: 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20287) Filter in Customize Services Page doesn't bring up all properties that matches
[ https://issues.apache.org/jira/browse/AMBARI-20287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903849#comment-15903849 ] Hudson commented on AMBARI-20287: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1224 (See [https://builds.apache.org/job/Ambari-branch-2.5/1224/]) AMBARI-20287 - Filter in Customize Services Page doesn't bring up all (rzang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=fcad14b39e55137912fee51a946b2b85f5140d0e]) * (edit) ambari-web/app/models/configs/theme/sub_section.js * (edit) ambari-web/app/models/configs/theme/sub_section_tab.js * (edit) ambari-web/app/views/common/configs/service_config_layout_tab_view.js * (add) ambari-web/test/models/configs/theme/sub_section_tab_test.js > Filter in Customize Services Page doesn't bring up all properties that matches > -- > > Key: AMBARI-20287 > URL: https://issues.apache.org/jira/browse/AMBARI-20287 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Dhanya Balasundaran >Assignee: Richard Zang > Fix For: 2.5.0 > > Attachments: AMBARI-20287.patch > > > - Navigate to Add Service Wizard to Add Ranger > - At Customize Services page, change Sync Source to LDAP/AD > - try to filter out few properties like: > - Enable Group Sync, Incremental Sync etc > They are not getting filtered out. As there are multiple tabs and tabs inside > first level tabs, its not easy to find the values of these properties without > the help of filter -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20287) Filter in Customize Services Page doesn't bring up all properties that matches
[ https://issues.apache.org/jira/browse/AMBARI-20287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903810#comment-15903810 ] Hudson commented on AMBARI-20287: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6991 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6991/]) AMBARI-20287 - Filter in Customize Services Page doesn't bring up all (rzang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=53e77ef5e19ddfd11630323d7e94edf448c27f50]) * (edit) ambari-web/test/models/configs/theme/sub_section_tab_test.js * (edit) ambari-web/app/models/configs/theme/sub_section.js * (edit) ambari-web/app/views/common/configs/service_config_layout_tab_view.js * (edit) ambari-web/app/models/configs/theme/sub_section_tab.js > Filter in Customize Services Page doesn't bring up all properties that matches > -- > > Key: AMBARI-20287 > URL: https://issues.apache.org/jira/browse/AMBARI-20287 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Dhanya Balasundaran >Assignee: Richard Zang > Fix For: 2.5.0 > > Attachments: AMBARI-20287.patch > > > - Navigate to Add Service Wizard to Add Ranger > - At Customize Services page, change Sync Source to LDAP/AD > - try to filter out few properties like: > - Enable Group Sync, Incremental Sync etc > They are not getting filtered out. As there are multiple tabs and tabs inside > first level tabs, its not easy to find the values of these properties without > the help of filter -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-20287) Filter in Customize Services Page doesn't bring up all properties that matches
[ https://issues.apache.org/jira/browse/AMBARI-20287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang resolved AMBARI-20287. --- Resolution: Fixed Committed to trunk and 2.5 fcad14b39e55137912fee51a946b2b85f5140d0e > Filter in Customize Services Page doesn't bring up all properties that matches > -- > > Key: AMBARI-20287 > URL: https://issues.apache.org/jira/browse/AMBARI-20287 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Dhanya Balasundaran >Assignee: Richard Zang > Fix For: 2.5.0 > > Attachments: AMBARI-20287.patch > > > - Navigate to Add Service Wizard to Add Ranger > - At Customize Services page, change Sync Source to LDAP/AD > - try to filter out few properties like: > - Enable Group Sync, Incremental Sync etc > They are not getting filtered out. As there are multiple tabs and tabs inside > first level tabs, its not easy to find the values of these properties without > the help of filter -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20278) Install Wizard > Select Services: Ambari warns me that "Ambari Infra is not selected" but it is selected
[
https://issues.apache.org/jira/browse/AMBARI-20278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903640#comment-15903640
]
Hadoop QA commented on AMBARI-20278:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12857036/AMBARI-20278_a2.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10954//console
This message is automatically generated.
> Install Wizard > Select Services: Ambari warns me that "Ambari Infra is not
> selected" but it is selected
>
>
> Key: AMBARI-20278
> URL: https://issues.apache.org/jira/browse/AMBARI-20278
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-20278_a2.patch,
> AMBARI-20278_additional_trunk_fix.patch, AMBARI-20278.patch, Screen Shot
> 2017-02-27 at 1.43.56 PM.png
>
>
> See attached.
> Most likely, I didn't select Ambari Infra originally, but then I cancelled
> out of the series of warning popups.
> Then I selected Ambari Infra. The warning does not go away.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20382) Log Search: Web UI Alert tries to use http protocol even if ssl is enabled
[
https://issues.apache.org/jira/browse/AMBARI-20382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903621#comment-15903621
]
Hadoop QA commented on AMBARI-20382:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12857051/AMBARI-20382.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10953//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10953//console
This message is automatically generated.
> Log Search: Web UI Alert tries to use http protocol even if ssl is enabled
> --
>
> Key: AMBARI-20382
> URL: https://issues.apache.org/jira/browse/AMBARI-20382
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 2.5.0
>
> Attachments: AMBARI-20382.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (AMBARI-20364) UI labels for SPARK and SPARK2 users in Customize Service Misc page and Service accounts page
[ https://issues.apache.org/jira/browse/AMBARI-20364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mingjie Tang resolved AMBARI-20364. --- Resolution: Fixed Fix Version/s: 2.5.0 > UI labels for SPARK and SPARK2 users in Customize Service Misc page and > Service accounts page > - > > Key: AMBARI-20364 > URL: https://issues.apache.org/jira/browse/AMBARI-20364 > Project: Ambari > Issue Type: Bug >Reporter: Mingjie Tang >Assignee: Mingjie Tang > Fix For: 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-18892) storm DRPC_SERVER kerberos configs duplicate
[ https://issues.apache.org/jira/browse/AMBARI-18892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903577#comment-15903577 ] Hudson commented on AMBARI-18892: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6990 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6990/]) AMBARI-18892. Summary:storm DRPC_SERVER kerberos configs duplicate (Wang (rlevas: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=c4ca3b8908c9b71a88de47400aebb874e66e17b6]) * (edit) ambari-web/app/assets/data/stacks/HDP-2.1/service_components.json * (edit) ambari-server/src/main/resources/common-services/STORM/1.0.1/kerberos.json * (edit) ambari-server/src/main/resources/common-services/STORM/0.9.1/kerberos.json > storm DRPC_SERVER kerberos configs duplicate > - > > Key: AMBARI-18892 > URL: https://issues.apache.org/jira/browse/AMBARI-18892 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk, 2.4.1 >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk, 3.0.0 > > Attachments: AMBARI-18892_01.patch, AMBARI-18892.patch, storm.png > > > when ambari enables kerberos, add storm service ,nimbus_keytab and > nimbus_principal_name will duplicate -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20384) Host Page filter doesn't work after sort by name
[ https://issues.apache.org/jira/browse/AMBARI-20384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-20384: -- Attachment: AMBARI-20384.patch > Host Page filter doesn't work after sort by name > > > Key: AMBARI-20384 > URL: https://issues.apache.org/jira/browse/AMBARI-20384 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20384_branch-2.5.patch, AMBARI-20384.patch > > > *STR*: > - Filter on say Infra SOLR Instance: All > - Sort by Name > - Clear filter > - Again use filter for any Component > Result: The value drop-down for the filter never appears. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20384) Host Page filter doesn't work after sort by name
[ https://issues.apache.org/jira/browse/AMBARI-20384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-20384: -- Status: Patch Available (was: Open) > Host Page filter doesn't work after sort by name > > > Key: AMBARI-20384 > URL: https://issues.apache.org/jira/browse/AMBARI-20384 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20384_branch-2.5.patch, AMBARI-20384.patch > > > *STR*: > - Filter on say Infra SOLR Instance: All > - Sort by Name > - Clear filter > - Again use filter for any Component > Result: The value drop-down for the filter never appears. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20384) Host Page filter doesn't work after sort by name
[ https://issues.apache.org/jira/browse/AMBARI-20384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903572#comment-15903572 ] Andrii Tkach commented on AMBARI-20384: --- branch-2.5: 30367 passing (35s) 157 pending > Host Page filter doesn't work after sort by name > > > Key: AMBARI-20384 > URL: https://issues.apache.org/jira/browse/AMBARI-20384 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20384_branch-2.5.patch > > > *STR*: > - Filter on say Infra SOLR Instance: All > - Sort by Name > - Clear filter > - Again use filter for any Component > Result: The value drop-down for the filter never appears. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20384) Host Page filter doesn't work after sort by name
[ https://issues.apache.org/jira/browse/AMBARI-20384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-20384: -- Status: Open (was: Patch Available) > Host Page filter doesn't work after sort by name > > > Key: AMBARI-20384 > URL: https://issues.apache.org/jira/browse/AMBARI-20384 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20384_branch-2.5.patch > > > *STR*: > - Filter on say Infra SOLR Instance: All > - Sort by Name > - Clear filter > - Again use filter for any Component > Result: The value drop-down for the filter never appears. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20384) Host Page filter doesn't work after sort by name
[ https://issues.apache.org/jira/browse/AMBARI-20384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-20384: -- Attachment: AMBARI-20384_branch-2.5.patch > Host Page filter doesn't work after sort by name > > > Key: AMBARI-20384 > URL: https://issues.apache.org/jira/browse/AMBARI-20384 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20384_branch-2.5.patch > > > *STR*: > - Filter on say Infra SOLR Instance: All > - Sort by Name > - Clear filter > - Again use filter for any Component > Result: The value drop-down for the filter never appears. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20384) Host Page filter doesn't work after sort by name
[ https://issues.apache.org/jira/browse/AMBARI-20384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-20384: -- Attachment: (was: AMBARI-20384.patch) > Host Page filter doesn't work after sort by name > > > Key: AMBARI-20384 > URL: https://issues.apache.org/jira/browse/AMBARI-20384 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20384_branch-2.5.patch > > > *STR*: > - Filter on say Infra SOLR Instance: All > - Sort by Name > - Clear filter > - Again use filter for any Component > Result: The value drop-down for the filter never appears. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20384) Host Page filter doesn't work after sort by name
[ https://issues.apache.org/jira/browse/AMBARI-20384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-20384: -- Status: Patch Available (was: Open) > Host Page filter doesn't work after sort by name > > > Key: AMBARI-20384 > URL: https://issues.apache.org/jira/browse/AMBARI-20384 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20384.patch > > > *STR*: > - Filter on say Infra SOLR Instance: All > - Sort by Name > - Clear filter > - Again use filter for any Component > Result: The value drop-down for the filter never appears. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20384) Host Page filter doesn't work after sort by name
[ https://issues.apache.org/jira/browse/AMBARI-20384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-20384: -- Attachment: AMBARI-20384.patch > Host Page filter doesn't work after sort by name > > > Key: AMBARI-20384 > URL: https://issues.apache.org/jira/browse/AMBARI-20384 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20384.patch > > > *STR*: > - Filter on say Infra SOLR Instance: All > - Sort by Name > - Clear filter > - Again use filter for any Component > Result: The value drop-down for the filter never appears. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20384) Host Page filter doesn't work after sort by name
Andrii Tkach created AMBARI-20384: - Summary: Host Page filter doesn't work after sort by name Key: AMBARI-20384 URL: https://issues.apache.org/jira/browse/AMBARI-20384 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Priority: Critical Fix For: 2.5.0 *STR*: - Filter on say Infra SOLR Instance: All - Sort by Name - Clear filter - Again use filter for any Component Result: The value drop-down for the filter never appears. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20369) Need hdfs-site for saving ranger audits to hdfs in namenode HA env
[
https://issues.apache.org/jira/browse/AMBARI-20369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903556#comment-15903556
]
Hadoop QA commented on AMBARI-20369:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12856966/AMBARI-20369.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10952//console
This message is automatically generated.
> Need hdfs-site for saving ranger audits to hdfs in namenode HA env
> --
>
> Key: AMBARI-20369
> URL: https://issues.apache.org/jira/browse/AMBARI-20369
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
> Labels: Ambari
> Fix For: 2.5.0
>
> Attachments: AMBARI-20369.patch
>
>
> For {{KNOX}} and {{RANGER_KMS}} services which supports ranger plugin, need
> to have hdfs-site.xml available in respective services conf directory for
> saving ranger audits to hdfs in namenode HA env.
> Below error logs are found, if hdfs-site.xml is not available,
> {noformat}
> 2017-03-01 18:48:50,150 ERROR provider.BaseAuditHandler
> (BaseAuditHandler.java:logError(327)) - Error writing to log file.
> java.lang.IllegalArgumentException: java.net.UnknownHostException: mycluster
> at
> org.apache.hadoop.security.SecurityUtil.buildTokenService(SecurityUtil.java:438)
> at
> org.apache.hadoop.hdfs.NameNodeProxies.createNonHAProxy(NameNodeProxies.java:311)
> at
> org.apache.hadoop.hdfs.NameNodeProxies.createProxy(NameNodeProxies.java:176)
> at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:690)
> at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:631)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem.initialize(DistributedFileSystem.java:160)
> at
> org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2795)
> at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:99)
> at
> org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2829)
> at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:2811)
> at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:390)
> at
> org.apache.ranger.audit.destination.HDFSAuditDestination.getLogFileStream(HDFSAuditDestination.java:271)
> at
> org.apache.ranger.audit.destination.HDFSAuditDestination.access$000(HDFSAuditDestination.java:43)
> at
> org.apache.ranger.audit.destination.HDFSAuditDestination$1.run(HDFSAuditDestination.java:157)
> at
> org.apache.ranger.audit.destination.HDFSAuditDestination$1.run(HDFSAuditDestination.java:154)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1866)
> at
> org.apache.ranger.audit.provider.MiscUtil.executePrivilegedAction(MiscUtil.java:523)
> at
> org.apache.ranger.audit.destination.HDFSAuditDestination.logJSON(HDFSAuditDestination.java:154)
> at
> org.apache.ranger.audit.queue.AuditFileSpool.sendEvent(AuditFileSpool.java:880)
> at
> org.apache.ranger.audit.queue.AuditFileSpool.runLogAudit(AuditFileSpool.java:828)
> at
> org.apache.ranger.audit.queue.AuditFileSpool.run(AuditFileSpool.java:758)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.net.UnknownHostException: mycluster
> ... 24 more
> 2017-03-01 18:48:50,151 ERROR queue.AuditFileSpool
> (AuditFileSpool.java:logError(710)) - Error sending logs to consumer.
> provider=knox.async.multi_dest.batch,
> consumer=knox.async.multi_dest.batch.hdfs{{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20370) Fix up tez view version
[
https://issues.apache.org/jira/browse/AMBARI-20370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903552#comment-15903552
]
Hadoop QA commented on AMBARI-20370:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12856968/AMBARI-20370_branch-2.5.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10951//console
This message is automatically generated.
> Fix up tez view version
> ---
>
> Key: AMBARI-20370
> URL: https://issues.apache.org/jira/browse/AMBARI-20370
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Nitiraj Singh Rathore
>Assignee: Nitiraj Singh Rathore
> Fix For: 2.5.0
>
> Attachments: AMBARI-20370_branch-2.5.patch
>
>
> Currently tez view version uses version and build in url. Because of this
> everytime tez view is changed the value of tez.tez-ui.history-url.base needs
> to be changed in tez-site.
> This url should no be fixed to auto tez view instance's short url.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19835) HDP 3.0 support for Slider with configs, kerberos, widgets, metrics, quicklinks, and themes
[
https://issues.apache.org/jira/browse/AMBARI-19835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903548#comment-15903548
]
Hadoop QA commented on AMBARI-19835:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12856978/AMBARI-19835_3.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10950//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10950//console
This message is automatically generated.
> HDP 3.0 support for Slider with configs, kerberos, widgets, metrics,
> quicklinks, and themes
> ---
>
> Key: AMBARI-19835
> URL: https://issues.apache.org/jira/browse/AMBARI-19835
> Project: Ambari
> Issue Type: Story
> Components: stacks
>Affects Versions: 3.0.0
>Reporter: Alejandro Fernandez
>Assignee: Dmytro Sen
> Fix For: 3.0.0
>
> Attachments: AMBARI-19835_2.patch, AMBARI-19835_3.patch
>
>
> HDP 3.0 support for Slider with configs, kerberos, widgets, metrics,
> quicklinks, and themes
> Flatten from HDP 2.0.6 - 2.6 into common-services, and reference in HDP 3.0
> In HDP 3.0, we have created a new stack definition that does not inherit from
> other stacks, in order to reduce the complexity of having to analyze older
> stacks.
> This means that we need to create a service definition (metainfo.xml,
> configs, kerberos, widgets, metrics, quicklinks, and themes) that is
> equivalent to what is inherit and deleted from all of the previous stacks.
> A merge needs to account for additions, overrides, and deletions.
> metainfo.xml and configs perform a merge of older versions
> kerberos.json always seems to override the previous file
> Because the bits for this service may not yet be available in the HDP 3.0
> repo,
> the task is to ensure that /api/v1/stacks/HDP/versions/2.6/services/SLIDER
> (which uses inheritance) is equivalent to the flattening of
> /api/v1/stacks/HDP/versions/3.0/services/SLIDER .
> Please take a look at how this was done for ZK, HDFS, and YARN/MR.
> This means that you will not be able to actually install the service for now,
> but can still perform validation during the Install Wizard that the correct
> components and configs show up.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-18892) storm DRPC_SERVER kerberos configs duplicate
[
https://issues.apache.org/jira/browse/AMBARI-18892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903494#comment-15903494
]
Robert Levas commented on AMBARI-18892:
---
[~forestsissi], Commit to trunk. You can resolve this JIRA and the RB.
{noformat}
commit c4ca3b8908c9b71a88de47400aebb874e66e17b6
Author: Wang Yaoxin
Date: Thu Mar 9 12:52:37 2017 -0500
{noformat}
> storm DRPC_SERVER kerberos configs duplicate
> -
>
> Key: AMBARI-18892
> URL: https://issues.apache.org/jira/browse/AMBARI-18892
> Project: Ambari
> Issue Type: Improvement
>Affects Versions: trunk, 2.4.1
>Reporter: wangyaoxin
>Assignee: wangyaoxin
> Fix For: trunk, 3.0.0
>
> Attachments: AMBARI-18892_01.patch, AMBARI-18892.patch, storm.png
>
>
> when ambari enables kerberos, add storm service ,nimbus_keytab and
> nimbus_principal_name will duplicate
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20383) Not able to view the error log details on UI
Supreeth Sharma created AMBARI-20383:
Summary: Not able to view the error log details on UI
Key: AMBARI-20383
URL: https://issues.apache.org/jira/browse/AMBARI-20383
Project: Ambari
Issue Type: Bug
Components: ambari-views
Affects Versions: 2.5.0
Reporter: Supreeth Sharma
Priority: Critical
Fix For: 2.5.0
Not able to view the error logs on UI. When user clicks on 'Details' link, UI
is failing with below error:
{code}
Uncaught TypeError: Cannot read property 'nodes' of null
at n.isWorkflowValid
(http://172.22.73.134:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-89dda89e1533d3f32ee5166954811095.js:8:25204)
at n.validate
(http://172.22.73.134:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-89dda89e1533d3f32ee5166954811095.js:58:12130)
at
http://172.22.73.134:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-b25c8db62aa353ea5ab0a4f9e228c623.js:65:30047
at Array.map (native)
at n.
(http://172.22.73.134:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-b25c8db62aa353ea5ab0a4f9e228c623.js:65:29848)
at n.
(http://172.22.73.134:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-b25c8db62aa353ea5ab0a4f9e228c623.js:65:24894)
at d.p.get
(http://172.22.73.134:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-b25c8db62aa353ea5ab0a4f9e228c623.js:9:31289)
at s
(http://172.22.73.134:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-b25c8db62aa353ea5ab0a4f9e228c623.js:11:3104)
at c
(http://172.22.73.134:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-b25c8db62aa353ea5ab0a4f9e228c623.js:11:3694)
at s
(http://172.22.73.134:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-b25c8db62aa353ea5ab0a4f9e228c623.js:11:3093)
{code}
Steps to reproduce :
1) Try to import a workflow which user doesn't have read permission.
2) 'Permission Denied' message is shown on the UI. But when user clicks on
'Details' link, UI is failing.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20372) RU: Oozie LR job failed
[
https://issues.apache.org/jira/browse/AMBARI-20372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903476#comment-15903476
]
Hadoop QA commented on AMBARI-20372:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12857000/AMBARI-20372.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10949//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10949//console
This message is automatically generated.
> RU: Oozie LR job failed
> ---
>
> Key: AMBARI-20372
> URL: https://issues.apache.org/jira/browse/AMBARI-20372
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Critical
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-20372.patch
>
>
> {code}2017-03-06 06:37:37,166|INFO|MainThread|machine.py:152 -
> run()||GUID=2a3e4542-9dbe-402a-b6e1-355445d22428|001-170305223753594-oozie-oozi-C@249
>FAILED164-170306030147803-oozie-oozi-W - 2017-03-06 01:33
> GMT 2009-01-01 21:40 GMT
>
> 2017-03-06 06:37:37,260|INFO|MainThread|machine.py:177 -
> run()||GUID=2a3e4542-9dbe-402a-b6e1-355445d22428|Exit Code: 0
> 2017-03-06 06:37:37,261|INFO|MainThread|ruUpgrade.py:70 - reportProgress()|
> [FAILED][Oozie][test_oozie_long_running] job status: DONEWITHERROR
> {code}
> {code}
> [164-170306030147803-oozie-oozi-W@wc]. Failing this action!]
> org.apache.oozie.action.ActionExecutorException: JA017: Unknown hadoop job
> [job_1488762906035_0733] associated with action
> [164-170306030147803-oozie-oozi-W@wc]. Failing this action!
> at
> org.apache.oozie.action.hadoop.JavaActionExecutor.check(JavaActionExecutor.java:1488)
> at
> org.apache.oozie.command.wf.ActionCheckXCommand.execute(ActionCheckXCommand.java:182)
> at
> org.apache.oozie.command.wf.ActionCheckXCommand.execute(ActionCheckXCommand.java:56)
> at org.apache.oozie.command.XCommand.call(XCommand.java:287)
> at
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:331)
> at
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:260)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:178)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> 2017-03-06 05:30:52,958 WARN ActionCheckXCommand:523 - SERVER USER[hrt_qa]
> GROUP[-] TOKEN[-] APP[wordcount] JOB[164-170306030147803-oozie-oozi-W]
> ACTION[164-170306030147803-oozie-oozi-W@wc] Exception while executing
> check(). Error Code [JA017], Message[JA017: Unknown hadoop job
> [job_1488762906035_0733] associated with action
> [164-170306030147803-oozie-oozi-W@wc]. Failing this action!]
> org.apache.oozie.action.ActionExecutorException: JA017: Unknown hadoop job
> [job_1488762906035_0733] associated with action
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20278) Install Wizard > Select Services: Ambari warns me that "Ambari Infra is not selected" but it is selected
[ https://issues.apache.org/jira/browse/AMBARI-20278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903455#comment-15903455 ] Hudson commented on AMBARI-20278: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6989 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6989/]) AMBARI-20278. Install Wizard > Select Services: Ambari warns me that (hiveww: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e2220ea8ae60eb02e76761772b9d0144871d24ad]) * (edit) ambari-web/app/controllers/wizard/step4_controller.js > Install Wizard > Select Services: Ambari warns me that "Ambari Infra is not > selected" but it is selected > > > Key: AMBARI-20278 > URL: https://issues.apache.org/jira/browse/AMBARI-20278 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: trunk > > Attachments: AMBARI-20278_a2.patch, > AMBARI-20278_additional_trunk_fix.patch, AMBARI-20278.patch, Screen Shot > 2017-02-27 at 1.43.56 PM.png > > > See attached. > Most likely, I didn't select Ambari Infra originally, but then I cancelled > out of the series of warning popups. > Then I selected Ambari Infra. The warning does not go away. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20322) HDP 3.0 TP - create Service Advisor for Slider
[ https://issues.apache.org/jira/browse/AMBARI-20322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903453#comment-15903453 ] Hudson commented on AMBARI-20322: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6989 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6989/]) AMBARI-20322 HDP 3.0 TP - create Service Advisor for Slider (dsen) (dsen: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e3405474324d021223c3e6bb8353a50528cc0c48]) * (add) ambari-server/src/main/resources/common-services/SLIDER/0.91.0.3.0/service_advisor.py > HDP 3.0 TP - create Service Advisor for Slider > -- > > Key: AMBARI-20322 > URL: https://issues.apache.org/jira/browse/AMBARI-20322 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 3.0.0 >Reporter: Alejandro Fernandez >Assignee: Dmytro Sen > Fix For: 3.0.0 > > Attachments: AMBARI-20322.patch > > > Create a Service Advisor script for Slider in HDP 3.0 Tech Preview. > The Service Advisor must encapsulate all of the logic inherited/overwritten > from HDP 2.0.6 through HDP 2.6 > Slider is being added to the HDP 3.0 stack temporarily in order to unblock > Hive LLAP. Later in the HDP 3.0 release, Slider RPM will be part of YARN. We > may still keep Slider as a Service, but it may move as a component of YARN > instead. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20323) Commands timed-out on ambari host without any error logs
[ https://issues.apache.org/jira/browse/AMBARI-20323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903450#comment-15903450 ] Hudson commented on AMBARI-20323: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6989 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6989/]) AMBARI-20323. Commands timed-out on ambari host without any error logs (echekanskiy: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=da0b7ad8f8974dfdeaf0e99d86339c7562cdd9f2]) * (edit) ambari-agent/src/main/python/ambari_agent/Controller.py * (edit) ambari-agent/src/main/python/ambari_agent/StatusCommandsExecutor.py * (edit) ambari-agent/src/main/python/ambari_agent/main.py * (edit) ambari-agent/src/test/python/ambari_agent/TestActionQueue.py * (edit) ambari-agent/src/main/python/ambari_agent/ActionQueue.py * (edit) ambari-agent/src/test/python/ambari_agent/TestController.py * (edit) ambari-agent/src/test/python/ambari_agent/TestMain.py > Commands timed-out on ambari host without any error logs > > > Key: AMBARI-20323 > URL: https://issues.apache.org/jira/browse/AMBARI-20323 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.5.0 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20323.2.patch, AMBARI-20323.3.patch, > AMBARI-20323.4.patch, AMBARI-20323.5.patch, AMBARI-20323.patch > > > Ambari-agent stop execution commands. It is happend because of threads > blocking due to broken multiprocessing.Queue after killing > StatusCommandsExecutor. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20323) Commands timed-out on ambari host without any error logs
[ https://issues.apache.org/jira/browse/AMBARI-20323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903441#comment-15903441 ] Hudson commented on AMBARI-20323: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1223 (See [https://builds.apache.org/job/Ambari-branch-2.5/1223/]) AMBARI-20323. Commands timed-out on ambari host without any error logs (echekanskiy: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=17ef555940758b73cd09ddcc9fc8a3461604c085]) * (edit) ambari-agent/src/main/python/ambari_agent/StatusCommandsExecutor.py * (edit) ambari-agent/src/test/python/ambari_agent/TestMain.py * (edit) ambari-agent/src/main/python/ambari_agent/Controller.py * (edit) ambari-agent/src/test/python/ambari_agent/TestController.py * (edit) ambari-agent/src/main/python/ambari_agent/ActionQueue.py * (edit) ambari-agent/src/test/python/ambari_agent/TestActionQueue.py * (edit) ambari-agent/src/main/python/ambari_agent/main.py > Commands timed-out on ambari host without any error logs > > > Key: AMBARI-20323 > URL: https://issues.apache.org/jira/browse/AMBARI-20323 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.5.0 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20323.2.patch, AMBARI-20323.3.patch, > AMBARI-20323.4.patch, AMBARI-20323.5.patch, AMBARI-20323.patch > > > Ambari-agent stop execution commands. It is happend because of threads > blocking due to broken multiprocessing.Queue after killing > StatusCommandsExecutor. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20382) Log Search: Web UI Alert tries to use http protocol even if ssl is enabled
[ https://issues.apache.org/jira/browse/AMBARI-20382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-20382: -- Status: Patch Available (was: Open) > Log Search: Web UI Alert tries to use http protocol even if ssl is enabled > -- > > Key: AMBARI-20382 > URL: https://issues.apache.org/jira/browse/AMBARI-20382 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 2.5.0 > > Attachments: AMBARI-20382.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20382) Log Search: Web UI Alert tries to use http protocol even if ssl is enabled
[ https://issues.apache.org/jira/browse/AMBARI-20382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-20382: -- Attachment: AMBARI-20382.patch > Log Search: Web UI Alert tries to use http protocol even if ssl is enabled > -- > > Key: AMBARI-20382 > URL: https://issues.apache.org/jira/browse/AMBARI-20382 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 2.5.0 > > Attachments: AMBARI-20382.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20382) Log Search: Web UI Alert tries to use http protocol even if ssl is enabled
Olivér Szabó created AMBARI-20382: - Summary: Log Search: Web UI Alert tries to use http protocol even if ssl is enabled Key: AMBARI-20382 URL: https://issues.apache.org/jira/browse/AMBARI-20382 Project: Ambari Issue Type: Bug Affects Versions: 2.4.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 2.5.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20379) Error during moving ResourceManager without Tez installed
[ https://issues.apache.org/jira/browse/AMBARI-20379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903393#comment-15903393 ] Hudson commented on AMBARI-20379: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6988 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6988/]) AMBARI-20379. Error during moving ResourceManager without Tez installed (akovalenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=8ce47e0cbd5caaaee7f444ddca1afefafceede1d]) * (edit) ambari-web/test/controllers/main/service/reassign/step4_controller_test.js * (edit) ambari-web/app/controllers/main/service/reassign/step4_controller.js > Error during moving ResourceManager without Tez installed > - > > Key: AMBARI-20379 > URL: https://issues.apache.org/jira/browse/AMBARI-20379 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20379_branch-2.5.patch, AMBARI-20379.patch > > > Run Move Wizard for ResourceManager without Tez installed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-18892) storm DRPC_SERVER kerberos configs duplicate
[ https://issues.apache.org/jira/browse/AMBARI-18892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903388#comment-15903388 ] Robert Levas commented on AMBARI-18892: --- [~forestsissi], sure.. working on it now > storm DRPC_SERVER kerberos configs duplicate > - > > Key: AMBARI-18892 > URL: https://issues.apache.org/jira/browse/AMBARI-18892 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk, 2.4.1 >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk, 3.0.0 > > Attachments: AMBARI-18892_01.patch, AMBARI-18892.patch, storm.png > > > when ambari enables kerberos, add storm service ,nimbus_keytab and > nimbus_principal_name will duplicate -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20379) Error during moving ResourceManager without Tez installed
[ https://issues.apache.org/jira/browse/AMBARI-20379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903362#comment-15903362 ] Hudson commented on AMBARI-20379: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1222 (See [https://builds.apache.org/job/Ambari-branch-2.5/1222/]) AMBARI-20379. Error during moving ResourceManager without Tez installed (akovalenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=c6a9a3ca49559e64858a25d5be916296ccd91c1f]) * (edit) ambari-web/test/controllers/main/service/reassign/step4_controller_test.js * (edit) ambari-web/app/controllers/main/service/reassign/step4_controller.js > Error during moving ResourceManager without Tez installed > - > > Key: AMBARI-20379 > URL: https://issues.apache.org/jira/browse/AMBARI-20379 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20379_branch-2.5.patch, AMBARI-20379.patch > > > Run Move Wizard for ResourceManager without Tez installed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20375) Remove duplicate code from wizard menu
[
https://issues.apache.org/jira/browse/AMBARI-20375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903360#comment-15903360
]
Hadoop QA commented on AMBARI-20375:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12856990/AMBARI-20375.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10946//console
This message is automatically generated.
> Remove duplicate code from wizard menu
> --
>
> Key: AMBARI-20375
> URL: https://issues.apache.org/jira/browse/AMBARI-20375
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20375.patch
>
>
> {{'isStep..Disabled'}} and {{'isStep..Completed'}} may be rewritten as
> computed macros
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20278) Install Wizard > Select Services: Ambari warns me that "Ambari Infra is not selected" but it is selected
[ https://issues.apache.org/jira/browse/AMBARI-20278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903351#comment-15903351 ] Antonenko Alexander commented on AMBARI-20278: -- additional fix committed to trunk > Install Wizard > Select Services: Ambari warns me that "Ambari Infra is not > selected" but it is selected > > > Key: AMBARI-20278 > URL: https://issues.apache.org/jira/browse/AMBARI-20278 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: trunk > > Attachments: AMBARI-20278_a2.patch, > AMBARI-20278_additional_trunk_fix.patch, AMBARI-20278.patch, Screen Shot > 2017-02-27 at 1.43.56 PM.png > > > See attached. > Most likely, I didn't select Ambari Infra originally, but then I cancelled > out of the series of warning popups. > Then I selected Ambari Infra. The warning does not go away. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20322) HDP 3.0 TP - create Service Advisor for Slider
[ https://issues.apache.org/jira/browse/AMBARI-20322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-20322: Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk > HDP 3.0 TP - create Service Advisor for Slider > -- > > Key: AMBARI-20322 > URL: https://issues.apache.org/jira/browse/AMBARI-20322 > Project: Ambari > Issue Type: Story > Components: stacks >Affects Versions: 3.0.0 >Reporter: Alejandro Fernandez >Assignee: Dmytro Sen > Fix For: 3.0.0 > > Attachments: AMBARI-20322.patch > > > Create a Service Advisor script for Slider in HDP 3.0 Tech Preview. > The Service Advisor must encapsulate all of the logic inherited/overwritten > from HDP 2.0.6 through HDP 2.6 > Slider is being added to the HDP 3.0 stack temporarily in order to unblock > Hive LLAP. Later in the HDP 3.0 release, Slider RPM will be part of YARN. We > may still keep Slider as a Service, but it may move as a component of YARN > instead. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20323) Commands timed-out on ambari host without any error logs
[ https://issues.apache.org/jira/browse/AMBARI-20323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Chekanskiy updated AMBARI-20323: --- Resolution: Fixed Status: Resolved (was: Patch Available) 8ce47e0..da0b7ad trunk -> trunk c6a9a3c..17ef555 branch-2.5 -> branch-2.5 > Commands timed-out on ambari host without any error logs > > > Key: AMBARI-20323 > URL: https://issues.apache.org/jira/browse/AMBARI-20323 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.5.0 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20323.2.patch, AMBARI-20323.3.patch, > AMBARI-20323.4.patch, AMBARI-20323.5.patch, AMBARI-20323.patch > > > Ambari-agent stop execution commands. It is happend because of threads > blocking due to broken multiprocessing.Queue after killing > StatusCommandsExecutor. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20381) User is not able to import workflows, coordinators and bundles
Supreeth Sharma created AMBARI-20381:
Summary: User is not able to import workflows, coordinators and
bundles
Key: AMBARI-20381
URL: https://issues.apache.org/jira/browse/AMBARI-20381
Project: Ambari
Issue Type: Bug
Components: ambari-views
Affects Versions: 2.5.0
Reporter: Supreeth Sharma
Priority: Blocker
Fix For: 2.5.0
User is not able to import workflows, coordinators and bundles. Seeing below
error in UI console.log
{code}
TypeError: Cannot read property 'workflow-app' of null
at n.processWorkflowXml (oozie-designer-89dda89….js:9)
at n.importWorkflow (oozie-designer-89dda89….js:9)
at n.importWorkflowFromString (oozie-designer-89dda89….js:3)
at n. (oozie-designer-89dda89….js:3)
at y (vendor-b25c8db….js:19)
at b (vendor-b25c8db….js:19)
at g (vendor-b25c8db….js:19)
at vendor-b25c8db….js:13
at invoke (vendor-b25c8db….js:5)
at n.flush (vendor-b25c8db….js:5)
{code}
Facing the same issue while importing the asset from hdfs as well.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20349) When SPNEGO authentication is enabled for Hadoop in a cluster with NN HA, PXF Process alert fails
[
https://issues.apache.org/jira/browse/AMBARI-20349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903302#comment-15903302
]
Hudson commented on AMBARI-20349:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6987 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6987/])
AMBARI-20349. When SPNEGO authentication is enabled for Hadoop in a (rlevas:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=a1012057452fde3f4b488dd1e0ebb83069fb29da])
* (edit)
ambari-server/src/main/resources/common-services/PXF/3.0.0/package/alerts/api_status.py
> When SPNEGO authentication is enabled for Hadoop in a cluster with NN HA, PXF
> Process alert fails
> -
>
> Key: AMBARI-20349
> URL: https://issues.apache.org/jira/browse/AMBARI-20349
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: PHD, PXF, kerberos
> Fix For: 2.5.0
>
> Attachments: AMBARI-20349_branch-2.5_01.patch,
> AMBARI-20349_trunk_01.patch
>
>
> When SPNEGO authentication is enabled for Hadoop in a cluster where NN HA is
> enabled, PXF Process alert fails with the following errors in the
> ambari-agent.log file
> {noformat}
> ERROR 2017-03-07 18:03:58,417 jmx.py:44 - Getting jmx metrics from NN failed.
> URL:
> http://c6401.ambari.apache.org:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesy
> stem
> Traceback (most recent call last):
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py",
> line 41, in get_value_from_jmx
> data_dict = json.loads(data)
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/__init__.py", line
> 307, in loads
> return _default_decoder.decode(s)
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line
> 335, in decode
> obj, end = self.raw_decode(s, idx=_w(s, 0).end())
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line
> 353, in raw_decode
> raise ValueError("No JSON object could be decoded")
> ValueError: No JSON object could be decoded
> INFO 2017-03-07 18:04:02,769 logger.py:71 - call['ambari-sudo.sh su hdfs -l
> -s /bin/bash -c 'curl --negotiate -u : -s
> '"'"'http://c6402.ambari.apache.org:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesystem'"'"'
> 1>/tmp/tmphTXg76 2>/tmp/tmp5bm2nM''] {'quiet': False}
> INFO 2017-03-07 18:04:02,797 logger.py:71 - call returned (0, '')
> ERROR 2017-03-07 18:04:02,798 jmx.py:44 - Getting jmx metrics from NN failed.
> URL:
> http://c6402.ambari.apache.org:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesystem
> Traceback (most recent call last):
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py",
> line 41, in get_value_from_jmx
> data_dict = json.loads(data)
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/__init__.py", line
> 307, in loads
> return _default_decoder.decode(s)
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line
> 335, in decode
> obj, end = self.raw_decode(s, idx=_w(s, 0).end())
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line
> 353, in raw_decode
> raise ValueError("No JSON object could be decoded")
> ValueError: No JSON object could be decoded
> {noformat}
> *Cause*
> During the test for the {{PXF Process}} alert, the Active NN is found using a
> JMX call. This call requires SPNEGO authentication since SPNEGO
> authentication is turned on for the Hadoop web interfaces. However, a valid
> Kerberos ticket is not found in the configured user's Kerberos ticket cache.
> In this case, the configured users is the HDFS user - which technically is
> not necessary.
> This occurs in
> {code:title=common-services/PXF/3.0.0/package/alerts/api_status.py:137}
> if CLUSTER_ENV_SECURITY in configurations and
> configurations[CLUSTER_ENV_SECURITY].lower() == "true":
> if 'dfs.nameservices' in configurations[HDFS_SITE]:
> namenode_address =
> get_active_namenode(ConfigDictionary(configurations[HDFS_SITE]),
> configurations[CLUSTER_ENV_SECURITY], configurations[HADOOP_ENV_HDFS_USER])[1]
> else:
> namenode_address =
> configurations[HDFS_SITE]['dfs.namenode.http-address']
> token = _get_delegation_token(namenode_address,
> configurations[HADOOP_ENV_HDFS_USER],
>
> configurations[HADOOP_ENV_HDFS_USER_KEYTAB],
>
> configurations[HADOOP_ENV_HDFS_PRINCIPAL_NAME],
> None)
> commonPXFHeaders.update({"X-GP-TOKEN": token})
> {code}
> Inside
[jira] [Commented] (AMBARI-20362) Enable Authentication in Zeppelin out of Box
[ https://issues.apache.org/jira/browse/AMBARI-20362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903299#comment-15903299 ] Hudson commented on AMBARI-20362: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6987 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6987/]) AMBARI-20362: Enable Authentication in Zeppelin out of Box (Prabhjyot (renjith.kamath: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=3db5addb9322b944ed8cc33264ffb505241ba281]) * (edit) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/configuration/zeppelin-shiro-ini.xml > Enable Authentication in Zeppelin out of Box > > > Key: AMBARI-20362 > URL: https://issues.apache.org/jira/browse/AMBARI-20362 > Project: Ambari > Issue Type: Bug > Components: blueprints >Affects Versions: 2.5.0 >Reporter: Kshitij Badani >Assignee: Prabhjyot Singh > Fix For: 2.5.0 > > Attachments: AMBARI-20362_brach-2.5_v1.patch > > > Right now Zeppelin does not have any authentication enabled out of the box. > As the security sensitivity is ever increasing we should enable > authentication by default. > We can use the same account Ambari Admin uses to authenticate with Zeppelin. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20377) Usability: Hostname hover of master is not discoverable in Summary section
[ https://issues.apache.org/jira/browse/AMBARI-20377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903297#comment-15903297 ] Hudson commented on AMBARI-20377: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6987 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6987/]) AMBARI-20377. Usability: Hostname hover of master is not discoverable in (hiveww: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7ff9bd429a1273074d6b8c1edf8b170d3f77ee0d]) * (edit) ambari-web/app/views/main/service/service.js * (edit) ambari-web/app/views/main/service/services/hdfs.js * (edit) ambari-web/app/views/main/service/info/components_list_view.js * (edit) ambari-web/test/views/main/service/services/hdfs_test.js * (edit) ambari-web/app/templates/main/service/info/summary/master_components.hbs * (edit) ambari-web/test/views/main/service/info/component_list_view_test.js > Usability: Hostname hover of master is not discoverable in Summary section > -- > > Key: AMBARI-20377 > URL: https://issues.apache.org/jira/browse/AMBARI-20377 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 3.0.0 > > Attachments: AMBARI-20377.patch > > > Currently, if you hover over a master component in Services > Summary, you > can see the hostname (for example, hover over NameNode). > The current hover takes a while to show, and is more of a title/alt hover vs. > a tooltip (for example, like hover on the Service status icons). Should > switch from title/alt hover to tooltip hover like Service status icons. It > shows faster and looks better. This will make hostname more discoverable. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20376) While Moving Namenode via Move Master wizard, datanodes reported as down
[
https://issues.apache.org/jira/browse/AMBARI-20376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903296#comment-15903296
]
Hudson commented on AMBARI-20376:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6987 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6987/])
AMBARI-20376. While Moving Namenode via Move Master wizard, datanodes (hiveww:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=647ff84b0b85b04bd350ddb268fde56b0778cf2b])
* (edit) ambari-web/app/messages.js
* (edit) ambari-web/app/controllers/main/service/reassign/step6_controller.js
* (edit) ambari-web/app/mixins/wizard/wizardProgressPageController.js
> While Moving Namenode via Move Master wizard, datanodes reported as down
>
>
> Key: AMBARI-20376
> URL: https://issues.apache.org/jira/browse/AMBARI-20376
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20376.patch
>
>
> While Moving Namenode via Move Master wizard, datanodes reported as down
> while starting ATS.
> Seeing this in a couple of splits today. ATS fails to start showing there are
> no live datanodes
> {code}
> {
> "RemoteException": {
> "exception": "RetriableException",
> "javaClassName": "org.apache.hadoop.ipc.RetriableException",
> "message": "org.apache.hadoop.hdfs.server.namenode.SafeModeException:
> Cannot set permission for /ats/done. Name node is in safe mode.\nThe reported
> blocks 934 has reached the threshold 0.9900 of total blocks 934. The number
> of live datanodes 3 has reached the minimum number 0. In safe mode extension.
> Safe mode will be turned off automatically in 21 seconds."
> }
> }
> {code}
> The step before ATS start, starts datanode explicitly. On retry ATS will
> possibly come up. But no retries were needed before
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20359) Not able to import workflow with fs action node
[
https://issues.apache.org/jira/browse/AMBARI-20359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903294#comment-15903294
]
Hudson commented on AMBARI-20359:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6987 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6987/])
AMBARI-20359. Not able to import workflow with fs action node (Madhan
(pallavkul:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=fbcf24f71a1ec1ea21cc236bab36b205822ec4e6])
* (edit)
contrib/views/wfmanager/src/main/resources/ui/app/domain/workflow-importer.js
> Not able to import workflow with fs action node
> ---
>
> Key: AMBARI-20359
> URL: https://issues.apache.org/jira/browse/AMBARI-20359
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Supreeth Sharma
>Assignee: M Madhan Mohan Reddy
>Priority: Critical
> Labels: WFD, WFM
> Fix For: 2.5.0
>
> Attachments: AMBARI-20359_trunk.patch
>
>
> Not able to import workflow with fs action node.
> Seeing below error in UI console log :
> {code}
> Uncaught TypeError: Cannot read property '0' of undefined
> at n.handleImport
> (http://172.27.32.136:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-35b7698efcbc6722853be0273625a4ef.js:7:28237)
> at n [as handleImport]
> (http://172.27.32.136:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-b25c8db62aa353ea5ab0a4f9e228c623.js:11:18180)
> at n.handleImportNode
> (http://172.27.32.136:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-35b7698efcbc6722853be0273625a4ef.js:9:13846)
> at
> http://172.27.32.136:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-35b7698efcbc6722853be0273625a4ef.js:9:27314
> at Array.forEach (native)
> at
> http://172.27.32.136:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-35b7698efcbc6722853be0273625a4ef.js:9:27286
> at Array.forEach (native)
> at n.setupNodeMap
> (http://172.27.32.136:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-35b7698efcbc6722853be0273625a4ef.js:9:27188)
> at n.processWorkflowXml
> (http://172.27.32.136:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-35b7698efcbc6722853be0273625a4ef.js:9:26231)
> at n.importWorkflow
> (http://172.27.32.136:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-35b7698efcbc6722853be0273625a4ef.js:9:25548)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20349) When SPNEGO authentication is enabled for Hadoop in a cluster with NN HA, PXF Process alert fails
[
https://issues.apache.org/jira/browse/AMBARI-20349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903285#comment-15903285
]
Hudson commented on AMBARI-20349:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1221 (See
[https://builds.apache.org/job/Ambari-branch-2.5/1221/])
AMBARI-20349. When SPNEGO authentication is enabled for Hadoop in a (rlevas:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=245fd5cf3689097fdcdde6a75c39de9d38e0bde8])
* (edit)
ambari-server/src/main/resources/common-services/PXF/3.0.0/package/alerts/api_status.py
> When SPNEGO authentication is enabled for Hadoop in a cluster with NN HA, PXF
> Process alert fails
> -
>
> Key: AMBARI-20349
> URL: https://issues.apache.org/jira/browse/AMBARI-20349
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: PHD, PXF, kerberos
> Fix For: 2.5.0
>
> Attachments: AMBARI-20349_branch-2.5_01.patch,
> AMBARI-20349_trunk_01.patch
>
>
> When SPNEGO authentication is enabled for Hadoop in a cluster where NN HA is
> enabled, PXF Process alert fails with the following errors in the
> ambari-agent.log file
> {noformat}
> ERROR 2017-03-07 18:03:58,417 jmx.py:44 - Getting jmx metrics from NN failed.
> URL:
> http://c6401.ambari.apache.org:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesy
> stem
> Traceback (most recent call last):
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py",
> line 41, in get_value_from_jmx
> data_dict = json.loads(data)
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/__init__.py", line
> 307, in loads
> return _default_decoder.decode(s)
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line
> 335, in decode
> obj, end = self.raw_decode(s, idx=_w(s, 0).end())
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line
> 353, in raw_decode
> raise ValueError("No JSON object could be decoded")
> ValueError: No JSON object could be decoded
> INFO 2017-03-07 18:04:02,769 logger.py:71 - call['ambari-sudo.sh su hdfs -l
> -s /bin/bash -c 'curl --negotiate -u : -s
> '"'"'http://c6402.ambari.apache.org:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesystem'"'"'
> 1>/tmp/tmphTXg76 2>/tmp/tmp5bm2nM''] {'quiet': False}
> INFO 2017-03-07 18:04:02,797 logger.py:71 - call returned (0, '')
> ERROR 2017-03-07 18:04:02,798 jmx.py:44 - Getting jmx metrics from NN failed.
> URL:
> http://c6402.ambari.apache.org:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesystem
> Traceback (most recent call last):
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py",
> line 41, in get_value_from_jmx
> data_dict = json.loads(data)
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/__init__.py", line
> 307, in loads
> return _default_decoder.decode(s)
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line
> 335, in decode
> obj, end = self.raw_decode(s, idx=_w(s, 0).end())
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line
> 353, in raw_decode
> raise ValueError("No JSON object could be decoded")
> ValueError: No JSON object could be decoded
> {noformat}
> *Cause*
> During the test for the {{PXF Process}} alert, the Active NN is found using a
> JMX call. This call requires SPNEGO authentication since SPNEGO
> authentication is turned on for the Hadoop web interfaces. However, a valid
> Kerberos ticket is not found in the configured user's Kerberos ticket cache.
> In this case, the configured users is the HDFS user - which technically is
> not necessary.
> This occurs in
> {code:title=common-services/PXF/3.0.0/package/alerts/api_status.py:137}
> if CLUSTER_ENV_SECURITY in configurations and
> configurations[CLUSTER_ENV_SECURITY].lower() == "true":
> if 'dfs.nameservices' in configurations[HDFS_SITE]:
> namenode_address =
> get_active_namenode(ConfigDictionary(configurations[HDFS_SITE]),
> configurations[CLUSTER_ENV_SECURITY], configurations[HADOOP_ENV_HDFS_USER])[1]
> else:
> namenode_address =
> configurations[HDFS_SITE]['dfs.namenode.http-address']
> token = _get_delegation_token(namenode_address,
> configurations[HADOOP_ENV_HDFS_USER],
>
> configurations[HADOOP_ENV_HDFS_USER_KEYTAB],
>
> configurations[HADOOP_ENV_HDFS_PRINCIPAL_NAME],
> None)
> commonPXFHeaders.update({"X-GP-TOKEN": token})
> {code}
> Inside the
[jira] [Commented] (AMBARI-20376) While Moving Namenode via Move Master wizard, datanodes reported as down
[
https://issues.apache.org/jira/browse/AMBARI-20376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903282#comment-15903282
]
Hudson commented on AMBARI-20376:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1221 (See
[https://builds.apache.org/job/Ambari-branch-2.5/1221/])
AMBARI-20376. While Moving Namenode via Move Master wizard, datanodes (hiveww:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=221ad2830f1ce3f82508ac92a226f8d4b784fd5c])
* (edit) ambari-web/app/messages.js
* (edit) ambari-web/app/mixins/wizard/wizardProgressPageController.js
* (edit) ambari-web/app/controllers/main/service/reassign/step6_controller.js
> While Moving Namenode via Move Master wizard, datanodes reported as down
>
>
> Key: AMBARI-20376
> URL: https://issues.apache.org/jira/browse/AMBARI-20376
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20376.patch
>
>
> While Moving Namenode via Move Master wizard, datanodes reported as down
> while starting ATS.
> Seeing this in a couple of splits today. ATS fails to start showing there are
> no live datanodes
> {code}
> {
> "RemoteException": {
> "exception": "RetriableException",
> "javaClassName": "org.apache.hadoop.ipc.RetriableException",
> "message": "org.apache.hadoop.hdfs.server.namenode.SafeModeException:
> Cannot set permission for /ats/done. Name node is in safe mode.\nThe reported
> blocks 934 has reached the threshold 0.9900 of total blocks 934. The number
> of live datanodes 3 has reached the minimum number 0. In safe mode extension.
> Safe mode will be turned off automatically in 21 seconds."
> }
> }
> {code}
> The step before ATS start, starts datanode explicitly. On retry ATS will
> possibly come up. But no retries were needed before
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20362) Enable Authentication in Zeppelin out of Box
[ https://issues.apache.org/jira/browse/AMBARI-20362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903278#comment-15903278 ] Hudson commented on AMBARI-20362: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1221 (See [https://builds.apache.org/job/Ambari-branch-2.5/1221/]) AMBARI-20362: Enable Authentication in Zeppelin out of Box (Prabhjyot (renjith.kamath: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=47f924334b850e572298fbd8700a993cdb19065c]) * (edit) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/configuration/zeppelin-shiro-ini.xml > Enable Authentication in Zeppelin out of Box > > > Key: AMBARI-20362 > URL: https://issues.apache.org/jira/browse/AMBARI-20362 > Project: Ambari > Issue Type: Bug > Components: blueprints >Affects Versions: 2.5.0 >Reporter: Kshitij Badani >Assignee: Prabhjyot Singh > Fix For: 2.5.0 > > Attachments: AMBARI-20362_brach-2.5_v1.patch > > > Right now Zeppelin does not have any authentication enabled out of the box. > As the security sensitivity is ever increasing we should enable > authentication by default. > We can use the same account Ambari Admin uses to authenticate with Zeppelin. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20359) Not able to import workflow with fs action node
[
https://issues.apache.org/jira/browse/AMBARI-20359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903275#comment-15903275
]
Hudson commented on AMBARI-20359:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1221 (See
[https://builds.apache.org/job/Ambari-branch-2.5/1221/])
AMBARI-20359. Not able to import workflow with fs action node (Madhan
(pallavkul:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=c476629345c05896a445f005e94f2ab605510362])
* (edit)
contrib/views/wfmanager/src/main/resources/ui/app/domain/workflow-importer.js
> Not able to import workflow with fs action node
> ---
>
> Key: AMBARI-20359
> URL: https://issues.apache.org/jira/browse/AMBARI-20359
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Supreeth Sharma
>Assignee: M Madhan Mohan Reddy
>Priority: Critical
> Labels: WFD, WFM
> Fix For: 2.5.0
>
> Attachments: AMBARI-20359_trunk.patch
>
>
> Not able to import workflow with fs action node.
> Seeing below error in UI console log :
> {code}
> Uncaught TypeError: Cannot read property '0' of undefined
> at n.handleImport
> (http://172.27.32.136:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-35b7698efcbc6722853be0273625a4ef.js:7:28237)
> at n [as handleImport]
> (http://172.27.32.136:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/vendor-b25c8db62aa353ea5ab0a4f9e228c623.js:11:18180)
> at n.handleImportNode
> (http://172.27.32.136:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-35b7698efcbc6722853be0273625a4ef.js:9:13846)
> at
> http://172.27.32.136:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-35b7698efcbc6722853be0273625a4ef.js:9:27314
> at Array.forEach (native)
> at
> http://172.27.32.136:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-35b7698efcbc6722853be0273625a4ef.js:9:27286
> at Array.forEach (native)
> at n.setupNodeMap
> (http://172.27.32.136:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-35b7698efcbc6722853be0273625a4ef.js:9:27188)
> at n.processWorkflowXml
> (http://172.27.32.136:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-35b7698efcbc6722853be0273625a4ef.js:9:26231)
> at n.importWorkflow
> (http://172.27.32.136:8080/views/WORKFLOW_MANAGER/1.0.0/WFD/assets/oozie-designer-35b7698efcbc6722853be0273625a4ef.js:9:25548)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20379) Error during moving ResourceManager without Tez installed
[ https://issues.apache.org/jira/browse/AMBARI-20379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903266#comment-15903266 ] Aleksandr Kovalenko commented on AMBARI-20379: -- committed to trunk and branch-2.5 > Error during moving ResourceManager without Tez installed > - > > Key: AMBARI-20379 > URL: https://issues.apache.org/jira/browse/AMBARI-20379 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20379_branch-2.5.patch, AMBARI-20379.patch > > > Run Move Wizard for ResourceManager without Tez installed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20379) Error during moving ResourceManager without Tez installed
[ https://issues.apache.org/jira/browse/AMBARI-20379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-20379: - Resolution: Fixed Status: Resolved (was: Patch Available) > Error during moving ResourceManager without Tez installed > - > > Key: AMBARI-20379 > URL: https://issues.apache.org/jira/browse/AMBARI-20379 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20379_branch-2.5.patch, AMBARI-20379.patch > > > Run Move Wizard for ResourceManager without Tez installed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20378) LogFeeder: Add de-duplication support
[
https://issues.apache.org/jira/browse/AMBARI-20378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-20378:
--
Attachment: AMBARI-20378.patch
> LogFeeder: Add de-duplication support
> -
>
> Key: AMBARI-20378
> URL: https://issues.apache.org/jira/browse/AMBARI-20378
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.5.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: trunk
>
> Attachments: AMBARI-20378.patch
>
>
> Add de-duplication support to logfeeder.
> For handling duplications, it will be an LRU cache for every input.
> It can be set up at input config block. For example (the values below are the
> defaults):
> {code:java}
> {
> "input": [
> {
> ...
> "cache_enabled" : "true",
> "cache_size" : "100",
> "cache_dedup_interval" : "1000",
> "cache_last_dedup_enabled" : "false",
> "cache_key_field" : "log_message"
> }
> ] ...
> {code}
> {{cache_dedup_interval}} : if the interval (timestamp - date difference) is
> not reached between 2 log messages (same content), then the new log will be
> dropped.
> {{cache_last_dedup_enabled}}: if its enabled and the new log message is the
> same as the last one, the new log will be dropped. (dedup interval wont have
> impact on that feature)
> {{cache_key_field}} : field of the log message which will be compared and
> stored in the cache (as keys)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20378) LogFeeder: Add de-duplication support
[
https://issues.apache.org/jira/browse/AMBARI-20378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-20378:
--
Attachment: (was: AMBARI-20378.patch)
> LogFeeder: Add de-duplication support
> -
>
> Key: AMBARI-20378
> URL: https://issues.apache.org/jira/browse/AMBARI-20378
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.5.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: trunk
>
> Attachments: AMBARI-20378.patch
>
>
> Add de-duplication support to logfeeder.
> For handling duplications, it will be an LRU cache for every input.
> It can be set up at input config block. For example (the values below are the
> defaults):
> {code:java}
> {
> "input": [
> {
> ...
> "cache_enabled" : "true",
> "cache_size" : "100",
> "cache_dedup_interval" : "1000",
> "cache_last_dedup_enabled" : "false",
> "cache_key_field" : "log_message"
> }
> ] ...
> {code}
> {{cache_dedup_interval}} : if the interval (timestamp - date difference) is
> not reached between 2 log messages (same content), then the new log will be
> dropped.
> {{cache_last_dedup_enabled}}: if its enabled and the new log message is the
> same as the last one, the new log will be dropped. (dedup interval wont have
> impact on that feature)
> {{cache_key_field}} : field of the log message which will be compared and
> stored in the cache (as keys)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
