[jira] [Updated] (AMBARI-21123) Part Two: Specify the script directly in alert target for script-based alert dispatchers

[Yao Lei (JIRA)]

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

Yao Lei updated AMBARI-21123:
-
Affects Version/s: trunk

> Part Two: Specify the script directly in alert target for script-based alert 
> dispatchers
> 
>
> Key: AMBARI-21123
> URL: https://issues.apache.org/jira/browse/AMBARI-21123
> Project: Ambari
>  Issue Type: Technical task
>  Components: alerts, ambari-web
>Affects Versions: trunk
>Reporter: Yao Lei
>Assignee: Yao Lei
> Fix For: 3.0.0
>
> Attachments: AMBARI-21123.patch, script_alert_notification_1.png, 
> script_alert_notification_2.png
>
>
> Web Codes Part
> This patch amis to support creating alert target  that inclueds property 
> *ambari.dispatch-property.script.filename*  on web UI



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

[jira] [Updated] (AMBARI-21122) Part One: Specify the script directly in alert target for script-based alert dispatchers

[Yao Lei (JIRA)]

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

Yao Lei updated AMBARI-21122:
-
Affects Version/s: trunk

> Part One:  Specify the script directly in alert target for script-based alert 
> dispatchers
> -
>
> Key: AMBARI-21122
> URL: https://issues.apache.org/jira/browse/AMBARI-21122
> Project: Ambari
>  Issue Type: Technical task
>Affects Versions: trunk
>Reporter: Yao Lei
>Assignee: Yao Lei
> Fix For: 3.0.0
>
> Attachments: AMBARI-21122.patch
>
>
> *Jave Codes Part*
> This patch will support using property  
> *ambari.dispatch-property.script.filename* in alert target  to tell 
> AlertScriptDispatcher to lookup script by filename,default in 
> /var/lib/ambari-server/resources/scripts directory. We can also change this  
> directory in ambari.properties by *ambari.dispatch-property.script.directory* 
> property.
> Execute a command manually like following to create an alert target that 
> includes this property:
> {code}
> POST api/v1/alert_targets
> {
>   "AlertTarget": {
> "name": "syslogger",
> "description": "Syslog Target",
> "notification_type": "ALERT_SCRIPT",
> "global": false,
> "groups":[1,3]
> "alert_states":["WARNING","CRITICAL","UNKNOWN"],
> "properties": {
>"ambari.dispatch-property.script.filename": "foo.py"
> }
>   }
> }
> {code}



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

[jira] [Commented] (AMBARI-21118) HDP + HDF cluster cannot save configs for Storm when Streamline is installed due to missing configs

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-21118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16025623#comment-16025623
 ] 

Hudson commented on AMBARI-21118:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1549 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/1549/])
AMBARI-21118. HDP + HDF cluster cannot save configs for Storm when (afernandez: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=75de63d35134626472eb5ca7adeccc8144712f18])
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/STORM/metainfo.xml
* (edit) 
ambari-server/src/main/resources/common-services/STORM/1.1.0/configuration/storm-site.xml


> HDP + HDF cluster cannot save configs for Storm when Streamline is installed 
> due to missing configs
> ---
>
> Key: AMBARI-21118
> URL: https://issues.apache.org/jira/browse/AMBARI-21118
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.1
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.2
>
> Attachments: AMBARI-21118.2.5-maint.patch
>
>
> STR:
> * Install Ambari 2.5.1 with HDP 2.6.1 plus Storm and Streamline (from HDF 
> MPack)
> * Attempt to change configs for Storm
> Ambari: 2.5.1.0-146
> HDF: 3.0.0.0-358
> HDP: 2.6.1.0-110
> This is happening because Storm does not have Streamline as a dependent 
> service, so the UI does not pass the Streamline configs to the 
> recommendations endpoint when calling Stack Advisor for Storm.
> {code}
> '), ('yarn.scheduler.capacity.root.accessible-node-labels', '*'), 
> ('yarn.scheduler.capacity.root.capacity', '100'), 
> ('yarn.scheduler.capacity.maximum-am-resource-percent', '0.2'), 
> ('yarn.scheduler.capacity.maximum-applications', '1'), 
> ('yarn.scheduler.capacity.root.de
> fault.user-limit-factor', '1'), 
> ('yarn.scheduler.capacity.node-locality-delay', '40'), 
> ('yarn.scheduler.capacity.root.default.acl_submit_applications', 'yarn'), 
> ('yarn.scheduler.capacity.root.default.state', 'RUNNING'), 
> ('yarn.scheduler.capacity.root.default.capacity', '1
> 00'), ('yarn.scheduler.capacity.root.acl_administer_queue', 'yarn'), 
> ('yarn.scheduler.capacity.root.default.maximum-capacity', '100'), 
> ('yarn.scheduler.capacity.root.queues', 'default'), 
> ('yarn.scheduler.capacity.root.acl_administer_jobs', 'yarn'), ('', ''), 
> ('yarn.schedu
> ler.capacity.root.default.acl_administer_jobs', 'yarn'), 
> ('yarn.scheduler.capacity.resource-calculator', 
> 'org.apache.hadoop.yarn.util.resource.DefaultResourceCalculator')]
> Error occured in stack advisor.
> Error details: argument of type 'NoneType' is not iterable
> 24 May 2017 19:43:17,686  INFO [ambari-client-thread-31] 
> StackAdvisorRunner:71 - advisor script stderr: Traceback (most recent 
> call last):
>   File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 166, 
> in 
> main(sys.argv)
>   File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 116, 
> in main
> result = stackAdvisor.recommendConfigurations(services, hosts)
>   File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py", 
> line 775, in recommendConfigurations
> calculation(configurations, clusterSummary, services, hosts)
>   File 
> "/var/lib/ambari-server/resources/scripts/./../stacks/HDP/2.6/services/stack_advisor.py",
>  line 68, in recommendSTORMConfigurations
> _streamline_principal_name = streamline_env['streamline_principal_name'] 
> if 'streamline_principal_name' in streamline_env else None
> TypeError: argument of type 'NoneType' is not iterable
> 24 May 2017 19:43:17,686  WARN [ambari-client-thread-31] 
> AbstractResourceProvider:97 - Error occured during recommendation
> org.apache.ambari.server.api.services.stackadvisor.StackAdvisorException: 
> Stack Advisor reported an error: TypeError: argument of type 'NoneType' is 
> not iterable
> StdOut file: /var/run/ambari-server/stack-recommendations/30/stackadvisor.out
> StdErr file: /var/run/ambari-server/stack-recommendations/30/stackadvisor.err
> at 
> org.apache.ambari.server.api.services.stackadvisor.StackAdvisorRunner.runScript(StackAdvisorRunner.java:96)
> at 
> org.apache.ambari.server.api.services.stackadvisor.commands.StackAdvisorCommand.invoke(StackAdvisorCommand.java:295)
> at 
> org.apache.ambari.server.api.services.stackadvisor.StackAdvisorHelper.recommend(StackAdvisorHelper.java:113)
> at 
> org.apache.ambari.server.controller.internal.RecommendationResourceProvider.createResources(RecommendationResourceProvider.java:92)
> at 
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:298)
> at 
> 

[jira] [Commented] (AMBARI-21131) Add NIFI JAAS Config StackFeatures to HDP StackFeatures

[Jayush Luniya (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-21131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16025616#comment-16025616
 ] 

Jayush Luniya commented on AMBARI-21131:


Trunk
commit 145a80294706f22914c043ebbb8a8d0b5d7d52ee
Author: Jayush Luniya 
Date:   Thu May 25 17:51:16 2017 -0700

AMBARI-21131: Add NIFI JAAS Config StackFeatures to HDP StackFeatures 
(jluniya)

> Add NIFI JAAS Config StackFeatures to HDP StackFeatures
> ---
>
> Key: AMBARI-21131
> URL: https://issues.apache.org/jira/browse/AMBARI-21131
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: 2.5.2
>
> Attachments: AMBARI-21131.patch
>
>




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

[jira] [Commented] (AMBARI-21131) Add NIFI JAAS Config StackFeatures to HDP StackFeatures

[Mahadev konar (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-21131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16025610#comment-16025610
 ] 

Mahadev konar commented on AMBARI-21131:


+1 for the patch.

> Add NIFI JAAS Config StackFeatures to HDP StackFeatures
> ---
>
> Key: AMBARI-21131
> URL: https://issues.apache.org/jira/browse/AMBARI-21131
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: 2.5.2
>
> Attachments: AMBARI-21131.patch
>
>




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

[jira] [Resolved] (AMBARI-21118) HDP + HDF cluster cannot save configs for Storm when Streamline is installed due to missing configs

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez resolved AMBARI-21118.
--
Resolution: Fixed

Pushed to branch-2.5, commit 75de63d35134626472eb5ca7adeccc8144712f18

trunk, commit f7c04148c1214277cf39479d9a0306850c034ef9

> HDP + HDF cluster cannot save configs for Storm when Streamline is installed 
> due to missing configs
> ---
>
> Key: AMBARI-21118
> URL: https://issues.apache.org/jira/browse/AMBARI-21118
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.1
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.2
>
> Attachments: AMBARI-21118.2.5-maint.patch
>
>
> STR:
> * Install Ambari 2.5.1 with HDP 2.6.1 plus Storm and Streamline (from HDF 
> MPack)
> * Attempt to change configs for Storm
> Ambari: 2.5.1.0-146
> HDF: 3.0.0.0-358
> HDP: 2.6.1.0-110
> This is happening because Storm does not have Streamline as a dependent 
> service, so the UI does not pass the Streamline configs to the 
> recommendations endpoint when calling Stack Advisor for Storm.
> {code}
> '), ('yarn.scheduler.capacity.root.accessible-node-labels', '*'), 
> ('yarn.scheduler.capacity.root.capacity', '100'), 
> ('yarn.scheduler.capacity.maximum-am-resource-percent', '0.2'), 
> ('yarn.scheduler.capacity.maximum-applications', '1'), 
> ('yarn.scheduler.capacity.root.de
> fault.user-limit-factor', '1'), 
> ('yarn.scheduler.capacity.node-locality-delay', '40'), 
> ('yarn.scheduler.capacity.root.default.acl_submit_applications', 'yarn'), 
> ('yarn.scheduler.capacity.root.default.state', 'RUNNING'), 
> ('yarn.scheduler.capacity.root.default.capacity', '1
> 00'), ('yarn.scheduler.capacity.root.acl_administer_queue', 'yarn'), 
> ('yarn.scheduler.capacity.root.default.maximum-capacity', '100'), 
> ('yarn.scheduler.capacity.root.queues', 'default'), 
> ('yarn.scheduler.capacity.root.acl_administer_jobs', 'yarn'), ('', ''), 
> ('yarn.schedu
> ler.capacity.root.default.acl_administer_jobs', 'yarn'), 
> ('yarn.scheduler.capacity.resource-calculator', 
> 'org.apache.hadoop.yarn.util.resource.DefaultResourceCalculator')]
> Error occured in stack advisor.
> Error details: argument of type 'NoneType' is not iterable
> 24 May 2017 19:43:17,686  INFO [ambari-client-thread-31] 
> StackAdvisorRunner:71 - advisor script stderr: Traceback (most recent 
> call last):
>   File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 166, 
> in 
> main(sys.argv)
>   File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 116, 
> in main
> result = stackAdvisor.recommendConfigurations(services, hosts)
>   File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py", 
> line 775, in recommendConfigurations
> calculation(configurations, clusterSummary, services, hosts)
>   File 
> "/var/lib/ambari-server/resources/scripts/./../stacks/HDP/2.6/services/stack_advisor.py",
>  line 68, in recommendSTORMConfigurations
> _streamline_principal_name = streamline_env['streamline_principal_name'] 
> if 'streamline_principal_name' in streamline_env else None
> TypeError: argument of type 'NoneType' is not iterable
> 24 May 2017 19:43:17,686  WARN [ambari-client-thread-31] 
> AbstractResourceProvider:97 - Error occured during recommendation
> org.apache.ambari.server.api.services.stackadvisor.StackAdvisorException: 
> Stack Advisor reported an error: TypeError: argument of type 'NoneType' is 
> not iterable
> StdOut file: /var/run/ambari-server/stack-recommendations/30/stackadvisor.out
> StdErr file: /var/run/ambari-server/stack-recommendations/30/stackadvisor.err
> at 
> org.apache.ambari.server.api.services.stackadvisor.StackAdvisorRunner.runScript(StackAdvisorRunner.java:96)
> at 
> org.apache.ambari.server.api.services.stackadvisor.commands.StackAdvisorCommand.invoke(StackAdvisorCommand.java:295)
> at 
> org.apache.ambari.server.api.services.stackadvisor.StackAdvisorHelper.recommend(StackAdvisorHelper.java:113)
> at 
> org.apache.ambari.server.controller.internal.RecommendationResourceProvider.createResources(RecommendationResourceProvider.java:92)
> at 
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:298)
> at 
> org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:97)
> at 
> org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:37)
> at 
> org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:73)
> at 
> 

[jira] [Updated] (AMBARI-21132) Export cluster_name in the cluster template file

[Amruta Borkar (JIRA)]

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

Amruta Borkar updated AMBARI-21132:
---
Description: Blueprint export from UI installer currently does not export 
cluster_name in the clustertemplate file. Adding patch to export the same.

> Export cluster_name in the cluster template file
> 
>
> Key: AMBARI-21132
> URL: https://issues.apache.org/jira/browse/AMBARI-21132
> Project: Ambari
>  Issue Type: Technical task
>  Components: ambari-web
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-21132.patch
>
>
> Blueprint export from UI installer currently does not export cluster_name in 
> the clustertemplate file. Adding patch to export the same.



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

[jira] [Updated] (AMBARI-21132) Export cluster_name in the cluster template file

[Amruta Borkar (JIRA)]

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

Amruta Borkar updated AMBARI-21132:
---
Attachment: AMBARI-21132.patch

> Export cluster_name in the cluster template file
> 
>
> Key: AMBARI-21132
> URL: https://issues.apache.org/jira/browse/AMBARI-21132
> Project: Ambari
>  Issue Type: Technical task
>  Components: ambari-web
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-21132.patch
>
>




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

[jira] [Updated] (AMBARI-21132) Export cluster_name in the cluster template file

[Amruta Borkar (JIRA)]

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

Amruta Borkar updated AMBARI-21132:
---
Status: Patch Available  (was: In Progress)

> Export cluster_name in the cluster template file
> 
>
> Key: AMBARI-21132
> URL: https://issues.apache.org/jira/browse/AMBARI-21132
> Project: Ambari
>  Issue Type: Technical task
>  Components: ambari-web
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-21132.patch
>
>




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

[jira] [Created] (AMBARI-21132) Export cluster_name in the cluster template file

[Amruta Borkar (JIRA)]

Amruta Borkar created AMBARI-21132:
--

 Summary: Export cluster_name in the cluster template file
 Key: AMBARI-21132
 URL: https://issues.apache.org/jira/browse/AMBARI-21132
 Project: Ambari
  Issue Type: Technical task
  Components: ambari-web
Reporter: Amruta Borkar
Assignee: Amruta Borkar
Priority: Minor
 Fix For: trunk






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

[jira] [Commented] (AMBARI-21125) Ambari STS2 checker should use principal in secure cluster

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-21125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16025516#comment-16025516
 ] 

Hudson commented on AMBARI-21125:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7541 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/7541/])
AMBARI-21125. Ambari STS2 checker should use principal in secure cluster 
(rlevas: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ad6a78eeed591cf5b6ea481161194c05eaa5e4b7])
* (edit) 
ambari-server/src/main/resources/common-services/SPARK/1.2.1/package/scripts/alerts/alert_spark_thrift_port.py
* (edit) 
ambari-server/src/main/resources/common-services/SPARK2/2.0.0/package/scripts/alerts/alert_spark2_thrift_port.py


> Ambari STS2 checker should use principal in secure cluster
> --
>
> Key: AMBARI-21125
> URL: https://issues.apache.org/jira/browse/AMBARI-21125
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.1
>Reporter: Mingjie Tang
>Assignee: Mingjie Tang
>  Labels: spark
> Fix For: 2.5.2
>
> Attachments: BUG-81619.diff
>
>
> In the secure cluster, Ambari STS checker for Spark2 seems to generate 
> misleading error every one minute.
> {code}
> 17/05/24 19:24:35 ERROR TThreadPoolServer: Error occurred during processing 
> of message.
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
> Unsupported mechanism type PLAIN
>  
> 17/05/24 19:25:35 ERROR TThreadPoolServer: Error occurred during processing 
> of message.
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
> Unsupported mechanism type PLAIN
>  
> 17/05/24 19:26:36 ERROR TThreadPoolServer: Error occurred during processing 
> of message.
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
> Unsupported mechanism type PLAIN
>  
> 17/05/24 19:27:35 ERROR TThreadPoolServer: Error occurred during processing 
> of message.
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
> Unsupported mechanism type PLAIN
> {code}



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

[jira] [Commented] (AMBARI-21104) Add Confirmation pop up for 'Generate Blueprint' button

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-21104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16025517#comment-16025517
 ] 

Hudson commented on AMBARI-21104:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7541 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/7541/])
AMBARI-21104 - Add Confirmation pop up for 'Generate Blueprint' button 
(sangeetar: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=a4482bba2c7f0d1bb3dfb79df45cd01909dd35ee])
* (edit) ambari-web/app/templates/wizard/step8.hbs
* (edit) ambari-web/app/messages.js
* (edit) ambari-web/app/controllers/wizard/step8_controller.js


> Add Confirmation pop up for 'Generate Blueprint' button
> ---
>
> Key: AMBARI-21104
> URL: https://issues.apache.org/jira/browse/AMBARI-21104
> Project: Ambari
>  Issue Type: Technical task
>  Components: ambari-web
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Fix For: trunk
>
> Attachments: AMBARI-21104.patch
>
>
> Add Confirmation pop up for 'Generate Blueprint' button.
> Notify user that two files will be downloaded and provide information on how 
> to use those files.



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

[jira] [Commented] (AMBARI-21117) Existing hosts state didn't save after host was added

[Antonenko Alexander (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-21117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16025510#comment-16025510
 ] 

Antonenko Alexander commented on AMBARI-21117:
--

committed to trunk

> Existing hosts state didn't save after host was added
> -
>
> Key: AMBARI-21117
> URL: https://issues.apache.org/jira/browse/AMBARI-21117
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.1
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.5.2
>
> Attachments: AMBARI-21117.patch
>
>
> Existing hosts state didn't save after host was added. In next test add host 
> wizard stay open.
> When we connect to cluster - automatically redirect on add host wizard. 
> (attached screenshot)
> First step validation passed and host registered successfully. 
> On Review Page, when we clicked Deploy we had popup with error that this host 
> already part of cluster.
> If we cluster wizard and try it again - validation on first step not passed



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

[jira] [Resolved] (AMBARI-21104) Add Confirmation pop up for 'Generate Blueprint' button

[Amruta Borkar (JIRA)]

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

Amruta Borkar resolved AMBARI-21104.

Resolution: Fixed

> Add Confirmation pop up for 'Generate Blueprint' button
> ---
>
> Key: AMBARI-21104
> URL: https://issues.apache.org/jira/browse/AMBARI-21104
> Project: Ambari
>  Issue Type: Technical task
>  Components: ambari-web
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Fix For: trunk
>
> Attachments: AMBARI-21104.patch
>
>
> Add Confirmation pop up for 'Generate Blueprint' button.
> Notify user that two files will be downloaded and provide information on how 
> to use those files.



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

[jira] [Commented] (AMBARI-21104) Add Confirmation pop up for 'Generate Blueprint' button

[Sangeeta Ravindran (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-21104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16025398#comment-16025398
 ] 

Sangeeta Ravindran commented on AMBARI-21104:
-

Pushed to trunk as 
commit a4482bba2c7f0d1bb3dfb79df45cd01909dd35ee

> Add Confirmation pop up for 'Generate Blueprint' button
> ---
>
> Key: AMBARI-21104
> URL: https://issues.apache.org/jira/browse/AMBARI-21104
> Project: Ambari
>  Issue Type: Technical task
>  Components: ambari-web
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Fix For: trunk
>
> Attachments: AMBARI-21104.patch
>
>
> Add Confirmation pop up for 'Generate Blueprint' button.
> Notify user that two files will be downloaded and provide information on how 
> to use those files.



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

[jira] [Updated] (AMBARI-21120) Roles below Cluster Administrator should not be allowed to edit repositories and install stack versions

[Sangeeta Ravindran (JIRA)]

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

Sangeeta Ravindran updated AMBARI-21120:

Attachment: AMBARI-21120.patch

> Roles below Cluster Administrator should not be allowed to edit repositories 
> and install stack versions
> ---
>
> Key: AMBARI-21120
> URL: https://issues.apache.org/jira/browse/AMBARI-21120
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-21120.patch
>
>
> Login as a user with a role below Cluster Administrator. For e.g. Service 
> Admnistrator.
> Click on Stack and Versions.
> 1. Try to edit a stack version that is not yet installed on the cluster.
> Click on Save. The UI reloads and returns to Services Dashboard.
> On the browser console, you can see a HTTP 403 because the user does not have 
> the privilege to edit stack versions. 
> 2. Click on Install. When you click on on the popup confirming that the 
> packages will be installed on all hosts, you get a popup with an error 
> "Packages could not be installed. You do not have permissions to access this 
> resource".
>  



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

[jira] [Updated] (AMBARI-21120) Roles below Cluster Administrator should not be allowed to edit repositories and install stack versions

[Sangeeta Ravindran (JIRA)]

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

Sangeeta Ravindran updated AMBARI-21120:

Status: In Progress  (was: Patch Available)

> Roles below Cluster Administrator should not be allowed to edit repositories 
> and install stack versions
> ---
>
> Key: AMBARI-21120
> URL: https://issues.apache.org/jira/browse/AMBARI-21120
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-21120.patch
>
>
> Login as a user with a role below Cluster Administrator. For e.g. Service 
> Admnistrator.
> Click on Stack and Versions.
> 1. Try to edit a stack version that is not yet installed on the cluster.
> Click on Save. The UI reloads and returns to Services Dashboard.
> On the browser console, you can see a HTTP 403 because the user does not have 
> the privilege to edit stack versions. 
> 2. Click on Install. When you click on on the popup confirming that the 
> packages will be installed on all hosts, you get a popup with an error 
> "Packages could not be installed. You do not have permissions to access this 
> resource".
>  



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

[jira] [Updated] (AMBARI-21120) Roles below Cluster Administrator should not be allowed to edit repositories and install stack versions

[Sangeeta Ravindran (JIRA)]

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

Sangeeta Ravindran updated AMBARI-21120:

Status: Patch Available  (was: In Progress)

> Roles below Cluster Administrator should not be allowed to edit repositories 
> and install stack versions
> ---
>
> Key: AMBARI-21120
> URL: https://issues.apache.org/jira/browse/AMBARI-21120
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-21120.patch
>
>
> Login as a user with a role below Cluster Administrator. For e.g. Service 
> Admnistrator.
> Click on Stack and Versions.
> 1. Try to edit a stack version that is not yet installed on the cluster.
> Click on Save. The UI reloads and returns to Services Dashboard.
> On the browser console, you can see a HTTP 403 because the user does not have 
> the privilege to edit stack versions. 
> 2. Click on Install. When you click on on the popup confirming that the 
> packages will be installed on all hosts, you get a popup with an error 
> "Packages could not be installed. You do not have permissions to access this 
> resource".
>  



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

[jira] [Updated] (AMBARI-21120) Roles below Cluster Administrator should not be allowed to edit repositories and install stack versions

[Sangeeta Ravindran (JIRA)]

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

Sangeeta Ravindran updated AMBARI-21120:

Attachment: (was: AMBARI-21120.patch)

> Roles below Cluster Administrator should not be allowed to edit repositories 
> and install stack versions
> ---
>
> Key: AMBARI-21120
> URL: https://issues.apache.org/jira/browse/AMBARI-21120
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-21120.patch
>
>
> Login as a user with a role below Cluster Administrator. For e.g. Service 
> Admnistrator.
> Click on Stack and Versions.
> 1. Try to edit a stack version that is not yet installed on the cluster.
> Click on Save. The UI reloads and returns to Services Dashboard.
> On the browser console, you can see a HTTP 403 because the user does not have 
> the privilege to edit stack versions. 
> 2. Click on Install. When you click on on the popup confirming that the 
> packages will be installed on all hosts, you get a popup with an error 
> "Packages could not be installed. You do not have permissions to access this 
> resource".
>  



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

[jira] [Commented] (AMBARI-21131) Add NIFI JAAS Config StackFeatures to HDP StackFeatures

[Alejandro Fernandez (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-21131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16025384#comment-16025384
 ] 

Alejandro Fernandez commented on AMBARI-21131:
--

+1 for [^AMBARI-21131.patch]

> Add NIFI JAAS Config StackFeatures to HDP StackFeatures
> ---
>
> Key: AMBARI-21131
> URL: https://issues.apache.org/jira/browse/AMBARI-21131
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: 2.5.2
>
> Attachments: AMBARI-21131.patch
>
>




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

[jira] [Commented] (AMBARI-21131) Add NIFI JAAS Config StackFeatures to HDP StackFeatures

[Jayush Luniya (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-21131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16025373#comment-16025373
 ] 

Jayush Luniya commented on AMBARI-21131:


cc: [~afernandez] can you review?

> Add NIFI JAAS Config StackFeatures to HDP StackFeatures
> ---
>
> Key: AMBARI-21131
> URL: https://issues.apache.org/jira/browse/AMBARI-21131
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: 2.5.2
>
> Attachments: AMBARI-21131.patch
>
>




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

[jira] [Updated] (AMBARI-21131) Add NIFI JAAS Config StackFeatures to HDP StackFeatures

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-21131:
---
Status: Patch Available  (was: Open)

> Add NIFI JAAS Config StackFeatures to HDP StackFeatures
> ---
>
> Key: AMBARI-21131
> URL: https://issues.apache.org/jira/browse/AMBARI-21131
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: 2.5.2
>
> Attachments: AMBARI-21131.patch
>
>




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

[jira] [Updated] (AMBARI-21130) Delete view privileges from the Users page

[Anita Gnanamalar Jebaraj (JIRA)]

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

Anita Gnanamalar Jebaraj updated AMBARI-21130:
--
Status: Patch Available  (was: Open)

> Delete view privileges from the Users page
> --
>
> Key: AMBARI-21130
> URL: https://issues.apache.org/jira/browse/AMBARI-21130
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-admin
>Reporter: Anita Gnanamalar Jebaraj
>Assignee: Anita Gnanamalar Jebaraj
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-21130.patch
>
>
> The view permissions are listed in the users page, but in order to remove it, 
> the user has to drill down to the views page and remove the user from it. To 
> remove the permission for multiple views for one users, we have to navigate 
> to different Views page to perform the operation 
> Including a delete option in the Users page for views privilege will simply 
> this



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

[jira] [Updated] (AMBARI-21131) Add NIFI JAAS Config StackFeatures to HDP StackFeatures

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-21131:
---
Attachment: AMBARI-21131.patch

> Add NIFI JAAS Config StackFeatures to HDP StackFeatures
> ---
>
> Key: AMBARI-21131
> URL: https://issues.apache.org/jira/browse/AMBARI-21131
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
> Fix For: 2.5.2
>
> Attachments: AMBARI-21131.patch
>
>




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

[jira] [Created] (AMBARI-21131) Add NIFI JAAS Config StackFeatures to HDP StackFeatures

[Jayush Luniya (JIRA)]

Jayush Luniya created AMBARI-21131:
--

 Summary: Add NIFI JAAS Config StackFeatures to HDP StackFeatures
 Key: AMBARI-21131
 URL: https://issues.apache.org/jira/browse/AMBARI-21131
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.5.0
Reporter: Jayush Luniya
Assignee: Jayush Luniya
 Fix For: 2.5.2






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

[jira] [Updated] (AMBARI-21130) Delete view privileges from the Users page

[Anita Gnanamalar Jebaraj (JIRA)]

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

Anita Gnanamalar Jebaraj updated AMBARI-21130:
--
Attachment: AMBARI-21130.patch

> Delete view privileges from the Users page
> --
>
> Key: AMBARI-21130
> URL: https://issues.apache.org/jira/browse/AMBARI-21130
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-admin
>Reporter: Anita Gnanamalar Jebaraj
>Assignee: Anita Gnanamalar Jebaraj
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-21130.patch
>
>
> The view permissions are listed in the users page, but in order to remove it, 
> the user has to drill down to the views page and remove the user from it. To 
> remove the permission for multiple views for one users, we have to navigate 
> to different Views page to perform the operation 
> Including a delete option in the Users page for views privilege will simply 
> this



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

[jira] [Created] (AMBARI-21130) Delete view privileges from the Users page

[Anita Gnanamalar Jebaraj (JIRA)]

Anita Gnanamalar Jebaraj created AMBARI-21130:
-

 Summary: Delete view privileges from the Users page
 Key: AMBARI-21130
 URL: https://issues.apache.org/jira/browse/AMBARI-21130
 Project: Ambari
  Issue Type: Bug
  Components: ambari-admin
Reporter: Anita Gnanamalar Jebaraj
Assignee: Anita Gnanamalar Jebaraj
Priority: Minor
 Fix For: trunk


The view permissions are listed in the users page, but in order to remove it, 
the user has to drill down to the views page and remove the user from it. To 
remove the permission for multiple views for one users, we have to navigate to 
different Views page to perform the operation 

Including a delete option in the Users page for views privilege will simply this



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

[jira] [Commented] (AMBARI-21125) Ambari STS2 checker should use principal in secure cluster

[Robert Levas (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-21125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16025303#comment-16025303
 ] 

Robert Levas commented on AMBARI-21125:
---

Leaving unresolved until the patch can be committed into branch-2.5 - waiting 
for Ambari 2.5.1 to be released first. 


> Ambari STS2 checker should use principal in secure cluster
> --
>
> Key: AMBARI-21125
> URL: https://issues.apache.org/jira/browse/AMBARI-21125
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.1
>Reporter: Mingjie Tang
>Assignee: Mingjie Tang
>  Labels: spark
> Fix For: 2.5.2
>
> Attachments: BUG-81619.diff
>
>
> In the secure cluster, Ambari STS checker for Spark2 seems to generate 
> misleading error every one minute.
> {code}
> 17/05/24 19:24:35 ERROR TThreadPoolServer: Error occurred during processing 
> of message.
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
> Unsupported mechanism type PLAIN
>  
> 17/05/24 19:25:35 ERROR TThreadPoolServer: Error occurred during processing 
> of message.
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
> Unsupported mechanism type PLAIN
>  
> 17/05/24 19:26:36 ERROR TThreadPoolServer: Error occurred during processing 
> of message.
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
> Unsupported mechanism type PLAIN
>  
> 17/05/24 19:27:35 ERROR TThreadPoolServer: Error occurred during processing 
> of message.
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
> Unsupported mechanism type PLAIN
> {code}



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

[jira] [Updated] (AMBARI-21125) Ambari STS2 checker should use principal in secure cluster

[Robert Levas (JIRA)]

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

Robert Levas updated AMBARI-21125:
--
Status: Patch Available  (was: Open)

> Ambari STS2 checker should use principal in secure cluster
> --
>
> Key: AMBARI-21125
> URL: https://issues.apache.org/jira/browse/AMBARI-21125
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.1
>Reporter: Mingjie Tang
>Assignee: Mingjie Tang
>  Labels: spark
> Fix For: 2.5.2
>
> Attachments: BUG-81619.diff
>
>
> In the secure cluster, Ambari STS checker for Spark2 seems to generate 
> misleading error every one minute.
> {code}
> 17/05/24 19:24:35 ERROR TThreadPoolServer: Error occurred during processing 
> of message.
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
> Unsupported mechanism type PLAIN
>  
> 17/05/24 19:25:35 ERROR TThreadPoolServer: Error occurred during processing 
> of message.
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
> Unsupported mechanism type PLAIN
>  
> 17/05/24 19:26:36 ERROR TThreadPoolServer: Error occurred during processing 
> of message.
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
> Unsupported mechanism type PLAIN
>  
> 17/05/24 19:27:35 ERROR TThreadPoolServer: Error occurred during processing 
> of message.
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
> Unsupported mechanism type PLAIN
> {code}



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

[jira] [Commented] (AMBARI-21125) Ambari STS2 checker should use principal in secure cluster

[Robert Levas (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-21125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16025296#comment-16025296
 ] 

Robert Levas commented on AMBARI-21125:
---

Committed to trunk
{noformat}
commit ad6a78eeed591cf5b6ea481161194c05eaa5e4b7
Author: Mingjie Tang 
Date:   Thu May 25 15:59:49 2017 -0400
{noformat}

> Ambari STS2 checker should use principal in secure cluster
> --
>
> Key: AMBARI-21125
> URL: https://issues.apache.org/jira/browse/AMBARI-21125
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.1
>Reporter: Mingjie Tang
>Assignee: Mingjie Tang
>  Labels: spark
> Fix For: 2.5.2
>
> Attachments: BUG-81619.diff
>
>
> In the secure cluster, Ambari STS checker for Spark2 seems to generate 
> misleading error every one minute.
> {code}
> 17/05/24 19:24:35 ERROR TThreadPoolServer: Error occurred during processing 
> of message.
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
> Unsupported mechanism type PLAIN
>  
> 17/05/24 19:25:35 ERROR TThreadPoolServer: Error occurred during processing 
> of message.
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
> Unsupported mechanism type PLAIN
>  
> 17/05/24 19:26:36 ERROR TThreadPoolServer: Error occurred during processing 
> of message.
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
> Unsupported mechanism type PLAIN
>  
> 17/05/24 19:27:35 ERROR TThreadPoolServer: Error occurred during processing 
> of message.
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
> Unsupported mechanism type PLAIN
> {code}



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

[jira] [Updated] (AMBARI-21125) Ambari STS2 checker should use principal in secure cluster

[Robert Levas (JIRA)]

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

Robert Levas updated AMBARI-21125:
--
Fix Version/s: 2.5.2

> Ambari STS2 checker should use principal in secure cluster
> --
>
> Key: AMBARI-21125
> URL: https://issues.apache.org/jira/browse/AMBARI-21125
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.1
>Reporter: Mingjie Tang
>Assignee: Mingjie Tang
>  Labels: spark
> Fix For: 2.5.2
>
> Attachments: BUG-81619.diff
>
>
> In the secure cluster, Ambari STS checker for Spark2 seems to generate 
> misleading error every one minute.
> {code}
> 17/05/24 19:24:35 ERROR TThreadPoolServer: Error occurred during processing 
> of message.
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
> Unsupported mechanism type PLAIN
>  
> 17/05/24 19:25:35 ERROR TThreadPoolServer: Error occurred during processing 
> of message.
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
> Unsupported mechanism type PLAIN
>  
> 17/05/24 19:26:36 ERROR TThreadPoolServer: Error occurred during processing 
> of message.
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
> Unsupported mechanism type PLAIN
>  
> 17/05/24 19:27:35 ERROR TThreadPoolServer: Error occurred during processing 
> of message.
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
> Unsupported mechanism type PLAIN
> {code}



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

[jira] [Commented] (AMBARI-21121) Missing storm-site.xml in HDP-2.6 stack

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-21121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16025203#comment-16025203
 ] 

Hudson commented on AMBARI-21121:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7540 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/7540/])
AMBARI-21121: Missing storm-site.xml in HDP-2.6 stack (Sriharsha (jluniya: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=1e3d64bfeaa59ac471c013cac1a96b1df14921f0])
* (add) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/STORM/configuration/storm-site.xml


> Missing storm-site.xml in HDP-2.6 stack
> ---
>
> Key: AMBARI-21121
> URL: https://issues.apache.org/jira/browse/AMBARI-21121
> Project: Ambari
>  Issue Type: Bug
>Reporter: Sriharsha Chintalapani
>Assignee: Sriharsha Chintalapani
>Priority: Blocker
> Fix For: 2.5.2
>
> Attachments: AMBARI-21121.patch
>
>




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

[jira] [Commented] (AMBARI-21129) Nimbus fails to start when Ambari is upgraded to 2.5.1, EU to HDP 2.6.1, and cluster is then Kerberized

[Sriharsha Chintalapani (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-21129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16025174#comment-16025174
 ] 

Sriharsha Chintalapani commented on AMBARI-21129:
-

+1. LGTM.

> Nimbus fails to start when Ambari is upgraded to 2.5.1, EU to HDP 2.6.1, and 
> cluster is then Kerberized
> ---
>
> Key: AMBARI-21129
> URL: https://issues.apache.org/jira/browse/AMBARI-21129
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.1
>Reporter: Denis Tarasyuk
>Assignee: Alejandro Fernandez
> Fix For: 2.5.2
>
> Attachments: AMBARI-21129.2.5-maint.patch
>
>
> STR:
> # Ambari 2.5.0 with Storm and HDP 2.6 and Storm
> # Upgrade Ambari to 2.5.1
> # EU to HDP 2.6.1
> # Kerberize the cluster
> The exception found in nimbus.log:
> {code}
> 2017-05-25 11:31:10.235 o.a.s.n.NimbusInfo [INFO] Nimbus figures out its name 
> to natu146-fpas-dlm30tofnsec-u14-re-re-4.openstacklocal
> 2017-05-25 11:31:10.247 o.a.s.d.nimbus [ERROR] Error on initialization of 
> server service-handler
> java.lang.RuntimeException: java.lang.ClassNotFoundException: 
> org.apache.storm.hdfs.security.AutoHDFS
>   at 
> org.apache.storm.security.auth.AuthUtils.getNimbusAutoCredPlugins(AuthUtils.java:188)
>  ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   at org.apache.storm.daemon.nimbus$nimbus_data.invoke(nimbus.clj:223) 
> ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   at 
> org.apache.storm.daemon.nimbus$fn__9066$exec_fn__2832__auto9067.invoke(nimbus.clj:2416)
>  ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   at clojure.lang.AFn.applyToHelper(AFn.java:156) ~[clojure-1.7.0.jar:?]
>   at clojure.lang.AFn.applyTo(AFn.java:144) ~[clojure-1.7.0.jar:?]
>   at clojure.core$apply.invoke(core.clj:630) ~[clojure-1.7.0.jar:?]
>   at 
> org.apache.storm.daemon.nimbus$fn__9066$service_handler__9099.doInvoke(nimbus.clj:2413)
>  ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   at clojure.lang.RestFn.invoke(RestFn.java:421) ~[clojure-1.7.0.jar:?]
>   at 
> org.apache.storm.daemon.nimbus$launch_server_BANG_.invoke(nimbus.clj:2501) 
> ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   at org.apache.storm.daemon.nimbus$_launch.invoke(nimbus.clj:2534) 
> ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   at org.apache.storm.daemon.nimbus$_main.invoke(nimbus.clj:2557) 
> ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   at clojure.lang.AFn.applyToHelper(AFn.java:152) ~[clojure-1.7.0.jar:?]
>   at clojure.lang.AFn.applyTo(AFn.java:144) ~[clojure-1.7.0.jar:?]
>   at org.apache.storm.daemon.nimbus.main(Unknown Source) 
> ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
> Caused by: java.lang.ClassNotFoundException: 
> org.apache.storm.hdfs.security.AutoHDFS
>   at java.net.URLClassLoader$1.run(URLClassLoader.java:366) ~[?:1.7.0_67]
>   at java.net.URLClassLoader$1.run(URLClassLoader.java:355) ~[?:1.7.0_67]
>   at java.security.AccessController.doPrivileged(Native Method) 
> ~[?:1.7.0_67]
>   at java.net.URLClassLoader.findClass(URLClassLoader.java:354) 
> ~[?:1.7.0_67]
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:425) ~[?:1.7.0_67]
>   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) 
> ~[?:1.7.0_67]
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:358) ~[?:1.7.0_67]
>   at java.lang.Class.forName0(Native Method) ~[?:1.7.0_67]
>   at java.lang.Class.forName(Class.java:190) ~[?:1.7.0_67]
>   at 
> org.apache.storm.security.auth.AuthUtils.getNimbusAutoCredPlugins(AuthUtils.java:181)
>  ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   ... 13 more
> 2017-05-25 11:31:10.295 o.a.s.util [ERROR] Halting process: ("Error on 
> initialization")
> java.lang.RuntimeException: ("Error on initialization")
>   at org.apache.storm.util$exit_process_BANG_.doInvoke(util.clj:341) 
> ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   at clojure.lang.RestFn.invoke(RestFn.java:423) ~[clojure-1.7.0.jar:?]
>   at 
> org.apache.storm.daemon.nimbus$fn__9066$service_handler__9099.doInvoke(nimbus.clj:2413)
>  ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   at clojure.lang.RestFn.invoke(RestFn.java:421) ~[clojure-1.7.0.jar:?]
>   at 
> org.apache.storm.daemon.nimbus$launch_server_BANG_.invoke(nimbus.clj:2501) 
> ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   at org.apache.storm.daemon.nimbus$_launch.invoke(nimbus.clj:2534) 
> ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   at org.apache.storm.daemon.nimbus$_main.invoke(nimbus.clj:2557) 
> ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   at 

[jira] [Updated] (AMBARI-21129) Nimbus fails to start when Ambari is upgraded to 2.5.1, EU to HDP 2.6.1, and cluster is then Kerberized

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-21129:
-
Status: Patch Available  (was: Open)

> Nimbus fails to start when Ambari is upgraded to 2.5.1, EU to HDP 2.6.1, and 
> cluster is then Kerberized
> ---
>
> Key: AMBARI-21129
> URL: https://issues.apache.org/jira/browse/AMBARI-21129
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.1
>Reporter: Denis Tarasyuk
>Assignee: Alejandro Fernandez
> Fix For: 2.5.2
>
> Attachments: AMBARI-21129.2.5-maint.patch
>
>
> STR:
> # Ambari 2.5.0 with Storm and HDP 2.6 and Storm
> # Upgrade Ambari to 2.5.1
> # EU to HDP 2.6.1
> # Kerberize the cluster
> The exception found in nimbus.log:
> {code}
> 2017-05-25 11:31:10.235 o.a.s.n.NimbusInfo [INFO] Nimbus figures out its name 
> to natu146-fpas-dlm30tofnsec-u14-re-re-4.openstacklocal
> 2017-05-25 11:31:10.247 o.a.s.d.nimbus [ERROR] Error on initialization of 
> server service-handler
> java.lang.RuntimeException: java.lang.ClassNotFoundException: 
> org.apache.storm.hdfs.security.AutoHDFS
>   at 
> org.apache.storm.security.auth.AuthUtils.getNimbusAutoCredPlugins(AuthUtils.java:188)
>  ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   at org.apache.storm.daemon.nimbus$nimbus_data.invoke(nimbus.clj:223) 
> ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   at 
> org.apache.storm.daemon.nimbus$fn__9066$exec_fn__2832__auto9067.invoke(nimbus.clj:2416)
>  ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   at clojure.lang.AFn.applyToHelper(AFn.java:156) ~[clojure-1.7.0.jar:?]
>   at clojure.lang.AFn.applyTo(AFn.java:144) ~[clojure-1.7.0.jar:?]
>   at clojure.core$apply.invoke(core.clj:630) ~[clojure-1.7.0.jar:?]
>   at 
> org.apache.storm.daemon.nimbus$fn__9066$service_handler__9099.doInvoke(nimbus.clj:2413)
>  ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   at clojure.lang.RestFn.invoke(RestFn.java:421) ~[clojure-1.7.0.jar:?]
>   at 
> org.apache.storm.daemon.nimbus$launch_server_BANG_.invoke(nimbus.clj:2501) 
> ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   at org.apache.storm.daemon.nimbus$_launch.invoke(nimbus.clj:2534) 
> ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   at org.apache.storm.daemon.nimbus$_main.invoke(nimbus.clj:2557) 
> ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   at clojure.lang.AFn.applyToHelper(AFn.java:152) ~[clojure-1.7.0.jar:?]
>   at clojure.lang.AFn.applyTo(AFn.java:144) ~[clojure-1.7.0.jar:?]
>   at org.apache.storm.daemon.nimbus.main(Unknown Source) 
> ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
> Caused by: java.lang.ClassNotFoundException: 
> org.apache.storm.hdfs.security.AutoHDFS
>   at java.net.URLClassLoader$1.run(URLClassLoader.java:366) ~[?:1.7.0_67]
>   at java.net.URLClassLoader$1.run(URLClassLoader.java:355) ~[?:1.7.0_67]
>   at java.security.AccessController.doPrivileged(Native Method) 
> ~[?:1.7.0_67]
>   at java.net.URLClassLoader.findClass(URLClassLoader.java:354) 
> ~[?:1.7.0_67]
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:425) ~[?:1.7.0_67]
>   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) 
> ~[?:1.7.0_67]
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:358) ~[?:1.7.0_67]
>   at java.lang.Class.forName0(Native Method) ~[?:1.7.0_67]
>   at java.lang.Class.forName(Class.java:190) ~[?:1.7.0_67]
>   at 
> org.apache.storm.security.auth.AuthUtils.getNimbusAutoCredPlugins(AuthUtils.java:181)
>  ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   ... 13 more
> 2017-05-25 11:31:10.295 o.a.s.util [ERROR] Halting process: ("Error on 
> initialization")
> java.lang.RuntimeException: ("Error on initialization")
>   at org.apache.storm.util$exit_process_BANG_.doInvoke(util.clj:341) 
> ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   at clojure.lang.RestFn.invoke(RestFn.java:423) ~[clojure-1.7.0.jar:?]
>   at 
> org.apache.storm.daemon.nimbus$fn__9066$service_handler__9099.doInvoke(nimbus.clj:2413)
>  ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   at clojure.lang.RestFn.invoke(RestFn.java:421) ~[clojure-1.7.0.jar:?]
>   at 
> org.apache.storm.daemon.nimbus$launch_server_BANG_.invoke(nimbus.clj:2501) 
> ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   at org.apache.storm.daemon.nimbus$_launch.invoke(nimbus.clj:2534) 
> ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   at org.apache.storm.daemon.nimbus$_main.invoke(nimbus.clj:2557) 
> ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   at 

[jira] [Updated] (AMBARI-21129) Nimbus fails to start when Ambari is upgraded to 2.5.1, EU to HDP 2.6.1, and cluster is then Kerberized

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-21129:
-
Attachment: AMBARI-21129.2.5-maint.patch

> Nimbus fails to start when Ambari is upgraded to 2.5.1, EU to HDP 2.6.1, and 
> cluster is then Kerberized
> ---
>
> Key: AMBARI-21129
> URL: https://issues.apache.org/jira/browse/AMBARI-21129
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.1
>Reporter: Denis Tarasyuk
>Assignee: Alejandro Fernandez
> Fix For: 2.5.2
>
> Attachments: AMBARI-21129.2.5-maint.patch
>
>
> STR:
> # Ambari 2.5.0 with Storm and HDP 2.6 and Storm
> # Upgrade Ambari to 2.5.1
> # EU to HDP 2.6.1
> # Kerberize the cluster
> The exception found in nimbus.log:
> {code}
> 2017-05-25 11:31:10.235 o.a.s.n.NimbusInfo [INFO] Nimbus figures out its name 
> to natu146-fpas-dlm30tofnsec-u14-re-re-4.openstacklocal
> 2017-05-25 11:31:10.247 o.a.s.d.nimbus [ERROR] Error on initialization of 
> server service-handler
> java.lang.RuntimeException: java.lang.ClassNotFoundException: 
> org.apache.storm.hdfs.security.AutoHDFS
>   at 
> org.apache.storm.security.auth.AuthUtils.getNimbusAutoCredPlugins(AuthUtils.java:188)
>  ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   at org.apache.storm.daemon.nimbus$nimbus_data.invoke(nimbus.clj:223) 
> ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   at 
> org.apache.storm.daemon.nimbus$fn__9066$exec_fn__2832__auto9067.invoke(nimbus.clj:2416)
>  ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   at clojure.lang.AFn.applyToHelper(AFn.java:156) ~[clojure-1.7.0.jar:?]
>   at clojure.lang.AFn.applyTo(AFn.java:144) ~[clojure-1.7.0.jar:?]
>   at clojure.core$apply.invoke(core.clj:630) ~[clojure-1.7.0.jar:?]
>   at 
> org.apache.storm.daemon.nimbus$fn__9066$service_handler__9099.doInvoke(nimbus.clj:2413)
>  ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   at clojure.lang.RestFn.invoke(RestFn.java:421) ~[clojure-1.7.0.jar:?]
>   at 
> org.apache.storm.daemon.nimbus$launch_server_BANG_.invoke(nimbus.clj:2501) 
> ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   at org.apache.storm.daemon.nimbus$_launch.invoke(nimbus.clj:2534) 
> ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   at org.apache.storm.daemon.nimbus$_main.invoke(nimbus.clj:2557) 
> ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   at clojure.lang.AFn.applyToHelper(AFn.java:152) ~[clojure-1.7.0.jar:?]
>   at clojure.lang.AFn.applyTo(AFn.java:144) ~[clojure-1.7.0.jar:?]
>   at org.apache.storm.daemon.nimbus.main(Unknown Source) 
> ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
> Caused by: java.lang.ClassNotFoundException: 
> org.apache.storm.hdfs.security.AutoHDFS
>   at java.net.URLClassLoader$1.run(URLClassLoader.java:366) ~[?:1.7.0_67]
>   at java.net.URLClassLoader$1.run(URLClassLoader.java:355) ~[?:1.7.0_67]
>   at java.security.AccessController.doPrivileged(Native Method) 
> ~[?:1.7.0_67]
>   at java.net.URLClassLoader.findClass(URLClassLoader.java:354) 
> ~[?:1.7.0_67]
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:425) ~[?:1.7.0_67]
>   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) 
> ~[?:1.7.0_67]
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:358) ~[?:1.7.0_67]
>   at java.lang.Class.forName0(Native Method) ~[?:1.7.0_67]
>   at java.lang.Class.forName(Class.java:190) ~[?:1.7.0_67]
>   at 
> org.apache.storm.security.auth.AuthUtils.getNimbusAutoCredPlugins(AuthUtils.java:181)
>  ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   ... 13 more
> 2017-05-25 11:31:10.295 o.a.s.util [ERROR] Halting process: ("Error on 
> initialization")
> java.lang.RuntimeException: ("Error on initialization")
>   at org.apache.storm.util$exit_process_BANG_.doInvoke(util.clj:341) 
> ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   at clojure.lang.RestFn.invoke(RestFn.java:423) ~[clojure-1.7.0.jar:?]
>   at 
> org.apache.storm.daemon.nimbus$fn__9066$service_handler__9099.doInvoke(nimbus.clj:2413)
>  ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   at clojure.lang.RestFn.invoke(RestFn.java:421) ~[clojure-1.7.0.jar:?]
>   at 
> org.apache.storm.daemon.nimbus$launch_server_BANG_.invoke(nimbus.clj:2501) 
> ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   at org.apache.storm.daemon.nimbus$_launch.invoke(nimbus.clj:2534) 
> ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   at org.apache.storm.daemon.nimbus$_main.invoke(nimbus.clj:2557) 
> ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   at 

[jira] [Updated] (AMBARI-21129) Nimbus fails to start when Ambari is upgraded to 2.5.1, EU to HDP 2.6.1, and cluster is then Kerberized

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-21129:
-
Reporter: Denis Tarasyuk  (was: Alejandro Fernandez)

> Nimbus fails to start when Ambari is upgraded to 2.5.1, EU to HDP 2.6.1, and 
> cluster is then Kerberized
> ---
>
> Key: AMBARI-21129
> URL: https://issues.apache.org/jira/browse/AMBARI-21129
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.1
>Reporter: Denis Tarasyuk
>Assignee: Alejandro Fernandez
> Fix For: 2.5.2
>
>
> STR:
> # Ambari 2.5.0 with Storm and HDP 2.6 and Storm
> # Upgrade Ambari to 2.5.1
> # EU to HDP 2.6.1
> # Kerberize the cluster
> The exception found in nimbus.log:
> {code}
> 2017-05-25 11:31:10.235 o.a.s.n.NimbusInfo [INFO] Nimbus figures out its name 
> to natu146-fpas-dlm30tofnsec-u14-re-re-4.openstacklocal
> 2017-05-25 11:31:10.247 o.a.s.d.nimbus [ERROR] Error on initialization of 
> server service-handler
> java.lang.RuntimeException: java.lang.ClassNotFoundException: 
> org.apache.storm.hdfs.security.AutoHDFS
>   at 
> org.apache.storm.security.auth.AuthUtils.getNimbusAutoCredPlugins(AuthUtils.java:188)
>  ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   at org.apache.storm.daemon.nimbus$nimbus_data.invoke(nimbus.clj:223) 
> ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   at 
> org.apache.storm.daemon.nimbus$fn__9066$exec_fn__2832__auto9067.invoke(nimbus.clj:2416)
>  ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   at clojure.lang.AFn.applyToHelper(AFn.java:156) ~[clojure-1.7.0.jar:?]
>   at clojure.lang.AFn.applyTo(AFn.java:144) ~[clojure-1.7.0.jar:?]
>   at clojure.core$apply.invoke(core.clj:630) ~[clojure-1.7.0.jar:?]
>   at 
> org.apache.storm.daemon.nimbus$fn__9066$service_handler__9099.doInvoke(nimbus.clj:2413)
>  ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   at clojure.lang.RestFn.invoke(RestFn.java:421) ~[clojure-1.7.0.jar:?]
>   at 
> org.apache.storm.daemon.nimbus$launch_server_BANG_.invoke(nimbus.clj:2501) 
> ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   at org.apache.storm.daemon.nimbus$_launch.invoke(nimbus.clj:2534) 
> ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   at org.apache.storm.daemon.nimbus$_main.invoke(nimbus.clj:2557) 
> ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   at clojure.lang.AFn.applyToHelper(AFn.java:152) ~[clojure-1.7.0.jar:?]
>   at clojure.lang.AFn.applyTo(AFn.java:144) ~[clojure-1.7.0.jar:?]
>   at org.apache.storm.daemon.nimbus.main(Unknown Source) 
> ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
> Caused by: java.lang.ClassNotFoundException: 
> org.apache.storm.hdfs.security.AutoHDFS
>   at java.net.URLClassLoader$1.run(URLClassLoader.java:366) ~[?:1.7.0_67]
>   at java.net.URLClassLoader$1.run(URLClassLoader.java:355) ~[?:1.7.0_67]
>   at java.security.AccessController.doPrivileged(Native Method) 
> ~[?:1.7.0_67]
>   at java.net.URLClassLoader.findClass(URLClassLoader.java:354) 
> ~[?:1.7.0_67]
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:425) ~[?:1.7.0_67]
>   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) 
> ~[?:1.7.0_67]
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:358) ~[?:1.7.0_67]
>   at java.lang.Class.forName0(Native Method) ~[?:1.7.0_67]
>   at java.lang.Class.forName(Class.java:190) ~[?:1.7.0_67]
>   at 
> org.apache.storm.security.auth.AuthUtils.getNimbusAutoCredPlugins(AuthUtils.java:181)
>  ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   ... 13 more
> 2017-05-25 11:31:10.295 o.a.s.util [ERROR] Halting process: ("Error on 
> initialization")
> java.lang.RuntimeException: ("Error on initialization")
>   at org.apache.storm.util$exit_process_BANG_.doInvoke(util.clj:341) 
> ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   at clojure.lang.RestFn.invoke(RestFn.java:423) ~[clojure-1.7.0.jar:?]
>   at 
> org.apache.storm.daemon.nimbus$fn__9066$service_handler__9099.doInvoke(nimbus.clj:2413)
>  ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   at clojure.lang.RestFn.invoke(RestFn.java:421) ~[clojure-1.7.0.jar:?]
>   at 
> org.apache.storm.daemon.nimbus$launch_server_BANG_.invoke(nimbus.clj:2501) 
> ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   at org.apache.storm.daemon.nimbus$_launch.invoke(nimbus.clj:2534) 
> ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   at org.apache.storm.daemon.nimbus$_main.invoke(nimbus.clj:2557) 
> ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
>   at clojure.lang.AFn.applyToHelper(AFn.java:152) 

[jira] [Created] (AMBARI-21129) Nimbus fails to start when Ambari is upgraded to 2.5.1, EU to HDP 2.6.1, and cluster is then Kerberized

[Alejandro Fernandez (JIRA)]

Alejandro Fernandez created AMBARI-21129:


 Summary: Nimbus fails to start when Ambari is upgraded to 2.5.1, 
EU to HDP 2.6.1, and cluster is then Kerberized
 Key: AMBARI-21129
 URL: https://issues.apache.org/jira/browse/AMBARI-21129
 Project: Ambari
  Issue Type: Bug
  Components: stacks
Affects Versions: 2.5.1
Reporter: Alejandro Fernandez
Assignee: Alejandro Fernandez
 Fix For: 2.5.2


STR:
# Ambari 2.5.0 with Storm and HDP 2.6 and Storm
# Upgrade Ambari to 2.5.1
# EU to HDP 2.6.1
# Kerberize the cluster


The exception found in nimbus.log:
{code}
2017-05-25 11:31:10.235 o.a.s.n.NimbusInfo [INFO] Nimbus figures out its name 
to natu146-fpas-dlm30tofnsec-u14-re-re-4.openstacklocal
2017-05-25 11:31:10.247 o.a.s.d.nimbus [ERROR] Error on initialization of 
server service-handler
java.lang.RuntimeException: java.lang.ClassNotFoundException: 
org.apache.storm.hdfs.security.AutoHDFS
at 
org.apache.storm.security.auth.AuthUtils.getNimbusAutoCredPlugins(AuthUtils.java:188)
 ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
at org.apache.storm.daemon.nimbus$nimbus_data.invoke(nimbus.clj:223) 
~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
at 
org.apache.storm.daemon.nimbus$fn__9066$exec_fn__2832__auto9067.invoke(nimbus.clj:2416)
 ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
at clojure.lang.AFn.applyToHelper(AFn.java:156) ~[clojure-1.7.0.jar:?]
at clojure.lang.AFn.applyTo(AFn.java:144) ~[clojure-1.7.0.jar:?]
at clojure.core$apply.invoke(core.clj:630) ~[clojure-1.7.0.jar:?]
at 
org.apache.storm.daemon.nimbus$fn__9066$service_handler__9099.doInvoke(nimbus.clj:2413)
 ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
at clojure.lang.RestFn.invoke(RestFn.java:421) ~[clojure-1.7.0.jar:?]
at 
org.apache.storm.daemon.nimbus$launch_server_BANG_.invoke(nimbus.clj:2501) 
~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
at org.apache.storm.daemon.nimbus$_launch.invoke(nimbus.clj:2534) 
~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
at org.apache.storm.daemon.nimbus$_main.invoke(nimbus.clj:2557) 
~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
at clojure.lang.AFn.applyToHelper(AFn.java:152) ~[clojure-1.7.0.jar:?]
at clojure.lang.AFn.applyTo(AFn.java:144) ~[clojure-1.7.0.jar:?]
at org.apache.storm.daemon.nimbus.main(Unknown Source) 
~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
Caused by: java.lang.ClassNotFoundException: 
org.apache.storm.hdfs.security.AutoHDFS
at java.net.URLClassLoader$1.run(URLClassLoader.java:366) ~[?:1.7.0_67]
at java.net.URLClassLoader$1.run(URLClassLoader.java:355) ~[?:1.7.0_67]
at java.security.AccessController.doPrivileged(Native Method) 
~[?:1.7.0_67]
at java.net.URLClassLoader.findClass(URLClassLoader.java:354) 
~[?:1.7.0_67]
at java.lang.ClassLoader.loadClass(ClassLoader.java:425) ~[?:1.7.0_67]
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) 
~[?:1.7.0_67]
at java.lang.ClassLoader.loadClass(ClassLoader.java:358) ~[?:1.7.0_67]
at java.lang.Class.forName0(Native Method) ~[?:1.7.0_67]
at java.lang.Class.forName(Class.java:190) ~[?:1.7.0_67]
at 
org.apache.storm.security.auth.AuthUtils.getNimbusAutoCredPlugins(AuthUtils.java:181)
 ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
... 13 more
2017-05-25 11:31:10.295 o.a.s.util [ERROR] Halting process: ("Error on 
initialization")
java.lang.RuntimeException: ("Error on initialization")
at org.apache.storm.util$exit_process_BANG_.doInvoke(util.clj:341) 
~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
at clojure.lang.RestFn.invoke(RestFn.java:423) ~[clojure-1.7.0.jar:?]
at 
org.apache.storm.daemon.nimbus$fn__9066$service_handler__9099.doInvoke(nimbus.clj:2413)
 ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
at clojure.lang.RestFn.invoke(RestFn.java:421) ~[clojure-1.7.0.jar:?]
at 
org.apache.storm.daemon.nimbus$launch_server_BANG_.invoke(nimbus.clj:2501) 
~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
at org.apache.storm.daemon.nimbus$_launch.invoke(nimbus.clj:2534) 
~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
at org.apache.storm.daemon.nimbus$_main.invoke(nimbus.clj:2557) 
~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
at clojure.lang.AFn.applyToHelper(AFn.java:152) ~[clojure-1.7.0.jar:?]
at clojure.lang.AFn.applyTo(AFn.java:144) ~[clojure-1.7.0.jar:?]
at org.apache.storm.daemon.nimbus.main(Unknown Source) 
~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
{code}

This is because upgrading Ambari from an older version to 2.5.1 right now will 
update storm-env only if Storm is present and the cluster is 

[jira] [Commented] (AMBARI-21121) Missing storm-site.xml in HDP-2.6 stack

[Jayush Luniya (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-21121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16025041#comment-16025041
 ] 

Jayush Luniya commented on AMBARI-21121:


Will keep JIRA open as this needs to go to branch-2.5 after 2.5.1 release.

> Missing storm-site.xml in HDP-2.6 stack
> ---
>
> Key: AMBARI-21121
> URL: https://issues.apache.org/jira/browse/AMBARI-21121
> Project: Ambari
>  Issue Type: Bug
>Reporter: Sriharsha Chintalapani
>Assignee: Sriharsha Chintalapani
>Priority: Blocker
> Fix For: 2.5.2
>
> Attachments: AMBARI-21121.patch
>
>




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

[jira] [Commented] (AMBARI-21121) Missing storm-site.xml in HDP-2.6 stack

[Jayush Luniya (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-21121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16025039#comment-16025039
 ] 

Jayush Luniya commented on AMBARI-21121:


Trunk
commit 1e3d64bfeaa59ac471c013cac1a96b1df14921f0
Author: Jayush Luniya 
Date:   Thu May 25 10:00:14 2017 -0700

AMBARI-21121: Missing storm-site.xml in HDP-2.6 stack (Sriharsha 
Chintalapani via jluniya)

> Missing storm-site.xml in HDP-2.6 stack
> ---
>
> Key: AMBARI-21121
> URL: https://issues.apache.org/jira/browse/AMBARI-21121
> Project: Ambari
>  Issue Type: Bug
>Reporter: Sriharsha Chintalapani
>Assignee: Sriharsha Chintalapani
>Priority: Blocker
> Fix For: 2.5.2
>
> Attachments: AMBARI-21121.patch
>
>




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

[jira] [Updated] (AMBARI-21095) Enable opening views in a new tab

[Anita Gnanamalar Jebaraj (JIRA)]

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

Anita Gnanamalar Jebaraj updated AMBARI-21095:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Enable opening views in a new tab
> -
>
> Key: AMBARI-21095
> URL: https://issues.apache.org/jira/browse/AMBARI-21095
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-admin, ambari-web
>Affects Versions: trunk
>Reporter: Anita Gnanamalar Jebaraj
>Assignee: Anita Gnanamalar Jebaraj
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-21095.patch
>
>
> Enable views to be opened in a new tab instead of being opened in the same 
> tab, this would help in going between the different tabs to look for 
> information or for config updates in the services.



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

[jira] [Commented] (AMBARI-21121) Missing storm-site.xml in HDP-2.6 stack

[Jayush Luniya (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-21121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16024923#comment-16024923
 ] 

Jayush Luniya commented on AMBARI-21121:


+1 for the patch

> Missing storm-site.xml in HDP-2.6 stack
> ---
>
> Key: AMBARI-21121
> URL: https://issues.apache.org/jira/browse/AMBARI-21121
> Project: Ambari
>  Issue Type: Bug
>Reporter: Sriharsha Chintalapani
>Assignee: Sriharsha Chintalapani
>Priority: Blocker
> Fix For: 2.5.2
>
> Attachments: AMBARI-21121.patch
>
>




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

[jira] [Commented] (AMBARI-21126) Unit Test Failures in RequiredConfigPropertiesValidatorTest With Certain Versions of Java

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-21126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16024857#comment-16024857
 ] 

Hudson commented on AMBARI-21126:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7539 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/7539/])
AMBARI-21126 Exception message generated based on ordered collections to 
(lpuskas: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=14acc0ae32a274184830a8e7bf847f5ede8ac953])
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/topology/validators/RequiredConfigPropertiesValidatorTest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/topology/validators/RequiredConfigPropertiesValidator.java


> Unit Test Failures in RequiredConfigPropertiesValidatorTest With Certain 
> Versions of Java
> -
>
> Key: AMBARI-21126
> URL: https://issues.apache.org/jira/browse/AMBARI-21126
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Laszlo Puskas
>Assignee: Laszlo Puskas
> Fix For: 3.0.0
>
> Attachments: AMAMBARI-21126.trunk.v2.patch
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> Assertions on formatted strings failed due to the ordering of map entries 
> merged into the message.
> Solution: used ordered maps to make generated strings predictable.



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

[jira] [Updated] (AMBARI-21126) Unit Test Failures in RequiredConfigPropertiesValidatorTest With Certain Versions of Java

[Laszlo Puskas (JIRA)]

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

Laszlo Puskas updated AMBARI-21126:
---
Attachment: (was: AMAMBARI-21126.trunk.v1.patch)

> Unit Test Failures in RequiredConfigPropertiesValidatorTest With Certain 
> Versions of Java
> -
>
> Key: AMBARI-21126
> URL: https://issues.apache.org/jira/browse/AMBARI-21126
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Laszlo Puskas
>Assignee: Laszlo Puskas
> Fix For: 3.0.0
>
> Attachments: AMAMBARI-21126.trunk.v2.patch
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> Assertions on formatted strings failed due to the ordering of map entries 
> merged into the message.
> Solution: used ordered maps to make generated strings predictable.



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

[jira] [Updated] (AMBARI-21126) Unit Test Failures in RequiredConfigPropertiesValidatorTest With Certain Versions of Java

[Laszlo Puskas (JIRA)]

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

Laszlo Puskas updated AMBARI-21126:
---
Attachment: AMAMBARI-21126.trunk.v2.patch

> Unit Test Failures in RequiredConfigPropertiesValidatorTest With Certain 
> Versions of Java
> -
>
> Key: AMBARI-21126
> URL: https://issues.apache.org/jira/browse/AMBARI-21126
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Laszlo Puskas
>Assignee: Laszlo Puskas
> Fix For: 3.0.0
>
> Attachments: AMAMBARI-21126.trunk.v2.patch
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> Assertions on formatted strings failed due to the ordering of map entries 
> merged into the message.
> Solution: used ordered maps to make generated strings predictable.



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

[jira] [Commented] (AMBARI-21126) Unit Test Failures in RequiredConfigPropertiesValidatorTest With Certain Versions of Java

[Laszlo Puskas (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-21126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16024808#comment-16024808
 ] 

Laszlo Puskas commented on AMBARI-21126:


author  lpuskas 
Thu, 25 May 2017 11:52:59 +0200 (11:52 +0200)
committer   lpuskas 
Thu, 25 May 2017 16:42:20 +0200 (16:42 +0200)
commit  14acc0ae32a274184830a8e7bf847f5ede8ac953

> Unit Test Failures in RequiredConfigPropertiesValidatorTest With Certain 
> Versions of Java
> -
>
> Key: AMBARI-21126
> URL: https://issues.apache.org/jira/browse/AMBARI-21126
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Laszlo Puskas
>Assignee: Laszlo Puskas
> Fix For: 3.0.0
>
> Attachments: AMAMBARI-21126.trunk.v2.patch
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> Assertions on formatted strings failed due to the ordering of map entries 
> merged into the message.
> Solution: used ordered maps to make generated strings predictable.



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

[jira] [Commented] (AMBARI-21116) Setting yarn.node-labels.fs-store.root-dir to a "path" changes the permission of the "root path"

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-21116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16024707#comment-16024707
 ] 

Hudson commented on AMBARI-21116:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7538 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/7538/])
AMBARI-21116. Setting yarn.node-labels.fs-store.root-dir to a "path" (aonishuk: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=9dbf8f15e659a19e3b4d8a6cdd7530160089c1dd])
* (edit) ambari-server/src/test/python/stacks/2.0.6/YARN/test_historyserver.py


> Setting yarn.node-labels.fs-store.root-dir to a "path" changes the permission 
> of the "root path"
> 
>
> Key: AMBARI-21116
> URL: https://issues.apache.org/jira/browse/AMBARI-21116
> Project: Ambari
>  Issue Type: Bug
>Reporter: Sumana Sathish
>Assignee: Andrew Onischuk
>Priority: Critical
> Fix For: 2.5.2
>
>
> 1. Set the following configs to run nodeLabels test via Ambari Rest Call
> {code}
>  yarnProperties = {'yarn.acl.enable': 'true',
>   'yarn.node-labels.enabled' : "True",
>   'yarn.node-labels.fs-store.root-dir': 
> NODE_LABEL_STORE_DIR,
>   'yarn.admin.acl': yarn_user + ',' + qa_user}
> {code}
> where NODE_LABEL_STORE_DIR = "/tmp/node-labels"
> 2Restart ResourceManager and NodeManagers via ambari 
> 3. After running these commands,  /tmp directory's permission changes to 
> [drwx--   - yarn   hadoop] from [drwxrwxrwx   - hdfs   hadoop]  causing 
> other tests to fail since it cannot access /tmp  



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

[jira] [Commented] (AMBARI-21116) Setting yarn.node-labels.fs-store.root-dir to a "path" changes the permission of the "root path"

[Doroszlai, Attila (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-21116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16024627#comment-16024627
 ] 

Doroszlai, Attila commented on AMBARI-21116:


Thanks!

> Setting yarn.node-labels.fs-store.root-dir to a "path" changes the permission 
> of the "root path"
> 
>
> Key: AMBARI-21116
> URL: https://issues.apache.org/jira/browse/AMBARI-21116
> Project: Ambari
>  Issue Type: Bug
>Reporter: Sumana Sathish
>Assignee: Andrew Onischuk
>Priority: Critical
> Fix For: 2.5.2
>
>
> 1. Set the following configs to run nodeLabels test via Ambari Rest Call
> {code}
>  yarnProperties = {'yarn.acl.enable': 'true',
>   'yarn.node-labels.enabled' : "True",
>   'yarn.node-labels.fs-store.root-dir': 
> NODE_LABEL_STORE_DIR,
>   'yarn.admin.acl': yarn_user + ',' + qa_user}
> {code}
> where NODE_LABEL_STORE_DIR = "/tmp/node-labels"
> 2Restart ResourceManager and NodeManagers via ambari 
> 3. After running these commands,  /tmp directory's permission changes to 
> [drwx--   - yarn   hadoop] from [drwxrwxrwx   - hdfs   hadoop]  causing 
> other tests to fail since it cannot access /tmp  



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

[jira] [Commented] (AMBARI-21116) Setting yarn.node-labels.fs-store.root-dir to a "path" changes the permission of the "root path"

[Andrew Onischuk (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-21116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16024622#comment-16024622
 ] 

Andrew Onischuk commented on AMBARI-21116:
--

thanks [~adoroszlai]. Committed the fix.

> Setting yarn.node-labels.fs-store.root-dir to a "path" changes the permission 
> of the "root path"
> 
>
> Key: AMBARI-21116
> URL: https://issues.apache.org/jira/browse/AMBARI-21116
> Project: Ambari
>  Issue Type: Bug
>Reporter: Sumana Sathish
>Assignee: Andrew Onischuk
>Priority: Critical
> Fix For: 2.5.2
>
>
> 1. Set the following configs to run nodeLabels test via Ambari Rest Call
> {code}
>  yarnProperties = {'yarn.acl.enable': 'true',
>   'yarn.node-labels.enabled' : "True",
>   'yarn.node-labels.fs-store.root-dir': 
> NODE_LABEL_STORE_DIR,
>   'yarn.admin.acl': yarn_user + ',' + qa_user}
> {code}
> where NODE_LABEL_STORE_DIR = "/tmp/node-labels"
> 2Restart ResourceManager and NodeManagers via ambari 
> 3. After running these commands,  /tmp directory's permission changes to 
> [drwx--   - yarn   hadoop] from [drwxrwxrwx   - hdfs   hadoop]  causing 
> other tests to fail since it cannot access /tmp  



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

[jira] [Comment Edited] (AMBARI-21116) Setting yarn.node-labels.fs-store.root-dir to a "path" changes the permission of the "root path"

[Doroszlai, Attila (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-21116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16024613#comment-16024613
 ] 

Doroszlai, Attila edited comment on AMBARI-21116 at 5/25/17 11:59 AM:
--

[~aonishuk], can you please change python unit test as well?  It's 
[failing|https://builds.apache.org/job/Ambari-trunk-Commit/7531/consoleText] 
since this commit.

{noformat}
FAIL: test_configure_default (test_historyserver.TestHistoryServer)
FAIL: test_configure_secured (test_historyserver.TestHistoryServer)
FAIL: test_start_default (test_historyserver.TestHistoryServer)
FAIL: test_start_secured (test_historyserver.TestHistoryServer)
{noformat}


was (Author: adoroszlai):
[~aonishuk], can you please change python unit test as well, it's 
[failing|https://builds.apache.org/job/Ambari-trunk-Commit/7531/consoleText] 
since this comit?

{noformat}
FAIL: test_configure_default (test_historyserver.TestHistoryServer)
FAIL: test_configure_secured (test_historyserver.TestHistoryServer)
FAIL: test_start_default (test_historyserver.TestHistoryServer)
FAIL: test_start_secured (test_historyserver.TestHistoryServer)
{noformat}

> Setting yarn.node-labels.fs-store.root-dir to a "path" changes the permission 
> of the "root path"
> 
>
> Key: AMBARI-21116
> URL: https://issues.apache.org/jira/browse/AMBARI-21116
> Project: Ambari
>  Issue Type: Bug
>Reporter: Sumana Sathish
>Assignee: Andrew Onischuk
>Priority: Critical
> Fix For: 2.5.2
>
>
> 1. Set the following configs to run nodeLabels test via Ambari Rest Call
> {code}
>  yarnProperties = {'yarn.acl.enable': 'true',
>   'yarn.node-labels.enabled' : "True",
>   'yarn.node-labels.fs-store.root-dir': 
> NODE_LABEL_STORE_DIR,
>   'yarn.admin.acl': yarn_user + ',' + qa_user}
> {code}
> where NODE_LABEL_STORE_DIR = "/tmp/node-labels"
> 2Restart ResourceManager and NodeManagers via ambari 
> 3. After running these commands,  /tmp directory's permission changes to 
> [drwx--   - yarn   hadoop] from [drwxrwxrwx   - hdfs   hadoop]  causing 
> other tests to fail since it cannot access /tmp  



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

[jira] [Updated] (AMBARI-21097) Edit notifications options are always grey but can click and open a popup

[Yao Lei (JIRA)]

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

Yao Lei updated AMBARI-21097:
-
   Resolution: Won't Do
Fix Version/s: (was: 3.0.0)
   2.5.1
   Status: Resolved  (was: Patch Available)

> Edit notifications options are always grey but can click and open a popup
> -
>
> Key: AMBARI-21097
> URL: https://issues.apache.org/jira/browse/AMBARI-21097
> Project: Ambari
>  Issue Type: Improvement
>Affects Versions: 2.5.0
>Reporter: Yao Lei
>Assignee: Yao Lei
> Fix For: 2.5.1
>
> Attachments: AMBARI-21097.patch, notification.png
>
>
> STR:
> 1.Open Alerts / Actions / Manage Alert Notifications
> 2.Create an alert notification named test
> 3.Select the created notification and click gear icon, you will find 
> Edit/Duplicate items are always grey but you can click and open a popup.



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

[jira] [Commented] (AMBARI-21116) Setting yarn.node-labels.fs-store.root-dir to a "path" changes the permission of the "root path"

[Doroszlai, Attila (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-21116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16024613#comment-16024613
 ] 

Doroszlai, Attila commented on AMBARI-21116:


[~aonishuk], can you please change python unit test as well, it's 
[failing|https://builds.apache.org/job/Ambari-trunk-Commit/7531/consoleText] 
since this comit?

{noformat}
FAIL: test_configure_default (test_historyserver.TestHistoryServer)
FAIL: test_configure_secured (test_historyserver.TestHistoryServer)
FAIL: test_start_default (test_historyserver.TestHistoryServer)
FAIL: test_start_secured (test_historyserver.TestHistoryServer)
{noformat}

> Setting yarn.node-labels.fs-store.root-dir to a "path" changes the permission 
> of the "root path"
> 
>
> Key: AMBARI-21116
> URL: https://issues.apache.org/jira/browse/AMBARI-21116
> Project: Ambari
>  Issue Type: Bug
>Reporter: Sumana Sathish
>Assignee: Andrew Onischuk
>Priority: Critical
> Fix For: 2.5.2
>
>
> 1. Set the following configs to run nodeLabels test via Ambari Rest Call
> {code}
>  yarnProperties = {'yarn.acl.enable': 'true',
>   'yarn.node-labels.enabled' : "True",
>   'yarn.node-labels.fs-store.root-dir': 
> NODE_LABEL_STORE_DIR,
>   'yarn.admin.acl': yarn_user + ',' + qa_user}
> {code}
> where NODE_LABEL_STORE_DIR = "/tmp/node-labels"
> 2Restart ResourceManager and NodeManagers via ambari 
> 3. After running these commands,  /tmp directory's permission changes to 
> [drwx--   - yarn   hadoop] from [drwxrwxrwx   - hdfs   hadoop]  causing 
> other tests to fail since it cannot access /tmp  



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

[jira] [Commented] (AMBARI-21097) Edit notifications options are always grey but can click and open a popup

[Yao Lei (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-21097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16024614#comment-16024614
 ] 

Yao Lei commented on AMBARI-21097:
--

This patch is just useful for 2.5

> Edit notifications options are always grey but can click and open a popup
> -
>
> Key: AMBARI-21097
> URL: https://issues.apache.org/jira/browse/AMBARI-21097
> Project: Ambari
>  Issue Type: Improvement
>Affects Versions: 2.5.0
>Reporter: Yao Lei
>Assignee: Yao Lei
> Fix For: 3.0.0
>
> Attachments: AMBARI-21097.patch, notification.png
>
>
> STR:
> 1.Open Alerts / Actions / Manage Alert Notifications
> 2.Create an alert notification named test
> 3.Select the created notification and click gear icon, you will find 
> Edit/Duplicate items are always grey but you can click and open a popup.



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

[jira] [Updated] (AMBARI-21099) Support services to use different JDKs (7 & 8)

[JIRA]

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

Olivér Szabó updated AMBARI-21099:
--
Description: 
Requirements:
- ambari should drop JDK 7 support for ambari-server and ambari-managed 
services (infra, ams, logsearch)
- HDP 2.x should be still able to use JDK 1.7
Changes in ambari setup:
1. First the usual ambari setup
{code:java}
Choose JDK for Ambari and Stack services:
[1] Oracle JDK 1.8 + Java Cryptography Extension (JCE) Policy Files 8
[2] Oracle JDK 1.7 + Java Cryptography Extension (JCE) Policy Files 7
[3] Custom JDK
{code}
2. If JDK 7 is picked, that cannot be used for ambari (only for the stack 
services)
{code:java}
JDK 7 is detected (JDK 8 required for ambari-server), install JDK 8 as well:
[1] Oracle JDK 1.8 + Java Cryptography Extension (JCE) Policy Files 8
[3] Custom JDK
{code}

After the commands are executed, the following properties would appear in 
ambari.properties
{code:java}
stack.java.home=/usr/jdk64/jdk1.7.0_67
stack.jdk.name=jdk-7u67linux-x64.tar.gz
stack.jce.name=UnlimitedJCEPolicyJDK7.zip
{code}
or opposite of it:
{code:java}
ambari.java.home=/usr/jdk64/jdk1.8.0_112
ambari.jdk.name=jdk-8u112linux-x64.tar.gz
ambari.jce.name=UnlimitedJCEPolicyJDK8.zip
{code}

During command.json generating, hostParameters would be filled with the proper 
jdk,jce info (different for infra/logsearch/ams from other services)

Also that requires to add JDK version check at the start of the ambari-upgrade. 
(tell the user to call ambari-server setup first)





  was:
Some of the services requires at least Java 8 in the future (like. infra-solr 
in ambari 3.0 or hadoop-3.0 in hdp 3.0), other than that we should still 
support JDK 7 as well for ambari-server.

In order to achieve that, ambari will need to install a JDK 8 even if JDK 7 is 
selected during ambari-server setup (that is the minimum right now)

Changes in ambari setup:
from
{code:java}
[1] Oracle JDK 1.8 + Java Cryptography Extension (JCE) Policy Files 8
[2] Oracle JDK 1.7 + Java Cryptography Extension (JCE) Policy Files 7
[3] Custom JDK
{code}
to
{code:java}
[1] Oracle JDK 1.8 + Java Cryptography Extension (JCE) Policy Files 8
[2] Oracle JDK 1.7 / 1.8 + Java Cryptography Extension (JCE) Policy Files 7 / 8
[3] Custom JDK
{code}
JDK 7 pick will install a JDK8/JCE-8 as well. It will generate 3 new properties 
in ambari.properties file:
{code:java}
java8.home=/usr/jdk64/jdk1.8.0_112
jdk8.name=jdk-8u112-linux-x64.tar.gz
jce8.name=UnlimitedJCEPolicyJDK8.zip
{code}

On service stack side, there will be a new tag in the metainfo.xml (in service 
info) called {{minJdk}}
{code:java}
...  
  

  AMBARI_INFRA
  Ambari Infra
  Core shared service used by Ambari managed components.
  0.1.0
  1.8
  ...
{code}

If minJdk is set to 1.8, the default {{java_home}},{{jdk_name}} and 
{{jce_name}} hostParams in command.jsons will be replaced with the new config 
entries from ambari.properties file, so specific services could use jdk 1.8, 
and ambari will be able to still use 1.7 (if that is the requirement). On 
ambari upgrade scenarios: these 3 properties should be added to 
ambari.properties if jdk 1.7 was used before. (same is true if custom jdk is 
used with 1.7)






> Support services to use different JDKs (7 & 8)
> --
>
> Key: AMBARI-21099
> URL: https://issues.apache.org/jira/browse/AMBARI-21099
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 3.0.0
>
> Attachments: AMBARI-21099.patch
>
>
> Requirements:
> - ambari should drop JDK 7 support for ambari-server and ambari-managed 
> services (infra, ams, logsearch)
> - HDP 2.x should be still able to use JDK 1.7
> Changes in ambari setup:
> 1. First the usual ambari setup
> {code:java}
> Choose JDK for Ambari and Stack services:
> [1] Oracle JDK 1.8 + Java Cryptography Extension (JCE) Policy Files 8
> [2] Oracle JDK 1.7 + Java Cryptography Extension (JCE) Policy Files 7
> [3] Custom JDK
> {code}
> 2. If JDK 7 is picked, that cannot be used for ambari (only for the stack 
> services)
> {code:java}
> JDK 7 is detected (JDK 8 required for ambari-server), install JDK 8 as well:
> [1] Oracle JDK 1.8 + Java Cryptography Extension (JCE) Policy Files 8
> [3] Custom JDK
> {code}
> After the commands are executed, the following properties would appear in 
> ambari.properties
> {code:java}
> stack.java.home=/usr/jdk64/jdk1.7.0_67
> stack.jdk.name=jdk-7u67linux-x64.tar.gz
> stack.jce.name=UnlimitedJCEPolicyJDK7.zip
> {code}
> or opposite of it:
> {code:java}
> ambari.java.home=/usr/jdk64/jdk1.8.0_112
> ambari.jdk.name=jdk-8u112linux-x64.tar.gz
> ambari.jce.name=UnlimitedJCEPolicyJDK8.zip
> {code}
> During command.json generating, 

[jira] [Updated] (AMBARI-21099) Drop JDK 7 support for Ambari Server and Ambari managed services (AMS, LogSearch,Infra)

[JIRA]

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

Olivér Szabó updated AMBARI-21099:
--
Summary: Drop JDK 7 support for Ambari Server and Ambari managed services 
(AMS, LogSearch,Infra)  (was: Drop JDK 7 support for Ambari Server and Ambari 
managed services)

> Drop JDK 7 support for Ambari Server and Ambari managed services (AMS, 
> LogSearch,Infra)
> ---
>
> Key: AMBARI-21099
> URL: https://issues.apache.org/jira/browse/AMBARI-21099
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 3.0.0
>
> Attachments: AMBARI-21099.patch
>
>
> Requirements:
> - ambari should drop JDK 7 support for ambari-server and ambari-managed 
> services (infra, ams, logsearch)
> - HDP 2.x should be still able to use JDK 1.7
> Changes in ambari setup:
> 1. First the usual ambari setup
> {code:java}
> Choose JDK for Ambari and Stack services:
> [1] Oracle JDK 1.8 + Java Cryptography Extension (JCE) Policy Files 8
> [2] Oracle JDK 1.7 + Java Cryptography Extension (JCE) Policy Files 7
> [3] Custom JDK
> {code}
> 2. If JDK 7 is picked, that cannot be used for ambari (only for the stack 
> services)
> {code:java}
> JDK 7 is detected (JDK 8 required for ambari-server), install JDK 8 as well:
> [1] Oracle JDK 1.8 + Java Cryptography Extension (JCE) Policy Files 8
> [3] Custom JDK
> {code}
> After the commands are executed, the following properties would appear in 
> ambari.properties
> {code:java}
> stack.java.home=/usr/jdk64/jdk1.7.0_67
> stack.jdk.name=jdk-7u67linux-x64.tar.gz
> stack.jce.name=UnlimitedJCEPolicyJDK7.zip
> {code}
> or opposite of it:
> {code:java}
> ambari.java.home=/usr/jdk64/jdk1.8.0_112
> ambari.jdk.name=jdk-8u112linux-x64.tar.gz
> ambari.jce.name=UnlimitedJCEPolicyJDK8.zip
> {code}
> During command.json generating, hostParameters would be filled with the 
> proper jdk,jce info (different for infra/logsearch/ams from other services)
> Also that requires to add JDK version check at the start of the 
> ambari-upgrade. (tell the user to call ambari-server setup first)



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

[jira] [Updated] (AMBARI-21099) Drop JDK 7 support for Ambari Server and Ambari managed services

[JIRA]

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

Olivér Szabó updated AMBARI-21099:
--
Summary: Drop JDK 7 support for Ambari Server and Ambari managed services  
(was: Support services to use different JDKs (7 & 8))

> Drop JDK 7 support for Ambari Server and Ambari managed services
> 
>
> Key: AMBARI-21099
> URL: https://issues.apache.org/jira/browse/AMBARI-21099
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 3.0.0
>
> Attachments: AMBARI-21099.patch
>
>
> Requirements:
> - ambari should drop JDK 7 support for ambari-server and ambari-managed 
> services (infra, ams, logsearch)
> - HDP 2.x should be still able to use JDK 1.7
> Changes in ambari setup:
> 1. First the usual ambari setup
> {code:java}
> Choose JDK for Ambari and Stack services:
> [1] Oracle JDK 1.8 + Java Cryptography Extension (JCE) Policy Files 8
> [2] Oracle JDK 1.7 + Java Cryptography Extension (JCE) Policy Files 7
> [3] Custom JDK
> {code}
> 2. If JDK 7 is picked, that cannot be used for ambari (only for the stack 
> services)
> {code:java}
> JDK 7 is detected (JDK 8 required for ambari-server), install JDK 8 as well:
> [1] Oracle JDK 1.8 + Java Cryptography Extension (JCE) Policy Files 8
> [3] Custom JDK
> {code}
> After the commands are executed, the following properties would appear in 
> ambari.properties
> {code:java}
> stack.java.home=/usr/jdk64/jdk1.7.0_67
> stack.jdk.name=jdk-7u67linux-x64.tar.gz
> stack.jce.name=UnlimitedJCEPolicyJDK7.zip
> {code}
> or opposite of it:
> {code:java}
> ambari.java.home=/usr/jdk64/jdk1.8.0_112
> ambari.jdk.name=jdk-8u112linux-x64.tar.gz
> ambari.jce.name=UnlimitedJCEPolicyJDK8.zip
> {code}
> During command.json generating, hostParameters would be filled with the 
> proper jdk,jce info (different for infra/logsearch/ams from other services)
> Also that requires to add JDK version check at the start of the 
> ambari-upgrade. (tell the user to call ambari-server setup first)



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

[jira] [Commented] (AMBARI-21111) Ambari 3.0: Outstanding navigation issues

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16024579#comment-16024579
 ] 

Hudson commented on AMBARI-2:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7537 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/7537/])
AMBARI-2 Ambari 3.0: Outstanding navigation issues. (atkach) (atkach: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=cd68c616177248911d7cba085cc584e76e7e])
* (edit) ambari-web/app/styles/alerts.less
* (edit) ambari-web/app/templates/main/service/menu_item.hbs
* (edit) ambari-web/app/styles/application.less
* (edit) ambari-web/app/styles/config_history_flow.less
* (edit) ambari-web/app/views/main/service/menu.js
* (edit) ambari-admin/src/main/resources/ui/admin-web/app/styles/main.css
* (edit) ambari-web/app/styles/common.less
* (edit) ambari-web/app/styles/theme/bootstrap-ambari.css
* (edit) ambari-web/app/views/main/menu.js
* (edit) ambari-web/test/views/main/service/menu_test.js


> Ambari 3.0: Outstanding navigation issues
> -
>
> Key: AMBARI-2
> URL: https://issues.apache.org/jira/browse/AMBARI-2
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-admin, ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: Action Bar.png, AMBARI-2.patch, Ambari metrics not 
> complete by default. .png, logo color and bar not same.png, Navigation 
> changes.png, two dark bar color not consistent .png
>
>
> Following are the outstanding issues with Ambari navigation:
> * Remove the Service status icon
> * Alert icon should be circle and positioned in front of service name
> * Do we need the green indicator for the selected menu?
> * Services with master down should be indicated by red (service name is red 
> and show the original tooltip on hovering "Namenode is stopped" .etc)
> Other issues:
> * Make sure "Ambari Metrics" text is displaying completely without ellipsis 
> after the above changes. If still not visible (as attached), should increase 
> the width of side navigation.
> * On Service configs page, the black horizontal bar and side navigation are 
> not consistent in color. One is black, the other is navy.
> * On Manage Ambari page, ambari logo is not the same color as the background.



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

[jira] [Updated] (AMBARI-21128) Add AMS HA support to local metrics aggregator application

[Dmytro Sen (JIRA)]

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

Dmytro Sen updated AMBARI-21128:

Attachment: AMBARI-21128.patch

> Add AMS HA support to local metrics aggregator application
> --
>
> Key: AMBARI-21128
> URL: https://issues.apache.org/jira/browse/AMBARI-21128
> Project: Ambari
>  Issue Type: Task
>Affects Versions: 3.0.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
> Fix For: 3.0.0
>
> Attachments: AMBARI-21128.patch
>
>
> Add AMS HA support for local in-memory metrics aggregation application 
> implemented in  AMBARI-20758
> This include switching to working collector



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

[jira] [Created] (AMBARI-21128) Add AMS HA support to local metrics aggregator application

[Dmytro Sen (JIRA)]

Dmytro Sen created AMBARI-21128:
---

 Summary: Add AMS HA support to local metrics aggregator application
 Key: AMBARI-21128
 URL: https://issues.apache.org/jira/browse/AMBARI-21128
 Project: Ambari
  Issue Type: Task
Affects Versions: 3.0.0
Reporter: Dmytro Sen
Assignee: Dmytro Sen
 Fix For: 3.0.0


Add AMS HA support for local in-memory metrics aggregation application 
implemented in  AMBARI-20758
This include switching to working collector



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

[jira] [Commented] (AMBARI-21097) Edit notifications options are always grey but can click and open a popup

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-21097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16024569#comment-16024569
 ] 

Hadoop QA commented on AMBARI-21097:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12869405/AMBARI-21097.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/11613//console

This message is automatically generated.

> Edit notifications options are always grey but can click and open a popup
> -
>
> Key: AMBARI-21097
> URL: https://issues.apache.org/jira/browse/AMBARI-21097
> Project: Ambari
>  Issue Type: Improvement
>Affects Versions: 2.5.0
>Reporter: Yao Lei
>Assignee: Yao Lei
> Fix For: 3.0.0
>
> Attachments: AMBARI-21097.patch, notification.png
>
>
> STR:
> 1.Open Alerts / Actions / Manage Alert Notifications
> 2.Create an alert notification named test
> 3.Select the created notification and click gear icon, you will find 
> Edit/Duplicate items are always grey but you can click and open a popup.



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

[jira] [Updated] (AMBARI-21097) Edit notifications options are always grey but can click and open a popup

[Antonenko Alexander (JIRA)]

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

Antonenko Alexander updated AMBARI-21097:
-
Fix Version/s: (was: 2.5.2)
   3.0.0

> Edit notifications options are always grey but can click and open a popup
> -
>
> Key: AMBARI-21097
> URL: https://issues.apache.org/jira/browse/AMBARI-21097
> Project: Ambari
>  Issue Type: Improvement
>Affects Versions: 2.5.0
>Reporter: Yao Lei
>Assignee: Yao Lei
> Fix For: 3.0.0
>
> Attachments: AMBARI-21097.patch, notification.png
>
>
> STR:
> 1.Open Alerts / Actions / Manage Alert Notifications
> 2.Create an alert notification named test
> 3.Select the created notification and click gear icon, you will find 
> Edit/Duplicate items are always grey but you can click and open a popup.



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

[jira] [Updated] (AMBARI-21102) To/From Version Information is Incorrect When Looking at Prior Upgrades

[Antonenko Alexander (JIRA)]

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

Antonenko Alexander updated AMBARI-21102:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

committed to branch-feature-AMBARI-12556

> To/From Version Information is Incorrect When Looking at Prior Upgrades
> ---
>
> Key: AMBARI-21102
> URL: https://issues.apache.org/jira/browse/AMBARI-21102
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 3.0.0
>
> Attachments: AMBARI-21102.patch, Screen Shot 2017-05-19 at 2.50.50 
> PM.png, Screen Shot 2017-05-19 at 2.51.04 PM.png
>
>
> Create a SERVICE or PATCH upgrade for a single service. Once the upgrade 
> completes, the "Upgrade History" section of Ambari contains incorrect 
> information:
> - The upgrade says "Upgrade from 2.5.4.0", yet 2.5.4.0 was the target. It 
> should say "Upgrade to 2.5.4.0". When dowgrading, it should use the "from" 
> preposition.
> - The To/From fields are still present in the list of upgrades, and they are 
> blank. They should be removed and a per-service display should be used 
> instead.



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

[jira] [Commented] (AMBARI-21102) To/From Version Information is Incorrect When Looking at Prior Upgrades

[Oleg Nechiporenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-21102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16024555#comment-16024555
 ] 

Oleg Nechiporenko commented on AMBARI-21102:


+1 for patch

> To/From Version Information is Incorrect When Looking at Prior Upgrades
> ---
>
> Key: AMBARI-21102
> URL: https://issues.apache.org/jira/browse/AMBARI-21102
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 3.0.0
>
> Attachments: AMBARI-21102.patch, Screen Shot 2017-05-19 at 2.50.50 
> PM.png, Screen Shot 2017-05-19 at 2.51.04 PM.png
>
>
> Create a SERVICE or PATCH upgrade for a single service. Once the upgrade 
> completes, the "Upgrade History" section of Ambari contains incorrect 
> information:
> - The upgrade says "Upgrade from 2.5.4.0", yet 2.5.4.0 was the target. It 
> should say "Upgrade to 2.5.4.0". When dowgrading, it should use the "from" 
> preposition.
> - The To/From fields are still present in the list of upgrades, and they are 
> blank. They should be removed and a per-service display should be used 
> instead.



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

[jira] [Updated] (AMBARI-21102) To/From Version Information is Incorrect When Looking at Prior Upgrades

[Antonenko Alexander (JIRA)]

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

Antonenko Alexander updated AMBARI-21102:
-
Attachment: AMBARI-21102.patch

> To/From Version Information is Incorrect When Looking at Prior Upgrades
> ---
>
> Key: AMBARI-21102
> URL: https://issues.apache.org/jira/browse/AMBARI-21102
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 3.0.0
>
> Attachments: AMBARI-21102.patch, Screen Shot 2017-05-19 at 2.50.50 
> PM.png, Screen Shot 2017-05-19 at 2.51.04 PM.png
>
>
> Create a SERVICE or PATCH upgrade for a single service. Once the upgrade 
> completes, the "Upgrade History" section of Ambari contains incorrect 
> information:
> - The upgrade says "Upgrade from 2.5.4.0", yet 2.5.4.0 was the target. It 
> should say "Upgrade to 2.5.4.0". When dowgrading, it should use the "from" 
> preposition.
> - The To/From fields are still present in the list of upgrades, and they are 
> blank. They should be removed and a per-service display should be used 
> instead.



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

[jira] [Updated] (AMBARI-21102) To/From Version Information is Incorrect When Looking at Prior Upgrades

[Antonenko Alexander (JIRA)]

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

Antonenko Alexander updated AMBARI-21102:
-
Status: Patch Available  (was: Open)

> To/From Version Information is Incorrect When Looking at Prior Upgrades
> ---
>
> Key: AMBARI-21102
> URL: https://issues.apache.org/jira/browse/AMBARI-21102
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 3.0.0
>
> Attachments: AMBARI-21102.patch, Screen Shot 2017-05-19 at 2.50.50 
> PM.png, Screen Shot 2017-05-19 at 2.51.04 PM.png
>
>
> Create a SERVICE or PATCH upgrade for a single service. Once the upgrade 
> completes, the "Upgrade History" section of Ambari contains incorrect 
> information:
> - The upgrade says "Upgrade from 2.5.4.0", yet 2.5.4.0 was the target. It 
> should say "Upgrade to 2.5.4.0". When dowgrading, it should use the "from" 
> preposition.
> - The To/From fields are still present in the list of upgrades, and they are 
> blank. They should be removed and a per-service display should be used 
> instead.



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

[jira] [Resolved] (AMBARI-21127) To/From Version Information is Incorrect When Looking at Prior Upgrades

[Antonenko Alexander (JIRA)]

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

Antonenko Alexander resolved AMBARI-21127.
--
Resolution: Duplicate

> To/From Version Information is Incorrect When Looking at Prior Upgrades
> ---
>
> Key: AMBARI-21127
> URL: https://issues.apache.org/jira/browse/AMBARI-21127
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 3.0.0
>
>
> Create a SERVICE or PATCH upgrade for a single service. Once the upgrade 
> completes, the "Upgrade History" section of Ambari contains incorrect 
> information:
> - The upgrade says "Upgrade from 2.5.4.0", yet 2.5.4.0 was the target. It 
> should say "Upgrade to 2.5.4.0". When dowgrading, it should use the "from" 
> preposition.
> - The To/From fields are still present in the list of upgrades, and they are 
> blank. They should be removed and a per-service display should be used 
> instead.



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

[jira] [Created] (AMBARI-21127) To/From Version Information is Incorrect When Looking at Prior Upgrades

[Antonenko Alexander (JIRA)]

Antonenko Alexander created AMBARI-21127:


 Summary: To/From Version Information is Incorrect When Looking at 
Prior Upgrades
 Key: AMBARI-21127
 URL: https://issues.apache.org/jira/browse/AMBARI-21127
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 3.0.0
Reporter: Antonenko Alexander
Assignee: Antonenko Alexander
 Fix For: 3.0.0


Create a SERVICE or PATCH upgrade for a single service. Once the upgrade 
completes, the "Upgrade History" section of Ambari contains incorrect 
information:

- The upgrade says "Upgrade from 2.5.4.0", yet 2.5.4.0 was the target. It 
should say "Upgrade to 2.5.4.0". When dowgrading, it should use the "from" 
preposition.

- The To/From fields are still present in the list of upgrades, and they are 
blank. They should be removed and a per-service display should be used instead.



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

[jira] [Commented] (AMBARI-21117) Existing hosts state didn't save after host was added

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-21117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16024513#comment-16024513
 ] 

Hudson commented on AMBARI-21117:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7536 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/7536/])
AMBARI-21117. Existing hosts state didn't save after host was added (hiveww: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=91d10fdc849f884f7e215a4006a843f2f91b9ea3])
* (edit) ambari-web/app/controllers/wizard.js
* (edit) ambari-web/test/controllers/main/host/add_controller_test.js
* (edit) ambari-web/app/controllers/main/host/add_controller.js
* (edit) ambari-web/app/routes/add_host_routes.js
* (edit) ambari-web/test/controllers/wizard_test.js


> Existing hosts state didn't save after host was added
> -
>
> Key: AMBARI-21117
> URL: https://issues.apache.org/jira/browse/AMBARI-21117
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.1
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.5.2
>
> Attachments: AMBARI-21117.patch
>
>
> Existing hosts state didn't save after host was added. In next test add host 
> wizard stay open.
> When we connect to cluster - automatically redirect on add host wizard. 
> (attached screenshot)
> First step validation passed and host registered successfully. 
> On Review Page, when we clicked Deploy we had popup with error that this host 
> already part of cluster.
> If we cluster wizard and try it again - validation on first step not passed



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

[jira] [Updated] (AMBARI-21111) Ambari 3.0: Outstanding navigation issues

[Andrii Tkach (JIRA)]

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

Andrii Tkach updated AMBARI-2:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Ambari 3.0: Outstanding navigation issues
> -
>
> Key: AMBARI-2
> URL: https://issues.apache.org/jira/browse/AMBARI-2
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-admin, ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: Action Bar.png, AMBARI-2.patch, Ambari metrics not 
> complete by default. .png, logo color and bar not same.png, Navigation 
> changes.png, two dark bar color not consistent .png
>
>
> Following are the outstanding issues with Ambari navigation:
> * Remove the Service status icon
> * Alert icon should be circle and positioned in front of service name
> * Do we need the green indicator for the selected menu?
> * Services with master down should be indicated by red (service name is red 
> and show the original tooltip on hovering "Namenode is stopped" .etc)
> Other issues:
> * Make sure "Ambari Metrics" text is displaying completely without ellipsis 
> after the above changes. If still not visible (as attached), should increase 
> the width of side navigation.
> * On Service configs page, the black horizontal bar and side navigation are 
> not consistent in color. One is black, the other is navy.
> * On Manage Ambari page, ambari logo is not the same color as the background.



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

[jira] [Commented] (AMBARI-21111) Ambari 3.0: Outstanding navigation issues

[Andrii Tkach (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16024475#comment-16024475
 ] 

Andrii Tkach commented on AMBARI-2:
---

committed to trunk

> Ambari 3.0: Outstanding navigation issues
> -
>
> Key: AMBARI-2
> URL: https://issues.apache.org/jira/browse/AMBARI-2
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-admin, ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: Action Bar.png, AMBARI-2.patch, Ambari metrics not 
> complete by default. .png, logo color and bar not same.png, Navigation 
> changes.png, two dark bar color not consistent .png
>
>
> Following are the outstanding issues with Ambari navigation:
> * Remove the Service status icon
> * Alert icon should be circle and positioned in front of service name
> * Do we need the green indicator for the selected menu?
> * Services with master down should be indicated by red (service name is red 
> and show the original tooltip on hovering "Namenode is stopped" .etc)
> Other issues:
> * Make sure "Ambari Metrics" text is displaying completely without ellipsis 
> after the above changes. If still not visible (as attached), should increase 
> the width of side navigation.
> * On Service configs page, the black horizontal bar and side navigation are 
> not consistent in color. One is black, the other is navy.
> * On Manage Ambari page, ambari logo is not the same color as the background.



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

[jira] [Updated] (AMBARI-21089) Host health tooltips going off the screen cannot read the alert details

[Hari Sekhon (JIRA)]

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

Hari Sekhon updated AMBARI-21089:
-
Attachment: tooltip off top of screen cannot read.png

> Host health tooltips going off the screen cannot read the alert details
> ---
>
> Key: AMBARI-21089
> URL: https://issues.apache.org/jira/browse/AMBARI-21089
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
> Environment: HDP 2.5
>Reporter: Hari Sekhon
>Priority: Minor
> Attachments: Ambari pop up off left edge of screen.png, tooltip off 
> top of screen cannot read.png
>
>
> The Host health indicator tool tip on the Host page is displaying to far off 
> the left of the screen, I've seen this before at different clients.
> See screenshot, you can't see if it's complaining about Ambari Agent or 
> SmartSense Agent being down as you can't read the first bit of the tool tip.



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

[jira] [Commented] (AMBARI-21089) Host health tooltips going off the screen cannot read the alert details

[Hari Sekhon (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-21089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16024473#comment-16024473
 ] 

Hari Sekhon commented on AMBARI-21089:
--

I'm attaching another screenshot of another tool tip going too far up off the 
browser such that I can never read the start of the error message.

> Host health tooltips going off the screen cannot read the alert details
> ---
>
> Key: AMBARI-21089
> URL: https://issues.apache.org/jira/browse/AMBARI-21089
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
> Environment: HDP 2.5
>Reporter: Hari Sekhon
>Priority: Minor
> Attachments: Ambari pop up off left edge of screen.png
>
>
> The Host health indicator tool tip on the Host page is displaying to far off 
> the left of the screen, I've seen this before at different clients.
> See screenshot, you can't see if it's complaining about Ambari Agent or 
> SmartSense Agent being down as you can't read the first bit of the tool tip.



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

[jira] [Updated] (AMBARI-21089) Host health tooltips going off the screen cannot read the alert details

[Hari Sekhon (JIRA)]

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

Hari Sekhon updated AMBARI-21089:
-
Summary: Host health tooltips going off the screen cannot read the alert 
details  (was: Host health tooltip is too far left off browser window/screen to 
be read)

> Host health tooltips going off the screen cannot read the alert details
> ---
>
> Key: AMBARI-21089
> URL: https://issues.apache.org/jira/browse/AMBARI-21089
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
> Environment: HDP 2.5
>Reporter: Hari Sekhon
>Priority: Minor
> Attachments: Ambari pop up off left edge of screen.png
>
>
> The Host health indicator tool tip on the Host page is displaying to far off 
> the left of the screen, I've seen this before at different clients.
> See screenshot, you can't see if it's complaining about Ambari Agent or 
> SmartSense Agent being down as you can't read the first bit of the tool tip.



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

[jira] [Updated] (AMBARI-21126) Unit Test Failures in RequiredConfigPropertiesValidatorTest With Certain Versions of Java

[Laszlo Puskas (JIRA)]

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

Laszlo Puskas updated AMBARI-21126:
---
Status: Patch Available  (was: In Progress)

> Unit Test Failures in RequiredConfigPropertiesValidatorTest With Certain 
> Versions of Java
> -
>
> Key: AMBARI-21126
> URL: https://issues.apache.org/jira/browse/AMBARI-21126
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Laszlo Puskas
>Assignee: Laszlo Puskas
> Fix For: 3.0.0
>
> Attachments: AMAMBARI-21126.trunk.v1.patch
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> Assertions on formatted strings failed due to the ordering of map entries 
> merged into the message.
> Solution: used ordered maps to make generated strings predictable.



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

[jira] [Updated] (AMBARI-21126) Unit Test Failures in RequiredConfigPropertiesValidatorTest With Certain Versions of Java

[Laszlo Puskas (JIRA)]

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

Laszlo Puskas updated AMBARI-21126:
---
Attachment: AMAMBARI-21126.trunk.v1.patch

> Unit Test Failures in RequiredConfigPropertiesValidatorTest With Certain 
> Versions of Java
> -
>
> Key: AMBARI-21126
> URL: https://issues.apache.org/jira/browse/AMBARI-21126
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Laszlo Puskas
>Assignee: Laszlo Puskas
> Fix For: 3.0.0
>
> Attachments: AMAMBARI-21126.trunk.v1.patch
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> Assertions on formatted strings failed due to the ordering of map entries 
> merged into the message.
> Solution: used ordered maps to make generated strings predictable.



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

[jira] [Created] (AMBARI-21126) Unit Test Failures in RequiredConfigPropertiesValidatorTest With Certain Versions of Java

[Laszlo Puskas (JIRA)]

Laszlo Puskas created AMBARI-21126:
--

 Summary: Unit Test Failures in 
RequiredConfigPropertiesValidatorTest With Certain Versions of Java
 Key: AMBARI-21126
 URL: https://issues.apache.org/jira/browse/AMBARI-21126
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Reporter: Laszlo Puskas
Assignee: Laszlo Puskas
 Fix For: 3.0.0


Assertions on formatted strings failed due to the ordering of map entries 
merged into the message.

Solution: used ordered maps to make generated strings predictable.



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

[jira] [Updated] (AMBARI-21113) hdfs_user_nofile_limit is not picking as expected for datanode process in a secure cluster

[Dmytro Grinenko (JIRA)]

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

Dmytro Grinenko updated AMBARI-21113:
-
Status: Patch Available  (was: In Progress)

> hdfs_user_nofile_limit is not picking as expected for datanode process in a 
> secure cluster
> --
>
> Key: AMBARI-21113
> URL: https://issues.apache.org/jira/browse/AMBARI-21113
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Critical
> Fix For: trunk, 2.5.2
>
> Attachments: AMBARI-21113-2.5.patch, AMBARI-21113-trunk.patch
>
>
> such code snipped were not added to the hadoop-env after Ambari upgrade
> {code}
> if [ "$command" == "datanode" ] && [ "$EUID" -eq 0 ] && [ -n 
> "$HADOOP_SECURE_DN_USER" ]; then
>   ulimit -n {{hdfs_user_nofile_limit}}
> fi
> {code}



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

[jira] [Updated] (AMBARI-21113) hdfs_user_nofile_limit is not picking as expected for datanode process in a secure cluster

[Dmytro Grinenko (JIRA)]

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

Dmytro Grinenko updated AMBARI-21113:
-
Attachment: AMBARI-21113-trunk.patch
AMBARI-21113-2.5.patch

> hdfs_user_nofile_limit is not picking as expected for datanode process in a 
> secure cluster
> --
>
> Key: AMBARI-21113
> URL: https://issues.apache.org/jira/browse/AMBARI-21113
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Critical
> Fix For: trunk, 2.5.2
>
> Attachments: AMBARI-21113-2.5.patch, AMBARI-21113-trunk.patch
>
>
> such code snipped were not added to the hadoop-env after Ambari upgrade
> {code}
> if [ "$command" == "datanode" ] && [ "$EUID" -eq 0 ] && [ -n 
> "$HADOOP_SECURE_DN_USER" ]; then
>   ulimit -n {{hdfs_user_nofile_limit}}
> fi
> {code}



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

[jira] [Commented] (AMBARI-19149) Clean up Ambari Server source code warnings

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16024436#comment-16024436
 ] 

Hudson commented on AMBARI-19149:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7535 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/7535/])
AMBARI-19149. Code cleanup: identical catch blocks (adoroszlai: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=1adb70d53041e64ac7e844592453cd3085704105])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/IPAKerberosOperationHandler.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/orm/helpers/ScriptRunner.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ServiceComponentHostEventWrapper.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/topology/TopologyManager.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/security/encryption/MasterKeyServiceImpl.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/utils/ShellCommandUtil.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/checks/DatabaseConsistencyCheckHelper.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/StackDependencyResourceProvider.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/topology/ClusterConfigurationRequest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/api/handlers/UpdateHandler.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClientConfigResourceProvider.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/security/encryption/AESEncryptor.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/scheduler/ExecutionScheduleManager.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterStackVersionResourceProvider.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/agent/LocalAgentSimulator.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/api/query/render/ClusterBlueprintRenderer.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/utils/HTTPUtils.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/ADKerberosOperationHandler.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/KerberosOperationHandler.java


> Clean up Ambari Server source code warnings
> ---
>
> Key: AMBARI-19149
> URL: https://issues.apache.org/jira/browse/AMBARI-19149
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0
>
> Attachments: AMBARI-19149-10.patch, AMBARI-19149-11.patch, 
> AMBARI-19149-12.patch, AMBARI-19149-13.patch, AMBARI-19149-1.patch, 
> AMBARI-19149-3.patch, AMBARI-19149-4.patch, AMBARI-19149-5.patch, 
> AMBARI-19149-6.patch, AMBARI-19149-7.patch, AMBARI-19149-9.patch, 
> IDEA_Ambari_v1.xml
>
>
> Eclipse's default warnings generated for {{ambari-server}} number roughly 
> over 3300. Out of these, at least half of them are:
> * Unused imports
> * Type safety due to forgotten {{<>}}
> * Missing Serialization IDs from anonymous {{HashMap}} implementations
> * Unused variables
> * {{Capture}} in tests
> * {{switch}} fall-through and missing {{case statements}}: *only makes 
> changes which won't affect existing functionality*
> This makes spotting actual problems, like missing {{case}} statements a 
> nightmare. We need to go through and clean out as many of these warnings as 
> possible. 
> Note: With respect to the import cleanup, the IDE of choice should have the 
> following import order setup. They should always be expanded and never use 
> {{*}}.
> # {{java}}
> # {{javax}}
> # {{org}}
> # {{com}}
> # other



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

[jira] [Commented] (AMBARI-19149) Clean up Ambari Server source code warnings

[Doroszlai, Attila (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16024394#comment-16024394
 ] 

Doroszlai, Attila commented on AMBARI-19149:


[Failure|https://builds.apache.org/job/Ambari-trunk-Commit/7534/consoleText] is 
unrelated, due to some Python tests that failed in [previous 
runs|https://builds.apache.org/job/Ambari-trunk-Commit/7531/consoleText], too.

> Clean up Ambari Server source code warnings
> ---
>
> Key: AMBARI-19149
> URL: https://issues.apache.org/jira/browse/AMBARI-19149
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0
>
> Attachments: AMBARI-19149-10.patch, AMBARI-19149-11.patch, 
> AMBARI-19149-12.patch, AMBARI-19149-13.patch, AMBARI-19149-1.patch, 
> AMBARI-19149-3.patch, AMBARI-19149-4.patch, AMBARI-19149-5.patch, 
> AMBARI-19149-6.patch, AMBARI-19149-7.patch, AMBARI-19149-9.patch, 
> IDEA_Ambari_v1.xml
>
>
> Eclipse's default warnings generated for {{ambari-server}} number roughly 
> over 3300. Out of these, at least half of them are:
> * Unused imports
> * Type safety due to forgotten {{<>}}
> * Missing Serialization IDs from anonymous {{HashMap}} implementations
> * Unused variables
> * {{Capture}} in tests
> * {{switch}} fall-through and missing {{case statements}}: *only makes 
> changes which won't affect existing functionality*
> This makes spotting actual problems, like missing {{case}} statements a 
> nightmare. We need to go through and clean out as many of these warnings as 
> possible. 
> Note: With respect to the import cleanup, the IDE of choice should have the 
> following import order setup. They should always be expanded and never use 
> {{*}}.
> # {{java}}
> # {{javax}}
> # {{org}}
> # {{com}}
> # other



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

[jira] [Commented] (AMBARI-19149) Clean up Ambari Server source code warnings

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16024385#comment-16024385
 ] 

Hudson commented on AMBARI-19149:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7534 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/7534/])
AMBARI-19149. Code cleanup: dangling Javadoc comment (adoroszlai: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=c2409e740f84d6f051659b3b36d853902e698a60])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertNoticeResourceProvider.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/orm/dao/ConfigGroupHostMappingDAO.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/api/services/TaskAttemptService.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/utilities/ScalingThreadPoolExecutor.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/DirectoriesTrimmingStrategy.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ObservableResourceProvider.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/notifications/dispatchers/EmailDispatcher.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/ViewPrivilegeRequest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ProvisionClusterRequest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/api/services/RepositoryService.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BaseProvider.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/alerts/StaleAlertRunnable.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/api/resources/OperatingSystemResourceDefinition.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/resources/api/rest/GetResource.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ClusterServiceEntityPK.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/api/resources/RootServiceHostComponentResourceDefinition.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/api/services/InstanceService.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/agent/RegistrationStatus.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/serveraction/upgrades/RangerKmsProxyConfig.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/api/services/stackadvisor/StackAdvisorHelper.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/api/query/JpaSortBuilder.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/metrics/system/impl/JvmMetricsSource.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/security/authorization/AmbariGrantedAuthority.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/api/services/QueryPostRequest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/api/handlers/DeleteHandler.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/api/services/stackadvisor/StackAdvisorRequest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/checks/HardcodedStackVersionPropertiesCheck.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/alerts/AgentHeartbeatAlertRunnable.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/api/services/stackadvisor/commands/StackAdvisorCommandType.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/utilities/PredicateHelper.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/RequestScheduleBatchRequestEntityPK.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/AlertHistoryRequest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariCustomCommandExecutionHelper.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/logging/LoggingSearchPropertyProvider.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/api/services/stackadvisor/StackAdvisorResponse.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/orm/dao/ClusterVersionDAO.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/spi/SortRequest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/stack/BaseModule.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/api/query/render/BaseRenderer.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/StackVersionResponse.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/orm/dao/RequestOperationLevelDAO.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/annotations/ExperimentalFeature.java
* (edit) 

[jira] [Updated] (AMBARI-20434) Enhance Kafka Service Check

[WangJie (JIRA)]

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

WangJie updated AMBARI-20434:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Enhance Kafka Service Check
> ---
>
> Key: AMBARI-20434
> URL: https://issues.apache.org/jira/browse/AMBARI-20434
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: WangJie
>Assignee: Dmitry Lysnichenko
> Fix For: trunk
>
> Attachments: AMBARI-20434-1.patch, AMBARI-20434.patch
>
>
> Problem:
> Kafka Service Check  will create the kafka topic only if the topic doesn't 
> exist.
> if it exists, Kafka Service Check will return success directly.
> After topic is being created, we sense that each time running service check 
> will not reflect the kafka actual state correctly
> Suggestion:
> Every running kafka service check, delete the existed topic and recreate it.



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

[jira] [Commented] (AMBARI-21125) Ambari STS2 checker should use principal in secure cluster

[Mingjie Tang (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-21125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16024345#comment-16024345
 ] 

Mingjie Tang commented on AMBARI-21125:
---

review link: https://reviews.apache.org/r/59570/

> Ambari STS2 checker should use principal in secure cluster
> --
>
> Key: AMBARI-21125
> URL: https://issues.apache.org/jira/browse/AMBARI-21125
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.1
>Reporter: Mingjie Tang
>Assignee: Mingjie Tang
>  Labels: spark
> Attachments: BUG-81619.diff
>
>
> In the secure cluster, Ambari STS checker for Spark2 seems to generate 
> misleading error every one minute.
> {code}
> 17/05/24 19:24:35 ERROR TThreadPoolServer: Error occurred during processing 
> of message.
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
> Unsupported mechanism type PLAIN
>  
> 17/05/24 19:25:35 ERROR TThreadPoolServer: Error occurred during processing 
> of message.
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
> Unsupported mechanism type PLAIN
>  
> 17/05/24 19:26:36 ERROR TThreadPoolServer: Error occurred during processing 
> of message.
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
> Unsupported mechanism type PLAIN
>  
> 17/05/24 19:27:35 ERROR TThreadPoolServer: Error occurred during processing 
> of message.
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
> Unsupported mechanism type PLAIN
> {code}



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

[jira] [Updated] (AMBARI-21125) Ambari STS2 checker should use principal in secure cluster

[Mingjie Tang (JIRA)]

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

Mingjie Tang updated AMBARI-21125:
--
Affects Version/s: 2.5.1

> Ambari STS2 checker should use principal in secure cluster
> --
>
> Key: AMBARI-21125
> URL: https://issues.apache.org/jira/browse/AMBARI-21125
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.1
>Reporter: Mingjie Tang
>Assignee: Mingjie Tang
>  Labels: spark
> Attachments: BUG-81619.diff
>
>
> In the secure cluster, Ambari STS checker for Spark2 seems to generate 
> misleading error every one minute.
> {code}
> 17/05/24 19:24:35 ERROR TThreadPoolServer: Error occurred during processing 
> of message.
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
> Unsupported mechanism type PLAIN
>  
> 17/05/24 19:25:35 ERROR TThreadPoolServer: Error occurred during processing 
> of message.
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
> Unsupported mechanism type PLAIN
>  
> 17/05/24 19:26:36 ERROR TThreadPoolServer: Error occurred during processing 
> of message.
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
> Unsupported mechanism type PLAIN
>  
> 17/05/24 19:27:35 ERROR TThreadPoolServer: Error occurred during processing 
> of message.
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
> Unsupported mechanism type PLAIN
> {code}



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

[jira] [Updated] (AMBARI-21125) Ambari STS2 checker should use principal in secure cluster

[Mingjie Tang (JIRA)]

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

Mingjie Tang updated AMBARI-21125:
--
Status: Open  (was: Patch Available)

> Ambari STS2 checker should use principal in secure cluster
> --
>
> Key: AMBARI-21125
> URL: https://issues.apache.org/jira/browse/AMBARI-21125
> Project: Ambari
>  Issue Type: Bug
>Reporter: Mingjie Tang
>Assignee: Mingjie Tang
>  Labels: spark
> Attachments: BUG-81619.diff
>
>
> In the secure cluster, Ambari STS checker for Spark2 seems to generate 
> misleading error every one minute.
> {code}
> 17/05/24 19:24:35 ERROR TThreadPoolServer: Error occurred during processing 
> of message.
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
> Unsupported mechanism type PLAIN
>  
> 17/05/24 19:25:35 ERROR TThreadPoolServer: Error occurred during processing 
> of message.
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
> Unsupported mechanism type PLAIN
>  
> 17/05/24 19:26:36 ERROR TThreadPoolServer: Error occurred during processing 
> of message.
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
> Unsupported mechanism type PLAIN
>  
> 17/05/24 19:27:35 ERROR TThreadPoolServer: Error occurred during processing 
> of message.
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
> Unsupported mechanism type PLAIN
> {code}



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

[jira] [Updated] (AMBARI-21125) Ambari STS2 checker should use principal in secure cluster

[Mingjie Tang (JIRA)]

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

Mingjie Tang updated AMBARI-21125:
--
Attachment: BUG-81619.diff

> Ambari STS2 checker should use principal in secure cluster
> --
>
> Key: AMBARI-21125
> URL: https://issues.apache.org/jira/browse/AMBARI-21125
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.1
>Reporter: Mingjie Tang
>Assignee: Mingjie Tang
>  Labels: spark
> Attachments: BUG-81619.diff
>
>
> In the secure cluster, Ambari STS checker for Spark2 seems to generate 
> misleading error every one minute.
> {code}
> 17/05/24 19:24:35 ERROR TThreadPoolServer: Error occurred during processing 
> of message.
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
> Unsupported mechanism type PLAIN
>  
> 17/05/24 19:25:35 ERROR TThreadPoolServer: Error occurred during processing 
> of message.
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
> Unsupported mechanism type PLAIN
>  
> 17/05/24 19:26:36 ERROR TThreadPoolServer: Error occurred during processing 
> of message.
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
> Unsupported mechanism type PLAIN
>  
> 17/05/24 19:27:35 ERROR TThreadPoolServer: Error occurred during processing 
> of message.
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
> Unsupported mechanism type PLAIN
> {code}



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

[jira] [Updated] (AMBARI-21125) Ambari STS2 checker should use principal in secure cluster

[Mingjie Tang (JIRA)]

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

Mingjie Tang updated AMBARI-21125:
--
Labels: spark  (was: )

> Ambari STS2 checker should use principal in secure cluster
> --
>
> Key: AMBARI-21125
> URL: https://issues.apache.org/jira/browse/AMBARI-21125
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.1
>Reporter: Mingjie Tang
>Assignee: Mingjie Tang
>  Labels: spark
> Attachments: BUG-81619.diff
>
>
> In the secure cluster, Ambari STS checker for Spark2 seems to generate 
> misleading error every one minute.
> {code}
> 17/05/24 19:24:35 ERROR TThreadPoolServer: Error occurred during processing 
> of message.
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
> Unsupported mechanism type PLAIN
>  
> 17/05/24 19:25:35 ERROR TThreadPoolServer: Error occurred during processing 
> of message.
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
> Unsupported mechanism type PLAIN
>  
> 17/05/24 19:26:36 ERROR TThreadPoolServer: Error occurred during processing 
> of message.
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
> Unsupported mechanism type PLAIN
>  
> 17/05/24 19:27:35 ERROR TThreadPoolServer: Error occurred during processing 
> of message.
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
> Unsupported mechanism type PLAIN
> {code}



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

[jira] [Created] (AMBARI-21125) Ambari STS2 checker should use principal in secure cluster

[Mingjie Tang (JIRA)]

Mingjie Tang created AMBARI-21125:
-

 Summary: Ambari STS2 checker should use principal in secure cluster
 Key: AMBARI-21125
 URL: https://issues.apache.org/jira/browse/AMBARI-21125
 Project: Ambari
  Issue Type: Bug
Reporter: Mingjie Tang


In the secure cluster, Ambari STS checker for Spark2 seems to generate 
misleading error every one minute.

{code}
17/05/24 19:24:35 ERROR TThreadPoolServer: Error occurred during processing of 
message.
java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
Unsupported mechanism type PLAIN
 
17/05/24 19:25:35 ERROR TThreadPoolServer: Error occurred during processing of 
message.
java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
Unsupported mechanism type PLAIN
 
17/05/24 19:26:36 ERROR TThreadPoolServer: Error occurred during processing of 
message.
java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
Unsupported mechanism type PLAIN
 
17/05/24 19:27:35 ERROR TThreadPoolServer: Error occurred during processing of 
message.
java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
Unsupported mechanism type PLAIN
{code}



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

[jira] [Updated] (AMBARI-21125) Ambari STS2 checker should use principal in secure cluster

[Mingjie Tang (JIRA)]

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

Mingjie Tang updated AMBARI-21125:
--
Assignee: Mingjie Tang
  Status: Patch Available  (was: Open)

> Ambari STS2 checker should use principal in secure cluster
> --
>
> Key: AMBARI-21125
> URL: https://issues.apache.org/jira/browse/AMBARI-21125
> Project: Ambari
>  Issue Type: Bug
>Reporter: Mingjie Tang
>Assignee: Mingjie Tang
>
> In the secure cluster, Ambari STS checker for Spark2 seems to generate 
> misleading error every one minute.
> {code}
> 17/05/24 19:24:35 ERROR TThreadPoolServer: Error occurred during processing 
> of message.
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
> Unsupported mechanism type PLAIN
>  
> 17/05/24 19:25:35 ERROR TThreadPoolServer: Error occurred during processing 
> of message.
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
> Unsupported mechanism type PLAIN
>  
> 17/05/24 19:26:36 ERROR TThreadPoolServer: Error occurred during processing 
> of message.
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
> Unsupported mechanism type PLAIN
>  
> 17/05/24 19:27:35 ERROR TThreadPoolServer: Error occurred during processing 
> of message.
> java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: 
> Unsupported mechanism type PLAIN
> {code}



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

[jira] [Updated] (AMBARI-21123) Part Two: Specify the script directly in alert target for script-based alert dispatchers

[Yao Lei (JIRA)]

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

Yao Lei updated AMBARI-21123:
-
Description: 
Web Codes Part

This patch amis to support creating alert target  that inclueds property 
*ambari.dispatch-property.script.filename*  on web UI

  was:Web Codes Part


> Part Two: Specify the script directly in alert target for script-based alert 
> dispatchers
> 
>
> Key: AMBARI-21123
> URL: https://issues.apache.org/jira/browse/AMBARI-21123
> Project: Ambari
>  Issue Type: Technical task
>  Components: alerts, ambari-web
>Reporter: Yao Lei
>Assignee: Yao Lei
> Fix For: 3.0.0
>
> Attachments: AMBARI-21123.patch, script_alert_notification_1.png, 
> script_alert_notification_2.png
>
>
> Web Codes Part
> This patch amis to support creating alert target  that inclueds property 
> *ambari.dispatch-property.script.filename*  on web UI



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

[jira] [Updated] (AMBARI-21122) Part One: Specify the script directly in alert target for script-based alert dispatchers

[Yao Lei (JIRA)]

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

Yao Lei updated AMBARI-21122:
-
Description: 
*Jave Codes Part*

This patch will support using property  
*ambari.dispatch-property.script.filename* in alert target  to tell 
AlertScriptDispatcher to lookup script by filename,default in 
/var/lib/ambari-server/resources/scripts directory. We can also change this  
directory in ambari.properties by ambari.dispatch-property.script.directory 
property.

Execute a command manually like following to create an alert target that 
includes this property:
{code}
POST api/v1/alert_targets
{
  "AlertTarget": {
"name": "syslogger",
"description": "Syslog Target",
"notification_type": "ALERT_SCRIPT",
"global": false,
"groups":[1,3]
"alert_states":["WARNING","CRITICAL","UNKNOWN"],
"properties": {
   "ambari.dispatch-property.script.filename": "foo.py"
}
  }
}
{code}



  was:
*Jave Codes Part*

This patch will support using property  
*ambari.dispatch-property.script.filename* in alert target  to tell 
AlertScriptDispatcher to lookup script by filename,default in 
/var/lib/ambari-server/resources/scripts directory. We can also change this  
directory in ambari.properties by ambari.dispatch-property.script.directory 
property.

Execute a command manually like following to create an alert target:
{code}
POST api/v1/alert_targets
{
  "AlertTarget": {
"name": "syslogger",
"description": "Syslog Target",
"notification_type": "ALERT_SCRIPT",
"global": false,
"groups":[1,3]
"alert_states":["WARNING","CRITICAL","UNKNOWN"],
"properties": {
   "ambari.dispatch-property.script.filename": "foo.py"
}
  }
}
{code}




> Part One:  Specify the script directly in alert target for script-based alert 
> dispatchers
> -
>
> Key: AMBARI-21122
> URL: https://issues.apache.org/jira/browse/AMBARI-21122
> Project: Ambari
>  Issue Type: Technical task
>Reporter: Yao Lei
>Assignee: Yao Lei
> Fix For: 3.0.0
>
> Attachments: AMBARI-21122.patch
>
>
> *Jave Codes Part*
> This patch will support using property  
> *ambari.dispatch-property.script.filename* in alert target  to tell 
> AlertScriptDispatcher to lookup script by filename,default in 
> /var/lib/ambari-server/resources/scripts directory. We can also change this  
> directory in ambari.properties by ambari.dispatch-property.script.directory 
> property.
> Execute a command manually like following to create an alert target that 
> includes this property:
> {code}
> POST api/v1/alert_targets
> {
>   "AlertTarget": {
> "name": "syslogger",
> "description": "Syslog Target",
> "notification_type": "ALERT_SCRIPT",
> "global": false,
> "groups":[1,3]
> "alert_states":["WARNING","CRITICAL","UNKNOWN"],
> "properties": {
>"ambari.dispatch-property.script.filename": "foo.py"
> }
>   }
> }
> {code}



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

[jira] [Updated] (AMBARI-21122) Part One: Specify the script directly in alert target for script-based alert dispatchers

[Yao Lei (JIRA)]

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

Yao Lei updated AMBARI-21122:
-
Description: 
*Jave Codes Part*

This patch will support using property  
*ambari.dispatch-property.script.filename* in alert target  to tell 
AlertScriptDispatcher to lookup script by filename,default in 
/var/lib/ambari-server/resources/scripts directory. We can also change this  
directory in ambari.properties by *ambari.dispatch-property.script.directory* 
property.

Execute a command manually like following to create an alert target that 
includes this property:
{code}
POST api/v1/alert_targets
{
  "AlertTarget": {
"name": "syslogger",
"description": "Syslog Target",
"notification_type": "ALERT_SCRIPT",
"global": false,
"groups":[1,3]
"alert_states":["WARNING","CRITICAL","UNKNOWN"],
"properties": {
   "ambari.dispatch-property.script.filename": "foo.py"
}
  }
}
{code}



  was:
*Jave Codes Part*

This patch will support using property  
*ambari.dispatch-property.script.filename* in alert target  to tell 
AlertScriptDispatcher to lookup script by filename,default in 
/var/lib/ambari-server/resources/scripts directory. We can also change this  
directory in ambari.properties by ambari.dispatch-property.script.directory 
property.

Execute a command manually like following to create an alert target that 
includes this property:
{code}
POST api/v1/alert_targets
{
  "AlertTarget": {
"name": "syslogger",
"description": "Syslog Target",
"notification_type": "ALERT_SCRIPT",
"global": false,
"groups":[1,3]
"alert_states":["WARNING","CRITICAL","UNKNOWN"],
"properties": {
   "ambari.dispatch-property.script.filename": "foo.py"
}
  }
}
{code}




> Part One:  Specify the script directly in alert target for script-based alert 
> dispatchers
> -
>
> Key: AMBARI-21122
> URL: https://issues.apache.org/jira/browse/AMBARI-21122
> Project: Ambari
>  Issue Type: Technical task
>Reporter: Yao Lei
>Assignee: Yao Lei
> Fix For: 3.0.0
>
> Attachments: AMBARI-21122.patch
>
>
> *Jave Codes Part*
> This patch will support using property  
> *ambari.dispatch-property.script.filename* in alert target  to tell 
> AlertScriptDispatcher to lookup script by filename,default in 
> /var/lib/ambari-server/resources/scripts directory. We can also change this  
> directory in ambari.properties by *ambari.dispatch-property.script.directory* 
> property.
> Execute a command manually like following to create an alert target that 
> includes this property:
> {code}
> POST api/v1/alert_targets
> {
>   "AlertTarget": {
> "name": "syslogger",
> "description": "Syslog Target",
> "notification_type": "ALERT_SCRIPT",
> "global": false,
> "groups":[1,3]
> "alert_states":["WARNING","CRITICAL","UNKNOWN"],
> "properties": {
>"ambari.dispatch-property.script.filename": "foo.py"
> }
>   }
> }
> {code}



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

[jira] [Updated] (AMBARI-21122) Part One: Specify the script directly in alert target for script-based alert dispatchers

[Yao Lei (JIRA)]

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

Yao Lei updated AMBARI-21122:
-
Description: 
*Jave Codes Part*

This patch will support using property  
*ambari.dispatch-property.script.filename* in alert target  to tell 
AlertScriptDispatcher to lookup script by filename,default in 
/var/lib/ambari-server/resources/scripts directory. We can also change this  
directory in ambari.properties by ambari.dispatch-property.script.directory 
property.

Execute a command manually like following to create an alert target:
{code}
POST api/v1/alert_targets
{
  "AlertTarget": {
"name": "syslogger",
"description": "Syslog Target",
"notification_type": "ALERT_SCRIPT",
"global": false,
"groups":[1,3]
"alert_states":["WARNING","CRITICAL","UNKNOWN"],
"properties": {
   "ambari.dispatch-property.script.filename": "foo.py"
}
  }
}
{code}



  was:
*Jave Codes Part*

Now we can use property *ambari.dispatch-property.script.filename* in alert 
target  to tell AlertScriptDispatcher to lookup script by filename,default in 
/var/lib/ambari-server/resources/scripts directory. We can also change this  
directory in ambari.properties by ambari.dispatch-property.script.directory 
property.

Execute a command manually like following to create an alert target:
{code}
POST api/v1/alert_targets
{
  "AlertTarget": {
"name": "syslogger",
"description": "Syslog Target",
"notification_type": "ALERT_SCRIPT",
"global": false,
"groups":[1,3]
"alert_states":["WARNING","CRITICAL","UNKNOWN"],
"properties": {
   "ambari.dispatch-property.script.filename": "foo.py"
}
  }
}
{code}




> Part One:  Specify the script directly in alert target for script-based alert 
> dispatchers
> -
>
> Key: AMBARI-21122
> URL: https://issues.apache.org/jira/browse/AMBARI-21122
> Project: Ambari
>  Issue Type: Technical task
>Reporter: Yao Lei
>Assignee: Yao Lei
> Fix For: 3.0.0
>
> Attachments: AMBARI-21122.patch
>
>
> *Jave Codes Part*
> This patch will support using property  
> *ambari.dispatch-property.script.filename* in alert target  to tell 
> AlertScriptDispatcher to lookup script by filename,default in 
> /var/lib/ambari-server/resources/scripts directory. We can also change this  
> directory in ambari.properties by ambari.dispatch-property.script.directory 
> property.
> Execute a command manually like following to create an alert target:
> {code}
> POST api/v1/alert_targets
> {
>   "AlertTarget": {
> "name": "syslogger",
> "description": "Syslog Target",
> "notification_type": "ALERT_SCRIPT",
> "global": false,
> "groups":[1,3]
> "alert_states":["WARNING","CRITICAL","UNKNOWN"],
> "properties": {
>"ambari.dispatch-property.script.filename": "foo.py"
> }
>   }
> }
> {code}



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

[jira] [Updated] (AMBARI-21122) Part One: Specify the script directly in alert target for script-based alert dispatchers

[Yao Lei (JIRA)]

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

Yao Lei updated AMBARI-21122:
-
Status: Patch Available  (was: Open)

> Part One:  Specify the script directly in alert target for script-based alert 
> dispatchers
> -
>
> Key: AMBARI-21122
> URL: https://issues.apache.org/jira/browse/AMBARI-21122
> Project: Ambari
>  Issue Type: Technical task
>Reporter: Yao Lei
>Assignee: Yao Lei
> Fix For: 3.0.0
>
> Attachments: AMBARI-21122.patch
>
>
> *Jave Codes Part*
> Now we can use property *ambari.dispatch-property.script.filename* in alert 
> target  to tell AlertScriptDispatcher to lookup script by filename,default in 
> /var/lib/ambari-server/resources/scripts directory. We can also change this  
> directory in ambari.properties by ambari.dispatch-property.script.directory 
> property.
> Execute a command manually like following to create an alert target:
> {code}
> POST api/v1/alert_targets
> {
>   "AlertTarget": {
> "name": "syslogger",
> "description": "Syslog Target",
> "notification_type": "ALERT_SCRIPT",
> "global": false,
> "groups":[1,3]
> "alert_states":["WARNING","CRITICAL","UNKNOWN"],
> "properties": {
>"ambari.dispatch-property.script.filename": "foo.py"
> }
>   }
> }
> {code}



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