[jira] [Commented] (AMBARI-24558) Add setup.py for ambari-commons (for pip)
[ https://issues.apache.org/jira/browse/AMBARI-24558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16599387#comment-16599387 ] Hudson commented on AMBARI-24558: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #214 (See [https://builds.apache.org/job/Ambari-branch-2.7/214/]) AMBARI-24558. ADDENDUM: add missing ambari_jinja2 modules + install (oleewere: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=c1b5c998d97e42929e91a8b23b71a803cb21d9ab]) * (edit) setup.py > Add setup.py for ambari-commons (for pip) > - > > Key: AMBARI-24558 > URL: https://issues.apache.org/jira/browse/AMBARI-24558 > Project: Ambari > Issue Type: Bug > Components: ambari-agent, ambari-server >Affects Versions: 3.0.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24558) Add setup.py for ambari-commons (for pip)
[ https://issues.apache.org/jira/browse/AMBARI-24558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16599383#comment-16599383 ] Hudson commented on AMBARI-24558: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9909 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9909/]) AMBARI-24558. ADDENDUM: add missing ambari_jinja2 modules + install (oleewere: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=4df6c5171a9b5c567feb95188152567889414d9f]) * (edit) setup.py > Add setup.py for ambari-commons (for pip) > - > > Key: AMBARI-24558 > URL: https://issues.apache.org/jira/browse/AMBARI-24558 > Project: Ambari > Issue Type: Bug > Components: ambari-agent, ambari-server >Affects Versions: 3.0.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24582) Ambari Alert - HiveServer2 Process - False negative in Certain Scenarios
[
https://issues.apache.org/jira/browse/AMBARI-24582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16599264#comment-16599264
]
Hudson commented on AMBARI-24582:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9908 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/9908/])
[AMBARI-24582] - Ambari Alert - HiveServer2 Process - False negative in
(jonathanhurley:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=a4b2901a9a16e356c230fb647471e099b2d965ba])
* (edit)
ambari-common/src/main/python/resource_management/libraries/functions/hive_check.py
> Ambari Alert - HiveServer2 Process - False negative in Certain Scenarios
>
>
> Key: AMBARI-24582
> URL: https://issues.apache.org/jira/browse/AMBARI-24582
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.2
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> The Hive Alert & Hive Service Check both share the same logic from
> {{hive_check}} which attempts to execute something similar to:
> {code}
> beeline -u '%s' %s -e ';' 2>&1| awk '{print}' | grep -i -e 'Connection
> refused' -e 'Invalid URL'"
> {code}
> This type of negative condition checking misses a lot of failures, such as
> permission problems and SSL/JKS problems. Instead, we should change this to a
> positive check.
> - Add the {{-n}} option to specify the hive user since the hive warehouse
> inode is protected. This option is ignored for Kerberos
> - Change the grep to look for positive conditions
> -- {code}
> Connecting to jdbc:hive2://c7403.ambari.apache.org:1/;transportMode=binary
> Connected to: Apache Hive (version 3.0.0.3.0.0.0-1553)
> Driver: Hive JDBC (version 3.0.0.3.0.0.0-1553)
> Transaction isolation: TRANSACTION_REPEATABLE_READ
> Beeline version 3.0.0.3.0.0.0-1553 by Apache Hive
> Closing: 0: jdbc:hive2://c7403.ambari.apache.org:1/;transportMode=binary
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24582) Ambari Alert - HiveServer2 Process - False negative in Certain Scenarios
[
https://issues.apache.org/jira/browse/AMBARI-24582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16599253#comment-16599253
]
Hudson commented on AMBARI-24582:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #213 (See
[https://builds.apache.org/job/Ambari-branch-2.7/213/])
[AMBARI-24582] - Ambari Alert - HiveServer2 Process - False negative in
(jonathanhurley:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=5cadc1d2ce6bc11e07f106c03466342a345919e4])
* (edit)
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/alerts/alert_hive_thrift_port.py
* (edit)
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/alerts/alert_hive_interactive_thrift_port.py
* (edit)
ambari-server/src/test/python/stacks/2.0.6/HIVE/test_hive_service_check.py
* (edit)
ambari-common/src/main/python/resource_management/libraries/functions/hive_check.py
> Ambari Alert - HiveServer2 Process - False negative in Certain Scenarios
>
>
> Key: AMBARI-24582
> URL: https://issues.apache.org/jira/browse/AMBARI-24582
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.2
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> The Hive Alert & Hive Service Check both share the same logic from
> {{hive_check}} which attempts to execute something similar to:
> {code}
> beeline -u '%s' %s -e ';' 2>&1| awk '{print}' | grep -i -e 'Connection
> refused' -e 'Invalid URL'"
> {code}
> This type of negative condition checking misses a lot of failures, such as
> permission problems and SSL/JKS problems. Instead, we should change this to a
> positive check.
> - Add the {{-n}} option to specify the hive user since the hive warehouse
> inode is protected. This option is ignored for Kerberos
> - Change the grep to look for positive conditions
> -- {code}
> Connecting to jdbc:hive2://c7403.ambari.apache.org:1/;transportMode=binary
> Connected to: Apache Hive (version 3.0.0.3.0.0.0-1553)
> Driver: Hive JDBC (version 3.0.0.3.0.0.0-1553)
> Transaction isolation: TRANSACTION_REPEATABLE_READ
> Beeline version 3.0.0.3.0.0.0-1553 by Apache Hive
> Closing: 0: jdbc:hive2://c7403.ambari.apache.org:1/;transportMode=binary
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24577) Services should display the "Stop" button if any of their components are started
[ https://issues.apache.org/jira/browse/AMBARI-24577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt resolved AMBARI-24577. -- Resolution: Fixed > Services should display the "Stop" button if any of their components are > started > > > Key: AMBARI-24577 > URL: https://issues.apache.org/jira/browse/AMBARI-24577 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: trunk > > Time Spent: 1h 20m > Remaining Estimate: 0h > > In Ambari 2.7, the "Stop" button for each service is only available if all > its components are started. This means that if any component is not started > (or down), the rest of the components must be stopped individually from every > host. > [!5516EB4E-F2A5-44DA-8A4A-453C40FDA0E4.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/162070/162070_5516EB4E-F2A5-44DA-8A4A-453C40FDA0E4.png] > > For services where one component cannot be started (for example, due to > memory limitations), stopping the service can be a very painful exercise. > Please enable the "stop" button to be triggered, if any component of a > service can be stopped. > Similarly for the Start button -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24577) Services should display the "Stop" button if any of their components are started
[ https://issues.apache.org/jira/browse/AMBARI-24577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-24577: - Fix Version/s: 2.7.2 > Services should display the "Stop" button if any of their components are > started > > > Key: AMBARI-24577 > URL: https://issues.apache.org/jira/browse/AMBARI-24577 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: trunk, 2.7.2 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > In Ambari 2.7, the "Stop" button for each service is only available if all > its components are started. This means that if any component is not started > (or down), the rest of the components must be stopped individually from every > host. > [!5516EB4E-F2A5-44DA-8A4A-453C40FDA0E4.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/162070/162070_5516EB4E-F2A5-44DA-8A4A-453C40FDA0E4.png] > > For services where one component cannot be started (for example, due to > memory limitations), stopping the service can be a very painful exercise. > Please enable the "stop" button to be triggered, if any component of a > service can be stopped. > Similarly for the Start button -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24582) Ambari Alert - HiveServer2 Process - False negative in Certain Scenarios
[
https://issues.apache.org/jira/browse/AMBARI-24582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley resolved AMBARI-24582.
--
Resolution: Fixed
> Ambari Alert - HiveServer2 Process - False negative in Certain Scenarios
>
>
> Key: AMBARI-24582
> URL: https://issues.apache.org/jira/browse/AMBARI-24582
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.2
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The Hive Alert & Hive Service Check both share the same logic from
> {{hive_check}} which attempts to execute something similar to:
> {code}
> beeline -u '%s' %s -e ';' 2>&1| awk '{print}' | grep -i -e 'Connection
> refused' -e 'Invalid URL'"
> {code}
> This type of negative condition checking misses a lot of failures, such as
> permission problems and SSL/JKS problems. Instead, we should change this to a
> positive check.
> - Add the {{-n}} option to specify the hive user since the hive warehouse
> inode is protected. This option is ignored for Kerberos
> - Change the grep to look for positive conditions
> -- {code}
> Connecting to jdbc:hive2://c7403.ambari.apache.org:1/;transportMode=binary
> Connected to: Apache Hive (version 3.0.0.3.0.0.0-1553)
> Driver: Hive JDBC (version 3.0.0.3.0.0.0-1553)
> Transaction isolation: TRANSACTION_REPEATABLE_READ
> Beeline version 3.0.0.3.0.0.0-1553 by Apache Hive
> Closing: 0: jdbc:hive2://c7403.ambari.apache.org:1/;transportMode=binary
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24577) Services should display the "Stop" button if any of their components are started
[ https://issues.apache.org/jira/browse/AMBARI-24577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16599157#comment-16599157 ] Hudson commented on AMBARI-24577: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9907 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9907/]) [AMBARI-24577] Services should display the Stop button if any of their (ishanbhatt.1989: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=dd5c769e516b9bd25c6c40db6bef16ca8ee16df7]) * (edit) ambari-web/test/controllers/main/service/item_test.js * (edit) ambari-web/app/controllers/main/service/item.js > Services should display the "Stop" button if any of their components are > started > > > Key: AMBARI-24577 > URL: https://issues.apache.org/jira/browse/AMBARI-24577 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: trunk > > Time Spent: 1h 20m > Remaining Estimate: 0h > > In Ambari 2.7, the "Stop" button for each service is only available if all > its components are started. This means that if any component is not started > (or down), the rest of the components must be stopped individually from every > host. > [!5516EB4E-F2A5-44DA-8A4A-453C40FDA0E4.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/162070/162070_5516EB4E-F2A5-44DA-8A4A-453C40FDA0E4.png] > > For services where one component cannot be started (for example, due to > memory limitations), stopping the service can be a very painful exercise. > Please enable the "stop" button to be triggered, if any component of a > service can be stopped. > Similarly for the Start button -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24577) Services should display the "Stop" button if any of their components are started
[ https://issues.apache.org/jira/browse/AMBARI-24577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16599148#comment-16599148 ] Hudson commented on AMBARI-24577: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #212 (See [https://builds.apache.org/job/Ambari-branch-2.7/212/]) [AMBARI-24577] Services should display the Stop button if any of their (ishanbhatt.1989: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=be87ee58c3bbd4f315d65836dc5d996211ba3463]) * (edit) ambari-web/app/controllers/main/service/item.js * (edit) ambari-web/test/controllers/main/service/item_test.js > Services should display the "Stop" button if any of their components are > started > > > Key: AMBARI-24577 > URL: https://issues.apache.org/jira/browse/AMBARI-24577 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: trunk > > Time Spent: 1h 20m > Remaining Estimate: 0h > > In Ambari 2.7, the "Stop" button for each service is only available if all > its components are started. This means that if any component is not started > (or down), the rest of the components must be stopped individually from every > host. > [!5516EB4E-F2A5-44DA-8A4A-453C40FDA0E4.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/162070/162070_5516EB4E-F2A5-44DA-8A4A-453C40FDA0E4.png] > > For services where one component cannot be started (for example, due to > memory limitations), stopping the service can be a very painful exercise. > Please enable the "stop" button to be triggered, if any component of a > service can be stopped. > Similarly for the Start button -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24582) Ambari Alert - HiveServer2 Process - False negative in Certain Scenarios
[
https://issues.apache.org/jira/browse/AMBARI-24582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-24582:
Labels: pull-request-available (was: )
> Ambari Alert - HiveServer2 Process - False negative in Certain Scenarios
>
>
> Key: AMBARI-24582
> URL: https://issues.apache.org/jira/browse/AMBARI-24582
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.2
>
>
> The Hive Alert & Hive Service Check both share the same logic from
> {{hive_check}} which attempts to execute something similar to:
> {code}
> beeline -u '%s' %s -e ';' 2>&1| awk '{print}' | grep -i -e 'Connection
> refused' -e 'Invalid URL'"
> {code}
> This type of negative condition checking misses a lot of failures, such as
> permission problems and SSL/JKS problems. Instead, we should change this to a
> positive check.
> - Add the {{-n}} option to specify the hive user since the hive warehouse
> inode is protected. This option is ignored for Kerberos
> - Change the grep to look for positive conditions
> -- {code}
> Connecting to jdbc:hive2://c7403.ambari.apache.org:1/;transportMode=binary
> Connected to: Apache Hive (version 3.0.0.3.0.0.0-1553)
> Driver: Hive JDBC (version 3.0.0.3.0.0.0-1553)
> Transaction isolation: TRANSACTION_REPEATABLE_READ
> Beeline version 3.0.0.3.0.0.0-1553 by Apache Hive
> Closing: 0: jdbc:hive2://c7403.ambari.apache.org:1/;transportMode=binary
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24582) Ambari Alert - HiveServer2 Process - False negative in Certain Scenarios
Jonathan Hurley created AMBARI-24582:
Summary: Ambari Alert - HiveServer2 Process - False negative in
Certain Scenarios
Key: AMBARI-24582
URL: https://issues.apache.org/jira/browse/AMBARI-24582
Project: Ambari
Issue Type: Bug
Affects Versions: 2.7.0
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Fix For: 2.7.2
The Hive Alert & Hive Service Check both share the same logic from
{{hive_check}} which attempts to execute something similar to:
{code}
beeline -u '%s' %s -e ';' 2>&1| awk '{print}' | grep -i -e 'Connection refused'
-e 'Invalid URL'"
{code}
This type of negative condition checking misses a lot of failures, such as
permission problems and SSL/JKS problems. Instead, we should change this to a
positive check.
- Add the {{-n}} option to specify the hive user since the hive warehouse inode
is protected. This option is ignored for Kerberos
- Change the grep to look for positive conditions
-- {code}
Connecting to jdbc:hive2://c7403.ambari.apache.org:1/;transportMode=binary
Connected to: Apache Hive (version 3.0.0.3.0.0.0-1553)
Driver: Hive JDBC (version 3.0.0.3.0.0.0-1553)
Transaction isolation: TRANSACTION_REPEATABLE_READ
Beeline version 3.0.0.3.0.0.0-1553 by Apache Hive
Closing: 0: jdbc:hive2://c7403.ambari.apache.org:1/;transportMode=binary
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24537) Use Mpack Instance Manager To Switch Component Instance Version on Upgrade
[
https://issues.apache.org/jira/browse/AMBARI-24537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley resolved AMBARI-24537.
--
Resolution: Fixed
> Use Mpack Instance Manager To Switch Component Instance Version on Upgrade
> --
>
> Key: AMBARI-24537
> URL: https://issues.apache.org/jira/browse/AMBARI-24537
> Project: Ambari
> Issue Type: Task
>Affects Versions: 3.0.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 3.0.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Mpacks will not continue use the {{stack-select}} tools which have been used
> by various stacks over the past few years. Previously, each stack shipped a
> tool which would manipulate the symlinks on the file system in order to both
> report versions for components and to change versions during an upgrade.
> The following pieces were required for this old framework:
> - A file, such as {{stack_packages.json}} which provided a mapping between
> Ambari's component name and the symlink name on the file system.
> - Each component's Python file would need code which flips the version before
> restarting during an upgrade:
> {code}
> def pre_upgrade_restart(self, env, upgrade_type=None):
> if params.version and check_stack_feature(StackFeature.ROLLING_UPGRADE,
> format_stack_version(params.version)):
> stack_select.select_packages(params.version)
> {code}
> Mpacks v2 will instead use the mpack instance manager to change the pointer
> on the file system:
> {noformat}
> /usr/hwx/mpacks
> └── hdpcore
> ├── 1.0.0-b575
> │ ├── zookeeper_client -> /usr/hwx/modules/zookeeper_clients/3.4.0.0-b42
> │ └── zookeeper_server -> /usr/hwx/modules/zookeeper/3.4.0.0-b42
> └── 1.0.0-b580
> ├── zookeeper_client -> /usr/hwx/modules/zookeeper_clients/3.4.0.0-b43
> └── zookeeper_server -> /usr/hwx/modules/zookeeper_clients/3.4.0.0-b43
> {noformat}
> {noformat}
> /usr/hwx/instances
> └── hdpcore
> └── HDPCORE
> └── default
> ├── zookeeper
> │ └── zookeeper_server
> │ └── ZK-1
> │ ├── current ->
> /usr/hwx/mpacks/hdpcore/1.0.0-b575/zookeeper_server
> └── zookeeper_client
> ├── current ->
> /usr/hwx/mpacks/hdpcore/1.0.0-b575/zookeeper_client
> {noformat}
> For each instance of a component, there is a {{current}} pointer which
> references the mpack (and indirectly) the module version. However, Ambari
> knows all of this information up front since it's all based on metadata
> contained with the {{mpack.json}}. Therefore, it is possible for Ambari to do
> all of this version linking inside of its own framework during the upgrade.
> The individual Python scripts will no longer have to perform these actions.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24579) Wrong Ambari Alert of HiveServer2 Process critical due to unescaped password of keystore
[
https://issues.apache.org/jira/browse/AMBARI-24579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-24579:
Labels: pull-request-available (was: )
> Wrong Ambari Alert of HiveServer2 Process critical due to unescaped password
> of keystore
>
>
> Key: AMBARI-24579
> URL: https://issues.apache.org/jira/browse/AMBARI-24579
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.2
> Environment: Ambari 2.6.2.2
> HDP 2.6.5.0
>Reporter: Christian Danner
>Priority: Minor
> Labels: pull-request-available
>
> After Enabling SSL for Hive Server 2, Ambari Alerts showing "HiveServer2
> Process critical".
> When the keystore passphrase is having spacial characters like '(', ')' ,
> '\{' or '}' the alert in Ambari is triggered and the following traceback is
> shown:
>
> {code:java}
> Connection failed on host hive.server2.example.com:1 (Traceback (most
> recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/alerts/alert_hive_thrift_port.py",
> line 212, in execute
> ldap_password=ldap_password)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/functions/hive_check.py",
> line 81, in check_thrift_port_sasl
> timeout_kill_strategy=TerminateStrategy.KILL_PROCESS_TREE,
> File "/usr/lib/ambari-agent/lib/resource_management/core/base.py", line 166,
> in __init__
> self.env.run()
> File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/ambari-agent/lib/resource_management/core/providers/system.py",
> line 262, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line 72,
> in inner
> result = function(command, **kwargs)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line 102,
> in checked_call
> tries=tries, try_sleep=try_sleep, timeout_kill_strategy=timeout_kill_strategy)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line 150,
> in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line 303,
> in _call
> raise ExecutionFailed(err_msg, code, out, err)
> ExecutionFailed: Execution of '! beeline -u
> 'jdbc:hive2://hive.server2.example.com:1/;transportMode=binary;ssl=true;sslTrustStore=/path/to/my/keystore.jks;trustStorePassword=[PROTECTED]'
> -e '' 2>&1| awk '{print}'|grep -i -e 'Connection refused' -e 'Invalid URL''
> returned 1. -bash: -c: line 0: syntax error near unexpected token `('
> -bash: -c: line 0: `export
> PATH='/usr/sbin:/sbin:/usr/lib/ambari-server/*:/usr/sbin:/sbin:/usr/lib/ambari-server/*:/sbin:/usr/sbin:/usr/local/sbin:/root/bin:/usr/local/bin:/usr/bin:/bin:/usr/games:/usr/lib/mit/bin:/var/lib/ambari-agent:/var/lib/ambari-agent:/bin/:/usr/bin/:/usr/lib/hive/bin/:/usr/sbin/'
> ; ! beeline -u
> 'jdbc:hive2://hive.server2.example.com:1/;transportMode=binary;ssl=true;sslTrustStore=/path/to/my/keystore.jks;trustStorePassword=[PROTECTED]'
> -e '' 2>&1| awk '{print}'|grep -i -e 'Connection refused' -e 'Invalid URL''
> )
> {code}
> Therefore I am suggesting that the password should be escaped before handing
> over to bash in the following file:
> {code:java}
> /usr/lib/ambari-agent/lib/resource_management/libraries/functions/hive_check.py
> {code}
> Line 60:
> {code:java}
> beeline_url.extend(['ssl={ssl_str}', 'sslTrustStore={ssl_keystore}',
> 'trustStorePassword={ssl_password!p}'])
> {code}
> should be replaced to this:
> {code:java}
> beeline_url.extend(['ssl={ssl_str}', 'sslTrustStore={ssl_keystore}',
> 'trustStorePassword=\'{ssl_password!p}\''])
> {code}
> This solved my problem on my cluster.
>
> Since I am new to the community and don't know the process and was not able
> to find the right repository to change it I am going this way by explaining
> my solution.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24578) Quicklinks URL overflow outside the UI box
[ https://issues.apache.org/jira/browse/AMBARI-24578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16599007#comment-16599007 ] Hudson commented on AMBARI-24578: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9906 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9906/]) AMBARI-24578 Quicklinks URL overflow outside the UI box (1963907+atkach: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=e3db41df1888d1b7f0e524760700cd94ee106d66]) * (edit) ambari-web/app/styles/application.less > Quicklinks URL overflow outside the UI box > -- > > Key: AMBARI-24578 > URL: https://issues.apache.org/jira/browse/AMBARI-24578 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.1 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.2 > > Attachments: quicklinks.png > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Quicklinks in HDI environment are overflowing in UI. See attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24581) Enable Oozie SSL config setup with hidden password
[
https://issues.apache.org/jira/browse/AMBARI-24581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-24581:
Labels: pull-request-available (was: )
> Enable Oozie SSL config setup with hidden password
> --
>
> Key: AMBARI-24581
> URL: https://issues.apache.org/jira/browse/AMBARI-24581
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Affects Versions: 2.6.2
> Environment: Ambari 2.6.2.2
> HDP 2.6.5.0
>Reporter: Christian Danner
>Priority: Minor
> Labels: pull-request-available
>
> Currently it is not possible to enable Oozie SSL with all parameters being
> entered in Ambari without showing the password for the keystore in clear text
> in the oozie-env file.
> Since non admin users should be able to get on Ambari to use e.g. Ambari
> Views, users are able to see the configuration. With the keystore password in
> clear text in the oozie-env file this is no desired approach.
> Therefore I suggest three new variables in the oozie-site.xml.
> {code:java}
>
> oozie.https.port
> 11443
> Oozie HTTPS Port
> Oozie HTTPS Port
>
>
>
> oozie.https.keystore.file
>
> Oozie HTTPS Keystore
> Keystore to be used for SSL
>
>
>
> oozie.https.keystore.pass
>
> Oozie HTTPS Keystore Passphrase
> PASSWORD
> Passphrase to be used for the provided keystore
>
>
> {code}
> The params_linux.py should be able to read those variables in.
> {code:java}
> oozie_https_port = config['configurations']['oozie-site']['oozie.https.port']
> oozie_https_keystore_file =
> config['configurations']['oozie-site']['oozie.https.keystore.file']
> oozie_https_keystore_pass =
> config['configurations']['oozie-site']['oozie.https.keystore.pass']
> {code}
> After all the oozie-env.sh should have an extension in case all three
> varables are set in oozie-site.xml that the environment variables are being
> set.
> {code:java}
> {% if oozie_https_port and oozie_https_keystore_file and
> oozie_https_keystore_pass%}
> # Export SSL Config
> export OOZIE_HTTPS_PORT={{oozie_https_port}}
> export OOZIE_HTTPS_KEYSTORE_FILE={{oozie_https_keystore_file}}
> export OOZIE_HTTPS_KEYSTORE_PASS='{{oozie_https_keystore_pass}}'
> {% endif %}
> {code}
> With this approach it is possible to hide the password within the UI of
> Ambari and also use Oozie with HTTPS enabled.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24578) Quicklinks URL overflow outside the UI box
[ https://issues.apache.org/jira/browse/AMBARI-24578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16598997#comment-16598997 ] Hudson commented on AMBARI-24578: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #211 (See [https://builds.apache.org/job/Ambari-branch-2.7/211/]) AMBARI-24578 Quicklinks URL overflow outside the UI box (1963907+atkach: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=6ccb8e6d314d1429802dc06d11513df0169ccff8]) * (edit) ambari-web/app/styles/application.less > Quicklinks URL overflow outside the UI box > -- > > Key: AMBARI-24578 > URL: https://issues.apache.org/jira/browse/AMBARI-24578 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.1 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.2 > > Attachments: quicklinks.png > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Quicklinks in HDI environment are overflowing in UI. See attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24578) Quicklinks URL overflow outside the UI box
[ https://issues.apache.org/jira/browse/AMBARI-24578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach resolved AMBARI-24578. --- Resolution: Fixed > Quicklinks URL overflow outside the UI box > -- > > Key: AMBARI-24578 > URL: https://issues.apache.org/jira/browse/AMBARI-24578 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.1 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.2 > > Attachments: quicklinks.png > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Quicklinks in HDI environment are overflowing in UI. See attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24578) Quicklinks URL overflow outside the UI box
[ https://issues.apache.org/jira/browse/AMBARI-24578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16598944#comment-16598944 ] Andrii Tkach commented on AMBARI-24578: --- committed to trunk and branch-2.7 > Quicklinks URL overflow outside the UI box > -- > > Key: AMBARI-24578 > URL: https://issues.apache.org/jira/browse/AMBARI-24578 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.1 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.2 > > Attachments: quicklinks.png > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Quicklinks in HDI environment are overflowing in UI. See attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24581) Enable Oozie SSL config setup with hidden password
Christian Danner created AMBARI-24581:
-
Summary: Enable Oozie SSL config setup with hidden password
Key: AMBARI-24581
URL: https://issues.apache.org/jira/browse/AMBARI-24581
Project: Ambari
Issue Type: Improvement
Components: ambari-server
Affects Versions: 2.6.2
Environment: Ambari 2.6.2.2
HDP 2.6.5.0
Reporter: Christian Danner
Currently it is not possible to enable Oozie SSL with all parameters being
entered in Ambari without showing the password for the keystore in clear text
in the oozie-env file.
Since non admin users should be able to get on Ambari to use e.g. Ambari Views,
users are able to see the configuration. With the keystore password in clear
text in the oozie-env file this is no desired approach.
Therefore I suggest three new variables in the oozie-site.xml.
{code:java}
oozie.https.port
11443
Oozie HTTPS Port
Oozie HTTPS Port
oozie.https.keystore.file
Oozie HTTPS Keystore
Keystore to be used for SSL
oozie.https.keystore.pass
Oozie HTTPS Keystore Passphrase
PASSWORD
Passphrase to be used for the provided keystore
{code}
The params_linux.py should be able to read those variables in.
{code:java}
oozie_https_port = config['configurations']['oozie-site']['oozie.https.port']
oozie_https_keystore_file =
config['configurations']['oozie-site']['oozie.https.keystore.file']
oozie_https_keystore_pass =
config['configurations']['oozie-site']['oozie.https.keystore.pass']
{code}
After all the oozie-env.sh should have an extension in case all three varables
are set in oozie-site.xml that the environment variables are being set.
{code:java}
{% if oozie_https_port and oozie_https_keystore_file and
oozie_https_keystore_pass%}
# Export SSL Config
export OOZIE_HTTPS_PORT={{oozie_https_port}}
export OOZIE_HTTPS_KEYSTORE_FILE={{oozie_https_keystore_file}}
export OOZIE_HTTPS_KEYSTORE_PASS='{{oozie_https_keystore_pass}}'
{% endif %}
{code}
With this approach it is possible to hide the password within the UI of Ambari
and also use Oozie with HTTPS enabled.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-22847) HBase should handle a customized Zookeeper service principal name
[
https://issues.apache.org/jira/browse/AMBARI-22847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16598749#comment-16598749
]
Hudson commented on AMBARI-22847:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #210 (See
[https://builds.apache.org/job/Ambari-branch-2.7/210/])
AMBARI-22847. Let HBase use ZK principal name set by users when enabling
(github:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=0d18dace6fe17a9a098eb2f763351601af9f07b5])
* (edit)
ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/configuration/hbase-env.xml
* (edit)
ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/package/scripts/params_linux.py
> HBase should handle a customized Zookeeper service principal name
> -
>
> Key: AMBARI-22847
> URL: https://issues.apache.org/jira/browse/AMBARI-22847
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Sandor Molnar
>Assignee: Sandor Molnar
>Priority: Critical
> Labels: kerberos, pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> HBase should handle a customized Zookeeper service principal name.
> Currently this is not supported due to hardcoded and implicit values
> expecting the Zookeeper service principal name to be {{zookeeper/_HOST}} as
> opposed to something like {{zookeeper-mycluster/_HOST}}.
> The following changes need to be made:
> * Add {{-Dzookeeper.sasl.client.username=}} to
> {{HBASE_OPTS}} in {{hbase-env/template}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24580) [Log Search UI] Change the fix with and the height for the modal to flexible layout
Istvan Tobias created AMBARI-24580: -- Summary: [Log Search UI] Change the fix with and the height for the modal to flexible layout Key: AMBARI-24580 URL: https://issues.apache.org/jira/browse/AMBARI-24580 Project: Ambari Issue Type: Bug Components: ambari-logsearch, logsearch Affects Versions: 2.7.0 Reporter: Istvan Tobias Assignee: Istvan Tobias The modals have fixed with and height and it can make the app difficult to use. So the modals should be flexible enough to be visible everytime. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24579) Wrong Ambari Alert of HiveServer2 Process critical due to unescaped password of keystore
Christian Danner created AMBARI-24579:
-
Summary: Wrong Ambari Alert of HiveServer2 Process critical due to
unescaped password of keystore
Key: AMBARI-24579
URL: https://issues.apache.org/jira/browse/AMBARI-24579
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.6.2
Environment: Ambari 2.6.2.2
HDP 2.6.5.0
Reporter: Christian Danner
After Enabling SSL for Hive Server 2, Ambari Alerts showing "HiveServer2
Process critical".
When the keystore passphrase is having spacial characters like '(', ')' , '\{'
or '}' the alert in Ambari is triggered and the following traceback is shown:
{code:java}
Connection failed on host hive.server2.example.com:1 (Traceback (most
recent call last):
File
"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/alerts/alert_hive_thrift_port.py",
line 212, in execute
ldap_password=ldap_password)
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/functions/hive_check.py",
line 81, in check_thrift_port_sasl
timeout_kill_strategy=TerminateStrategy.KILL_PROCESS_TREE,
File "/usr/lib/ambari-agent/lib/resource_management/core/base.py", line 166, in
__init__
self.env.run()
File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py", line
160, in run
self.run_action(resource, action)
File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py", line
124, in run_action
provider_action()
File "/usr/lib/ambari-agent/lib/resource_management/core/providers/system.py",
line 262, in action_run
tries=self.resource.tries, try_sleep=self.resource.try_sleep)
File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line 72, in
inner
result = function(command, **kwargs)
File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line 102,
in checked_call
tries=tries, try_sleep=try_sleep, timeout_kill_strategy=timeout_kill_strategy)
File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line 150,
in _call_wrapper
result = _call(command, **kwargs_copy)
File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line 303,
in _call
raise ExecutionFailed(err_msg, code, out, err)
ExecutionFailed: Execution of '! beeline -u
'jdbc:hive2://hive.server2.example.com:1/;transportMode=binary;ssl=true;sslTrustStore=/path/to/my/keystore.jks;trustStorePassword=[PROTECTED]'
-e '' 2>&1| awk '{print}'|grep -i -e 'Connection refused' -e 'Invalid URL''
returned 1. -bash: -c: line 0: syntax error near unexpected token `('
-bash: -c: line 0: `export
PATH='/usr/sbin:/sbin:/usr/lib/ambari-server/*:/usr/sbin:/sbin:/usr/lib/ambari-server/*:/sbin:/usr/sbin:/usr/local/sbin:/root/bin:/usr/local/bin:/usr/bin:/bin:/usr/games:/usr/lib/mit/bin:/var/lib/ambari-agent:/var/lib/ambari-agent:/bin/:/usr/bin/:/usr/lib/hive/bin/:/usr/sbin/'
; ! beeline -u
'jdbc:hive2://hive.server2.example.com:1/;transportMode=binary;ssl=true;sslTrustStore=/path/to/my/keystore.jks;trustStorePassword=[PROTECTED]'
-e '' 2>&1| awk '{print}'|grep -i -e 'Connection refused' -e 'Invalid URL''
)
{code}
Therefore I am suggesting that the password should be escaped before handing
over to bash in the following file:
{code:java}
/usr/lib/ambari-agent/lib/resource_management/libraries/functions/hive_check.py
{code}
Line 60:
{code:java}
beeline_url.extend(['ssl={ssl_str}', 'sslTrustStore={ssl_keystore}',
'trustStorePassword={ssl_password!p}'])
{code}
should be replaced to this:
{code:java}
beeline_url.extend(['ssl={ssl_str}', 'sslTrustStore={ssl_keystore}',
'trustStorePassword=\'{ssl_password!p}\''])
{code}
This solved my problem on my cluster.
Since I am new to the community and don't know the process and was not able to
find the right repository to change it I am going this way by explaining my
solution.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-21659) Remove obsolete security_state data
[ https://issues.apache.org/jira/browse/AMBARI-21659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Levas updated AMBARI-21659: -- Affects Version/s: (was: 3.0.0) 2.0.0 > Remove obsolete security_state data > --- > > Key: AMBARI-21659 > URL: https://issues.apache.org/jira/browse/AMBARI-21659 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Attila Magyar >Assignee: Attila Magyar >Priority: Major > Fix For: 2.7.0 > > Attachments: AMBARI-21659.patch > > > Remove the outdated security_state information from the Ambari server and the > Ambari database. > The following tables will be affected: > - hostcomponentdesiredstate > - hostcomponentstate > - servicedesiredstate -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-21659) Remove obsolete security_state data
[ https://issues.apache.org/jira/browse/AMBARI-21659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Levas updated AMBARI-21659: -- Fix Version/s: (was: 3.0.0) 2.7.0 > Remove obsolete security_state data > --- > > Key: AMBARI-21659 > URL: https://issues.apache.org/jira/browse/AMBARI-21659 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Attila Magyar >Assignee: Attila Magyar >Priority: Major > Fix For: 2.7.0 > > Attachments: AMBARI-21659.patch > > > Remove the outdated security_state information from the Ambari server and the > Ambari database. > The following tables will be affected: > - hostcomponentdesiredstate > - hostcomponentstate > - servicedesiredstate -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-21659) Remove obsolete security_state data
[ https://issues.apache.org/jira/browse/AMBARI-21659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Levas updated AMBARI-21659: -- Affects Version/s: (was: 2.0.0) 2.7.0 > Remove obsolete security_state data > --- > > Key: AMBARI-21659 > URL: https://issues.apache.org/jira/browse/AMBARI-21659 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Attila Magyar >Assignee: Attila Magyar >Priority: Major > Fix For: 2.7.0 > > Attachments: AMBARI-21659.patch > > > Remove the outdated security_state information from the Ambari server and the > Ambari database. > The following tables will be affected: > - hostcomponentdesiredstate > - hostcomponentstate > - servicedesiredstate -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24578) Quicklinks URL overflow outside the UI box
[ https://issues.apache.org/jira/browse/AMBARI-24578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24578: Labels: pull-request-available (was: ) > Quicklinks URL overflow outside the UI box > -- > > Key: AMBARI-24578 > URL: https://issues.apache.org/jira/browse/AMBARI-24578 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.1 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.2 > > Attachments: quicklinks.png > > > Quicklinks in HDI environment are overflowing in UI. See attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24228) Agent-side command-*.json files should optionally be deleted when no longer needed by the command
[
https://issues.apache.org/jira/browse/AMBARI-24228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-24228:
--
Description:
Agent-side _command JSON_ files ({{command-*.json}}, {{status_command.json}})
should optionally be deleted when no longer needed by the command. One reason
for this is to reduce the risk of leaking sensitive data stored at plaintext in
the _command JSON_ files.
Currently the _command JSON_ files are stored on disk in
/var/lib/ambari-agent/data. These files may be cleared out over time, but
there is a need to have them removed as soon as they are no longer needed.
To do this, a retention policy may be defined so that the Ambari agent behaves
accordingly:
* {{keep}}
** No automatic removal is performed
** This is the default behavior
* {{remove}}
** The _command JSON_ file are removed as soon as the command completes
* {{remove_on_success}}
** The _command JSON_ files are removed as soon as the command *successfully*
completes
** The _command JSON_ files are not removed on failure conditions
This value is to be set in the {{ambari-agent.ini}} file, typically found at
{{/etc/ambari-agent/conf/ambari-agent.ini}} using the
*{{command_file_retention_policy}}* property. After setting this property, the
agent needs to be restarted.
was:
Agent-side _command JSON_ files ({{command-*.json}}, {{status_command.json}})
should optionally be deleted when no longer needed by the command. One reason
for this is to reduce the risk of leaking sensitive data stored at plaintext in
the _command JSON_ files.
Currently the _command JSON_ files are stored on disk in
/var/lib/ambari-agent/data. These files may be cleared out over time, but
there is a need to have them removed as soon as they are no longer needed.
To do this, a retention policy may be defined so that the Ambari agent behaves
accordingly:
* {{keep}}
** No automatic removal is performed
** This is the default behavior
* {{remove}}
** The _command JSON_ file are remove as soon as the command completes
* {{remove_on_success}}
** The _command JSON_ files are remove as soon as the command *successfully*
completes
** The _command JSON_ files are not removed on failure conditions
> Agent-side command-*.json files should optionally be deleted when no longer
> needed by the command
> -
>
> Key: AMBARI-24228
> URL: https://issues.apache.org/jira/browse/AMBARI-24228
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.1.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 4h 50m
> Remaining Estimate: 0h
>
> Agent-side _command JSON_ files ({{command-*.json}}, {{status_command.json}})
> should optionally be deleted when no longer needed by the command. One
> reason for this is to reduce the risk of leaking sensitive data stored at
> plaintext in the _command JSON_ files.
> Currently the _command JSON_ files are stored on disk in
> /var/lib/ambari-agent/data. These files may be cleared out over time, but
> there is a need to have them removed as soon as they are no longer needed.
> To do this, a retention policy may be defined so that the Ambari agent
> behaves accordingly:
> * {{keep}}
> ** No automatic removal is performed
> ** This is the default behavior
> * {{remove}}
> ** The _command JSON_ file are removed as soon as the command completes
> * {{remove_on_success}}
> ** The _command JSON_ files are removed as soon as the command *successfully*
> completes
> ** The _command JSON_ files are not removed on failure conditions
> This value is to be set in the {{ambari-agent.ini}} file, typically found at
> {{/etc/ambari-agent/conf/ambari-agent.ini}} using the
> *{{command_file_retention_policy}}* property. After setting this property,
> the agent needs to be restarted.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24555) Nifi Registry install fails
[
https://issues.apache.org/jira/browse/AMBARI-24555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16598658#comment-16598658
]
Hudson commented on AMBARI-24555:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9905 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/9905/])
AMBARI-24555 Nifi Registry install fails. (ababiichuk) (ababiichuk:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=14811e4ff0049382e8f9496e9f3742ca0e141873])
* (edit) ambari-web/app/mixins/wizard/addSecurityConfigs.js
* (edit) ambari-web/test/mixins/wizard/addSeccurityConfigs_test.js
> Nifi Registry install fails
> ---
>
> Key: AMBARI-24555
> URL: https://issues.apache.org/jira/browse/AMBARI-24555
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.2
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Facing issue installing Nifi Registry on HDP_HDF cluster. The create keytab
> step in Ambari is failing during installation. Below exception is seen in
> ambari logs.
>
> {code}
> 2018-08-21 13:11:03,401 ERROR [Server Action Executor Worker 1305]
> CreatePrincipalsServerAction:309 - Failed to create principal, - Failed to
> create new principal - no principal specified
> org.apache.ambari.server.serveraction.kerberos.KerberosOperationException:
> Failed to create new principal - no principal specified
> at
> org.apache.ambari.server.serveraction.kerberos.MITKerberosOperationHandler.createPrincipal(MITKerberosOperationHandler.java:159)
> at
> org.apache.ambari.server.serveraction.kerberos.CreatePrincipalsServerAction.createPrincipal(CreatePrincipalsServerAction.java:268)
> at
> org.apache.ambari.server.serveraction.kerberos.CreatePrincipalsServerAction.processIdentity(CreatePrincipalsServerAction.java:157)
> at
> org.apache.ambari.server.serveraction.kerberos.KerberosServerAction.processIdentities(KerberosServerAction.java:460)
> at
> org.apache.ambari.server.serveraction.kerberos.CreatePrincipalsServerAction.execute(CreatePrincipalsServerAction.java:92)
> at
> org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.execute(ServerActionExecutor.java:550)
> at
> org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.run(ServerActionExecutor.java:466)
> at java.lang.Thread.run(Thread.java:748)
> 2018-08-21 13:11:03,401 INFO [Server Action Executor Worker 1305]
> KerberosServerAction:481 - Processing identities completed.
> 2018-08-21 13:11:04,191 ERROR [ambari-action-scheduler] ActionScheduler:482 -
> Operation completely failed, aborting request id: 117
> {code}
> The Ambari UI should not display any properties from Kerberos identity blocks
> that indicate they are referencing another Kerberos identity. There are 2
> ways we know this:
> - The new/preferred way: the identity block has a non-empty/non-null
> "reference" attribute
> - The old (backwards compatible way): the identity block has a "name"
> attribute the starts with a '/'.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24561) Update styles for pre-upgrade modals
[ https://issues.apache.org/jira/browse/AMBARI-24561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16598659#comment-16598659 ] Hudson commented on AMBARI-24561: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9905 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9905/]) AMBARI-24561 Update styles for pre-upgrade modals. (ababiichuk) (ababiichuk: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=6451f81783a11b9e159763d98df8a9691062ddc9]) * (edit) ambari-web/app/templates/common/modal_popups/cluster_check_dialog.hbs * (edit) ambari-web/app/templates/main/admin/stack_upgrade/upgrade_configs_recommend_table.hbs * (edit) ambari-web/app/views/common/modal_popups/cluster_check_popup.js * (edit) ambari-web/app/controllers/main/admin/stack_and_upgrade_controller.js * (edit) ambari-web/app/styles/stack_versions.less * (edit) ambari-web/app/templates/main/admin/stack_upgrade/upgrade_options.hbs * (edit) ambari-web/app/templates/main/admin/stack_upgrade/upgrade_configs_merge_table.hbs * (edit) ambari-web/app/templates/wizard/step8/step8_log_popup.hbs > Update styles for pre-upgrade modals > > > Key: AMBARI-24561 > URL: https://issues.apache.org/jira/browse/AMBARI-24561 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.1 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 40m > Remaining Estimate: 0h > > - Move 'Preparing the Upgrade' text from the corresponding modal to its header > - Upgrade Options popup: add some vertical padding between peragraphs > - Upgrade Options popup: center the contents of upgrade type blocks and add > more padding to them > - Make pre-upgrade checks popup wider > - Pre-upgrade checks popup: display warnings as regular text instead of well > blocks -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24555) Nifi Registry install fails
[
https://issues.apache.org/jira/browse/AMBARI-24555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16598631#comment-16598631
]
Hudson commented on AMBARI-24555:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #209 (See
[https://builds.apache.org/job/Ambari-branch-2.7/209/])
AMBARI-24555 Nifi Registry install fails. (ababiichuk) (ababiichuk:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=f1bd6b93159a799c38f7ffbe1bbaba815323038f])
* (edit) ambari-web/app/mixins/wizard/addSecurityConfigs.js
* (edit) ambari-web/test/mixins/wizard/addSeccurityConfigs_test.js
> Nifi Registry install fails
> ---
>
> Key: AMBARI-24555
> URL: https://issues.apache.org/jira/browse/AMBARI-24555
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.2
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Facing issue installing Nifi Registry on HDP_HDF cluster. The create keytab
> step in Ambari is failing during installation. Below exception is seen in
> ambari logs.
>
> {code}
> 2018-08-21 13:11:03,401 ERROR [Server Action Executor Worker 1305]
> CreatePrincipalsServerAction:309 - Failed to create principal, - Failed to
> create new principal - no principal specified
> org.apache.ambari.server.serveraction.kerberos.KerberosOperationException:
> Failed to create new principal - no principal specified
> at
> org.apache.ambari.server.serveraction.kerberos.MITKerberosOperationHandler.createPrincipal(MITKerberosOperationHandler.java:159)
> at
> org.apache.ambari.server.serveraction.kerberos.CreatePrincipalsServerAction.createPrincipal(CreatePrincipalsServerAction.java:268)
> at
> org.apache.ambari.server.serveraction.kerberos.CreatePrincipalsServerAction.processIdentity(CreatePrincipalsServerAction.java:157)
> at
> org.apache.ambari.server.serveraction.kerberos.KerberosServerAction.processIdentities(KerberosServerAction.java:460)
> at
> org.apache.ambari.server.serveraction.kerberos.CreatePrincipalsServerAction.execute(CreatePrincipalsServerAction.java:92)
> at
> org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.execute(ServerActionExecutor.java:550)
> at
> org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.run(ServerActionExecutor.java:466)
> at java.lang.Thread.run(Thread.java:748)
> 2018-08-21 13:11:03,401 INFO [Server Action Executor Worker 1305]
> KerberosServerAction:481 - Processing identities completed.
> 2018-08-21 13:11:04,191 ERROR [ambari-action-scheduler] ActionScheduler:482 -
> Operation completely failed, aborting request id: 117
> {code}
> The Ambari UI should not display any properties from Kerberos identity blocks
> that indicate they are referencing another Kerberos identity. There are 2
> ways we know this:
> - The new/preferred way: the identity block has a non-empty/non-null
> "reference" attribute
> - The old (backwards compatible way): the identity block has a "name"
> attribute the starts with a '/'.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24538) OneFS mpack quicklinks require port, https
[ https://issues.apache.org/jira/browse/AMBARI-24538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16598629#comment-16598629 ] Hudson commented on AMBARI-24538: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #209 (See [https://builds.apache.org/job/Ambari-branch-2.7/209/]) AMBARI-24538: OneFS mpack quicklinks require port, https (#2169) (#2221) (github: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=445157a3b77887fa5eaae2038cdffd4ac5b60f47]) * (edit) contrib/management-packs/isilon-onefs-mpack/src/main/resources/addon-services/ONEFS/1.0.0/quicklinks/quicklinks.json > OneFS mpack quicklinks require port, https > -- > > Key: AMBARI-24538 > URL: https://issues.apache.org/jira/browse/AMBARI-24538 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Robert Ketcherside >Priority: Major > Labels: pull-request-available > Time Spent: 1h 50m > Remaining Estimate: 0h > > Quicklinks for OneFS in the OneFS management pack currently have no port. > Normally that's okay because OneFS is configured by default to redirect port > 80 traffic to the management port, 8080. But if http file browse is enabled > (`isi http settings modify --service=enabled`), that uses port 80. We need to > point to port 8080. > Also, OneFS will redirect from http to https, but a 400 error appears > briefly. For better user experience the quicklinks should use https. > Both the onefs_web_ui and onefs_hdfs_web_ui need to be fixed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24525) Accumulo does not startup in Federated Cluster
[
https://issues.apache.org/jira/browse/AMBARI-24525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16598630#comment-16598630
]
Hudson commented on AMBARI-24525:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #209 (See
[https://builds.apache.org/job/Ambari-branch-2.7/209/])
AMBARI-24525 Accumulo does not startup in Federated Cluster. (ababiichuk:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=bfcec7bf72677785539eae5130ed56ed84877e06])
* (edit) ambari-web/app/data/configs/wizards/federation_properties.js
* (edit) ambari-web/app/controllers/main/admin/federation/step3_controller.js
* (edit) ambari-web/app/controllers/main/admin/federation/step4_controller.js
> Accumulo does not startup in Federated Cluster
> --
>
> Key: AMBARI-24525
> URL: https://issues.apache.org/jira/browse/AMBARI-24525
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.2
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> In a manually setup federated cluster (not through deployNG) --
> Accumulo was installed and when trying to start, below error thrown --
> {noformat}
> 2018-08-16 07:33:31,748 [start.Main] ERROR: Thread
> 'org.apache.accumulo.master.state.SetGoalState' died.
> java.lang.IllegalArgumentException: Expected fully qualified URI for
> instance.volumes got ns2/apps/accumulo/data
> at
> org.apache.accumulo.core.volume.VolumeConfiguration.getVolumeUris(VolumeConfiguration.java:107)
> at
> org.apache.accumulo.server.fs.VolumeManagerImpl.get(VolumeManagerImpl.java:334)
> {noformat}
> Caused by incorrect config value:
> {{instance.volumes = hdfs://ns1,ns2/apps/accumulo/data}}
> where ns1 and ns2 are namespaces
> Expected is --
> {{instance.volumes =
> hdfs://ns1/apps/accumulo/data,hdfs://ns2/apps/accumulo/data}}
> according to --
> https://accumulo.apache.org/docs/2.0/administration/multivolume
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24546) Protect the Request resource so that only authorized users may have read-only access the data
[
https://issues.apache.org/jira/browse/AMBARI-24546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16598632#comment-16598632
]
Hudson commented on AMBARI-24546:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #209 (See
[https://builds.apache.org/job/Ambari-branch-2.7/209/])
AMBARI-24546. Only authenticated users with proper AMBARI/CLUSTER (github:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=0c3812bbb563b1d05d916e7af46ac9bc6cab31ea])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RequestResourceProvider.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/security/authorization/RoleAuthorization.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog272.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/RequestResourceProviderTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog272Test.java
> Protect the Request resource so that only authorized users may have read-only
> access the data
> -
>
> Key: AMBARI-24546
> URL: https://issues.apache.org/jira/browse/AMBARI-24546
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.3.0
>Reporter: Robert Levas
>Assignee: Sandor Molnar
>Priority: Major
> Labels: pull-request-available, rbac
> Fix For: 2.7.2
>
> Time Spent: 3h 50m
> Remaining Estimate: 0h
>
> Protect the Request resource so that only authorized users may have read-only
> access the data.
> Users with the following roles should have read-only access:
> * {{AMBARI.ADMINISTRATOR}}
> * {{CLUSTER.ADMINISTRATOR}}
> * {{CLUSTER.OPERATOR}}
> * {{SERVICE.ADMINISTRATOR}}
> * {{SERVICE.OPERATOR}}
> * {{CLUSTER.USER}}
> Users with no role related to the cluster may not view the data.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24525) Accumulo does not startup in Federated Cluster
[
https://issues.apache.org/jira/browse/AMBARI-24525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16598600#comment-16598600
]
Hudson commented on AMBARI-24525:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9904 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/9904/])
AMBARI-24525 Accumulo does not startup in Federated Cluster. (github:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=e6f1d35bf630ca3f7f5f479978baf3430a10089d])
* (edit) ambari-web/app/controllers/main/admin/federation/step3_controller.js
* (edit) ambari-web/app/data/configs/wizards/federation_properties.js
* (edit) ambari-web/app/controllers/main/admin/federation/step4_controller.js
* (edit)
ambari-web/test/controllers/main/admin/federation/step3_controller_test.js
> Accumulo does not startup in Federated Cluster
> --
>
> Key: AMBARI-24525
> URL: https://issues.apache.org/jira/browse/AMBARI-24525
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.2
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> In a manually setup federated cluster (not through deployNG) --
> Accumulo was installed and when trying to start, below error thrown --
> {noformat}
> 2018-08-16 07:33:31,748 [start.Main] ERROR: Thread
> 'org.apache.accumulo.master.state.SetGoalState' died.
> java.lang.IllegalArgumentException: Expected fully qualified URI for
> instance.volumes got ns2/apps/accumulo/data
> at
> org.apache.accumulo.core.volume.VolumeConfiguration.getVolumeUris(VolumeConfiguration.java:107)
> at
> org.apache.accumulo.server.fs.VolumeManagerImpl.get(VolumeManagerImpl.java:334)
> {noformat}
> Caused by incorrect config value:
> {{instance.volumes = hdfs://ns1,ns2/apps/accumulo/data}}
> where ns1 and ns2 are namespaces
> Expected is --
> {{instance.volumes =
> hdfs://ns1/apps/accumulo/data,hdfs://ns2/apps/accumulo/data}}
> according to --
> https://accumulo.apache.org/docs/2.0/administration/multivolume
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24539) OneFS mpack should not include webhdfs enable setting
[ https://issues.apache.org/jira/browse/AMBARI-24539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16598599#comment-16598599 ] Hudson commented on AMBARI-24539: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #208 (See [https://builds.apache.org/job/Ambari-branch-2.7/208/]) AMBARI-24539: OneFS mpack should not include webhdfs enable setting (github: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=c8e7049639b1607a08167df6ec61fbda63643392]) * (edit) contrib/management-packs/isilon-onefs-mpack/src/main/resources/addon-services/ONEFS/1.0.0/configuration/hdfs-site.xml > OneFS mpack should not include webhdfs enable setting > - > > Key: AMBARI-24539 > URL: https://issues.apache.org/jira/browse/AMBARI-24539 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Robert Ketcherside >Assignee: Attila Magyar >Priority: Major > Labels: pull-request-available > Time Spent: 1.5h > Remaining Estimate: 0h > > webhdfs.dfs.enabled is included in the configurations for OneFS management > pack. That is not needed because OneFS 8.1.2.0 (used with Ambari 2.7 and the > mpack) does not require the disablement of webhdfs in Ambari to support > Ambari Views. > webhdfs.dfs.enabled property should be removed entirely from > configurations/hdfs-site.xml -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24561) Update styles for pre-upgrade modals
[ https://issues.apache.org/jira/browse/AMBARI-24561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-24561: -- Resolution: Fixed Status: Resolved (was: Patch Available) Merged to trunk > Update styles for pre-upgrade modals > > > Key: AMBARI-24561 > URL: https://issues.apache.org/jira/browse/AMBARI-24561 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.1 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 40m > Remaining Estimate: 0h > > - Move 'Preparing the Upgrade' text from the corresponding modal to its header > - Upgrade Options popup: add some vertical padding between peragraphs > - Upgrade Options popup: center the contents of upgrade type blocks and add > more padding to them > - Make pre-upgrade checks popup wider > - Pre-upgrade checks popup: display warnings as regular text instead of well > blocks -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24578) Quicklinks URL overflow outside the UI box
Andrii Tkach created AMBARI-24578: - Summary: Quicklinks URL overflow outside the UI box Key: AMBARI-24578 URL: https://issues.apache.org/jira/browse/AMBARI-24578 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.1 Reporter: Andrii Tkach Assignee: Andrii Tkach Fix For: 2.7.2 Attachments: quicklinks.png Quicklinks in HDI environment are overflowing in UI. See attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24578) Quicklinks URL overflow outside the UI box
[ https://issues.apache.org/jira/browse/AMBARI-24578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-24578: -- Attachment: quicklinks.png > Quicklinks URL overflow outside the UI box > -- > > Key: AMBARI-24578 > URL: https://issues.apache.org/jira/browse/AMBARI-24578 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.1 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.7.2 > > Attachments: quicklinks.png > > > Quicklinks in HDI environment are overflowing in UI. See attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24525) Accumulo does not startup in Federated Cluster
[
https://issues.apache.org/jira/browse/AMBARI-24525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Babiichuk updated AMBARI-24525:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Merged to trunk and branch-2.7
> Accumulo does not startup in Federated Cluster
> --
>
> Key: AMBARI-24525
> URL: https://issues.apache.org/jira/browse/AMBARI-24525
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.2
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> In a manually setup federated cluster (not through deployNG) --
> Accumulo was installed and when trying to start, below error thrown --
> {noformat}
> 2018-08-16 07:33:31,748 [start.Main] ERROR: Thread
> 'org.apache.accumulo.master.state.SetGoalState' died.
> java.lang.IllegalArgumentException: Expected fully qualified URI for
> instance.volumes got ns2/apps/accumulo/data
> at
> org.apache.accumulo.core.volume.VolumeConfiguration.getVolumeUris(VolumeConfiguration.java:107)
> at
> org.apache.accumulo.server.fs.VolumeManagerImpl.get(VolumeManagerImpl.java:334)
> {noformat}
> Caused by incorrect config value:
> {{instance.volumes = hdfs://ns1,ns2/apps/accumulo/data}}
> where ns1 and ns2 are namespaces
> Expected is --
> {{instance.volumes =
> hdfs://ns1/apps/accumulo/data,hdfs://ns2/apps/accumulo/data}}
> according to --
> https://accumulo.apache.org/docs/2.0/administration/multivolume
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24555) Nifi Registry install fails
[
https://issues.apache.org/jira/browse/AMBARI-24555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Babiichuk updated AMBARI-24555:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Merged to trunk and branch-2.7
> Nifi Registry install fails
> ---
>
> Key: AMBARI-24555
> URL: https://issues.apache.org/jira/browse/AMBARI-24555
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.2
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Facing issue installing Nifi Registry on HDP_HDF cluster. The create keytab
> step in Ambari is failing during installation. Below exception is seen in
> ambari logs.
>
> {code}
> 2018-08-21 13:11:03,401 ERROR [Server Action Executor Worker 1305]
> CreatePrincipalsServerAction:309 - Failed to create principal, - Failed to
> create new principal - no principal specified
> org.apache.ambari.server.serveraction.kerberos.KerberosOperationException:
> Failed to create new principal - no principal specified
> at
> org.apache.ambari.server.serveraction.kerberos.MITKerberosOperationHandler.createPrincipal(MITKerberosOperationHandler.java:159)
> at
> org.apache.ambari.server.serveraction.kerberos.CreatePrincipalsServerAction.createPrincipal(CreatePrincipalsServerAction.java:268)
> at
> org.apache.ambari.server.serveraction.kerberos.CreatePrincipalsServerAction.processIdentity(CreatePrincipalsServerAction.java:157)
> at
> org.apache.ambari.server.serveraction.kerberos.KerberosServerAction.processIdentities(KerberosServerAction.java:460)
> at
> org.apache.ambari.server.serveraction.kerberos.CreatePrincipalsServerAction.execute(CreatePrincipalsServerAction.java:92)
> at
> org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.execute(ServerActionExecutor.java:550)
> at
> org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.run(ServerActionExecutor.java:466)
> at java.lang.Thread.run(Thread.java:748)
> 2018-08-21 13:11:03,401 INFO [Server Action Executor Worker 1305]
> KerberosServerAction:481 - Processing identities completed.
> 2018-08-21 13:11:04,191 ERROR [ambari-action-scheduler] ActionScheduler:482 -
> Operation completely failed, aborting request id: 117
> {code}
> The Ambari UI should not display any properties from Kerberos identity blocks
> that indicate they are referencing another Kerberos identity. There are 2
> ways we know this:
> - The new/preferred way: the identity block has a non-empty/non-null
> "reference" attribute
> - The old (backwards compatible way): the identity block has a "name"
> attribute the starts with a '/'.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (AMBARI-24538) OneFS mpack quicklinks require port, https
[ https://issues.apache.org/jira/browse/AMBARI-24538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Magyar reassigned AMBARI-24538: -- Assignee: (was: Attila Magyar) > OneFS mpack quicklinks require port, https > -- > > Key: AMBARI-24538 > URL: https://issues.apache.org/jira/browse/AMBARI-24538 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Robert Ketcherside >Priority: Major > Labels: pull-request-available > Time Spent: 1h 50m > Remaining Estimate: 0h > > Quicklinks for OneFS in the OneFS management pack currently have no port. > Normally that's okay because OneFS is configured by default to redirect port > 80 traffic to the management port, 8080. But if http file browse is enabled > (`isi http settings modify --service=enabled`), that uses port 80. We need to > point to port 8080. > Also, OneFS will redirect from http to https, but a 400 error appears > briefly. For better user experience the quicklinks should use https. > Both the onefs_web_ui and onefs_hdfs_web_ui need to be fixed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-24538) OneFS mpack quicklinks require port, https
[ https://issues.apache.org/jira/browse/AMBARI-24538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Magyar reassigned AMBARI-24538: -- Assignee: Attila Magyar > OneFS mpack quicklinks require port, https > -- > > Key: AMBARI-24538 > URL: https://issues.apache.org/jira/browse/AMBARI-24538 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Robert Ketcherside >Assignee: Attila Magyar >Priority: Major > Labels: pull-request-available > Time Spent: 1h 50m > Remaining Estimate: 0h > > Quicklinks for OneFS in the OneFS management pack currently have no port. > Normally that's okay because OneFS is configured by default to redirect port > 80 traffic to the management port, 8080. But if http file browse is enabled > (`isi http settings modify --service=enabled`), that uses port 80. We need to > point to port 8080. > Also, OneFS will redirect from http to https, but a 400 error appears > briefly. For better user experience the quicklinks should use https. > Both the onefs_web_ui and onefs_hdfs_web_ui need to be fixed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24538) OneFS mpack quicklinks require port, https
[ https://issues.apache.org/jira/browse/AMBARI-24538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Magyar resolved AMBARI-24538. Resolution: Fixed > OneFS mpack quicklinks require port, https > -- > > Key: AMBARI-24538 > URL: https://issues.apache.org/jira/browse/AMBARI-24538 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Robert Ketcherside >Priority: Major > Labels: pull-request-available > Time Spent: 1h 50m > Remaining Estimate: 0h > > Quicklinks for OneFS in the OneFS management pack currently have no port. > Normally that's okay because OneFS is configured by default to redirect port > 80 traffic to the management port, 8080. But if http file browse is enabled > (`isi http settings modify --service=enabled`), that uses port 80. We need to > point to port 8080. > Also, OneFS will redirect from http to https, but a 400 error appears > briefly. For better user experience the quicklinks should use https. > Both the onefs_web_ui and onefs_hdfs_web_ui need to be fixed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24539) OneFS mpack should not include webhdfs enable setting
[ https://issues.apache.org/jira/browse/AMBARI-24539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Magyar resolved AMBARI-24539. Resolution: Fixed > OneFS mpack should not include webhdfs enable setting > - > > Key: AMBARI-24539 > URL: https://issues.apache.org/jira/browse/AMBARI-24539 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Robert Ketcherside >Priority: Major > Labels: pull-request-available > Time Spent: 1.5h > Remaining Estimate: 0h > > webhdfs.dfs.enabled is included in the configurations for OneFS management > pack. That is not needed because OneFS 8.1.2.0 (used with Ambari 2.7 and the > mpack) does not require the disablement of webhdfs in Ambari to support > Ambari Views. > webhdfs.dfs.enabled property should be removed entirely from > configurations/hdfs-site.xml -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-24539) OneFS mpack should not include webhdfs enable setting
[ https://issues.apache.org/jira/browse/AMBARI-24539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Magyar reassigned AMBARI-24539: -- Assignee: Attila Magyar > OneFS mpack should not include webhdfs enable setting > - > > Key: AMBARI-24539 > URL: https://issues.apache.org/jira/browse/AMBARI-24539 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Robert Ketcherside >Assignee: Attila Magyar >Priority: Major > Labels: pull-request-available > Time Spent: 1.5h > Remaining Estimate: 0h > > webhdfs.dfs.enabled is included in the configurations for OneFS management > pack. That is not needed because OneFS 8.1.2.0 (used with Ambari 2.7 and the > mpack) does not require the disablement of webhdfs in Ambari to support > Ambari Views. > webhdfs.dfs.enabled property should be removed entirely from > configurations/hdfs-site.xml -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23288) stateWatcherClient should be closed upon return from OutputSolr#createSolrStateWatcher
[
https://issues.apache.org/jira/browse/AMBARI-23288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated AMBARI-23288:
Description:
{code}
CloudSolrClient stateWatcherClient = createSolrClient();
{code}
stateWatcherClient should be closed upon return from the method.
was:
{code}
CloudSolrClient stateWatcherClient = createSolrClient();
{code}
stateWatcherClient should be closed upon return from the method.
> stateWatcherClient should be closed upon return from
> OutputSolr#createSolrStateWatcher
> --
>
> Key: AMBARI-23288
> URL: https://issues.apache.org/jira/browse/AMBARI-23288
> Project: Ambari
> Issue Type: Bug
>Reporter: Ted Yu
>Priority: Minor
>
> {code}
> CloudSolrClient stateWatcherClient = createSolrClient();
> {code}
> stateWatcherClient should be closed upon return from the method.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23287) Lack of synchronization accessing topologyHolder in HostResourceProvider#processDeleteHostRequests
[ https://issues.apache.org/jira/browse/AMBARI-23287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated AMBARI-23287: Description: HostResourceProvider#processDeleteHostRequests accesses topologyHolder without any synchronization . was: HostResourceProvider#processDeleteHostRequests accesses topologyHolder without any synchronization. > Lack of synchronization accessing topologyHolder in > HostResourceProvider#processDeleteHostRequests > -- > > Key: AMBARI-23287 > URL: https://issues.apache.org/jira/browse/AMBARI-23287 > Project: Ambari > Issue Type: Bug >Reporter: Ted Yu >Priority: Minor > > HostResourceProvider#processDeleteHostRequests accesses topologyHolder > without any synchronization . > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24032) Ambari should be selective about which HBase components that need to be restarted
[ https://issues.apache.org/jira/browse/AMBARI-24032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated AMBARI-24032: Description: For hbase config changes that only involve hbase master, Ambari should explicitly say so after the change. One example of such config change is for hbase.master.loadbalancer.class and hbase.coprocessor.master.classes was: For hbase config changes that only involve hbase master, Ambari should explicitly say so after the change. One example of such config change is for hbase.master.loadbalancer.class and hbase.coprocessor.master.classes > Ambari should be selective about which HBase components that need to be > restarted > - > > Key: AMBARI-24032 > URL: https://issues.apache.org/jira/browse/AMBARI-24032 > Project: Ambari > Issue Type: Bug >Reporter: Ted Yu >Priority: Major > > For hbase config changes that only involve hbase master, Ambari should > explicitly say so after the change. > One example of such config change is for hbase.master.loadbalancer.class and > hbase.coprocessor.master.classes -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24526) Status of components does not become RED if their deamon goes down immediately after successful start
[ https://issues.apache.org/jira/browse/AMBARI-24526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24526: - Resolution: Fixed Status: Resolved (was: Patch Available) > Status of components does not become RED if their deamon goes down > immediately after successful start > - > > Key: AMBARI-24526 > URL: https://issues.apache.org/jira/browse/AMBARI-24526 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.2 > > Attachments: AMBARI-24526.patch > > Time Spent: 1h 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24546) Protect the Request resource so that only authorized users may have read-only access the data
[
https://issues.apache.org/jira/browse/AMBARI-24546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16598461#comment-16598461
]
Hudson commented on AMBARI-24546:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9903 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/9903/])
AMBARI-24546. Only authenticated users with proper AMBARI/CLUSTER (github:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=8a79291ff36b23014a14261c703658437db9acc3])
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog272Test.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RequestResourceProvider.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog272.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/RequestResourceProviderTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/security/authorization/RoleAuthorization.java
> Protect the Request resource so that only authorized users may have read-only
> access the data
> -
>
> Key: AMBARI-24546
> URL: https://issues.apache.org/jira/browse/AMBARI-24546
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.3.0
>Reporter: Robert Levas
>Assignee: Sandor Molnar
>Priority: Major
> Labels: pull-request-available, rbac
> Fix For: 2.7.2
>
> Time Spent: 3h
> Remaining Estimate: 0h
>
> Protect the Request resource so that only authorized users may have read-only
> access the data.
> Users with the following roles should have read-only access:
> * {{AMBARI.ADMINISTRATOR}}
> * {{CLUSTER.ADMINISTRATOR}}
> * {{CLUSTER.OPERATOR}}
> * {{SERVICE.ADMINISTRATOR}}
> * {{SERVICE.OPERATOR}}
> * {{CLUSTER.USER}}
> Users with no role related to the cluster may not view the data.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24576) Ambari Metrics should handle a customized Zookeeper service principal name
[ https://issues.apache.org/jira/browse/AMBARI-24576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24576: Labels: pull-request-available (was: ) > Ambari Metrics should handle a customized Zookeeper service principal name > -- > > Key: AMBARI-24576 > URL: https://issues.apache.org/jira/browse/AMBARI-24576 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.7.2 >Reporter: Attila Magyar >Assignee: Attila Magyar >Priority: Major > Labels: pull-request-available > Fix For: 2.7.2 > > > AMS should handle a customized Zookeeper service principal name. > Currently this is not supported due to hardcoded and implicit values > expecting the Zookeeper service principal name to be zookeeper/_HOST as > opposed to something like zookeeper-mycluster/_HOST. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24570) Atlas should handle a customized Zookeeper service principal name
[ https://issues.apache.org/jira/browse/AMBARI-24570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Magyar resolved AMBARI-24570. Resolution: Fixed > Atlas should handle a customized Zookeeper service principal name > - > > Key: AMBARI-24570 > URL: https://issues.apache.org/jira/browse/AMBARI-24570 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.7.1 >Reporter: Attila Magyar >Assignee: Attila Magyar >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 20m > Remaining Estimate: 0h > > Atlas should handle a customized Zookeeper service principal name. > Currently this is not supported due to hardcoded and implicit values > expecting the Zookeeper service principal name to be zookeeper/_HOST as > opposed to something like zookeeper-mycluster/_HOST. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24570) Atlas should handle a customized Zookeeper service principal name
[ https://issues.apache.org/jira/browse/AMBARI-24570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16598385#comment-16598385 ] Hudson commented on AMBARI-24570: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #207 (See [https://builds.apache.org/job/Ambari-branch-2.7/207/]) AMBARI-24570. Atlas should handle a customized Zookeeper service (github: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=f35b251d5cc32cd0a2101140e19f7ef5b9543e90]) * (edit) ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/package/scripts/params.py * (edit) ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/configuration/atlas-env.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/services/ATLAS/configuration/atlas-env.xml > Atlas should handle a customized Zookeeper service principal name > - > > Key: AMBARI-24570 > URL: https://issues.apache.org/jira/browse/AMBARI-24570 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.7.1 >Reporter: Attila Magyar >Assignee: Attila Magyar >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 20m > Remaining Estimate: 0h > > Atlas should handle a customized Zookeeper service principal name. > Currently this is not supported due to hardcoded and implicit values > expecting the Zookeeper service principal name to be zookeeper/_HOST as > opposed to something like zookeeper-mycluster/_HOST. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24548) Allow skipping Hive Metastore schema creation for sysprepped cluster
[
https://issues.apache.org/jira/browse/AMBARI-24548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-24548:
---
Fix Version/s: 2.7.2
Status: Patch Available (was: In Progress)
> Allow skipping Hive Metastore schema creation for sysprepped cluster
>
>
> Key: AMBARI-24548
> URL: https://issues.apache.org/jira/browse/AMBARI-24548
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.2
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Similar to AMBARI-24540, Hive Metastore DB schema may be manually pre-created
> to save time during initial service start. However, {{schematool}} could
> still take quite some time to confirm that the schema exists. The goal of
> this change is to allow users who pre-create Hive Metastore DB schema to make
> Ambari skip managing the DB (create or check existence).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
