[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.
[
https://issues.apache.org/jira/browse/AMBARI-20947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15999231#comment-15999231
]
Sumit Mohanty commented on AMBARI-20947:
LGTM, +1
Any unit test changes?
> 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] [Assigned] (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.
[
https://issues.apache.org/jira/browse/AMBARI-20947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty reassigned AMBARI-20947:
--
Assignee: Swapan Shridhar
> 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] [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.
[
https://issues.apache.org/jira/browse/AMBARI-20947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15999226#comment-15999226
]
Swapan Shridhar commented on AMBARI-20947:
--
[~sumitmohanty] | [~afernandez] Patch for review.
> 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
>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.
[
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.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
>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.
[
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.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
>Priority: Blocker
> Fix For: trunk, 2.5.1
>
> Attachments: AMBARI-20947.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.
[
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.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
>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.
[
https://issues.apache.org/jira/browse/AMBARI-20947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-20947:
-
Description:
*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.
was:
*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.
> 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
>Priority: Blocker
> Fix For: trunk, 2.5.1
>
>
> *Issue:*
> HSI server start failed with "kinit: Key tabl
[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.
[
https://issues.apache.org/jira/browse/AMBARI-20947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-20947:
-
Description:
*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.
was:
*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.
> 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
>Priority: Blocker
> Fix For: trunk, 2.5.1
>
>
> *Issue:*
> HSI server start failed with "kinit: Key table fi
[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.
[
https://issues.apache.org/jira/browse/AMBARI-20947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-20947:
-
Description:
*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.
> 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
>Priority: Blocker
> Fix For: trunk, 2.5.1
>
>
> *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
[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.
[ https://issues.apache.org/jira/browse/AMBARI-20947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-20947: - Affects Version/s: trunk > 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 >Priority: Blocker > Fix For: trunk, 2.5.1 > > -- 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.
[ https://issues.apache.org/jira/browse/AMBARI-20947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-20947: - Fix Version/s: 2.5.1 trunk > 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 >Priority: Blocker > Fix For: trunk, 2.5.1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (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 created AMBARI-20947: Summary: 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: 2.5.0 Reporter: Swapan Shridhar Priority: Blocker -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-20934) Service check for Falcon is failed [Upgrade from 2.4.0.0/2.4.1.0 to 2.4.3.0]
[ https://issues.apache.org/jira/browse/AMBARI-20934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-20934. Resolution: Invalid > Service check for Falcon is failed [Upgrade from 2.4.0.0/2.4.1.0 to 2.4.3.0] > > > Key: AMBARI-20934 > URL: https://issues.apache.org/jira/browse/AMBARI-20934 > Project: Ambari > Issue Type: Bug > Components: ambari-upgrade >Affects Versions: 2.4.3 >Reporter: Sviatoslav Tereshchenko > Labels: system_test, upgrade > Fix For: 2.4.3 > > > STR: > 1) Deploy cluster - 2.4.0.0 > 2) Make ambari only upgrade to 2.4.3.0 > 3) Enable security > 4) Run service check for Falcon > Actual result: Service check for Falcon is failed -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20934) Service check for Falcon is failed [Upgrade from 2.4.0.0/2.4.1.0 to 2.4.3.0]
[ https://issues.apache.org/jira/browse/AMBARI-20934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15999049#comment-15999049 ] Aravindan Vijayan commented on AMBARI-20934: Falcon service was not able to start due to je-5.0.73.jar absence. Closing as invalid. > Service check for Falcon is failed [Upgrade from 2.4.0.0/2.4.1.0 to 2.4.3.0] > > > Key: AMBARI-20934 > URL: https://issues.apache.org/jira/browse/AMBARI-20934 > Project: Ambari > Issue Type: Bug > Components: ambari-upgrade >Affects Versions: 2.4.3 >Reporter: Sviatoslav Tereshchenko > Labels: system_test, upgrade > Fix For: 2.4.3 > > > STR: > 1) Deploy cluster - 2.4.0.0 > 2) Make ambari only upgrade to 2.4.3.0 > 3) Enable security > 4) Run service check for Falcon > Actual result: Service check for Falcon is failed -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-20933) Metrics Collector stopped by itself after enabling security [Upgrade from 2.4.0.0 to 2.4.3.0]
[ https://issues.apache.org/jira/browse/AMBARI-20933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-20933. Resolution: Invalid > Metrics Collector stopped by itself after enabling security [Upgrade from > 2.4.0.0 to 2.4.3.0] > - > > Key: AMBARI-20933 > URL: https://issues.apache.org/jira/browse/AMBARI-20933 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.4.3 > Environment: OS: Ubuntu > Upgrade type: ambari only upgrade >Reporter: Sviatoslav Tereshchenko >Assignee: Siddharth Wagle >Priority: Critical > Labels: upgrade > Fix For: 2.4.3 > > > STR: > 1) Deploy cluster - 2.4.0.0 > 2) Make ambari only upgrade to 2.4.3.0 > 3) Enable security > Actual result: Metrics Collector stopped by itself after enabling security. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20933) Metrics Collector stopped by itself after enabling security [Upgrade from 2.4.0.0 to 2.4.3.0]
[
https://issues.apache.org/jira/browse/AMBARI-20933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15999048#comment-15999048
]
Aravindan Vijayan commented on AMBARI-20933:
NN is in standby mode and so HMaster failed to start:
{code}
2017-05-04 16:12:47,281 FATAL [61300.activeMasterManager] master.HMaster:
Unhandled exception. Starting shutdown.
org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.ipc.StandbyException):
Operation category READ is not supported in state standby
at
org.apache.hadoop.hdfs.server.namenode.ha.StandbyState.checkOperation(StandbyState.java:87)
{code}
Closing as it is a test issue.
cc [~swagle]
> Metrics Collector stopped by itself after enabling security [Upgrade from
> 2.4.0.0 to 2.4.3.0]
> -
>
> Key: AMBARI-20933
> URL: https://issues.apache.org/jira/browse/AMBARI-20933
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.4.3
> Environment: OS: Ubuntu
> Upgrade type: ambari only upgrade
>Reporter: Sviatoslav Tereshchenko
>Priority: Critical
> Labels: upgrade
> Fix For: 2.4.3
>
>
> STR:
> 1) Deploy cluster - 2.4.0.0
> 2) Make ambari only upgrade to 2.4.3.0
> 3) Enable security
> Actual result: Metrics Collector stopped by itself after enabling security.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (AMBARI-20933) Metrics Collector stopped by itself after enabling security [Upgrade from 2.4.0.0 to 2.4.3.0]
[ https://issues.apache.org/jira/browse/AMBARI-20933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan reassigned AMBARI-20933: -- Assignee: Siddharth Wagle > Metrics Collector stopped by itself after enabling security [Upgrade from > 2.4.0.0 to 2.4.3.0] > - > > Key: AMBARI-20933 > URL: https://issues.apache.org/jira/browse/AMBARI-20933 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.4.3 > Environment: OS: Ubuntu > Upgrade type: ambari only upgrade >Reporter: Sviatoslav Tereshchenko >Assignee: Siddharth Wagle >Priority: Critical > Labels: upgrade > Fix For: 2.4.3 > > > STR: > 1) Deploy cluster - 2.4.0.0 > 2) Make ambari only upgrade to 2.4.3.0 > 3) Enable security > Actual result: Metrics Collector stopped by itself after enabling security. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20938) LDAPS connections to an Active Directory when enabling Kerberos should validate the server's SSL certificate
[
https://issues.apache.org/jira/browse/AMBARI-20938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-20938:
--
Description:
LDAPS connections to an Active Directory when enabling Kerberos should validate
the server's SSL certificate. The current implementation skips validation
checks to help avoid SSL issues; however this is not secure. Also the
_trusting_ SSL connection may not support the more secure SSL protocols -
TLSv1.2.
A flag in the {{ambari.properties}} file
({{kerberos.operation.verify.kdc.trust}}) should be available to allow for the
user to select either a _trusting_ SSL connection or a validating
(non-trusting) SSL connection to be used. The default should be to use the
standard (non-trusting) SSL connection.
was:
LDAPS connections to an Active Directory when enabling Kerberos should validate
the server's SSL certificate. The current implementation skips validation
checks to help avoid SSL issues; however this is not secure. Also the
_trusting_ SSL connection may not support the more secure SSL protocols -
TLSv1.2.
A flag in the {{ambari.properties}} file should be available to allow for the
_trusting_ SSL connection to be used; but the default should be to use the
standard (non-trusting) SSL connection.
> LDAPS connections to an Active Directory when enabling Kerberos should
> validate the server's SSL certificate
>
>
> Key: AMBARI-20938
> URL: https://issues.apache.org/jira/browse/AMBARI-20938
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: active-directory, active_directory, kerberos, ssl
> Fix For: 2.5.2
>
>
> LDAPS connections to an Active Directory when enabling Kerberos should
> validate the server's SSL certificate. The current implementation skips
> validation checks to help avoid SSL issues; however this is not secure. Also
> the _trusting_ SSL connection may not support the more secure SSL protocols -
> TLSv1.2.
> A flag in the {{ambari.properties}} file
> ({{kerberos.operation.verify.kdc.trust}}) should be available to allow for
> the user to select either a _trusting_ SSL connection or a validating
> (non-trusting) SSL connection to be used. The default should be to use the
> standard (non-trusting) SSL connection.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20925) Service Auto-Start behavior is incorrect for Service Administrator and Service Operator Roles
[ https://issues.apache.org/jira/browse/AMBARI-20925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15998860#comment-15998860 ] Hudson commented on AMBARI-20925: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1505 (See [https://builds.apache.org/job/Ambari-branch-2.5/1505/]) AMBARI-20925: Service Auto-Start behavior is incorrect for Service (sangeetar: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=d8f7d3ae34233378e6eb52db6b0d316d4d906db2]) * (edit) ambari-web/app/views/main/menu.js * (edit) ambari-web/app/views/main/admin.js * (edit) ambari-web/app/routes/main.js > Service Auto-Start behavior is incorrect for Service Administrator and > Service Operator Roles > - > > Key: AMBARI-20925 > URL: https://issues.apache.org/jira/browse/AMBARI-20925 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk, 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > Fix For: trunk, 2.5.1 > > Attachments: AMBARI-20925_2.5.1.patch, AMBARI-20925_trunk.patch > > > As per the Role based access control list, users with Service Administrator > role should be able to manage service auto-start while users with Service > Operator role should not have this privilege. > Currently, Service Administrators and Service Operators can view Service Auto > Start menu item, but clicking on it displays the main dashboard. > Service Operators should not see this menu and Service Administrators should > be able to navigate to the Service Auto Start page and enable or disable > auto-start at service level. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20925) Service Auto-Start behavior is incorrect for Service Administrator and Service Operator Roles
[ https://issues.apache.org/jira/browse/AMBARI-20925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-20925: Resolution: Fixed Fix Version/s: 2.5.1 Status: Resolved (was: Patch Available) Pushed to trunk as commit 2b676c1829560c91ccafd8510a3202e61730ff66 Pushed to 2.5.1 as commit d8f7d3ae34233378e6eb52db6b0d316d4d906db2 > Service Auto-Start behavior is incorrect for Service Administrator and > Service Operator Roles > - > > Key: AMBARI-20925 > URL: https://issues.apache.org/jira/browse/AMBARI-20925 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk, 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > Fix For: trunk, 2.5.1 > > Attachments: AMBARI-20925_2.5.1.patch, AMBARI-20925_trunk.patch > > > As per the Role based access control list, users with Service Administrator > role should be able to manage service auto-start while users with Service > Operator role should not have this privilege. > Currently, Service Administrators and Service Operators can view Service Auto > Start menu item, but clicking on it displays the main dashboard. > Service Operators should not see this menu and Service Administrators should > be able to navigate to the Service Auto Start page and enable or disable > auto-start at service level. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20925) Service Auto-Start behavior is incorrect for Service Administrator and Service Operator Roles
[ https://issues.apache.org/jira/browse/AMBARI-20925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15998834#comment-15998834 ] Sangeeta Ravindran commented on AMBARI-20925: - Failure seems unrelated to patch. [ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.4:yarn (yarn install) on project ambari-web: Failed to run task: 'yarn install --ignore-engines --pure-lockfile' failed. org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1) -> [Help 1] > Service Auto-Start behavior is incorrect for Service Administrator and > Service Operator Roles > - > > Key: AMBARI-20925 > URL: https://issues.apache.org/jira/browse/AMBARI-20925 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk, 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > Fix For: trunk > > Attachments: AMBARI-20925_2.5.1.patch, AMBARI-20925_trunk.patch > > > As per the Role based access control list, users with Service Administrator > role should be able to manage service auto-start while users with Service > Operator role should not have this privilege. > Currently, Service Administrators and Service Operators can view Service Auto > Start menu item, but clicking on it displays the main dashboard. > Service Operators should not see this menu and Service Administrators should > be able to navigate to the Service Auto Start page and enable or disable > auto-start at service level. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20942) HDP 3.0 TP - create Service Advisor for Kafka
[ https://issues.apache.org/jira/browse/AMBARI-20942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15998825#comment-15998825 ] Hudson commented on AMBARI-20942: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7433 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7433/]) AMBARI-20942. HDP 3.0 TP - create Service Advisor for (vbrodetskyi: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=0abfb352596b1650647c33d929b04210481453bd]) * (add) ambari-server/src/main/resources/common-services/KAFKA/0.10.0.3.0/service_advisor.py > HDP 3.0 TP - create Service Advisor for Kafka > - > > Key: AMBARI-20942 > URL: https://issues.apache.org/jira/browse/AMBARI-20942 > 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-20942.patch > > > . -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20925) Service Auto-Start behavior is incorrect for Service Administrator and Service Operator Roles
[ https://issues.apache.org/jira/browse/AMBARI-20925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-20925: Attachment: AMBARI-20925_2.5.1.patch > Service Auto-Start behavior is incorrect for Service Administrator and > Service Operator Roles > - > > Key: AMBARI-20925 > URL: https://issues.apache.org/jira/browse/AMBARI-20925 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk, 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > Fix For: trunk > > Attachments: AMBARI-20925_2.5.1.patch, AMBARI-20925_trunk.patch > > > As per the Role based access control list, users with Service Administrator > role should be able to manage service auto-start while users with Service > Operator role should not have this privilege. > Currently, Service Administrators and Service Operators can view Service Auto > Start menu item, but clicking on it displays the main dashboard. > Service Operators should not see this menu and Service Administrators should > be able to navigate to the Service Auto Start page and enable or disable > auto-start at service level. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20946) Zip file with a service's "package" subdirectory is not recreated if the old zip file is removed but the archived hash file exists
Diego Santesteban created AMBARI-20946: -- Summary: Zip file with a service's "package" subdirectory is not recreated if the old zip file is removed but the archived hash file exists Key: AMBARI-20946 URL: https://issues.apache.org/jira/browse/AMBARI-20946 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.5.0 Reporter: Diego Santesteban Priority: Minor Fix For: trunk When Ambari recreates the archive.zip file for a service's "package" directory (to distribute to Ambari Agents), it creates a .hash file that checks if the archive should be recreated in the future. If the .hash file is removed but the archive.zip is not, the archive will always be recreated. However, if the .hash file exists and matches the current directory's hash (i.e. no changes have been made in the directory), Ambari won't recreate the archive file, even if it was removed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20942) HDP 3.0 TP - create Service Advisor for Kafka
[ https://issues.apache.org/jira/browse/AMBARI-20942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-20942: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk > HDP 3.0 TP - create Service Advisor for Kafka > - > > Key: AMBARI-20942 > URL: https://issues.apache.org/jira/browse/AMBARI-20942 > 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-20942.patch > > > . -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20925) Service Auto-Start behavior is incorrect for Service Administrator and Service Operator Roles
[ https://issues.apache.org/jira/browse/AMBARI-20925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15998694#comment-15998694 ] Hudson commented on AMBARI-20925: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7432 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7432/]) AMBARI-20925: Service Auto-Start behavior is incorrect for Service (sangeetar: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=2b676c1829560c91ccafd8510a3202e61730ff66]) * (edit) ambari-web/app/views/main/menu.js * (edit) ambari-web/app/routes/main.js * (edit) ambari-web/app/views/main/admin.js > Service Auto-Start behavior is incorrect for Service Administrator and > Service Operator Roles > - > > Key: AMBARI-20925 > URL: https://issues.apache.org/jira/browse/AMBARI-20925 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk, 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > Fix For: trunk > > Attachments: AMBARI-20925_trunk.patch > > > As per the Role based access control list, users with Service Administrator > role should be able to manage service auto-start while users with Service > Operator role should not have this privilege. > Currently, Service Administrators and Service Operators can view Service Auto > Start menu item, but clicking on it displays the main dashboard. > Service Operators should not see this menu and Service Administrators should > be able to navigate to the Service Auto Start page and enable or disable > auto-start at service level. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-20945) Configuration parameter 'hdfs-site' was not found error when AMS rootdir is on s3a
[
https://issues.apache.org/jira/browse/AMBARI-20945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siddharth Wagle reassigned AMBARI-20945:
Assignee: Aravindan Vijayan
> Configuration parameter 'hdfs-site' was not found error when AMS rootdir is
> on s3a
> --
>
> Key: AMBARI-20945
> URL: https://issues.apache.org/jira/browse/AMBARI-20945
> Project: Ambari
> Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Aravindan Vijayan
>
> When I specify AMS rootdir to be on s3a and restart AMS, I would get the
> following error:
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_collector.py",
> line 86, in
> AmsCollector().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 817, in restart
> self.start(env)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_collector.py",
> line 48, in start
> self.configure(env, action = 'start') # for security
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 118, in locking_configure
> original_configure(obj, *args, **kw)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_collector.py",
> line 43, in configure
> hbase('master', action)
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/hbase.py",
> line 222, in hbase
> dfs_type=params.dfs_type
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 155, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 119, in run_action
> provider = provider_class(resource)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 503, in __init__
> self.assert_parameter_is_set('hdfs_site')
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 575, in assert_parameter_is_set
> if not getattr(self.resource, parameter_name):
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py",
> line 73, in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found in
> configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter 'hdfs-site'
> was not found in configurations dictionary!
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20945) Configuration parameter 'hdfs-site' was not found error when AMS rootdir is on s3a
Ted Yu created AMBARI-20945:
---
Summary: Configuration parameter 'hdfs-site' was not found error
when AMS rootdir is on s3a
Key: AMBARI-20945
URL: https://issues.apache.org/jira/browse/AMBARI-20945
Project: Ambari
Issue Type: Bug
Reporter: Ted Yu
When I specify AMS rootdir to be on s3a and restart AMS, I would get the
following error:
{code}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_collector.py",
line 86, in
AmsCollector().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 817, in restart
self.start(env)
File
"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_collector.py",
line 48, in start
self.configure(env, action = 'start') # for security
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 118, in locking_configure
original_configure(obj, *args, **kw)
File
"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_collector.py",
line 43, in configure
hbase('master', action)
File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
line 89, in thunk
return fn(*args, **kwargs)
File
"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/hbase.py",
line 222, in hbase
dfs_type=params.dfs_type
File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
line 155, in __init__
self.env.run()
File
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
line 160, in run
self.run_action(resource, action)
File
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
line 119, in run_action
provider = provider_class(resource)
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
line 503, in __init__
self.assert_parameter_is_set('hdfs_site')
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
line 575, in assert_parameter_is_set
if not getattr(self.resource, parameter_name):
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py",
line 73, in __getattr__
raise Fail("Configuration parameter '" + self.name + "' was not found in
configurations dictionary!")
resource_management.core.exceptions.Fail: Configuration parameter 'hdfs-site'
was not found in configurations dictionary!
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20698) Ability to export blueprint via Ambari installer UI
[ https://issues.apache.org/jira/browse/AMBARI-20698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20698: --- Status: Patch Available (was: In Progress) > Ability to export blueprint via Ambari installer UI > --- > > Key: AMBARI-20698 > URL: https://issues.apache.org/jira/browse/AMBARI-20698 > Project: Ambari > Issue Type: Technical task > Components: ambari-web >Affects Versions: trunk >Reporter: Di Li >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20698.patch, Generate blueprint via Ambari > Installer UI - v2.pdf > > > UI be able to export a blueprint when a user reaches the Deploy page and the > bp can be used to install a cluster later on. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20698) Ability to export blueprint via Ambari installer UI
[ https://issues.apache.org/jira/browse/AMBARI-20698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20698: --- Attachment: AMBARI-20698.patch > Ability to export blueprint via Ambari installer UI > --- > > Key: AMBARI-20698 > URL: https://issues.apache.org/jira/browse/AMBARI-20698 > Project: Ambari > Issue Type: Technical task > Components: ambari-web >Affects Versions: trunk >Reporter: Di Li >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20698.patch, Generate blueprint via Ambari > Installer UI - v2.pdf > > > UI be able to export a blueprint when a user reaches the Deploy page and the > bp can be used to install a cluster later on. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20698) Ability to export blueprint via Ambari installer UI
[ https://issues.apache.org/jira/browse/AMBARI-20698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20698: --- Attachment: (was: AMBARI-20698.patch) > Ability to export blueprint via Ambari installer UI > --- > > Key: AMBARI-20698 > URL: https://issues.apache.org/jira/browse/AMBARI-20698 > Project: Ambari > Issue Type: Technical task > Components: ambari-web >Affects Versions: trunk >Reporter: Di Li >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20698.patch, Generate blueprint via Ambari > Installer UI - v2.pdf > > > UI be able to export a blueprint when a user reaches the Deploy page and the > bp can be used to install a cluster later on. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20698) Ability to export blueprint via Ambari installer UI
[ https://issues.apache.org/jira/browse/AMBARI-20698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-20698: --- Status: Open (was: Patch Available) > Ability to export blueprint via Ambari installer UI > --- > > Key: AMBARI-20698 > URL: https://issues.apache.org/jira/browse/AMBARI-20698 > Project: Ambari > Issue Type: Technical task > Components: ambari-web >Affects Versions: trunk >Reporter: Di Li >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20698.patch, Generate blueprint via Ambari > Installer UI - v2.pdf > > > UI be able to export a blueprint when a user reaches the Deploy page and the > bp can be used to install a cluster later on. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20926) Ranger Quick links not showing load balancer in Ranger-admin HA
[ https://issues.apache.org/jira/browse/AMBARI-20926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-20926: - Affects Version/s: 2.4.2 > Ranger Quick links not showing load balancer in Ranger-admin HA > --- > > Key: AMBARI-20926 > URL: https://issues.apache.org/jira/browse/AMBARI-20926 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0, 2.4.2 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 2.5.1, 2.4.3 > > Attachments: AMBARI-20926-branch-2.4.patch, > AMBARI-20926-branch-2.5.patch, AMBARI-20926-trunk.patch > > > Ranger Quick links not pointing to load balancer URL when ranger HA is > enabled. Quick links pointing to http://:6080 port. > Ambari affected: 2.4.2 and 2.5.0.3 > Prior to ambari upgrade in 2.2.2, quicklink was showing only the Ranger > loadbalancer UI. After upgrading to 2.4.2, it showing both ranger admin URLs > instead of the load balancer URL in quicklinks. > Solution: > Should always use Ranger External URL property for the quick link. > (admin-properties.xml/policymgr_external_url) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20926) Ranger Quick links not showing load balancer in Ranger-admin HA
[ https://issues.apache.org/jira/browse/AMBARI-20926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15998606#comment-15998606 ] Yusaku Sako commented on AMBARI-20926: -- Committed to branch-2.4. > Ranger Quick links not showing load balancer in Ranger-admin HA > --- > > Key: AMBARI-20926 > URL: https://issues.apache.org/jira/browse/AMBARI-20926 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0, 2.4.2 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 2.5.1, 2.4.3 > > Attachments: AMBARI-20926-branch-2.4.patch, > AMBARI-20926-branch-2.5.patch, AMBARI-20926-trunk.patch > > > Ranger Quick links not pointing to load balancer URL when ranger HA is > enabled. Quick links pointing to http://:6080 port. > Ambari affected: 2.4.2 and 2.5.0.3 > Prior to ambari upgrade in 2.2.2, quicklink was showing only the Ranger > loadbalancer UI. After upgrading to 2.4.2, it showing both ranger admin URLs > instead of the load balancer URL in quicklinks. > Solution: > Should always use Ranger External URL property for the quick link. > (admin-properties.xml/policymgr_external_url) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20926) Ranger Quick links not showing load balancer in Ranger-admin HA
[ https://issues.apache.org/jira/browse/AMBARI-20926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-20926: - Fix Version/s: 2.4.3 > Ranger Quick links not showing load balancer in Ranger-admin HA > --- > > Key: AMBARI-20926 > URL: https://issues.apache.org/jira/browse/AMBARI-20926 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0, 2.4.2 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 2.5.1, 2.4.3 > > Attachments: AMBARI-20926-branch-2.4.patch, > AMBARI-20926-branch-2.5.patch, AMBARI-20926-trunk.patch > > > Ranger Quick links not pointing to load balancer URL when ranger HA is > enabled. Quick links pointing to http://:6080 port. > Ambari affected: 2.4.2 and 2.5.0.3 > Prior to ambari upgrade in 2.2.2, quicklink was showing only the Ranger > loadbalancer UI. After upgrading to 2.4.2, it showing both ranger admin URLs > instead of the load balancer URL in quicklinks. > Solution: > Should always use Ranger External URL property for the quick link. > (admin-properties.xml/policymgr_external_url) -- 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
[
https://issues.apache.org/jira/browse/AMBARI-20937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-20937:
-
Summary: Ambari Upgrade to 2.5 fails due to custom service; rpm upgrade
does not preserve the custom service directory (was: Ambari 2.5 schema upgrade
failing with custom service installed)
> 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
>
> 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.act
[jira] [Updated] (AMBARI-20789) UI to display install process of an blueprint install
[ https://issues.apache.org/jira/browse/AMBARI-20789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-20789: --- Parent Issue: AMBARI-20944 (was: AMBARI-20698) > UI to display install process of an blueprint install > - > > Key: AMBARI-20789 > URL: https://issues.apache.org/jira/browse/AMBARI-20789 > Project: Ambari > Issue Type: Technical task > Components: ambari-web >Affects Versions: trunk >Reporter: Di Li >Assignee: Amruta Borkar > Fix For: trunk > > > This is the third step where UI needs to provide feedback/progress on the > installation (now bp based). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20698) Ability to export blueprint via Ambari installer UI
[ https://issues.apache.org/jira/browse/AMBARI-20698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-20698: --- Issue Type: Technical task (was: New Feature) Parent: AMBARI-20944 > Ability to export blueprint via Ambari installer UI > --- > > Key: AMBARI-20698 > URL: https://issues.apache.org/jira/browse/AMBARI-20698 > Project: Ambari > Issue Type: Technical task > Components: ambari-web >Affects Versions: trunk >Reporter: Di Li >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20698.patch, Generate blueprint via Ambari > Installer UI - v2.pdf > > > UI be able to export a blueprint when a user reaches the Deploy page and the > bp can be used to install a cluster later on. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20788) Able to kick off cluster install from UI via blueprint generated
[ https://issues.apache.org/jira/browse/AMBARI-20788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-20788: --- Parent Issue: AMBARI-20944 (was: AMBARI-20698) > Able to kick off cluster install from UI via blueprint generated > > > Key: AMBARI-20788 > URL: https://issues.apache.org/jira/browse/AMBARI-20788 > Project: Ambari > Issue Type: Technical task > Components: ambari-web >Affects Versions: trunk >Reporter: Di Li >Assignee: Amruta Borkar > Fix For: trunk > > > This is the second step of the jira is to be able to use the blueprint and > cluster template created by the UI to install a cluster. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20698) Ability to export blueprint via Ambari installer UI
[ https://issues.apache.org/jira/browse/AMBARI-20698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-20698: --- Issue Type: New Feature (was: Task) > Ability to export blueprint via Ambari installer UI > --- > > Key: AMBARI-20698 > URL: https://issues.apache.org/jira/browse/AMBARI-20698 > Project: Ambari > Issue Type: New Feature > Components: ambari-web >Affects Versions: trunk >Reporter: Di Li >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20698.patch, Generate blueprint via Ambari > Installer UI - v2.pdf > > > UI be able to export a blueprint when a user reaches the Deploy page and the > bp can be used to install a cluster later on. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20944) Ambari installer UI support for blueprint
Di Li created AMBARI-20944: -- Summary: Ambari installer UI support for blueprint Key: AMBARI-20944 URL: https://issues.apache.org/jira/browse/AMBARI-20944 Project: Ambari Issue Type: New Feature Components: ambari-web Affects Versions: trunk Reporter: Di Li Assignee: Amruta Borkar Fix For: trunk Currently, blueprint based install is a REST API operation, the JIRA here contains a series of UI-based improvements for better user experience with blueprints. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20698) Ability to export blueprint via Ambari installer UI
[ https://issues.apache.org/jira/browse/AMBARI-20698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-20698: --- Issue Type: Task (was: New Feature) > Ability to export blueprint via Ambari installer UI > --- > > Key: AMBARI-20698 > URL: https://issues.apache.org/jira/browse/AMBARI-20698 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: trunk >Reporter: Di Li >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20698.patch, Generate blueprint via Ambari > Installer UI - v2.pdf > > > UI be able to export a blueprint when a user reaches the Deploy page and the > bp can be used to install a cluster later on. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20941) UI Deploy: On enabling hive interactive query, value of 'Number of nodes used by Hive's LLAP' becomes invalid
[ https://issues.apache.org/jira/browse/AMBARI-20941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15998502#comment-15998502 ] Hudson commented on AMBARI-20941: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7431 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7431/]) AMBARI-20941 UI Deploy: On enabling hive interactive query, value of (ababiichuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=57359c930fb3efea0e319f208b6784e1377ba8f3]) * (edit) ambari-web/test/views/common/configs/widgets/slider_config_widget_view_test.js * (edit) ambari-web/app/views/common/configs/widgets/slider_config_widget_view.js > UI Deploy: On enabling hive interactive query, value of 'Number of nodes used > by Hive's LLAP' becomes invalid > - > > Key: AMBARI-20941 > URL: https://issues.apache.org/jira/browse/AMBARI-20941 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Blocker > Fix For: 2.5.1 > > Attachments: AMBARI-20941.patch > > > After enabling Hive Interactive query, the value of "Number of nodes used by > Hive's LLAP" becomes invalid. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20943) Hive View 1.5 and 2.0 result with special characters are being printed as ?
[
https://issues.apache.org/jira/browse/AMBARI-20943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
JaySenSharma updated AMBARI-20943:
--
Attachment: Issue1.png
> Hive View 1.5 and 2.0 result with special characters are being printed as ?
> ---
>
> Key: AMBARI-20943
> URL: https://issues.apache.org/jira/browse/AMBARI-20943
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
> Environment: All
>Reporter: JaySenSharma
> Attachments: Issue1.png
>
>
> - Hive View result panel is not showing special character data properly. The
> special characters are being replaced with ?
> Example: Run the following queries from Hive View 1.5/2.0 in Ambari 2.5 and
> then check the result section.
> {code}
> CREATE TABLE IF NOT EXISTS customerinfo (address string) ROW FORMAT SERDE
> 'org.apache.hadoop.hive.serde2.lazy.LazySimpleSerDe' WITH
> SERDEPROPERTIES("serialization.encoding"='UTF-8','store.charset'='UTF-8',
> 'retrieve.charset'='UTF-8');
> INSERT INTO customerinfo VALUES ("Envägen");
> SELECT * FROM customerinfo;
> {code}
> - Result is printed as following:
> {code}
> Env�gen
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20943) Hive View 1.5 and 2.0 result with special characters are being printed as ?
[
https://issues.apache.org/jira/browse/AMBARI-20943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15998485#comment-15998485
]
JaySenSharma commented on AMBARI-20943:
---
The hiveserver2.log shows the data was inserted properly:
{code}
hiveserver2.log shows:
2017-05-05 02:51:09,802 INFO [HiveServer2-Background-Pool: Thread-263]:
ql.Driver (Driver.java:execute(1411)) - Starting
command(queryId=hive_20170505025109_812f399d-a3bb-4224-959f-2c962d4e8492):
INSERT INTO customerinfo VALUES ("Envägen")
2017-05-05 02:51:20,017 INFO [HiveServer2-Background-Pool: Thread-263]:
exec.Task (TezTask.java:build(323)) - Dag name: INSERT INTO customerinfo VALUES
("Envägen")(Stage-1)
2017-05-05 02:51:20,242 INFO [HiveServer2-Background-Pool: Thread-263]:
client.TezClient (TezClient.java:submitDAGSession(429)) - Submitting dag to
TezSession, sessionName=HIVE-6eddd621-2b46-4598-bfa7-a435686f236b,
applicationId=application_1493948525801_0001, dagName=INSERT INTO customerinfo
VALUES ("Envägen")(Stage-1), callerContext={ context=HIVE,
callerType=HIVE_QUERY_ID,
callerId=hive_20170505025109_812f399d-a3bb-4224-959f-2c962d4e8492 }
2017-05-05 02:51:20,242 INFO [HiveServer2-Background-Pool: Thread-263]:
client.TezClient (TezClient.java:submitDAGSession(429)) - Submitting dag to
TezSession, sessionName=HIVE-6eddd621-2b46-4598-bfa7-a435686f236b,
applicationId=application_1493948525801_0001, dagName=INSERT INTO customerinfo
VALUES ("Envägen")(Stage-1), callerContext={ context=HIVE,
callerType=HIVE_QUERY_ID,
callerId=hive_20170505025109_812f399d-a3bb-4224-959f-2c962d4e8492 }
2017-05-05 02:51:20,595 INFO [HiveServer2-Background-Pool: Thread-263]:
client.TezClient (TezClient.java:submitDAGSession(501)) - Submitted dag to
TezSession, sessionName=HIVE-6eddd621-2b46-4598-bfa7-a435686f236b,
applicationId=application_1493948525801_0001, dagName=INSERT INTO customerinfo
VALUES ("Envägen")(Stage-1)
2017-05-05 02:51:27,650 INFO [HiveServer2-Background-Pool: Thread-285]:
ql.Driver (Driver.java:execute(1411)) - Starting
command(queryId=hive_20170505025127_56a8c52a-c257-4d33-bbe4-36c4eac82bba):
SELECT * FROM customerinfo
{code}
Attaching screenshots of HiveView 2.0
> Hive View 1.5 and 2.0 result with special characters are being printed as ?
> ---
>
> Key: AMBARI-20943
> URL: https://issues.apache.org/jira/browse/AMBARI-20943
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
> Environment: All
>Reporter: JaySenSharma
> Attachments: Issue1.png
>
>
> - Hive View result panel is not showing special character data properly. The
> special characters are being replaced with ?
> Example: Run the following queries from Hive View 1.5/2.0 in Ambari 2.5 and
> then check the result section.
> {code}
> CREATE TABLE IF NOT EXISTS customerinfo (address string) ROW FORMAT SERDE
> 'org.apache.hadoop.hive.serde2.lazy.LazySimpleSerDe' WITH
> SERDEPROPERTIES("serialization.encoding"='UTF-8','store.charset'='UTF-8',
> 'retrieve.charset'='UTF-8');
> INSERT INTO customerinfo VALUES ("Envägen");
> SELECT * FROM customerinfo;
> {code}
> - Result is printed as following:
> {code}
> Env�gen
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20943) Hive View 1.5 and 2.0 result with special characters are being printed as ?
JaySenSharma created AMBARI-20943:
-
Summary: Hive View 1.5 and 2.0 result with special characters are
being printed as ?
Key: AMBARI-20943
URL: https://issues.apache.org/jira/browse/AMBARI-20943
Project: Ambari
Issue Type: Bug
Components: ambari-views
Affects Versions: 2.5.0
Environment: All
Reporter: JaySenSharma
- Hive View result panel is not showing special character data properly. The
special characters are being replaced with ?
Example: Run the following queries from Hive View 1.5/2.0 in Ambari 2.5 and
then check the result section.
{code}
CREATE TABLE IF NOT EXISTS customerinfo (address string) ROW FORMAT SERDE
'org.apache.hadoop.hive.serde2.lazy.LazySimpleSerDe' WITH
SERDEPROPERTIES("serialization.encoding"='UTF-8','store.charset'='UTF-8',
'retrieve.charset'='UTF-8');
INSERT INTO customerinfo VALUES ("Envägen");
SELECT * FROM customerinfo;
{code}
- Result is printed as following:
{code}
Env�gen
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20941) UI Deploy: On enabling hive interactive query, value of 'Number of nodes used by Hive's LLAP' becomes invalid
[ https://issues.apache.org/jira/browse/AMBARI-20941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15998477#comment-15998477 ] Hudson commented on AMBARI-20941: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1504 (See [https://builds.apache.org/job/Ambari-branch-2.5/1504/]) AMBARI-20941 UI Deploy: On enabling hive interactive query, value of (ababiichuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=f740a9fddf032bbb8f5d9df160e2561d9ea43c44]) * (edit) ambari-web/app/views/common/configs/widgets/slider_config_widget_view.js * (edit) ambari-web/test/views/common/configs/widgets/slider_config_widget_view_test.js > UI Deploy: On enabling hive interactive query, value of 'Number of nodes used > by Hive's LLAP' becomes invalid > - > > Key: AMBARI-20941 > URL: https://issues.apache.org/jira/browse/AMBARI-20941 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Blocker > Fix For: 2.5.1 > > Attachments: AMBARI-20941.patch > > > After enabling Hive Interactive query, the value of "Number of nodes used by > Hive's LLAP" becomes invalid. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20928) Ambari Views are failing to compile in 2.4.3
[ https://issues.apache.org/jira/browse/AMBARI-20928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15998456#comment-15998456 ] venkat commented on AMBARI-20928: - Committed to branch-2.4 > Ambari Views are failing to compile in 2.4.3 > > > Key: AMBARI-20928 > URL: https://issues.apache.org/jira/browse/AMBARI-20928 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.3 >Reporter: venkat >Assignee: venkat > Fix For: 2.4.3 > > Attachments: AMBARI-20928-branch-2.4.01.patch, > AMBARI-20928-branch-2.4.02.patch, AMBARI-20928-branch-2.4.patch > > > It looks like views are failing to compile due to dependent npm package > version upgrades. > So it would be good if we use yarn package manager instead of npm -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20928) Ambari Views are failing to compile in 2.4.3
[ https://issues.apache.org/jira/browse/AMBARI-20928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-20928: Resolution: Fixed Status: Resolved (was: Patch Available) > Ambari Views are failing to compile in 2.4.3 > > > Key: AMBARI-20928 > URL: https://issues.apache.org/jira/browse/AMBARI-20928 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.3 >Reporter: venkat >Assignee: venkat > Fix For: 2.4.3 > > Attachments: AMBARI-20928-branch-2.4.01.patch, > AMBARI-20928-branch-2.4.02.patch, AMBARI-20928-branch-2.4.patch > > > It looks like views are failing to compile due to dependent npm package > version upgrades. > So it would be good if we use yarn package manager instead of npm -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20939) HDP 3.0 TP - create service definition for Kafka with configs, kerberos, widgets, etc
[ https://issues.apache.org/jira/browse/AMBARI-20939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15998455#comment-15998455 ] Hudson commented on AMBARI-20939: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7430 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7430/]) AMBARI-20939. HDP 3.0 TP - create service definition for Kafka with (vbrodetskyi: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=3817ad5da2076a274ca9fa4674b6d9d704610cb2]) * (add) ambari-server/src/main/resources/common-services/KAFKA/0.10.0.3.0/package/templates/input.config-kafka.json.j2 * (add) ambari-server/src/main/resources/common-services/KAFKA/0.10.0.3.0/package/scripts/upgrade.py * (add) ambari-server/src/main/resources/common-services/KAFKA/0.10.0.3.0/package/scripts/service_check.py * (add) ambari-server/src/main/resources/common-services/KAFKA/0.10.0.3.0/package/templates/kafka_jaas.conf.j2 * (add) ambari-server/src/main/resources/common-services/KAFKA/0.10.0.3.0/configuration/kafka-env.xml * (add) ambari-server/src/main/resources/common-services/KAFKA/0.10.0.3.0/role_command_order.json * (add) ambari-server/src/main/resources/common-services/KAFKA/0.10.0.3.0/kerberos.json * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/KAFKA/metainfo.xml * (add) ambari-server/src/main/resources/common-services/KAFKA/0.10.0.3.0/alerts.json * (add) ambari-server/src/main/resources/common-services/KAFKA/0.10.0.3.0/configuration/ranger-kafka-audit.xml * (add) ambari-server/src/main/resources/common-services/KAFKA/0.10.0.3.0/configuration/ranger-kafka-policymgr-ssl.xml * (add) ambari-server/src/main/resources/common-services/KAFKA/0.10.0.3.0/package/scripts/kafka.py * (add) ambari-server/src/main/resources/common-services/KAFKA/0.10.0.3.0/package/scripts/utils.py * (add) ambari-server/src/main/resources/common-services/KAFKA/0.10.0.3.0/configuration/kafka-broker.xml * (add) ambari-server/src/main/resources/common-services/KAFKA/0.10.0.3.0/widgets.json * (add) ambari-server/src/main/resources/common-services/KAFKA/0.10.0.3.0/package/templates/kafka.conf.j2 * (add) ambari-server/src/main/resources/common-services/KAFKA/0.10.0.3.0/configuration/kafka-log4j.xml * (add) ambari-server/src/main/resources/common-services/KAFKA/0.10.0.3.0/configuration/kafka_jaas_conf.xml * (add) ambari-server/src/main/resources/common-services/KAFKA/0.10.0.3.0/package/scripts/setup_ranger_kafka.py * (add) ambari-server/src/main/resources/common-services/KAFKA/0.10.0.3.0/metrics.json * (add) ambari-server/src/main/resources/common-services/KAFKA/0.10.0.3.0/configuration/ranger-kafka-security.xml * (add) ambari-server/src/main/resources/common-services/KAFKA/0.10.0.3.0/package/scripts/params.py * (add) ambari-server/src/main/resources/common-services/KAFKA/0.10.0.3.0/configuration/ranger-kafka-plugin-properties.xml * (add) ambari-server/src/main/resources/common-services/KAFKA/0.10.0.3.0/package/templates/tools-log4j.properties.j2 * (add) ambari-server/src/main/resources/common-services/KAFKA/0.10.0.3.0/package/scripts/status_params.py * (add) ambari-server/src/main/resources/common-services/KAFKA/0.10.0.3.0/package/scripts/kafka_broker.py * (add) ambari-server/src/main/resources/common-services/KAFKA/0.10.0.3.0/metainfo.xml * (add) ambari-server/src/main/resources/common-services/KAFKA/0.10.0.3.0/package/templates/kafka_client_jaas.conf.j2 * (add) ambari-server/src/main/resources/common-services/KAFKA/0.10.0.3.0/configuration/kafka_client_jaas_conf.xml > HDP 3.0 TP - create service definition for Kafka with configs, kerberos, > widgets, etc > - > > Key: AMBARI-20939 > URL: https://issues.apache.org/jira/browse/AMBARI-20939 > 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-20939.patch > > > . -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20942) HDP 3.0 TP - create Service Advisor for Kafka
[ https://issues.apache.org/jira/browse/AMBARI-20942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-20942: --- Status: Patch Available (was: Open) > HDP 3.0 TP - create Service Advisor for Kafka > - > > Key: AMBARI-20942 > URL: https://issues.apache.org/jira/browse/AMBARI-20942 > 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-20942.patch > > > . -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20942) HDP 3.0 TP - create Service Advisor for Kafka
[ https://issues.apache.org/jira/browse/AMBARI-20942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-20942: --- Attachment: AMBARI-20942.patch > HDP 3.0 TP - create Service Advisor for Kafka > - > > Key: AMBARI-20942 > URL: https://issues.apache.org/jira/browse/AMBARI-20942 > 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-20942.patch > > > . -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20942) HDP 3.0 TP - create Service Advisor for Kafka
Vitaly Brodetskyi created AMBARI-20942: -- Summary: HDP 3.0 TP - create Service Advisor for Kafka Key: AMBARI-20942 URL: https://issues.apache.org/jira/browse/AMBARI-20942 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-20941) UI Deploy: On enabling hive interactive query, value of 'Number of nodes used by Hive's LLAP' becomes invalid
[ https://issues.apache.org/jira/browse/AMBARI-20941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-20941: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.5 > UI Deploy: On enabling hive interactive query, value of 'Number of nodes used > by Hive's LLAP' becomes invalid > - > > Key: AMBARI-20941 > URL: https://issues.apache.org/jira/browse/AMBARI-20941 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Blocker > Fix For: 2.5.1 > > Attachments: AMBARI-20941.patch > > > After enabling Hive Interactive query, the value of "Number of nodes used by > Hive's LLAP" becomes invalid. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20941) UI Deploy: On enabling hive interactive query, value of 'Number of nodes used by Hive's LLAP' becomes invalid
[
https://issues.apache.org/jira/browse/AMBARI-20941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15998443#comment-15998443
]
Hadoop QA commented on AMBARI-20941:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12866627/AMBARI-20941.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 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/11571//console
This message is automatically generated.
> UI Deploy: On enabling hive interactive query, value of 'Number of nodes used
> by Hive's LLAP' becomes invalid
> -
>
> Key: AMBARI-20941
> URL: https://issues.apache.org/jira/browse/AMBARI-20941
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.1
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Blocker
> Fix For: 2.5.1
>
> Attachments: AMBARI-20941.patch
>
>
> After enabling Hive Interactive query, the value of "Number of nodes used by
> Hive's LLAP" becomes invalid.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20941) UI Deploy: On enabling hive interactive query, value of 'Number of nodes used by Hive's LLAP' becomes invalid
[ https://issues.apache.org/jira/browse/AMBARI-20941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-20941: -- Status: Patch Available (was: Open) > UI Deploy: On enabling hive interactive query, value of 'Number of nodes used > by Hive's LLAP' becomes invalid > - > > Key: AMBARI-20941 > URL: https://issues.apache.org/jira/browse/AMBARI-20941 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Blocker > Fix For: 2.5.1 > > Attachments: AMBARI-20941.patch > > > After enabling Hive Interactive query, the value of "Number of nodes used by > Hive's LLAP" becomes invalid. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20941) UI Deploy: On enabling hive interactive query, value of 'Number of nodes used by Hive's LLAP' becomes invalid
[ https://issues.apache.org/jira/browse/AMBARI-20941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-20941: -- Attachment: AMBARI-20941.patch > UI Deploy: On enabling hive interactive query, value of 'Number of nodes used > by Hive's LLAP' becomes invalid > - > > Key: AMBARI-20941 > URL: https://issues.apache.org/jira/browse/AMBARI-20941 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Blocker > Fix For: 2.5.1 > > Attachments: AMBARI-20941.patch > > > After enabling Hive Interactive query, the value of "Number of nodes used by > Hive's LLAP" becomes invalid. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20940) Propagate Component versions and states to Service
[ https://issues.apache.org/jira/browse/AMBARI-20940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-20940: - Status: Patch Available (was: Open) > Propagate Component versions and states to Service > -- > > Key: AMBARI-20940 > URL: https://issues.apache.org/jira/browse/AMBARI-20940 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: trunk >Reporter: Jonathan Hurley >Assignee: Jonathan Hurley >Priority: Critical > Fix For: trunk > > Attachments: AMBARI-20940.patch > > > In order to make it simpler for the UI, the version and repo_state should be > propagated to the service level. Repo_versions should also move to the > service, from the component. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20940) Propagate Component versions and states to Service
[ https://issues.apache.org/jira/browse/AMBARI-20940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-20940: - Attachment: AMBARI-20940.patch > Propagate Component versions and states to Service > -- > > Key: AMBARI-20940 > URL: https://issues.apache.org/jira/browse/AMBARI-20940 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: trunk >Reporter: Jonathan Hurley >Assignee: Jonathan Hurley >Priority: Critical > Fix For: trunk > > Attachments: AMBARI-20940.patch > > > In order to make it simpler for the UI, the version and repo_state should be > propagated to the service level. Repo_versions should also move to the > service, from the component. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20366) Filter out kerberos rules in exported blueprint
[ https://issues.apache.org/jira/browse/AMBARI-20366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15998409#comment-15998409 ] Hudson commented on AMBARI-20366: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7429 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7429/]) AMBARI-20366. Filter out kerberos rules in exported blueprint (Amruta (smagyari: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=1aad067cff1601d3c0ddd1f019df0fa9eb442199]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessor.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/api/query/render/ClusterBlueprintRendererTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessorTest.java > Filter out kerberos rules in exported blueprint > --- > > Key: AMBARI-20366 > URL: https://issues.apache.org/jira/browse/AMBARI-20366 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20366.patch > > > If blueprint is exported from a kerberos enabled cluster Kerberos rules > export principal names which contain cluster name and Realm, this patch > filter out kerberos rules properties so that hardcoded cluster name and realm > are not exported. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20941) UI Deploy: On enabling hive interactive query, value of 'Number of nodes used by Hive's LLAP' becomes invalid
Andrii Babiichuk created AMBARI-20941: - Summary: UI Deploy: On enabling hive interactive query, value of 'Number of nodes used by Hive's LLAP' becomes invalid Key: AMBARI-20941 URL: https://issues.apache.org/jira/browse/AMBARI-20941 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.1 Reporter: Andrii Babiichuk Assignee: Andrii Babiichuk Priority: Blocker Fix For: 2.5.1 After enabling Hive Interactive query, the value of "Number of nodes used by Hive's LLAP" becomes invalid. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20939) HDP 3.0 TP - create service definition for Kafka with configs, kerberos, widgets, etc
[ https://issues.apache.org/jira/browse/AMBARI-20939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-20939: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk > HDP 3.0 TP - create service definition for Kafka with configs, kerberos, > widgets, etc > - > > Key: AMBARI-20939 > URL: https://issues.apache.org/jira/browse/AMBARI-20939 > 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-20939.patch > > > . -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20940) Propagate Component versions and states to Service
Jonathan Hurley created AMBARI-20940: Summary: Propagate Component versions and states to Service Key: AMBARI-20940 URL: https://issues.apache.org/jira/browse/AMBARI-20940 Project: Ambari Issue Type: Task Components: ambari-server Affects Versions: trunk Reporter: Jonathan Hurley Assignee: Jonathan Hurley Priority: Critical Fix For: trunk In order to make it simpler for the UI, the version and repo_state should be propagated to the service level. Repo_versions should also move to the service, from the component. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20932) Ranger plugin setup should handle Nifi service
[ https://issues.apache.org/jira/browse/AMBARI-20932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-20932: Attachment: AMBARI-20932.1.patch > Ranger plugin setup should handle Nifi service > -- > > Key: AMBARI-20932 > URL: https://issues.apache.org/jira/browse/AMBARI-20932 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.1 > > Attachments: AMBARI-20932.1.patch, AMBARI-20932.patch > > > Add support to enable Ranger Nifi plugin. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20366) Filter out kerberos rules in exported blueprint
[ https://issues.apache.org/jira/browse/AMBARI-20366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15998348#comment-15998348 ] Sandor Magyari commented on AMBARI-20366: - Committed to trunk. > Filter out kerberos rules in exported blueprint > --- > > Key: AMBARI-20366 > URL: https://issues.apache.org/jira/browse/AMBARI-20366 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20366.patch > > > If blueprint is exported from a kerberos enabled cluster Kerberos rules > export principal names which contain cluster name and Realm, this patch > filter out kerberos rules properties so that hardcoded cluster name and realm > are not exported. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20366) Filter out kerberos rules in exported blueprint
[ https://issues.apache.org/jira/browse/AMBARI-20366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Magyari updated AMBARI-20366: Resolution: Fixed Status: Resolved (was: Patch Available) > Filter out kerberos rules in exported blueprint > --- > > Key: AMBARI-20366 > URL: https://issues.apache.org/jira/browse/AMBARI-20366 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-20366.patch > > > If blueprint is exported from a kerberos enabled cluster Kerberos rules > export principal names which contain cluster name and Realm, this patch > filter out kerberos rules properties so that hardcoded cluster name and realm > are not exported. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20779) Create Ranger KMS HDFS audit folder as part of install
[
https://issues.apache.org/jira/browse/AMBARI-20779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-20779:
-
Attachment: AMBARI-20779-ADDENDUM.patch
> Create Ranger KMS HDFS audit folder as part of install
> --
>
> Key: AMBARI-20779
> URL: https://issues.apache.org/jira/browse/AMBARI-20779
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.1
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
> Fix For: 2.5.1
>
> Attachments: AMBARI-20779.1.patch, AMBARI-20779.2.patch,
> AMBARI-20779.3.patch, AMBARI-20779-ADDENDUM.patch,
> AMBARI-20779-branch-2.5-unit-test.patch, AMBARI-20779.patch,
> AMBARI-20779-trunk.1.patch, AMBARI-20779-trunk.2.patch,
> AMBARI-20779-trunk.3.patch, AMBARI-20779-trunk.patch,
> AMBARI-20779-trunk-unit-test.patch
>
>
> Create audit directory {{/ranger/audit/kms}} in hdfs, if
> {{xasecure.audit.destination.hdfs}} (Audit To HDFS) property is set to true.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20779) Create Ranger KMS HDFS audit folder as part of install
[
https://issues.apache.org/jira/browse/AMBARI-20779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-20779:
-
Attachment: (was: AMBARI-20779-ADDENDUM.patch)
> Create Ranger KMS HDFS audit folder as part of install
> --
>
> Key: AMBARI-20779
> URL: https://issues.apache.org/jira/browse/AMBARI-20779
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.1
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
> Fix For: 2.5.1
>
> Attachments: AMBARI-20779.1.patch, AMBARI-20779.2.patch,
> AMBARI-20779.3.patch, AMBARI-20779-branch-2.5-unit-test.patch,
> AMBARI-20779.patch, AMBARI-20779-trunk.1.patch, AMBARI-20779-trunk.2.patch,
> AMBARI-20779-trunk.3.patch, AMBARI-20779-trunk.patch,
> AMBARI-20779-trunk-unit-test.patch
>
>
> Create audit directory {{/ranger/audit/kms}} in hdfs, if
> {{xasecure.audit.destination.hdfs}} (Audit To HDFS) property is set to true.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20930) stackadvisor recommendations for atlas hooks should be disabled for external Atlas
[ https://issues.apache.org/jira/browse/AMBARI-20930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-20930: Attachment: AMBARI-20930-trunk.1.patch > stackadvisor recommendations for atlas hooks should be disabled for external > Atlas > -- > > Key: AMBARI-20930 > URL: https://issues.apache.org/jira/browse/AMBARI-20930 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.1 > > Attachments: AMBARI-20930-branck-2.5.patch, > AMBARI-20930-trunk.1.patch, AMBARI-20930-trunk.patch > > > In cases where Atlas is not setup on the cluster but the Atlas hooks are > enabled for external Atlas. > Ambari recommendations show to disable the Atlas hooks. > This behaviour needs to be changed to support externally used Atlas service. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20930) stackadvisor recommendations for atlas hooks should be disabled for external Atlas
[ https://issues.apache.org/jira/browse/AMBARI-20930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-20930: Attachment: (was: AMBARI-20930-trunk.1.patch) > stackadvisor recommendations for atlas hooks should be disabled for external > Atlas > -- > > Key: AMBARI-20930 > URL: https://issues.apache.org/jira/browse/AMBARI-20930 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.1 > > Attachments: AMBARI-20930-branck-2.5.patch, AMBARI-20930-trunk.patch > > > In cases where Atlas is not setup on the cluster but the Atlas hooks are > enabled for external Atlas. > Ambari recommendations show to disable the Atlas hooks. > This behaviour needs to be changed to support externally used Atlas service. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20930) stackadvisor recommendations for atlas hooks should be disabled for external Atlas
[ https://issues.apache.org/jira/browse/AMBARI-20930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-20930: Attachment: AMBARI-20930-trunk.1.patch > stackadvisor recommendations for atlas hooks should be disabled for external > Atlas > -- > > Key: AMBARI-20930 > URL: https://issues.apache.org/jira/browse/AMBARI-20930 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.1 > > Attachments: AMBARI-20930-branck-2.5.patch, AMBARI-20930-trunk.patch > > > In cases where Atlas is not setup on the cluster but the Atlas hooks are > enabled for external Atlas. > Ambari recommendations show to disable the Atlas hooks. > This behaviour needs to be changed to support externally used Atlas service. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20779) Create Ranger KMS HDFS audit folder as part of install
[
https://issues.apache.org/jira/browse/AMBARI-20779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-20779:
-
Attachment: (was: AMBARI-20779-ADDENDUM-trunk.patch)
> Create Ranger KMS HDFS audit folder as part of install
> --
>
> Key: AMBARI-20779
> URL: https://issues.apache.org/jira/browse/AMBARI-20779
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.1
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
> Fix For: 2.5.1
>
> Attachments: AMBARI-20779.1.patch, AMBARI-20779.2.patch,
> AMBARI-20779.3.patch, AMBARI-20779-ADDENDUM.patch,
> AMBARI-20779-branch-2.5-unit-test.patch, AMBARI-20779.patch,
> AMBARI-20779-trunk.1.patch, AMBARI-20779-trunk.2.patch,
> AMBARI-20779-trunk.3.patch, AMBARI-20779-trunk.patch,
> AMBARI-20779-trunk-unit-test.patch
>
>
> Create audit directory {{/ranger/audit/kms}} in hdfs, if
> {{xasecure.audit.destination.hdfs}} (Audit To HDFS) property is set to true.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20936) Users are not able to login to ambari UI after Ambari upgrade from 2.4.x to 2.5.0
[ https://issues.apache.org/jira/browse/AMBARI-20936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15997981#comment-15997981 ] Nitiraj Singh Rathore commented on AMBARI-20936: Instead of deleting entries from DB directly, used uninstalling. Did refactoring to take the DB related code out of the ViewRegistry (which is anyway growing very big and is live object which cannot be used during Upgrade process) to create ViewInstanceOperationHandler.java. > Users are not able to login to ambari UI after Ambari upgrade from 2.4.x to > 2.5.0 > - > > Key: AMBARI-20936 > URL: https://issues.apache.org/jira/browse/AMBARI-20936 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.1 > Environment: LDAP is configured. > Zeppline view is created and USE permission is given to users. >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.1 > > Attachments: AMBARI-20936_branch-2.5.patch, error.log > > > After upgrade from Ambari 2.4 to Ambari 2.5 when LDAP users try to login they > get error and are not able to login. > Attached is log snippet. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20936) Users are not able to login to ambari UI after Ambari upgrade from 2.4.x to 2.5.0
[ https://issues.apache.org/jira/browse/AMBARI-20936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-20936: --- Status: Patch Available (was: Open) > Users are not able to login to ambari UI after Ambari upgrade from 2.4.x to > 2.5.0 > - > > Key: AMBARI-20936 > URL: https://issues.apache.org/jira/browse/AMBARI-20936 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.1 > Environment: LDAP is configured. > Zeppline view is created and USE permission is given to users. >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.1 > > Attachments: AMBARI-20936_branch-2.5.patch, error.log > > > After upgrade from Ambari 2.4 to Ambari 2.5 when LDAP users try to login they > get error and are not able to login. > Attached is log snippet. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20936) Users are not able to login to ambari UI after Ambari upgrade from 2.4.x to 2.5.0
[ https://issues.apache.org/jira/browse/AMBARI-20936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-20936: --- Attachment: AMBARI-20936_branch-2.5.patch > Users are not able to login to ambari UI after Ambari upgrade from 2.4.x to > 2.5.0 > - > > Key: AMBARI-20936 > URL: https://issues.apache.org/jira/browse/AMBARI-20936 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.1 > Environment: LDAP is configured. > Zeppline view is created and USE permission is given to users. >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.1 > > Attachments: AMBARI-20936_branch-2.5.patch, error.log > > > After upgrade from Ambari 2.4 to Ambari 2.5 when LDAP users try to login they > get error and are not able to login. > Attached is log snippet. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20936) Users are not able to login to ambari UI after Ambari upgrade from 2.4.x to 2.5.0
[ https://issues.apache.org/jira/browse/AMBARI-20936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-20936: --- Fix Version/s: (was: 2.5.0) 2.5.1 > Users are not able to login to ambari UI after Ambari upgrade from 2.4.x to > 2.5.0 > - > > Key: AMBARI-20936 > URL: https://issues.apache.org/jira/browse/AMBARI-20936 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.1 > Environment: LDAP is configured. > Zeppline view is created and USE permission is given to users. >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.1 > > Attachments: error.log > > > After upgrade from Ambari 2.4 to Ambari 2.5 when LDAP users try to login they > get error and are not able to login. > Attached is log snippet. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20936) Users are not able to login to ambari UI after Ambari upgrade from 2.4.x to 2.5.0
[ https://issues.apache.org/jira/browse/AMBARI-20936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-20936: --- Affects Version/s: (was: 2.5.0) 2.5.1 > Users are not able to login to ambari UI after Ambari upgrade from 2.4.x to > 2.5.0 > - > > Key: AMBARI-20936 > URL: https://issues.apache.org/jira/browse/AMBARI-20936 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.1 > Environment: LDAP is configured. > Zeppline view is created and USE permission is given to users. >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.1 > > Attachments: error.log > > > After upgrade from Ambari 2.4 to Ambari 2.5 when LDAP users try to login they > get error and are not able to login. > Attached is log snippet. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
