[jira] [Commented] (AMBARI-20220) Parameterize the Startup Web Server Timeout Default Value

[Rogue Hosaka (JIRA)]

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

Rogue Hosaka commented on AMBARI-20220:
---

Hello @Jonathan Hurley, can you tell me the exact location of the files to 
patch? I have a hard time finding them on my server.

> Parameterize the Startup Web Server Timeout Default Value
> -
>
> Key: AMBARI-20220
> URL: https://issues.apache.org/jira/browse/AMBARI-20220
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vivek Rathod
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20220.patch
>
>
> The {{ambari-server start}} and {{ambari-server restart}} commands are 
> currently hard coded to wait a maximum of 50 seconds for the Jetty server to 
> bind to port 8080 (or whatever the configured port is).
> Under normal circumstances, this value should be fine. However, since Jetty 
> loads classes from views, the more views which are installed increases the 
> total load time before Jetty binds to the server port.
> {code}
> ambari-server restart --debug
> Using python  /usr/bin/python
> Restarting ambari-server
> Waiting for server stop...
> Ambari Server stopped
> Ambari Server running with administrator privileges.
> Organizing resource files at /var/lib/ambari-server/resources...
> Ambari database consistency check started...
> Server PID at: /var/run/ambari-server/ambari-server.pid
> Server out at: /var/log/ambari-server/ambari-server.out
> Server log at: /var/log/ambari-server/ambari-server.log
> Waiting for server 
> start
> DB configs consistency check found warnings. See 
> /var/log/ambari-server/ambari-server-check-database.log for more details.
> ERROR: Exiting with exit code 1.
> REASON: Server not yet listening on http port 8080 after 50 seconds. Exiting.
> {code}
> Although this a general problem with the architecture of Views, it's still 
> valuable to have this startup property configurable.



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

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

[WangJie (JIRA)]

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

WangJie updated AMBARI-20434:
-
Attachment: AMBARI-20434-1.patch

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



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

[jira] [Updated] (AMBARI-20977) Journalnode should support batch restart in hosts' page likeing datanode or region

[zhangxiaolu (JIRA)]

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

zhangxiaolu updated AMBARI-20977:
-
Fix Version/s: 2.5.1
   trunk

> Journalnode should support batch restart in hosts' page likeing datanode or 
> region
> --
>
> Key: AMBARI-20977
> URL: https://issues.apache.org/jira/browse/AMBARI-20977
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: zhangxiaolu
>Assignee: zhangxiaolu
> Fix For: trunk, 2.5.1
>
> Attachments: AMBARI-20977.patch
>
>
> Journalnode should support batch restart in hosts' page likeing datanode or 
> region.



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

[jira] [Updated] (AMBARI-20977) Journalnode should support batch restart in hosts' page likeing datanode or region

[zhangxiaolu (JIRA)]

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

zhangxiaolu updated AMBARI-20977:
-
Affects Version/s: (was: 2.5.2)
   (was: 2.5.1)
   (was: 2.5.0)

> Journalnode should support batch restart in hosts' page likeing datanode or 
> region
> --
>
> Key: AMBARI-20977
> URL: https://issues.apache.org/jira/browse/AMBARI-20977
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: zhangxiaolu
>Assignee: zhangxiaolu
> Fix For: trunk, 2.5.1
>
> Attachments: AMBARI-20977.patch
>
>
> Journalnode should support batch restart in hosts' page likeing datanode or 
> region.



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

[jira] [Updated] (AMBARI-20974) Ambari fails to start due to NPE after installation of HDF mpack

[Madhuvanthi Radhakrishnan (JIRA)]

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

Madhuvanthi Radhakrishnan updated AMBARI-20974:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Ambari fails to start due to NPE after installation of HDF mpack
> 
>
> Key: AMBARI-20974
> URL: https://issues.apache.org/jira/browse/AMBARI-20974
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-sever
>Reporter: Madhuvanthi Radhakrishnan
>Assignee: Madhuvanthi Radhakrishnan
>Priority: Blocker
> Fix For: 2.5.1
>
> Attachments: AMBARI-20974_addendum.patch, AMBARI-20974_trunk.patch
>
>
> when we install HDF mpack we do the following steps
> yum install ambari-server
> ambari-server install-mpack --mpack=/path/to/hdf-mpack --purge --verbose
> ambari-server setup
> The permissions and ownership for stacks , common-services etc is set 
> correctly during ambari-server setup
> Ambari-server daemon is configured to run under user 'slava'. Change this 
> setting [y/n] (n)? n
> Adjusting ambari-server permissions and ownership...
> However, to add HDF services to HDP cluster we install the mpack after 
> deploying the HDP cluster and hence when running Ambari as non-root and with 
> umask = 0027, the permissions and ownerships don't get updated.
> Workaround:
> Re-run ambari-server setup command after installing the HDF mpack but don't 
> really make any config changes. Run this step only to update the permissions.
>  ambari-server setup -s



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

[jira] [Commented] (AMBARI-20947) Use keytab file named 'hive.service.keytab' instead of 'hive.llap.zk.sm.keytab' in hive_server_interactive.py for copying to slider.

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20947:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7454 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/7454/])
AMBARI-20947. Use keytab file named 'hive.service.keytab' instead of 
(sshridhar: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=242d9e76f93d17532a60296d86d4e42f7299e039])
* (edit) 
ambari-server/src/main/resources/common-services/HIVE/2.1.0.3.0/package/scripts/params_linux.py
* (edit) 
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/alerts/alert_llap_app_status.py
* (edit) 
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py
* (edit) 
ambari-server/src/main/resources/common-services/HIVE/2.1.0.3.0/package/alerts/alert_llap_app_status.py
* (edit) 
ambari-server/src/main/resources/common-services/HIVE/2.1.0.3.0/package/scripts/hive_server_interactive.py
* (edit) 
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py


> Use keytab file named 'hive.service.keytab' instead of 
> 'hive.llap.zk.sm.keytab' in hive_server_interactive.py for copying to slider.
> 
>
> Key: AMBARI-20947
> URL: https://issues.apache.org/jira/browse/AMBARI-20947
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Blocker
> Fix For: trunk, 2.5.1
>
> Attachments: AMBARI-20947.01.trunk.patch, AMBARI-20947.1.patch, 
> AMBARI-20947.patch
>
>
> *Issue:* 
> HSI server start failed with "kinit: Key table file 
> '/etc/security/keytabs/hive.llap.zk.sm.keytab' not found while getting 
> initial credentials".
> *Reason:* 
> This can happen when HSI is placed on a node where YARN's NodeManager node 
> doesn't exists. Thus, 'hive.llap.zk.sm.keytab' file wont get generated.
> *Fix:*
> Following are the principals in both keytab files:
> {code}
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# klist -kt 
> hive.service.keytab
> Keytab name: FILE:hive.service.keytab
> KVNO Timestamp Principal
>  - 
> 
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# 
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# klist -kt 
> hive.llap.zk.sm.keytab 
> Keytab name: FILE:hive.llap.zk.sm.keytab
> KVNO Timestamp Principal
>  - 
> 
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# 
> {code}
> Given that *'hive.service.keytab'* and *'hive.llap.zk.sm.keytab'* contains 
> the same principals, we can use 'hive.service.keytab'  for copying principals 
> to slider in HDFS.



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

[jira] [Commented] (AMBARI-20977) Journalnode should support batch restart in hosts' page likeing datanode or region

[zhangxiaolu (JIRA)]

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

zhangxiaolu commented on AMBARI-20977:
--

Hi [~afernandez] , Thank you so much for reviewing my patch on reviewboard, and 
could you be so kind as to commit the patch for me please? Thanks in advance

> Journalnode should support batch restart in hosts' page likeing datanode or 
> region
> --
>
> Key: AMBARI-20977
> URL: https://issues.apache.org/jira/browse/AMBARI-20977
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk, 2.5.0, 2.5.1, 2.5.2
>Reporter: zhangxiaolu
>Assignee: zhangxiaolu
> Attachments: AMBARI-20977.patch
>
>
> Journalnode should support batch restart in hosts' page likeing datanode or 
> region.



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

[jira] [Commented] (AMBARI-20947) Use keytab file named 'hive.service.keytab' instead of 'hive.llap.zk.sm.keytab' in hive_server_interactive.py for copying to slider.

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20947:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1522 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/1522/])
AMBARI-20947. Use keytab file named 'hive.service.keytab' instead of 
(sshridhar: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=f125f6059680572802f7a7dc9922e8379d0e5730])
* (edit) 
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/alerts/alert_llap_app_status.py
* (edit) 
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py
* (edit) 
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py


> Use keytab file named 'hive.service.keytab' instead of 
> 'hive.llap.zk.sm.keytab' in hive_server_interactive.py for copying to slider.
> 
>
> Key: AMBARI-20947
> URL: https://issues.apache.org/jira/browse/AMBARI-20947
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Blocker
> Fix For: trunk, 2.5.1
>
> Attachments: AMBARI-20947.01.trunk.patch, AMBARI-20947.1.patch, 
> AMBARI-20947.patch
>
>
> *Issue:* 
> HSI server start failed with "kinit: Key table file 
> '/etc/security/keytabs/hive.llap.zk.sm.keytab' not found while getting 
> initial credentials".
> *Reason:* 
> This can happen when HSI is placed on a node where YARN's NodeManager node 
> doesn't exists. Thus, 'hive.llap.zk.sm.keytab' file wont get generated.
> *Fix:*
> Following are the principals in both keytab files:
> {code}
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# klist -kt 
> hive.service.keytab
> Keytab name: FILE:hive.service.keytab
> KVNO Timestamp Principal
>  - 
> 
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# 
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# klist -kt 
> hive.llap.zk.sm.keytab 
> Keytab name: FILE:hive.llap.zk.sm.keytab
> KVNO Timestamp Principal
>  - 
> 
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# 
> {code}
> Given that *'hive.service.keytab'* and *'hive.llap.zk.sm.keytab'* contains 
> the same principals, we can use 'hive.service.keytab'  for copying principals 
> to slider in HDFS.



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

[jira] [Updated] (AMBARI-20947) Use keytab file named 'hive.service.keytab' instead of 'hive.llap.zk.sm.keytab' in hive_server_interactive.py for copying to slider.

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar updated AMBARI-20947:
-
Status: Patch Available  (was: Reopened)

> Use keytab file named 'hive.service.keytab' instead of 
> 'hive.llap.zk.sm.keytab' in hive_server_interactive.py for copying to slider.
> 
>
> Key: AMBARI-20947
> URL: https://issues.apache.org/jira/browse/AMBARI-20947
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Blocker
> Fix For: trunk, 2.5.1
>
> Attachments: AMBARI-20947.01.trunk.patch, AMBARI-20947.1.patch, 
> AMBARI-20947.patch
>
>
> *Issue:* 
> HSI server start failed with "kinit: Key table file 
> '/etc/security/keytabs/hive.llap.zk.sm.keytab' not found while getting 
> initial credentials".
> *Reason:* 
> This can happen when HSI is placed on a node where YARN's NodeManager node 
> doesn't exists. Thus, 'hive.llap.zk.sm.keytab' file wont get generated.
> *Fix:*
> Following are the principals in both keytab files:
> {code}
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# klist -kt 
> hive.service.keytab
> Keytab name: FILE:hive.service.keytab
> KVNO Timestamp Principal
>  - 
> 
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# 
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# klist -kt 
> hive.llap.zk.sm.keytab 
> Keytab name: FILE:hive.llap.zk.sm.keytab
> KVNO Timestamp Principal
>  - 
> 
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# 
> {code}
> Given that *'hive.service.keytab'* and *'hive.llap.zk.sm.keytab'* contains 
> the same principals, we can use 'hive.service.keytab'  for copying principals 
> to slider in HDFS.



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

[jira] [Updated] (AMBARI-20947) Use keytab file named 'hive.service.keytab' instead of 'hive.llap.zk.sm.keytab' in hive_server_interactive.py for copying to slider.

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar updated AMBARI-20947:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Use keytab file named 'hive.service.keytab' instead of 
> 'hive.llap.zk.sm.keytab' in hive_server_interactive.py for copying to slider.
> 
>
> Key: AMBARI-20947
> URL: https://issues.apache.org/jira/browse/AMBARI-20947
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Blocker
> Fix For: trunk, 2.5.1
>
> Attachments: AMBARI-20947.01.trunk.patch, AMBARI-20947.1.patch, 
> AMBARI-20947.patch
>
>
> *Issue:* 
> HSI server start failed with "kinit: Key table file 
> '/etc/security/keytabs/hive.llap.zk.sm.keytab' not found while getting 
> initial credentials".
> *Reason:* 
> This can happen when HSI is placed on a node where YARN's NodeManager node 
> doesn't exists. Thus, 'hive.llap.zk.sm.keytab' file wont get generated.
> *Fix:*
> Following are the principals in both keytab files:
> {code}
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# klist -kt 
> hive.service.keytab
> Keytab name: FILE:hive.service.keytab
> KVNO Timestamp Principal
>  - 
> 
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# 
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# klist -kt 
> hive.llap.zk.sm.keytab 
> Keytab name: FILE:hive.llap.zk.sm.keytab
> KVNO Timestamp Principal
>  - 
> 
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# 
> {code}
> Given that *'hive.service.keytab'* and *'hive.llap.zk.sm.keytab'* contains 
> the same principals, we can use 'hive.service.keytab'  for copying principals 
> to slider in HDFS.



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

[jira] [Commented] (AMBARI-20947) Use keytab file named 'hive.service.keytab' instead of 'hive.llap.zk.sm.keytab' in hive_server_interactive.py for copying to slider.

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar commented on AMBARI-20947:
--

branch-2.5

{code}
commit f125f6059680572802f7a7dc9922e8379d0e5730
Author: Swapan Shridhar 
Date:   Wed May 10 14:01:59 2017 -0700

AMBARI-20947. Use keytab file named 'hive.service.keytab' instead of 
'hive.llap.zk.sm.keytab' in hive_server_interactive.py for copying to slider.
{code}


trunk:

{code}
commit 242d9e76f93d17532a60296d86d4e42f7299e039
Author: Swapan Shridhar 
Date:   Wed May 10 17:02:42 2017 -0700

AMBARI-20947. Use keytab file named 'hive.service.keytab' instead of 
'hive.llap.zk.sm.keytab' in hive_server_interactive.py for copying to slider.
{code}

> Use keytab file named 'hive.service.keytab' instead of 
> 'hive.llap.zk.sm.keytab' in hive_server_interactive.py for copying to slider.
> 
>
> Key: AMBARI-20947
> URL: https://issues.apache.org/jira/browse/AMBARI-20947
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Blocker
> Fix For: trunk, 2.5.1
>
> Attachments: AMBARI-20947.01.trunk.patch, AMBARI-20947.1.patch, 
> AMBARI-20947.patch
>
>
> *Issue:* 
> HSI server start failed with "kinit: Key table file 
> '/etc/security/keytabs/hive.llap.zk.sm.keytab' not found while getting 
> initial credentials".
> *Reason:* 
> This can happen when HSI is placed on a node where YARN's NodeManager node 
> doesn't exists. Thus, 'hive.llap.zk.sm.keytab' file wont get generated.
> *Fix:*
> Following are the principals in both keytab files:
> {code}
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# klist -kt 
> hive.service.keytab
> Keytab name: FILE:hive.service.keytab
> KVNO Timestamp Principal
>  - 
> 
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# 
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# klist -kt 
> hive.llap.zk.sm.keytab 
> Keytab name: FILE:hive.llap.zk.sm.keytab
> KVNO Timestamp Principal
>  - 
> 
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# 
> {code}
> Given that *'hive.service.keytab'* and *'hive.llap.zk.sm.keytab'* contains 
> the same principals, we can use 'hive.service.keytab'  for copying principals 
> to slider in HDFS.



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

[jira] [Updated] (AMBARI-20947) Use keytab file named 'hive.service.keytab' instead of 'hive.llap.zk.sm.keytab' in hive_server_interactive.py for copying to slider.

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar updated AMBARI-20947:
-
Attachment: AMBARI-20947.01.trunk.patch

> Use keytab file named 'hive.service.keytab' instead of 
> 'hive.llap.zk.sm.keytab' in hive_server_interactive.py for copying to slider.
> 
>
> Key: AMBARI-20947
> URL: https://issues.apache.org/jira/browse/AMBARI-20947
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Blocker
> Fix For: trunk, 2.5.1
>
> Attachments: AMBARI-20947.01.trunk.patch, AMBARI-20947.1.patch, 
> AMBARI-20947.patch
>
>
> *Issue:* 
> HSI server start failed with "kinit: Key table file 
> '/etc/security/keytabs/hive.llap.zk.sm.keytab' not found while getting 
> initial credentials".
> *Reason:* 
> This can happen when HSI is placed on a node where YARN's NodeManager node 
> doesn't exists. Thus, 'hive.llap.zk.sm.keytab' file wont get generated.
> *Fix:*
> Following are the principals in both keytab files:
> {code}
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# klist -kt 
> hive.service.keytab
> Keytab name: FILE:hive.service.keytab
> KVNO Timestamp Principal
>  - 
> 
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# 
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# klist -kt 
> hive.llap.zk.sm.keytab 
> Keytab name: FILE:hive.llap.zk.sm.keytab
> KVNO Timestamp Principal
>  - 
> 
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# 
> {code}
> Given that *'hive.service.keytab'* and *'hive.llap.zk.sm.keytab'* contains 
> the same principals, we can use 'hive.service.keytab'  for copying principals 
> to slider in HDFS.



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

[jira] [Commented] (AMBARI-20947) Use keytab file named 'hive.service.keytab' instead of 'hive.llap.zk.sm.keytab' in hive_server_interactive.py for copying to slider.

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty commented on AMBARI-20947:


LGTM, +1

> Use keytab file named 'hive.service.keytab' instead of 
> 'hive.llap.zk.sm.keytab' in hive_server_interactive.py for copying to slider.
> 
>
> Key: AMBARI-20947
> URL: https://issues.apache.org/jira/browse/AMBARI-20947
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Blocker
> Fix For: trunk, 2.5.1
>
> Attachments: AMBARI-20947.1.patch, AMBARI-20947.patch
>
>
> *Issue:* 
> HSI server start failed with "kinit: Key table file 
> '/etc/security/keytabs/hive.llap.zk.sm.keytab' not found while getting 
> initial credentials".
> *Reason:* 
> This can happen when HSI is placed on a node where YARN's NodeManager node 
> doesn't exists. Thus, 'hive.llap.zk.sm.keytab' file wont get generated.
> *Fix:*
> Following are the principals in both keytab files:
> {code}
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# klist -kt 
> hive.service.keytab
> Keytab name: FILE:hive.service.keytab
> KVNO Timestamp Principal
>  - 
> 
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# 
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# klist -kt 
> hive.llap.zk.sm.keytab 
> Keytab name: FILE:hive.llap.zk.sm.keytab
> KVNO Timestamp Principal
>  - 
> 
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# 
> {code}
> Given that *'hive.service.keytab'* and *'hive.llap.zk.sm.keytab'* contains 
> the same principals, we can use 'hive.service.keytab'  for copying principals 
> to slider in HDFS.



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

[jira] [Commented] (AMBARI-20937) Ambari Upgrade to 2.5 fails due to custom service; rpm upgrade does not preserve the custom service directory

[Derek Wood (JIRA)]

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

Derek Wood commented on AMBARI-20937:
-

Thanks all.

Also worth mentioning for others: a workaround was to reinstall the files for 
the custom service after the ambari upgrade.  In this case: yum reinstall 
cdap-ambari-service

> Ambari Upgrade to 2.5 fails due to custom service; rpm upgrade does not 
> preserve the custom service directory
> -
>
> Key: AMBARI-20937
> URL: https://issues.apache.org/jira/browse/AMBARI-20937
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-upgrade
>Affects Versions: 2.5.0
>Reporter: Derek Wood
>Assignee: Vitaly Brodetskyi
> Fix For: 2.5.1
>
> Attachments: AMBARI-20937.patch
>
>
> We have a 2.4.0.0 Ambari cluster, with HDP 2.5 and the custom service 
> definition for CDAP installed (source here: 
> https://github.com/caskdata/cdap-ambari-service).  When attempting to upgrade 
> to Ambari 2.5.0.3, the "ambari-server upgrade" command to upgrade the db 
> schema fails, apparently due to the existence of the custom service.  Is this 
> expected, and is there a workaround?
> Steps taken:
> 1. stop all cluster services
> 2. stop ambari 2.4 server and agents
> 3. yum upgrade the ambari packages
> 4. run the schema upgrade as below:
> {code}
> # ambari-server upgrade
> Using python  /usr/bin/python
> Upgrading ambari-server
> INFO: Upgrade Ambari Server
> INFO: Updating Ambari Server properties in ambari.properties ...
> INFO: Updating Ambari Server properties in ambari-env.sh ...
> WARNING: Original file ambari-env.sh kept
> INFO: Fixing database objects owner
> Ambari Server configured for Embedded Postgres. Confirm you have made a 
> backup of the Ambari Server database [y/n] (y)? y
> INFO: Upgrading database schema
> INFO: Return code from schema upgrade command, retcode = 1
> ERROR: Error executing schema upgrade, please check the server logs.
> ERROR: Error output from schema upgrade command:
> ERROR: Exception in thread "main" org.apache.ambari.server.AmbariException: 
> Guice provision errors:
> 1) Error injecting method, java.lang.RuntimeException: Trying to create a 
> ServiceComponent not recognized in stack info, clusterName=lamb-00022663, 
> serviceName=CDAP, componentName=CDAP_CLI, stackInfo=HDP-2.5
>   at 
> org.apache.ambari.server.state.cluster.ClustersImpl.loadClustersAndHosts(ClustersImpl.java:186)
>   at 
> org.apache.ambari.server.state.cluster.ClustersImpl.class(ClustersImpl.java:102)
>   while locating org.apache.ambari.server.state.cluster.ClustersImpl
>   while locating org.apache.ambari.server.state.Clusters
> for field at 
> org.apache.ambari.server.actionmanager.ActionDBAccessorImpl.clusters(ActionDBAccessorImpl.java:84)
>   at 
> org.apache.ambari.server.actionmanager.ActionDBAccessorImpl.class(ActionDBAccessorImpl.java:84)
>   while locating org.apache.ambari.server.actionmanager.ActionDBAccessorImpl
>   while locating org.apache.ambari.server.actionmanager.ActionDBAccessor
> for parameter 0 at 
> org.apache.ambari.server.actionmanager.ActionManager.(ActionManager.java:63)
>   at 
> org.apache.ambari.server.actionmanager.ActionManager.class(ActionManager.java:46)
>   while locating org.apache.ambari.server.actionmanager.ActionManager
> for parameter 0 at 
> org.apache.ambari.server.controller.AmbariManagementControllerImpl.(AmbariManagementControllerImpl.java:356)
>   at 
> org.apache.ambari.server.controller.AmbariManagementControllerImpl.class(AmbariManagementControllerImpl.java:226)
>   while locating 
> org.apache.ambari.server.controller.AmbariManagementControllerImpl
>   while locating 
> org.apache.ambari.server.controller.AmbariManagementController
> 1 error
>   at 
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:240)
>   at 
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:430)
> Caused by: com.google.inject.ProvisionException: Guice provision errors:
> 1) Error injecting method, java.lang.RuntimeException: Trying to create a 
> ServiceComponent not recognized in stack info, clusterName=lamb-00022663, 
> serviceName=CDAP, componentName=CDAP_CLI, stackInfo=HDP-2.5
>   at 
> org.apache.ambari.server.state.cluster.ClustersImpl.loadClustersAndHosts(ClustersImpl.java:186)
>   at 
> org.apache.ambari.server.state.cluster.ClustersImpl.class(ClustersImpl.java:102)
>   while locating org.apache.ambari.server.state.cluster.ClustersImpl
>   while locating org.apache.ambari.server.state.Clusters
> for field at 
> org.apache.ambari.server.actionmanager.ActionDBAccessorImpl.clusters(ActionDBAccessorImpl.java:84)
>   at 

[jira] [Commented] (AMBARI-20974) Ambari fails to start due to NPE after installation of HDF mpack

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20974:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7453 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/7453/])
AMBARI-20974. Ambari fails to start due to NPE after installation of HDF 
(mradhakrishnan: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=09ca0316d42240ea375e83b901ad3a4b0f55b37a])
* (edit) ambari-server/src/main/python/ambari_server/setupMpacks.py


> Ambari fails to start due to NPE after installation of HDF mpack
> 
>
> Key: AMBARI-20974
> URL: https://issues.apache.org/jira/browse/AMBARI-20974
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-sever
>Reporter: Madhuvanthi Radhakrishnan
>Assignee: Madhuvanthi Radhakrishnan
>Priority: Blocker
> Fix For: 2.5.1
>
> Attachments: AMBARI-20974_addendum.patch, AMBARI-20974_trunk.patch
>
>
> when we install HDF mpack we do the following steps
> yum install ambari-server
> ambari-server install-mpack --mpack=/path/to/hdf-mpack --purge --verbose
> ambari-server setup
> The permissions and ownership for stacks , common-services etc is set 
> correctly during ambari-server setup
> Ambari-server daemon is configured to run under user 'slava'. Change this 
> setting [y/n] (n)? n
> Adjusting ambari-server permissions and ownership...
> However, to add HDF services to HDP cluster we install the mpack after 
> deploying the HDP cluster and hence when running Ambari as non-root and with 
> umask = 0027, the permissions and ownerships don't get updated.
> Workaround:
> Re-run ambari-server setup command after installing the HDF mpack but don't 
> really make any config changes. Run this step only to update the permissions.
>  ambari-server setup -s



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

[jira] [Commented] (AMBARI-20974) Ambari fails to start due to NPE after installation of HDF mpack

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20974:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1521 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/1521/])
AMBARI-20974. Ambari fails to start due to NPE after installation of HDF 
(mradhakrishnan: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=5b79b196c2eca8b01d4b9c5b17a3ed2daad409fe])
* (edit) ambari-server/src/main/python/ambari_server/setupMpacks.py


> Ambari fails to start due to NPE after installation of HDF mpack
> 
>
> Key: AMBARI-20974
> URL: https://issues.apache.org/jira/browse/AMBARI-20974
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-sever
>Reporter: Madhuvanthi Radhakrishnan
>Assignee: Madhuvanthi Radhakrishnan
>Priority: Blocker
> Fix For: 2.5.1
>
> Attachments: AMBARI-20974_addendum.patch, AMBARI-20974_trunk.patch
>
>
> when we install HDF mpack we do the following steps
> yum install ambari-server
> ambari-server install-mpack --mpack=/path/to/hdf-mpack --purge --verbose
> ambari-server setup
> The permissions and ownership for stacks , common-services etc is set 
> correctly during ambari-server setup
> Ambari-server daemon is configured to run under user 'slava'. Change this 
> setting [y/n] (n)? n
> Adjusting ambari-server permissions and ownership...
> However, to add HDF services to HDP cluster we install the mpack after 
> deploying the HDP cluster and hence when running Ambari as non-root and with 
> umask = 0027, the permissions and ownerships don't get updated.
> Workaround:
> Re-run ambari-server setup command after installing the HDF mpack but don't 
> really make any config changes. Run this step only to update the permissions.
>  ambari-server setup -s



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

[jira] [Commented] (AMBARI-20726) Aggregate alert does not show status properly at Maintenance Mode change

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20726:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7452 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/7452/])
AMBARI-20726 - Aggregate alert does not show status properly at (jhurley: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a60f1328bfcf3cfa8ae90ecc59bdc8b51e6daa65])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/events/listeners/alerts/AlertMaintenanceModeListener.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/events/listeners/upgrade/AlertMaintenanceModeListenerTest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/AlertState.java


> Aggregate alert does not show status properly at Maintenance Mode change
> 
>
> Key: AMBARI-20726
> URL: https://issues.apache.org/jira/browse/AMBARI-20726
> Project: Ambari
>  Issue Type: Bug
>  Components: alerts
>Affects Versions: 2.4.2
>Reporter: Qin Liu
>Assignee: Qin Liu
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-20726.patch
>
>
> Aggregate alert does not show status properly at Maintenance Mode change.
> Steps to reproduce:
> Install a cluster that has HBase with one regionserver installed.
> Scenario 1:
> 1. Turn On Maintenance Mode on the RegionServer or on the RegionServer host 
> or on the HBase service.
> 2. Stop the RegionServer after that.
> 3. No red alerts will show as expected.
>Percent RegionServers Available - OK affected: [0], total: [1]
> 4. Now Turn Off Maintenance Mode, still keep the RegionServer down.
>But Percent RegionServers Available alert will still show "OK" - "CRIT" is 
> expected.
> Scenario 2:
> 1) Stop the RegionServer - Red alert will show as expected.
>Percent RegionServers Available - CRIT affected: [1], total: [1]
> 2) Now Turn On Maintenance Mode - For RegionServer status, Red alert will be 
> gone as expected.
>But Percent RegionServers Available alert will still show "CRIT" - "OK" is 
> expected.



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

[jira] [Updated] (AMBARI-20985) HDP 3.0 TP - create service definition for Ranger with configs, kerberos, widgets, etc

[Vitaly Brodetskyi (JIRA)]

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

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

> HDP 3.0 TP - create service definition for Ranger with configs, kerberos, 
> widgets, etc
> --
>
> Key: AMBARI-20985
> URL: https://issues.apache.org/jira/browse/AMBARI-20985
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-20985.patch
>
>
> .



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

[jira] [Updated] (AMBARI-20985) HDP 3.0 TP - create service definition for Ranger with configs, kerberos, widgets, etc

[Vitaly Brodetskyi (JIRA)]

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

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

> HDP 3.0 TP - create service definition for Ranger with configs, kerberos, 
> widgets, etc
> --
>
> Key: AMBARI-20985
> URL: https://issues.apache.org/jira/browse/AMBARI-20985
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-20985.patch
>
>
> .



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

[jira] [Created] (AMBARI-20985) HDP 3.0 TP - create service definition for Ranger with configs, kerberos, widgets, etc

[Vitaly Brodetskyi (JIRA)]

Vitaly Brodetskyi created AMBARI-20985:
--

 Summary: HDP 3.0 TP - create service definition for Ranger with 
configs, kerberos, widgets, etc
 Key: AMBARI-20985
 URL: https://issues.apache.org/jira/browse/AMBARI-20985
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 3.0.0
Reporter: Vitaly Brodetskyi
Assignee: Vitaly Brodetskyi
Priority: Critical
 Fix For: 3.0.0


.



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

[jira] [Updated] (AMBARI-20984) Be able to include HDP repos in blueprint

[Di Li (JIRA)]

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

Di Li updated AMBARI-20984:
---
Status: Patch Available  (was: Open)

> Be able to include HDP repos in blueprint
> -
>
> Key: AMBARI-20984
> URL: https://issues.apache.org/jira/browse/AMBARI-20984
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Fix For: ambari-server
>
> Attachments: AMBARI-20984.patch
>
>
> Currently, if a user wants to use custom HDP repos during a blueprint 
> deployment, he has to update the repo URLs before hand via a REST API. The 
> JIRA here proposes a way to include stack repos in the blueprint as optional 
> fields so that when the fields exist, Ambari server will use the repos to 
> deploy a cluster. This eliminates the need for user to run a separate rest 
> api call before the actual blueprint deployment.



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

[jira] [Updated] (AMBARI-20984) Be able to include HDP repos in blueprint

[Di Li (JIRA)]

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

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

> Be able to include HDP repos in blueprint
> -
>
> Key: AMBARI-20984
> URL: https://issues.apache.org/jira/browse/AMBARI-20984
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Fix For: ambari-server
>
> Attachments: AMBARI-20984.patch
>
>
> Currently, if a user wants to use custom HDP repos during a blueprint 
> deployment, he has to update the repo URLs before hand via a REST API. The 
> JIRA here proposes a way to include stack repos in the blueprint as optional 
> fields so that when the fields exist, Ambari server will use the repos to 
> deploy a cluster. This eliminates the need for user to run a separate rest 
> api call before the actual blueprint deployment.



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

[jira] [Created] (AMBARI-20984) Be able to include HDP repos in blueprint

[Di Li (JIRA)]

Di Li created AMBARI-20984:
--

 Summary: Be able to include HDP repos in blueprint
 Key: AMBARI-20984
 URL: https://issues.apache.org/jira/browse/AMBARI-20984
 Project: Ambari
  Issue Type: New Feature
  Components: ambari-server
Affects Versions: trunk
Reporter: Di Li
Assignee: Di Li
 Fix For: ambari-server


Currently, if a user wants to use custom HDP repos during a blueprint 
deployment, he has to update the repo URLs before hand via a REST API. The JIRA 
here proposes a way to include stack repos in the blueprint as optional fields 
so that when the fields exist, Ambari server will use the repos to deploy a 
cluster. This eliminates the need for user to run a separate rest api call 
before the actual blueprint deployment.



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

[jira] [Updated] (AMBARI-20974) Ambari fails to start due to NPE after installation of HDF mpack

[Madhuvanthi Radhakrishnan (JIRA)]

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

Madhuvanthi Radhakrishnan updated AMBARI-20974:
---
Status: Patch Available  (was: Reopened)

> Ambari fails to start due to NPE after installation of HDF mpack
> 
>
> Key: AMBARI-20974
> URL: https://issues.apache.org/jira/browse/AMBARI-20974
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-sever
>Reporter: Madhuvanthi Radhakrishnan
>Assignee: Madhuvanthi Radhakrishnan
>Priority: Blocker
> Fix For: 2.5.1
>
> Attachments: AMBARI-20974_addendum.patch, AMBARI-20974_trunk.patch
>
>
> when we install HDF mpack we do the following steps
> yum install ambari-server
> ambari-server install-mpack --mpack=/path/to/hdf-mpack --purge --verbose
> ambari-server setup
> The permissions and ownership for stacks , common-services etc is set 
> correctly during ambari-server setup
> Ambari-server daemon is configured to run under user 'slava'. Change this 
> setting [y/n] (n)? n
> Adjusting ambari-server permissions and ownership...
> However, to add HDF services to HDP cluster we install the mpack after 
> deploying the HDP cluster and hence when running Ambari as non-root and with 
> umask = 0027, the permissions and ownerships don't get updated.
> Workaround:
> Re-run ambari-server setup command after installing the HDF mpack but don't 
> really make any config changes. Run this step only to update the permissions.
>  ambari-server setup -s



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

[jira] [Commented] (AMBARI-20947) Use keytab file named 'hive.service.keytab' instead of 'hive.llap.zk.sm.keytab' in hive_server_interactive.py for copying to slider.

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar commented on AMBARI-20947:
--

[^AMBARI-20947.1.patch] for review.
CC [~sumitmohanty] | [~afernandez]

--
Ran 272 tests in 6.767s

OK
--
Total run:1160
Total errors:0
Total failures:0
OK

> Use keytab file named 'hive.service.keytab' instead of 
> 'hive.llap.zk.sm.keytab' in hive_server_interactive.py for copying to slider.
> 
>
> Key: AMBARI-20947
> URL: https://issues.apache.org/jira/browse/AMBARI-20947
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Blocker
> Fix For: trunk, 2.5.1
>
> Attachments: AMBARI-20947.1.patch, AMBARI-20947.patch
>
>
> *Issue:* 
> HSI server start failed with "kinit: Key table file 
> '/etc/security/keytabs/hive.llap.zk.sm.keytab' not found while getting 
> initial credentials".
> *Reason:* 
> This can happen when HSI is placed on a node where YARN's NodeManager node 
> doesn't exists. Thus, 'hive.llap.zk.sm.keytab' file wont get generated.
> *Fix:*
> Following are the principals in both keytab files:
> {code}
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# klist -kt 
> hive.service.keytab
> Keytab name: FILE:hive.service.keytab
> KVNO Timestamp Principal
>  - 
> 
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# 
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# klist -kt 
> hive.llap.zk.sm.keytab 
> Keytab name: FILE:hive.llap.zk.sm.keytab
> KVNO Timestamp Principal
>  - 
> 
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# 
> {code}
> Given that *'hive.service.keytab'* and *'hive.llap.zk.sm.keytab'* contains 
> the same principals, we can use 'hive.service.keytab'  for copying principals 
> to slider in HDFS.



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

[jira] [Updated] (AMBARI-20947) Use keytab file named 'hive.service.keytab' instead of 'hive.llap.zk.sm.keytab' in hive_server_interactive.py for copying to slider.

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar updated AMBARI-20947:
-
Attachment: (was: AMBARI-20947.1.patch)

> Use keytab file named 'hive.service.keytab' instead of 
> 'hive.llap.zk.sm.keytab' in hive_server_interactive.py for copying to slider.
> 
>
> Key: AMBARI-20947
> URL: https://issues.apache.org/jira/browse/AMBARI-20947
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Blocker
> Fix For: trunk, 2.5.1
>
> Attachments: AMBARI-20947.1.patch, AMBARI-20947.patch
>
>
> *Issue:* 
> HSI server start failed with "kinit: Key table file 
> '/etc/security/keytabs/hive.llap.zk.sm.keytab' not found while getting 
> initial credentials".
> *Reason:* 
> This can happen when HSI is placed on a node where YARN's NodeManager node 
> doesn't exists. Thus, 'hive.llap.zk.sm.keytab' file wont get generated.
> *Fix:*
> Following are the principals in both keytab files:
> {code}
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# klist -kt 
> hive.service.keytab
> Keytab name: FILE:hive.service.keytab
> KVNO Timestamp Principal
>  - 
> 
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# 
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# klist -kt 
> hive.llap.zk.sm.keytab 
> Keytab name: FILE:hive.llap.zk.sm.keytab
> KVNO Timestamp Principal
>  - 
> 
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# 
> {code}
> Given that *'hive.service.keytab'* and *'hive.llap.zk.sm.keytab'* contains 
> the same principals, we can use 'hive.service.keytab'  for copying principals 
> to slider in HDFS.



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

[jira] [Updated] (AMBARI-20947) Use keytab file named 'hive.service.keytab' instead of 'hive.llap.zk.sm.keytab' in hive_server_interactive.py for copying to slider.

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar updated AMBARI-20947:
-
Attachment: AMBARI-20947.1.patch

> Use keytab file named 'hive.service.keytab' instead of 
> 'hive.llap.zk.sm.keytab' in hive_server_interactive.py for copying to slider.
> 
>
> Key: AMBARI-20947
> URL: https://issues.apache.org/jira/browse/AMBARI-20947
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Blocker
> Fix For: trunk, 2.5.1
>
> Attachments: AMBARI-20947.1.patch, AMBARI-20947.patch
>
>
> *Issue:* 
> HSI server start failed with "kinit: Key table file 
> '/etc/security/keytabs/hive.llap.zk.sm.keytab' not found while getting 
> initial credentials".
> *Reason:* 
> This can happen when HSI is placed on a node where YARN's NodeManager node 
> doesn't exists. Thus, 'hive.llap.zk.sm.keytab' file wont get generated.
> *Fix:*
> Following are the principals in both keytab files:
> {code}
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# klist -kt 
> hive.service.keytab
> Keytab name: FILE:hive.service.keytab
> KVNO Timestamp Principal
>  - 
> 
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# 
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# klist -kt 
> hive.llap.zk.sm.keytab 
> Keytab name: FILE:hive.llap.zk.sm.keytab
> KVNO Timestamp Principal
>  - 
> 
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# 
> {code}
> Given that *'hive.service.keytab'* and *'hive.llap.zk.sm.keytab'* contains 
> the same principals, we can use 'hive.service.keytab'  for copying principals 
> to slider in HDFS.



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

[jira] [Commented] (AMBARI-20974) Ambari fails to start due to NPE after installation of HDF mpack

[Jayush Luniya (JIRA)]

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

Jayush Luniya commented on AMBARI-20974:


+1 for addendum

> Ambari fails to start due to NPE after installation of HDF mpack
> 
>
> Key: AMBARI-20974
> URL: https://issues.apache.org/jira/browse/AMBARI-20974
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-sever
>Reporter: Madhuvanthi Radhakrishnan
>Assignee: Madhuvanthi Radhakrishnan
>Priority: Blocker
> Fix For: 2.5.1
>
> Attachments: AMBARI-20974_addendum.patch, AMBARI-20974_trunk.patch
>
>
> when we install HDF mpack we do the following steps
> yum install ambari-server
> ambari-server install-mpack --mpack=/path/to/hdf-mpack --purge --verbose
> ambari-server setup
> The permissions and ownership for stacks , common-services etc is set 
> correctly during ambari-server setup
> Ambari-server daemon is configured to run under user 'slava'. Change this 
> setting [y/n] (n)? n
> Adjusting ambari-server permissions and ownership...
> However, to add HDF services to HDP cluster we install the mpack after 
> deploying the HDP cluster and hence when running Ambari as non-root and with 
> umask = 0027, the permissions and ownerships don't get updated.
> Workaround:
> Re-run ambari-server setup command after installing the HDF mpack but don't 
> really make any config changes. Run this step only to update the permissions.
>  ambari-server setup -s



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

[jira] [Reopened] (AMBARI-20974) Ambari fails to start due to NPE after installation of HDF mpack

[Madhuvanthi Radhakrishnan (JIRA)]

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

Madhuvanthi Radhakrishnan reopened AMBARI-20974:


> Ambari fails to start due to NPE after installation of HDF mpack
> 
>
> Key: AMBARI-20974
> URL: https://issues.apache.org/jira/browse/AMBARI-20974
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-sever
>Reporter: Madhuvanthi Radhakrishnan
>Assignee: Madhuvanthi Radhakrishnan
>Priority: Blocker
> Fix For: 2.5.1
>
> Attachments: AMBARI-20974_addendum.patch, AMBARI-20974_trunk.patch
>
>
> when we install HDF mpack we do the following steps
> yum install ambari-server
> ambari-server install-mpack --mpack=/path/to/hdf-mpack --purge --verbose
> ambari-server setup
> The permissions and ownership for stacks , common-services etc is set 
> correctly during ambari-server setup
> Ambari-server daemon is configured to run under user 'slava'. Change this 
> setting [y/n] (n)? n
> Adjusting ambari-server permissions and ownership...
> However, to add HDF services to HDP cluster we install the mpack after 
> deploying the HDP cluster and hence when running Ambari as non-root and with 
> umask = 0027, the permissions and ownerships don't get updated.
> Workaround:
> Re-run ambari-server setup command after installing the HDF mpack but don't 
> really make any config changes. Run this step only to update the permissions.
>  ambari-server setup -s



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

[jira] [Updated] (AMBARI-20947) Use keytab file named 'hive.service.keytab' instead of 'hive.llap.zk.sm.keytab' in hive_server_interactive.py for copying to slider.

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar updated AMBARI-20947:
-
Attachment: AMBARI-20947.1.patch

> Use keytab file named 'hive.service.keytab' instead of 
> 'hive.llap.zk.sm.keytab' in hive_server_interactive.py for copying to slider.
> 
>
> Key: AMBARI-20947
> URL: https://issues.apache.org/jira/browse/AMBARI-20947
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Blocker
> Fix For: trunk, 2.5.1
>
> Attachments: AMBARI-20947.1.patch, AMBARI-20947.patch
>
>
> *Issue:* 
> HSI server start failed with "kinit: Key table file 
> '/etc/security/keytabs/hive.llap.zk.sm.keytab' not found while getting 
> initial credentials".
> *Reason:* 
> This can happen when HSI is placed on a node where YARN's NodeManager node 
> doesn't exists. Thus, 'hive.llap.zk.sm.keytab' file wont get generated.
> *Fix:*
> Following are the principals in both keytab files:
> {code}
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# klist -kt 
> hive.service.keytab
> Keytab name: FILE:hive.service.keytab
> KVNO Timestamp Principal
>  - 
> 
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# 
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# klist -kt 
> hive.llap.zk.sm.keytab 
> Keytab name: FILE:hive.llap.zk.sm.keytab
> KVNO Timestamp Principal
>  - 
> 
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# 
> {code}
> Given that *'hive.service.keytab'* and *'hive.llap.zk.sm.keytab'* contains 
> the same principals, we can use 'hive.service.keytab'  for copying principals 
> to slider in HDFS.



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

[jira] [Updated] (AMBARI-20726) Aggregate alert does not show status properly at Maintenance Mode change

[Jonathan Hurley (JIRA)]

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

Jonathan Hurley updated AMBARI-20726:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Aggregate alert does not show status properly at Maintenance Mode change
> 
>
> Key: AMBARI-20726
> URL: https://issues.apache.org/jira/browse/AMBARI-20726
> Project: Ambari
>  Issue Type: Bug
>  Components: alerts
>Affects Versions: 2.4.2
>Reporter: Qin Liu
>Assignee: Qin Liu
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-20726.patch
>
>
> Aggregate alert does not show status properly at Maintenance Mode change.
> Steps to reproduce:
> Install a cluster that has HBase with one regionserver installed.
> Scenario 1:
> 1. Turn On Maintenance Mode on the RegionServer or on the RegionServer host 
> or on the HBase service.
> 2. Stop the RegionServer after that.
> 3. No red alerts will show as expected.
>Percent RegionServers Available - OK affected: [0], total: [1]
> 4. Now Turn Off Maintenance Mode, still keep the RegionServer down.
>But Percent RegionServers Available alert will still show "OK" - "CRIT" is 
> expected.
> Scenario 2:
> 1) Stop the RegionServer - Red alert will show as expected.
>Percent RegionServers Available - CRIT affected: [1], total: [1]
> 2) Now Turn On Maintenance Mode - For RegionServer status, Red alert will be 
> gone as expected.
>But Percent RegionServers Available alert will still show "CRIT" - "OK" is 
> expected.



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

[jira] [Updated] (AMBARI-20947) Use keytab file named 'hive.service.keytab' instead of 'hive.llap.zk.sm.keytab' in hive_server_interactive.py for copying to slider.

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar updated AMBARI-20947:
-
Attachment: (was: AMBARI-20947.1.patch)

> Use keytab file named 'hive.service.keytab' instead of 
> 'hive.llap.zk.sm.keytab' in hive_server_interactive.py for copying to slider.
> 
>
> Key: AMBARI-20947
> URL: https://issues.apache.org/jira/browse/AMBARI-20947
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Blocker
> Fix For: trunk, 2.5.1
>
> Attachments: AMBARI-20947.patch
>
>
> *Issue:* 
> HSI server start failed with "kinit: Key table file 
> '/etc/security/keytabs/hive.llap.zk.sm.keytab' not found while getting 
> initial credentials".
> *Reason:* 
> This can happen when HSI is placed on a node where YARN's NodeManager node 
> doesn't exists. Thus, 'hive.llap.zk.sm.keytab' file wont get generated.
> *Fix:*
> Following are the principals in both keytab files:
> {code}
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# klist -kt 
> hive.service.keytab
> Keytab name: FILE:hive.service.keytab
> KVNO Timestamp Principal
>  - 
> 
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# 
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# klist -kt 
> hive.llap.zk.sm.keytab 
> Keytab name: FILE:hive.llap.zk.sm.keytab
> KVNO Timestamp Principal
>  - 
> 
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# 
> {code}
> Given that *'hive.service.keytab'* and *'hive.llap.zk.sm.keytab'* contains 
> the same principals, we can use 'hive.service.keytab'  for copying principals 
> to slider in HDFS.



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

[jira] [Updated] (AMBARI-20947) Use keytab file named 'hive.service.keytab' instead of 'hive.llap.zk.sm.keytab' in hive_server_interactive.py for copying to slider.

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar updated AMBARI-20947:
-
Attachment: AMBARI-20947.1.patch

> Use keytab file named 'hive.service.keytab' instead of 
> 'hive.llap.zk.sm.keytab' in hive_server_interactive.py for copying to slider.
> 
>
> Key: AMBARI-20947
> URL: https://issues.apache.org/jira/browse/AMBARI-20947
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Blocker
> Fix For: trunk, 2.5.1
>
> Attachments: AMBARI-20947.1.patch, AMBARI-20947.patch
>
>
> *Issue:* 
> HSI server start failed with "kinit: Key table file 
> '/etc/security/keytabs/hive.llap.zk.sm.keytab' not found while getting 
> initial credentials".
> *Reason:* 
> This can happen when HSI is placed on a node where YARN's NodeManager node 
> doesn't exists. Thus, 'hive.llap.zk.sm.keytab' file wont get generated.
> *Fix:*
> Following are the principals in both keytab files:
> {code}
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# klist -kt 
> hive.service.keytab
> Keytab name: FILE:hive.service.keytab
> KVNO Timestamp Principal
>  - 
> 
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# 
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# klist -kt 
> hive.llap.zk.sm.keytab 
> Keytab name: FILE:hive.llap.zk.sm.keytab
> KVNO Timestamp Principal
>  - 
> 
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
>2 05/03/17 20:57:16 
> hive/ctr-e133-1493418528701-3077-01-03.hwx.s...@example.com
> [root@ctr-e133-1493418528701-3077-01-03 keytabs]# 
> {code}
> Given that *'hive.service.keytab'* and *'hive.llap.zk.sm.keytab'* contains 
> the same principals, we can use 'hive.service.keytab'  for copying principals 
> to slider in HDFS.



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

[jira] [Commented] (AMBARI-20974) Ambari fails to start due to NPE after installation of HDF mpack

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty commented on AMBARI-20974:


Addendum patch looks good, +1

> Ambari fails to start due to NPE after installation of HDF mpack
> 
>
> Key: AMBARI-20974
> URL: https://issues.apache.org/jira/browse/AMBARI-20974
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-sever
>Reporter: Madhuvanthi Radhakrishnan
>Assignee: Madhuvanthi Radhakrishnan
>Priority: Blocker
> Fix For: 2.5.1
>
> Attachments: AMBARI-20974_addendum.patch, AMBARI-20974_trunk.patch
>
>
> when we install HDF mpack we do the following steps
> yum install ambari-server
> ambari-server install-mpack --mpack=/path/to/hdf-mpack --purge --verbose
> ambari-server setup
> The permissions and ownership for stacks , common-services etc is set 
> correctly during ambari-server setup
> Ambari-server daemon is configured to run under user 'slava'. Change this 
> setting [y/n] (n)? n
> Adjusting ambari-server permissions and ownership...
> However, to add HDF services to HDP cluster we install the mpack after 
> deploying the HDP cluster and hence when running Ambari as non-root and with 
> umask = 0027, the permissions and ownerships don't get updated.
> Workaround:
> Re-run ambari-server setup command after installing the HDF mpack but don't 
> really make any config changes. Run this step only to update the permissions.
>  ambari-server setup -s



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

[jira] [Commented] (AMBARI-20974) Ambari fails to start due to NPE after installation of HDF mpack

[Madhuvanthi Radhakrishnan (JIRA)]

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

Madhuvanthi Radhakrishnan commented on AMBARI-20974:


 [~jluniya], [~afernandez], [~sumitmohanty],
Can you please take a look at addendum patch?

> Ambari fails to start due to NPE after installation of HDF mpack
> 
>
> Key: AMBARI-20974
> URL: https://issues.apache.org/jira/browse/AMBARI-20974
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-sever
>Reporter: Madhuvanthi Radhakrishnan
>Assignee: Madhuvanthi Radhakrishnan
>Priority: Blocker
> Fix For: 2.5.1
>
> Attachments: AMBARI-20974_addendum.patch, AMBARI-20974_trunk.patch
>
>
> when we install HDF mpack we do the following steps
> yum install ambari-server
> ambari-server install-mpack --mpack=/path/to/hdf-mpack --purge --verbose
> ambari-server setup
> The permissions and ownership for stacks , common-services etc is set 
> correctly during ambari-server setup
> Ambari-server daemon is configured to run under user 'slava'. Change this 
> setting [y/n] (n)? n
> Adjusting ambari-server permissions and ownership...
> However, to add HDF services to HDP cluster we install the mpack after 
> deploying the HDP cluster and hence when running Ambari as non-root and with 
> umask = 0027, the permissions and ownerships don't get updated.
> Workaround:
> Re-run ambari-server setup command after installing the HDF mpack but don't 
> really make any config changes. Run this step only to update the permissions.
>  ambari-server setup -s



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

[jira] [Updated] (AMBARI-20983) ambari/dev-support/docker build is broken on trunk

[Michael Harp (JIRA)]

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

Michael Harp updated AMBARI-20983:
--
Status: Patch Available  (was: Open)

> ambari/dev-support/docker build is broken on trunk
> --
>
> Key: AMBARI-20983
> URL: https://issues.apache.org/jira/browse/AMBARI-20983
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Michael Harp
>Assignee: Michael Harp
>Priority: Minor
>  Labels: docker
> Attachments: AMBARI_20983.patch
>
>
> Several issues need to be fixed to get the container working;
> 1. Version of maven needs to be updated
> 2. JDK should be version 7
> 3. Set bower flag to run as root in container
> {code}
> docker build -t ambari/build ./dev-support/docker/docker
> 
> [INFO] Reactor Summary:
> [INFO] 
> [INFO] Ambari Main ... SUCCESS [4:58.949s]
> [INFO] Apache Ambari Project POM . SUCCESS [6.050s]
> [INFO] Ambari Web  FAILURE [15.348s]
> [INFO] Ambari Views .. SKIPPED
> [INFO] Ambari Admin View . SKIPPED
> [INFO] utility ... SKIPPED
> [INFO] ambari-metrics  SKIPPED
> [INFO] Ambari Metrics Common . SKIPPED
> [INFO] Ambari Metrics Hadoop Sink  SKIPPED
> [INFO] Ambari Metrics Flume Sink . SKIPPED
> [INFO] Ambari Metrics Kafka Sink . SKIPPED
> [INFO] Ambari Metrics Storm Sink . SKIPPED
> [INFO] Ambari Metrics Storm Sink (Legacy)  SKIPPED
> [INFO] Ambari Metrics Collector .. SKIPPED
> [INFO] Ambari Metrics Monitor  SKIPPED
> [INFO] Ambari Metrics Grafana  SKIPPED
> [INFO] Ambari Metrics Assembly ... SKIPPED
> [INFO] Ambari Server . SKIPPED
> [INFO] Ambari Functional Tests ... SKIPPED
> [INFO] Ambari Agent .. SKIPPED
> [INFO] Ambari Client . SKIPPED
> [INFO] Ambari Python Client .. SKIPPED
> [INFO] Ambari Groovy Client .. SKIPPED
> [INFO] Ambari Shell .. SKIPPED
> [INFO] Ambari Python Shell ... SKIPPED
> [INFO] Ambari Groovy Shell ... SKIPPED
> [INFO] ambari-logsearch .. SKIPPED
> [INFO] Ambari Logsearch Appender . SKIPPED
> [INFO] Ambari Logsearch Config Api ... SKIPPED
> [INFO] Ambari Logsearch Config Zookeeper . SKIPPED
> [INFO] Ambari Logsearch Web .. SKIPPED
> [INFO] Ambari Logsearch Server ... SKIPPED
> [INFO] Ambari Logsearch Log Feeder ... SKIPPED
> [INFO] Ambari Logsearch Assembly . SKIPPED
> [INFO] Ambari Logsearch Integration Test . SKIPPED
> [INFO] ambari-infra .. SKIPPED
> [INFO] Ambari Infra Solr Client .. SKIPPED
> [INFO] Ambari Infra Solr Plugin .. SKIPPED
> [INFO] Ambari Infra Solr Assembly  SKIPPED
> [INFO] Ambari Infra Manager .. SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 6:01.681s
> [INFO] Finished at: Wed May 10 19:58:42 UTC 2017
> [INFO] Final Memory: 21M/225M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> com.github.eirslett:frontend-maven-plugin:1.4:install-node-and-yarn (install 
> node and yarn) on project ambari-web: The plugin 
> com.github.eirslett:frontend-maven-plugin:1.4 requires Maven version 3.1.0 -> 
> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal com.github.eirslett:frontend-maven-plugin:1.4:install-node-and-yarn 
> (install node and yarn) on project ambari-web: The plugin 
> com.github.eirslett:frontend-maven-plugin:1.4 requires Maven version 3.1.0
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:170)
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at 
> org.apache.maven.lifecycle.internal.MojoEx

[jira] [Updated] (AMBARI-20983) ambari/dev-support/docker build is broken on trunk

[Michael Harp (JIRA)]

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

Michael Harp updated AMBARI-20983:
--
Attachment: AMBARI_20983.patch

> ambari/dev-support/docker build is broken on trunk
> --
>
> Key: AMBARI-20983
> URL: https://issues.apache.org/jira/browse/AMBARI-20983
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Michael Harp
>Assignee: Michael Harp
>Priority: Minor
>  Labels: docker
> Attachments: AMBARI_20983.patch
>
>
> Several issues need to be fixed to get the container working;
> 1. Version of maven needs to be updated
> 2. JDK should be version 7
> 3. Set bower flag to run as root in container
> {code}
> docker build -t ambari/build ./dev-support/docker/docker
> 
> [INFO] Reactor Summary:
> [INFO] 
> [INFO] Ambari Main ... SUCCESS [4:58.949s]
> [INFO] Apache Ambari Project POM . SUCCESS [6.050s]
> [INFO] Ambari Web  FAILURE [15.348s]
> [INFO] Ambari Views .. SKIPPED
> [INFO] Ambari Admin View . SKIPPED
> [INFO] utility ... SKIPPED
> [INFO] ambari-metrics  SKIPPED
> [INFO] Ambari Metrics Common . SKIPPED
> [INFO] Ambari Metrics Hadoop Sink  SKIPPED
> [INFO] Ambari Metrics Flume Sink . SKIPPED
> [INFO] Ambari Metrics Kafka Sink . SKIPPED
> [INFO] Ambari Metrics Storm Sink . SKIPPED
> [INFO] Ambari Metrics Storm Sink (Legacy)  SKIPPED
> [INFO] Ambari Metrics Collector .. SKIPPED
> [INFO] Ambari Metrics Monitor  SKIPPED
> [INFO] Ambari Metrics Grafana  SKIPPED
> [INFO] Ambari Metrics Assembly ... SKIPPED
> [INFO] Ambari Server . SKIPPED
> [INFO] Ambari Functional Tests ... SKIPPED
> [INFO] Ambari Agent .. SKIPPED
> [INFO] Ambari Client . SKIPPED
> [INFO] Ambari Python Client .. SKIPPED
> [INFO] Ambari Groovy Client .. SKIPPED
> [INFO] Ambari Shell .. SKIPPED
> [INFO] Ambari Python Shell ... SKIPPED
> [INFO] Ambari Groovy Shell ... SKIPPED
> [INFO] ambari-logsearch .. SKIPPED
> [INFO] Ambari Logsearch Appender . SKIPPED
> [INFO] Ambari Logsearch Config Api ... SKIPPED
> [INFO] Ambari Logsearch Config Zookeeper . SKIPPED
> [INFO] Ambari Logsearch Web .. SKIPPED
> [INFO] Ambari Logsearch Server ... SKIPPED
> [INFO] Ambari Logsearch Log Feeder ... SKIPPED
> [INFO] Ambari Logsearch Assembly . SKIPPED
> [INFO] Ambari Logsearch Integration Test . SKIPPED
> [INFO] ambari-infra .. SKIPPED
> [INFO] Ambari Infra Solr Client .. SKIPPED
> [INFO] Ambari Infra Solr Plugin .. SKIPPED
> [INFO] Ambari Infra Solr Assembly  SKIPPED
> [INFO] Ambari Infra Manager .. SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 6:01.681s
> [INFO] Finished at: Wed May 10 19:58:42 UTC 2017
> [INFO] Final Memory: 21M/225M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> com.github.eirslett:frontend-maven-plugin:1.4:install-node-and-yarn (install 
> node and yarn) on project ambari-web: The plugin 
> com.github.eirslett:frontend-maven-plugin:1.4 requires Maven version 3.1.0 -> 
> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal com.github.eirslett:frontend-maven-plugin:1.4:install-node-and-yarn 
> (install node and yarn) on project ambari-web: The plugin 
> com.github.eirslett:frontend-maven-plugin:1.4 requires Maven version 3.1.0
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:170)
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor

[jira] [Updated] (AMBARI-20974) Ambari fails to start due to NPE after installation of HDF mpack

[Madhuvanthi Radhakrishnan (JIRA)]

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

Madhuvanthi Radhakrishnan updated AMBARI-20974:
---
Attachment: AMBARI-20974_addendum.patch

> Ambari fails to start due to NPE after installation of HDF mpack
> 
>
> Key: AMBARI-20974
> URL: https://issues.apache.org/jira/browse/AMBARI-20974
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-sever
>Reporter: Madhuvanthi Radhakrishnan
>Assignee: Madhuvanthi Radhakrishnan
>Priority: Blocker
> Fix For: 2.5.1
>
> Attachments: AMBARI-20974_addendum.patch, AMBARI-20974_trunk.patch
>
>
> when we install HDF mpack we do the following steps
> yum install ambari-server
> ambari-server install-mpack --mpack=/path/to/hdf-mpack --purge --verbose
> ambari-server setup
> The permissions and ownership for stacks , common-services etc is set 
> correctly during ambari-server setup
> Ambari-server daemon is configured to run under user 'slava'. Change this 
> setting [y/n] (n)? n
> Adjusting ambari-server permissions and ownership...
> However, to add HDF services to HDP cluster we install the mpack after 
> deploying the HDP cluster and hence when running Ambari as non-root and with 
> umask = 0027, the permissions and ownerships don't get updated.
> Workaround:
> Re-run ambari-server setup command after installing the HDF mpack but don't 
> really make any config changes. Run this step only to update the permissions.
>  ambari-server setup -s



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

[jira] [Created] (AMBARI-20983) ambari/dev-support/docker build is broken on trunk

[Michael Harp (JIRA)]

Michael Harp created AMBARI-20983:
-

 Summary: ambari/dev-support/docker build is broken on trunk
 Key: AMBARI-20983
 URL: https://issues.apache.org/jira/browse/AMBARI-20983
 Project: Ambari
  Issue Type: Bug
Affects Versions: trunk
Reporter: Michael Harp
Assignee: Michael Harp
Priority: Minor


Several issues need to be fixed to get the container working;
1. Version of maven needs to be updated
2. JDK should be version 7
3. Set bower flag to run as root in container

{code}
docker build -t ambari/build ./dev-support/docker/docker

[INFO] Reactor Summary:
[INFO] 
[INFO] Ambari Main ... SUCCESS [4:58.949s]
[INFO] Apache Ambari Project POM . SUCCESS [6.050s]
[INFO] Ambari Web  FAILURE [15.348s]
[INFO] Ambari Views .. SKIPPED
[INFO] Ambari Admin View . SKIPPED
[INFO] utility ... SKIPPED
[INFO] ambari-metrics  SKIPPED
[INFO] Ambari Metrics Common . SKIPPED
[INFO] Ambari Metrics Hadoop Sink  SKIPPED
[INFO] Ambari Metrics Flume Sink . SKIPPED
[INFO] Ambari Metrics Kafka Sink . SKIPPED
[INFO] Ambari Metrics Storm Sink . SKIPPED
[INFO] Ambari Metrics Storm Sink (Legacy)  SKIPPED
[INFO] Ambari Metrics Collector .. SKIPPED
[INFO] Ambari Metrics Monitor  SKIPPED
[INFO] Ambari Metrics Grafana  SKIPPED
[INFO] Ambari Metrics Assembly ... SKIPPED
[INFO] Ambari Server . SKIPPED
[INFO] Ambari Functional Tests ... SKIPPED
[INFO] Ambari Agent .. SKIPPED
[INFO] Ambari Client . SKIPPED
[INFO] Ambari Python Client .. SKIPPED
[INFO] Ambari Groovy Client .. SKIPPED
[INFO] Ambari Shell .. SKIPPED
[INFO] Ambari Python Shell ... SKIPPED
[INFO] Ambari Groovy Shell ... SKIPPED
[INFO] ambari-logsearch .. SKIPPED
[INFO] Ambari Logsearch Appender . SKIPPED
[INFO] Ambari Logsearch Config Api ... SKIPPED
[INFO] Ambari Logsearch Config Zookeeper . SKIPPED
[INFO] Ambari Logsearch Web .. SKIPPED
[INFO] Ambari Logsearch Server ... SKIPPED
[INFO] Ambari Logsearch Log Feeder ... SKIPPED
[INFO] Ambari Logsearch Assembly . SKIPPED
[INFO] Ambari Logsearch Integration Test . SKIPPED
[INFO] ambari-infra .. SKIPPED
[INFO] Ambari Infra Solr Client .. SKIPPED
[INFO] Ambari Infra Solr Plugin .. SKIPPED
[INFO] Ambari Infra Solr Assembly  SKIPPED
[INFO] Ambari Infra Manager .. SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 6:01.681s
[INFO] Finished at: Wed May 10 19:58:42 UTC 2017
[INFO] Final Memory: 21M/225M
[INFO] 
[ERROR] Failed to execute goal 
com.github.eirslett:frontend-maven-plugin:1.4:install-node-and-yarn (install 
node and yarn) on project ambari-web: The plugin 
com.github.eirslett:frontend-maven-plugin:1.4 requires Maven version 3.1.0 -> 
[Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal 
com.github.eirslett:frontend-maven-plugin:1.4:install-node-and-yarn (install 
node and yarn) on project ambari-web: The plugin 
com.github.eirslett:frontend-maven-plugin:1.4 requires Maven version 3.1.0
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:170)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at 
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at 
org.apache.maven.lifecycle.internal.Lifec

[jira] [Updated] (AMBARI-20975) Add NIFI Admin Toolkit StackFeatures to HDP StackFeatures

[Madhuvanthi Radhakrishnan (JIRA)]

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

Madhuvanthi Radhakrishnan updated AMBARI-20975:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Add NIFI Admin Toolkit StackFeatures to HDP StackFeatures
> -
>
> Key: AMBARI-20975
> URL: https://issues.apache.org/jira/browse/AMBARI-20975
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Madhuvanthi Radhakrishnan
>Assignee: Madhuvanthi Radhakrishnan
>Priority: Blocker
> Fix For: 2.5.1
>
> Attachments: AMBARI-20975.patch
>
>
> Add to HDP stack_features.json
> {noformat}
> {
>"name": "admin_toolkit_support",
>"description": "Supports the nifi admin toolkit",
>"min_version": "3.0.0.0"
> },
>  {
>   "name": "tls_toolkit_san",
>   "description": "Support subject alternative name flag",
>   "min_version": "3.0.0.0"
> }
> {noformat}



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

[jira] [Updated] (AMBARI-20975) Add NIFI Admin Toolkit StackFeatures to HDP StackFeatures

[Madhuvanthi Radhakrishnan (JIRA)]

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

Madhuvanthi Radhakrishnan updated AMBARI-20975:
---
Priority: Blocker  (was: Major)

> Add NIFI Admin Toolkit StackFeatures to HDP StackFeatures
> -
>
> Key: AMBARI-20975
> URL: https://issues.apache.org/jira/browse/AMBARI-20975
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Madhuvanthi Radhakrishnan
>Assignee: Madhuvanthi Radhakrishnan
>Priority: Blocker
> Fix For: 2.5.1
>
> Attachments: AMBARI-20975.patch
>
>
> Add to HDP stack_features.json
> {noformat}
> {
>"name": "admin_toolkit_support",
>"description": "Supports the nifi admin toolkit",
>"min_version": "3.0.0.0"
> },
>  {
>   "name": "tls_toolkit_san",
>   "description": "Support subject alternative name flag",
>   "min_version": "3.0.0.0"
> }
> {noformat}



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

[jira] [Updated] (AMBARI-20974) Ambari fails to start due to NPE after installation of HDF mpack

[Madhuvanthi Radhakrishnan (JIRA)]

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

Madhuvanthi Radhakrishnan updated AMBARI-20974:
---
Priority: Blocker  (was: Major)

> Ambari fails to start due to NPE after installation of HDF mpack
> 
>
> Key: AMBARI-20974
> URL: https://issues.apache.org/jira/browse/AMBARI-20974
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-sever
>Reporter: Madhuvanthi Radhakrishnan
>Assignee: Madhuvanthi Radhakrishnan
>Priority: Blocker
> Fix For: 2.5.1
>
> Attachments: AMBARI-20974_trunk.patch
>
>
> when we install HDF mpack we do the following steps
> yum install ambari-server
> ambari-server install-mpack --mpack=/path/to/hdf-mpack --purge --verbose
> ambari-server setup
> The permissions and ownership for stacks , common-services etc is set 
> correctly during ambari-server setup
> Ambari-server daemon is configured to run under user 'slava'. Change this 
> setting [y/n] (n)? n
> Adjusting ambari-server permissions and ownership...
> However, to add HDF services to HDP cluster we install the mpack after 
> deploying the HDP cluster and hence when running Ambari as non-root and with 
> umask = 0027, the permissions and ownerships don't get updated.
> Workaround:
> Re-run ambari-server setup command after installing the HDF mpack but don't 
> really make any config changes. Run this step only to update the permissions.
>  ambari-server setup -s



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

[jira] [Updated] (AMBARI-20974) Ambari fails to start due to NPE after installation of HDF mpack

[Madhuvanthi Radhakrishnan (JIRA)]

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

Madhuvanthi Radhakrishnan updated AMBARI-20974:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Ambari fails to start due to NPE after installation of HDF mpack
> 
>
> Key: AMBARI-20974
> URL: https://issues.apache.org/jira/browse/AMBARI-20974
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-sever
>Reporter: Madhuvanthi Radhakrishnan
>Assignee: Madhuvanthi Radhakrishnan
>Priority: Blocker
> Fix For: 2.5.1
>
> Attachments: AMBARI-20974_trunk.patch
>
>
> when we install HDF mpack we do the following steps
> yum install ambari-server
> ambari-server install-mpack --mpack=/path/to/hdf-mpack --purge --verbose
> ambari-server setup
> The permissions and ownership for stacks , common-services etc is set 
> correctly during ambari-server setup
> Ambari-server daemon is configured to run under user 'slava'. Change this 
> setting [y/n] (n)? n
> Adjusting ambari-server permissions and ownership...
> However, to add HDF services to HDP cluster we install the mpack after 
> deploying the HDP cluster and hence when running Ambari as non-root and with 
> umask = 0027, the permissions and ownerships don't get updated.
> Workaround:
> Re-run ambari-server setup command after installing the HDF mpack but don't 
> really make any config changes. Run this step only to update the permissions.
>  ambari-server setup -s



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

[jira] [Commented] (AMBARI-20937) Ambari Upgrade to 2.5 fails due to custom service; rpm upgrade does not preserve the custom service directory

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20937:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7451 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/7451/])
AMBARI-20937. Ambari Upgrade to 2.5 fails due to custom service; rpm 
(vbrodetskyi: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=c12c320f81de6cfed34b5d913384fc3851b71f4a])
* (edit) ambari-server/src/main/python/ambari_server/serverUpgrade.py


> Ambari Upgrade to 2.5 fails due to custom service; rpm upgrade does not 
> preserve the custom service directory
> -
>
> Key: AMBARI-20937
> URL: https://issues.apache.org/jira/browse/AMBARI-20937
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-upgrade
>Affects Versions: 2.5.0
>Reporter: Derek Wood
>Assignee: Vitaly Brodetskyi
> Fix For: 2.5.1
>
> Attachments: AMBARI-20937.patch
>
>
> We have a 2.4.0.0 Ambari cluster, with HDP 2.5 and the custom service 
> definition for CDAP installed (source here: 
> https://github.com/caskdata/cdap-ambari-service).  When attempting to upgrade 
> to Ambari 2.5.0.3, the "ambari-server upgrade" command to upgrade the db 
> schema fails, apparently due to the existence of the custom service.  Is this 
> expected, and is there a workaround?
> Steps taken:
> 1. stop all cluster services
> 2. stop ambari 2.4 server and agents
> 3. yum upgrade the ambari packages
> 4. run the schema upgrade as below:
> {code}
> # ambari-server upgrade
> Using python  /usr/bin/python
> Upgrading ambari-server
> INFO: Upgrade Ambari Server
> INFO: Updating Ambari Server properties in ambari.properties ...
> INFO: Updating Ambari Server properties in ambari-env.sh ...
> WARNING: Original file ambari-env.sh kept
> INFO: Fixing database objects owner
> Ambari Server configured for Embedded Postgres. Confirm you have made a 
> backup of the Ambari Server database [y/n] (y)? y
> INFO: Upgrading database schema
> INFO: Return code from schema upgrade command, retcode = 1
> ERROR: Error executing schema upgrade, please check the server logs.
> ERROR: Error output from schema upgrade command:
> ERROR: Exception in thread "main" org.apache.ambari.server.AmbariException: 
> Guice provision errors:
> 1) Error injecting method, java.lang.RuntimeException: Trying to create a 
> ServiceComponent not recognized in stack info, clusterName=lamb-00022663, 
> serviceName=CDAP, componentName=CDAP_CLI, stackInfo=HDP-2.5
>   at 
> org.apache.ambari.server.state.cluster.ClustersImpl.loadClustersAndHosts(ClustersImpl.java:186)
>   at 
> org.apache.ambari.server.state.cluster.ClustersImpl.class(ClustersImpl.java:102)
>   while locating org.apache.ambari.server.state.cluster.ClustersImpl
>   while locating org.apache.ambari.server.state.Clusters
> for field at 
> org.apache.ambari.server.actionmanager.ActionDBAccessorImpl.clusters(ActionDBAccessorImpl.java:84)
>   at 
> org.apache.ambari.server.actionmanager.ActionDBAccessorImpl.class(ActionDBAccessorImpl.java:84)
>   while locating org.apache.ambari.server.actionmanager.ActionDBAccessorImpl
>   while locating org.apache.ambari.server.actionmanager.ActionDBAccessor
> for parameter 0 at 
> org.apache.ambari.server.actionmanager.ActionManager.(ActionManager.java:63)
>   at 
> org.apache.ambari.server.actionmanager.ActionManager.class(ActionManager.java:46)
>   while locating org.apache.ambari.server.actionmanager.ActionManager
> for parameter 0 at 
> org.apache.ambari.server.controller.AmbariManagementControllerImpl.(AmbariManagementControllerImpl.java:356)
>   at 
> org.apache.ambari.server.controller.AmbariManagementControllerImpl.class(AmbariManagementControllerImpl.java:226)
>   while locating 
> org.apache.ambari.server.controller.AmbariManagementControllerImpl
>   while locating 
> org.apache.ambari.server.controller.AmbariManagementController
> 1 error
>   at 
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:240)
>   at 
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:430)
> Caused by: com.google.inject.ProvisionException: Guice provision errors:
> 1) Error injecting method, java.lang.RuntimeException: Trying to create a 
> ServiceComponent not recognized in stack info, clusterName=lamb-00022663, 
> serviceName=CDAP, componentName=CDAP_CLI, stackInfo=HDP-2.5
>   at 
> org.apache.ambari.server.state.cluster.ClustersImpl.loadClustersAndHosts(ClustersImpl.java:186)
>   at 
> org.apache.ambari.server.state.cluster.ClustersImpl.class(ClustersImpl.java:102)
>   while locating org.apache.ambari.server.state.cluster.Clus

[jira] [Resolved] (AMBARI-15406) Enhance blueprints to export placeholder/token for password properties

[Amruta Borkar (JIRA)]

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

Amruta Borkar resolved AMBARI-15406.

Resolution: Unresolved

> Enhance blueprints to export placeholder/token for password properties
> --
>
> Key: AMBARI-15406
> URL: https://issues.apache.org/jira/browse/AMBARI-15406
> Project: Ambari
>  Issue Type: Technical task
>  Components: ambari-server, blueprints
>Affects Versions: 2.2.0
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Fix For: trunk
>
> Attachments: AMBARI-15406.patch, AMBARI-15406.patch, 
> AMBARI-15406.patch
>
>
> Secret References acting as tokens to password properties would be replaced 
> by user with appropriate passwords, 
> If any Secret references are found during cluster deployment with blueprint, 
> those will be replaced by default_password provided in blueprint template.



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

[jira] [Updated] (AMBARI-15406) Enhance blueprints to export placeholder/token for password properties

[Amruta Borkar (JIRA)]

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

Amruta Borkar updated AMBARI-15406:
---
Status: Open  (was: Patch Available)

> Enhance blueprints to export placeholder/token for password properties
> --
>
> Key: AMBARI-15406
> URL: https://issues.apache.org/jira/browse/AMBARI-15406
> Project: Ambari
>  Issue Type: Technical task
>  Components: ambari-server, blueprints
>Affects Versions: 2.2.0
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Fix For: trunk
>
> Attachments: AMBARI-15406.patch, AMBARI-15406.patch, 
> AMBARI-15406.patch
>
>
> Secret References acting as tokens to password properties would be replaced 
> by user with appropriate passwords, 
> If any Secret references are found during cluster deployment with blueprint, 
> those will be replaced by default_password provided in blueprint template.



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

[jira] [Resolved] (AMBARI-20192) HostCleaup.py throws exception and exits when hostcheck_custom_actions.result not present

[Amruta Borkar (JIRA)]

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

Amruta Borkar resolved AMBARI-20192.

Resolution: Invalid

> HostCleaup.py throws exception and exits when hostcheck_custom_actions.result 
> not present
> -
>
> Key: AMBARI-20192
> URL: https://issues.apache.org/jira/browse/AMBARI-20192
> Project: Ambari
>  Issue Type: Bug
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-20192.patch
>
>
> HostCleanup script throws following exception and exits when 
> hostcheck_custom_actions.result  not present
> [root@tsar1 ~]# /usr/lib/python2.6/site-packages/ambari_agent/HostCleanup.py
> You have elected to remove all users as well. If it is not intended then use 
> option --skip "users". Do you want to continue [y/n] (y)y
> Host Check results not found. There is no 
> /var/lib/ambari-agent/data/hostcheck_custom_actions.result. Do you want to 
> run host checks [y/n] (y)n
> Traceback (most recent call last):
>   File "/usr/lib/python2.6/site-packages/ambari_agent/HostCleanup.py", line 
> 705, in 
> main()
>   File "/usr/lib/python2.6/site-packages/ambari_agent/HostCleanup.py", line 
> 689, in main
> with open(hostcheckfileca, "rb") as f2:
> IOError: [Errno 2] No such file or directory: 
> '/var/lib/ambari-agent/data/hostcheck_custom_actions.result'



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

[jira] [Updated] (AMBARI-20192) HostCleaup.py throws exception and exits when hostcheck_custom_actions.result not present

[Amruta Borkar (JIRA)]

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

Amruta Borkar updated AMBARI-20192:
---
Status: Open  (was: Patch Available)

> HostCleaup.py throws exception and exits when hostcheck_custom_actions.result 
> not present
> -
>
> Key: AMBARI-20192
> URL: https://issues.apache.org/jira/browse/AMBARI-20192
> Project: Ambari
>  Issue Type: Bug
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-20192.patch
>
>
> HostCleanup script throws following exception and exits when 
> hostcheck_custom_actions.result  not present
> [root@tsar1 ~]# /usr/lib/python2.6/site-packages/ambari_agent/HostCleanup.py
> You have elected to remove all users as well. If it is not intended then use 
> option --skip "users". Do you want to continue [y/n] (y)y
> Host Check results not found. There is no 
> /var/lib/ambari-agent/data/hostcheck_custom_actions.result. Do you want to 
> run host checks [y/n] (y)n
> Traceback (most recent call last):
>   File "/usr/lib/python2.6/site-packages/ambari_agent/HostCleanup.py", line 
> 705, in 
> main()
>   File "/usr/lib/python2.6/site-packages/ambari_agent/HostCleanup.py", line 
> 689, in main
> with open(hostcheckfileca, "rb") as f2:
> IOError: [Errno 2] No such file or directory: 
> '/var/lib/ambari-agent/data/hostcheck_custom_actions.result'



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

[jira] [Commented] (AMBARI-20937) Ambari Upgrade to 2.5 fails due to custom service; rpm upgrade does not preserve the custom service directory

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20937:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1520 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/1520/])
AMBARI-20937. Ambari Upgrade to 2.5 fails due to custom service; rpm 
(vbrodetskyi: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=aa1d0047082663529b16dd9d08f8b4d7a7dd071d])
* (edit) ambari-server/src/main/python/ambari_server/serverUpgrade.py


> Ambari Upgrade to 2.5 fails due to custom service; rpm upgrade does not 
> preserve the custom service directory
> -
>
> Key: AMBARI-20937
> URL: https://issues.apache.org/jira/browse/AMBARI-20937
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-upgrade
>Affects Versions: 2.5.0
>Reporter: Derek Wood
>Assignee: Vitaly Brodetskyi
> Fix For: 2.5.1
>
> Attachments: AMBARI-20937.patch
>
>
> We have a 2.4.0.0 Ambari cluster, with HDP 2.5 and the custom service 
> definition for CDAP installed (source here: 
> https://github.com/caskdata/cdap-ambari-service).  When attempting to upgrade 
> to Ambari 2.5.0.3, the "ambari-server upgrade" command to upgrade the db 
> schema fails, apparently due to the existence of the custom service.  Is this 
> expected, and is there a workaround?
> Steps taken:
> 1. stop all cluster services
> 2. stop ambari 2.4 server and agents
> 3. yum upgrade the ambari packages
> 4. run the schema upgrade as below:
> {code}
> # ambari-server upgrade
> Using python  /usr/bin/python
> Upgrading ambari-server
> INFO: Upgrade Ambari Server
> INFO: Updating Ambari Server properties in ambari.properties ...
> INFO: Updating Ambari Server properties in ambari-env.sh ...
> WARNING: Original file ambari-env.sh kept
> INFO: Fixing database objects owner
> Ambari Server configured for Embedded Postgres. Confirm you have made a 
> backup of the Ambari Server database [y/n] (y)? y
> INFO: Upgrading database schema
> INFO: Return code from schema upgrade command, retcode = 1
> ERROR: Error executing schema upgrade, please check the server logs.
> ERROR: Error output from schema upgrade command:
> ERROR: Exception in thread "main" org.apache.ambari.server.AmbariException: 
> Guice provision errors:
> 1) Error injecting method, java.lang.RuntimeException: Trying to create a 
> ServiceComponent not recognized in stack info, clusterName=lamb-00022663, 
> serviceName=CDAP, componentName=CDAP_CLI, stackInfo=HDP-2.5
>   at 
> org.apache.ambari.server.state.cluster.ClustersImpl.loadClustersAndHosts(ClustersImpl.java:186)
>   at 
> org.apache.ambari.server.state.cluster.ClustersImpl.class(ClustersImpl.java:102)
>   while locating org.apache.ambari.server.state.cluster.ClustersImpl
>   while locating org.apache.ambari.server.state.Clusters
> for field at 
> org.apache.ambari.server.actionmanager.ActionDBAccessorImpl.clusters(ActionDBAccessorImpl.java:84)
>   at 
> org.apache.ambari.server.actionmanager.ActionDBAccessorImpl.class(ActionDBAccessorImpl.java:84)
>   while locating org.apache.ambari.server.actionmanager.ActionDBAccessorImpl
>   while locating org.apache.ambari.server.actionmanager.ActionDBAccessor
> for parameter 0 at 
> org.apache.ambari.server.actionmanager.ActionManager.(ActionManager.java:63)
>   at 
> org.apache.ambari.server.actionmanager.ActionManager.class(ActionManager.java:46)
>   while locating org.apache.ambari.server.actionmanager.ActionManager
> for parameter 0 at 
> org.apache.ambari.server.controller.AmbariManagementControllerImpl.(AmbariManagementControllerImpl.java:356)
>   at 
> org.apache.ambari.server.controller.AmbariManagementControllerImpl.class(AmbariManagementControllerImpl.java:226)
>   while locating 
> org.apache.ambari.server.controller.AmbariManagementControllerImpl
>   while locating 
> org.apache.ambari.server.controller.AmbariManagementController
> 1 error
>   at 
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:240)
>   at 
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:430)
> Caused by: com.google.inject.ProvisionException: Guice provision errors:
> 1) Error injecting method, java.lang.RuntimeException: Trying to create a 
> ServiceComponent not recognized in stack info, clusterName=lamb-00022663, 
> serviceName=CDAP, componentName=CDAP_CLI, stackInfo=HDP-2.5
>   at 
> org.apache.ambari.server.state.cluster.ClustersImpl.loadClustersAndHosts(ClustersImpl.java:186)
>   at 
> org.apache.ambari.server.state.cluster.ClustersImpl.class(ClustersImpl.java:102)
>   while locating org.apache.ambari.server.state.cluster.Clusters

[jira] [Resolved] (AMBARI-20971) Repository Resource Providers Should Expose the Repository ID by Default on Minimal Responses

[Jonathan Hurley (JIRA)]

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

Jonathan Hurley resolved AMBARI-20971.
--
Resolution: Fixed

> Repository Resource Providers Should Expose the Repository ID by Default on 
> Minimal Responses
> -
>
> Key: AMBARI-20971
> URL: https://issues.apache.org/jira/browse/AMBARI-20971
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
> Fix For: trunk
>
> Attachments: AMBARI-20971.patch
>
>
> There are 3 resource providers which should begin exposed the repository ID 
> by default on all responses, even minimal responses:
> - {{RepositoryResourceProvider}}
> - {{RespositoryVersionResourceProvider}}
> - {{CompatibleRepositoryVersionResourceProvider}}
> This will allow anyone querying these endpoints to reference a repository 
> uniquely, instead of by version.



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

[jira] [Updated] (AMBARI-20937) Ambari Upgrade to 2.5 fails due to custom service; rpm upgrade does not preserve the custom service directory

[Vitaly Brodetskyi (JIRA)]

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

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

Committed to trunk and branch-2.5

> Ambari Upgrade to 2.5 fails due to custom service; rpm upgrade does not 
> preserve the custom service directory
> -
>
> Key: AMBARI-20937
> URL: https://issues.apache.org/jira/browse/AMBARI-20937
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-upgrade
>Affects Versions: 2.5.0
>Reporter: Derek Wood
>Assignee: Vitaly Brodetskyi
> Fix For: 2.5.1
>
> Attachments: AMBARI-20937.patch
>
>
> We have a 2.4.0.0 Ambari cluster, with HDP 2.5 and the custom service 
> definition for CDAP installed (source here: 
> https://github.com/caskdata/cdap-ambari-service).  When attempting to upgrade 
> to Ambari 2.5.0.3, the "ambari-server upgrade" command to upgrade the db 
> schema fails, apparently due to the existence of the custom service.  Is this 
> expected, and is there a workaround?
> Steps taken:
> 1. stop all cluster services
> 2. stop ambari 2.4 server and agents
> 3. yum upgrade the ambari packages
> 4. run the schema upgrade as below:
> {code}
> # ambari-server upgrade
> Using python  /usr/bin/python
> Upgrading ambari-server
> INFO: Upgrade Ambari Server
> INFO: Updating Ambari Server properties in ambari.properties ...
> INFO: Updating Ambari Server properties in ambari-env.sh ...
> WARNING: Original file ambari-env.sh kept
> INFO: Fixing database objects owner
> Ambari Server configured for Embedded Postgres. Confirm you have made a 
> backup of the Ambari Server database [y/n] (y)? y
> INFO: Upgrading database schema
> INFO: Return code from schema upgrade command, retcode = 1
> ERROR: Error executing schema upgrade, please check the server logs.
> ERROR: Error output from schema upgrade command:
> ERROR: Exception in thread "main" org.apache.ambari.server.AmbariException: 
> Guice provision errors:
> 1) Error injecting method, java.lang.RuntimeException: Trying to create a 
> ServiceComponent not recognized in stack info, clusterName=lamb-00022663, 
> serviceName=CDAP, componentName=CDAP_CLI, stackInfo=HDP-2.5
>   at 
> org.apache.ambari.server.state.cluster.ClustersImpl.loadClustersAndHosts(ClustersImpl.java:186)
>   at 
> org.apache.ambari.server.state.cluster.ClustersImpl.class(ClustersImpl.java:102)
>   while locating org.apache.ambari.server.state.cluster.ClustersImpl
>   while locating org.apache.ambari.server.state.Clusters
> for field at 
> org.apache.ambari.server.actionmanager.ActionDBAccessorImpl.clusters(ActionDBAccessorImpl.java:84)
>   at 
> org.apache.ambari.server.actionmanager.ActionDBAccessorImpl.class(ActionDBAccessorImpl.java:84)
>   while locating org.apache.ambari.server.actionmanager.ActionDBAccessorImpl
>   while locating org.apache.ambari.server.actionmanager.ActionDBAccessor
> for parameter 0 at 
> org.apache.ambari.server.actionmanager.ActionManager.(ActionManager.java:63)
>   at 
> org.apache.ambari.server.actionmanager.ActionManager.class(ActionManager.java:46)
>   while locating org.apache.ambari.server.actionmanager.ActionManager
> for parameter 0 at 
> org.apache.ambari.server.controller.AmbariManagementControllerImpl.(AmbariManagementControllerImpl.java:356)
>   at 
> org.apache.ambari.server.controller.AmbariManagementControllerImpl.class(AmbariManagementControllerImpl.java:226)
>   while locating 
> org.apache.ambari.server.controller.AmbariManagementControllerImpl
>   while locating 
> org.apache.ambari.server.controller.AmbariManagementController
> 1 error
>   at 
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:240)
>   at 
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:430)
> Caused by: com.google.inject.ProvisionException: Guice provision errors:
> 1) Error injecting method, java.lang.RuntimeException: Trying to create a 
> ServiceComponent not recognized in stack info, clusterName=lamb-00022663, 
> serviceName=CDAP, componentName=CDAP_CLI, stackInfo=HDP-2.5
>   at 
> org.apache.ambari.server.state.cluster.ClustersImpl.loadClustersAndHosts(ClustersImpl.java:186)
>   at 
> org.apache.ambari.server.state.cluster.ClustersImpl.class(ClustersImpl.java:102)
>   while locating org.apache.ambari.server.state.cluster.ClustersImpl
>   while locating org.apache.ambari.server.state.Clusters
> for field at 
> org.apache.ambari.server.actionmanager.ActionDBAccessorImpl.clusters(ActionDBAccessorImpl.java:84)
>   at 
> org.apache.ambari.server.actionmanager.ActionDBAccessorImpl.class(ActionDBAccessorImpl.java:84)
>   while locating org.apa

[jira] [Updated] (AMBARI-20982) StackAdvisor error - Slider(Metastore Heap Size) has small range of value from 512 mb to 2048 mb [upgrade from 2.1.2.1 to 2.4]

[Dmytro Grinenko (JIRA)]

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

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

> StackAdvisor error - Slider(Metastore Heap Size) has small range of value 
> from 512 mb to 2048 mb [upgrade from 2.1.2.1 to 2.4]
> --
>
> Key: AMBARI-20982
> URL: https://issues.apache.org/jira/browse/AMBARI-20982
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Critical
> Fix For: 2.4.4
>
> Attachments: AMBARI-20982.patch
>
>
> {
>   "status" : 500,
>   "message" : "Stack Advisor reported an error: TypeError: 'NoneType' object 
> is unsubscriptable\nStdOut file: 
> /var/run/ambari-server/stack-recommendations/7/stackadvisor.out\n\nStdErr 
> file: /var/run/ambari-server/stack-recommendations/7/stackadvisor.err"
> }



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

[jira] [Commented] (AMBARI-20982) StackAdvisor error - Slider(Metastore Heap Size) has small range of value from 512 mb to 2048 mb [upgrade from 2.1.2.1 to 2.4]

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty commented on AMBARI-20982:


Patch looks good +1

> StackAdvisor error - Slider(Metastore Heap Size) has small range of value 
> from 512 mb to 2048 mb [upgrade from 2.1.2.1 to 2.4]
> --
>
> Key: AMBARI-20982
> URL: https://issues.apache.org/jira/browse/AMBARI-20982
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Critical
> Fix For: 2.4.4
>
> Attachments: AMBARI-20982.patch
>
>
> {
>   "status" : 500,
>   "message" : "Stack Advisor reported an error: TypeError: 'NoneType' object 
> is unsubscriptable\nStdOut file: 
> /var/run/ambari-server/stack-recommendations/7/stackadvisor.out\n\nStdErr 
> file: /var/run/ambari-server/stack-recommendations/7/stackadvisor.err"
> }



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

[jira] [Updated] (AMBARI-20982) StackAdvisor error - Slider(Metastore Heap Size) has small range of value from 512 mb to 2048 mb [upgrade from 2.1.2.1 to 2.4]

[Dmytro Grinenko (JIRA)]

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

Dmytro Grinenko updated AMBARI-20982:
-
Attachment: AMBARI-20982.patch

> StackAdvisor error - Slider(Metastore Heap Size) has small range of value 
> from 512 mb to 2048 mb [upgrade from 2.1.2.1 to 2.4]
> --
>
> Key: AMBARI-20982
> URL: https://issues.apache.org/jira/browse/AMBARI-20982
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Critical
> Fix For: 2.4.4
>
> Attachments: AMBARI-20982.patch
>
>
> {
>   "status" : 500,
>   "message" : "Stack Advisor reported an error: TypeError: 'NoneType' object 
> is unsubscriptable\nStdOut file: 
> /var/run/ambari-server/stack-recommendations/7/stackadvisor.out\n\nStdErr 
> file: /var/run/ambari-server/stack-recommendations/7/stackadvisor.err"
> }



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

[jira] [Created] (AMBARI-20982) StackAdvisor error - Slider(Metastore Heap Size) has small range of value from 512 mb to 2048 mb [upgrade from 2.1.2.1 to 2.4]

[Dmytro Grinenko (JIRA)]

Dmytro Grinenko created AMBARI-20982:


 Summary: StackAdvisor error - Slider(Metastore Heap Size) has 
small range of value from 512 mb to 2048 mb [upgrade from 2.1.2.1 to 2.4]
 Key: AMBARI-20982
 URL: https://issues.apache.org/jira/browse/AMBARI-20982
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: trunk, 2.4.0
Reporter: Dmytro Grinenko
Assignee: Dmytro Grinenko
Priority: Critical
 Fix For: 2.4.4


{
  "status" : 500,
  "message" : "Stack Advisor reported an error: TypeError: 'NoneType' object is 
unsubscriptable\nStdOut file: 
/var/run/ambari-server/stack-recommendations/7/stackadvisor.out\n\nStdErr file: 
/var/run/ambari-server/stack-recommendations/7/stackadvisor.err"
}



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

[jira] [Updated] (AMBARI-20968) Pig and CapSched views are not loading in 2.4.3

[Sumit Mohanty (JIRA)]

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

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

> Pig and CapSched views are not loading in 2.4.3
> ---
>
> Key: AMBARI-20968
> URL: https://issues.apache.org/jira/browse/AMBARI-20968
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.4.3
>Reporter: Akhil PB
>Assignee: Akhil PB
>Priority: Blocker
>  Labels: system_test
> Fix For: 2.4.4
>
> Attachments: AMBARI-20968-branch-2.4.patch
>
>
> After "ember-precompile-brunch" package has been changed from "1.5.1" to 
> "0.1.0", ember fails to resolve view templates results in pig and capsched 
> views fails to render and goes blank. This patch adds custom resolver to fix 
> the issue.
> Pig and Cap sched views are not loading :
> Cap Sched : 
> https://172.22.106.180:8443/#/main/views/CAPACITY-SCHEDULER/1.0.0/AUTO_CS_INSTANCE
> Pig : https://172.22.106.180:8443/#/main/views/PIG/1.0.0/Pig
> Pig View error:
> {code:java}
> ember.js:15373 Error while processing route: splash Assertion Failed: Could 
> not find "splash" template or view. Error: Assertion Failed: Could not find 
> "splash" template or view.
> at EmberError 
> (https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:30819:23)
> at Object.Ember.assert 
> (https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:20433:15)
> at Class.render 
> (https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:41957:17)
> at Class.renderTemplate 
> (https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/app.js:3438:10)
> at apply 
> (https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:36242:27)
> at Class.superWrapper [as renderTemplate] 
> (https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:35813:15)
> at Class.setup 
> (https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:41223:16)
> at applyHook 
> (https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:63552:30)
> at callHook 
> (https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:63546:14)
> at handlerEnteredOrUpdated 
> (https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:62306:7)
> {code}



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

[jira] [Updated] (AMBARI-20968) Pig and CapSched views are not loading in 2.4.3

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-20968:
---
Fix Version/s: (was: 2.4.3)
   2.4.4

> Pig and CapSched views are not loading in 2.4.3
> ---
>
> Key: AMBARI-20968
> URL: https://issues.apache.org/jira/browse/AMBARI-20968
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.4.3
>Reporter: Akhil PB
>Assignee: Akhil PB
>Priority: Blocker
>  Labels: system_test
> Fix For: 2.4.4
>
> Attachments: AMBARI-20968-branch-2.4.patch
>
>
> After "ember-precompile-brunch" package has been changed from "1.5.1" to 
> "0.1.0", ember fails to resolve view templates results in pig and capsched 
> views fails to render and goes blank. This patch adds custom resolver to fix 
> the issue.
> Pig and Cap sched views are not loading :
> Cap Sched : 
> https://172.22.106.180:8443/#/main/views/CAPACITY-SCHEDULER/1.0.0/AUTO_CS_INSTANCE
> Pig : https://172.22.106.180:8443/#/main/views/PIG/1.0.0/Pig
> Pig View error:
> {code:java}
> ember.js:15373 Error while processing route: splash Assertion Failed: Could 
> not find "splash" template or view. Error: Assertion Failed: Could not find 
> "splash" template or view.
> at EmberError 
> (https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:30819:23)
> at Object.Ember.assert 
> (https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:20433:15)
> at Class.render 
> (https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:41957:17)
> at Class.renderTemplate 
> (https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/app.js:3438:10)
> at apply 
> (https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:36242:27)
> at Class.superWrapper [as renderTemplate] 
> (https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:35813:15)
> at Class.setup 
> (https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:41223:16)
> at applyHook 
> (https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:63552:30)
> at callHook 
> (https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:63546:14)
> at handlerEnteredOrUpdated 
> (https://172.22.106.182:8443/views/PIG/1.0.0/PIG/static/javascripts/vendor.js:62306:7)
> {code}



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

[jira] [Updated] (AMBARI-20937) Ambari Upgrade to 2.5 fails due to custom service; rpm upgrade does not preserve the custom service directory

[Vitaly Brodetskyi (JIRA)]

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

Vitaly Brodetskyi updated AMBARI-20937:
---
Fix Version/s: 2.5.1

> Ambari Upgrade to 2.5 fails due to custom service; rpm upgrade does not 
> preserve the custom service directory
> -
>
> Key: AMBARI-20937
> URL: https://issues.apache.org/jira/browse/AMBARI-20937
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-upgrade
>Affects Versions: 2.5.0
>Reporter: Derek Wood
>Assignee: Vitaly Brodetskyi
> Fix For: 2.5.1
>
> Attachments: AMBARI-20937.patch
>
>
> We have a 2.4.0.0 Ambari cluster, with HDP 2.5 and the custom service 
> definition for CDAP installed (source here: 
> https://github.com/caskdata/cdap-ambari-service).  When attempting to upgrade 
> to Ambari 2.5.0.3, the "ambari-server upgrade" command to upgrade the db 
> schema fails, apparently due to the existence of the custom service.  Is this 
> expected, and is there a workaround?
> Steps taken:
> 1. stop all cluster services
> 2. stop ambari 2.4 server and agents
> 3. yum upgrade the ambari packages
> 4. run the schema upgrade as below:
> {code}
> # ambari-server upgrade
> Using python  /usr/bin/python
> Upgrading ambari-server
> INFO: Upgrade Ambari Server
> INFO: Updating Ambari Server properties in ambari.properties ...
> INFO: Updating Ambari Server properties in ambari-env.sh ...
> WARNING: Original file ambari-env.sh kept
> INFO: Fixing database objects owner
> Ambari Server configured for Embedded Postgres. Confirm you have made a 
> backup of the Ambari Server database [y/n] (y)? y
> INFO: Upgrading database schema
> INFO: Return code from schema upgrade command, retcode = 1
> ERROR: Error executing schema upgrade, please check the server logs.
> ERROR: Error output from schema upgrade command:
> ERROR: Exception in thread "main" org.apache.ambari.server.AmbariException: 
> Guice provision errors:
> 1) Error injecting method, java.lang.RuntimeException: Trying to create a 
> ServiceComponent not recognized in stack info, clusterName=lamb-00022663, 
> serviceName=CDAP, componentName=CDAP_CLI, stackInfo=HDP-2.5
>   at 
> org.apache.ambari.server.state.cluster.ClustersImpl.loadClustersAndHosts(ClustersImpl.java:186)
>   at 
> org.apache.ambari.server.state.cluster.ClustersImpl.class(ClustersImpl.java:102)
>   while locating org.apache.ambari.server.state.cluster.ClustersImpl
>   while locating org.apache.ambari.server.state.Clusters
> for field at 
> org.apache.ambari.server.actionmanager.ActionDBAccessorImpl.clusters(ActionDBAccessorImpl.java:84)
>   at 
> org.apache.ambari.server.actionmanager.ActionDBAccessorImpl.class(ActionDBAccessorImpl.java:84)
>   while locating org.apache.ambari.server.actionmanager.ActionDBAccessorImpl
>   while locating org.apache.ambari.server.actionmanager.ActionDBAccessor
> for parameter 0 at 
> org.apache.ambari.server.actionmanager.ActionManager.(ActionManager.java:63)
>   at 
> org.apache.ambari.server.actionmanager.ActionManager.class(ActionManager.java:46)
>   while locating org.apache.ambari.server.actionmanager.ActionManager
> for parameter 0 at 
> org.apache.ambari.server.controller.AmbariManagementControllerImpl.(AmbariManagementControllerImpl.java:356)
>   at 
> org.apache.ambari.server.controller.AmbariManagementControllerImpl.class(AmbariManagementControllerImpl.java:226)
>   while locating 
> org.apache.ambari.server.controller.AmbariManagementControllerImpl
>   while locating 
> org.apache.ambari.server.controller.AmbariManagementController
> 1 error
>   at 
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:240)
>   at 
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:430)
> Caused by: com.google.inject.ProvisionException: Guice provision errors:
> 1) Error injecting method, java.lang.RuntimeException: Trying to create a 
> ServiceComponent not recognized in stack info, clusterName=lamb-00022663, 
> serviceName=CDAP, componentName=CDAP_CLI, stackInfo=HDP-2.5
>   at 
> org.apache.ambari.server.state.cluster.ClustersImpl.loadClustersAndHosts(ClustersImpl.java:186)
>   at 
> org.apache.ambari.server.state.cluster.ClustersImpl.class(ClustersImpl.java:102)
>   while locating org.apache.ambari.server.state.cluster.ClustersImpl
>   while locating org.apache.ambari.server.state.Clusters
> for field at 
> org.apache.ambari.server.actionmanager.ActionDBAccessorImpl.clusters(ActionDBAccessorImpl.java:84)
>   at 
> org.apache.ambari.server.actionmanager.ActionDBAccessorImpl.class(ActionDBAccessorImpl.java:84)
>   while locating org.apache.ambari.server.actionmanager.ActionDBAccessorImpl
>   while locating org.apach

[jira] [Commented] (AMBARI-20972) Workflow Designer View: Provide sorting of workflows on dashboard

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-20972:


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

{color:red}-1 patch{color}.  Top-level [trunk 
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/11580//artifact/patch-work/trunkJavacWarnings.txt]
 may be broken.

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

This message is automatically generated.

> Workflow Designer View: Provide sorting of workflows on dashboard
> -
>
> Key: AMBARI-20972
> URL: https://issues.apache.org/jira/browse/AMBARI-20972
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: trunk
>Reporter: Anita Gnanamalar Jebaraj
>Assignee: Anita Gnanamalar Jebaraj
>  Labels: WFD, WFM
> Fix For: trunk
>
> Attachments: AMBARI-20972.patch, wfmSort.PNG
>
>
> The workflows displayed on the worflow designer view dashboard are not 
> sortable. The ability to sort via Name, Status, User, Created Time, End Time 
> and jobId should be included



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

[jira] [Updated] (AMBARI-20972) Workflow Designer View: Provide sorting of workflows on dashboard

[Anita Gnanamalar Jebaraj (JIRA)]

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

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

> Workflow Designer View: Provide sorting of workflows on dashboard
> -
>
> Key: AMBARI-20972
> URL: https://issues.apache.org/jira/browse/AMBARI-20972
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: trunk
>Reporter: Anita Gnanamalar Jebaraj
>Assignee: Anita Gnanamalar Jebaraj
>  Labels: WFD, WFM
> Fix For: trunk
>
> Attachments: AMBARI-20972.patch, wfmSort.PNG
>
>
> The workflows displayed on the worflow designer view dashboard are not 
> sortable. The ability to sort via Name, Status, User, Created Time, End Time 
> and jobId should be included



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

[jira] [Updated] (AMBARI-20972) Workflow Designer View: Provide sorting of workflows on dashboard

[Anita Gnanamalar Jebaraj (JIRA)]

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

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

> Workflow Designer View: Provide sorting of workflows on dashboard
> -
>
> Key: AMBARI-20972
> URL: https://issues.apache.org/jira/browse/AMBARI-20972
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: trunk
>Reporter: Anita Gnanamalar Jebaraj
>Assignee: Anita Gnanamalar Jebaraj
>  Labels: WFD, WFM
> Fix For: trunk
>
> Attachments: AMBARI-20972.patch, wfmSort.PNG
>
>
> The workflows displayed on the worflow designer view dashboard are not 
> sortable. The ability to sort via Name, Status, User, Created Time, End Time 
> and jobId should be included



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

[jira] [Updated] (AMBARI-20972) Workflow Designer View: Provide sorting of workflows on dashboard

[Anita Gnanamalar Jebaraj (JIRA)]

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

Anita Gnanamalar Jebaraj updated AMBARI-20972:
--
Attachment: (was: AMBARI-20972.patch)

> Workflow Designer View: Provide sorting of workflows on dashboard
> -
>
> Key: AMBARI-20972
> URL: https://issues.apache.org/jira/browse/AMBARI-20972
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: trunk
>Reporter: Anita Gnanamalar Jebaraj
>Assignee: Anita Gnanamalar Jebaraj
>  Labels: WFD, WFM
> Fix For: trunk
>
> Attachments: AMBARI-20972.patch, wfmSort.PNG
>
>
> The workflows displayed on the worflow designer view dashboard are not 
> sortable. The ability to sort via Name, Status, User, Created Time, End Time 
> and jobId should be included



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

[jira] [Updated] (AMBARI-20972) Workflow Designer View: Provide sorting of workflows on dashboard

[Anita Gnanamalar Jebaraj (JIRA)]

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

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

> Workflow Designer View: Provide sorting of workflows on dashboard
> -
>
> Key: AMBARI-20972
> URL: https://issues.apache.org/jira/browse/AMBARI-20972
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: trunk
>Reporter: Anita Gnanamalar Jebaraj
>Assignee: Anita Gnanamalar Jebaraj
>  Labels: WFD, WFM
> Fix For: trunk
>
> Attachments: AMBARI-20972.patch, wfmSort.PNG
>
>
> The workflows displayed on the worflow designer view dashboard are not 
> sortable. The ability to sort via Name, Status, User, Created Time, End Time 
> and jobId should be included



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

[jira] [Updated] (AMBARI-18766) Add Service failed when none of the host components report version

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-18766:
---
Fix Version/s: (was: 2.4.4)

> Add Service failed when none of the host components report version
> --
>
> Key: AMBARI-18766
> URL: https://issues.apache.org/jira/browse/AMBARI-18766
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Sumit Mohanty
>Assignee: Jaimin Jetly
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18766.2.patch, AMBARI-18766.patch
>
>
> When the underlying packages do not support versioned layout or do not report 
> version (basically distro-select is not supported) then the stack version 
> associated with the cluster is not changed to CURRENT from INIT.
> This blocks the UI from discovering the stack version associated with the 
> cluster. UI instead should simply rely on the stack version that is specified 
> in the cluster resource.
> *Cluster resource* ("version": "ODPi-1.0")
> {code}
> {
> "href": "http://c6402.ambari.apache.org:8080/api/v1/clusters/c1";,
> "Clusters": {
> "cluster_id": 2,
> "cluster_name": "c1",
> "health_report": {
> "Host/stale_config": 1,
> "Host/maintenance_state": 0,
> "Host/host_status/ALERT": 0
> },
> "provisioning_state": "INSTALLED",
> "security_type": "NONE",
> "total_hosts": 1,
> "version": "ODPi-1.0",
> {code}
> *stack_version resource* ("state": "INIT")
> {code}
> {
> "href": 
> "http://c6402.ambari.apache.org:8080/api/v1/clusters/c1/stack_versions/1";,
> "ClusterStackVersions": {
> "cluster_name": "c1",
> "id": 1,
> "repository_version": 1,
> "stack": "ODPi",
> "state": "INIT",
> "version": "1.0",
> "host_states": {
> "CURRENT": [],
> "INIT": [],
> "INSTALLED": [],
> "INSTALLING": [],
> "INSTALL_FAILED": [],
> {code}



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

[jira] [Updated] (AMBARI-18766) Add Service failed when none of the host components report version

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty updated AMBARI-18766:
---
Fix Version/s: 2.4.4

> Add Service failed when none of the host components report version
> --
>
> Key: AMBARI-18766
> URL: https://issues.apache.org/jira/browse/AMBARI-18766
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Sumit Mohanty
>Assignee: Jaimin Jetly
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18766.2.patch, AMBARI-18766.patch
>
>
> When the underlying packages do not support versioned layout or do not report 
> version (basically distro-select is not supported) then the stack version 
> associated with the cluster is not changed to CURRENT from INIT.
> This blocks the UI from discovering the stack version associated with the 
> cluster. UI instead should simply rely on the stack version that is specified 
> in the cluster resource.
> *Cluster resource* ("version": "ODPi-1.0")
> {code}
> {
> "href": "http://c6402.ambari.apache.org:8080/api/v1/clusters/c1";,
> "Clusters": {
> "cluster_id": 2,
> "cluster_name": "c1",
> "health_report": {
> "Host/stale_config": 1,
> "Host/maintenance_state": 0,
> "Host/host_status/ALERT": 0
> },
> "provisioning_state": "INSTALLED",
> "security_type": "NONE",
> "total_hosts": 1,
> "version": "ODPi-1.0",
> {code}
> *stack_version resource* ("state": "INIT")
> {code}
> {
> "href": 
> "http://c6402.ambari.apache.org:8080/api/v1/clusters/c1/stack_versions/1";,
> "ClusterStackVersions": {
> "cluster_name": "c1",
> "id": 1,
> "repository_version": 1,
> "stack": "ODPi",
> "state": "INIT",
> "version": "1.0",
> "host_states": {
> "CURRENT": [],
> "INIT": [],
> "INSTALLED": [],
> "INSTALLING": [],
> "INSTALL_FAILED": [],
> {code}



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

[jira] [Commented] (AMBARI-20972) Workflow Designer View: Provide sorting of workflows on dashboard

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-20972:


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

This message is automatically generated.

> Workflow Designer View: Provide sorting of workflows on dashboard
> -
>
> Key: AMBARI-20972
> URL: https://issues.apache.org/jira/browse/AMBARI-20972
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: trunk
>Reporter: Anita Gnanamalar Jebaraj
>Assignee: Anita Gnanamalar Jebaraj
>  Labels: WFD, WFM
> Fix For: trunk
>
> Attachments: AMBARI-20972.patch, wfmSort.PNG
>
>
> The workflows displayed on the worflow designer view dashboard are not 
> sortable. The ability to sort via Name, Status, User, Created Time, End Time 
> and jobId should be included



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

[jira] [Updated] (AMBARI-20972) Workflow Designer View: Provide sorting of workflows on dashboard

[Anita Gnanamalar Jebaraj (JIRA)]

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

Anita Gnanamalar Jebaraj updated AMBARI-20972:
--
Affects Version/s: (was: 2.5.0)
   trunk

> Workflow Designer View: Provide sorting of workflows on dashboard
> -
>
> Key: AMBARI-20972
> URL: https://issues.apache.org/jira/browse/AMBARI-20972
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: trunk
>Reporter: Anita Gnanamalar Jebaraj
>Assignee: Anita Gnanamalar Jebaraj
>  Labels: WFD, WFM
> Fix For: trunk
>
> Attachments: AMBARI-20972.patch, wfmSort.PNG
>
>
> The workflows displayed on the worflow designer view dashboard are not 
> sortable. The ability to sort via Name, Status, User, Created Time, End Time 
> and jobId should be included



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

[jira] [Updated] (AMBARI-20972) Workflow Designer View: Provide sorting of workflows on dashboard

[Anita Gnanamalar Jebaraj (JIRA)]

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

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

> Workflow Designer View: Provide sorting of workflows on dashboard
> -
>
> Key: AMBARI-20972
> URL: https://issues.apache.org/jira/browse/AMBARI-20972
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: trunk
>Reporter: Anita Gnanamalar Jebaraj
>Assignee: Anita Gnanamalar Jebaraj
>  Labels: WFD, WFM
> Fix For: trunk
>
> Attachments: AMBARI-20972.patch, wfmSort.PNG
>
>
> The workflows displayed on the worflow designer view dashboard are not 
> sortable. The ability to sort via Name, Status, User, Created Time, End Time 
> and jobId should be included



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

[jira] [Updated] (AMBARI-20972) Workflow Designer View: Provide sorting of workflows on dashboard

[Anita Gnanamalar Jebaraj (JIRA)]

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

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

> Workflow Designer View: Provide sorting of workflows on dashboard
> -
>
> Key: AMBARI-20972
> URL: https://issues.apache.org/jira/browse/AMBARI-20972
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: trunk
>Reporter: Anita Gnanamalar Jebaraj
>Assignee: Anita Gnanamalar Jebaraj
>  Labels: WFD, WFM
> Fix For: trunk
>
> Attachments: AMBARI-20972.patch, wfmSort.PNG
>
>
> The workflows displayed on the worflow designer view dashboard are not 
> sortable. The ability to sort via Name, Status, User, Created Time, End Time 
> and jobId should be included



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

[jira] [Updated] (AMBARI-20972) Workflow Designer View: Provide sorting of workflows on dashboard

[Anita Gnanamalar Jebaraj (JIRA)]

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

Anita Gnanamalar Jebaraj updated AMBARI-20972:
--
Labels: WFD WFM  (was: )

> Workflow Designer View: Provide sorting of workflows on dashboard
> -
>
> Key: AMBARI-20972
> URL: https://issues.apache.org/jira/browse/AMBARI-20972
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Anita Gnanamalar Jebaraj
>Assignee: Anita Gnanamalar Jebaraj
>  Labels: WFD, WFM
> Fix For: trunk
>
> Attachments: AMBARI-20972.patch, wfmSort.PNG
>
>
> The workflows displayed on the worflow designer view dashboard are not 
> sortable. The ability to sort via Name, Status, User, Created Time, End Time 
> and jobId should be included



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

[jira] [Commented] (AMBARI-20978) Ambari 3.0: Outstanding new components issues

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20978:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7450 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/7450/])
AMBARI-20978 Ambari 3.0: Outstanding new components issues. (atkach) (atkach: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=506b84768581311d944b57cbd270ee3b96613b65])
* (edit) ambari-web/app/styles/theme/bootstrap-ambari.css
* (edit) ambari-web/app/styles/wizard.less


> Ambari 3.0: Outstanding new components issues
> -
>
> Key: AMBARI-20978
> URL: https://issues.apache.org/jira/browse/AMBARI-20978
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: 2. create widget checkbox.png, 2. step1 checkbox.png, 3. 
> disabled area too dark .png, 3. step2 disabled too dark and eye catching.png, 
> 4. modal button border.png, 4. modal button.png, AMBARI-20978.patch, Disabled 
> fields.png, dropdown select color 1.png
>
>
> The following issues are related new style guide components:
> * Checkbox: some checkboxes are not centered. see attached (effected places: 
> installer step 1, create widget step 3, and user settings do not show 
> background ops checkbox)
> * Input: disabled area is too prominent, too dark. see attached. 
> * Modal: some modal primary button has a blk border, should remove that. 
> * Dropdown: on hovering each option, the background should be dark and text 
> should be white. 



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

[jira] [Commented] (AMBARI-20979) Outstanding Alerts UI issues

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20979:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7450 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/7450/])
AMBARI-20979. Outstanding Alerts UI issues (akovalenko) (akovalenko: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4595f00b0ec6bfd86eb8270d3af2f6876080a84f])
* (edit) ambari-web/app/controllers/main/service/info/summary.js
* (edit) ambari-web/app/styles/alerts.less
* (edit) ambari-web/app/templates/main/alerts.hbs
* (edit) ambari-web/app/styles/top-nav.less


> Outstanding Alerts UI issues
> 
>
> Key: AMBARI-20979
> URL: https://issues.apache.org/jira/browse/AMBARI-20979
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-20979.patch
>
>
> Following are the outstanding issues with Alerts:
> Alerts table on alerts page:
> * Status labels (# of hosts) shoud be the first column.
> On the Ambari top bar:
> * Alert number indicator: 1-2 digits, should be round. 3+ digits, shoud be a 
> pill/ellipse shape. 
> Alerts popup on services page:
> * Hide the horizontal scrollbar. The info should be nicely fitted into the 
> popup window, scroll bar is useless. 



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

[jira] [Updated] (AMBARI-20937) Ambari Upgrade to 2.5 fails due to custom service; rpm upgrade does not preserve the custom service directory

[Vitaly Brodetskyi (JIRA)]

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

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

> Ambari Upgrade to 2.5 fails due to custom service; rpm upgrade does not 
> preserve the custom service directory
> -
>
> Key: AMBARI-20937
> URL: https://issues.apache.org/jira/browse/AMBARI-20937
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-upgrade
>Affects Versions: 2.5.0
>Reporter: Derek Wood
>Assignee: Vitaly Brodetskyi
> Attachments: AMBARI-20937.patch
>
>
> We have a 2.4.0.0 Ambari cluster, with HDP 2.5 and the custom service 
> definition for CDAP installed (source here: 
> https://github.com/caskdata/cdap-ambari-service).  When attempting to upgrade 
> to Ambari 2.5.0.3, the "ambari-server upgrade" command to upgrade the db 
> schema fails, apparently due to the existence of the custom service.  Is this 
> expected, and is there a workaround?
> Steps taken:
> 1. stop all cluster services
> 2. stop ambari 2.4 server and agents
> 3. yum upgrade the ambari packages
> 4. run the schema upgrade as below:
> {code}
> # ambari-server upgrade
> Using python  /usr/bin/python
> Upgrading ambari-server
> INFO: Upgrade Ambari Server
> INFO: Updating Ambari Server properties in ambari.properties ...
> INFO: Updating Ambari Server properties in ambari-env.sh ...
> WARNING: Original file ambari-env.sh kept
> INFO: Fixing database objects owner
> Ambari Server configured for Embedded Postgres. Confirm you have made a 
> backup of the Ambari Server database [y/n] (y)? y
> INFO: Upgrading database schema
> INFO: Return code from schema upgrade command, retcode = 1
> ERROR: Error executing schema upgrade, please check the server logs.
> ERROR: Error output from schema upgrade command:
> ERROR: Exception in thread "main" org.apache.ambari.server.AmbariException: 
> Guice provision errors:
> 1) Error injecting method, java.lang.RuntimeException: Trying to create a 
> ServiceComponent not recognized in stack info, clusterName=lamb-00022663, 
> serviceName=CDAP, componentName=CDAP_CLI, stackInfo=HDP-2.5
>   at 
> org.apache.ambari.server.state.cluster.ClustersImpl.loadClustersAndHosts(ClustersImpl.java:186)
>   at 
> org.apache.ambari.server.state.cluster.ClustersImpl.class(ClustersImpl.java:102)
>   while locating org.apache.ambari.server.state.cluster.ClustersImpl
>   while locating org.apache.ambari.server.state.Clusters
> for field at 
> org.apache.ambari.server.actionmanager.ActionDBAccessorImpl.clusters(ActionDBAccessorImpl.java:84)
>   at 
> org.apache.ambari.server.actionmanager.ActionDBAccessorImpl.class(ActionDBAccessorImpl.java:84)
>   while locating org.apache.ambari.server.actionmanager.ActionDBAccessorImpl
>   while locating org.apache.ambari.server.actionmanager.ActionDBAccessor
> for parameter 0 at 
> org.apache.ambari.server.actionmanager.ActionManager.(ActionManager.java:63)
>   at 
> org.apache.ambari.server.actionmanager.ActionManager.class(ActionManager.java:46)
>   while locating org.apache.ambari.server.actionmanager.ActionManager
> for parameter 0 at 
> org.apache.ambari.server.controller.AmbariManagementControllerImpl.(AmbariManagementControllerImpl.java:356)
>   at 
> org.apache.ambari.server.controller.AmbariManagementControllerImpl.class(AmbariManagementControllerImpl.java:226)
>   while locating 
> org.apache.ambari.server.controller.AmbariManagementControllerImpl
>   while locating 
> org.apache.ambari.server.controller.AmbariManagementController
> 1 error
>   at 
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:240)
>   at 
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:430)
> Caused by: com.google.inject.ProvisionException: Guice provision errors:
> 1) Error injecting method, java.lang.RuntimeException: Trying to create a 
> ServiceComponent not recognized in stack info, clusterName=lamb-00022663, 
> serviceName=CDAP, componentName=CDAP_CLI, stackInfo=HDP-2.5
>   at 
> org.apache.ambari.server.state.cluster.ClustersImpl.loadClustersAndHosts(ClustersImpl.java:186)
>   at 
> org.apache.ambari.server.state.cluster.ClustersImpl.class(ClustersImpl.java:102)
>   while locating org.apache.ambari.server.state.cluster.ClustersImpl
>   while locating org.apache.ambari.server.state.Clusters
> for field at 
> org.apache.ambari.server.actionmanager.ActionDBAccessorImpl.clusters(ActionDBAccessorImpl.java:84)
>   at 
> org.apache.ambari.server.actionmanager.ActionDBAccessorImpl.class(ActionDBAccessorImpl.java:84)
>   while locating org.apache.ambari.server.actionmanager.ActionDBAccessorImpl
>   while locating org.apache.ambari.server

[jira] [Updated] (AMBARI-20937) Ambari Upgrade to 2.5 fails due to custom service; rpm upgrade does not preserve the custom service directory

[Vitaly Brodetskyi (JIRA)]

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

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

> Ambari Upgrade to 2.5 fails due to custom service; rpm upgrade does not 
> preserve the custom service directory
> -
>
> Key: AMBARI-20937
> URL: https://issues.apache.org/jira/browse/AMBARI-20937
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-upgrade
>Affects Versions: 2.5.0
>Reporter: Derek Wood
>Assignee: Vitaly Brodetskyi
> Attachments: AMBARI-20937.patch
>
>
> We have a 2.4.0.0 Ambari cluster, with HDP 2.5 and the custom service 
> definition for CDAP installed (source here: 
> https://github.com/caskdata/cdap-ambari-service).  When attempting to upgrade 
> to Ambari 2.5.0.3, the "ambari-server upgrade" command to upgrade the db 
> schema fails, apparently due to the existence of the custom service.  Is this 
> expected, and is there a workaround?
> Steps taken:
> 1. stop all cluster services
> 2. stop ambari 2.4 server and agents
> 3. yum upgrade the ambari packages
> 4. run the schema upgrade as below:
> {code}
> # ambari-server upgrade
> Using python  /usr/bin/python
> Upgrading ambari-server
> INFO: Upgrade Ambari Server
> INFO: Updating Ambari Server properties in ambari.properties ...
> INFO: Updating Ambari Server properties in ambari-env.sh ...
> WARNING: Original file ambari-env.sh kept
> INFO: Fixing database objects owner
> Ambari Server configured for Embedded Postgres. Confirm you have made a 
> backup of the Ambari Server database [y/n] (y)? y
> INFO: Upgrading database schema
> INFO: Return code from schema upgrade command, retcode = 1
> ERROR: Error executing schema upgrade, please check the server logs.
> ERROR: Error output from schema upgrade command:
> ERROR: Exception in thread "main" org.apache.ambari.server.AmbariException: 
> Guice provision errors:
> 1) Error injecting method, java.lang.RuntimeException: Trying to create a 
> ServiceComponent not recognized in stack info, clusterName=lamb-00022663, 
> serviceName=CDAP, componentName=CDAP_CLI, stackInfo=HDP-2.5
>   at 
> org.apache.ambari.server.state.cluster.ClustersImpl.loadClustersAndHosts(ClustersImpl.java:186)
>   at 
> org.apache.ambari.server.state.cluster.ClustersImpl.class(ClustersImpl.java:102)
>   while locating org.apache.ambari.server.state.cluster.ClustersImpl
>   while locating org.apache.ambari.server.state.Clusters
> for field at 
> org.apache.ambari.server.actionmanager.ActionDBAccessorImpl.clusters(ActionDBAccessorImpl.java:84)
>   at 
> org.apache.ambari.server.actionmanager.ActionDBAccessorImpl.class(ActionDBAccessorImpl.java:84)
>   while locating org.apache.ambari.server.actionmanager.ActionDBAccessorImpl
>   while locating org.apache.ambari.server.actionmanager.ActionDBAccessor
> for parameter 0 at 
> org.apache.ambari.server.actionmanager.ActionManager.(ActionManager.java:63)
>   at 
> org.apache.ambari.server.actionmanager.ActionManager.class(ActionManager.java:46)
>   while locating org.apache.ambari.server.actionmanager.ActionManager
> for parameter 0 at 
> org.apache.ambari.server.controller.AmbariManagementControllerImpl.(AmbariManagementControllerImpl.java:356)
>   at 
> org.apache.ambari.server.controller.AmbariManagementControllerImpl.class(AmbariManagementControllerImpl.java:226)
>   while locating 
> org.apache.ambari.server.controller.AmbariManagementControllerImpl
>   while locating 
> org.apache.ambari.server.controller.AmbariManagementController
> 1 error
>   at 
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:240)
>   at 
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:430)
> Caused by: com.google.inject.ProvisionException: Guice provision errors:
> 1) Error injecting method, java.lang.RuntimeException: Trying to create a 
> ServiceComponent not recognized in stack info, clusterName=lamb-00022663, 
> serviceName=CDAP, componentName=CDAP_CLI, stackInfo=HDP-2.5
>   at 
> org.apache.ambari.server.state.cluster.ClustersImpl.loadClustersAndHosts(ClustersImpl.java:186)
>   at 
> org.apache.ambari.server.state.cluster.ClustersImpl.class(ClustersImpl.java:102)
>   while locating org.apache.ambari.server.state.cluster.ClustersImpl
>   while locating org.apache.ambari.server.state.Clusters
> for field at 
> org.apache.ambari.server.actionmanager.ActionDBAccessorImpl.clusters(ActionDBAccessorImpl.java:84)
>   at 
> org.apache.ambari.server.actionmanager.ActionDBAccessorImpl.class(ActionDBAccessorImpl.java:84)
>   while locating org.apache.ambari.server.actionmanager.ActionDBAccessorImpl
>   while locating org.apache.ambari.server.actio

[jira] [Assigned] (AMBARI-20937) Ambari Upgrade to 2.5 fails due to custom service; rpm upgrade does not preserve the custom service directory

[Vitaly Brodetskyi (JIRA)]

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

Vitaly Brodetskyi reassigned AMBARI-20937:
--

Assignee: Vitaly Brodetskyi

> Ambari Upgrade to 2.5 fails due to custom service; rpm upgrade does not 
> preserve the custom service directory
> -
>
> Key: AMBARI-20937
> URL: https://issues.apache.org/jira/browse/AMBARI-20937
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-upgrade
>Affects Versions: 2.5.0
>Reporter: Derek Wood
>Assignee: Vitaly Brodetskyi
>
> We have a 2.4.0.0 Ambari cluster, with HDP 2.5 and the custom service 
> definition for CDAP installed (source here: 
> https://github.com/caskdata/cdap-ambari-service).  When attempting to upgrade 
> to Ambari 2.5.0.3, the "ambari-server upgrade" command to upgrade the db 
> schema fails, apparently due to the existence of the custom service.  Is this 
> expected, and is there a workaround?
> Steps taken:
> 1. stop all cluster services
> 2. stop ambari 2.4 server and agents
> 3. yum upgrade the ambari packages
> 4. run the schema upgrade as below:
> {code}
> # ambari-server upgrade
> Using python  /usr/bin/python
> Upgrading ambari-server
> INFO: Upgrade Ambari Server
> INFO: Updating Ambari Server properties in ambari.properties ...
> INFO: Updating Ambari Server properties in ambari-env.sh ...
> WARNING: Original file ambari-env.sh kept
> INFO: Fixing database objects owner
> Ambari Server configured for Embedded Postgres. Confirm you have made a 
> backup of the Ambari Server database [y/n] (y)? y
> INFO: Upgrading database schema
> INFO: Return code from schema upgrade command, retcode = 1
> ERROR: Error executing schema upgrade, please check the server logs.
> ERROR: Error output from schema upgrade command:
> ERROR: Exception in thread "main" org.apache.ambari.server.AmbariException: 
> Guice provision errors:
> 1) Error injecting method, java.lang.RuntimeException: Trying to create a 
> ServiceComponent not recognized in stack info, clusterName=lamb-00022663, 
> serviceName=CDAP, componentName=CDAP_CLI, stackInfo=HDP-2.5
>   at 
> org.apache.ambari.server.state.cluster.ClustersImpl.loadClustersAndHosts(ClustersImpl.java:186)
>   at 
> org.apache.ambari.server.state.cluster.ClustersImpl.class(ClustersImpl.java:102)
>   while locating org.apache.ambari.server.state.cluster.ClustersImpl
>   while locating org.apache.ambari.server.state.Clusters
> for field at 
> org.apache.ambari.server.actionmanager.ActionDBAccessorImpl.clusters(ActionDBAccessorImpl.java:84)
>   at 
> org.apache.ambari.server.actionmanager.ActionDBAccessorImpl.class(ActionDBAccessorImpl.java:84)
>   while locating org.apache.ambari.server.actionmanager.ActionDBAccessorImpl
>   while locating org.apache.ambari.server.actionmanager.ActionDBAccessor
> for parameter 0 at 
> org.apache.ambari.server.actionmanager.ActionManager.(ActionManager.java:63)
>   at 
> org.apache.ambari.server.actionmanager.ActionManager.class(ActionManager.java:46)
>   while locating org.apache.ambari.server.actionmanager.ActionManager
> for parameter 0 at 
> org.apache.ambari.server.controller.AmbariManagementControllerImpl.(AmbariManagementControllerImpl.java:356)
>   at 
> org.apache.ambari.server.controller.AmbariManagementControllerImpl.class(AmbariManagementControllerImpl.java:226)
>   while locating 
> org.apache.ambari.server.controller.AmbariManagementControllerImpl
>   while locating 
> org.apache.ambari.server.controller.AmbariManagementController
> 1 error
>   at 
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:240)
>   at 
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:430)
> Caused by: com.google.inject.ProvisionException: Guice provision errors:
> 1) Error injecting method, java.lang.RuntimeException: Trying to create a 
> ServiceComponent not recognized in stack info, clusterName=lamb-00022663, 
> serviceName=CDAP, componentName=CDAP_CLI, stackInfo=HDP-2.5
>   at 
> org.apache.ambari.server.state.cluster.ClustersImpl.loadClustersAndHosts(ClustersImpl.java:186)
>   at 
> org.apache.ambari.server.state.cluster.ClustersImpl.class(ClustersImpl.java:102)
>   while locating org.apache.ambari.server.state.cluster.ClustersImpl
>   while locating org.apache.ambari.server.state.Clusters
> for field at 
> org.apache.ambari.server.actionmanager.ActionDBAccessorImpl.clusters(ActionDBAccessorImpl.java:84)
>   at 
> org.apache.ambari.server.actionmanager.ActionDBAccessorImpl.class(ActionDBAccessorImpl.java:84)
>   while locating org.apache.ambari.server.actionmanager.ActionDBAccessorImpl
>   while locating org.apache.ambari.server.actionmanager.ActionDBAccessor
> for para

[jira] [Updated] (AMBARI-20981) Hive20 View Table Statistics overflows Integer Type convert to Long

[Greg Senia (JIRA)]

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

Greg Senia updated AMBARI-20981:

Component/s: contrib

> Hive20 View Table Statistics overflows Integer Type convert to Long
> ---
>
> Key: AMBARI-20981
> URL: https://issues.apache.org/jira/browse/AMBARI-20981
> Project: Ambari
>  Issue Type: Bug
>  Components: contrib
>Affects Versions: 2.5.0, 2.5.1, 2.5.2
> Environment: Ambari 2.5.0.x
>Reporter: Greg Senia
>  Labels: views
> Attachments: AMBARI-20981.patch
>
>
> When testing with our extremely large datasets the statistics data returns a 
> failure and the following stack trace. Using Integer for Hive Table Stats 
> unfortunately is not going to work. It needs to be a long. I've provided a 
> patch to fix this.
> 09 May 2017 10:24:34,474 ERROR [ambari-client-thread-55044] 
> ContainerResponse:419 - The RuntimeException could not be mapped to a 
> response, re-throwing to the HT
> TP container
> java.lang.NumberFormatException: For input string: "12375183159"
> at 
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.lang.Integer.parseInt(Integer.java:583)
> at java.lang.Integer.valueOf(Integer.java:766)
> at 
> org.apache.ambari.view.hive20.internal.parsers.TableMetaParserImpl.getTableStats(TableMetaParserImpl.java:115)
> at 
> org.apache.ambari.view.hive20.internal.parsers.TableMetaParserImpl.parse(TableMetaParserImpl.java:62)
> at 
> org.apache.ambari.view.hive20.resources.browser.DDLProxy.getTableProperties(DDLProxy.java:157)
> at 
> org.apache.ambari.view.hive20.resources.browser.DDLService.getTableInfo(DDLService.java:278)
> at sun.reflect.GeneratedMethodAccessor253.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
> at 
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
> at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
> at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
> at 
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)
> at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHand

[jira] [Updated] (AMBARI-20981) Hive 2.0 View Table Statistics overflows Integer Type convert to Long

[Greg Senia (JIRA)]

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

Greg Senia updated AMBARI-20981:

Summary: Hive 2.0 View Table Statistics overflows Integer Type convert to 
Long  (was: Hive20 View Table Statistics overflows Integer Type convert to Long)

> Hive 2.0 View Table Statistics overflows Integer Type convert to Long
> -
>
> Key: AMBARI-20981
> URL: https://issues.apache.org/jira/browse/AMBARI-20981
> Project: Ambari
>  Issue Type: Bug
>  Components: contrib
>Affects Versions: 2.5.0, 2.5.1, 2.5.2
> Environment: Ambari 2.5.0.x
>Reporter: Greg Senia
>  Labels: views
> Attachments: AMBARI-20981.patch
>
>
> When testing with our extremely large datasets the statistics data returns a 
> failure and the following stack trace. Using Integer for Hive Table Stats 
> unfortunately is not going to work. It needs to be a long. I've provided a 
> patch to fix this.
> 09 May 2017 10:24:34,474 ERROR [ambari-client-thread-55044] 
> ContainerResponse:419 - The RuntimeException could not be mapped to a 
> response, re-throwing to the HT
> TP container
> java.lang.NumberFormatException: For input string: "12375183159"
> at 
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.lang.Integer.parseInt(Integer.java:583)
> at java.lang.Integer.valueOf(Integer.java:766)
> at 
> org.apache.ambari.view.hive20.internal.parsers.TableMetaParserImpl.getTableStats(TableMetaParserImpl.java:115)
> at 
> org.apache.ambari.view.hive20.internal.parsers.TableMetaParserImpl.parse(TableMetaParserImpl.java:62)
> at 
> org.apache.ambari.view.hive20.resources.browser.DDLProxy.getTableProperties(DDLProxy.java:157)
> at 
> org.apache.ambari.view.hive20.resources.browser.DDLService.getTableInfo(DDLService.java:278)
> at sun.reflect.GeneratedMethodAccessor253.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
> at 
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
> at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
> at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
> at 
> org.eclipse.jetty.ser

[jira] [Updated] (AMBARI-20981) Hive20 View Table Statistics overflows Integer Type convert to Long

[Greg Senia (JIRA)]

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

Greg Senia updated AMBARI-20981:

Labels: views  (was: )

> Hive20 View Table Statistics overflows Integer Type convert to Long
> ---
>
> Key: AMBARI-20981
> URL: https://issues.apache.org/jira/browse/AMBARI-20981
> Project: Ambari
>  Issue Type: Bug
>  Components: contrib
>Affects Versions: 2.5.0, 2.5.1, 2.5.2
> Environment: Ambari 2.5.0.x
>Reporter: Greg Senia
>  Labels: views
> Attachments: AMBARI-20981.patch
>
>
> When testing with our extremely large datasets the statistics data returns a 
> failure and the following stack trace. Using Integer for Hive Table Stats 
> unfortunately is not going to work. It needs to be a long. I've provided a 
> patch to fix this.
> 09 May 2017 10:24:34,474 ERROR [ambari-client-thread-55044] 
> ContainerResponse:419 - The RuntimeException could not be mapped to a 
> response, re-throwing to the HT
> TP container
> java.lang.NumberFormatException: For input string: "12375183159"
> at 
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.lang.Integer.parseInt(Integer.java:583)
> at java.lang.Integer.valueOf(Integer.java:766)
> at 
> org.apache.ambari.view.hive20.internal.parsers.TableMetaParserImpl.getTableStats(TableMetaParserImpl.java:115)
> at 
> org.apache.ambari.view.hive20.internal.parsers.TableMetaParserImpl.parse(TableMetaParserImpl.java:62)
> at 
> org.apache.ambari.view.hive20.resources.browser.DDLProxy.getTableProperties(DDLProxy.java:157)
> at 
> org.apache.ambari.view.hive20.resources.browser.DDLService.getTableInfo(DDLService.java:278)
> at sun.reflect.GeneratedMethodAccessor253.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
> at 
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
> at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
> at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
> at 
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)
> at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHa

[jira] [Updated] (AMBARI-20970) Integrate StackService resource and it's subresources with swagger

[Doroszlai, Attila (JIRA)]

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

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

Committed to 
[ambari-rest-api-explorer|http://git-wip-us.apache.org/repos/asf/ambari/commit/54983ee3].

> Integrate StackService resource and it's subresources with swagger
> --
>
> Key: AMBARI-20970
> URL: https://issues.apache.org/jira/browse/AMBARI-20970
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Balázs Bence Sári
>Assignee: Balázs Bence Sári
> Fix For: 3.0.0
>
> Attachments: AMBARI-20970-Stacks-API_v3.patch
>
>




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

[jira] [Updated] (AMBARI-20981) Hive20 View Table Statistics overflows Integer Type convert to Long

[Greg Senia (JIRA)]

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

Greg Senia updated AMBARI-20981:

Affects Version/s: 2.5.0

> Hive20 View Table Statistics overflows Integer Type convert to Long
> ---
>
> Key: AMBARI-20981
> URL: https://issues.apache.org/jira/browse/AMBARI-20981
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.0, 2.5.1, 2.5.2
> Environment: Ambari 2.5.0.x
>Reporter: Greg Senia
> Attachments: AMBARI-20981.patch
>
>
> When testing with our extremely large datasets the statistics data returns a 
> failure and the following stack trace. Using Integer for Hive Table Stats 
> unfortunately is not going to work. It needs to be a long. I've provided a 
> patch to fix this.
> 09 May 2017 10:24:34,474 ERROR [ambari-client-thread-55044] 
> ContainerResponse:419 - The RuntimeException could not be mapped to a 
> response, re-throwing to the HT
> TP container
> java.lang.NumberFormatException: For input string: "12375183159"
> at 
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.lang.Integer.parseInt(Integer.java:583)
> at java.lang.Integer.valueOf(Integer.java:766)
> at 
> org.apache.ambari.view.hive20.internal.parsers.TableMetaParserImpl.getTableStats(TableMetaParserImpl.java:115)
> at 
> org.apache.ambari.view.hive20.internal.parsers.TableMetaParserImpl.parse(TableMetaParserImpl.java:62)
> at 
> org.apache.ambari.view.hive20.resources.browser.DDLProxy.getTableProperties(DDLProxy.java:157)
> at 
> org.apache.ambari.view.hive20.resources.browser.DDLService.getTableInfo(DDLService.java:278)
> at sun.reflect.GeneratedMethodAccessor253.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
> at 
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
> at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
> at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
> at 
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)
> at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1507)
> at 
> org.springframework.secur

[jira] [Commented] (AMBARI-20981) Hive20 View Table Statistics overflows Integer Type convert to Long

[Greg Senia (JIRA)]

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

Greg Senia commented on AMBARI-20981:
-

Example of sample code I wrote showing that you cannot use Integer with Hive 
View long is safer value to use specifically since Hadoop handles large 
datasets.

MaxInt: 2147483647
MaxLong: 9223372036854775807
StringVersionofNumber: 4819276224
Long Value: 4819276224
Cannot Convert Large String Value to Integer 4819276224 > MaxInt: 2147483647
java.lang.NumberFormatException: For input string: "4819276224"
at 
java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.lang.Integer.parseInt(Integer.java:583)
at java.lang.Integer.valueOf(Integer.java:766)
at sample_test.IntLongTest.main(IntLongTest.java:15)

> Hive20 View Table Statistics overflows Integer Type convert to Long
> ---
>
> Key: AMBARI-20981
> URL: https://issues.apache.org/jira/browse/AMBARI-20981
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.1, 2.5.2
> Environment: Ambari 2.5.0.x
>Reporter: Greg Senia
> Attachments: AMBARI-20981.patch
>
>
> When testing with our extremely large datasets the statistics data returns a 
> failure and the following stack trace. Using Integer for Hive Table Stats 
> unfortunately is not going to work. It needs to be a long. I've provided a 
> patch to fix this.
> 09 May 2017 10:24:34,474 ERROR [ambari-client-thread-55044] 
> ContainerResponse:419 - The RuntimeException could not be mapped to a 
> response, re-throwing to the HT
> TP container
> java.lang.NumberFormatException: For input string: "12375183159"
> at 
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.lang.Integer.parseInt(Integer.java:583)
> at java.lang.Integer.valueOf(Integer.java:766)
> at 
> org.apache.ambari.view.hive20.internal.parsers.TableMetaParserImpl.getTableStats(TableMetaParserImpl.java:115)
> at 
> org.apache.ambari.view.hive20.internal.parsers.TableMetaParserImpl.parse(TableMetaParserImpl.java:62)
> at 
> org.apache.ambari.view.hive20.resources.browser.DDLProxy.getTableProperties(DDLProxy.java:157)
> at 
> org.apache.ambari.view.hive20.resources.browser.DDLService.getTableInfo(DDLService.java:278)
> at sun.reflect.GeneratedMethodAccessor253.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at 
> com.sun.jersey.server.i

[jira] [Updated] (AMBARI-20978) Ambari 3.0: Outstanding new components issues

[Andrii Tkach (JIRA)]

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

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

> Ambari 3.0: Outstanding new components issues
> -
>
> Key: AMBARI-20978
> URL: https://issues.apache.org/jira/browse/AMBARI-20978
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: 2. create widget checkbox.png, 2. step1 checkbox.png, 3. 
> disabled area too dark .png, 3. step2 disabled too dark and eye catching.png, 
> 4. modal button border.png, 4. modal button.png, AMBARI-20978.patch, Disabled 
> fields.png, dropdown select color 1.png
>
>
> The following issues are related new style guide components:
> * Checkbox: some checkboxes are not centered. see attached (effected places: 
> installer step 1, create widget step 3, and user settings do not show 
> background ops checkbox)
> * Input: disabled area is too prominent, too dark. see attached. 
> * Modal: some modal primary button has a blk border, should remove that. 
> * Dropdown: on hovering each option, the background should be dark and text 
> should be white. 



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

[jira] [Commented] (AMBARI-20978) Ambari 3.0: Outstanding new components issues

[Andrii Tkach (JIRA)]

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

Andrii Tkach commented on AMBARI-20978:
---

committed to trunk

> Ambari 3.0: Outstanding new components issues
> -
>
> Key: AMBARI-20978
> URL: https://issues.apache.org/jira/browse/AMBARI-20978
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: 2. create widget checkbox.png, 2. step1 checkbox.png, 3. 
> disabled area too dark .png, 3. step2 disabled too dark and eye catching.png, 
> 4. modal button border.png, 4. modal button.png, AMBARI-20978.patch, Disabled 
> fields.png, dropdown select color 1.png
>
>
> The following issues are related new style guide components:
> * Checkbox: some checkboxes are not centered. see attached (effected places: 
> installer step 1, create widget step 3, and user settings do not show 
> background ops checkbox)
> * Input: disabled area is too prominent, too dark. see attached. 
> * Modal: some modal primary button has a blk border, should remove that. 
> * Dropdown: on hovering each option, the background should be dark and text 
> should be white. 



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

[jira] [Commented] (AMBARI-20978) Ambari 3.0: Outstanding new components issues

[Aleksandr Kovalenko (JIRA)]

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

Aleksandr Kovalenko commented on AMBARI-20978:
--

+1 for the patch

> Ambari 3.0: Outstanding new components issues
> -
>
> Key: AMBARI-20978
> URL: https://issues.apache.org/jira/browse/AMBARI-20978
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: 2. create widget checkbox.png, 2. step1 checkbox.png, 3. 
> disabled area too dark .png, 3. step2 disabled too dark and eye catching.png, 
> 4. modal button border.png, 4. modal button.png, AMBARI-20978.patch, Disabled 
> fields.png, dropdown select color 1.png
>
>
> The following issues are related new style guide components:
> * Checkbox: some checkboxes are not centered. see attached (effected places: 
> installer step 1, create widget step 3, and user settings do not show 
> background ops checkbox)
> * Input: disabled area is too prominent, too dark. see attached. 
> * Modal: some modal primary button has a blk border, should remove that. 
> * Dropdown: on hovering each option, the background should be dark and text 
> should be white. 



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

[jira] [Updated] (AMBARI-20981) Hive 20 View Table Statistics overflows Integer Type convert to Long

[Greg Senia (JIRA)]

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

Greg Senia updated AMBARI-20981:

Attachment: AMBARI-20981.patch

> Hive 20 View Table Statistics overflows Integer Type convert to Long
> 
>
> Key: AMBARI-20981
> URL: https://issues.apache.org/jira/browse/AMBARI-20981
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.1, 2.5.2
> Environment: Ambari 2.5.0.x
>Reporter: Greg Senia
> Attachments: AMBARI-20981.patch
>
>
> When testing with our extremely large datasets the statistics data returns a 
> failure and the following stack trace. Using Integer for Hive Table Stats 
> unfortunately is not going to work. It needs to be a long. I've provided a 
> patch to fix this.
> 09 May 2017 10:24:34,474 ERROR [ambari-client-thread-55044] 
> ContainerResponse:419 - The RuntimeException could not be mapped to a 
> response, re-throwing to the HT
> TP container
> java.lang.NumberFormatException: For input string: "12375183159"
> at 
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.lang.Integer.parseInt(Integer.java:583)
> at java.lang.Integer.valueOf(Integer.java:766)
> at 
> org.apache.ambari.view.hive20.internal.parsers.TableMetaParserImpl.getTableStats(TableMetaParserImpl.java:115)
> at 
> org.apache.ambari.view.hive20.internal.parsers.TableMetaParserImpl.parse(TableMetaParserImpl.java:62)
> at 
> org.apache.ambari.view.hive20.resources.browser.DDLProxy.getTableProperties(DDLProxy.java:157)
> at 
> org.apache.ambari.view.hive20.resources.browser.DDLService.getTableInfo(DDLService.java:278)
> at sun.reflect.GeneratedMethodAccessor253.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
> at 
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
> at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
> at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
> at 
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)
> at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1507)
> at 
> org.springframework.secu

[jira] [Updated] (AMBARI-20981) Hive 20 View Table Statistics overflows Integer Type convert to Long

[Greg Senia (JIRA)]

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

Greg Senia updated AMBARI-20981:

Affects Version/s: 2.5.2
   2.5.1
   Status: Patch Available  (was: Open)

> Hive 20 View Table Statistics overflows Integer Type convert to Long
> 
>
> Key: AMBARI-20981
> URL: https://issues.apache.org/jira/browse/AMBARI-20981
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.1, 2.5.2
> Environment: Ambari 2.5.0.x
>Reporter: Greg Senia
> Attachments: AMBARI-20981.patch
>
>
> When testing with our extremely large datasets the statistics data returns a 
> failure and the following stack trace. Using Integer for Hive Table Stats 
> unfortunately is not going to work. It needs to be a long. I've provided a 
> patch to fix this.
> 09 May 2017 10:24:34,474 ERROR [ambari-client-thread-55044] 
> ContainerResponse:419 - The RuntimeException could not be mapped to a 
> response, re-throwing to the HT
> TP container
> java.lang.NumberFormatException: For input string: "12375183159"
> at 
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.lang.Integer.parseInt(Integer.java:583)
> at java.lang.Integer.valueOf(Integer.java:766)
> at 
> org.apache.ambari.view.hive20.internal.parsers.TableMetaParserImpl.getTableStats(TableMetaParserImpl.java:115)
> at 
> org.apache.ambari.view.hive20.internal.parsers.TableMetaParserImpl.parse(TableMetaParserImpl.java:62)
> at 
> org.apache.ambari.view.hive20.resources.browser.DDLProxy.getTableProperties(DDLProxy.java:157)
> at 
> org.apache.ambari.view.hive20.resources.browser.DDLService.getTableInfo(DDLService.java:278)
> at sun.reflect.GeneratedMethodAccessor253.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
> at 
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
> at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
> at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
> at 
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)
> at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.

[jira] [Updated] (AMBARI-20981) Hive20 View Table Statistics overflows Integer Type convert to Long

[Greg Senia (JIRA)]

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

Greg Senia updated AMBARI-20981:

Summary: Hive20 View Table Statistics overflows Integer Type convert to 
Long  (was: Hive 20 View Table Statistics overflows Integer Type convert to 
Long)

> Hive20 View Table Statistics overflows Integer Type convert to Long
> ---
>
> Key: AMBARI-20981
> URL: https://issues.apache.org/jira/browse/AMBARI-20981
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.1, 2.5.2
> Environment: Ambari 2.5.0.x
>Reporter: Greg Senia
> Attachments: AMBARI-20981.patch
>
>
> When testing with our extremely large datasets the statistics data returns a 
> failure and the following stack trace. Using Integer for Hive Table Stats 
> unfortunately is not going to work. It needs to be a long. I've provided a 
> patch to fix this.
> 09 May 2017 10:24:34,474 ERROR [ambari-client-thread-55044] 
> ContainerResponse:419 - The RuntimeException could not be mapped to a 
> response, re-throwing to the HT
> TP container
> java.lang.NumberFormatException: For input string: "12375183159"
> at 
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.lang.Integer.parseInt(Integer.java:583)
> at java.lang.Integer.valueOf(Integer.java:766)
> at 
> org.apache.ambari.view.hive20.internal.parsers.TableMetaParserImpl.getTableStats(TableMetaParserImpl.java:115)
> at 
> org.apache.ambari.view.hive20.internal.parsers.TableMetaParserImpl.parse(TableMetaParserImpl.java:62)
> at 
> org.apache.ambari.view.hive20.resources.browser.DDLProxy.getTableProperties(DDLProxy.java:157)
> at 
> org.apache.ambari.view.hive20.resources.browser.DDLService.getTableInfo(DDLService.java:278)
> at sun.reflect.GeneratedMethodAccessor253.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at 
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
> at 
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
> at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
> at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
> at 
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)
> at 
> org.e

[jira] [Created] (AMBARI-20981) Hive 20 View Table Statistics overflows Integer Type convert to Long

[Greg Senia (JIRA)]

Greg Senia created AMBARI-20981:
---

 Summary: Hive 20 View Table Statistics overflows Integer Type 
convert to Long
 Key: AMBARI-20981
 URL: https://issues.apache.org/jira/browse/AMBARI-20981
 Project: Ambari
  Issue Type: Bug
 Environment: Ambari 2.5.0.x
Reporter: Greg Senia


When testing with our extremely large datasets the statistics data returns a 
failure and the following stack trace. Using Integer for Hive Table Stats 
unfortunately is not going to work. It needs to be a long. I've provided a 
patch to fix this.


09 May 2017 10:24:34,474 ERROR [ambari-client-thread-55044] 
ContainerResponse:419 - The RuntimeException could not be mapped to a response, 
re-throwing to the HT
TP container
java.lang.NumberFormatException: For input string: "12375183159"
at 
java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.lang.Integer.parseInt(Integer.java:583)
at java.lang.Integer.valueOf(Integer.java:766)
at 
org.apache.ambari.view.hive20.internal.parsers.TableMetaParserImpl.getTableStats(TableMetaParserImpl.java:115)
at 
org.apache.ambari.view.hive20.internal.parsers.TableMetaParserImpl.parse(TableMetaParserImpl.java:62)
at 
org.apache.ambari.view.hive20.resources.browser.DDLProxy.getTableProperties(DDLProxy.java:157)
at 
org.apache.ambari.view.hive20.resources.browser.DDLService.getTableInfo(DDLService.java:278)
at sun.reflect.GeneratedMethodAccessor253.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
at 
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
at 
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at 
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at 
com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at 
com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at 
com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at 
com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at 
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at 
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
at 
com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
at 
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
at 
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at 
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1507)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)



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

[jira] [Updated] (AMBARI-20916) Run new heartbeatThread and statusCommand executor instead of old

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk updated AMBARI-20916:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed to branch-3.0-perf

> Run new heartbeatThread and statusCommand executor instead of old 
> --
>
> Key: AMBARI-20916
> URL: https://issues.apache.org/jira/browse/AMBARI-20916
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-20916.patch, AMBARI-20916.patch
>
>
> We have these threads running only in scope of UT. Need to start them on
> ambari-agent start for so testing with ambari-server can be done.



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

[jira] [Updated] (AMBARI-20979) Outstanding Alerts UI issues

[Aleksandr Kovalenko (JIRA)]

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

Aleksandr Kovalenko updated AMBARI-20979:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Outstanding Alerts UI issues
> 
>
> Key: AMBARI-20979
> URL: https://issues.apache.org/jira/browse/AMBARI-20979
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-20979.patch
>
>
> Following are the outstanding issues with Alerts:
> Alerts table on alerts page:
> * Status labels (# of hosts) shoud be the first column.
> On the Ambari top bar:
> * Alert number indicator: 1-2 digits, should be round. 3+ digits, shoud be a 
> pill/ellipse shape. 
> Alerts popup on services page:
> * Hide the horizontal scrollbar. The info should be nicely fitted into the 
> popup window, scroll bar is useless. 



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

[jira] [Commented] (AMBARI-20979) Outstanding Alerts UI issues

[Aleksandr Kovalenko (JIRA)]

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

Aleksandr Kovalenko commented on AMBARI-20979:
--

committed to trunk

> Outstanding Alerts UI issues
> 
>
> Key: AMBARI-20979
> URL: https://issues.apache.org/jira/browse/AMBARI-20979
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-20979.patch
>
>
> Following are the outstanding issues with Alerts:
> Alerts table on alerts page:
> * Status labels (# of hosts) shoud be the first column.
> On the Ambari top bar:
> * Alert number indicator: 1-2 digits, should be round. 3+ digits, shoud be a 
> pill/ellipse shape. 
> Alerts popup on services page:
> * Hide the horizontal scrollbar. The info should be nicely fitted into the 
> popup window, scroll bar is useless. 



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

[jira] [Commented] (AMBARI-20979) Outstanding Alerts UI issues

[Aleksandr Kovalenko (JIRA)]

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

Aleksandr Kovalenko commented on AMBARI-20979:
--

Patch contains changes only in styles and templates, no logic changes, it 
doesn't require changing unit tests.

> Outstanding Alerts UI issues
> 
>
> Key: AMBARI-20979
> URL: https://issues.apache.org/jira/browse/AMBARI-20979
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-20979.patch
>
>
> Following are the outstanding issues with Alerts:
> Alerts table on alerts page:
> * Status labels (# of hosts) shoud be the first column.
> On the Ambari top bar:
> * Alert number indicator: 1-2 digits, should be round. 3+ digits, shoud be a 
> pill/ellipse shape. 
> Alerts popup on services page:
> * Hide the horizontal scrollbar. The info should be nicely fitted into the 
> popup window, scroll bar is useless. 



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

[jira] [Updated] (AMBARI-20907) Create Database Schema for Improved User Account Management

[Robert Levas (JIRA)]

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

Robert Levas updated AMBARI-20907:
--
Description: 
User management tables in the DB should be:

*{{users}}*
||Name||Type||Description||
|user_id|INTEGER|Internal unique identifier|
|principal_id|INTEGER|Foreign key from adminprincipal table|
|user_name|VARCHAR|Unique, case-insensitive, login identifier expected to be 
used when logging into Ambari|
|active|BOOLEAN|Active/not active flag|
|consecutive_failures|INTEGER|The number a failed authorization attempts since 
the last successful authentication|
|active_widgets_layout|VARCHAR| |
|display_name|VARCHAR|Cosmetic name value to show the user in user interfaces|
|local_username|VARCHAR|Case-sensitive username to use when impersonating user 
in facilities like Ambari Views|
|create_time|TIMESTAMP|Creation time for this account in Ambari|
* Primary Key: {{user_id}}
* Foreign Key: {{principal_id}} -> {{adminprincipal.principal_id}}

*{{user_authentication}}*
||Name||Type||Description||
|user_authentication_id|INTEGER|Primary key for this table|
|user_id|INTEGER|Foreign key from users table|
|authentication_type|VARCHAR|Type of authentication system - LOCAL, LDAP,  
KERBEROS, JTW, PAM, etc...
|authentication_key|VARCHAR|Type-specific key (or identifier):
* LOCAL: the user's password (digest)
* LDAP: the user’s distinguished name
* KERBEROS: the user’s principal
* etc...|
|create_time|TIMESTAMP|Creation time of this record
|update_time|TIMESTAMP|Update time for this record, can be used to enforce 
password retention times|
* Primary Key: {{user_authentication_id}}
* Foreign Key: {{user_id}} -> {{users.user_id}}


  was:
User management tables in the DB should be:

*{{users}}*
||Name||Type||Description||
|user_id|INTEGER|Internal unique identifier|
|principal_id|INTEGER|Foreign key from adminprincipal table|
|user_name|VARCHAR|Unique, case-insensitive, login identifier expected to be 
used when logging into Ambari|
|create_time|TIMESTAMP|Creation time for this account in Ambari|
|active|BOOLEAN|Active/not active flag|
|consecutive_failed_auth_attemps|INTEGER|The number a failed authorization 
attempts since the last successful authentication|
|active_widgets_layout|VARCHAR| |
|display_name|VARCHAR|Cosmetic name value to show the user in user interfaces|
|local_username|VARCHAR|Case-sensitive username to use when impersonating user 
in facilities like Ambari Views|
* Primary Key: {{user_id}}
* Foreign Key: {{principal_id}} -> {{adminprincipal.principal_id}}

*{{user_authentication}}*
||Name||Type||Description||
|user_authentication_id|INTEGER|Primary key for this table|
|user_id|INTEGER|Foreign key from users table|
|authentication_type|VARCHAR|Type of authentication system - LOCAL, LDAP,  
KERBEROS, JTW, PAM, etc...
|authentication_key|VARCHAR|Type-specific key (or identifier):
* LOCAL: the user's password (digest)
* LDAP: the user’s distinguished name
* KERBEROS: the user’s principal
* etc...|
|create_time|TIMESTAMP|Creation time of this record
|update_time|TIMESTAMP|Update time for this record, can be used to enforce 
password retention times|
* Primary Key: {{user_authentication_id}}
* Foreign Key: {{user_id}} -> {{users.user_id}}



> Create Database Schema for Improved User Account Management
> ---
>
> Key: AMBARI-20907
> URL: https://issues.apache.org/jira/browse/AMBARI-20907
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-20907_branch-feature-AMBARI-20859_02.patch, 
> AMBARI-20907_branch-feature-AMBARI-20859.patch
>
>
> User management tables in the DB should be:
> *{{users}}*
> ||Name||Type||Description||
> |user_id|INTEGER|Internal unique identifier|
> |principal_id|INTEGER|Foreign key from adminprincipal table|
> |user_name|VARCHAR|Unique, case-insensitive, login identifier expected to be 
> used when logging into Ambari|
> |active|BOOLEAN|Active/not active flag|
> |consecutive_failures|INTEGER|The number a failed authorization attempts 
> since the last successful authentication|
> |active_widgets_layout|VARCHAR| |
> |display_name|VARCHAR|Cosmetic name value to show the user in user interfaces|
> |local_username|VARCHAR|Case-sensitive username to use when impersonating 
> user in facilities like Ambari Views|
> |create_time|TIMESTAMP|Creation time for this account in Ambari|
> * Primary Key: {{user_id}}
> * Foreign Key: {{principal_id}} -> {{adminprincipal.principal_id}}
> *{{user_authentication}}*
> ||Name||Type||Description||
> |user_authentication_id|INTEGER|Primary key for this table|
> |user_id|INTEGER|Foreign key from users table|
> |authentication_type|VARCH

[jira] [Updated] (AMBARI-20980) RU: RESTART SPARK2/SPARK2_CLIENT failed

[Dmitry Lysnichenko (JIRA)]

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

Dmitry Lysnichenko updated AMBARI-20980:

Fix Version/s: 2.5.1

> RU: RESTART SPARK2/SPARK2_CLIENT failed
> ---
>
> Key: AMBARI-20980
> URL: https://issues.apache.org/jira/browse/AMBARI-20980
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.1
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Fix For: 2.5.1
>
> Attachments: AMBARI-20980.patch
>
>
> STR:
> # Deploy HDP 2.5.3.0-37 on Ambari 2.4.2.0
> # Enable NN HA
> # Upgrade ambari to 2.5.1.0-95
> # Register and install HDP 2.6.1.0-56
> # Perform RU to Finalize
> # Perform Downgrade
> Result: RESTART SPARK2/SPARK2_CLIENT failed during Downgrade
> std.err
> {code}
> Traceback (most recent call last):
> File 
> "/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/spark_client.py",
>  line 60, in 
> SparkClient().execute()
> File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 315, in execute
> method(env)
> File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 783, in restart
> self.pre_upgrade_restart(env, upgrade_type=upgrade_type)
> File 
> "/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/spark_client.py",
>  line 51, in pre_upgrade_restart
> import params
> File 
> "/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/params.py",
>  line 209, in 
> livy2_pid_dir = status_params.livy2_pid_dir
> AttributeError: 'module' object has no attribute 'livy2_pid_dir'
> {code}
> it was caused by AMBARI-19248 which assumes that livy2_pid_dir is present 
> even if livy2 is not installed.



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

[jira] [Updated] (AMBARI-20980) RU: RESTART SPARK2/SPARK2_CLIENT failed

[Dmitry Lysnichenko (JIRA)]

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

Dmitry Lysnichenko updated AMBARI-20980:

Affects Version/s: 2.5.1

> RU: RESTART SPARK2/SPARK2_CLIENT failed
> ---
>
> Key: AMBARI-20980
> URL: https://issues.apache.org/jira/browse/AMBARI-20980
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.1
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Fix For: 2.5.1
>
> Attachments: AMBARI-20980.patch
>
>
> STR:
> # Deploy HDP 2.5.3.0-37 on Ambari 2.4.2.0
> # Enable NN HA
> # Upgrade ambari to 2.5.1.0-95
> # Register and install HDP 2.6.1.0-56
> # Perform RU to Finalize
> # Perform Downgrade
> Result: RESTART SPARK2/SPARK2_CLIENT failed during Downgrade
> std.err
> {code}
> Traceback (most recent call last):
> File 
> "/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/spark_client.py",
>  line 60, in 
> SparkClient().execute()
> File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 315, in execute
> method(env)
> File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 783, in restart
> self.pre_upgrade_restart(env, upgrade_type=upgrade_type)
> File 
> "/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/spark_client.py",
>  line 51, in pre_upgrade_restart
> import params
> File 
> "/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/params.py",
>  line 209, in 
> livy2_pid_dir = status_params.livy2_pid_dir
> AttributeError: 'module' object has no attribute 'livy2_pid_dir'
> {code}
> it was caused by AMBARI-19248 which assumes that livy2_pid_dir is present 
> even if livy2 is not installed.



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

[jira] [Updated] (AMBARI-20980) RU: RESTART SPARK2/SPARK2_CLIENT failed

[Dmitry Lysnichenko (JIRA)]

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

Dmitry Lysnichenko updated AMBARI-20980:

Attachment: AMBARI-20980.patch

> RU: RESTART SPARK2/SPARK2_CLIENT failed
> ---
>
> Key: AMBARI-20980
> URL: https://issues.apache.org/jira/browse/AMBARI-20980
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Attachments: AMBARI-20980.patch
>
>
> STR:
> # Deploy HDP 2.5.3.0-37 on Ambari 2.4.2.0
> # Enable NN HA
> # Upgrade ambari to 2.5.1.0-95
> # Register and install HDP 2.6.1.0-56
> # Perform RU to Finalize
> # Perform Downgrade
> Result: RESTART SPARK2/SPARK2_CLIENT failed during Downgrade
> std.err
> {code}
> Traceback (most recent call last):
> File 
> "/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/spark_client.py",
>  line 60, in 
> SparkClient().execute()
> File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 315, in execute
> method(env)
> File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 783, in restart
> self.pre_upgrade_restart(env, upgrade_type=upgrade_type)
> File 
> "/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/spark_client.py",
>  line 51, in pre_upgrade_restart
> import params
> File 
> "/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/params.py",
>  line 209, in 
> livy2_pid_dir = status_params.livy2_pid_dir
> AttributeError: 'module' object has no attribute 'livy2_pid_dir'
> {code}
> it was caused by AMBARI-19248 which assumes that livy2_pid_dir is present 
> even if livy2 is not installed.



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

[jira] [Updated] (AMBARI-20980) RU: RESTART SPARK2/SPARK2_CLIENT failed

[Dmitry Lysnichenko (JIRA)]

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

Dmitry Lysnichenko updated AMBARI-20980:

Status: Patch Available  (was: Open)

> RU: RESTART SPARK2/SPARK2_CLIENT failed
> ---
>
> Key: AMBARI-20980
> URL: https://issues.apache.org/jira/browse/AMBARI-20980
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Attachments: AMBARI-20980.patch
>
>
> STR:
> # Deploy HDP 2.5.3.0-37 on Ambari 2.4.2.0
> # Enable NN HA
> # Upgrade ambari to 2.5.1.0-95
> # Register and install HDP 2.6.1.0-56
> # Perform RU to Finalize
> # Perform Downgrade
> Result: RESTART SPARK2/SPARK2_CLIENT failed during Downgrade
> std.err
> {code}
> Traceback (most recent call last):
> File 
> "/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/spark_client.py",
>  line 60, in 
> SparkClient().execute()
> File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 315, in execute
> method(env)
> File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 783, in restart
> self.pre_upgrade_restart(env, upgrade_type=upgrade_type)
> File 
> "/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/spark_client.py",
>  line 51, in pre_upgrade_restart
> import params
> File 
> "/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/params.py",
>  line 209, in 
> livy2_pid_dir = status_params.livy2_pid_dir
> AttributeError: 'module' object has no attribute 'livy2_pid_dir'
> {code}
> it was caused by AMBARI-19248 which assumes that livy2_pid_dir is present 
> even if livy2 is not installed.



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

[jira] [Updated] (AMBARI-20980) RU: RESTART SPARK2/SPARK2_CLIENT failed

[Dmitry Lysnichenko (JIRA)]

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

Dmitry Lysnichenko updated AMBARI-20980:

Component/s: ambari-server

> RU: RESTART SPARK2/SPARK2_CLIENT failed
> ---
>
> Key: AMBARI-20980
> URL: https://issues.apache.org/jira/browse/AMBARI-20980
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Attachments: AMBARI-20980.patch
>
>
> STR:
> # Deploy HDP 2.5.3.0-37 on Ambari 2.4.2.0
> # Enable NN HA
> # Upgrade ambari to 2.5.1.0-95
> # Register and install HDP 2.6.1.0-56
> # Perform RU to Finalize
> # Perform Downgrade
> Result: RESTART SPARK2/SPARK2_CLIENT failed during Downgrade
> std.err
> {code}
> Traceback (most recent call last):
> File 
> "/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/spark_client.py",
>  line 60, in 
> SparkClient().execute()
> File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 315, in execute
> method(env)
> File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 783, in restart
> self.pre_upgrade_restart(env, upgrade_type=upgrade_type)
> File 
> "/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/spark_client.py",
>  line 51, in pre_upgrade_restart
> import params
> File 
> "/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/params.py",
>  line 209, in 
> livy2_pid_dir = status_params.livy2_pid_dir
> AttributeError: 'module' object has no attribute 'livy2_pid_dir'
> {code}
> it was caused by AMBARI-19248 which assumes that livy2_pid_dir is present 
> even if livy2 is not installed.



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

[jira] [Created] (AMBARI-20980) RU: RESTART SPARK2/SPARK2_CLIENT failed

[Dmitry Lysnichenko (JIRA)]

Dmitry Lysnichenko created AMBARI-20980:
---

 Summary: RU: RESTART SPARK2/SPARK2_CLIENT failed
 Key: AMBARI-20980
 URL: https://issues.apache.org/jira/browse/AMBARI-20980
 Project: Ambari
  Issue Type: Bug
Reporter: Dmitry Lysnichenko
Assignee: Dmitry Lysnichenko
Priority: Blocker
 Attachments: AMBARI-20980.patch


STR:
# Deploy HDP 2.5.3.0-37 on Ambari 2.4.2.0
# Enable NN HA
# Upgrade ambari to 2.5.1.0-95
# Register and install HDP 2.6.1.0-56
# Perform RU to Finalize
# Perform Downgrade
Result: RESTART SPARK2/SPARK2_CLIENT failed during Downgrade


std.err
{code}
Traceback (most recent call last):
File 
"/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/spark_client.py",
 line 60, in 
SparkClient().execute()
File 
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
 line 315, in execute
method(env)
File 
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
 line 783, in restart
self.pre_upgrade_restart(env, upgrade_type=upgrade_type)
File 
"/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/spark_client.py",
 line 51, in pre_upgrade_restart
import params
File 
"/var/lib/ambari-agent/cache/common-services/SPARK2/2.0.0/package/scripts/params.py",
 line 209, in 
livy2_pid_dir = status_params.livy2_pid_dir
AttributeError: 'module' object has no attribute 'livy2_pid_dir'
{code}

it was caused by AMBARI-19248 which assumes that livy2_pid_dir is present even 
if livy2 is not installed.




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

[jira] [Commented] (AMBARI-20979) Outstanding Alerts UI issues

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-20979:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12867342/AMBARI-20979.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 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

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

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

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

This message is automatically generated.

> Outstanding Alerts UI issues
> 
>
> Key: AMBARI-20979
> URL: https://issues.apache.org/jira/browse/AMBARI-20979
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-20979.patch
>
>
> Following are the outstanding issues with Alerts:
> Alerts table on alerts page:
> * Status labels (# of hosts) shoud be the first column.
> On the Ambari top bar:
> * Alert number indicator: 1-2 digits, should be round. 3+ digits, shoud be a 
> pill/ellipse shape. 
> Alerts popup on services page:
> * Hide the horizontal scrollbar. The info should be nicely fitted into the 
> popup window, scroll bar is useless. 



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