[jira] [Updated] (AMBARI-19186) RU install_packages fails on suse
[
https://issues.apache.org/jira/browse/AMBARI-19186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-19186:
-
Attachment: AMBARI-19186.patch
> RU install_packages fails on suse
> -
>
> Key: AMBARI-19186
> URL: https://issues.apache.org/jira/browse/AMBARI-19186
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Dmytro Grinenko
>Priority: Critical
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19186.patch
>
>
> {code}
> zypper search --installed-only --details
> {code}
> Command above failing on the SuSe if any unsigned repo present in the system
> with:
> {code}
> Retrieving repository 'local' metadata [\]
> File 'repomd.xml' from repository 'local' is unsigned, continue? [yes/no]
> (no):
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19186) RU install_packages fails on suse
Dmytro Grinenko created AMBARI-19186:
Summary: RU install_packages fails on suse
Key: AMBARI-19186
URL: https://issues.apache.org/jira/browse/AMBARI-19186
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: trunk, 2.5.0
Reporter: Dmytro Grinenko
Priority: Critical
Fix For: trunk, 2.5.0
{code}
zypper search --installed-only --details
{code}
Command above failing on the SuSe if any unsigned repo present in the system
with:
{code}
Retrieving repository 'local' metadata [\]
File 'repomd.xml' from repository 'local' is unsigned, continue? [yes/no] (no):
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19170) NPE during Ambari server schema upgrade
[
https://issues.apache.org/jira/browse/AMBARI-19170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15744072#comment-15744072
]
Hadoop QA commented on AMBARI-19170:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12842861/AMBARI-19170_trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.controller.metrics.JMXPropertyProviderTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9634//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9634//console
This message is automatically generated.
> NPE during Ambari server schema upgrade
> ---
>
> Key: AMBARI-19170
> URL: https://issues.apache.org/jira/browse/AMBARI-19170
> Project: Ambari
> Issue Type: Bug
> Components: ambari-upgrade
>Affects Versions: 2.5.0
>Reporter: Vivek Sharma
>Assignee: Doroszlai, Attila
>Priority: Critical
> Labels: upgrade
> Fix For: 2.5.0
>
> Attachments: AMBARI-19170_branch-2.5.patch, AMBARI-19170_trunk.patch
>
>
> Ambari server upgrade path: 2.2.2.0 to 2.5.0.0-453
> Error seen while running 'ambari-server upgrade' command"
> {code}
> Using python /usr/bin/python
> Upgrading ambari-server
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> 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
> WARNING: Original file krb5JAASLogin.conf kept
> INFO: File krb5JAASLogin.conf updated.
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: No mpack replay logs found. Skipping replaying mpack commands
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Fixing database objects owner
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: using SERVICE_NAME instead of SID for Oracle
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> Ambari Server configured for Oracle. Confirm you have made a backup of the
> Ambari Server database [y/n] (y)? INFO: Loading properties from
> /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: using SERVICE_NAME instead of SID for Oracle
> INFO: Upgrading database schema
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: AMBARI_SERVER_LIB is not set, using default /usr/lib/ambari-server
> INFO: using SERVICE_NAME instead of SID for Oracle
> INFO: using SERVICE_NAME instead of SID for Oracle
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: about to run command: /usr/jdk64/jdk1.7.0_67/bin/java -cp
> '/etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/ojdbc6.jar'
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper >
> /var/log/ambari-server/ambari-server.out 2>&1
> 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
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:209)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:424)
> Caused by: java.lang.NullPointerException
> at
> com.google.inject.persist.jpa.JpaPersistService.begin(JpaPersistService.java:70)
> at
> com.google.inject.persist.jpa.AmbariJpaPersistService.begin(AmbariJpaPersistService.java:29)
> at
>
[jira] [Commented] (AMBARI-19184) Remove HSI host name from UI
[
https://issues.apache.org/jira/browse/AMBARI-19184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15743989#comment-15743989
]
Hadoop QA commented on AMBARI-19184:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12842916/AMBARI-19184.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9633//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9633//console
This message is automatically generated.
> Remove HSI host name from UI
>
>
> Key: AMBARI-19184
> URL: https://issues.apache.org/jira/browse/AMBARI-19184
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.5.0
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
> Fix For: 2.5.0
>
> Attachments: AMBARI-19184.patch, Screen Shot 2016-12-12 at 6.12.42
> PM.png
>
>
> Given that we are supporting HSI HA, we need to remove "HiveServer2
> Interactive Host" from UI
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19165) Ambari-web unit tests cannot be run in Mac OS Sierra
[ https://issues.apache.org/jira/browse/AMBARI-19165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15743975#comment-15743975 ] Hudson commented on AMBARI-19165: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6213 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6213/]) AMBARI-19165. Ambari-web unit tests cannot be run in Mac OS Sierra. (jaimin: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=79d743b9d14530106ef107611f58345fb7f2e93b]) * (edit) ambari-web/test/controllers/main/admin/highAvailability/hawq/addStandby/step3_controller_test.js * (edit) ambari-web/test/controllers/wizard/step9_test.js * (edit) ambari-web/test/utils/date/date_test.js * (edit) ambari-web/package.json * (edit) ambari-web/app/controllers/wizard.js * (edit) ambari-web/test/utils/configs/config_initializer_test.js * (edit) ambari-web/app/assets/test/test.html * (edit) ambari-web/test/utils/date/timezone_test.js > Ambari-web unit tests cannot be run in Mac OS Sierra > > > Key: AMBARI-19165 > URL: https://issues.apache.org/jira/browse/AMBARI-19165 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19165.patch > > > Running "npm test" just hangs in Mac OS Sierra. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19165) Ambari-web unit tests cannot be run in Mac OS Sierra
[ https://issues.apache.org/jira/browse/AMBARI-19165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15743882#comment-15743882 ] Hudson commented on AMBARI-19165: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #513 (See [https://builds.apache.org/job/Ambari-branch-2.5/513/]) Revert "AMBARI-19165. Ambari-web unit tests cannot be run in Mac OS (jaimin: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ef0486611c584cbea1817eb78ea1fb61cf891052]) * (edit) ambari-web/test/utils/configs/config_initializer_test.js * (edit) ambari-web/test/utils/date/date_test.js * (edit) ambari-web/test/controllers/wizard/step9_test.js * (edit) ambari-web/package.json * (edit) ambari-web/test/views/common/configs/widgets/slider_config_widget_view_test.js * (edit) ambari-web/test/controllers/main/admin/highAvailability/hawq/addStandby/step3_controller_test.js * (edit) ambari-web/app/assets/test/test.html * (edit) ambari-web/test/utils/date/timezone_test.js AMBARI-19165. Ambari-web unit tests cannot be run in Mac OS Sierra. (jaimin: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7b980928e7a4f29a9a0ef205b92f0e1974fb]) * (edit) ambari-web/app/assets/test/test.html * (edit) ambari-web/test/views/common/configs/widgets/slider_config_widget_view_test.js * (edit) ambari-web/test/utils/configs/config_initializer_test.js * (edit) ambari-web/test/utils/date/date_test.js * (edit) ambari-web/test/utils/date/timezone_test.js * (edit) ambari-web/test/controllers/wizard/step9_test.js * (edit) ambari-web/package.json * (edit) ambari-web/test/controllers/main/admin/highAvailability/hawq/addStandby/step3_controller_test.js > Ambari-web unit tests cannot be run in Mac OS Sierra > > > Key: AMBARI-19165 > URL: https://issues.apache.org/jira/browse/AMBARI-19165 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19165.patch > > > Running "npm test" just hangs in Mac OS Sierra. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19184) Remove HSI host name from UI
[ https://issues.apache.org/jira/browse/AMBARI-19184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15743869#comment-15743869 ] Sumit Mohanty commented on AMBARI-19184: The patch only removes the variable and does not have any changes to delete it on a live cluster. The property need not be deleted as there are no consumer for the property and adding logic to delete as part of HDP or Ambari upgrade seems like extra work with no real gain. > Remove HSI host name from UI > > > Key: AMBARI-19184 > URL: https://issues.apache.org/jira/browse/AMBARI-19184 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.0 >Reporter: Sumit Mohanty >Assignee: Sumit Mohanty > Fix For: 2.5.0 > > Attachments: AMBARI-19184.patch, Screen Shot 2016-12-12 at 6.12.42 > PM.png > > > Given that we are supporting HSI HA, we need to remove "HiveServer2 > Interactive Host" from UI -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19184) Remove HSI host name from UI
[ https://issues.apache.org/jira/browse/AMBARI-19184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-19184: --- Status: Patch Available (was: Open) > Remove HSI host name from UI > > > Key: AMBARI-19184 > URL: https://issues.apache.org/jira/browse/AMBARI-19184 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.0 >Reporter: Sumit Mohanty >Assignee: Sumit Mohanty > Fix For: 2.5.0 > > Attachments: AMBARI-19184.patch, Screen Shot 2016-12-12 at 6.12.42 > PM.png > > > Given that we are supporting HSI HA, we need to remove "HiveServer2 > Interactive Host" from UI -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19184) Remove HSI host name from UI
[ https://issues.apache.org/jira/browse/AMBARI-19184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-19184: --- Attachment: AMBARI-19184.patch > Remove HSI host name from UI > > > Key: AMBARI-19184 > URL: https://issues.apache.org/jira/browse/AMBARI-19184 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.0 >Reporter: Sumit Mohanty >Assignee: Sumit Mohanty > Fix For: 2.5.0 > > Attachments: AMBARI-19184.patch, Screen Shot 2016-12-12 at 6.12.42 > PM.png > > > Given that we are supporting HSI HA, we need to remove "HiveServer2 > Interactive Host" from UI -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19184) Remove HSI host name from UI
[ https://issues.apache.org/jira/browse/AMBARI-19184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-19184: --- Attachment: Screen Shot 2016-12-12 at 6.12.42 PM.png > Remove HSI host name from UI > > > Key: AMBARI-19184 > URL: https://issues.apache.org/jira/browse/AMBARI-19184 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.0 >Reporter: Sumit Mohanty >Assignee: Sumit Mohanty > Fix For: 2.5.0 > > Attachments: Screen Shot 2016-12-12 at 6.12.42 PM.png > > > Given that we are supporting HSI HA, we need to remove "HiveServer2 > Interactive Host" from UI -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19184) Remove HSI host name from UI
Sumit Mohanty created AMBARI-19184: -- Summary: Remove HSI host name from UI Key: AMBARI-19184 URL: https://issues.apache.org/jira/browse/AMBARI-19184 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 2.5.0 Reporter: Sumit Mohanty Assignee: Sumit Mohanty Fix For: 2.5.0 Given that we are supporting HSI HA, we need to remove "HiveServer2 Interactive Host" from UI -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (AMBARI-18528) Need a way to escape config values that contain $
[
https://issues.apache.org/jira/browse/AMBARI-18528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15603928#comment-15603928
]
Ted Yu edited comment on AMBARI-18528 at 12/13/16 2:06 AM:
---
Escaping the dollar sign automatically is a desirable solution .
was (Author: yuzhih...@gmail.com):
Escaping the dollar sign automatically is the desirable solution .
> Need a way to escape config values that contain $
> -
>
> Key: AMBARI-18528
> URL: https://issues.apache.org/jira/browse/AMBARI-18528
> Project: Ambari
> Issue Type: Bug
>Reporter: Ted Yu
> Labels: zookeeper
>
> We tried specifying auth_to_local in zookeeper env input box:
> {code}
> export SERVER_JVMFLAGS="$SERVER_JVMFLAGS
> -Dzookeeper.security.auth_to_local=RULE:[2:$1@$0](hb...@c.net)s/.*/hbase/
> -Djava.security.auth.login.config={{zk_server_jaas_file}}"
> {code}
> However, when zookeeper quorum starts, the rule got interrupted with
> zkServer.sh
> We should add the capability of specifying auth_to_local in Ambari UI
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18574) Set hbase.hregion.memstore.chunkpool.maxsize to 1.0
[
https://issues.apache.org/jira/browse/AMBARI-18574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated AMBARI-18574:
Description:
The default value for hbase.hregion.memstore.chunkpool.maxsize is:
{code}
final static float POOL_MAX_SIZE_DEFAULT = 0.0f;
{code}
This would result in chunk pool being disabled, leading to excessive
MemStoreLAB chunk allocations.
Ambari should set the value to 1.0
was:
The default value for hbase.hregion.memstore.chunkpool.maxsize is:
{code}
final static float POOL_MAX_SIZE_DEFAULT = 0.0f;
{code}
This would result in chunk pool being disabled, leading to excessive
MemStoreLAB chunk allocations.
Ambari should set the value to 1.0
> Set hbase.hregion.memstore.chunkpool.maxsize to 1.0
> ---
>
> Key: AMBARI-18574
> URL: https://issues.apache.org/jira/browse/AMBARI-18574
> Project: Ambari
> Issue Type: Bug
>Reporter: Ted Yu
>
> The default value for hbase.hregion.memstore.chunkpool.maxsize is:
> {code}
> final static float POOL_MAX_SIZE_DEFAULT = 0.0f;
> {code}
> This would result in chunk pool being disabled, leading to excessive
> MemStoreLAB chunk allocations.
> Ambari should set the value to 1.0
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19165) Ambari-web unit tests cannot be run in Mac OS Sierra
[ https://issues.apache.org/jira/browse/AMBARI-19165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15743811#comment-15743811 ] Hudson commented on AMBARI-19165: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #512 (See [https://builds.apache.org/job/Ambari-branch-2.5/512/]) AMBARI-19165. Ambari-web unit tests cannot be run in Mac OS Sierra. (jaimin: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=3eb3dd34060a5a900136ecdd85ea2a1cc164f4ef]) * (edit) ambari-web/package.json * (edit) ambari-web/test/utils/configs/config_initializer_test.js * (edit) ambari-web/test/views/common/configs/widgets/slider_config_widget_view_test.js * (edit) ambari-web/test/controllers/wizard/step9_test.js * (edit) ambari-web/test/utils/date/date_test.js * (edit) ambari-web/app/assets/test/test.html * (edit) ambari-web/test/utils/date/timezone_test.js * (edit) ambari-web/test/controllers/main/admin/highAvailability/hawq/addStandby/step3_controller_test.js > Ambari-web unit tests cannot be run in Mac OS Sierra > > > Key: AMBARI-19165 > URL: https://issues.apache.org/jira/browse/AMBARI-19165 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19165.patch > > > Running "npm test" just hangs in Mac OS Sierra. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19183) Ambari allows creation of invalid config type
Dhanya Balasundaran created AMBARI-19183: Summary: Ambari allows creation of invalid config type Key: AMBARI-19183 URL: https://issues.apache.org/jira/browse/AMBARI-19183 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Dhanya Balasundaran Fix For: 2.5.0 After deployment try to create an invalid config type to HDFS Verify that call failed with 500 Error code Verify that the invalid configtype is not created Eventhough PUT call fails with 500 error, invalid config type was created successfully. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19182) Config Groups: Save button not enabled while trying to overwrite configs
Vivek Rathod created AMBARI-19182: - Summary: Config Groups: Save button not enabled while trying to overwrite configs Key: AMBARI-19182 URL: https://issues.apache.org/jira/browse/AMBARI-19182 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Vivek Rathod Fix For: 2.5.0 STR: -> For a service, create a config group -> Go to configs page, select the config group. Now try to overwrite a config, Save button is not enabled here. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19181) Add alerts for unhealthy flume agents based on metrics.
Aravindan Vijayan created AMBARI-19181: -- Summary: Add alerts for unhealthy flume agents based on metrics. Key: AMBARI-19181 URL: https://issues.apache.org/jira/browse/AMBARI-19181 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: 2.5.0 Reporter: Aravindan Vijayan Priority: Critical Fix For: 2.5.0 Ambari Alerts triggered from Flume when a Batch is empty -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19169) Add Service Page in Atlas doesn't show config on change
[ https://issues.apache.org/jira/browse/AMBARI-19169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15743484#comment-15743484 ] Hudson commented on AMBARI-19169: - ABORTED: Integrated in Jenkins build Ambari-trunk-Commit #6212 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6212/]) AMBARI-19169. Add Service Page in Atlas doesn't show config on change (akovalenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=b69bcc1f2d14bff050571bc165110a59e701dd83]) * (edit) ambari-web/app/views/common/configs/service_configs_by_category_view.js * (edit) ambari-web/app/views/common/configs/widgets/config_widget_view.js > Add Service Page in Atlas doesn't show config on change > --- > > Key: AMBARI-19169 > URL: https://issues.apache.org/jira/browse/AMBARI-19169 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19169.patch > > > Steps to reproduce: > # Add Atlas service > # Under Authentication Tab > Enable LDAP Authentication > # This will open LDAP/AD section below > # Now in LDAP/AD section > select LDAP Authentication Type as AD, here the > properties related to AD are not shown. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19180) Service Flume failed to start with "cannot open /grid/0/log/flume/a1.out for reading: Permission denied"
Vivek Rathod created AMBARI-19180:
-
Summary: Service Flume failed to start with "cannot open
/grid/0/log/flume/a1.out for reading: Permission denied"
Key: AMBARI-19180
URL: https://issues.apache.org/jira/browse/AMBARI-19180
Project: Ambari
Issue Type: Bug
Affects Versions: 2.5.0
Reporter: Vivek Rathod
Fix For: 2.5.0
STR:
-> Delete the following services on the cluster : Flume, Atlas, Hbase, Sqoop,
Storm, Knox, AMS
-> Add them back using add service wizard
Flume fails to start with
{noformat}
2016-12-12 03:47:12,623 - Execute['ambari-sudo.sh su cstm-flume -l -s /bin/bash
-c 'export
PATH='"'"'/usr/sbin:/sbin:/usr/lib/ambari-server/*:/usr/lib64/qt-3.3/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/agentslava/bin:/var/lib/ambari-agent'"'"'
JAVA_HOME=/usr/jdk64/jdk1.8.0_77 ; /usr/hdp/current/flume-server/bin/flume-ng
agent --name a1 --conf /usr/hdp/current/flume-server/conf/a1 --conf-file
/usr/hdp/current/flume-server/conf/a1/flume.conf
-Dflume.monitoring.type=org.apache.hadoop.metrics2.sink.flume.FlumeTimelineMetricsSink
-Dflume.monitoring.node=ctr-e64-1480733150053-10989-01-02.hwx.site:6188 >
/grid/0/log/flume/a1.out 2>&1' &'] {'environment': {'JAVA_HOME':
'/usr/jdk64/jdk1.8.0_77'}, 'wait_for_finish': False}
2016-12-12 03:47:12,640 - Execute['ambari-sudo.sh -H -E pgrep -o -u cstm-flume
-f '^/usr/jdk64/jdk1.8.0_77.*a1.*' | ambari-sudo.sh -H -E tee
/var/run/flume/a1.pid && test ${PIPESTATUS[0]} -eq 0'] {'logoutput': True,
'tries': 20, 'try_sleep': 10}
2016-12-12 03:47:12,667 - Retrying after 10 seconds. Reason: Execution of
'ambari-sudo.sh -H -E pgrep -o -u cstm-flume -f
'^/usr/jdk64/jdk1.8.0_77.*a1.*' | ambari-sudo.sh -H -E tee
/var/run/flume/a1.pid && test ${PIPESTATUS[0]} -eq 0' returned 1.
2016-12-12 03:47:22,706 - Retrying after 10 seconds. Reason: Execution of
'ambari-sudo.sh -H -E pgrep -o -u cstm-flume -f
'^/usr/jdk64/jdk1.8.0_77.*a1.*' | ambari-sudo.sh -H -E tee
/var/run/flume/a1.pid && test ${PIPESTATUS[0]} -eq 0' returned 1.
2016-12-12 03:47:32,748 - Retrying after 10 seconds. Reason: Execution of
'ambari-sudo.sh -H -E pgrep -o -u cstm-flume -f
'^/usr/jdk64/jdk1.8.0_77.*a1.*' | ambari-sudo.sh -H -E tee
/var/run/flume/a1.pid && test ${PIPESTATUS[0]} -eq 0' returned 1.
2016-12-12 03:47:42,791 - Retrying after 10 seconds. Reason: Execution of
'ambari-sudo.sh -H -E pgrep -o -u cstm-flume -f
'^/usr/jdk64/jdk1.8.0_77.*a1.*' | ambari-sudo.sh -H -E tee
/var/run/flume/a1.pid && test ${PIPESTATUS[0]} -eq 0' returned 1.
2016-12-12 03:47:52,835 - Retrying after 10 seconds. Reason: Execution of
'ambari-sudo.sh -H -E pgrep -o -u cstm-flume -f
'^/usr/jdk64/jdk1.8.0_77.*a1.*' | ambari-sudo.sh -H -E tee
/var/run/flume/a1.pid && test ${PIPESTATUS[0]} -eq 0' returned 1.
2016-12-12 03:48:02,880 - Retrying after 10 seconds. Reason: Execution of
'ambari-sudo.sh -H -E pgrep -o -u cstm-flume -f
'^/usr/jdk64/jdk1.8.0_77.*a1.*' | ambari-sudo.sh -H -E tee
/var/run/flume/a1.pid && test ${PIPESTATUS[0]} -eq 0' returned 1.
2016-12-12 03:48:12,926 - Retrying after 10 seconds. Reason: Execution of
'ambari-sudo.sh -H -E pgrep -o -u cstm-flume -f
'^/usr/jdk64/jdk1.8.0_77.*a1.*' | ambari-sudo.sh -H -E tee
/var/run/flume/a1.pid && test ${PIPESTATUS[0]} -eq 0' returned 1.
2016-12-12 03:48:22,974 - Retrying after 10 seconds. Reason: Execution of
'ambari-sudo.sh -H -E pgrep -o -u cstm-flume -f
'^/usr/jdk64/jdk1.8.0_77.*a1.*' | ambari-sudo.sh -H -E tee
/var/run/flume/a1.pid && test ${PIPESTATUS[0]} -eq 0' returned 1.
2016-12-12 03:48:33,021 - Retrying after 10 seconds. Reason: Execution of
'ambari-sudo.sh -H -E pgrep -o -u cstm-flume -f
'^/usr/jdk64/jdk1.8.0_77.*a1.*' | ambari-sudo.sh -H -E tee
/var/run/flume/a1.pid && test ${PIPESTATUS[0]} -eq 0' returned 1.
2016-12-12 03:48:43,063 - Retrying after 10 seconds. Reason: Execution of
'ambari-sudo.sh -H -E pgrep -o -u cstm-flume -f
'^/usr/jdk64/jdk1.8.0_77.*a1.*' | ambari-sudo.sh -H -E tee
/var/run/flume/a1.pid && test ${PIPESTATUS[0]} -eq 0' returned 1.
2016-12-12 03:48:53,104 - Retrying after 10 seconds. Reason: Execution of
'ambari-sudo.sh -H -E pgrep -o -u cstm-flume -f
'^/usr/jdk64/jdk1.8.0_77.*a1.*' | ambari-sudo.sh -H -E tee
/var/run/flume/a1.pid && test ${PIPESTATUS[0]} -eq 0' returned 1.
2016-12-12 03:49:03,153 - Retrying after 10 seconds. Reason: Execution of
'ambari-sudo.sh -H -E pgrep -o -u cstm-flume -f
'^/usr/jdk64/jdk1.8.0_77.*a1.*' | ambari-sudo.sh -H -E tee
/var/run/flume/a1.pid && test ${PIPESTATUS[0]} -eq 0' returned 1.
2016-12-12 03:49:13,191 - Retrying after 10 seconds. Reason: Execution of
'ambari-sudo.sh -H -E pgrep -o -u cstm-flume -f
'^/usr/jdk64/jdk1.8.0_77.*a1.*' | ambari-sudo.sh -H -E tee
/var/run/flume/a1.pid && test ${PIPESTATUS[0]} -eq 0' returned 1.
2016-12-12 03:49:23,237 - Retrying
[jira] [Commented] (AMBARI-19178) HostCleanup can't list process details on RHEL7
[
https://issues.apache.org/jira/browse/AMBARI-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15743029#comment-15743029
]
Hadoop QA commented on AMBARI-19178:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12842844/AMBARI-19178.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9632//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9632//console
This message is automatically generated.
> HostCleanup can't list process details on RHEL7
> ---
>
> Key: AMBARI-19178
> URL: https://issues.apache.org/jira/browse/AMBARI-19178
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: trunk, 2.5.0
>Reporter: Di Li
>Assignee: Di Li
> Attachments: AMBARI-19178.patch
>
>
> need to use ps auxww instead of just ps aux
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19170) NPE during Ambari server schema upgrade
[
https://issues.apache.org/jira/browse/AMBARI-19170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-19170:
---
Status: Patch Available (was: Open)
> NPE during Ambari server schema upgrade
> ---
>
> Key: AMBARI-19170
> URL: https://issues.apache.org/jira/browse/AMBARI-19170
> Project: Ambari
> Issue Type: Bug
> Components: ambari-upgrade
>Affects Versions: 2.5.0
>Reporter: Vivek Sharma
>Assignee: Doroszlai, Attila
>Priority: Critical
> Labels: upgrade
> Fix For: 2.5.0
>
> Attachments: AMBARI-19170_branch-2.5.patch, AMBARI-19170_trunk.patch
>
>
> Ambari server upgrade path: 2.2.2.0 to 2.5.0.0-453
> Error seen while running 'ambari-server upgrade' command"
> {code}
> Using python /usr/bin/python
> Upgrading ambari-server
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> 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
> WARNING: Original file krb5JAASLogin.conf kept
> INFO: File krb5JAASLogin.conf updated.
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: No mpack replay logs found. Skipping replaying mpack commands
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Fixing database objects owner
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: using SERVICE_NAME instead of SID for Oracle
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> Ambari Server configured for Oracle. Confirm you have made a backup of the
> Ambari Server database [y/n] (y)? INFO: Loading properties from
> /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: using SERVICE_NAME instead of SID for Oracle
> INFO: Upgrading database schema
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: AMBARI_SERVER_LIB is not set, using default /usr/lib/ambari-server
> INFO: using SERVICE_NAME instead of SID for Oracle
> INFO: using SERVICE_NAME instead of SID for Oracle
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: about to run command: /usr/jdk64/jdk1.7.0_67/bin/java -cp
> '/etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/ojdbc6.jar'
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper >
> /var/log/ambari-server/ambari-server.out 2>&1
> 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
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:209)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:424)
> Caused by: java.lang.NullPointerException
> at
> com.google.inject.persist.jpa.JpaPersistService.begin(JpaPersistService.java:70)
> at
> com.google.inject.persist.jpa.AmbariJpaPersistService.begin(AmbariJpaPersistService.java:29)
> at
> org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.invoke(AmbariJpaLocalTxnInterceptor.java:106)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog240.executeDDLUpdates(UpgradeCatalog240.java:294)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeSchema(AbstractUpgradeCatalog.java:938)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:206)
> ... 1 more
> ERROR: Ambari server upgrade failed. Please look at
> /var/log/ambari-server/ambari-server.log, for more details.
> ERROR: Exiting with exit code 11.
> REASON: Schema upgrade failed.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19170) NPE during Ambari server schema upgrade
[
https://issues.apache.org/jira/browse/AMBARI-19170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-19170:
---
Attachment: AMBARI-19170_trunk.patch
> NPE during Ambari server schema upgrade
> ---
>
> Key: AMBARI-19170
> URL: https://issues.apache.org/jira/browse/AMBARI-19170
> Project: Ambari
> Issue Type: Bug
> Components: ambari-upgrade
>Affects Versions: 2.5.0
>Reporter: Vivek Sharma
>Assignee: Doroszlai, Attila
>Priority: Critical
> Labels: upgrade
> Fix For: 2.5.0
>
> Attachments: AMBARI-19170_branch-2.5.patch, AMBARI-19170_trunk.patch
>
>
> Ambari server upgrade path: 2.2.2.0 to 2.5.0.0-453
> Error seen while running 'ambari-server upgrade' command"
> {code}
> Using python /usr/bin/python
> Upgrading ambari-server
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> 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
> WARNING: Original file krb5JAASLogin.conf kept
> INFO: File krb5JAASLogin.conf updated.
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: No mpack replay logs found. Skipping replaying mpack commands
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Fixing database objects owner
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: using SERVICE_NAME instead of SID for Oracle
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> Ambari Server configured for Oracle. Confirm you have made a backup of the
> Ambari Server database [y/n] (y)? INFO: Loading properties from
> /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: using SERVICE_NAME instead of SID for Oracle
> INFO: Upgrading database schema
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: AMBARI_SERVER_LIB is not set, using default /usr/lib/ambari-server
> INFO: using SERVICE_NAME instead of SID for Oracle
> INFO: using SERVICE_NAME instead of SID for Oracle
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: about to run command: /usr/jdk64/jdk1.7.0_67/bin/java -cp
> '/etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/ojdbc6.jar'
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper >
> /var/log/ambari-server/ambari-server.out 2>&1
> 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
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:209)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:424)
> Caused by: java.lang.NullPointerException
> at
> com.google.inject.persist.jpa.JpaPersistService.begin(JpaPersistService.java:70)
> at
> com.google.inject.persist.jpa.AmbariJpaPersistService.begin(AmbariJpaPersistService.java:29)
> at
> org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.invoke(AmbariJpaLocalTxnInterceptor.java:106)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog240.executeDDLUpdates(UpgradeCatalog240.java:294)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeSchema(AbstractUpgradeCatalog.java:938)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:206)
> ... 1 more
> ERROR: Ambari server upgrade failed. Please look at
> /var/log/ambari-server/ambari-server.log, for more details.
> ERROR: Exiting with exit code 11.
> REASON: Schema upgrade failed.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19176) Perf: enable security fails
[
https://issues.apache.org/jira/browse/AMBARI-19176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15742973#comment-15742973
]
Hadoop QA commented on AMBARI-19176:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12842829/AMBARI-19176.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9631//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9631//console
This message is automatically generated.
> Perf: enable security fails
> ---
>
> Key: AMBARI-19176
> URL: https://issues.apache.org/jira/browse/AMBARI-19176
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
> Fix For: 2.5.0
>
> Attachments: AMBARI-19176.patch
>
>
> STR:
> 1) Go to "Enable security" wizard.
> 2) Choose MIT security.
> 3) Populate all fields and click "Next" button. "Next" button doesn't work.
> Failed request
> {code}
> Request URL:http://as:8080/api/v1/clusters/fff/services/KERBEROS
> Request Method:DELETE
> Status Code:404 Not Found
> Remote Address:104.196.95.5:8080
> message
> :
> "org.apache.ambari.server.controller.spi.NoSuchResourceException: The
> specified resource doesn't exist: Service not found, clusterName=fff,
> serviceName=KERBEROS"
> status
> :
> 404
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19169) Add Service Page in Atlas doesn't show config on change
[ https://issues.apache.org/jira/browse/AMBARI-19169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15742959#comment-15742959 ] Hudson commented on AMBARI-19169: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #511 (See [https://builds.apache.org/job/Ambari-branch-2.5/511/]) AMBARI-19169. Add Service Page in Atlas doesn't show config on change (akovalenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=41838162f55129f153cc358ba5d360cda62bb5ae]) * (edit) ambari-web/app/views/common/configs/service_configs_by_category_view.js * (edit) ambari-web/app/views/common/configs/widgets/config_widget_view.js > Add Service Page in Atlas doesn't show config on change > --- > > Key: AMBARI-19169 > URL: https://issues.apache.org/jira/browse/AMBARI-19169 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19169.patch > > > Steps to reproduce: > # Add Atlas service > # Under Authentication Tab > Enable LDAP Authentication > # This will open LDAP/AD section below > # Now in LDAP/AD section > select LDAP Authentication Type as AD, here the > properties related to AD are not shown. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19170) NPE during Ambari server schema upgrade
[
https://issues.apache.org/jira/browse/AMBARI-19170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-19170:
---
Attachment: AMBARI-19170_branch-2.5.patch
> NPE during Ambari server schema upgrade
> ---
>
> Key: AMBARI-19170
> URL: https://issues.apache.org/jira/browse/AMBARI-19170
> Project: Ambari
> Issue Type: Bug
> Components: ambari-upgrade
>Affects Versions: 2.5.0
>Reporter: Vivek Sharma
>Assignee: Doroszlai, Attila
>Priority: Critical
> Labels: upgrade
> Fix For: 2.5.0
>
> Attachments: AMBARI-19170_branch-2.5.patch
>
>
> Ambari server upgrade path: 2.2.2.0 to 2.5.0.0-453
> Error seen while running 'ambari-server upgrade' command"
> {code}
> Using python /usr/bin/python
> Upgrading ambari-server
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> 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
> WARNING: Original file krb5JAASLogin.conf kept
> INFO: File krb5JAASLogin.conf updated.
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: No mpack replay logs found. Skipping replaying mpack commands
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Fixing database objects owner
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: using SERVICE_NAME instead of SID for Oracle
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> Ambari Server configured for Oracle. Confirm you have made a backup of the
> Ambari Server database [y/n] (y)? INFO: Loading properties from
> /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: using SERVICE_NAME instead of SID for Oracle
> INFO: Upgrading database schema
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: AMBARI_SERVER_LIB is not set, using default /usr/lib/ambari-server
> INFO: using SERVICE_NAME instead of SID for Oracle
> INFO: using SERVICE_NAME instead of SID for Oracle
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: about to run command: /usr/jdk64/jdk1.7.0_67/bin/java -cp
> '/etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/ojdbc6.jar'
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper >
> /var/log/ambari-server/ambari-server.out 2>&1
> 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
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:209)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:424)
> Caused by: java.lang.NullPointerException
> at
> com.google.inject.persist.jpa.JpaPersistService.begin(JpaPersistService.java:70)
> at
> com.google.inject.persist.jpa.AmbariJpaPersistService.begin(AmbariJpaPersistService.java:29)
> at
> org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.invoke(AmbariJpaLocalTxnInterceptor.java:106)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog240.executeDDLUpdates(UpgradeCatalog240.java:294)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeSchema(AbstractUpgradeCatalog.java:938)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:206)
> ... 1 more
> ERROR: Ambari server upgrade failed. Please look at
> /var/log/ambari-server/ambari-server.log, for more details.
> ERROR: Exiting with exit code 11.
> REASON: Schema upgrade failed.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (AMBARI-19170) NPE during Ambari server schema upgrade
[
https://issues.apache.org/jira/browse/AMBARI-19170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila reassigned AMBARI-19170:
--
Assignee: Doroszlai, Attila
> NPE during Ambari server schema upgrade
> ---
>
> Key: AMBARI-19170
> URL: https://issues.apache.org/jira/browse/AMBARI-19170
> Project: Ambari
> Issue Type: Bug
> Components: ambari-upgrade
>Affects Versions: 2.5.0
>Reporter: Vivek Sharma
>Assignee: Doroszlai, Attila
>Priority: Critical
> Labels: upgrade
> Fix For: 2.5.0
>
>
> Ambari server upgrade path: 2.2.2.0 to 2.5.0.0-453
> Error seen while running 'ambari-server upgrade' command"
> {code}
> Using python /usr/bin/python
> Upgrading ambari-server
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> 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
> WARNING: Original file krb5JAASLogin.conf kept
> INFO: File krb5JAASLogin.conf updated.
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: No mpack replay logs found. Skipping replaying mpack commands
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Fixing database objects owner
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: using SERVICE_NAME instead of SID for Oracle
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> Ambari Server configured for Oracle. Confirm you have made a backup of the
> Ambari Server database [y/n] (y)? INFO: Loading properties from
> /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: using SERVICE_NAME instead of SID for Oracle
> INFO: Upgrading database schema
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: AMBARI_SERVER_LIB is not set, using default /usr/lib/ambari-server
> INFO: using SERVICE_NAME instead of SID for Oracle
> INFO: using SERVICE_NAME instead of SID for Oracle
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: about to run command: /usr/jdk64/jdk1.7.0_67/bin/java -cp
> '/etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/ojdbc6.jar'
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper >
> /var/log/ambari-server/ambari-server.out 2>&1
> 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
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:209)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:424)
> Caused by: java.lang.NullPointerException
> at
> com.google.inject.persist.jpa.JpaPersistService.begin(JpaPersistService.java:70)
> at
> com.google.inject.persist.jpa.AmbariJpaPersistService.begin(AmbariJpaPersistService.java:29)
> at
> org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.invoke(AmbariJpaLocalTxnInterceptor.java:106)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog240.executeDDLUpdates(UpgradeCatalog240.java:294)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeSchema(AbstractUpgradeCatalog.java:938)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:206)
> ... 1 more
> ERROR: Ambari server upgrade failed. Please look at
> /var/log/ambari-server/ambari-server.log, for more details.
> ERROR: Exiting with exit code 11.
> REASON: Schema upgrade failed.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19179) NPE during Ambari server schema upgrade
Doroszlai, Attila created AMBARI-19179:
--
Summary: NPE during Ambari server schema upgrade
Key: AMBARI-19179
URL: https://issues.apache.org/jira/browse/AMBARI-19179
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.5.0
Reporter: Doroszlai, Attila
Assignee: Doroszlai, Attila
Priority: Blocker
Fix For: 3.0.0, 2.5.0
Ambari server upgrade path: 2.2.2.0 to 2.5.0.0-453
{noformat}
NullPointerException
at
com.google.inject.persist.jpa.JpaPersistService.begin(JpaPersistService.java:70)
at
com.google.inject.persist.jpa.AmbariJpaPersistService.begin(AmbariJpaPersistService.java:29)
at
org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.invoke(AmbariJpaLocalTxnInterceptor.java:106)
at
org.apache.ambari.server.upgrade.UpgradeCatalog240.executeDDLUpdates(UpgradeCatalog240.java:294)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (AMBARI-19179) NPE during Ambari server schema upgrade
[
https://issues.apache.org/jira/browse/AMBARI-19179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila resolved AMBARI-19179.
Resolution: Duplicate
> NPE during Ambari server schema upgrade
> ---
>
> Key: AMBARI-19179
> URL: https://issues.apache.org/jira/browse/AMBARI-19179
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Blocker
> Fix For: 3.0.0, 2.5.0
>
>
> Ambari server upgrade path: 2.2.2.0 to 2.5.0.0-453
> {noformat}
> NullPointerException
> at
> com.google.inject.persist.jpa.JpaPersistService.begin(JpaPersistService.java:70)
> at
> com.google.inject.persist.jpa.AmbariJpaPersistService.begin(AmbariJpaPersistService.java:29)
> at
> org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.invoke(AmbariJpaLocalTxnInterceptor.java:106)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog240.executeDDLUpdates(UpgradeCatalog240.java:294)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19169) Add Service Page in Atlas doesn't show config on change
[ https://issues.apache.org/jira/browse/AMBARI-19169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15742815#comment-15742815 ] Aleksandr Kovalenko commented on AMBARI-19169: -- committed to trunk and branch-2.5 > Add Service Page in Atlas doesn't show config on change > --- > > Key: AMBARI-19169 > URL: https://issues.apache.org/jira/browse/AMBARI-19169 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19169.patch > > > Steps to reproduce: > # Add Atlas service > # Under Authentication Tab > Enable LDAP Authentication > # This will open LDAP/AD section below > # Now in LDAP/AD section > select LDAP Authentication Type as AD, here the > properties related to AD are not shown. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19176) Perf: enable security fails
[
https://issues.apache.org/jira/browse/AMBARI-19176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15742766#comment-15742766
]
Hadoop QA commented on AMBARI-19176:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12842829/AMBARI-19176.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9630//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9630//console
This message is automatically generated.
> Perf: enable security fails
> ---
>
> Key: AMBARI-19176
> URL: https://issues.apache.org/jira/browse/AMBARI-19176
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
> Fix For: 2.5.0
>
> Attachments: AMBARI-19176.patch
>
>
> STR:
> 1) Go to "Enable security" wizard.
> 2) Choose MIT security.
> 3) Populate all fields and click "Next" button. "Next" button doesn't work.
> Failed request
> {code}
> Request URL:http://as:8080/api/v1/clusters/fff/services/KERBEROS
> Request Method:DELETE
> Status Code:404 Not Found
> Remote Address:104.196.95.5:8080
> message
> :
> "org.apache.ambari.server.controller.spi.NoSuchResourceException: The
> specified resource doesn't exist: Service not found, clusterName=fff,
> serviceName=KERBEROS"
> status
> :
> 404
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19178) HostCleanup can't list process details on RHEL7
[ https://issues.apache.org/jira/browse/AMBARI-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-19178: --- Attachment: AMBARI-19178.patch > HostCleanup can't list process details on RHEL7 > --- > > Key: AMBARI-19178 > URL: https://issues.apache.org/jira/browse/AMBARI-19178 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: trunk, 2.5.0 >Reporter: Di Li >Assignee: Di Li > Attachments: AMBARI-19178.patch > > > need to use ps auxww instead of just ps aux -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19178) HostCleanup can't list process details on RHEL7
[ https://issues.apache.org/jira/browse/AMBARI-19178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-19178: --- Status: Patch Available (was: Open) > HostCleanup can't list process details on RHEL7 > --- > > Key: AMBARI-19178 > URL: https://issues.apache.org/jira/browse/AMBARI-19178 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: trunk, 2.5.0 >Reporter: Di Li >Assignee: Di Li > Attachments: AMBARI-19178.patch > > > need to use ps auxww instead of just ps aux -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19174) Version in process of downgrade isn't displayed by selecting any filter
[
https://issues.apache.org/jira/browse/AMBARI-19174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15742679#comment-15742679
]
Hadoop QA commented on AMBARI-19174:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12842825/AMBARI-19174.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9629//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9629//console
This message is automatically generated.
> Version in process of downgrade isn't displayed by selecting any filter
> ---
>
> Key: AMBARI-19174
> URL: https://issues.apache.org/jira/browse/AMBARI-19174
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-19174.patch, downgrade.jpg
>
>
> During downgrade no repo version is filtered by 'Upgrade/Downgrade in
> process' value. See screenshot attached
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19178) HostCleanup can't list process details on RHEL7
Di Li created AMBARI-19178: -- Summary: HostCleanup can't list process details on RHEL7 Key: AMBARI-19178 URL: https://issues.apache.org/jira/browse/AMBARI-19178 Project: Ambari Issue Type: Bug Components: ambari-agent Affects Versions: trunk, 2.5.0 Reporter: Di Li Assignee: Di Li need to use ps auxww instead of just ps aux -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-19167) Druid install through ambari is not optimal in selecting Druid-Historical service across the nodes.
[ https://issues.apache.org/jira/browse/AMBARI-19167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa resolved AMBARI-19167. --- Resolution: Invalid looks like this is already fixed. > Druid install through ambari is not optimal in selecting Druid-Historical > service across the nodes. > --- > > Key: AMBARI-19167 > URL: https://issues.apache.org/jira/browse/AMBARI-19167 > Project: Ambari > Issue Type: Task >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: 2.5.0 > > > Druid install through ambari is not optimal in selecting Druid-Historical > service across the nodes. > The ambari installer walks through Druid where it selects only one instance > of Druid-Historical service to be installed in any of the node. > Expecting this to recommend install of this services across the machines just > like Node Manager service in analogy. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19149) Clean up Ambari Server source code warnings
[ https://issues.apache.org/jira/browse/AMBARI-19149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15742629#comment-15742629 ] Hudson commented on AMBARI-19149: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6211 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6211/]) AMBARI-19149 - Clean up Ambari Server source code warnings (Attila (jhurley: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e4db57093f4d17497366cdfbf02127f36399bf42]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/checks/ServicesMapReduceDistributedCacheCheck.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/api/predicate/operators/GreaterEqualsOperatorTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/collections/PredicateUtils.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/api/services/stackadvisor/commands/StackAdvisorCommandTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/api/services/StacksServiceTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/audit/request/creator/PrivilegeEventCreatorTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/ServiceConfigVersionResponse.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ClusterPrivilegeResourceProviderTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/quicklinks/QuickLinksConfiguration.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/hooks/users/UserCreatedEvent.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/api/resources/BlueprintResourceDefinitionTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/api/services/AmbariPrivilegeService.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/view/AmbariViewsMDCLoggingFilter.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/collections/PredicateUtilsTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/checks/ComponentsInstallationCheck.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/api/services/GroupServiceTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/serveraction/ServerActionExecutor.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/dao/UserDAO.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/audit/StartOperationRequestAuditEventTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RequestStageContainer.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/dao/RequestScheduleDAO.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ConfigGroupConfigMappingEntityPK.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/collections/functors/EqualsPredicateTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/StackTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/utilities/KerberosChecker.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/view/persistence/DataStoreModule.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/topology/SettingFactory.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/checks/ServicesNamenodeHighAvailabilityCheck.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ArtifactEntity.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/authorization/internal/InternalTokenStorage.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/jmx/JMXHostProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/api/services/PrivilegeService.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/UserResourceProviderDBTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/HostKerberosIdentityResourceProviderTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/api/services/ActionService.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/audit/kerberos/CreatePrincipalKerberosAuditEventTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/predicate/OrPredicate.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ViewEntity.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/api/services/PersistenceManagerImplTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/api/services/PrivilegeServiceTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/api/query/render/MetricsPaddingRenderer.java * (edit)
[jira] [Commented] (AMBARI-19169) Add Service Page in Atlas doesn't show config on change
[
https://issues.apache.org/jira/browse/AMBARI-19169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15742605#comment-15742605
]
Hadoop QA commented on AMBARI-19169:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12842824/AMBARI-19169.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9628//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9628//console
This message is automatically generated.
> Add Service Page in Atlas doesn't show config on change
> ---
>
> Key: AMBARI-19169
> URL: https://issues.apache.org/jira/browse/AMBARI-19169
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19169.patch
>
>
> Steps to reproduce:
> # Add Atlas service
> # Under Authentication Tab > Enable LDAP Authentication
> # This will open LDAP/AD section below
> # Now in LDAP/AD section > select LDAP Authentication Type as AD, here the
> properties related to AD are not shown.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19177) kafka Consumer Alerting to check if the Kafka topics are able to read the data
[ https://issues.apache.org/jira/browse/AMBARI-19177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkata Sudheer Kumar M updated AMBARI-19177: - Flags: Patch Labels: patch (was: ) > kafka Consumer Alerting to check if the Kafka topics are able to read the data > -- > > Key: AMBARI-19177 > URL: https://issues.apache.org/jira/browse/AMBARI-19177 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.2.2 > Environment: HDP 2.3.4 >Reporter: Venkata Sudheer Kumar M > Labels: patch > Fix For: 2.4.1 > > > customer needs alerting for the Kafka topic when they are not able to consume > to data -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19177) kafka Consumer Alerting to check if the Kafka topics are able to read the data
Venkata Sudheer Kumar M created AMBARI-19177: Summary: kafka Consumer Alerting to check if the Kafka topics are able to read the data Key: AMBARI-19177 URL: https://issues.apache.org/jira/browse/AMBARI-19177 Project: Ambari Issue Type: Improvement Components: ambari-server Affects Versions: 2.2.2 Environment: HDP 2.3.4 Reporter: Venkata Sudheer Kumar M Fix For: 2.4.1 customer needs alerting for the Kafka topic when they are not able to consume to data -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19176) Perf: enable security fails
[
https://issues.apache.org/jira/browse/AMBARI-19176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen updated AMBARI-19176:
Status: Patch Available (was: Open)
> Perf: enable security fails
> ---
>
> Key: AMBARI-19176
> URL: https://issues.apache.org/jira/browse/AMBARI-19176
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
> Fix For: 2.5.0
>
> Attachments: AMBARI-19176.patch
>
>
> STR:
> 1) Go to "Enable security" wizard.
> 2) Choose MIT security.
> 3) Populate all fields and click "Next" button. "Next" button doesn't work.
> Failed request
> {code}
> Request URL:http://as:8080/api/v1/clusters/fff/services/KERBEROS
> Request Method:DELETE
> Status Code:404 Not Found
> Remote Address:104.196.95.5:8080
> message
> :
> "org.apache.ambari.server.controller.spi.NoSuchResourceException: The
> specified resource doesn't exist: Service not found, clusterName=fff,
> serviceName=KERBEROS"
> status
> :
> 404
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19176) Perf: enable security fails
[
https://issues.apache.org/jira/browse/AMBARI-19176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen updated AMBARI-19176:
Attachment: AMBARI-19176.patch
> Perf: enable security fails
> ---
>
> Key: AMBARI-19176
> URL: https://issues.apache.org/jira/browse/AMBARI-19176
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
> Fix For: 2.5.0
>
> Attachments: AMBARI-19176.patch
>
>
> STR:
> 1) Go to "Enable security" wizard.
> 2) Choose MIT security.
> 3) Populate all fields and click "Next" button. "Next" button doesn't work.
> Failed request
> {code}
> Request URL:http://as:8080/api/v1/clusters/fff/services/KERBEROS
> Request Method:DELETE
> Status Code:404 Not Found
> Remote Address:104.196.95.5:8080
> message
> :
> "org.apache.ambari.server.controller.spi.NoSuchResourceException: The
> specified resource doesn't exist: Service not found, clusterName=fff,
> serviceName=KERBEROS"
> status
> :
> 404
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19176) Perf: enable security fails
Dmytro Sen created AMBARI-19176:
---
Summary: Perf: enable security fails
Key: AMBARI-19176
URL: https://issues.apache.org/jira/browse/AMBARI-19176
Project: Ambari
Issue Type: Bug
Affects Versions: 2.5.0
Reporter: Dmytro Sen
Assignee: Dmytro Sen
Fix For: 2.5.0
STR:
1) Go to "Enable security" wizard.
2) Choose MIT security.
3) Populate all fields and click "Next" button. "Next" button doesn't work.
Failed request
{code}
Request URL:http://as:8080/api/v1/clusters/fff/services/KERBEROS
Request Method:DELETE
Status Code:404 Not Found
Remote Address:104.196.95.5:8080
message
:
"org.apache.ambari.server.controller.spi.NoSuchResourceException: The specified
resource doesn't exist: Service not found, clusterName=fff,
serviceName=KERBEROS"
status
:
404
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19149) Clean up Ambari Server source code warnings
[
https://issues.apache.org/jira/browse/AMBARI-19149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15742540#comment-15742540
]
Hadoop QA commented on AMBARI-19149:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12842827/AMBARI-19149-1.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9627//console
This message is automatically generated.
> Clean up Ambari Server source code warnings
> ---
>
> Key: AMBARI-19149
> URL: https://issues.apache.org/jira/browse/AMBARI-19149
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0
>
> Attachments: AMBARI-19149-1.patch, IDEA_Ambari_v1.xml
>
>
> Eclipse's default warnings generated for {{ambari-server}} number roughly
> over 3300. Out of these, at least half of them are:
> * Unused imports
> * Type safety due to forgotten {{<>}}
> * Missing Serialization IDs from anonymous {{HashMap}} implementations
> * Unused variables
> * {{Capture}} in tests
> * {{switch}} fall-through and missing {{case statements}}: *only makes
> changes which won't affect existing functionality*
> This makes spotting actual problems, like missing {{case}} statements a
> nightmare. We need to go through and clean out as many of these warnings as
> possible.
> Note: With respect to the import cleanup, the IDE of choice should have the
> following import order setup. They should always be expanded and never use
> {{*}}.
> # {{java}}
> # {{javax}}
> # {{org}}
> # {{com}}
> # other
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19149) Clean up Ambari Server source code warnings
[
https://issues.apache.org/jira/browse/AMBARI-19149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15742527#comment-15742527
]
Doroszlai, Attila commented on AMBARI-19149:
[~jonathan.hurley] committed [^AMBARI-19149-1.patch] (import cleanup) to
[trunk|http://git-wip-us.apache.org/repos/asf/ambari/commit/e4db5709]. Thanks!
> Clean up Ambari Server source code warnings
> ---
>
> Key: AMBARI-19149
> URL: https://issues.apache.org/jira/browse/AMBARI-19149
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0
>
> Attachments: AMBARI-19149-1.patch, IDEA_Ambari_v1.xml
>
>
> Eclipse's default warnings generated for {{ambari-server}} number roughly
> over 3300. Out of these, at least half of them are:
> * Unused imports
> * Type safety due to forgotten {{<>}}
> * Missing Serialization IDs from anonymous {{HashMap}} implementations
> * Unused variables
> * {{Capture}} in tests
> * {{switch}} fall-through and missing {{case statements}}: *only makes
> changes which won't affect existing functionality*
> This makes spotting actual problems, like missing {{case}} statements a
> nightmare. We need to go through and clean out as many of these warnings as
> possible.
> Note: With respect to the import cleanup, the IDE of choice should have the
> following import order setup. They should always be expanded and never use
> {{*}}.
> # {{java}}
> # {{javax}}
> # {{org}}
> # {{com}}
> # other
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19169) Add Service Page in Atlas doesn't show config on change
[
https://issues.apache.org/jira/browse/AMBARI-19169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15742517#comment-15742517
]
Hadoop QA commented on AMBARI-19169:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12842824/AMBARI-19169.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9626//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9626//console
This message is automatically generated.
> Add Service Page in Atlas doesn't show config on change
> ---
>
> Key: AMBARI-19169
> URL: https://issues.apache.org/jira/browse/AMBARI-19169
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19169.patch
>
>
> Steps to reproduce:
> # Add Atlas service
> # Under Authentication Tab > Enable LDAP Authentication
> # This will open LDAP/AD section below
> # Now in LDAP/AD section > select LDAP Authentication Type as AD, here the
> properties related to AD are not shown.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19149) Clean up Ambari Server source code warnings
[
https://issues.apache.org/jira/browse/AMBARI-19149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-19149:
---
Attachment: (was: AMBARI-19149-1.patch)
> Clean up Ambari Server source code warnings
> ---
>
> Key: AMBARI-19149
> URL: https://issues.apache.org/jira/browse/AMBARI-19149
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0
>
> Attachments: AMBARI-19149-1.patch, IDEA_Ambari_v1.xml
>
>
> Eclipse's default warnings generated for {{ambari-server}} number roughly
> over 3300. Out of these, at least half of them are:
> * Unused imports
> * Type safety due to forgotten {{<>}}
> * Missing Serialization IDs from anonymous {{HashMap}} implementations
> * Unused variables
> * {{Capture}} in tests
> * {{switch}} fall-through and missing {{case statements}}: *only makes
> changes which won't affect existing functionality*
> This makes spotting actual problems, like missing {{case}} statements a
> nightmare. We need to go through and clean out as many of these warnings as
> possible.
> Note: With respect to the import cleanup, the IDE of choice should have the
> following import order setup. They should always be expanded and never use
> {{*}}.
> # {{java}}
> # {{javax}}
> # {{org}}
> # {{com}}
> # other
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19149) Clean up Ambari Server source code warnings
[
https://issues.apache.org/jira/browse/AMBARI-19149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-19149:
---
Attachment: AMBARI-19149-1.patch
> Clean up Ambari Server source code warnings
> ---
>
> Key: AMBARI-19149
> URL: https://issues.apache.org/jira/browse/AMBARI-19149
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0
>
> Attachments: AMBARI-19149-1.patch, IDEA_Ambari_v1.xml
>
>
> Eclipse's default warnings generated for {{ambari-server}} number roughly
> over 3300. Out of these, at least half of them are:
> * Unused imports
> * Type safety due to forgotten {{<>}}
> * Missing Serialization IDs from anonymous {{HashMap}} implementations
> * Unused variables
> * {{Capture}} in tests
> * {{switch}} fall-through and missing {{case statements}}: *only makes
> changes which won't affect existing functionality*
> This makes spotting actual problems, like missing {{case}} statements a
> nightmare. We need to go through and clean out as many of these warnings as
> possible.
> Note: With respect to the import cleanup, the IDE of choice should have the
> following import order setup. They should always be expanded and never use
> {{*}}.
> # {{java}}
> # {{javax}}
> # {{org}}
> # {{com}}
> # other
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19149) Clean up Ambari Server source code warnings
[
https://issues.apache.org/jira/browse/AMBARI-19149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15742491#comment-15742491
]
Jonathan Hurley commented on AMBARI-19149:
--
Agreed - it's unrelated. We're actually seeing more of these lately and it's
most likely related to embedded Derby during the tests. I'll open a new Jira to
investigate this.
> Clean up Ambari Server source code warnings
> ---
>
> Key: AMBARI-19149
> URL: https://issues.apache.org/jira/browse/AMBARI-19149
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0
>
> Attachments: AMBARI-19149-1.patch, IDEA_Ambari_v1.xml
>
>
> Eclipse's default warnings generated for {{ambari-server}} number roughly
> over 3300. Out of these, at least half of them are:
> * Unused imports
> * Type safety due to forgotten {{<>}}
> * Missing Serialization IDs from anonymous {{HashMap}} implementations
> * Unused variables
> * {{Capture}} in tests
> * {{switch}} fall-through and missing {{case statements}}: *only makes
> changes which won't affect existing functionality*
> This makes spotting actual problems, like missing {{case}} statements a
> nightmare. We need to go through and clean out as many of these warnings as
> possible.
> Note: With respect to the import cleanup, the IDE of choice should have the
> following import order setup. They should always be expanded and never use
> {{*}}.
> # {{java}}
> # {{javax}}
> # {{org}}
> # {{com}}
> # other
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19149) Clean up Ambari Server source code warnings
[
https://issues.apache.org/jira/browse/AMBARI-19149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15742477#comment-15742477
]
Doroszlai, Attila commented on AMBARI-19149:
Failure is unrelated:
{noformat}
Failed tests:
ClusterDeadlockTest.testDeadlockWhileRestartingComponents:275
{noformat}
> Clean up Ambari Server source code warnings
> ---
>
> Key: AMBARI-19149
> URL: https://issues.apache.org/jira/browse/AMBARI-19149
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0
>
> Attachments: AMBARI-19149-1.patch, IDEA_Ambari_v1.xml
>
>
> Eclipse's default warnings generated for {{ambari-server}} number roughly
> over 3300. Out of these, at least half of them are:
> * Unused imports
> * Type safety due to forgotten {{<>}}
> * Missing Serialization IDs from anonymous {{HashMap}} implementations
> * Unused variables
> * {{Capture}} in tests
> * {{switch}} fall-through and missing {{case statements}}: *only makes
> changes which won't affect existing functionality*
> This makes spotting actual problems, like missing {{case}} statements a
> nightmare. We need to go through and clean out as many of these warnings as
> possible.
> Note: With respect to the import cleanup, the IDE of choice should have the
> following import order setup. They should always be expanded and never use
> {{*}}.
> # {{java}}
> # {{javax}}
> # {{org}}
> # {{com}}
> # other
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19174) Version in process of downgrade isn't displayed by selecting any filter
[ https://issues.apache.org/jira/browse/AMBARI-19174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-19174: -- Status: Patch Available (was: Open) > Version in process of downgrade isn't displayed by selecting any filter > --- > > Key: AMBARI-19174 > URL: https://issues.apache.org/jira/browse/AMBARI-19174 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-19174.patch, downgrade.jpg > > > During downgrade no repo version is filtered by 'Upgrade/Downgrade in > process' value. See screenshot attached -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19174) Version in process of downgrade isn't displayed by selecting any filter
[ https://issues.apache.org/jira/browse/AMBARI-19174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15742472#comment-15742472 ] Andrii Tkach commented on AMBARI-19174: --- 19881 tests complete (28 seconds) 153 tests pending > Version in process of downgrade isn't displayed by selecting any filter > --- > > Key: AMBARI-19174 > URL: https://issues.apache.org/jira/browse/AMBARI-19174 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-19174.patch, downgrade.jpg > > > During downgrade no repo version is filtered by 'Upgrade/Downgrade in > process' value. See screenshot attached -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19174) Version in process of downgrade isn't displayed by selecting any filter
[ https://issues.apache.org/jira/browse/AMBARI-19174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-19174: -- Attachment: AMBARI-19174.patch > Version in process of downgrade isn't displayed by selecting any filter > --- > > Key: AMBARI-19174 > URL: https://issues.apache.org/jira/browse/AMBARI-19174 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-19174.patch, downgrade.jpg > > > During downgrade no repo version is filtered by 'Upgrade/Downgrade in > process' value. See screenshot attached -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19160) Add ReviewBoard config file
[
https://issues.apache.org/jira/browse/AMBARI-19160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15742463#comment-15742463
]
Hudson commented on AMBARI-19160:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6210 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6210/])
AMBARI-19160. Add ReviewBoard config file (Attila Doroszlai via (oleewere:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e990fb8fcb6b2678b0c0c32f2689065a3f6616b3])
* (add) .reviewboardrc
> Add ReviewBoard config file
> ---
>
> Key: AMBARI-19160
> URL: https://issues.apache.org/jira/browse/AMBARI-19160
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Trivial
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-19160.patch
>
>
> ReviewBoard has [command-line
> tools|https://www.reviewboard.org/docs/rbtools/] for working with review
> requests. The goal of this task is to add a small [config
> file|https://www.reviewboard.org/docs/rbtools/0.7/rbt/configuration/repositories/#reviewboardrc]
> to the Ambari project, so that {{rbt}} can talk to the right RB server
> out-of-the box.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19158) Plugin configuration ignored when directly running checkstyle goals
[
https://issues.apache.org/jira/browse/AMBARI-19158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15742461#comment-15742461
]
Hudson commented on AMBARI-19158:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6210 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6210/])
AMBARI-19158. Plugin configuration ignored when directly running (oleewere:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=cc5645831dfcb59b9318bd29eea5a741ba7097be])
* (edit) ambari-project/pom.xml
> Plugin configuration ignored when directly running checkstyle goals
> ---
>
> Key: AMBARI-19158
> URL: https://issues.apache.org/jira/browse/AMBARI-19158
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Minor
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-19158.patch
>
>
> Checkstyle uses the default checks when running {{mvn checkstyle:check}} on
> {{ambari-server}} instead of the custom list defined in
> {{ambari-server/checkstyle.xml}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19162) LogSearch - use fully qualified hostname instead of localhost for spnego.host
[ https://issues.apache.org/jira/browse/AMBARI-19162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15742462#comment-15742462 ] Hudson commented on AMBARI-19162: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6210 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6210/]) AMBARI-19162. LogSearch - use fully qualified hostname instead of (oleewere: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=66124ac8a31894637ed95094d1e40d9e7e86a791]) * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/configuration/logsearch-properties.xml * (edit) ambari-server/src/test/python/stacks/2.4/configs/default.json * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/package/scripts/params.py * (edit) ambari-server/src/test/python/stacks/2.4/LOGSEARCH/test_logsearch.py > LogSearch - use fully qualified hostname instead of localhost for spnego.host > - > > Key: AMBARI-19162 > URL: https://issues.apache.org/jira/browse/AMBARI-19162 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, ambari-server >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 2.5.0 > > Attachments: AMBARI-19162.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19149) Clean up Ambari Server source code warnings
[
https://issues.apache.org/jira/browse/AMBARI-19149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15742460#comment-15742460
]
Hudson commented on AMBARI-19149:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6210 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6210/])
AMBARI-19149. Code cleanup: fallthrough (Attila Doroszlai via oleewere)
(oleewere:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=076ed757b83a5d6907f7239f6de1334c81aeecc7])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/ControllerModule.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/stack/ConfigurationDirectory.java
* (edit) ambari-server/src/main/java/org/apache/ambari/server/state/State.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/agent/TestActionQueue.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/DBAccessorImpl.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/audit/request/eventcreator/UserEventCreator.java
* (edit) ambari-server/checkstyle.xml
> Clean up Ambari Server source code warnings
> ---
>
> Key: AMBARI-19149
> URL: https://issues.apache.org/jira/browse/AMBARI-19149
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0
>
> Attachments: AMBARI-19149-1.patch, IDEA_Ambari_v1.xml
>
>
> Eclipse's default warnings generated for {{ambari-server}} number roughly
> over 3300. Out of these, at least half of them are:
> * Unused imports
> * Type safety due to forgotten {{<>}}
> * Missing Serialization IDs from anonymous {{HashMap}} implementations
> * Unused variables
> * {{Capture}} in tests
> * {{switch}} fall-through and missing {{case statements}}: *only makes
> changes which won't affect existing functionality*
> This makes spotting actual problems, like missing {{case}} statements a
> nightmare. We need to go through and clean out as many of these warnings as
> possible.
> Note: With respect to the import cleanup, the IDE of choice should have the
> following import order setup. They should always be expanded and never use
> {{*}}.
> # {{java}}
> # {{javax}}
> # {{org}}
> # {{com}}
> # other
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19175) DB configs consistency check failed after disable kerberos or Ambari upgrade
[
https://issues.apache.org/jira/browse/AMBARI-19175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-19175:
Affects Version/s: 2.5.0
> DB configs consistency check failed after disable kerberos or Ambari upgrade
>
>
> Key: AMBARI-19175
> URL: https://issues.apache.org/jira/browse/AMBARI-19175
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Fix For: 2.5.0
>
>
> DB configs consistency check failed after disable kerberos.
> Services start successful and service check passed.
> {noformat}Checking database
> DB configs consistency check failed. Run "ambari-server start
> --skip-database-check" to skip.
> You may try --auto-fix-database flag to attempt to fix issues automatically.
> If you use this "--skip-database-check" option, do not make any changes to
> your cluster topology or perform a cluster upgrade until you correct the
> database consistency issues.
> See "/var/log/ambari-server/ambari-server-check-database.log" for more
> details on the consistency issues.
> Ambari Server 'check-database' completed{noformat}
> =
> Also seen after Ambari upgrade. Below entry in
> ambari-server-check-database.log might be the issue:
> {code}
> 2016-12-12 15:49:03,973 ERROR - Found configs that are not mapped to any
> service!
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19169) Add Service Page in Atlas doesn't show config on change
[ https://issues.apache.org/jira/browse/AMBARI-19169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-19169: - Attachment: AMBARI-19169.patch > Add Service Page in Atlas doesn't show config on change > --- > > Key: AMBARI-19169 > URL: https://issues.apache.org/jira/browse/AMBARI-19169 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19169.patch > > > Steps to reproduce: > # Add Atlas service > # Under Authentication Tab > Enable LDAP Authentication > # This will open LDAP/AD section below > # Now in LDAP/AD section > select LDAP Authentication Type as AD, here the > properties related to AD are not shown. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19169) Add Service Page in Atlas doesn't show config on change
[ https://issues.apache.org/jira/browse/AMBARI-19169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-19169: - Status: Patch Available (was: Open) > Add Service Page in Atlas doesn't show config on change > --- > > Key: AMBARI-19169 > URL: https://issues.apache.org/jira/browse/AMBARI-19169 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19169.patch > > > Steps to reproduce: > # Add Atlas service > # Under Authentication Tab > Enable LDAP Authentication > # This will open LDAP/AD section below > # Now in LDAP/AD section > select LDAP Authentication Type as AD, here the > properties related to AD are not shown. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19175) DB configs consistency check failed after disable kerberos or Ambari upgrade
[
https://issues.apache.org/jira/browse/AMBARI-19175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-19175:
Fix Version/s: 2.5.0
> DB configs consistency check failed after disable kerberos or Ambari upgrade
>
>
> Key: AMBARI-19175
> URL: https://issues.apache.org/jira/browse/AMBARI-19175
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Fix For: 2.5.0
>
>
> DB configs consistency check failed after disable kerberos.
> Services start successful and service check passed.
> {noformat}Checking database
> DB configs consistency check failed. Run "ambari-server start
> --skip-database-check" to skip.
> You may try --auto-fix-database flag to attempt to fix issues automatically.
> If you use this "--skip-database-check" option, do not make any changes to
> your cluster topology or perform a cluster upgrade until you correct the
> database consistency issues.
> See "/var/log/ambari-server/ambari-server-check-database.log" for more
> details on the consistency issues.
> Ambari Server 'check-database' completed{noformat}
> =
> Also seen after Ambari upgrade. Below entry in
> ambari-server-check-database.log might be the issue:
> {code}
> 2016-12-12 15:49:03,973 ERROR - Found configs that are not mapped to any
> service!
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19175) DB configs consistency check failed after disable kerberos or Ambari upgrade
Dmitry Lysnichenko created AMBARI-19175:
---
Summary: DB configs consistency check failed after disable
kerberos or Ambari upgrade
Key: AMBARI-19175
URL: https://issues.apache.org/jira/browse/AMBARI-19175
Project: Ambari
Issue Type: Bug
Reporter: Dmitry Lysnichenko
Assignee: Dmitry Lysnichenko
Priority: Blocker
DB configs consistency check failed after disable kerberos.
Services start successful and service check passed.
{noformat}Checking database
DB configs consistency check failed. Run "ambari-server start
--skip-database-check" to skip.
You may try --auto-fix-database flag to attempt to fix issues automatically.
If you use this "--skip-database-check" option, do not make any changes to your
cluster topology or perform a cluster upgrade until you correct the database
consistency issues.
See "/var/log/ambari-server/ambari-server-check-database.log" for more details
on the consistency issues.
Ambari Server 'check-database' completed{noformat}
=
Also seen after Ambari upgrade. Below entry in ambari-server-check-database.log
might be the issue:
{code}
2016-12-12 15:49:03,973 ERROR - Found configs that are not mapped to any
service!
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19175) DB configs consistency check failed after disable kerberos or Ambari upgrade
[
https://issues.apache.org/jira/browse/AMBARI-19175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-19175:
Component/s: ambari-server
> DB configs consistency check failed after disable kerberos or Ambari upgrade
>
>
> Key: AMBARI-19175
> URL: https://issues.apache.org/jira/browse/AMBARI-19175
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
>
> DB configs consistency check failed after disable kerberos.
> Services start successful and service check passed.
> {noformat}Checking database
> DB configs consistency check failed. Run "ambari-server start
> --skip-database-check" to skip.
> You may try --auto-fix-database flag to attempt to fix issues automatically.
> If you use this "--skip-database-check" option, do not make any changes to
> your cluster topology or perform a cluster upgrade until you correct the
> database consistency issues.
> See "/var/log/ambari-server/ambari-server-check-database.log" for more
> details on the consistency issues.
> Ambari Server 'check-database' completed{noformat}
> =
> Also seen after Ambari upgrade. Below entry in
> ambari-server-check-database.log might be the issue:
> {code}
> 2016-12-12 15:49:03,973 ERROR - Found configs that are not mapped to any
> service!
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19149) Clean up Ambari Server source code warnings
[
https://issues.apache.org/jira/browse/AMBARI-19149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15742449#comment-15742449
]
Jonathan Hurley commented on AMBARI-19149:
--
Yep, I confirmed that AMBARI-19158 fixes the issues we were seeing running
checkstyle. Thanks Attila!
What are your thoughts about creating a new Jira to track moving the
{{utility}} project under {{org.apache.ambari}} ?
> Clean up Ambari Server source code warnings
> ---
>
> Key: AMBARI-19149
> URL: https://issues.apache.org/jira/browse/AMBARI-19149
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0
>
> Attachments: AMBARI-19149-1.patch, IDEA_Ambari_v1.xml
>
>
> Eclipse's default warnings generated for {{ambari-server}} number roughly
> over 3300. Out of these, at least half of them are:
> * Unused imports
> * Type safety due to forgotten {{<>}}
> * Missing Serialization IDs from anonymous {{HashMap}} implementations
> * Unused variables
> * {{Capture}} in tests
> * {{switch}} fall-through and missing {{case statements}}: *only makes
> changes which won't affect existing functionality*
> This makes spotting actual problems, like missing {{case}} statements a
> nightmare. We need to go through and clean out as many of these warnings as
> possible.
> Note: With respect to the import cleanup, the IDE of choice should have the
> following import order setup. They should always be expanded and never use
> {{*}}.
> # {{java}}
> # {{javax}}
> # {{org}}
> # {{com}}
> # other
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19158) Plugin configuration ignored when directly running checkstyle goals
[
https://issues.apache.org/jira/browse/AMBARI-19158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15742442#comment-15742442
]
Hudson commented on AMBARI-19158:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #510 (See
[https://builds.apache.org/job/Ambari-branch-2.5/510/])
AMBARI-19158. Plugin configuration ignored when directly running (oleewere:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=c2a4fa64db2b148b5a174fb936120a3239a6271c])
* (edit) ambari-project/pom.xml
> Plugin configuration ignored when directly running checkstyle goals
> ---
>
> Key: AMBARI-19158
> URL: https://issues.apache.org/jira/browse/AMBARI-19158
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Minor
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-19158.patch
>
>
> Checkstyle uses the default checks when running {{mvn checkstyle:check}} on
> {{ambari-server}} instead of the custom list defined in
> {{ambari-server/checkstyle.xml}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19162) LogSearch - use fully qualified hostname instead of localhost for spnego.host
[ https://issues.apache.org/jira/browse/AMBARI-19162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15742444#comment-15742444 ] Hudson commented on AMBARI-19162: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #510 (See [https://builds.apache.org/job/Ambari-branch-2.5/510/]) AMBARI-19162. LogSearch - use fully qualified hostname instead of (oleewere: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f570eae37b5b3ebbdee4a6a0a80ceb2c87a6a634]) * (edit) ambari-server/src/test/python/stacks/2.4/LOGSEARCH/test_logsearch.py * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/configuration/logsearch-properties.xml * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/package/scripts/params.py * (edit) ambari-server/src/test/python/stacks/2.4/configs/default.json > LogSearch - use fully qualified hostname instead of localhost for spnego.host > - > > Key: AMBARI-19162 > URL: https://issues.apache.org/jira/browse/AMBARI-19162 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, ambari-server >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 2.5.0 > > Attachments: AMBARI-19162.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19160) Add ReviewBoard config file
[
https://issues.apache.org/jira/browse/AMBARI-19160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15742445#comment-15742445
]
Hudson commented on AMBARI-19160:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #510 (See
[https://builds.apache.org/job/Ambari-branch-2.5/510/])
AMBARI-19160. Add ReviewBoard config file (Attila Doroszlai via (oleewere:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=87a8b00acf46ec5be2640dda0bede19d16d9788d])
* (add) .reviewboardrc
> Add ReviewBoard config file
> ---
>
> Key: AMBARI-19160
> URL: https://issues.apache.org/jira/browse/AMBARI-19160
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Trivial
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-19160.patch
>
>
> ReviewBoard has [command-line
> tools|https://www.reviewboard.org/docs/rbtools/] for working with review
> requests. The goal of this task is to add a small [config
> file|https://www.reviewboard.org/docs/rbtools/0.7/rbt/configuration/repositories/#reviewboardrc]
> to the Ambari project, so that {{rbt}} can talk to the right RB server
> out-of-the box.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19149) Clean up Ambari Server source code warnings
[
https://issues.apache.org/jira/browse/AMBARI-19149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15742431#comment-15742431
]
Doroszlai, Attila commented on AMBARI-19149:
* {{test}} phase fails if style checks fail: OK.
* {{mvn checkstyle:check}} works (since AMBARI-19158 is fixed): OK
* We still have several cleanups to go, will post patches when they are ready.
To be able to build just one project (eg. {{ambari-server}}), one needs to have
the dependencies installed. This is nothing new.
Try this:
{noformat}
rm -fr ~/.m2/repository/utility
rm -fr ~/.m2/repository/org/apache/ambari
git checkout branch-2.4
git clean -fd
cd ambari-server
mvn compile
{noformat}
It will fail with:
{noformat}
[ERROR] Failed to execute goal on project ambari-server: Could not resolve
dependencies for project org.apache.ambari:ambari-server:jar:2.4.2.0.0: The
following artifacts could not be resolved:
org.apache.ambari:ambari-views:jar:2.4.2.0.0,
org.apache.ambari:ambari-metrics-common:jar:2.4.2.0.0: Could not find artifact
org.apache.ambari:ambari-views:jar:2.4.2.0.0 in oss.sonatype.org
(https://oss.sonatype.org/content/groups/staging) -> [Help 1]
{noformat}
branch-2.4 has no {{utility}} module, but {{ambari-server}} has several other
dependencies. If one can build {{ambari-server}} without having to worry about
those dependencies, it's just that they are already built, installed (in
{{~/.m2/repository}}) and forgotten about. However, if they change in ways
that affect {{ambari-server}}, then they need to be rebuilt.
> Clean up Ambari Server source code warnings
> ---
>
> Key: AMBARI-19149
> URL: https://issues.apache.org/jira/browse/AMBARI-19149
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0
>
> Attachments: AMBARI-19149-1.patch, IDEA_Ambari_v1.xml
>
>
> Eclipse's default warnings generated for {{ambari-server}} number roughly
> over 3300. Out of these, at least half of them are:
> * Unused imports
> * Type safety due to forgotten {{<>}}
> * Missing Serialization IDs from anonymous {{HashMap}} implementations
> * Unused variables
> * {{Capture}} in tests
> * {{switch}} fall-through and missing {{case statements}}: *only makes
> changes which won't affect existing functionality*
> This makes spotting actual problems, like missing {{case}} statements a
> nightmare. We need to go through and clean out as many of these warnings as
> possible.
> Note: With respect to the import cleanup, the IDE of choice should have the
> following import order setup. They should always be expanded and never use
> {{*}}.
> # {{java}}
> # {{javax}}
> # {{org}}
> # {{com}}
> # other
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19161) Hadoop native library location need to be changed in mapred-site.xml for PPC
[
https://issues.apache.org/jira/browse/AMBARI-19161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15742390#comment-15742390
]
Hudson commented on AMBARI-19161:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6209 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6209/])
AMBARI-19161. Hadoop native library location need to be changed in (aonishuk:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=baad9b9cdd4783a889ce8dab5395ca9f2ad7533a])
* (edit)
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/configuration/hadoop-env.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.3/services/OOZIE/configuration/oozie-env.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.2/services/YARN/configuration-mapred/mapred-site.xml
* (edit)
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/params_linux.py
* (edit)
ambari-server/src/main/resources/common-services/TEZ/0.4.0.2.1/configuration/tez-site.xml
* (edit)
ambari-server/src/main/resources/common-services/TEZ/0.4.0.2.1/package/scripts/params_linux.py
* (edit)
ambari-server/src/main/resources/common-services/OOZIE/4.2.0.2.3/configuration/oozie-env.xml
* (add)
ambari-common/src/main/python/resource_management/libraries/functions/get_architecture.py
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.2/services/TEZ/configuration/tez-site.xml
* (edit)
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/configuration-mapred/mapred-site.xml
* (edit)
ambari-server/src/main/resources/common-services/YARN/3.0.0/package/scripts/params_linux.py
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.2/services/OOZIE/configuration/oozie-env.xml
* (edit)
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/params_linux.py
* (edit)
ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/params_linux.py
* (edit)
ambari-server/src/main/resources/stacks/HDP/3.0/services/YARN/configuration-mapred/mapred-site.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.0.6/services/OOZIE/configuration/oozie-env.xml
* (edit)
ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/configuration/oozie-env.xml
> Hadoop native library location need to be changed in mapred-site.xml for PPC
> -
>
> Key: AMBARI-19161
> URL: https://issues.apache.org/jira/browse/AMBARI-19161
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-19161.patch, AMBARI-19161.patch
>
>
> ppc64le hadoop native library location to be changed to :
> /usr/hdp/2.5.0.0-1245/hadoop/lib/native/Linux-ppc64le-64/ for IBM
> We need to modify /usr/hdp/2.5.0.0-1245/hadoop/conf/mapred-site.xml
>
>
>
> FROM:
>
> mapreduce.admin.user.env
>
> LD_LIBRARY_PATH=/usr/hdp/${hdp.version}/hadoop/lib/native:/usr/hdp/${hdp.version}/hadoop/lib/native/Linux-amd64-64
>
>
> TO:
>
> mapreduce.admin.user.env
>
> LD_LIBRARY_PATH=/usr/hdp/${hdp.version}/hadoop/lib/native:/usr/hdp/${hdp.version}/hadoop/lib/native/Linux-ppc64le-64
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19161) Hadoop native library location need to be changed in mapred-site.xml for PPC
[
https://issues.apache.org/jira/browse/AMBARI-19161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15742380#comment-15742380
]
Hudson commented on AMBARI-19161:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #509 (See
[https://builds.apache.org/job/Ambari-branch-2.5/509/])
AMBARI-19161. Hadoop native library location need to be changed in (aonishuk:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=0c89587a9c773a4469833cc9b7253c05549e1388])
* (edit)
ambari-server/src/main/resources/common-services/TEZ/0.4.0.2.1/package/scripts/params_linux.py
* (edit)
ambari-server/src/main/resources/common-services/TEZ/0.4.0.2.1/configuration/tez-site.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.2/services/OOZIE/configuration/oozie-env.xml
* (edit)
ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/configuration/oozie-env.xml
* (edit)
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/configuration/hadoop-env.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.0.6/services/OOZIE/configuration/oozie-env.xml
* (edit)
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/configuration-mapred/mapred-site.xml
* (edit)
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/params_linux.py
* (edit)
ambari-server/src/main/resources/stacks/HDP/3.0/services/YARN/configuration-mapred/mapred-site.xml
* (edit)
ambari-server/src/main/resources/common-services/OOZIE/4.2.0.2.3/configuration/oozie-env.xml
* (edit)
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/params_linux.py
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.3/services/OOZIE/configuration/oozie-env.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.2/services/YARN/configuration-mapred/mapred-site.xml
* (add)
ambari-common/src/main/python/resource_management/libraries/functions/get_architecture.py
* (edit)
ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/params_linux.py
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.2/services/TEZ/configuration/tez-site.xml
* (edit)
ambari-server/src/main/resources/common-services/YARN/3.0.0/package/scripts/params_linux.py
> Hadoop native library location need to be changed in mapred-site.xml for PPC
> -
>
> Key: AMBARI-19161
> URL: https://issues.apache.org/jira/browse/AMBARI-19161
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-19161.patch, AMBARI-19161.patch
>
>
> ppc64le hadoop native library location to be changed to :
> /usr/hdp/2.5.0.0-1245/hadoop/lib/native/Linux-ppc64le-64/ for IBM
> We need to modify /usr/hdp/2.5.0.0-1245/hadoop/conf/mapred-site.xml
>
>
>
> FROM:
>
> mapreduce.admin.user.env
>
> LD_LIBRARY_PATH=/usr/hdp/${hdp.version}/hadoop/lib/native:/usr/hdp/${hdp.version}/hadoop/lib/native/Linux-amd64-64
>
>
> TO:
>
> mapreduce.admin.user.env
>
> LD_LIBRARY_PATH=/usr/hdp/${hdp.version}/hadoop/lib/native:/usr/hdp/${hdp.version}/hadoop/lib/native/Linux-ppc64le-64
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19162) LogSearch - use fully qualified hostname instead of localhost for spnego.host
[
https://issues.apache.org/jira/browse/AMBARI-19162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-19162:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
committed to trunk:
{code:java}
commit 66124ac8a31894637ed95094d1e40d9e7e86a791
Author: oleewere
Date: Mon Dec 12 17:19:24 2016 +0100
AMBARI-19162. LogSearch - use fully qualified hostname instead of localhost
for spnego.host (oleewere)
Change-Id: I0757c4358213cd300bdc3c9179afa15e9acd
{code}
committed to branch-2.5:
{code:java}
commit f570eae37b5b3ebbdee4a6a0a80ceb2c87a6a634
Author: oleewere
Date: Mon Dec 12 17:19:24 2016 +0100
AMBARI-19162. LogSearch - use fully qualified hostname instead of localhost
for spnego.host (oleewere)
Change-Id: I0757c4358213cd300bdc3c9179afa15e9acd
{code}
> LogSearch - use fully qualified hostname instead of localhost for spnego.host
> -
>
> Key: AMBARI-19162
> URL: https://issues.apache.org/jira/browse/AMBARI-19162
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch, ambari-server
>Affects Versions: 2.4.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 2.5.0
>
> Attachments: AMBARI-19162.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19133) hadoop.proxyuser.HTTP.hosts should not be updated when Hive is installed unless WebHcat is installed
[
https://issues.apache.org/jira/browse/AMBARI-19133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15742358#comment-15742358
]
Hadoop QA commented on AMBARI-19133:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12842810/AMBARI-19133_trunk_02.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9625//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9625//console
This message is automatically generated.
> hadoop.proxyuser.HTTP.hosts should not be updated when Hive is installed
> unless WebHcat is installed
>
>
> Key: AMBARI-19133
> URL: https://issues.apache.org/jira/browse/AMBARI-19133
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: kerberos, kerberos_descriptor
> Fix For: 2.5.0
>
> Attachments: AMBARI-19133_branch-2.5_01.patch,
> AMBARI-19133_branch-2.5_02.patch, AMBARI-19133_trunk_01.patch,
> AMBARI-19133_trunk_02.patch
>
>
> {{hadoop.proxyuser.HTTP.hosts}} should not be updated when Hive is installed
> unless WebHcat is installed.
> This is happening because the following block in the Kerberos descriptor is
> at the HIVE service level rather than the WEBHCAT_SERVER component level.
> {code}
> {
> "core-site": {
> "hadoop.proxyuser.HTTP.hosts":
> "${clusterHostInfo/webhcat_server_host}"
> }
> },
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19149) Clean up Ambari Server source code warnings
[
https://issues.apache.org/jira/browse/AMBARI-19149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15742332#comment-15742332
]
Jonathan Hurley commented on AMBARI-19149:
--
So, where are we at with this? I think we wanted to:
- Have the {{test}} phase fail if these style checks fail.
- Allow developers to very easily run the checks directly (ie {{mvn
checkstyle:check}} from {{ambari-server}}) and just have it work.
> Clean up Ambari Server source code warnings
> ---
>
> Key: AMBARI-19149
> URL: https://issues.apache.org/jira/browse/AMBARI-19149
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0
>
> Attachments: AMBARI-19149-1.patch, IDEA_Ambari_v1.xml
>
>
> Eclipse's default warnings generated for {{ambari-server}} number roughly
> over 3300. Out of these, at least half of them are:
> * Unused imports
> * Type safety due to forgotten {{<>}}
> * Missing Serialization IDs from anonymous {{HashMap}} implementations
> * Unused variables
> * {{Capture}} in tests
> * {{switch}} fall-through and missing {{case statements}}: *only makes
> changes which won't affect existing functionality*
> This makes spotting actual problems, like missing {{case}} statements a
> nightmare. We need to go through and clean out as many of these warnings as
> possible.
> Note: With respect to the import cleanup, the IDE of choice should have the
> following import order setup. They should always be expanded and never use
> {{*}}.
> # {{java}}
> # {{javax}}
> # {{org}}
> # {{com}}
> # other
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19158) Plugin configuration ignored when directly running checkstyle goals
[
https://issues.apache.org/jira/browse/AMBARI-19158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-19158:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
committed to trunk:
{code:java}
commit cc5645831dfcb59b9318bd29eea5a741ba7097be
Author: Attila Doroszlai
Date: Mon Dec 12 16:55:24 2016 +0100
AMBARI-19158. Plugin configuration ignored when directly running checkstyle
goals (Attila Doroszlai via oleewere)
Change-Id: Iaf65354eec0adfcf9a2dc7bb0cdb1356f81099b9
{code}
committed to branch-2.5:
{code:java}
commit c2a4fa64db2b148b5a174fb936120a3239a6271c
Author: Attila Doroszlai
Date: Mon Dec 12 16:55:24 2016 +0100
AMBARI-19158. Plugin configuration ignored when directly running checkstyle
goals (Attila Doroszlai via oleewere)
Change-Id: Iaf65354eec0adfcf9a2dc7bb0cdb1356f81099b9
{code}
> Plugin configuration ignored when directly running checkstyle goals
> ---
>
> Key: AMBARI-19158
> URL: https://issues.apache.org/jira/browse/AMBARI-19158
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Minor
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-19158.patch
>
>
> Checkstyle uses the default checks when running {{mvn checkstyle:check}} on
> {{ambari-server}} instead of the custom list defined in
> {{ambari-server/checkstyle.xml}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19149) Clean up Ambari Server source code warnings
[
https://issues.apache.org/jira/browse/AMBARI-19149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15742324#comment-15742324
]
Olivér Szabó commented on AMBARI-19149:
---
committed to trunk:
{code:java}
commit 076ed757b83a5d6907f7239f6de1334c81aeecc7
Author: Attila Doroszlai
Date: Mon Dec 12 16:58:54 2016 +0100
AMBARI-19149. Code cleanup: fallthrough (Attila Doroszlai via oleewere)
Change-Id: I6925a08c0ebe7c12b26691646d3c335342913b2e
{code}
> Clean up Ambari Server source code warnings
> ---
>
> Key: AMBARI-19149
> URL: https://issues.apache.org/jira/browse/AMBARI-19149
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0
>
> Attachments: AMBARI-19149-1.patch, IDEA_Ambari_v1.xml
>
>
> Eclipse's default warnings generated for {{ambari-server}} number roughly
> over 3300. Out of these, at least half of them are:
> * Unused imports
> * Type safety due to forgotten {{<>}}
> * Missing Serialization IDs from anonymous {{HashMap}} implementations
> * Unused variables
> * {{Capture}} in tests
> * {{switch}} fall-through and missing {{case statements}}: *only makes
> changes which won't affect existing functionality*
> This makes spotting actual problems, like missing {{case}} statements a
> nightmare. We need to go through and clean out as many of these warnings as
> possible.
> Note: With respect to the import cleanup, the IDE of choice should have the
> following import order setup. They should always be expanded and never use
> {{*}}.
> # {{java}}
> # {{javax}}
> # {{org}}
> # {{com}}
> # other
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19174) Version in process of downgrade isn't displayed by selecting any filter
Andrii Tkach created AMBARI-19174: - Summary: Version in process of downgrade isn't displayed by selecting any filter Key: AMBARI-19174 URL: https://issues.apache.org/jira/browse/AMBARI-19174 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Priority: Critical Fix For: 3.0.0 Attachments: downgrade.jpg During downgrade no repo version is filtered by 'Upgrade/Downgrade in process' value. See screenshot attached -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19174) Version in process of downgrade isn't displayed by selecting any filter
[ https://issues.apache.org/jira/browse/AMBARI-19174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-19174: -- Attachment: downgrade.jpg > Version in process of downgrade isn't displayed by selecting any filter > --- > > Key: AMBARI-19174 > URL: https://issues.apache.org/jira/browse/AMBARI-19174 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 3.0.0 > > Attachments: downgrade.jpg > > > During downgrade no repo version is filtered by 'Upgrade/Downgrade in > process' value. See screenshot attached -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19161) Hadoop native library location need to be changed in mapred-site.xml for PPC
[
https://issues.apache.org/jira/browse/AMBARI-19161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-19161:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk and branch-2.5
> Hadoop native library location need to be changed in mapred-site.xml for PPC
> -
>
> Key: AMBARI-19161
> URL: https://issues.apache.org/jira/browse/AMBARI-19161
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-19161.patch, AMBARI-19161.patch
>
>
> ppc64le hadoop native library location to be changed to :
> /usr/hdp/2.5.0.0-1245/hadoop/lib/native/Linux-ppc64le-64/ for IBM
> We need to modify /usr/hdp/2.5.0.0-1245/hadoop/conf/mapred-site.xml
>
>
>
> FROM:
>
> mapreduce.admin.user.env
>
> LD_LIBRARY_PATH=/usr/hdp/${hdp.version}/hadoop/lib/native:/usr/hdp/${hdp.version}/hadoop/lib/native/Linux-amd64-64
>
>
> TO:
>
> mapreduce.admin.user.env
>
> LD_LIBRARY_PATH=/usr/hdp/${hdp.version}/hadoop/lib/native:/usr/hdp/${hdp.version}/hadoop/lib/native/Linux-ppc64le-64
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19153) "Create Principals" fails intermittently
[
https://issues.apache.org/jira/browse/AMBARI-19153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15742276#comment-15742276
]
Hudson commented on AMBARI-19153:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #508 (See
[https://builds.apache.org/job/Ambari-branch-2.5/508/])
AMBARI-19153. "Create Principals" fails intermittently (dlysnichenko)
(dlysnichenko:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=51914fd93502c0377afb0d2c882a7582f9be513c])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/utils/ShellCommandUtil.java
> "Create Principals" fails intermittently
>
>
> Key: AMBARI-19153
> URL: https://issues.apache.org/jira/browse/AMBARI-19153
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Critical
> Fix For: 2.5.0
>
>
> {panel:title=stderr}
> 2016-12-05 21:08:15,369 - Failed to create principal,
> activity_explorer/host-3.dom...@example.com - Failed to execute the command:
> Broken pipe
> {panel}
> {panel:title=stdout}
> 2016-12-05 21:07:40,114 - Processing identities...\n2016-12-05 21:07:40,120 -
> Processing principal, activity_explorer/host-3.dom...@example.com
> {panel}
> {panel:title=from ambari-server.log}
> 05 Dec 2016 21:08:55,686 INFO [Server Action Executor Worker 166]
> KerberosServerAction:353 - Processing identities...
> 05 Dec 2016 21:08:55,689 INFO [Server Action Executor Worker 166]
> CreatePrincipalsServerAction:203 - Processing principal,
> HTTP/host-2.dom...@example.com
> 05 Dec 2016 21:09:05,698 WARN [Server Action Executor Worker 166]
> MITKerberosOperationHandler:481 - Retrying to execute kadmin after a wait of
> 10 seconds :
> Command: [/usr/bin/kadmin, -s, host-5.domain, -p, admin/ad...@example.com,
> -r, EXAMPLE.COM, -q, add_principal HTTP/host-2.dom...@example.com]
> 05 Dec 2016 21:09:05,709 ERROR [Server Action Executor Worker 166]
> KerberosOperationHandler:739 - Failed to execute the command: Broken pipe
> java.io.IOException: Broken pipe
> at java.io.FileOutputStream.writeBytes(Native Method)
> at java.io.FileOutputStream.write(FileOutputStream.java:345)
> at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
> at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
> at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:297)
> at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:141)
> at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229)
> at java.io.BufferedWriter.flush(BufferedWriter.java:254)
> at
> org.apache.ambari.server.utils.ShellCommandUtil.runCommand(ShellCommandUtil.java:451)
> at
> org.apache.ambari.server.serveraction.kerberos.KerberosOperationHandler.executeCommand(KerberosOperationHandler.java:736)
> at
> org.apache.ambari.server.serveraction.kerberos.MITKerberosOperationHandler.invokeKAdmin(MITKerberosOperationHandler.java:464)
> at
> org.apache.ambari.server.serveraction.kerberos.MITKerberosOperationHandler.createPrincipal(MITKerberosOperationHandler.java:195)
> at
> org.apache.ambari.server.serveraction.kerberos.CreatePrincipalsServerAction.createPrincipal(CreatePrincipalsServerAction.java:256)
> at
> org.apache.ambari.server.serveraction.kerberos.CreatePrincipalsServerAction.processIdentity(CreatePrincipalsServerAction.java:159)
> at
> org.apache.ambari.server.serveraction.kerberos.KerberosServerAction.processRecord(KerberosServerAction.java:532)
> at
> org.apache.ambari.server.serveraction.kerberos.KerberosServerAction.processIdentities(KerberosServerAction.java:414)
> at
> org.apache.ambari.server.serveraction.kerberos.CreatePrincipalsServerAction.execute(CreatePrincipalsServerAction.java:91)
> at
> org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.execute(ServerActionExecutor.java:555)
> at
> org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.run(ServerActionExecutor.java:492)
> at java.lang.Thread.run(Thread.java:745)
> 05 Dec 2016 21:09:15,710 WARN [Server Action Executor Worker 166]
> MITKerberosOperationHandler:481 - Retrying to execute kadmin after a wait of
> 10 seconds :
> Command: [/usr/bin/kadmin, -s, host-5.domain, -p, admin/ad...@example.com,
> -r, EXAMPLE.COM, -q, add_principal HTTP/host-2.dom...@example.com]
> 05 Dec 2016 21:09:15,722 ERROR [Server Action Executor Worker 166]
> KerberosOperationHandler:739 - Failed to execute the command: Broken pipe
> java.io.IOException: Broken pipe
> at java.io.FileOutputStream.writeBytes(Native Method)
> at java.io.FileOutputStream.write(FileOutputStream.java:345)
> at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
> at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
> at
[jira] [Commented] (AMBARI-19153) "Create Principals" fails intermittently
[
https://issues.apache.org/jira/browse/AMBARI-19153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15742254#comment-15742254
]
Hudson commented on AMBARI-19153:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6208 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6208/])
AMBARI-19153. "Create Principals" fails intermittently (dlysnichenko)
(dlysnichenko:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=9ccd9979c72812d58e220158c2869a053883b392])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/utils/ShellCommandUtil.java
> "Create Principals" fails intermittently
>
>
> Key: AMBARI-19153
> URL: https://issues.apache.org/jira/browse/AMBARI-19153
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Critical
> Fix For: 2.5.0
>
>
> {panel:title=stderr}
> 2016-12-05 21:08:15,369 - Failed to create principal,
> activity_explorer/host-3.dom...@example.com - Failed to execute the command:
> Broken pipe
> {panel}
> {panel:title=stdout}
> 2016-12-05 21:07:40,114 - Processing identities...\n2016-12-05 21:07:40,120 -
> Processing principal, activity_explorer/host-3.dom...@example.com
> {panel}
> {panel:title=from ambari-server.log}
> 05 Dec 2016 21:08:55,686 INFO [Server Action Executor Worker 166]
> KerberosServerAction:353 - Processing identities...
> 05 Dec 2016 21:08:55,689 INFO [Server Action Executor Worker 166]
> CreatePrincipalsServerAction:203 - Processing principal,
> HTTP/host-2.dom...@example.com
> 05 Dec 2016 21:09:05,698 WARN [Server Action Executor Worker 166]
> MITKerberosOperationHandler:481 - Retrying to execute kadmin after a wait of
> 10 seconds :
> Command: [/usr/bin/kadmin, -s, host-5.domain, -p, admin/ad...@example.com,
> -r, EXAMPLE.COM, -q, add_principal HTTP/host-2.dom...@example.com]
> 05 Dec 2016 21:09:05,709 ERROR [Server Action Executor Worker 166]
> KerberosOperationHandler:739 - Failed to execute the command: Broken pipe
> java.io.IOException: Broken pipe
> at java.io.FileOutputStream.writeBytes(Native Method)
> at java.io.FileOutputStream.write(FileOutputStream.java:345)
> at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
> at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
> at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:297)
> at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:141)
> at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229)
> at java.io.BufferedWriter.flush(BufferedWriter.java:254)
> at
> org.apache.ambari.server.utils.ShellCommandUtil.runCommand(ShellCommandUtil.java:451)
> at
> org.apache.ambari.server.serveraction.kerberos.KerberosOperationHandler.executeCommand(KerberosOperationHandler.java:736)
> at
> org.apache.ambari.server.serveraction.kerberos.MITKerberosOperationHandler.invokeKAdmin(MITKerberosOperationHandler.java:464)
> at
> org.apache.ambari.server.serveraction.kerberos.MITKerberosOperationHandler.createPrincipal(MITKerberosOperationHandler.java:195)
> at
> org.apache.ambari.server.serveraction.kerberos.CreatePrincipalsServerAction.createPrincipal(CreatePrincipalsServerAction.java:256)
> at
> org.apache.ambari.server.serveraction.kerberos.CreatePrincipalsServerAction.processIdentity(CreatePrincipalsServerAction.java:159)
> at
> org.apache.ambari.server.serveraction.kerberos.KerberosServerAction.processRecord(KerberosServerAction.java:532)
> at
> org.apache.ambari.server.serveraction.kerberos.KerberosServerAction.processIdentities(KerberosServerAction.java:414)
> at
> org.apache.ambari.server.serveraction.kerberos.CreatePrincipalsServerAction.execute(CreatePrincipalsServerAction.java:91)
> at
> org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.execute(ServerActionExecutor.java:555)
> at
> org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.run(ServerActionExecutor.java:492)
> at java.lang.Thread.run(Thread.java:745)
> 05 Dec 2016 21:09:15,710 WARN [Server Action Executor Worker 166]
> MITKerberosOperationHandler:481 - Retrying to execute kadmin after a wait of
> 10 seconds :
> Command: [/usr/bin/kadmin, -s, host-5.domain, -p, admin/ad...@example.com,
> -r, EXAMPLE.COM, -q, add_principal HTTP/host-2.dom...@example.com]
> 05 Dec 2016 21:09:15,722 ERROR [Server Action Executor Worker 166]
> KerberosOperationHandler:739 - Failed to execute the command: Broken pipe
> java.io.IOException: Broken pipe
> at java.io.FileOutputStream.writeBytes(Native Method)
> at java.io.FileOutputStream.write(FileOutputStream.java:345)
> at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
> at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
> at
[jira] [Updated] (AMBARI-19133) hadoop.proxyuser.HTTP.hosts should not be updated when Hive is installed unless WebHcat is installed
[
https://issues.apache.org/jira/browse/AMBARI-19133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-19133:
--
Attachment: AMBARI-19133_trunk_02.patch
AMBARI-19133_branch-2.5_02.patch
> hadoop.proxyuser.HTTP.hosts should not be updated when Hive is installed
> unless WebHcat is installed
>
>
> Key: AMBARI-19133
> URL: https://issues.apache.org/jira/browse/AMBARI-19133
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: kerberos, kerberos_descriptor
> Fix For: 2.5.0
>
> Attachments: AMBARI-19133_branch-2.5_01.patch,
> AMBARI-19133_branch-2.5_02.patch, AMBARI-19133_trunk_01.patch,
> AMBARI-19133_trunk_02.patch
>
>
> {{hadoop.proxyuser.HTTP.hosts}} should not be updated when Hive is installed
> unless WebHcat is installed.
> This is happening because the following block in the Kerberos descriptor is
> at the HIVE service level rather than the WEBHCAT_SERVER component level.
> {code}
> {
> "core-site": {
> "hadoop.proxyuser.HTTP.hosts":
> "${clusterHostInfo/webhcat_server_host}"
> }
> },
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (AMBARI-19153) "Create Principals" fails intermittently
[
https://issues.apache.org/jira/browse/AMBARI-19153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko resolved AMBARI-19153.
-
Resolution: Fixed
Committed
To https://git-wip-us.apache.org/repos/asf/ambari.git
30bf4af81a..51914fd935 branch-2.5 -> branch-2.5
c6f90cf6a3..9ccd9979c7 trunk -> trunk
> "Create Principals" fails intermittently
>
>
> Key: AMBARI-19153
> URL: https://issues.apache.org/jira/browse/AMBARI-19153
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Critical
> Fix For: 2.5.0
>
>
> {panel:title=stderr}
> 2016-12-05 21:08:15,369 - Failed to create principal,
> activity_explorer/host-3.dom...@example.com - Failed to execute the command:
> Broken pipe
> {panel}
> {panel:title=stdout}
> 2016-12-05 21:07:40,114 - Processing identities...\n2016-12-05 21:07:40,120 -
> Processing principal, activity_explorer/host-3.dom...@example.com
> {panel}
> {panel:title=from ambari-server.log}
> 05 Dec 2016 21:08:55,686 INFO [Server Action Executor Worker 166]
> KerberosServerAction:353 - Processing identities...
> 05 Dec 2016 21:08:55,689 INFO [Server Action Executor Worker 166]
> CreatePrincipalsServerAction:203 - Processing principal,
> HTTP/host-2.dom...@example.com
> 05 Dec 2016 21:09:05,698 WARN [Server Action Executor Worker 166]
> MITKerberosOperationHandler:481 - Retrying to execute kadmin after a wait of
> 10 seconds :
> Command: [/usr/bin/kadmin, -s, host-5.domain, -p, admin/ad...@example.com,
> -r, EXAMPLE.COM, -q, add_principal HTTP/host-2.dom...@example.com]
> 05 Dec 2016 21:09:05,709 ERROR [Server Action Executor Worker 166]
> KerberosOperationHandler:739 - Failed to execute the command: Broken pipe
> java.io.IOException: Broken pipe
> at java.io.FileOutputStream.writeBytes(Native Method)
> at java.io.FileOutputStream.write(FileOutputStream.java:345)
> at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
> at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
> at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:297)
> at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:141)
> at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229)
> at java.io.BufferedWriter.flush(BufferedWriter.java:254)
> at
> org.apache.ambari.server.utils.ShellCommandUtil.runCommand(ShellCommandUtil.java:451)
> at
> org.apache.ambari.server.serveraction.kerberos.KerberosOperationHandler.executeCommand(KerberosOperationHandler.java:736)
> at
> org.apache.ambari.server.serveraction.kerberos.MITKerberosOperationHandler.invokeKAdmin(MITKerberosOperationHandler.java:464)
> at
> org.apache.ambari.server.serveraction.kerberos.MITKerberosOperationHandler.createPrincipal(MITKerberosOperationHandler.java:195)
> at
> org.apache.ambari.server.serveraction.kerberos.CreatePrincipalsServerAction.createPrincipal(CreatePrincipalsServerAction.java:256)
> at
> org.apache.ambari.server.serveraction.kerberos.CreatePrincipalsServerAction.processIdentity(CreatePrincipalsServerAction.java:159)
> at
> org.apache.ambari.server.serveraction.kerberos.KerberosServerAction.processRecord(KerberosServerAction.java:532)
> at
> org.apache.ambari.server.serveraction.kerberos.KerberosServerAction.processIdentities(KerberosServerAction.java:414)
> at
> org.apache.ambari.server.serveraction.kerberos.CreatePrincipalsServerAction.execute(CreatePrincipalsServerAction.java:91)
> at
> org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.execute(ServerActionExecutor.java:555)
> at
> org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.run(ServerActionExecutor.java:492)
> at java.lang.Thread.run(Thread.java:745)
> 05 Dec 2016 21:09:15,710 WARN [Server Action Executor Worker 166]
> MITKerberosOperationHandler:481 - Retrying to execute kadmin after a wait of
> 10 seconds :
> Command: [/usr/bin/kadmin, -s, host-5.domain, -p, admin/ad...@example.com,
> -r, EXAMPLE.COM, -q, add_principal HTTP/host-2.dom...@example.com]
> 05 Dec 2016 21:09:15,722 ERROR [Server Action Executor Worker 166]
> KerberosOperationHandler:739 - Failed to execute the command: Broken pipe
> java.io.IOException: Broken pipe
> at java.io.FileOutputStream.writeBytes(Native Method)
> at java.io.FileOutputStream.write(FileOutputStream.java:345)
> at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
> at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
> at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:297)
> at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:141)
> at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229)
> at java.io.BufferedWriter.flush(BufferedWriter.java:254)
> at
[jira] [Commented] (AMBARI-19150) Stack Advisor Throws Exception On ZooKeeper Configs
[
https://issues.apache.org/jira/browse/AMBARI-19150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15742184#comment-15742184
]
Hudson commented on AMBARI-19150:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #507 (See
[https://builds.apache.org/job/Ambari-branch-2.5/507/])
AMBARI-19150. Stack Advisor Throws Exception On ZooKeeper Configs
(dlysnichenko:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=30bf4af81a3fa5fd25cae0c9bed06b7d092b5230])
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py
> Stack Advisor Throws Exception On ZooKeeper Configs
> ---
>
> Key: AMBARI-19150
> URL: https://issues.apache.org/jira/browse/AMBARI-19150
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Dmytro Grinenko
>Assignee: Dmitry Lysnichenko
>Priority: Critical
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19150.patch
>
>
> When viewing the ZooKeeper configurations, the following Python error is
> thrown:
> {code}
> Caused by:
> org.apache.ambari.server.api.services.stackadvisor.StackAdvisorException:
> Stack Advisor reported an error: TypeError: 'NoneType' object has no
> attribute '__getitem__'
> {code}
> {code:title=stackadvisor.out}
> StackAdvisor implementation for stack HDP, version 2.0.6 was loaded
> StackAdvisor implementation for stack HDP, version 2.1 was loaded
> StackAdvisor implementation for stack HDP, version 2.2 was loaded
> StackAdvisor implementation for stack HDP, version 2.3 was loaded
> StackAdvisor implementation for stack HDP, version 2.4 was loaded
> Returning HDP24StackAdvisor implementation
> Error occured in stack advisor.
> Error details: 'NoneType' object has no attribute '__getitem__'
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19150) Stack Advisor Throws Exception On ZooKeeper Configs
[
https://issues.apache.org/jira/browse/AMBARI-19150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15742179#comment-15742179
]
Hudson commented on AMBARI-19150:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6207 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6207/])
AMBARI-19150. Stack Advisor Throws Exception On ZooKeeper Configs
(dlysnichenko:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=c6f90cf6a37148b7de5b1d1d13aa62c807eaab79])
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py
> Stack Advisor Throws Exception On ZooKeeper Configs
> ---
>
> Key: AMBARI-19150
> URL: https://issues.apache.org/jira/browse/AMBARI-19150
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Dmytro Grinenko
>Assignee: Dmitry Lysnichenko
>Priority: Critical
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19150.patch
>
>
> When viewing the ZooKeeper configurations, the following Python error is
> thrown:
> {code}
> Caused by:
> org.apache.ambari.server.api.services.stackadvisor.StackAdvisorException:
> Stack Advisor reported an error: TypeError: 'NoneType' object has no
> attribute '__getitem__'
> {code}
> {code:title=stackadvisor.out}
> StackAdvisor implementation for stack HDP, version 2.0.6 was loaded
> StackAdvisor implementation for stack HDP, version 2.1 was loaded
> StackAdvisor implementation for stack HDP, version 2.2 was loaded
> StackAdvisor implementation for stack HDP, version 2.3 was loaded
> StackAdvisor implementation for stack HDP, version 2.4 was loaded
> Returning HDP24StackAdvisor implementation
> Error occured in stack advisor.
> Error details: 'NoneType' object has no attribute '__getitem__'
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19173) zookeeper client install failed on attempt to reinstall
Shreya Bhat created AMBARI-19173:
Summary: zookeeper client install failed on attempt to reinstall
Key: AMBARI-19173
URL: https://issues.apache.org/jira/browse/AMBARI-19173
Project: Ambari
Issue Type: Bug
Reporter: Shreya Bhat
1. Install cluster
2. Simulate failure in client installs
3. Reinstall clients.
Zookeeper client install fails with :
{code}
Caught an exception while executing custom service command: : 'Script
/var/lib/ambari-agent/cache/common-services/ZOOKEEPER/3.4.5/package/scripts/zookeeper_client.py
does not exist'; 'Script
/var/lib/ambari-agent/cache/common-services/ZOOKEEPER/3.4.5/package/scripts/zookeeper_client.py
does not exist'
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (AMBARI-19150) Stack Advisor Throws Exception On ZooKeeper Configs
[
https://issues.apache.org/jira/browse/AMBARI-19150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko reassigned AMBARI-19150:
---
Assignee: Dmitry Lysnichenko
> Stack Advisor Throws Exception On ZooKeeper Configs
> ---
>
> Key: AMBARI-19150
> URL: https://issues.apache.org/jira/browse/AMBARI-19150
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Dmytro Grinenko
>Assignee: Dmitry Lysnichenko
>Priority: Critical
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19150.patch
>
>
> When viewing the ZooKeeper configurations, the following Python error is
> thrown:
> {code}
> Caused by:
> org.apache.ambari.server.api.services.stackadvisor.StackAdvisorException:
> Stack Advisor reported an error: TypeError: 'NoneType' object has no
> attribute '__getitem__'
> {code}
> {code:title=stackadvisor.out}
> StackAdvisor implementation for stack HDP, version 2.0.6 was loaded
> StackAdvisor implementation for stack HDP, version 2.1 was loaded
> StackAdvisor implementation for stack HDP, version 2.2 was loaded
> StackAdvisor implementation for stack HDP, version 2.3 was loaded
> StackAdvisor implementation for stack HDP, version 2.4 was loaded
> Returning HDP24StackAdvisor implementation
> Error occured in stack advisor.
> Error details: 'NoneType' object has no attribute '__getitem__'
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19150) Stack Advisor Throws Exception On ZooKeeper Configs
[
https://issues.apache.org/jira/browse/AMBARI-19150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-19150:
Resolution: Fixed
Status: Resolved (was: Patch Available)
To https://git-wip-us.apache.org/repos/asf/ambari.git
71767feed7..30bf4af81a branch-2.5 -> branch-2.5
63dc498c1d..c6f90cf6a3 trunk -> trunk
> Stack Advisor Throws Exception On ZooKeeper Configs
> ---
>
> Key: AMBARI-19150
> URL: https://issues.apache.org/jira/browse/AMBARI-19150
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Dmytro Grinenko
>Assignee: Dmitry Lysnichenko
>Priority: Critical
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19150.patch
>
>
> When viewing the ZooKeeper configurations, the following Python error is
> thrown:
> {code}
> Caused by:
> org.apache.ambari.server.api.services.stackadvisor.StackAdvisorException:
> Stack Advisor reported an error: TypeError: 'NoneType' object has no
> attribute '__getitem__'
> {code}
> {code:title=stackadvisor.out}
> StackAdvisor implementation for stack HDP, version 2.0.6 was loaded
> StackAdvisor implementation for stack HDP, version 2.1 was loaded
> StackAdvisor implementation for stack HDP, version 2.2 was loaded
> StackAdvisor implementation for stack HDP, version 2.3 was loaded
> StackAdvisor implementation for stack HDP, version 2.4 was loaded
> Returning HDP24StackAdvisor implementation
> Error occured in stack advisor.
> Error details: 'NoneType' object has no attribute '__getitem__'
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19149) Clean up Ambari Server source code warnings
[
https://issues.apache.org/jira/browse/AMBARI-19149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15741910#comment-15741910
]
Nate Cole commented on AMBARI-19149:
I'm ok with it going with the test phase.
> Clean up Ambari Server source code warnings
> ---
>
> Key: AMBARI-19149
> URL: https://issues.apache.org/jira/browse/AMBARI-19149
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0
>
> Attachments: AMBARI-19149-1.patch, IDEA_Ambari_v1.xml
>
>
> Eclipse's default warnings generated for {{ambari-server}} number roughly
> over 3300. Out of these, at least half of them are:
> * Unused imports
> * Type safety due to forgotten {{<>}}
> * Missing Serialization IDs from anonymous {{HashMap}} implementations
> * Unused variables
> * {{Capture}} in tests
> * {{switch}} fall-through and missing {{case statements}}: *only makes
> changes which won't affect existing functionality*
> This makes spotting actual problems, like missing {{case}} statements a
> nightmare. We need to go through and clean out as many of these warnings as
> possible.
> Note: With respect to the import cleanup, the IDE of choice should have the
> following import order setup. They should always be expanded and never use
> {{*}}.
> # {{java}}
> # {{javax}}
> # {{org}}
> # {{com}}
> # other
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19104) Ambari Server - LogSearch integration code SSL support
[ https://issues.apache.org/jira/browse/AMBARI-19104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15741819#comment-15741819 ] Hudson commented on AMBARI-19104: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6206 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6206/]) AMBARI-19104. Ambari Server - LogSearch integration code SSL support (oleewere: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=63dc498c1d660277abd719ddfa9a256e36869718]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/logging/LoggingRequestHelperFactoryImpl.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/logging/LoggingRequestHelperImpl.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/logging/LoggingRequestHelperImplTest.java > Ambari Server - LogSearch integration code SSL support > -- > > Key: AMBARI-19104 > URL: https://issues.apache.org/jira/browse/AMBARI-19104 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, ambari-server >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 2.5.0 > > Attachments: AMBARI-19104.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19104) Ambari Server - LogSearch integration code SSL support
[ https://issues.apache.org/jira/browse/AMBARI-19104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15741812#comment-15741812 ] Hudson commented on AMBARI-19104: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #506 (See [https://builds.apache.org/job/Ambari-branch-2.5/506/]) AMBARI-19104. Ambari Server - LogSearch integration code SSL support (oleewere: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=71767feed730e8714b32f563d62d7c392173791d]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/logging/LoggingRequestHelperImplTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/logging/LoggingRequestHelperFactoryImpl.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/logging/LoggingRequestHelperImpl.java > Ambari Server - LogSearch integration code SSL support > -- > > Key: AMBARI-19104 > URL: https://issues.apache.org/jira/browse/AMBARI-19104 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, ambari-server >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 2.5.0 > > Attachments: AMBARI-19104.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19165) Ambari-web unit tests cannot be run in Mac OS Sierra
[
https://issues.apache.org/jira/browse/AMBARI-19165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15741799#comment-15741799
]
Hadoop QA commented on AMBARI-19165:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12842760/AMBARI-19165.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9624//console
This message is automatically generated.
> Ambari-web unit tests cannot be run in Mac OS Sierra
>
>
> Key: AMBARI-19165
> URL: https://issues.apache.org/jira/browse/AMBARI-19165
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Jaimin Jetly
>Assignee: Jaimin Jetly
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19165.patch
>
>
> Running "npm test" just hangs in Mac OS Sierra.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19160) Add ReviewBoard config file
[
https://issues.apache.org/jira/browse/AMBARI-19160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15741797#comment-15741797
]
Hadoop QA commented on AMBARI-19160:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12842790/AMBARI-19160.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9623//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9623//console
This message is automatically generated.
> Add ReviewBoard config file
> ---
>
> Key: AMBARI-19160
> URL: https://issues.apache.org/jira/browse/AMBARI-19160
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Trivial
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-19160.patch
>
>
> ReviewBoard has [command-line
> tools|https://www.reviewboard.org/docs/rbtools/] for working with review
> requests. The goal of this task is to add a small [config
> file|https://www.reviewboard.org/docs/rbtools/0.7/rbt/configuration/repositories/#reviewboardrc]
> to the Ambari project, so that {{rbt}} can talk to the right RB server
> out-of-the box.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19104) Ambari Server - LogSearch integration code SSL support
[
https://issues.apache.org/jira/browse/AMBARI-19104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-19104:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
committed to trunk:
{code:java}
commit 63dc498c1d660277abd719ddfa9a256e36869718
Author: oleewere
Date: Fri Dec 9 13:05:20 2016 +0100
AMBARI-19104. Ambari Server - LogSearch integration code SSL support
(oleewere)
Change-Id: Iba17bccd34e93fac52ab18726a66959dd79766b2
{code}
committed to branch-2.5:
{code:java}
commit 71767feed730e8714b32f563d62d7c392173791d
Author: oleewere
Date: Fri Dec 9 13:05:20 2016 +0100
AMBARI-19104. Ambari Server - LogSearch integration code SSL support
(oleewere)
Change-Id: Iba17bccd34e93fac52ab18726a66959dd79766b2
{code}
> Ambari Server - LogSearch integration code SSL support
> --
>
> Key: AMBARI-19104
> URL: https://issues.apache.org/jira/browse/AMBARI-19104
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch, ambari-server
>Affects Versions: 2.4.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 2.5.0
>
> Attachments: AMBARI-19104.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19172) 'Backup Oozie DB' message is masked when FixOozieAdminUsers code is invoked in EU wizard
[ https://issues.apache.org/jira/browse/AMBARI-19172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Sharma updated AMBARI-19172: -- Attachment: Working.png Error.png > 'Backup Oozie DB' message is masked when FixOozieAdminUsers code is invoked > in EU wizard > > > Key: AMBARI-19172 > URL: https://issues.apache.org/jira/browse/AMBARI-19172 > Project: Ambari > Issue Type: Bug > Components: ambari-upgrade >Affects Versions: 2.5.0 >Reporter: Vivek Sharma >Priority: Critical > Labels: express_upgrade > Fix For: 2.5.0 > > Attachments: Error.png, Working.png > > > EU path from HDP-2.3.6.0 to 2.6.0.0 with Ambari-2.5.0.0 > In upgrade pack: > There are two tasks: > a. Fix oozie admin users > b. Manual prompt to 'Backup Oozie Database' > When a.) gets invoked then the manual prompt message to backup Oozie DB gets > suppressed. As a result user is not informed to backup the Oozie DB before > the actual upgrade > Please see attached screenshots -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19172) 'Backup Oozie DB' message is masked when FixOozieAdminUsers code is invoked in EU wizard
Vivek Sharma created AMBARI-19172: - Summary: 'Backup Oozie DB' message is masked when FixOozieAdminUsers code is invoked in EU wizard Key: AMBARI-19172 URL: https://issues.apache.org/jira/browse/AMBARI-19172 Project: Ambari Issue Type: Bug Components: ambari-upgrade Affects Versions: 2.5.0 Reporter: Vivek Sharma Priority: Critical Fix For: 2.5.0 EU path from HDP-2.3.6.0 to 2.6.0.0 with Ambari-2.5.0.0 In upgrade pack: There are two tasks: a. Fix oozie admin users b. Manual prompt to 'Backup Oozie Database' When a.) gets invoked then the manual prompt message to backup Oozie DB gets suppressed. As a result user is not informed to backup the Oozie DB before the actual upgrade Please see attached screenshots -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19171) Configuring YARN with custom queues leads to misleading errors in Stack Advisor
[ https://issues.apache.org/jira/browse/AMBARI-19171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Sharma updated AMBARI-19171: -- Attachment: yarn2.png yarn1.png > Configuring YARN with custom queues leads to misleading errors in Stack > Advisor > --- > > Key: AMBARI-19171 > URL: https://issues.apache.org/jira/browse/AMBARI-19171 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Sharma >Priority: Critical > Labels: ui > Fix For: 2.5.0 > > Attachments: yarn1.png, yarn2.png > > > Configure custom (non-default) YARN queues as per this link > (http://hortonworks.com/hadoop-tutorial/configuring-yarn-capacity-scheduler-ambari/) > Result: Stack Advisor gives errors related to deletion of 'default' queue > (check screenshots - yarn1, yarn2) for various service configs like YARN, > Hive, Tez, MR, Spark -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19171) Configuring YARN with custom queues leads to misleading errors in Stack Advisor
Vivek Sharma created AMBARI-19171: - Summary: Configuring YARN with custom queues leads to misleading errors in Stack Advisor Key: AMBARI-19171 URL: https://issues.apache.org/jira/browse/AMBARI-19171 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Vivek Sharma Priority: Critical Fix For: 2.5.0 Configure custom (non-default) YARN queues as per this link (http://hortonworks.com/hadoop-tutorial/configuring-yarn-capacity-scheduler-ambari/) Result: Stack Advisor gives errors related to deletion of 'default' queue (check screenshots - yarn1, yarn2) for various service configs like YARN, Hive, Tez, MR, Spark -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19170) NPE during Ambari server schema upgrade
Vivek Sharma created AMBARI-19170:
-
Summary: NPE during Ambari server schema upgrade
Key: AMBARI-19170
URL: https://issues.apache.org/jira/browse/AMBARI-19170
Project: Ambari
Issue Type: Bug
Components: ambari-upgrade
Affects Versions: 2.5.0
Reporter: Vivek Sharma
Priority: Critical
Fix For: 2.5.0
Ambari server upgrade path: 2.2.2.0 to 2.5.0.0-453
Error seen while running 'ambari-server upgrade' command"
{code}
Using python /usr/bin/python
Upgrading ambari-server
INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
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
WARNING: Original file krb5JAASLogin.conf kept
INFO: File krb5JAASLogin.conf updated.
INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
INFO: No mpack replay logs found. Skipping replaying mpack commands
INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
INFO: Fixing database objects owner
INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
INFO: using SERVICE_NAME instead of SID for Oracle
INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
Ambari Server configured for Oracle. Confirm you have made a backup of the
Ambari Server database [y/n] (y)? INFO: Loading properties from
/etc/ambari-server/conf/ambari.properties
INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
INFO: using SERVICE_NAME instead of SID for Oracle
INFO: Upgrading database schema
INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
INFO: AMBARI_SERVER_LIB is not set, using default /usr/lib/ambari-server
INFO: using SERVICE_NAME instead of SID for Oracle
INFO: using SERVICE_NAME instead of SID for Oracle
INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
INFO: about to run command: /usr/jdk64/jdk1.7.0_67/bin/java -cp
'/etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/ojdbc6.jar'
org.apache.ambari.server.upgrade.SchemaUpgradeHelper >
/var/log/ambari-server/ambari-server.out 2>&1
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
at
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:209)
at
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:424)
Caused by: java.lang.NullPointerException
at
com.google.inject.persist.jpa.JpaPersistService.begin(JpaPersistService.java:70)
at
com.google.inject.persist.jpa.AmbariJpaPersistService.begin(AmbariJpaPersistService.java:29)
at
org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.invoke(AmbariJpaLocalTxnInterceptor.java:106)
at
org.apache.ambari.server.upgrade.UpgradeCatalog240.executeDDLUpdates(UpgradeCatalog240.java:294)
at
org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeSchema(AbstractUpgradeCatalog.java:938)
at
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:206)
... 1 more
ERROR: Ambari server upgrade failed. Please look at
/var/log/ambari-server/ambari-server.log, for more details.
ERROR: Exiting with exit code 11.
REASON: Schema upgrade failed.
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19169) Add Service Page in Atlas doesn't show config on change
Aleksandr Kovalenko created AMBARI-19169: Summary: Add Service Page in Atlas doesn't show config on change Key: AMBARI-19169 URL: https://issues.apache.org/jira/browse/AMBARI-19169 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Priority: Critical Fix For: 2.5.0 Steps to reproduce: # Add Atlas service # Under Authentication Tab > Enable LDAP Authentication # This will open LDAP/AD section below # Now in LDAP/AD section > select LDAP Authentication Type as AD, here the properties related to AD are not shown. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19160) Add ReviewBoard config file
[
https://issues.apache.org/jira/browse/AMBARI-19160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-19160:
---
Attachment: (was: AMBARI-19160_trunk.patch)
> Add ReviewBoard config file
> ---
>
> Key: AMBARI-19160
> URL: https://issues.apache.org/jira/browse/AMBARI-19160
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Trivial
> Fix For: 3.0.0, 2.5.0
>
>
> ReviewBoard has [command-line
> tools|https://www.reviewboard.org/docs/rbtools/] for working with review
> requests. The goal of this task is to add a small [config
> file|https://www.reviewboard.org/docs/rbtools/0.7/rbt/configuration/repositories/#reviewboardrc]
> to the Ambari project, so that {{rbt}} can talk to the right RB server
> out-of-the box.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19160) Add ReviewBoard config file
[
https://issues.apache.org/jira/browse/AMBARI-19160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-19160:
---
Attachment: (was: AMBARI-19160_branch-2.5.patch)
> Add ReviewBoard config file
> ---
>
> Key: AMBARI-19160
> URL: https://issues.apache.org/jira/browse/AMBARI-19160
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Trivial
> Fix For: 3.0.0, 2.5.0
>
>
> ReviewBoard has [command-line
> tools|https://www.reviewboard.org/docs/rbtools/] for working with review
> requests. The goal of this task is to add a small [config
> file|https://www.reviewboard.org/docs/rbtools/0.7/rbt/configuration/repositories/#reviewboardrc]
> to the Ambari project, so that {{rbt}} can talk to the right RB server
> out-of-the box.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
