[jira] [Updated] (AMBARI-19206) When Namenode HA is enabled, hbase.rootdir property for ambari-metrics (distributed) does not get updated

[Sangeeta Ravindran (JIRA)]

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

Sangeeta Ravindran updated AMBARI-19206:

Fix Version/s: 2.5.0
   Status: Patch Available  (was: In Progress)

> When Namenode HA is enabled, hbase.rootdir property for ambari-metrics 
> (distributed) does not get updated
> -
>
> Key: AMBARI-19206
> URL: https://issues.apache.org/jira/browse/AMBARI-19206
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0, 2.4.2
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
> Fix For: 2.5.0
>
> Attachments: AMBARI-19206.patch, AMSHbaseRootdirPostNNHAEnabling.jpg, 
> NNHAWizard1.jpg, NNHAWizard2.jpg
>
>
> On a cluster with ambari-metrics in distributed operation mode, enable 
> Namenode HA.
> After HA wizard is run, the amabri-metrics property for hbase.rootdir should 
> point to hdfs://, but it actually still points to the 
> explicit Namenode.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18263) Agent connection retry fails after one try

[Doroszlai, Attila (JIRA)]

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

Doroszlai, Attila updated AMBARI-18263:
---
Component/s: (was: ambari-server)
 ambari-agent

> Agent connection retry fails after one try
> --
>
> Key: AMBARI-18263
> URL: https://issues.apache.org/jira/browse/AMBARI-18263
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: 2.2.1
>Reporter: Sandor Magyari
>Assignee: Sandor Magyari
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-18263.patch
>
>
> Currently agent connection retry mechanism fails after one try:
> {code}
> WARNING 2016-08-12 16:13:08,291 main.py:351 - Unable to determine the IP 
> address of the Ambari server 'ambari-server'
> ERROR 2016-08-12 16:13:08,292 main.py:392 - Exiting with exception:
> Traceback (most recent call last):
>   File "/usr/lib/python2.6/site-packages/ambari_agent/main.py", line 387, in 
> 
> main(heartbeat_stop_callback)
>   File "/usr/lib/python2.6/site-packages/ambari_agent/main.py", line 355, in 
> main
> (retries, connected, stopped) = netutil.try_to_connect(server_url, 
> MAX_RETRIES, logger)
> UnboundLocalError: local variable 'server_url' referenced before assignment
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19248) Add Livy to HDP 2.6 as slave component of Spark2

[mingjie tang (JIRA)]

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

mingjie tang updated AMBARI-19248:
--
Summary: Add Livy to HDP 2.6 as slave component of Spark2  (was: Add Livy 
to HDP 2.6 as slave component of Spark)

> Add Livy to HDP 2.6 as slave component of Spark2
> 
>
> Key: AMBARI-19248
> URL: https://issues.apache.org/jira/browse/AMBARI-19248
> Project: Ambari
>  Issue Type: New Feature
>Reporter: mingjie tang
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-19248) Add Livy to HDP 2.6 as slave component of Spark

[mingjie tang (JIRA)]

mingjie tang created AMBARI-19248:
-

 Summary: Add Livy to HDP 2.6 as slave component of Spark
 Key: AMBARI-19248
 URL: https://issues.apache.org/jira/browse/AMBARI-19248
 Project: Ambari
  Issue Type: New Feature
Reporter: mingjie tang






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19247) Add log to stack_select for details on which role to get version info

[Di Li (JIRA)]

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

Di Li updated AMBARI-19247:
---
Attachment: AMBARI-19247.patch

> Add log to stack_select for details on which role to get version info
> -
>
> Key: AMBARI-19247
> URL: https://issues.apache.org/jira/browse/AMBARI-19247
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-19247.patch
>
>
> there is currently no log indicating mismatched roles and the corresponding 
> behavior on skipping checking role (component) versions when the service 
> status map or service check map does not have the role.
> there should be minimal logging to be included in output-[taskid].out



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19247) Add log to stack_select for details on which role to get version info

[Di Li (JIRA)]

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

Di Li updated AMBARI-19247:
---
Fix Version/s: trunk
   Status: Patch Available  (was: Open)

> Add log to stack_select for details on which role to get version info
> -
>
> Key: AMBARI-19247
> URL: https://issues.apache.org/jira/browse/AMBARI-19247
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-19247.patch
>
>
> there is currently no log indicating mismatched roles and the corresponding 
> behavior on skipping checking role (component) versions when the service 
> status map or service check map does not have the role.
> there should be minimal logging to be included in output-[taskid].out



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-19247) Add log to stack_select for details on which role to get version info

[Di Li (JIRA)]

Di Li created AMBARI-19247:
--

 Summary: Add log to stack_select for details on which role to get 
version info
 Key: AMBARI-19247
 URL: https://issues.apache.org/jira/browse/AMBARI-19247
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: trunk
Reporter: Di Li
Assignee: Di Li
Priority: Minor


there is currently no log indicating mismatched roles and the corresponding 
behavior on skipping checking role (component) versions when the service status 
map or service check map does not have the role.

there should be minimal logging to be included in output-[taskid].out



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18952) Register BackupObserver and BackupHFileCleaner

[Ted Yu (JIRA)]

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

Ted Yu updated AMBARI-18952:

Description: 
Over in HBASE-14417, two new classes are added.

BackupHFileCleaner should be registered through 
hbase.master.hfilecleaner.plugins . It is responsible for keeping bulk loaded 
hfiles so that incremental backup can pick them up.


BackupObserver should be registered through hbase.coprocessor.region.classes
It is notified when bulk load completes and writes records into hbase:backup 
table.

  was:
Over in HBASE-14417, two new classes are added.

BackupHFileCleaner should be registered through 
hbase.master.hfilecleaner.plugins . It is responsible for keeping bulk loaded 
hfiles so that incremental backup can pick them up.

BackupObserver should be registered through hbase.coprocessor.region.classes
It is notified when bulk load completes and writes records into hbase:backup 
table.


> Register BackupObserver and BackupHFileCleaner
> --
>
> Key: AMBARI-18952
> URL: https://issues.apache.org/jira/browse/AMBARI-18952
> Project: Ambari
>  Issue Type: Improvement
>Reporter: Ted Yu
>
> Over in HBASE-14417, two new classes are added.
> BackupHFileCleaner should be registered through 
> hbase.master.hfilecleaner.plugins . It is responsible for keeping bulk loaded 
> hfiles so that incremental backup can pick them up.
> BackupObserver should be registered through hbase.coprocessor.region.classes
> It is notified when bulk load completes and writes records into hbase:backup 
> table.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19096) HDP 3.0 TP - create Service Advisor for ZK

[Alejandro Fernandez (JIRA)]

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

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

> HDP 3.0 TP - create Service Advisor for ZK
> --
>
> Key: AMBARI-19096
> URL: https://issues.apache.org/jira/browse/AMBARI-19096
> Project: Ambari
>  Issue Type: Story
>  Components: stacks
>Affects Versions: 3.0.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 3.0.0
>
> Attachments: AMBARI-19096.preview.patch
>
>
> Create a Service Advisor script for ZK in HDP 3.0 Tech Preview.
> The Service Advisor must encapsulate all of the logic inherited/overwritten 
> from HDP 2.0.6 through HDP 2.6



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19096) HDP 3.0 TP - create Service Advisor for ZK

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-19096:
-
Attachment: AMBARI-19096.preview.patch

> HDP 3.0 TP - create Service Advisor for ZK
> --
>
> Key: AMBARI-19096
> URL: https://issues.apache.org/jira/browse/AMBARI-19096
> Project: Ambari
>  Issue Type: Story
>  Components: stacks
>Affects Versions: 3.0.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 3.0.0
>
> Attachments: AMBARI-19096.preview.patch
>
>
> Create a Service Advisor script for ZK in HDP 3.0 Tech Preview.
> The Service Advisor must encapsulate all of the logic inherited/overwritten 
> from HDP 2.0.6 through HDP 2.6



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-19246) Ambari Agent start fails with local variable 'server_url' referenced before assignment

[Alejandro Fernandez (JIRA)]

Alejandro Fernandez created AMBARI-19246:


 Summary: Ambari Agent start fails with local variable 'server_url' 
referenced before assignment
 Key: AMBARI-19246
 URL: https://issues.apache.org/jira/browse/AMBARI-19246
 Project: Ambari
  Issue Type: Bug
  Components: ambari-agent
Affects Versions: 2.5.0
Reporter: Alejandro Fernandez
 Fix For: 2.5.0


ambari-server-2.5.0.0-496.x86_64

When starting Ambari Agent, getting this error.
The server host is accessible.

{code}
[root@c6405 ~]# ambari-agent start
Verifying Python version compatibility...
Using python  /usr/bin/python
Checking for previously running Ambari Agent...
Starting ambari-agent
Verifying ambari-agent process status...
ERROR: ambari-agent start failed. For more details, see 
/var/log/ambari-agent/ambari-agent.out:

Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/ambari_agent/main.py", line 407, in 

main(heartbeat_stop_callback)
  File "/usr/lib/python2.6/site-packages/ambari_agent/main.py", line 375, in 
main
(retries, connected, stopped) = netutil.try_to_connect(server_url, 
MAX_RETRIES, logger)
UnboundLocalError: local variable 'server_url' referenced before assignment

Agent out at: /var/log/ambari-agent/ambari-agent.out
Agent log at: /var/log/ambari-agent/ambari-agent.log
{code}

ambari-agent.log:
{code}
INFO 2016-12-19 23:53:42,640 PingPortListener.py:50 - Ping port listener 
started on port: 8670
WARNING 2016-12-19 23:53:42,761 main.py:371 - Unable to determine the IP 
address of the Ambari server 'c6404.ambari.apache.org'
ERROR 2016-12-19 23:53:42,762 main.py:412 - Exiting with exception:
Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/ambari_agent/main.py", line 407, in 

main(heartbeat_stop_callback)
  File "/usr/lib/python2.6/site-packages/ambari_agent/main.py", line 375, in 
main
(retries, connected, stopped) = netutil.try_to_connect(server_url, 
MAX_RETRIES, logger)
UnboundLocalError: local variable 'server_url' referenced before assignment
INFO 2016-12-19 23:53:42,762 ExitHelper.py:53 - Performing cleanup before 
exiting...
{code}

cc [~aonishuk]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-19245) Smartsense Install fails while installing cluster with Blueprint with Customized Service Users

[Vivek Rathod (JIRA)]

Vivek Rathod created AMBARI-19245:
-

 Summary: Smartsense Install fails while installing cluster with 
Blueprint with Customized Service Users
 Key: AMBARI-19245
 URL: https://issues.apache.org/jira/browse/AMBARI-19245
 Project: Ambari
  Issue Type: Bug
Affects Versions: 2.5.0
Reporter: Vivek Rathod
 Fix For: 2.5.0


Smartsense Install fails while installing cluster with Blueprint with 
Customized Service User
{code}
Execution of 'useradd -m -G cstm-hdfs -g hadoop activity_analyzer' returned 6. 
useradd: group 'cstm-hdfs' does not exist
{code}

{code}
Traceback (most recent call last):
  File 
"/var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_agent.py",
 line 22, in 
HSTScript('agent').execute()
  File 
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
 line 282, in execute
method(env)
  File 
"/var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_script.py",
 line 48, in install
self.deploy_component_specific_config(env)
  File 
"/var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_script.py",
 line 360, in deploy_component_specific_config
self.create_activity_user()
  File 
"/var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_script.py",
 line 516, in create_activity_user
groups = params.config['configurations']['hadoop-env']['hdfs_user']
  File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", 
line 155, in __init__
self.env.run()
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
line 160, in run
self.run_action(resource, action)
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
line 124, in run_action
provider_action()
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/providers/accounts.py",
 line 82, in action_create
shell.checked_call(command, sudo=True)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
line 72, in inner
result = function(command, **kwargs)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
line 102, in checked_call
tries=tries, try_sleep=try_sleep, 
timeout_kill_strategy=timeout_kill_strategy)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
line 150, in _call_wrapper
result = _call(command, **kwargs_copy)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
line 303, in _call
raise ExecutionFailed(err_msg, code, out, err)
resource_management.core.exceptions.ExecutionFailed: Execution of 'useradd -m 
-G cstm-hdfs -g hadoop activity_analyzer' returned 6. useradd: group 
'cstm-hdfs' does not exist
Traceback (most recent call last):
  File 
"/var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_agent.py",
 line 22, in 
HSTScript('agent').execute()
  File 
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
 line 282, in execute
method(env)
  File 
"/var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_script.py",
 line 48, in install
self.deploy_component_specific_config(env)
  File 
"/var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_script.py",
 line 360, in deploy_component_specific_config
self.create_activity_user()
  File 
"/var/lib/ambari-agent/cache/stacks/HDP/2.1/services/SMARTSENSE/package/scripts/hst_script.py",
 line 516, in create_activity_user
groups = params.config['configurations']['hadoop-env']['hdfs_user']
  File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", 
line 155, in __init__
self.env.run()
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
line 160, in run
self.run_action(resource, action)
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
line 124, in run_action
provider_action()
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/providers/accounts.py",
 line 82, in action_create
shell.checked_call(command, sudo=True)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
line 72, in inner
result = function(command, **kwargs)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
line 102, in checked_call
tries=tries, try_sleep=try_sleep, 
timeout_kill_strategy=timeout_kill_strategy)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
line 150, in _call_wrapper
result = _call(command, **kwargs_copy)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
line 303, in _call
raise ExecutionFailed(err_msg, code, out, err)

[jira] [Created] (AMBARI-19244) Create profile evaluator

[JIRA]

Balázs Bence Sári created AMBARI-19244:
--

 Summary: Create profile evaluator
 Key: AMBARI-19244
 URL: https://issues.apache.org/jira/browse/AMBARI-19244
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.5.0
Reporter: Balázs Bence Sári
Assignee: Balázs Bence Sári
 Fix For: trunk, 2.5.0


The profile evaluator should interpret the quick links profile and decide on 
the visibility of each quick link.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19243) Metric monitor start command failed though the process started successfully.

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19243:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #557 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/557/])
AMBARI-19243 : Metric monitor start command failed though the process 
(avijayan: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=eaa57846aa22b2a69073d6be69269bc0b1a77493])
* (edit) 
ambari-metrics/ambari-metrics-host-monitoring/src/main/python/core/host_info.py
* (edit) 
ambari-metrics/ambari-metrics-host-monitoring/conf/unix/ambari-metrics-monitor


> Metric monitor start command failed though the process started successfully.
> 
>
> Key: AMBARI-19243
> URL: https://issues.apache.org/jira/browse/AMBARI-19243
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19243.patch
>
>
> {code}
> psutil build directory is not empty, continuing...
> Verifying Python version compatibility...
> Using python  /usr/bin/python2.7
> Checking for previously running Metric Monitor...
> Starting ambari-metrics-monitor
> Verifying ambari-metrics-monitor process status...
> ERROR: ambari-metrics-monitor start failed. For more details, see 
> /grid/0/log/metric_monitor/ambari-metrics-monitor.out:
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19243) Metric monitor start command failed though the process started successfully.

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19243:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6261 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6261/])
AMBARI-19243 : Metric monitor start command failed though the process 
(avijayan: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=6da5935bdffee119909741637f8404f7f807f7ec])
* (edit) 
ambari-metrics/ambari-metrics-host-monitoring/conf/unix/ambari-metrics-monitor
* (edit) 
ambari-metrics/ambari-metrics-host-monitoring/src/main/python/core/host_info.py


> Metric monitor start command failed though the process started successfully.
> 
>
> Key: AMBARI-19243
> URL: https://issues.apache.org/jira/browse/AMBARI-19243
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19243.patch
>
>
> {code}
> psutil build directory is not empty, continuing...
> Verifying Python version compatibility...
> Using python  /usr/bin/python2.7
> Checking for previously running Metric Monitor...
> Starting ambari-metrics-monitor
> Verifying ambari-metrics-monitor process status...
> ERROR: ambari-metrics-monitor start failed. For more details, see 
> /grid/0/log/metric_monitor/ambari-metrics-monitor.out:
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19239) Logs modal window in Host Details> Logs Tab not displayed properly with hidden modal-footer

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19239:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #556 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/556/])
AMBARI-19239. Logs modal window in Host Details> Logs Tab not displayed 
(hiveww: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=9b8a17bd2b442878523816eb0cecd81b34b72d55])
* (edit) ambari-web/app/styles/application.less


> Logs modal window in Host Details> Logs Tab not displayed properly with 
> hidden modal-footer
> ---
>
> Key: AMBARI-19239
> URL: https://issues.apache.org/jira/browse/AMBARI-19239
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19239.patch
>
>
> Logs modal window in Host Details> Logs Tab not displayed properly with 
> hidden modal-footer.
> Chrome Version : 55.0



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19241) Ambari python scripts should support hdfs download

[Tim Thorpe (JIRA)]

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

Tim Thorpe updated AMBARI-19241:

Attachment: AMBARI-19241.patch

> Ambari python scripts should support hdfs download
> --
>
> Key: AMBARI-19241
> URL: https://issues.apache.org/jira/browse/AMBARI-19241
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-agent, contrib
>Affects Versions: trunk, 2.5.0
>Reporter: Tim Thorpe
>Assignee: Tim Thorpe
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19241.patch
>
>   Original Estimate: 192h
>  Remaining Estimate: 192h
>
> Currently the hdfs_resources.py supports 
> 1) create files/directories in HDFS
> 2) delete files/directories in HDFS
> 3) upload files/directories to HDFS
> We should also support download of files/directories from HDFS.  This will 
> help particularly in cloud environments where the users of the cluster don't 
> necessarily have write access to the local file system.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19241) Ambari python scripts should support hdfs download

[Tim Thorpe (JIRA)]

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

Tim Thorpe updated AMBARI-19241:

Status: Patch Available  (was: Open)

> Ambari python scripts should support hdfs download
> --
>
> Key: AMBARI-19241
> URL: https://issues.apache.org/jira/browse/AMBARI-19241
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-agent, contrib
>Affects Versions: trunk, 2.5.0
>Reporter: Tim Thorpe
>Assignee: Tim Thorpe
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19241.patch
>
>   Original Estimate: 192h
>  Remaining Estimate: 192h
>
> Currently the hdfs_resources.py supports 
> 1) create files/directories in HDFS
> 2) delete files/directories in HDFS
> 3) upload files/directories to HDFS
> We should also support download of files/directories from HDFS.  This will 
> help particularly in cloud environments where the users of the cluster don't 
> necessarily have write access to the local file system.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19243) Metric monitor start command failed though the process started successfully.

[Aravindan Vijayan (JIRA)]

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

Aravindan Vijayan updated AMBARI-19243:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Pushed to branch-2.5 and trunk.

> Metric monitor start command failed though the process started successfully.
> 
>
> Key: AMBARI-19243
> URL: https://issues.apache.org/jira/browse/AMBARI-19243
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19243.patch
>
>
> {code}
> psutil build directory is not empty, continuing...
> Verifying Python version compatibility...
> Using python  /usr/bin/python2.7
> Checking for previously running Metric Monitor...
> Starting ambari-metrics-monitor
> Verifying ambari-metrics-monitor process status...
> ERROR: ambari-metrics-monitor start failed. For more details, see 
> /grid/0/log/metric_monitor/ambari-metrics-monitor.out:
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19243) Metric monitor start command failed though the process started successfully.

[Siddharth Wagle (JIRA)]

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

Siddharth Wagle commented on AMBARI-19243:
--

+1

> Metric monitor start command failed though the process started successfully.
> 
>
> Key: AMBARI-19243
> URL: https://issues.apache.org/jira/browse/AMBARI-19243
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19243.patch
>
>
> {code}
> psutil build directory is not empty, continuing...
> Verifying Python version compatibility...
> Using python  /usr/bin/python2.7
> Checking for previously running Metric Monitor...
> Starting ambari-metrics-monitor
> Verifying ambari-metrics-monitor process status...
> ERROR: ambari-metrics-monitor start failed. For more details, see 
> /grid/0/log/metric_monitor/ambari-metrics-monitor.out:
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19243) Metric monitor start command failed though the process started successfully.

[Aravindan Vijayan (JIRA)]

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

Aravindan Vijayan updated AMBARI-19243:
---
Description: 
{code}
psutil build directory is not empty, continuing...
Verifying Python version compatibility...
Using python  /usr/bin/python2.7
Checking for previously running Metric Monitor...
Starting ambari-metrics-monitor
Verifying ambari-metrics-monitor process status...
ERROR: ambari-metrics-monitor start failed. For more details, see 
/grid/0/log/metric_monitor/ambari-metrics-monitor.out:

{code}

> Metric monitor start command failed though the process started successfully.
> 
>
> Key: AMBARI-19243
> URL: https://issues.apache.org/jira/browse/AMBARI-19243
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19243.patch
>
>
> {code}
> psutil build directory is not empty, continuing...
> Verifying Python version compatibility...
> Using python  /usr/bin/python2.7
> Checking for previously running Metric Monitor...
> Starting ambari-metrics-monitor
> Verifying ambari-metrics-monitor process status...
> ERROR: ambari-metrics-monitor start failed. For more details, see 
> /grid/0/log/metric_monitor/ambari-metrics-monitor.out:
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19243) Metric monitor start command failed though the process started successfully.

[Aravindan Vijayan (JIRA)]

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

Aravindan Vijayan updated AMBARI-19243:
---
Status: Patch Available  (was: Open)

> Metric monitor start command failed though the process started successfully.
> 
>
> Key: AMBARI-19243
> URL: https://issues.apache.org/jira/browse/AMBARI-19243
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19243.patch
>
>
> {code}
> psutil build directory is not empty, continuing...
> Verifying Python version compatibility...
> Using python  /usr/bin/python2.7
> Checking for previously running Metric Monitor...
> Starting ambari-metrics-monitor
> Verifying ambari-metrics-monitor process status...
> ERROR: ambari-metrics-monitor start failed. For more details, see 
> /grid/0/log/metric_monitor/ambari-metrics-monitor.out:
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19243) Metric monitor start command failed though the process started successfully.

[Aravindan Vijayan (JIRA)]

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

Aravindan Vijayan updated AMBARI-19243:
---
Attachment: AMBARI-19243.patch

> Metric monitor start command failed though the process started successfully.
> 
>
> Key: AMBARI-19243
> URL: https://issues.apache.org/jira/browse/AMBARI-19243
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19243.patch
>
>
> {code}
> psutil build directory is not empty, continuing...
> Verifying Python version compatibility...
> Using python  /usr/bin/python2.7
> Checking for previously running Metric Monitor...
> Starting ambari-metrics-monitor
> Verifying ambari-metrics-monitor process status...
> ERROR: ambari-metrics-monitor start failed. For more details, see 
> /grid/0/log/metric_monitor/ambari-metrics-monitor.out:
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-19243) Metric monitor start command failed though the process started successfully.

[Aravindan Vijayan (JIRA)]

Aravindan Vijayan created AMBARI-19243:
--

 Summary: Metric monitor start command failed though the process 
started successfully.
 Key: AMBARI-19243
 URL: https://issues.apache.org/jira/browse/AMBARI-19243
 Project: Ambari
  Issue Type: Bug
  Components: ambari-metrics
Affects Versions: 2.5.0
Reporter: Aravindan Vijayan
Assignee: Aravindan Vijayan
Priority: Blocker
 Fix For: 2.5.0






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19239) Logs modal window in Host Details> Logs Tab not displayed properly with hidden modal-footer

[Antonenko Alexander (JIRA)]

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

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

committed to 2.5

> Logs modal window in Host Details> Logs Tab not displayed properly with 
> hidden modal-footer
> ---
>
> Key: AMBARI-19239
> URL: https://issues.apache.org/jira/browse/AMBARI-19239
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19239.patch
>
>
> Logs modal window in Host Details> Logs Tab not displayed properly with 
> hidden modal-footer.
> Chrome Version : 55.0



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19095) HDP 3.0 flatten Role Command Order and remote duplicate configs

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-19095:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12843938/AMBARI-19095.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-server.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9734//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9734//console

This message is automatically generated.

> HDP 3.0 flatten Role Command Order and remote duplicate configs
> ---
>
> Key: AMBARI-19095
> URL: https://issues.apache.org/jira/browse/AMBARI-19095
> Project: Ambari
>  Issue Type: Story
>  Components: stacks
>Affects Versions: 3.0.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 3.0.0
>
> Attachments: AMBARI-19095.patch
>
>
> Flatten out Role Command Order for HDP 3.0 TP based on previous stacks.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19095) HDP 3.0 flatten Role Command Order and remote duplicate configs

[Alejandro Fernandez (JIRA)]

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

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

> HDP 3.0 flatten Role Command Order and remote duplicate configs
> ---
>
> Key: AMBARI-19095
> URL: https://issues.apache.org/jira/browse/AMBARI-19095
> Project: Ambari
>  Issue Type: Story
>  Components: stacks
>Affects Versions: 3.0.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 3.0.0
>
> Attachments: AMBARI-19095.patch
>
>
> Flatten out Role Command Order for HDP 3.0 TP based on previous stacks.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19226) Provide default value for hdfs_tmp_dir parameter in HDFS params script.

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-19226:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12843912/AMBARI-19226-v2.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-server.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9733//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9733//console

This message is automatically generated.

> Provide default value for hdfs_tmp_dir parameter in HDFS params script.
> ---
>
> Key: AMBARI-19226
> URL: https://issues.apache.org/jira/browse/AMBARI-19226
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
>Priority: Minor
> Attachments: AMBARI-19226-v2.patch, AMBARI-19226.patch
>
>
> provide a default value in params.py for hdfs_tmp_dir. The property is not 
> shown on the UI, making it difficult for users to change its value via Ambari 
> web UI if the cluster is deployed via blueprint and the property is missing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19095) HDP 3.0 flatten Role Command Order and remote duplicate configs

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-19095:
-
Attachment: AMBARI-19095.patch

> HDP 3.0 flatten Role Command Order and remote duplicate configs
> ---
>
> Key: AMBARI-19095
> URL: https://issues.apache.org/jira/browse/AMBARI-19095
> Project: Ambari
>  Issue Type: Story
>  Components: stacks
>Affects Versions: 3.0.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 3.0.0
>
> Attachments: AMBARI-19095.patch
>
>
> Flatten out Role Command Order for HDP 3.0 TP based on previous stacks.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19095) HDP 3.0 flatten Role Command Order and remote duplicate configs

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-19095:
-
Summary: HDP 3.0 flatten Role Command Order and remote duplicate configs  
(was: HDP 3.0 flatten Role Command Order and update service versions in 
metainfo.xml  )

> HDP 3.0 flatten Role Command Order and remote duplicate configs
> ---
>
> Key: AMBARI-19095
> URL: https://issues.apache.org/jira/browse/AMBARI-19095
> Project: Ambari
>  Issue Type: Story
>  Components: stacks
>Affects Versions: 3.0.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 3.0.0
>
>
> Flatten out Role Command Order for HDP 3.0 TP based on previous stacks.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19240) Ambari UI should use "hosts_with_failures" from "host_resolution_check" in host check

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19240:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #555 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/555/])
AMBARI-19240 Ambari UI should use "hosts_with_failures" from (atkach: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=578e9a266a1999c1e4b737d3e539d28f37ab2e95])
* (edit) ambari-web/app/utils/ajax/ajax.js
* (edit) ambari-web/test/controllers/wizard/step3_test.js
* (edit) ambari-web/app/controllers/wizard/step3_controller.js


> Ambari UI should use "hosts_with_failures" from "host_resolution_check" in 
> host check
> -
>
> Key: AMBARI-19240
> URL: https://issues.apache.org/jira/browse/AMBARI-19240
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19240.patch, AMBARI-19240_branch-2.5.patch
>
>
> Earlier UI parsed "failures" property value to get hosts which were failed. 
> But in perf clusters "failures" is very big (more than 300 MB), so we decided 
> to add one more property which contains only hostnames which failed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19218) Exception when running Slider view - java.lang.NoClassDefFoundError: org/apache/hadoop/yarn/api/protocolrecords/GetLabelsToNodesResponse

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19218:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #555 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/555/])
AMBARI-19218: Exception when running Slider view - (sangeetar: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=21934340edd7d1fddd895258f0a7c174e0624919])
* (edit) contrib/views/slider/pom.xml


> Exception when running Slider view -  java.lang.NoClassDefFoundError: 
> org/apache/hadoop/yarn/api/protocolrecords/GetLabelsToNodesResponse
> -
>
> Key: AMBARI-19218
> URL: https://issues.apache.org/jira/browse/AMBARI-19218
> Project: Ambari
>  Issue Type: Bug
>  Components: contrib
>Affects Versions: 2.5.0
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>Priority: Minor
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19218_1216.patch, SliderViewExecutionError.jpg
>
>
> When a Slider view is executed, the following error is thrown.
> 15 Dec 2016 10:11:15,645  WARN [ambari-client-thread-28] [SLIDER 2.0.0 S1] 
> SliderAppsViewControllerImpl:847 - Unable to create SliderClient
> java.lang.NoClassDefFoundError: 
> org/apache/hadoop/yarn/api/protocolrecords/GetLabelsToNodesResponse
> This is because the version of hadoop-yarn-api jar under 
> /var/lib/ambari-server/resources/views/work/SLIDER{2.0.0} is 2.6.0.
> The GetLabelsToNodesResponse class was added in 2.7.0 version.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-19149:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12843917/AMBARI-19149-5.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-server.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9732//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9732//console

This message is automatically generated.

> 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-1.patch, AMBARI-19149-3.patch, 
> AMBARI-19149-4.patch, AMBARI-19149-5.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.4#6332)

[jira] [Commented] (AMBARI-19218) Exception when running Slider view - java.lang.NoClassDefFoundError: org/apache/hadoop/yarn/api/protocolrecords/GetLabelsToNodesResponse

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19218:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6260 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6260/])
AMBARI-19218: Exception when running Slider view - (sangeetar: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=8a125c57a383c926f4ae9961b8b1ef7941bad6f1])
* (edit) contrib/views/slider/pom.xml


> Exception when running Slider view -  java.lang.NoClassDefFoundError: 
> org/apache/hadoop/yarn/api/protocolrecords/GetLabelsToNodesResponse
> -
>
> Key: AMBARI-19218
> URL: https://issues.apache.org/jira/browse/AMBARI-19218
> Project: Ambari
>  Issue Type: Bug
>  Components: contrib
>Affects Versions: 2.5.0
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>Priority: Minor
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19218_1216.patch, SliderViewExecutionError.jpg
>
>
> When a Slider view is executed, the following error is thrown.
> 15 Dec 2016 10:11:15,645  WARN [ambari-client-thread-28] [SLIDER 2.0.0 S1] 
> SliderAppsViewControllerImpl:847 - Unable to create SliderClient
> java.lang.NoClassDefFoundError: 
> org/apache/hadoop/yarn/api/protocolrecords/GetLabelsToNodesResponse
> This is because the version of hadoop-yarn-api jar under 
> /var/lib/ambari-server/resources/views/work/SLIDER{2.0.0} is 2.6.0.
> The GetLabelsToNodesResponse class was added in 2.7.0 version.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19240) Ambari UI should use "hosts_with_failures" from "host_resolution_check" in host check

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19240:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6260 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6260/])
AMBARI-19240 Ambari UI should use "hosts_with_failures" from (atkach: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=72e9d4a4fb6a09b436a363b7ba8cdf6f6fa17132])
* (edit) ambari-web/test/controllers/wizard/step3_test.js
* (edit) ambari-web/app/mixins/main/host/details/actions/check_host.js
* (edit) ambari-web/app/utils/ajax/ajax.js


> Ambari UI should use "hosts_with_failures" from "host_resolution_check" in 
> host check
> -
>
> Key: AMBARI-19240
> URL: https://issues.apache.org/jira/browse/AMBARI-19240
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19240.patch, AMBARI-19240_branch-2.5.patch
>
>
> Earlier UI parsed "failures" property value to get hosts which were failed. 
> But in perf clusters "failures" is very big (more than 300 MB), so we decided 
> to add one more property which contains only hostnames which failed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19132) When disabling Kerberos, rm should be used when deleting the Ambari Server keytab file(s)

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19132:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #554 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/554/])
AMBARI-19132. Use "rm" to delete Ambari Server keytab files when (rlevas: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=435006d4b763b626336a92e2dd43adc72c6a7c10])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/utils/ShellCommandUtil.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/utils/TestShellCommandUtil.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/DestroyPrincipalsServerAction.java


> When disabling Kerberos, rm should be used when deleting the Ambari Server 
> keytab file(s)
> -
>
> Key: AMBARI-19132
> URL: https://issues.apache.org/jira/browse/AMBARI-19132
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Levas
>Assignee: Doroszlai, Attila
>  Labels: kerberos, sudo
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-19132_branch-2.5.patch, AMBARI-19132_trunk.patch
>
>
> When disabling Kerberos, {{rm}} should be used when deleting the Ambari 
> Server keytab file(s) rather than the Java {{java.io.File#delete}} method. 
> This is to allow for the file to be removed properly when Ambari is not 
> executed as _root_.  
> Currently the Ambari server keytab files may not be removed due to permission 
> issues. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19229) Remove HDP-3.0.0 stack definition from Ambari-2.5

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19229:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #554 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/554/])
AMBARI-19229. Remove HDP-3.0.0 stack definition from Ambari-2.5 (afernandez: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=c358ae0c251748a373542a7b0e6ac9ea9e1b0b78])
* (delete) 
ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/package/templates/exclude_hosts_list.j2
* (delete) 
ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/configuration/ranger-yarn-security.xml
* (delete) 
ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/package/scripts/nodemanager.py
* (delete) 
ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/quicklinks-mapred/quicklinks.json
* (delete) ambari-server/src/main/resources/stacks/HDP/3.0/metainfo.xml
* (delete) 
ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/configuration/ranger-yarn-policymgr-ssl.xml
* (delete) 
ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/package/scripts/service.py
* (delete) 
ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/package/scripts/mapreduce2_client.py
* (delete) 
ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/configuration/hadoop-policy.xml
* (delete) 
ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/kerberos.json
* (delete) 
ambari-server/src/main/resources/stacks/HDP/3.0/configuration/cluster-env.xml
* (delete) 
ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/package/scripts/params.py
* (delete) 
ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/package/files/checkWebUI.py
* (delete) 
ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/metainfo.xml
* (delete) 
ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/package/scripts/datanode.py
* (delete) 
ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/package/scripts/__init__.py
* (delete) 
ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/package/scripts/yarn.py
* (delete) 
ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/package/scripts/nodemanager_upgrade.py
* (delete) 
ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/package/scripts/status_params.py
* (delete) 
ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/configuration-mapred/mapred-site.xml
* (delete) 
ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/package/scripts/application_timeline_server.py
* (delete) 
ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/themes/theme.json
* (delete) 
ambari-server/src/main/resources/stacks/HDP/3.0/properties/stack_tools.json
* (delete) 
ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/configuration/yarn-log4j.xml
* (delete) 
ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/package/scripts/params.py
* (delete) 
ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/package/scripts/utils.py
* (delete) 
ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/alerts.json
* (delete) 
ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/package/scripts/__init__.py
* (delete) 
ambari-server/src/main/resources/common-services/ZOOKEEPER/3.4.9/metainfo.xml
* (delete) 
ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-START/templates/exclude_hosts_list.j2
* (delete) 
ambari-server/src/main/resources/stacks/HDP/3.0/hooks/before-START/files/checkForFormat.sh
* (delete) 
ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/package/scripts/hdfs_nfsgateway.py
* (delete) 
ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/package/templates/hdfs.conf.j2
* (delete) 
ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/package/files/validateYarnComponentStatusWindows.py
* (delete) 
ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/configuration/ranger-yarn-plugin-properties.xml
* (delete) ambari-server/src/main/resources/stacks/HDP/3.0/repos/repoinfo.xml
* (delete) 
ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/configuration/hadoop-metrics2.properties.xml
* (delete) 
ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/quicklinks/quicklinks.json
* (delete) 
ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/metrics.json
* (delete) 
ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/package/scripts/params_linux.py
* (delete) 
ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/package/scripts/yarn_client.py
* (delete) 
ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/package/scripts/params_windows.py
* (delete) 
ambari-server/src/main/resources/stacks/HDP/3.0/services/YARN/metainfo.xml

[jira] [Updated] (AMBARI-19218) Exception when running Slider view - java.lang.NoClassDefFoundError: org/apache/hadoop/yarn/api/protocolrecords/GetLabelsToNodesResponse

[Sangeeta Ravindran (JIRA)]

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

Sangeeta Ravindran updated AMBARI-19218:

   Resolution: Fixed
Fix Version/s: trunk
   Status: Resolved  (was: Patch Available)

Commited to 2.5 and trunk

commit 21934340edd7d1fddd895258f0a7c174e0624919
Author: Sangeeta Ravindran 
Date:   Mon Dec 19 10:21:49 2016 -0800

AMBARI-19218: Exception when running Slider view - 
java.lang.NoClassDefFoundError: 
org/apache/hadoop/yarn/api/protocolrecords/GetLabelsToNodesResponse (sangeetar)

commit 8a125c57a383c926f4ae9961b8b1ef7941bad6f1
Author: Sangeeta Ravindran 
Date:   Mon Dec 19 10:32:42 2016 -0800

AMBARI-19218: Exception when running Slider view - 
java.lang.NoClassDefFoundError: 
org/apache/hadoop/yarn/api/protocolrecords/GetLabelsToNodesResponse (sangeetar)

> Exception when running Slider view -  java.lang.NoClassDefFoundError: 
> org/apache/hadoop/yarn/api/protocolrecords/GetLabelsToNodesResponse
> -
>
> Key: AMBARI-19218
> URL: https://issues.apache.org/jira/browse/AMBARI-19218
> Project: Ambari
>  Issue Type: Bug
>  Components: contrib
>Affects Versions: 2.5.0
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>Priority: Minor
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19218_1216.patch, SliderViewExecutionError.jpg
>
>
> When a Slider view is executed, the following error is thrown.
> 15 Dec 2016 10:11:15,645  WARN [ambari-client-thread-28] [SLIDER 2.0.0 S1] 
> SliderAppsViewControllerImpl:847 - Unable to create SliderClient
> java.lang.NoClassDefFoundError: 
> org/apache/hadoop/yarn/api/protocolrecords/GetLabelsToNodesResponse
> This is because the version of hadoop-yarn-api jar under 
> /var/lib/ambari-server/resources/views/work/SLIDER{2.0.0} is 2.6.0.
> The GetLabelsToNodesResponse class was added in 2.7.0 version.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19132) When disabling Kerberos, rm should be used when deleting the Ambari Server keytab file(s)

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19132:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6259 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6259/])
AMBARI-19132. Use "rm" to delete Ambari Server keytab files when (rlevas: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f0544dfa9a1bf462451dbbaf688ceb22e5ceb773])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/utils/ShellCommandUtil.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/DestroyPrincipalsServerAction.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/utils/TestShellCommandUtil.java


> When disabling Kerberos, rm should be used when deleting the Ambari Server 
> keytab file(s)
> -
>
> Key: AMBARI-19132
> URL: https://issues.apache.org/jira/browse/AMBARI-19132
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Levas
>Assignee: Doroszlai, Attila
>  Labels: kerberos, sudo
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-19132_branch-2.5.patch, AMBARI-19132_trunk.patch
>
>
> When disabling Kerberos, {{rm}} should be used when deleting the Ambari 
> Server keytab file(s) rather than the Java {{java.io.File#delete}} method. 
> This is to allow for the file to be removed properly when Ambari is not 
> executed as _root_.  
> Currently the Ambari server keytab files may not be removed due to permission 
> issues. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19240) Ambari UI should use "hosts_with_failures" from "host_resolution_check" in host check

[Andrii Tkach (JIRA)]

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

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

> Ambari UI should use "hosts_with_failures" from "host_resolution_check" in 
> host check
> -
>
> Key: AMBARI-19240
> URL: https://issues.apache.org/jira/browse/AMBARI-19240
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19240.patch, AMBARI-19240_branch-2.5.patch
>
>
> Earlier UI parsed "failures" property value to get hosts which were failed. 
> But in perf clusters "failures" is very big (more than 300 MB), so we decided 
> to add one more property which contains only hostnames which failed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18956) Ambari attempts to commit transactions marked as rollback-only

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18956:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #553 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/553/])
AMBARI-18956. Ambari attempts to commit transactions marked as (stoader: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4c04a91536f87c422440b4e954d810336585882d])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/orm/AmbariJpaLocalTxnInterceptor.java
* (add) 
ambari-server/src/test/java/org/apache/ambari/server/orm/AmbariJpaLocalTxnInterceptorTest.java


> Ambari attempts to commit transactions marked as rollback-only
> --
>
> Key: AMBARI-18956
> URL: https://issues.apache.org/jira/browse/AMBARI-18956
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Minor
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-18956.patch
>
>
> {{EntityTransaction}} may be marked 
> [rollback-only|http://docs.oracle.com/javaee/6/api/javax/persistence/EntityTransaction.html#setRollbackOnly()]
>  due to exception.  If {{@Transactional}} is not marked to {{rollbackOn()}} 
> such exception, Ambari still attempts to commit the transaction.  The end 
> result for the transaction is the same (rollback), but instead of the 
> original exception a {{RollbackException}} is reported, so information is 
> lost.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19132) When disabling Kerberos, rm should be used when deleting the Ambari Server keytab file(s)

[Doroszlai, Attila (JIRA)]

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

Doroszlai, Attila updated AMBARI-19132:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed to 
[trunk|https://git1-us-west.apache.org/repos/asf?p=ambari.git;a=commit;h=f0544dfa9a1bf462451dbbaf688ceb22e5ceb773]
 and 
[branch-2.5|https://git1-us-west.apache.org/repos/asf?p=ambari.git;a=commit;h=435006d4].

> When disabling Kerberos, rm should be used when deleting the Ambari Server 
> keytab file(s)
> -
>
> Key: AMBARI-19132
> URL: https://issues.apache.org/jira/browse/AMBARI-19132
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Levas
>Assignee: Doroszlai, Attila
>  Labels: kerberos, sudo
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-19132_branch-2.5.patch, AMBARI-19132_trunk.patch
>
>
> When disabling Kerberos, {{rm}} should be used when deleting the Ambari 
> Server keytab file(s) rather than the Java {{java.io.File#delete}} method. 
> This is to allow for the file to be removed properly when Ambari is not 
> executed as _root_.  
> Currently the Ambari server keytab files may not be removed due to permission 
> issues. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19229) Remove HDP-3.0.0 stack definition from Ambari-2.5

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-19229:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Pushed to branch-2.5, commit c358ae0c251748a373542a7b0e6ac9ea9e1b0b78

> Remove HDP-3.0.0 stack definition from Ambari-2.5
> -
>
> Key: AMBARI-19229
> URL: https://issues.apache.org/jira/browse/AMBARI-19229
> Project: Ambari
>  Issue Type: Task
>  Components: stacks
>Affects Versions: 2.5.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.0
>
> Attachments: AMBARI-19229.patch
>
>
> Now that we are targeting Ambari-3.0.0 for HDP-3.0.0 stack, there is no need 
> for the stack definition to be in the 2.5 branch.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19238) Avoid copying hadoop xml files for druid configs

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19238:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #552 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/552/])
AMBARI-19238. Avoid copying hadoop xml files for druid configs (Nishant 
(smohanty: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=77908c64f5f11c50a8ce2b79262933cc5646cda3])
* (edit) 
ambari-server/src/main/resources/common-services/DRUID/0.9.2/package/scripts/druid.py
* (edit) ambari-server/src/test/python/stacks/2.6/DRUID/test_druid.py
* (edit) 
ambari-server/src/main/resources/common-services/DRUID/0.9.2/configuration/druid-env.xml


> Avoid copying hadoop xml files for druid configs
> 
>
> Key: AMBARI-19238
> URL: https://issues.apache.org/jira/browse/AMBARI-19238
> Project: Ambari
>  Issue Type: Improvement
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19238.patch
>
>
> Current druid ambari integration creates a copy of hadoop xml files, use 
> hadoop_conf_dir and add that to the classpath instead of making a copy.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19227) Provide support to show Ranger solr-configs in Ambari

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-19227:


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12843907/AMBARI-19227.1.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 3 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-server.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9729//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9729//console

This message is automatically generated.

> Provide support to show Ranger solr-configs in Ambari
> -
>
> Key: AMBARI-19227
> URL: https://issues.apache.org/jira/browse/AMBARI-19227
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
> Fix For: 2.5.0
>
> Attachments: AMBARI-19227.1.patch, AMBARI-19227.patch
>
>
> Need to provide feature for Ranger and update Ambari stacks to show 
> solrconfig.xml on Ambari, so that user can update solr related configs 
> directly from Ambari.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19236) Stackadvisor: incorrect recommendations when only one of two dependencies was changed

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19236:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #552 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/552/])
AMBARI-19236. Stackadvisor: incorrect recommendations when only one of 
(vbrodetskyi: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=6512cc1a08b306737043a525c49f19f8bffb9131])
* (edit) ambari-server/src/main/resources/stacks/stack_advisor.py
* (edit) ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor.py


> Stackadvisor: incorrect recommendations when only one of two dependencies was 
> changed
> -
>
> Key: AMBARI-19236
> URL: https://issues.apache.org/jira/browse/AMBARI-19236
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19236.patch
>
>
> For example:
> 'mapreduce.map.memory.mb' depends on 'yarn.scheduler.maximum-allocation-mb' 
> and 'yarn.scheduler.minimum-allocation-mb'. 
> *The case:*
> 'yarn.scheduler.minimum-allocation-mb' was changed, but 
> 'yarn.scheduler.maximum-allocation-mb' not. In this case recommendations will 
> use provided value for the first property and recommended value for the 
> second. 'mapreduce.map.memory.mb' will be recalculated incorrectly.
> *Expected:*
> Use the provided values for both properties.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18978) Create Quick link profile data model and json parser

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18978:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #552 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/552/])
AMBARI-18978. Create Quick link profile data model and json parser. (stoader: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=2e154608fdd078ce6f879c3a2d747341c17202af])
* (add) 
ambari-server/src/main/java/org/apache/ambari/server/state/quicklinksprofile/QuickLinksProfile.java
* (add) 
ambari-server/src/main/java/org/apache/ambari/server/state/quicklinksprofile/PropertyFilter.java
* (add) 
ambari-server/src/main/java/org/apache/ambari/server/state/quicklinksprofile/AcceptAllFilter.java
* (add) 
ambari-server/src/main/java/org/apache/ambari/server/state/quicklinksprofile/Component.java
* (add) 
ambari-server/src/test/java/org/apache/ambari/server/state/quicklinksprofile/QuickLinksProfileParserTest.java
* (add) 
ambari-server/src/main/java/org/apache/ambari/server/state/quicklinksprofile/QuickLinksProfileParser.java
* (add) ambari-server/src/test/resources/inconsistent_quicklinks_profile.json
* (add) 
ambari-server/src/main/java/org/apache/ambari/server/state/quicklinksprofile/LinkNameFilter.java
* (add) ambari-server/src/test/resources/example_quicklinks_profile.json
* (add) 
ambari-server/src/main/java/org/apache/ambari/server/state/quicklinksprofile/Filter.java
* (add) 
ambari-server/src/main/java/org/apache/ambari/server/state/quicklinksprofile/Service.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/stack/QuickLinksConfigurationModuleTest.java


> Create Quick link profile data model and json parser
> 
>
> Key: AMBARI-18978
> URL: https://issues.apache.org/jira/browse/AMBARI-18978
> Project: Ambari
>  Issue Type: Task
>Affects Versions: 2.5.0
>Reporter: Balázs Bence Sári
>Assignee: Balázs Bence Sári
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-18978-quick-link-profile-data-model_trunk_v7.patch
>
>
> Create the data model and JSON parser for quick link profiles.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18956) Ambari attempts to commit transactions marked as rollback-only

[Doroszlai, Attila (JIRA)]

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

Doroszlai, Attila updated AMBARI-18956:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed to 
[branch-2.5|http://git-wip-us.apache.org/repos/asf/ambari/commit/4c04a915].

> Ambari attempts to commit transactions marked as rollback-only
> --
>
> Key: AMBARI-18956
> URL: https://issues.apache.org/jira/browse/AMBARI-18956
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Minor
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-18956.patch
>
>
> {{EntityTransaction}} may be marked 
> [rollback-only|http://docs.oracle.com/javaee/6/api/javax/persistence/EntityTransaction.html#setRollbackOnly()]
>  due to exception.  If {{@Transactional}} is not marked to {{rollbackOn()}} 
> such exception, Ambari still attempts to commit the transaction.  The end 
> result for the transaction is the same (rollback), but instead of the 
> original exception a {{RollbackException}} is reported, so information is 
> lost.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19240) Ambari UI should use "hosts_with_failures" from "host_resolution_check" in host check

[Andrii Tkach (JIRA)]

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

Andrii Tkach updated AMBARI-19240:
--
Attachment: (was: AMBARI-19240.patch)

> Ambari UI should use "hosts_with_failures" from "host_resolution_check" in 
> host check
> -
>
> Key: AMBARI-19240
> URL: https://issues.apache.org/jira/browse/AMBARI-19240
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19240.patch, AMBARI-19240_branch-2.5.patch
>
>
> Earlier UI parsed "failures" property value to get hosts which were failed. 
> But in perf clusters "failures" is very big (more than 300 MB), so we decided 
> to add one more property which contains only hostnames which failed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19240) Ambari UI should use "hosts_with_failures" from "host_resolution_check" in host check

[Andrii Tkach (JIRA)]

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

Andrii Tkach updated AMBARI-19240:
--
Attachment: AMBARI-19240_branch-2.5.patch

> Ambari UI should use "hosts_with_failures" from "host_resolution_check" in 
> host check
> -
>
> Key: AMBARI-19240
> URL: https://issues.apache.org/jira/browse/AMBARI-19240
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19240.patch, AMBARI-19240_branch-2.5.patch
>
>
> Earlier UI parsed "failures" property value to get hosts which were failed. 
> But in perf clusters "failures" is very big (more than 300 MB), so we decided 
> to add one more property which contains only hostnames which failed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19240) Ambari UI should use "hosts_with_failures" from "host_resolution_check" in host check

[Andrii Tkach (JIRA)]

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

Andrii Tkach updated AMBARI-19240:
--
Attachment: AMBARI-19240.patch

> Ambari UI should use "hosts_with_failures" from "host_resolution_check" in 
> host check
> -
>
> Key: AMBARI-19240
> URL: https://issues.apache.org/jira/browse/AMBARI-19240
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19240.patch, AMBARI-19240_branch-2.5.patch
>
>
> Earlier UI parsed "failures" property value to get hosts which were failed. 
> But in perf clusters "failures" is very big (more than 300 MB), so we decided 
> to add one more property which contains only hostnames which failed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19239) Logs modal window in Host Details> Logs Tab not displayed properly with hidden modal-footer

[Andrii Babiichuk (JIRA)]

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

Andrii Babiichuk commented on AMBARI-19239:
---

+1 for the patch

> Logs modal window in Host Details> Logs Tab not displayed properly with 
> hidden modal-footer
> ---
>
> Key: AMBARI-19239
> URL: https://issues.apache.org/jira/browse/AMBARI-19239
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19239.patch
>
>
> Logs modal window in Host Details> Logs Tab not displayed properly with 
> hidden modal-footer.
> Chrome Version : 55.0



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19239) Logs modal window in Host Details> Logs Tab not displayed properly with hidden modal-footer

[Antonenko Alexander (JIRA)]

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

Antonenko Alexander commented on AMBARI-19239:
--

QA test failed because patch is only for 2.5, also there is no such issue in 
trunk.

rat check passed 

> Logs modal window in Host Details> Logs Tab not displayed properly with 
> hidden modal-footer
> ---
>
> Key: AMBARI-19239
> URL: https://issues.apache.org/jira/browse/AMBARI-19239
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19239.patch
>
>
> Logs modal window in Host Details> Logs Tab not displayed properly with 
> hidden modal-footer.
> Chrome Version : 55.0



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19225) Ambari server should prints error messages to its log if it can't find property for given property attribute type

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-19225:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12843910/AMBARI-19225-v2.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-server.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9728//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9728//console

This message is automatically generated.

> Ambari server should prints error messages to its log if it can't find 
> property for given property attribute type
> -
>
> Key: AMBARI-19225
> URL: https://issues.apache.org/jira/browse/AMBARI-19225
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Attachments: AMBARI-19225-v2.patch, AMBARI-19225.patch
>
>
> Ambari server should prints error messages to its log if it can't find 
> property for given property attribute type, such as NOT_MANAGED_HDFS_PATH



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19233) ATS reports as down in Ambari UI after upgrade

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19233:
-

ABORTED: Integrated in Jenkins build Ambari-branch-2.5 #551 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/551/])
AMBARI-19233. ATS reports as down in Ambari UI after upgrade  (aonishuk) 
(aonishuk: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=0c4bd69e6171b4d58a465fd1fe8e837dd039c2bc])
* (edit) ambari-agent/src/main/python/ambari_agent/main.py


> ATS reports as down in Ambari UI after upgrade 
> ---
>
> Key: AMBARI-19233
> URL: https://issues.apache.org/jira/browse/AMBARI-19233
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-19233.patch
>
>
> Live cluster from today's run:  (available for
> next 18 hours)  
> Cluster name: vs-hdp250-70297  
> ATS Host: 172.22.90.143  
> Keypair - see attached file named - ok
> **Steps**
>   1. Deploy HDP-2.5.0 cluster with Ambari-2.4.1.0
>   2. Upgrade Ambari to 2.5.0.0-419
>   3. Restart ATS and observe the status of ATS after sometime in Ambari UI
> **Result:**  
> ATS shows down. Ambari-agent log shows below:
> 
> 
> 
> INFO 2016-12-08 16:14:44,419 ActionQueue.py:105 - Adding STATUS_COMMAND 
> for component APP_TIMELINE_SERVER of service YARN of cluster cl1 to the queue.
> INFO 2016-12-08 16:14:44,621 ActionQueue.py:105 - Adding STATUS_COMMAND 
> for component NODEMANAGER of service YARN of cluster cl1 to the queue.
> INFO 2016-12-08 16:14:46,429 PythonReflectiveExecutor.py:65 - Reflective 
> command failed with exception:
> Traceback (most recent call last):
>   File 
> "/usr/lib/python2.6/site-packages/ambari_agent/PythonReflectiveExecutor.py", 
> line 57, in run_file
> imp.load_source('__main__', script)
>   File 
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/application_timeline_server.py",
>  line 155, in 
> ApplicationTimelineServer().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 282, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/application_timeline_server.py",
>  line 82, in status
> only_if = format("test -e {yarn_historyserver_pid_file_old}", 
> user=status_params.yarn_user))
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line 
> 155, in __init__
> self.env.run()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 143, in run
> Logger.info_resource(resource)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/logger.py", line 
> 87, in info_resource
> Logger.info(Logger.filter_text(Logger._get_resource_repr(resource)))
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/logger.py", line 
> 110, in _get_resource_repr
> return Logger.get_function_repr(repr(resource), resource.arguments, 
> resource)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/logger.py", line 
> 180, in get_function_repr
> return unicode("{0} {{{1}}}", 'UTF-8').format(name, arguments_str)
>   File "/usr/lib64/python2.6/encodings/utf_8.py", line 16, in decode
> return codecs.utf_8_decode(input, errors, True)
> AttributeError: 'NoneType' object has no attribute 'utf_8_decode'
> INFO 2016-12-08 16:14:53,190 Controller.py:283 - Heartbeat (response id = 
> 15365) with server is running...
> INFO 2016-12-08 16:14:55,083 Heartbeat.py:90 - Adding host info/state to 
> heartbeat message.
> 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-19242) Ambari Server hangs generating tasks for install+start when adding 600 hosts at a time

[Myroslav Papirkovskyi (JIRA)]

Myroslav Papirkovskyi created AMBARI-19242:
--

 Summary: Ambari Server hangs generating tasks for install+start 
when adding 600 hosts at a time
 Key: AMBARI-19242
 URL: https://issues.apache.org/jira/browse/AMBARI-19242
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.4.0
Reporter: Myroslav Papirkovskyi
Assignee: Myroslav Papirkovskyi
Priority: Critical
 Fix For: 2.5.0


ambari-server --hash
bb803fb332d8d247e236b5e1b29fe97acfd7a7ec
rpm -qa | grep ambari
ambari-server-2.4.0.0-6480.x86_64
I deployed one of the PERF clusters using code from trunk with 600 agents.
Upon trying to add another 600 agents, I was able to register the hosts 
manually through the UI, but the server would get stuck when generating the 
install+start tasks.
I waited for over 30 mins and it was stuck.
Refreshing the page caused it go go back to that same step in the wizard, so I 
had to exit the dialog and start those services on my own.
Because this was the PERF stack, there were no actual bits to install. This 
points to a performance problem on the server.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (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:all-tabpanel
 ]

Doroszlai, Attila updated AMBARI-19149:
---
Attachment: AMBARI-19149-5.patch

> 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-1.patch, AMBARI-19149-3.patch, 
> AMBARI-19149-4.patch, AMBARI-19149-5.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.4#6332)

[jira] [Updated] (AMBARI-19241) Ambari python scripts should support hdfs download

[Tim Thorpe (JIRA)]

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

Tim Thorpe updated AMBARI-19241:

Fix Version/s: 2.5.0
   trunk

> Ambari python scripts should support hdfs download
> --
>
> Key: AMBARI-19241
> URL: https://issues.apache.org/jira/browse/AMBARI-19241
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-agent, contrib
>Affects Versions: trunk, 2.5.0
>Reporter: Tim Thorpe
>Assignee: Tim Thorpe
> Fix For: trunk, 2.5.0
>
>   Original Estimate: 192h
>  Remaining Estimate: 192h
>
> Currently the hdfs_resources.py supports 
> 1) create files/directories in HDFS
> 2) delete files/directories in HDFS
> 3) upload files/directories to HDFS
> We should also support download of files/directories from HDFS.  This will 
> help particularly in cloud environments where the users of the cluster don't 
> necessarily have write access to the local file system.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19241) Ambari python scripts should support hdfs download

[Tim Thorpe (JIRA)]

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

Tim Thorpe updated AMBARI-19241:

Affects Version/s: 2.5.0
   trunk

> Ambari python scripts should support hdfs download
> --
>
> Key: AMBARI-19241
> URL: https://issues.apache.org/jira/browse/AMBARI-19241
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-agent, contrib
>Affects Versions: trunk, 2.5.0
>Reporter: Tim Thorpe
>Assignee: Tim Thorpe
> Fix For: trunk, 2.5.0
>
>   Original Estimate: 192h
>  Remaining Estimate: 192h
>
> Currently the hdfs_resources.py supports 
> 1) create files/directories in HDFS
> 2) delete files/directories in HDFS
> 3) upload files/directories to HDFS
> We should also support download of files/directories from HDFS.  This will 
> help particularly in cloud environments where the users of the cluster don't 
> necessarily have write access to the local file system.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-19241) Ambari python scripts should support hdfs download

[Tim Thorpe (JIRA)]

Tim Thorpe created AMBARI-19241:
---

 Summary: Ambari python scripts should support hdfs download
 Key: AMBARI-19241
 URL: https://issues.apache.org/jira/browse/AMBARI-19241
 Project: Ambari
  Issue Type: New Feature
  Components: ambari-agent, contrib
Reporter: Tim Thorpe
Assignee: Tim Thorpe


Currently the hdfs_resources.py supports 
1) create files/directories in HDFS
2) delete files/directories in HDFS
3) upload files/directories to HDFS

We should also support download of files/directories from HDFS.  This will help 
particularly in cloud environments where the users of the cluster don't 
necessarily have write access to the local file system.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19240) Ambari UI should use "hosts_with_failures" from "host_resolution_check" in host check

[Andrii Tkach (JIRA)]

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

Andrii Tkach updated AMBARI-19240:
--
Attachment: AMBARI-19240.patch

> Ambari UI should use "hosts_with_failures" from "host_resolution_check" in 
> host check
> -
>
> Key: AMBARI-19240
> URL: https://issues.apache.org/jira/browse/AMBARI-19240
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19240.patch
>
>
> Earlier UI parsed "failures" property value to get hosts which were failed. 
> But in perf clusters "failures" is very big (more than 300 MB), so we decided 
> to add one more property which contains only hostnames which failed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19240) Ambari UI should use "hosts_with_failures" from "host_resolution_check" in host check

[Andrii Tkach (JIRA)]

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

Andrii Tkach updated AMBARI-19240:
--
Status: Patch Available  (was: Open)

> Ambari UI should use "hosts_with_failures" from "host_resolution_check" in 
> host check
> -
>
> Key: AMBARI-19240
> URL: https://issues.apache.org/jira/browse/AMBARI-19240
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19240.patch
>
>
> Earlier UI parsed "failures" property value to get hosts which were failed. 
> But in perf clusters "failures" is very big (more than 300 MB), so we decided 
> to add one more property which contains only hostnames which failed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19240) Ambari UI should use "hosts_with_failures" from "host_resolution_check" in host check

[Andrii Tkach (JIRA)]

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

Andrii Tkach updated AMBARI-19240:
--
Summary: Ambari UI should use "hosts_with_failures" from 
"host_resolution_check" in host check  (was: Ambari UI should use 
"hosts_with_failures" from "host_resolution_check" in host chec)

> Ambari UI should use "hosts_with_failures" from "host_resolution_check" in 
> host check
> -
>
> Key: AMBARI-19240
> URL: https://issues.apache.org/jira/browse/AMBARI-19240
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.5.0
>
>
> Earlier UI parsed "failures" property value to get hosts which were failed. 
> But in perf clusters "failures" is very big (more than 300 MB), so we decided 
> to add one more property which contains only hostnames which failed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-19240) Ambari UI should use "hosts_with_failures" from "host_resolution_check" in host chec

[Andrii Tkach (JIRA)]

Andrii Tkach created AMBARI-19240:
-

 Summary: Ambari UI should use "hosts_with_failures" from 
"host_resolution_check" in host chec
 Key: AMBARI-19240
 URL: https://issues.apache.org/jira/browse/AMBARI-19240
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.5.0
Reporter: Andrii Tkach
Assignee: Andrii Tkach
Priority: Critical
 Fix For: 2.5.0


Earlier UI parsed "failures" property value to get hosts which were failed. But 
in perf clusters "failures" is very big (more than 300 MB), so we decided to 
add one more property which contains only hostnames which failed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19236) Stackadvisor: incorrect recommendations when only one of two dependencies was changed

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19236:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6258 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6258/])
AMBARI-19236. Stackadvisor: incorrect recommendations when only one of 
(vbrodetskyi: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=a08bdc0618ca99d98ae6b93a0a15c278eeec5f75])
* (edit) ambari-server/src/main/resources/stacks/stack_advisor.py
* (edit) ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor.py


> Stackadvisor: incorrect recommendations when only one of two dependencies was 
> changed
> -
>
> Key: AMBARI-19236
> URL: https://issues.apache.org/jira/browse/AMBARI-19236
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19236.patch
>
>
> For example:
> 'mapreduce.map.memory.mb' depends on 'yarn.scheduler.maximum-allocation-mb' 
> and 'yarn.scheduler.minimum-allocation-mb'. 
> *The case:*
> 'yarn.scheduler.minimum-allocation-mb' was changed, but 
> 'yarn.scheduler.maximum-allocation-mb' not. In this case recommendations will 
> use provided value for the first property and recommended value for the 
> second. 'mapreduce.map.memory.mb' will be recalculated incorrectly.
> *Expected:*
> Use the provided values for both properties.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19237) Upper case for selected config group

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19237:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6258 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6258/])
AMBARI-19237. Upper case for selected config group (alexantonenko) (hiveww: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f9d37dfbc9b23b92eb3fd2514611513066c3300d])
* (edit) ambari-web/app/templates/common/configs/service_config.hbs


> Upper case for selected config group
> 
>
> Key: AMBARI-19237
> URL: https://issues.apache.org/jira/browse/AMBARI-19237
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-19237.patch
>
>
> After creating config group with name "q", if we select this group it's name 
> is shown as "Q" (upper case).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19226) Provide default value for hdfs_tmp_dir parameter in HDFS params script.

[Di Li (JIRA)]

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

Di Li updated AMBARI-19226:
---
Status: Patch Available  (was: In Progress)

> Provide default value for hdfs_tmp_dir parameter in HDFS params script.
> ---
>
> Key: AMBARI-19226
> URL: https://issues.apache.org/jira/browse/AMBARI-19226
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
>Priority: Minor
> Attachments: AMBARI-19226-v2.patch, AMBARI-19226.patch
>
>
> provide a default value in params.py for hdfs_tmp_dir. The property is not 
> shown on the UI, making it difficult for users to change its value via Ambari 
> web UI if the cluster is deployed via blueprint and the property is missing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19239) Logs modal window in Host Details> Logs Tab not displayed properly with hidden modal-footer

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-19239:


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

This message is automatically generated.

> Logs modal window in Host Details> Logs Tab not displayed properly with 
> hidden modal-footer
> ---
>
> Key: AMBARI-19239
> URL: https://issues.apache.org/jira/browse/AMBARI-19239
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19239.patch
>
>
> Logs modal window in Host Details> Logs Tab not displayed properly with 
> hidden modal-footer.
> Chrome Version : 55.0



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19226) Provide default value for hdfs_tmp_dir parameter in HDFS params script.

[Di Li (JIRA)]

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

Di Li updated AMBARI-19226:
---
Status: In Progress  (was: Patch Available)

> Provide default value for hdfs_tmp_dir parameter in HDFS params script.
> ---
>
> Key: AMBARI-19226
> URL: https://issues.apache.org/jira/browse/AMBARI-19226
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
>Priority: Minor
> Attachments: AMBARI-19226-v2.patch, AMBARI-19226.patch
>
>
> provide a default value in params.py for hdfs_tmp_dir. The property is not 
> shown on the UI, making it difficult for users to change its value via Ambari 
> web UI if the cluster is deployed via blueprint and the property is missing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19226) Provide default value for hdfs_tmp_dir parameter in HDFS params script.

[Di Li (JIRA)]

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

Di Li updated AMBARI-19226:
---
Attachment: AMBARI-19226-v2.patch

> Provide default value for hdfs_tmp_dir parameter in HDFS params script.
> ---
>
> Key: AMBARI-19226
> URL: https://issues.apache.org/jira/browse/AMBARI-19226
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
>Priority: Minor
> Attachments: AMBARI-19226-v2.patch, AMBARI-19226.patch
>
>
> provide a default value in params.py for hdfs_tmp_dir. The property is not 
> shown on the UI, making it difficult for users to change its value via Ambari 
> web UI if the cluster is deployed via blueprint and the property is missing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19239) Logs modal window in Host Details> Logs Tab not displayed properly with hidden modal-footer

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-19239:


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

This message is automatically generated.

> Logs modal window in Host Details> Logs Tab not displayed properly with 
> hidden modal-footer
> ---
>
> Key: AMBARI-19239
> URL: https://issues.apache.org/jira/browse/AMBARI-19239
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19239.patch
>
>
> Logs modal window in Host Details> Logs Tab not displayed properly with 
> hidden modal-footer.
> Chrome Version : 55.0



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19236) Stackadvisor: incorrect recommendations when only one of two dependencies was changed

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-19236:


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12843863/AMBARI-19236.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-server.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9725//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9725//console

This message is automatically generated.

> Stackadvisor: incorrect recommendations when only one of two dependencies was 
> changed
> -
>
> Key: AMBARI-19236
> URL: https://issues.apache.org/jira/browse/AMBARI-19236
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19236.patch
>
>
> For example:
> 'mapreduce.map.memory.mb' depends on 'yarn.scheduler.maximum-allocation-mb' 
> and 'yarn.scheduler.minimum-allocation-mb'. 
> *The case:*
> 'yarn.scheduler.minimum-allocation-mb' was changed, but 
> 'yarn.scheduler.maximum-allocation-mb' not. In this case recommendations will 
> use provided value for the first property and recommended value for the 
> second. 'mapreduce.map.memory.mb' will be recalculated incorrectly.
> *Expected:*
> Use the provided values for both properties.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19225) Ambari server should prints error messages to its log if it can't find property for given property attribute type

[Di Li (JIRA)]

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

Di Li updated AMBARI-19225:
---
Attachment: AMBARI-19225-v2.patch

> Ambari server should prints error messages to its log if it can't find 
> property for given property attribute type
> -
>
> Key: AMBARI-19225
> URL: https://issues.apache.org/jira/browse/AMBARI-19225
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Attachments: AMBARI-19225-v2.patch, AMBARI-19225.patch
>
>
> Ambari server should prints error messages to its log if it can't find 
> property for given property attribute type, such as NOT_MANAGED_HDFS_PATH



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19225) Ambari server should prints error messages to its log if it can't find property for given property attribute type

[Di Li (JIRA)]

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

Di Li updated AMBARI-19225:
---
Status: Patch Available  (was: In Progress)

> Ambari server should prints error messages to its log if it can't find 
> property for given property attribute type
> -
>
> Key: AMBARI-19225
> URL: https://issues.apache.org/jira/browse/AMBARI-19225
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Attachments: AMBARI-19225-v2.patch, AMBARI-19225.patch
>
>
> Ambari server should prints error messages to its log if it can't find 
> property for given property attribute type, such as NOT_MANAGED_HDFS_PATH



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19225) Ambari server should prints error messages to its log if it can't find property for given property attribute type

[Di Li (JIRA)]

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

Di Li updated AMBARI-19225:
---
Status: In Progress  (was: Patch Available)

> Ambari server should prints error messages to its log if it can't find 
> property for given property attribute type
> -
>
> Key: AMBARI-19225
> URL: https://issues.apache.org/jira/browse/AMBARI-19225
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Attachments: AMBARI-19225-v2.patch, AMBARI-19225.patch
>
>
> Ambari server should prints error messages to its log if it can't find 
> property for given property attribute type, such as NOT_MANAGED_HDFS_PATH



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19239) Logs modal window in Host Details> Logs Tab not displayed properly with hidden modal-footer

[Antonenko Alexander (JIRA)]

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

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

> Logs modal window in Host Details> Logs Tab not displayed properly with 
> hidden modal-footer
> ---
>
> Key: AMBARI-19239
> URL: https://issues.apache.org/jira/browse/AMBARI-19239
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19239.patch
>
>
> Logs modal window in Host Details> Logs Tab not displayed properly with 
> hidden modal-footer.
> Chrome Version : 55.0



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19239) Logs modal window in Host Details> Logs Tab not displayed properly with hidden modal-footer

[Antonenko Alexander (JIRA)]

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

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

> Logs modal window in Host Details> Logs Tab not displayed properly with 
> hidden modal-footer
> ---
>
> Key: AMBARI-19239
> URL: https://issues.apache.org/jira/browse/AMBARI-19239
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19239.patch
>
>
> Logs modal window in Host Details> Logs Tab not displayed properly with 
> hidden modal-footer.
> Chrome Version : 55.0



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-19239) Logs modal window in Host Details> Logs Tab not displayed properly with hidden modal-footer

[Antonenko Alexander (JIRA)]

Antonenko Alexander created AMBARI-19239:


 Summary: Logs modal window in Host Details> Logs Tab not displayed 
properly with hidden modal-footer
 Key: AMBARI-19239
 URL: https://issues.apache.org/jira/browse/AMBARI-19239
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.5.0
Reporter: Antonenko Alexander
Assignee: Antonenko Alexander
Priority: Critical
 Fix For: 2.5.0


Logs modal window in Host Details> Logs Tab not displayed properly with hidden 
modal-footer.

Chrome Version : 55.0



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19237) Upper case for selected config group

[Antonenko Alexander (JIRA)]

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

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

pushed to trunk

> Upper case for selected config group
> 
>
> Key: AMBARI-19237
> URL: https://issues.apache.org/jira/browse/AMBARI-19237
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-19237.patch
>
>
> After creating config group with name "q", if we select this group it's name 
> is shown as "Q" (upper case).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19227) Provide support to show Ranger solr-configs in Ambari

[Vishal Suvagia (JIRA)]

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

Vishal Suvagia updated AMBARI-19227:

Attachment: AMBARI-19227.1.patch

> Provide support to show Ranger solr-configs in Ambari
> -
>
> Key: AMBARI-19227
> URL: https://issues.apache.org/jira/browse/AMBARI-19227
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
> Fix For: 2.5.0
>
> Attachments: AMBARI-19227.1.patch, AMBARI-19227.patch
>
>
> Need to provide feature for Ranger and update Ambari stacks to show 
> solrconfig.xml on Ambari, so that user can update solr related configs 
> directly from Ambari.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19236) Stackadvisor: incorrect recommendations when only one of two dependencies was changed

[Vitaly Brodetskyi (JIRA)]

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

Vitaly Brodetskyi updated AMBARI-19236:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed to trunk and branch-2.5

> Stackadvisor: incorrect recommendations when only one of two dependencies was 
> changed
> -
>
> Key: AMBARI-19236
> URL: https://issues.apache.org/jira/browse/AMBARI-19236
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19236.patch
>
>
> For example:
> 'mapreduce.map.memory.mb' depends on 'yarn.scheduler.maximum-allocation-mb' 
> and 'yarn.scheduler.minimum-allocation-mb'. 
> *The case:*
> 'yarn.scheduler.minimum-allocation-mb' was changed, but 
> 'yarn.scheduler.maximum-allocation-mb' not. In this case recommendations will 
> use provided value for the first property and recommended value for the 
> second. 'mapreduce.map.memory.mb' will be recalculated incorrectly.
> *Expected:*
> Use the provided values for both properties.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19237) Upper case for selected config group

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-19237:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12843866/AMBARI-19237.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-web.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9724//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9724//console

This message is automatically generated.

> Upper case for selected config group
> 
>
> Key: AMBARI-19237
> URL: https://issues.apache.org/jira/browse/AMBARI-19237
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-19237.patch
>
>
> After creating config group with name "q", if we select this group it's name 
> is shown as "Q" (upper case).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19238) Avoid copying hadoop xml files for druid configs

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19238:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6257 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6257/])
AMBARI-19238. Avoid copying hadoop xml files for druid configs (Nishant 
(smohanty: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=9cb96ad08fe2ff148a4fdb148fc6358ebb8155d0])
* (edit) 
ambari-server/src/main/resources/common-services/DRUID/0.9.2/configuration/druid-env.xml
* (edit) 
ambari-server/src/main/resources/common-services/DRUID/0.9.2/package/scripts/druid.py
* (edit) ambari-server/src/test/python/stacks/2.6/DRUID/test_druid.py


> Avoid copying hadoop xml files for druid configs
> 
>
> Key: AMBARI-19238
> URL: https://issues.apache.org/jira/browse/AMBARI-19238
> Project: Ambari
>  Issue Type: Improvement
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19238.patch
>
>
> Current druid ambari integration creates a copy of hadoop xml files, use 
> hadoop_conf_dir and add that to the classpath instead of making a copy.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18949) Extend current quick link JSON with properties

[JIRA]

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

Balázs Bence Sári updated AMBARI-18949:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Extend current quick link JSON with properties
> --
>
> Key: AMBARI-18949
> URL: https://issues.apache.org/jira/browse/AMBARI-18949
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Balázs Bence Sári
>Assignee: Balázs Bence Sári
> Fix For: 2.5.0
>
> Attachments: AMBARI-18949-Quicklinks-properties-trunk-v2.patch
>
>
> Quick link data json should have an optional _properties_ field for each 
> link. This field is a list of Strings and can contain informative tags about 
> the quicklink such a _sso_ or _authenticated_.
> New json parser should be compatible with legacy quick links not having this 
> field.
> *Example (change highlighted)*
> {code:javascript}
> ...
> "links": [
>   {
> "name": "ranger_admin_ui",
> "label": "Ranger Admin UI",
> "requires_user_name": "false",
> "url": "%@://%@:%@",
> --> "properties": ["sso", "authenticated"], <--
> "port":{
>   "http_property": "ranger.service.http.port",
>   "http_default_port": "6080",
>   "https_property": "ranger.service.https.port",
>   "https_default_port": "6182",
>   "regex": "(\\d*)+",
>   "site": "ranger-admin-site"
> }
>   }
> ]
> ...
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19238) Avoid copying hadoop xml files for druid configs

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-19238:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

committed to trunk and branch-2.5

> Avoid copying hadoop xml files for druid configs
> 
>
> Key: AMBARI-19238
> URL: https://issues.apache.org/jira/browse/AMBARI-19238
> Project: Ambari
>  Issue Type: Improvement
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19238.patch
>
>
> Current druid ambari integration creates a copy of hadoop xml files, use 
> hadoop_conf_dir and add that to the classpath instead of making a copy.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19238) Avoid copying hadoop xml files for druid configs

[Nishant Bangarwa (JIRA)]

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

Nishant Bangarwa updated AMBARI-19238:
--
Description: 
Current druid ambari integration creates a copy of hadoop xml files, use 
hadoop_conf_dir and add that to the classpath instead of making a copy.


  was:
Current druid ambari integration creates a copy of hadoop xml files, evaluate 
if we can use HADOOP_HOME and add that to the classpath instead of making a 
copy.



> Avoid copying hadoop xml files for druid configs
> 
>
> Key: AMBARI-19238
> URL: https://issues.apache.org/jira/browse/AMBARI-19238
> Project: Ambari
>  Issue Type: Improvement
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19238.patch
>
>
> Current druid ambari integration creates a copy of hadoop xml files, use 
> hadoop_conf_dir and add that to the classpath instead of making a copy.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19238) Avoid copying hadoop xml files for druid configs

[Nishant Bangarwa (JIRA)]

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

Nishant Bangarwa updated AMBARI-19238:
--
Status: Patch Available  (was: Open)

> Avoid copying hadoop xml files for druid configs
> 
>
> Key: AMBARI-19238
> URL: https://issues.apache.org/jira/browse/AMBARI-19238
> Project: Ambari
>  Issue Type: Improvement
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19238.patch
>
>
> Current druid ambari integration creates a copy of hadoop xml files, evaluate 
> if we can use HADOOP_HOME and add that to the classpath instead of making a 
> copy.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19238) Avoid copying hadoop xml files for druid configs

[Nishant Bangarwa (JIRA)]

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

Nishant Bangarwa updated AMBARI-19238:
--
Attachment: AMBARI-19238.patch

> Avoid copying hadoop xml files for druid configs
> 
>
> Key: AMBARI-19238
> URL: https://issues.apache.org/jira/browse/AMBARI-19238
> Project: Ambari
>  Issue Type: Improvement
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19238.patch
>
>
> Current druid ambari integration creates a copy of hadoop xml files, evaluate 
> if we can use HADOOP_HOME and add that to the classpath instead of making a 
> copy.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-19238) Avoid copying hadoop xml files for druid configs

[Nishant Bangarwa (JIRA)]

Nishant Bangarwa created AMBARI-19238:
-

 Summary: Avoid copying hadoop xml files for druid configs
 Key: AMBARI-19238
 URL: https://issues.apache.org/jira/browse/AMBARI-19238
 Project: Ambari
  Issue Type: Improvement
Reporter: Nishant Bangarwa
Assignee: Nishant Bangarwa
 Fix For: trunk, 2.5.0


Current druid ambari integration creates a copy of hadoop xml files, evaluate 
if we can use HADOOP_HOME and add that to the classpath instead of making a 
copy.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19237) Upper case for selected config group

[Andrii Babiichuk (JIRA)]

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

Andrii Babiichuk commented on AMBARI-19237:
---

+1 for the patch

> Upper case for selected config group
> 
>
> Key: AMBARI-19237
> URL: https://issues.apache.org/jira/browse/AMBARI-19237
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-19237.patch
>
>
> After creating config group with name "q", if we select this group it's name 
> is shown as "Q" (upper case).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-19237) Upper case for selected config group

[Antonenko Alexander (JIRA)]

Antonenko Alexander created AMBARI-19237:


 Summary: Upper case for selected config group
 Key: AMBARI-19237
 URL: https://issues.apache.org/jira/browse/AMBARI-19237
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 3.0.0
Reporter: Antonenko Alexander
Assignee: Antonenko Alexander
Priority: Critical
 Fix For: 3.0.0


After creating config group with name "q", if we select this group it's name is 
shown as "Q" (upper case).




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19237) Upper case for selected config group

[Antonenko Alexander (JIRA)]

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

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

> Upper case for selected config group
> 
>
> Key: AMBARI-19237
> URL: https://issues.apache.org/jira/browse/AMBARI-19237
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-19237.patch
>
>
> After creating config group with name "q", if we select this group it's name 
> is shown as "Q" (upper case).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19237) Upper case for selected config group

[Antonenko Alexander (JIRA)]

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

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

> Upper case for selected config group
> 
>
> Key: AMBARI-19237
> URL: https://issues.apache.org/jira/browse/AMBARI-19237
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-19237.patch
>
>
> After creating config group with name "q", if we select this group it's name 
> is shown as "Q" (upper case).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19236) Stackadvisor: incorrect recommendations when only one of two dependencies was changed

[Vitaly Brodetskyi (JIRA)]

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

Vitaly Brodetskyi updated AMBARI-19236:
---
Status: Patch Available  (was: Open)

> Stackadvisor: incorrect recommendations when only one of two dependencies was 
> changed
> -
>
> Key: AMBARI-19236
> URL: https://issues.apache.org/jira/browse/AMBARI-19236
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19236.patch
>
>
> For example:
> 'mapreduce.map.memory.mb' depends on 'yarn.scheduler.maximum-allocation-mb' 
> and 'yarn.scheduler.minimum-allocation-mb'. 
> *The case:*
> 'yarn.scheduler.minimum-allocation-mb' was changed, but 
> 'yarn.scheduler.maximum-allocation-mb' not. In this case recommendations will 
> use provided value for the first property and recommended value for the 
> second. 'mapreduce.map.memory.mb' will be recalculated incorrectly.
> *Expected:*
> Use the provided values for both properties.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-19236) Stackadvisor: incorrect recommendations when only one of two dependencies was changed

[Vitaly Brodetskyi (JIRA)]

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

Vitaly Brodetskyi updated AMBARI-19236:
---
Attachment: AMBARI-19236.patch

> Stackadvisor: incorrect recommendations when only one of two dependencies was 
> changed
> -
>
> Key: AMBARI-19236
> URL: https://issues.apache.org/jira/browse/AMBARI-19236
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19236.patch
>
>
> For example:
> 'mapreduce.map.memory.mb' depends on 'yarn.scheduler.maximum-allocation-mb' 
> and 'yarn.scheduler.minimum-allocation-mb'. 
> *The case:*
> 'yarn.scheduler.minimum-allocation-mb' was changed, but 
> 'yarn.scheduler.maximum-allocation-mb' not. In this case recommendations will 
> use provided value for the first property and recommended value for the 
> second. 'mapreduce.map.memory.mb' will be recalculated incorrectly.
> *Expected:*
> Use the provided values for both properties.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-19236) Stackadvisor: incorrect recommendations when only one of two dependencies was changed

[Vitaly Brodetskyi (JIRA)]

Vitaly Brodetskyi created AMBARI-19236:
--

 Summary: Stackadvisor: incorrect recommendations when only one of 
two dependencies was changed
 Key: AMBARI-19236
 URL: https://issues.apache.org/jira/browse/AMBARI-19236
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.4.0
Reporter: Vitaly Brodetskyi
Assignee: Vitaly Brodetskyi
Priority: Critical
 Fix For: 2.5.0


For example:
'mapreduce.map.memory.mb' depends on 'yarn.scheduler.maximum-allocation-mb' and 
'yarn.scheduler.minimum-allocation-mb'. 

*The case:*
'yarn.scheduler.minimum-allocation-mb' was changed, but 
'yarn.scheduler.maximum-allocation-mb' not. In this case recommendations will 
use provided value for the first property and recommended value for the second. 
'mapreduce.map.memory.mb' will be recalculated incorrectly.

*Expected:*
Use the provided values for both properties.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18791) ADD configs for DRUID in KNOX service definitions

[Nishant Bangarwa (JIRA)]

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

Nishant Bangarwa commented on AMBARI-18791:
---

[~sumitmohanty] can we merge this if there are no additional comments ? 

> ADD configs for DRUID in KNOX service definitions
> -
>
> Key: AMBARI-18791
> URL: https://issues.apache.org/jira/browse/AMBARI-18791
> Project: Ambari
>  Issue Type: Task
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
> Fix For: trunk, 2.5.0
>
> Attachments: ambari-18791.patch
>
>
> KNOX now supports proxying druid services -  
> https://issues.apache.org/jira/browse/KNOX-758
> Add configs for DRUID in KNOX service definitions. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19233) ATS reports as down in Ambari UI after upgrade

[Hudson (JIRA)]

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

Hudson commented on AMBARI-19233:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6256 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6256/])
AMBARI-19233. ATS reports as down in Ambari UI after upgrade  (aonishuk) 
(aonishuk: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=32896cb68659b49ee30f56cc5efd9d642454])
* (edit) ambari-agent/src/main/python/ambari_agent/main.py


> ATS reports as down in Ambari UI after upgrade 
> ---
>
> Key: AMBARI-19233
> URL: https://issues.apache.org/jira/browse/AMBARI-19233
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-19233.patch
>
>
> Live cluster from today's run:  (available for
> next 18 hours)  
> Cluster name: vs-hdp250-70297  
> ATS Host: 172.22.90.143  
> Keypair - see attached file named - ok
> **Steps**
>   1. Deploy HDP-2.5.0 cluster with Ambari-2.4.1.0
>   2. Upgrade Ambari to 2.5.0.0-419
>   3. Restart ATS and observe the status of ATS after sometime in Ambari UI
> **Result:**  
> ATS shows down. Ambari-agent log shows below:
> 
> 
> 
> INFO 2016-12-08 16:14:44,419 ActionQueue.py:105 - Adding STATUS_COMMAND 
> for component APP_TIMELINE_SERVER of service YARN of cluster cl1 to the queue.
> INFO 2016-12-08 16:14:44,621 ActionQueue.py:105 - Adding STATUS_COMMAND 
> for component NODEMANAGER of service YARN of cluster cl1 to the queue.
> INFO 2016-12-08 16:14:46,429 PythonReflectiveExecutor.py:65 - Reflective 
> command failed with exception:
> Traceback (most recent call last):
>   File 
> "/usr/lib/python2.6/site-packages/ambari_agent/PythonReflectiveExecutor.py", 
> line 57, in run_file
> imp.load_source('__main__', script)
>   File 
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/application_timeline_server.py",
>  line 155, in 
> ApplicationTimelineServer().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 282, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/application_timeline_server.py",
>  line 82, in status
> only_if = format("test -e {yarn_historyserver_pid_file_old}", 
> user=status_params.yarn_user))
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line 
> 155, in __init__
> self.env.run()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 143, in run
> Logger.info_resource(resource)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/logger.py", line 
> 87, in info_resource
> Logger.info(Logger.filter_text(Logger._get_resource_repr(resource)))
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/logger.py", line 
> 110, in _get_resource_repr
> return Logger.get_function_repr(repr(resource), resource.arguments, 
> resource)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/logger.py", line 
> 180, in get_function_repr
> return unicode("{0} {{{1}}}", 'UTF-8').format(name, arguments_str)
>   File "/usr/lib64/python2.6/encodings/utf_8.py", line 16, in decode
> return codecs.utf_8_decode(input, errors, True)
> AttributeError: 'NoneType' object has no attribute 'utf_8_decode'
> INFO 2016-12-08 16:14:53,190 Controller.py:283 - Heartbeat (response id = 
> 15365) with server is running...
> INFO 2016-12-08 16:14:55,083 Heartbeat.py:90 - Adding host info/state to 
> heartbeat message.
> 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19235) 'Cluster User' role issue after Ambari 2.4.2.0 upgrade

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-19235:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12843854/AMBARI-19235.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 2 new 
or modified test files.

{color:red}-1 javac{color:red}.  The patch appears to cause the build to 
fail.

Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9723//console

This message is automatically generated.

> 'Cluster User' role issue after Ambari 2.4.2.0 upgrade
> --
>
> Key: AMBARI-19235
> URL: https://issues.apache.org/jira/browse/AMBARI-19235
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Eugene Chekanskiy
>Assignee: Eugene Chekanskiy
> Fix For: 2.5.0
>
> Attachments: AMBARI-19235.patch
>
>
> After upgrading from Ambari 2.4.0.1 to Ambari 2.4.2, something has changed 
> that breaks role based access control. Users in the "Cluster User" role no 
> longer get access to the views as they could in 2.4.0.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-19234) ATS reports as down in Ambari UI after upgrade

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-19234:


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

This message is automatically generated.

> ATS reports as down in Ambari UI after upgrade
> --
>
> Key: AMBARI-19234
> URL: https://issues.apache.org/jira/browse/AMBARI-19234
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-upgrade
>Affects Versions: 2.5.0
>Reporter: Vivek Sharma
>Assignee: Andrew Onischuk
>Priority: Critical
>  Labels: upgrade
> Fix For: 2.5.0
>
> Attachments: AMBARI-19234.patch
>
>
> Steps
> 1. Deploy HDP-2.5.0 cluster with Ambari-2.4.1.0
> 2. Upgrade Ambari to 2.5.0.0-419
> 3. Restart ATS and observe the status of ATS after sometime in Ambari UI
> Result:
> ATS shows down. Ambari-agent log shows below:
> {code}
> INFO 2016-12-08 16:14:44,419 ActionQueue.py:105 - Adding STATUS_COMMAND for 
> component APP_TIMELINE_SERVER of service YARN of cluster cl1 to the queue.
> INFO 2016-12-08 16:14:44,621 ActionQueue.py:105 - Adding STATUS_COMMAND for 
> component NODEMANAGER of service YARN of cluster cl1 to the queue.
> INFO 2016-12-08 16:14:46,429 PythonReflectiveExecutor.py:65 - Reflective 
> command failed with exception:
> Traceback (most recent call last):
>   File 
> "/usr/lib/python2.6/site-packages/ambari_agent/PythonReflectiveExecutor.py", 
> line 57, in run_file
> imp.load_source('__main__', script)
>   File 
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/application_timeline_server.py",
>  line 155, in 
> ApplicationTimelineServer().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 282, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/application_timeline_server.py",
>  line 82, in status
> only_if = format("test -e {yarn_historyserver_pid_file_old}", 
> user=status_params.yarn_user))
>   File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", 
> line 155, in __init__
> self.env.run()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 143, in run
> Logger.info_resource(resource)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/logger.py", 
> line 87, in info_resource
> Logger.info(Logger.filter_text(Logger._get_resource_repr(resource)))
>   File "/usr/lib/python2.6/site-packages/resource_management/core/logger.py", 
> line 110, in _get_resource_repr
> return Logger.get_function_repr(repr(resource), resource.arguments, 
> resource)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/logger.py", 
> line 180, in get_function_repr
> return unicode("{0} {{{1}}}", 'UTF-8').format(name, arguments_str)
>   File "/usr/lib64/python2.6/encodings/utf_8.py", line 16, in decode
> return codecs.utf_8_decode(input, errors, True)
> AttributeError: 'NoneType' object has no attribute 'utf_8_decode'
> INFO 2016-12-08 16:14:53,190 Controller.py:283 - Heartbeat (response id = 
> 15365) with server is running...
> INFO 2016-12-08 16:14:55,083 Heartbeat.py:90 - Adding host info/state to 
> heartbeat message.
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)