[jira] [Updated] (AMBARI-16920) Follow up issue for Spark2 stack definition
[ https://issues.apache.org/jira/browse/AMBARI-16920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated AMBARI-16920: Summary: Follow up issue for Spark2 stack definition (was: Spark2 thrift server can not started due to miss of spark-thrift-fairscheduler.xml) > Follow up issue for Spark2 stack definition > --- > > Key: AMBARI-16920 > URL: https://issues.apache.org/jira/browse/AMBARI-16920 > Project: Ambari > Issue Type: Sub-task > Components: stacks >Affects Versions: 2.4.0 >Reporter: Jeff Zhang >Assignee: Jeff Zhang > Fix For: 2.4.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16920) Follow up issue for Spark2 stack definition
[ https://issues.apache.org/jira/browse/AMBARI-16920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated AMBARI-16920: Description: 1. Spark2 thrift server can not started due to miss of spark-thrift-fairscheduler.xml 2. Miss of add spark2 cache file in copy_barball.py 3. Miss the role_commnad_order of spark2 > Follow up issue for Spark2 stack definition > --- > > Key: AMBARI-16920 > URL: https://issues.apache.org/jira/browse/AMBARI-16920 > Project: Ambari > Issue Type: Sub-task > Components: stacks >Affects Versions: 2.4.0 >Reporter: Jeff Zhang >Assignee: Jeff Zhang > Fix For: 2.4.0 > > > 1. Spark2 thrift server can not started due to miss of > spark-thrift-fairscheduler.xml > 2. Miss of add spark2 cache file in copy_barball.py > 3. Miss the role_commnad_order of spark2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16998) Fix intermittent unit test failure in TestMpacks
[
https://issues.apache.org/jira/browse/AMBARI-16998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15325721#comment-15325721
]
Hudson commented on AMBARI-16998:
-
FAILURE: Integrated in Ambari-trunk-Commit #5059 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5059/])
AMBARI-16998: Fix intermittent unit test failure in TestMpacks (jluniya)
(jluniya:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=5adc30d30337cd9be993ccb38fe7bc9a2c63350e])
* ambari-server/src/test/python/TestMpacks.py
> Fix intermittent unit test failure in TestMpacks
>
>
> Key: AMBARI-16998
> URL: https://issues.apache.org/jira/browse/AMBARI-16998
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-16998.patch
>
>
> {code}
> Running tests for ambari-server
> Traceback (most recent call last):
> File "unitTests.py", line 298, in
> sys.exit(main())
> File "unitTests.py", line 250, in main
> File ambari.properties not found in search path $AMBARI_CONF_DIR:
> /etc/ambari-server/conf
> suites = [unittest.defaultTestLoader.loadTestsFromName(name) for name in
> modules]
> File "/usr/lib/python2.7/unittest/loader.py", line 91, in loadTestsFromName
> module = __import__('.'.join(parts_copy))
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/test/python/TestMpacks.py",
> line 21, in
> from ambari_server.setupMpacks import install_mpack, upgrade_mpack,
> replay_mpack_logs, purge_stacks_and_mpacks, \
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/setupMpacks.py",
> line 31, in
> from ambari_server.serverConfiguration import get_ambari_properties,
> get_ambari_version, get_stack_location, \
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverConfiguration.py",
> line 537, in
> configDefaults = ServerConfigDefaults()
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverConfiguration.py",
> line 456, in __init__
> super(ServerConfigDefaultsLinux, self).__init__()
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverConfiguration.py",
> line 327, in __init__
> properties = get_ambari_properties()
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverConfiguration.py",
> line 225, in get_ambari_properties
> conf_file = find_properties_file()
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverConfiguration.py",
> line 218, in find_properties_file
> raise FatalException(1, err)
> ambari_commons.exceptions.FatalException: 'Fatal exception: File
> ambari.properties not found in search path $AMBARI_CONF_DIR:
> /etc/ambari-server/conf, exit code 1'
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17175) On Enabling HS Interactive default queue shown for llap is 'default' queue
[ https://issues.apache.org/jira/browse/AMBARI-17175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15325676#comment-15325676 ] Hudson commented on AMBARI-17175: - FAILURE: Integrated in Ambari-trunk-Commit #5058 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5058/]) AMBARI-17175. On Enabling HS Interactive default queue shown for llap is (jaimin: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=82abc9ea7886d746e9fea4e5710064e22a1c33cd]) * ambari-web/app/views/common/configs/widgets/combo_config_widget_view.js > On Enabling HS Interactive default queue shown for llap is 'default' queue > -- > > Key: AMBARI-17175 > URL: https://issues.apache.org/jira/browse/AMBARI-17175 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: ambari-2.4.0 >Reporter: Shraddha Sumit >Assignee: Jaimin D Jetly >Priority: Critical > Fix For: ambari-2.4.0 > > Attachments: AMBARI-17175.patch > > > 1. Deploy ambari secure cluster > 2. Enable HSI > Expected: llap queue is created by ambari and is set as default for llap > Actual: ldap queue is not created and default queue is set for ldap -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16998) Fix intermittent unit test failure in TestMpacks
[
https://issues.apache.org/jira/browse/AMBARI-16998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-16998:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Fix intermittent unit test failure in TestMpacks
>
>
> Key: AMBARI-16998
> URL: https://issues.apache.org/jira/browse/AMBARI-16998
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-16998.patch
>
>
> {code}
> Running tests for ambari-server
> Traceback (most recent call last):
> File "unitTests.py", line 298, in
> sys.exit(main())
> File "unitTests.py", line 250, in main
> File ambari.properties not found in search path $AMBARI_CONF_DIR:
> /etc/ambari-server/conf
> suites = [unittest.defaultTestLoader.loadTestsFromName(name) for name in
> modules]
> File "/usr/lib/python2.7/unittest/loader.py", line 91, in loadTestsFromName
> module = __import__('.'.join(parts_copy))
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/test/python/TestMpacks.py",
> line 21, in
> from ambari_server.setupMpacks import install_mpack, upgrade_mpack,
> replay_mpack_logs, purge_stacks_and_mpacks, \
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/setupMpacks.py",
> line 31, in
> from ambari_server.serverConfiguration import get_ambari_properties,
> get_ambari_version, get_stack_location, \
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverConfiguration.py",
> line 537, in
> configDefaults = ServerConfigDefaults()
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverConfiguration.py",
> line 456, in __init__
> super(ServerConfigDefaultsLinux, self).__init__()
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverConfiguration.py",
> line 327, in __init__
> properties = get_ambari_properties()
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverConfiguration.py",
> line 225, in get_ambari_properties
> conf_file = find_properties_file()
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverConfiguration.py",
> line 218, in find_properties_file
> raise FatalException(1, err)
> ambari_commons.exceptions.FatalException: 'Fatal exception: File
> ambari.properties not found in search path $AMBARI_CONF_DIR:
> /etc/ambari-server/conf, exit code 1'
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17171) Falcon to create data-mirroring directory in HDFS if extensions is supported
[ https://issues.apache.org/jira/browse/AMBARI-17171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15325622#comment-15325622 ] Hudson commented on AMBARI-17171: - FAILURE: Integrated in Ambari-trunk-Commit #5057 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5057/]) AMBARI-17171. Falcon to create data-mirroring directory in HDFS if (afernandez: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=38bfa42e027a47a3ecbdb57d0453f8140ef7f92f]) * ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/package/scripts/falcon.py * ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/package/scripts/params_linux.py * ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/package/scripts/falcon_server.py > Falcon to create data-mirroring directory in HDFS if extensions is supported > > > Key: AMBARI-17171 > URL: https://issues.apache.org/jira/browse/AMBARI-17171 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: Murali Ramasami >Assignee: Alejandro Fernandez > Fix For: trunk, 2.4.0 > > Attachments: AMBARI-17171.branch-2.4.patch, AMBARI-17171.trunk.patch > > > If Falcon extensions is supported, Ambari still needs to create the > /apps/data-mirroring directory in HDFS. > Also, RU/EU does not need to explicitly create the extensions directory in > the pre_upgrade_restart function since the start function will create it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17174) Ambari 2.4 with HDF management pack Ranger Service page : Domain Name(Only for AD)
[ https://issues.apache.org/jira/browse/AMBARI-17174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15325619#comment-15325619 ] Hudson commented on AMBARI-17174: - FAILURE: Integrated in Ambari-trunk-Commit #5057 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5057/]) AMBARI-17174. Ambari 2.4 with HDF management Pack : Ranger Service Page (sgunturi: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=5f16380b60e3db39d20ad4ca924f041330a808b9]) * ambari-web/app/data/custom_stack_map.js > Ambari 2.4 with HDF management pack Ranger Service page : Domain Name(Only > for AD) > -- > > Key: AMBARI-17174 > URL: https://issues.apache.org/jira/browse/AMBARI-17174 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Srimanth Gunturi >Assignee: Srimanth Gunturi > Fix For: 2.4.0 > > Attachments: AMBARI-17174.patch, Screen Shot 2016-05-18 at 11.21.48 > PM.png > > > This Jira issue is for Ambari 2.4 with HDF management pack. > Please feel free to change to the right project/component. > While testing HDF 2.0 deployment using Ambari GUI, need to add Ranger service. > In the Customize Service page of Ranger, in the "Advance" tab of Ranger > Service, there is one mandatory field called "Domain Name(Only for AD)". > The GUI automation test breaks due to this field. > 1. Is this a new feature? > 2. For internal testing, what should be the right value for this field? > Screenshot is attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17164) Handle Ranger upgrade scenario in Kerberized env
[
https://issues.apache.org/jira/browse/AMBARI-17164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15325620#comment-15325620
]
Hudson commented on AMBARI-17164:
-
FAILURE: Integrated in Ambari-trunk-Commit #5057 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5057/])
AMBARI-17164. Handle Ranger upgrade scenario in Kerberized env (Mugdha
(sgunturi:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=a4144d4e8dacb4b4d0ab08d2865a966b87dc25f9])
*
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.5.xml
*
ambari-server/src/test/java/org/apache/ambari/server/serveraction/upgrades/RangerKerberosConfigCalculationTest.java
*
ambari-server/src/main/resources/common-services/RANGER/0.6.0/configuration/ranger-admin-site.xml
*
ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.5.xml
* ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.5.xml
* ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.5.xml
*
ambari-server/src/main/java/org/apache/ambari/server/serveraction/upgrades/RangerKerberosConfigCalculation.java
* ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py
> Handle Ranger upgrade scenario in Kerberized env
>
>
> Key: AMBARI-17164
> URL: https://issues.apache.org/jira/browse/AMBARI-17164
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
> Fix For: 2.4.0
>
> Attachments: AMBARI-17164.patch
>
>
> Add this property to ranger-admin-site.xm:
> {code}
> ranger.plugins.{component}.serviceuser=service_user
> {code}
> Add spnego principal and keytab if cluster is kerberized to below properties:
> {code}
> ranger.spnego.kerberos.principal
> ranger.spnego.kerberos.keytab
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17118) Incorrect formated external url in ranger configuration - causes Namenode startup failure
[
https://issues.apache.org/jira/browse/AMBARI-17118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15325621#comment-15325621
]
Hudson commented on AMBARI-17118:
-
FAILURE: Integrated in Ambari-trunk-Commit #5057 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5057/])
AMBARI-17118. Incorrect formated external url in ranger configuration -
(sgunturi:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=60a7054dd62764efefde81fc20f1790c443d4c58])
*
ambari-common/src/main/python/resource_management/libraries/functions/setup_ranger_plugin.py
*
ambari-server/src/main/resources/common-services/STORM/0.9.1/package/scripts/params_linux.py
*
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/params_linux.py
*
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/params_linux.py
*
ambari-server/src/main/resources/common-services/RANGER_KMS/0.5.0.2.3/package/scripts/kms.py
* ambari-server/src/main/resources/stacks/HDP/2.3/services/stack_advisor.py
*
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py
*
ambari-server/src/main/resources/common-services/KAFKA/0.8.1/package/scripts/params.py
* ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py
*
ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/package/scripts/params_linux.py
*
ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/params.py
*
ambari-server/src/main/resources/common-services/KNOX/0.5.0.2.2/package/scripts/params_linux.py
*
ambari-server/src/main/resources/stacks/HDP/2.5/services/HDFS/configuration/ranger-hdfs-plugin-properties.xml
*
ambari-common/src/main/python/resource_management/libraries/functions/ranger_functions_v2.py
*
ambari-common/src/main/python/resource_management/libraries/functions/ranger_functions.py
*
ambari-server/src/main/resources/common-services/RANGER_KMS/0.5.0.2.3/package/scripts/params.py
*
ambari-common/src/main/python/resource_management/libraries/functions/setup_ranger_plugin_xml.py
> Incorrect formated external url in ranger configuration - causes Namenode
> startup failure
> -
>
> Key: AMBARI-17118
> URL: https://issues.apache.org/jira/browse/AMBARI-17118
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.1.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
> Fix For: 2.4.0
>
> Attachments: AMBARI-17118.1.patch, AMBARI-17118.patch
>
>
> STR:
> 1. install ambari and HDP with HDFS,YARN,HIVE
> 2. install ranger and configure *External URL*
> https://c6401.ambari.apache.org:6182/ ( means slash at the end of the URL
> which is allowed without any problem and installation is done successfully)
> 3. enable ranger plugin in hdfs config and restart it
> Result: NN startup fails and even after failure , error message in stack
> trace is confusing
> ERROR:
> ==
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/ranger_functions.py",
> line 108, in create_ranger_repository
> raise Fail('Ambari admin username and password are blank ')
> resource_management.core.exceptions.Fail: Ambari admin username and password
> are blank
> but actual reason is a slash at the end of the External URL,
> it fails the following point in
> usr/lib/python2.6/site-packages/resource_management/libraries/functions/ranger_functions.py:
> result = urllib2.urlopen(request)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17176) VDF: include default version definition in list, even if Internet Access is available
[
https://issues.apache.org/jira/browse/AMBARI-17176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15325591#comment-15325591
]
Hadoop QA commented on AMBARI-17176:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12809585/AMBARI-17176.v0.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-admin ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7307//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7307//console
This message is automatically generated.
> VDF: include default version definition in list, even if Internet Access is
> available
> -
>
> Key: AMBARI-17176
> URL: https://issues.apache.org/jira/browse/AMBARI-17176
> Project: Ambari
> Issue Type: Bug
> Components: ambari-admin, ambari-web
>Affects Versions: 2.4.0
>Reporter: Zhe (Joe) Wang
>Assignee: Zhe (Joe) Wang
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17176.v0.patch
>
>
> We need to include the Default Version Definition in the list of dropdown
> Versions along with the discovered versions.
> Current experience: we only include Default if we believe we do not have
> internet access
> New experience: include Default in the list regardless of internet or not.
> This is for backwards compatibility, and in the case where the user "just
> does not know" their version (and therefore, needs Ambari to just figure it
> out best it can).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-16220) No INSTALL commands
[
https://issues.apache.org/jira/browse/AMBARI-16220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15325571#comment-15325571
]
Hadoop QA commented on AMBARI-16220:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12809550/AMBARI-16220.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:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.state.ServicePropertiesTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7305//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7305//console
This message is automatically generated.
> No INSTALL commands
> ---
>
> Key: AMBARI-16220
> URL: https://issues.apache.org/jira/browse/AMBARI-16220
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Sebastian Toader
>Assignee: Sandor Magyari
> Fix For: 2.5.0
>
> Attachments: AMBARI-16220.patch
>
>
> In case packages.pre.installed=true is set in ambari.properties, Blueprint
> based deployments will not create INSTALL commands for service components.
> Normally START command should call configure, but we must ensure this is true
> for all used components. For client components INSTALL will be still
> generated.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17175) On Enabling HS Interactive default queue shown for llap is 'default' queue
[ https://issues.apache.org/jira/browse/AMBARI-17175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly updated AMBARI-17175: Resolution: Fixed Status: Resolved (was: Patch Available) Received +1 on reviewboard. Patch committed to trunk and branch-2.4 > On Enabling HS Interactive default queue shown for llap is 'default' queue > -- > > Key: AMBARI-17175 > URL: https://issues.apache.org/jira/browse/AMBARI-17175 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: ambari-2.4.0 >Reporter: Shraddha Sumit >Assignee: Jaimin D Jetly >Priority: Critical > Fix For: ambari-2.4.0 > > Attachments: AMBARI-17175.patch > > > 1. Deploy ambari secure cluster > 2. Enable HSI > Expected: llap queue is created by ambari and is set as default for llap > Actual: ldap queue is not created and default queue is set for ldap -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17175) On Enabling HS Interactive default queue shown for llap is 'default' queue
[ https://issues.apache.org/jira/browse/AMBARI-17175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly updated AMBARI-17175: Attachment: AMBARI-17175.patch > On Enabling HS Interactive default queue shown for llap is 'default' queue > -- > > Key: AMBARI-17175 > URL: https://issues.apache.org/jira/browse/AMBARI-17175 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: ambari-2.4.0 >Reporter: Shraddha Sumit >Assignee: Jaimin D Jetly >Priority: Critical > Fix For: ambari-2.4.0 > > Attachments: AMBARI-17175.patch > > > 1. Deploy ambari secure cluster > 2. Enable HSI > Expected: llap queue is created by ambari and is set as default for llap > Actual: ldap queue is not created and default queue is set for ldap -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17176) VDF: include default version definition in list, even if Internet Access is available
[ https://issues.apache.org/jira/browse/AMBARI-17176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-17176: Status: Patch Available (was: Open) > VDF: include default version definition in list, even if Internet Access is > available > - > > Key: AMBARI-17176 > URL: https://issues.apache.org/jira/browse/AMBARI-17176 > Project: Ambari > Issue Type: Bug > Components: ambari-admin, ambari-web >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17176.v0.patch > > > We need to include the Default Version Definition in the list of dropdown > Versions along with the discovered versions. > Current experience: we only include Default if we believe we do not have > internet access > New experience: include Default in the list regardless of internet or not. > This is for backwards compatibility, and in the case where the user "just > does not know" their version (and therefore, needs Ambari to just figure it > out best it can). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17175) On Enabling HS Interactive default queue shown for llap is 'default' queue
[ https://issues.apache.org/jira/browse/AMBARI-17175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly updated AMBARI-17175: Status: Patch Available (was: Open) Verified that the patch fixes the issue on a cluster ambari-web unit tests passes successfully with the patch: 28668 tests complete (28 seconds) 154 tests pending > On Enabling HS Interactive default queue shown for llap is 'default' queue > -- > > Key: AMBARI-17175 > URL: https://issues.apache.org/jira/browse/AMBARI-17175 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: ambari-2.4.0 >Reporter: Shraddha Sumit >Assignee: Jaimin D Jetly >Priority: Critical > Fix For: ambari-2.4.0 > > Attachments: AMBARI-17175.patch > > > 1. Deploy ambari secure cluster > 2. Enable HSI > Expected: llap queue is created by ambari and is set as default for llap > Actual: ldap queue is not created and default queue is set for ldap -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17176) VDF: include default version definition in list, even if Internet Access is available
[ https://issues.apache.org/jira/browse/AMBARI-17176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-17176: Attachment: AMBARI-17176.v0.patch ambari-web: 28670 tests complete (24 seconds) 154 tests pending ambari-admin: Executed 71 of 71 SUCCESS (0.142 secs / 0.356 secs) Manual testing done. > VDF: include default version definition in list, even if Internet Access is > available > - > > Key: AMBARI-17176 > URL: https://issues.apache.org/jira/browse/AMBARI-17176 > Project: Ambari > Issue Type: Bug > Components: ambari-admin, ambari-web >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17176.v0.patch > > > We need to include the Default Version Definition in the list of dropdown > Versions along with the discovered versions. > Current experience: we only include Default if we believe we do not have > internet access > New experience: include Default in the list regardless of internet or not. > This is for backwards compatibility, and in the case where the user "just > does not know" their version (and therefore, needs Ambari to just figure it > out best it can). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AMBARI-17175) On Enabling HS Interactive default queue shown for llap is 'default' queue
[ https://issues.apache.org/jira/browse/AMBARI-17175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly reassigned AMBARI-17175: --- Assignee: Jaimin D Jetly > On Enabling HS Interactive default queue shown for llap is 'default' queue > -- > > Key: AMBARI-17175 > URL: https://issues.apache.org/jira/browse/AMBARI-17175 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: ambari-2.4.0 >Reporter: Shraddha Sumit >Assignee: Jaimin D Jetly >Priority: Critical > Fix For: ambari-2.4.0 > > > 1. Deploy ambari secure cluster > 2. Enable HSI > Expected: llap queue is created by ambari and is set as default for llap > Actual: ldap queue is not created and default queue is set for ldap -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17176) VDF: include default version definition in list, even if Internet Access is available
Zhe (Joe) Wang created AMBARI-17176: --- Summary: VDF: include default version definition in list, even if Internet Access is available Key: AMBARI-17176 URL: https://issues.apache.org/jira/browse/AMBARI-17176 Project: Ambari Issue Type: Bug Components: ambari-admin, ambari-web Affects Versions: 2.4.0 Reporter: Zhe (Joe) Wang Assignee: Zhe (Joe) Wang Priority: Critical Fix For: 2.4.0 We need to include the Default Version Definition in the list of dropdown Versions along with the discovered versions. Current experience: we only include Default if we believe we do not have internet access New experience: include Default in the list regardless of internet or not. This is for backwards compatibility, and in the case where the user "just does not know" their version (and therefore, needs Ambari to just figure it out best it can). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17054) Configure Atlas Ranger Plugin
[ https://issues.apache.org/jira/browse/AMBARI-17054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15325528#comment-15325528 ] Hudson commented on AMBARI-17054: - FAILURE: Integrated in Ambari-trunk-Commit #5056 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5056/]) AMBARI-17054. Configure Atlas Ranger Plugin - with test fixes. (Gautam (sgunturi: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=6ddb04ecdf26126b8b85316488116f3f964a5cc8]) * ambari-server/src/main/resources/stacks/HDP/2.5/services/ATLAS/configuration/ranger-atlas-policymgr-ssl.xml * ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/package/scripts/status_params.py * ambari-server/src/main/resources/stacks/HDP/2.5/services/ATLAS/configuration/ranger-atlas-security.xml * ambari-common/src/main/python/resource_management/libraries/functions/constants.py * ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata_server.py * ambari-server/src/test/python/stacks/2.5/common/test_stack_advisor.py * ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py * ambari-server/src/main/resources/common-services/RANGER/0.6.0/configuration/ranger-env.xml * ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/package/scripts/setup_ranger_atlas.py * ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/package/scripts/params.py * ambari-server/src/main/resources/common-services/RANGER/0.6.0/themes/theme_version_3.json * ambari-server/src/main/resources/stacks/HDP/2.5/services/ATLAS/configuration/application-properties.xml * ambari-server/src/main/resources/stacks/HDP/2.5/services/ATLAS/configuration/ranger-atlas-plugin-properties.xml * ambari-server/src/main/resources/stacks/HDP/2.5/services/ATLAS/configuration/ranger-atlas-audit.xml * ambari-server/src/main/resources/stacks/HDP/2.0.6/properties/stack_features.json > Configure Atlas Ranger Plugin > - > > Key: AMBARI-17054 > URL: https://issues.apache.org/jira/browse/AMBARI-17054 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Gautam Borad >Assignee: Gautam Borad > Fix For: 2.4.0 > > Attachments: AMBARI-17054.1.patch, AMBARI-17054.2.patch, > AMBARI-17054.3.patch, AMBARI-17054_trunk.1.patch, AMBARI-17054_trunk.patch > > > Need to do following changes to support Ranger Atlas Plugin from Ambari: > 1) Check stack support and provide smart config section to Enable / disable > ranger atlas plugin > 2) Stack advisor changes to suggest recommended configs on enable / disable > plugin actions. > 3) Ranger service creation on Enable plugin action from Ambari. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17151) Blueprint deployments fail when services manually removed from stack definitions
[ https://issues.apache.org/jira/browse/AMBARI-17151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15325527#comment-15325527 ] Hudson commented on AMBARI-17151: - FAILURE: Integrated in Ambari-trunk-Commit #5056 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5056/]) AMBARI-17151. Blueprint deployments fail when services manually removed (rnettleton: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e0dd3bf6218fc8c2733e936aa24bfc87fd60739e]) * ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessor.java * ambari-server/src/test/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessorTest.java > Blueprint deployments fail when services manually removed from stack > definitions > > > Key: AMBARI-17151 > URL: https://issues.apache.org/jira/browse/AMBARI-17151 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Robert Nettleton >Assignee: Robert Nettleton >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17151.patch > > Original Estimate: 24h > Remaining Estimate: 24h > > In certain custom use cases, an Ambari user may choose to customize the > Ambari stack definitions by manually removing services. > This can cause some failures during a Blueprint deployment, particularly in > the area of "excluded" configurations. > When an "excluded" configuration type is found, the Blueprint processor > attempts to add this configuration, and queries the Stack APIs to determine > the service associated with this configuration type. > If this particular service has been manually deleted from the stacks, the > Stack APIs will throw a runtime exception, which causes the entire Blueprint > deployment to fail. > Example: > If Ambari Metrics is included in a Blueprint, the "storm-site" configuration > type is considered an "excluded-configuration" by the stack definitions. In > this case, if the "STORM" service definitions have been removed, then the > following exception will result when a cluster deployment based on a > Blueprint is attempted: > java.lang.IllegalArgumentException: Specified configuration type is not > associated with any service: storm-site > at > org.apache.ambari.server.controller.internal.Stack.getServiceForConfigType(Stack.java:485) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.addExcludedConfigProperties(BlueprintConfigurationProcessor.java:2781) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.setMissingConfigurations(BlueprintConfigurationProcessor.java:2751) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doUpdateForClusterCreate(BlueprintConfigurationProcessor.java:335) > at > org.apache.ambari.server.topology.ClusterConfigurationRequest.process(ClusterConfigurationRequest.java:153) > at > org.apache.ambari.server.topology.TopologyManager$ConfigureClusterTask.call(TopologyManager.java:780) > at > org.apache.ambari.server.topology.TopologyManager$ConfigureClusterTask.call(TopologyManager.java:754) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > ... > In these custom deployments, the Blueprints processor should be more lenient > with respect to error handling. > If a matching service is not found for a given "excluded" configuration type, > the Blueprint processor should log this as a WARNING, indicating that the > stacks have likely been modified outside of Ambari. > I'm working on a fix for this, and will be submitting a patch soon. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17113) Add user home directory verification as part of Service Check
[ https://issues.apache.org/jira/browse/AMBARI-17113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15325526#comment-15325526 ] Hudson commented on AMBARI-17113: - FAILURE: Integrated in Ambari-trunk-Commit #5056 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5056/]) Revert "AMBARI-17113. Add user home directory verification as part of (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=07f94cb7ac9627cb114e3c41edb524664660ff87]) * contrib/views/pig/src/main/java/org/apache/ambari/view/pig/resources/files/FileService.java * contrib/views/hive/src/main/resources/ui/hive-web/app/routes/splash.js * contrib/views/files/src/main/resources/ui/app/templates/splash.hbs * contrib/views/pig/src/main/resources/ui/pig-web/app/templates/splash.hbs * contrib/views/hive/src/main/resources/ui/hive-web/app/templates/splash.hbs * contrib/views/pig/src/main/resources/ui/pig-web/app/translations.js * contrib/views/pig/src/main/java/org/apache/ambari/view/pig/services/HelpService.java * contrib/views/hive/src/main/java/org/apache/ambari/view/hive/HelpService.java * contrib/views/pig/pom.xml * contrib/views/pig/src/main/resources/ui/pig-web/app/routes/splash.js * contrib/views/pig/src/main/resources/ui/pig-web/app/controllers/splash.js * contrib/views/hive/src/main/resources/ui/hive-web/app/controllers/splash.js * contrib/views/hive/src/main/java/org/apache/ambari/view/hive/resources/files/FileService.java * contrib/views/hive/pom.xml > Add user home directory verification as part of Service Check > - > > Key: AMBARI-17113 > URL: https://issues.apache.org/jira/browse/AMBARI-17113 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Pallav Kulshreshtha >Assignee: Pallav Kulshreshtha > Fix For: 2.4.0 > > Attachments: AMBARI-17113_branch-2.4-2.patch > > > Add a check at the time of loading the view for presence of home directory > and provide error message if absent. Prompt the user to verify this before he > starts using this. Following views: > - Pig > - Hive -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17175) On Enabling HS Interactive default queue shown for llap is 'default' queue
[ https://issues.apache.org/jira/browse/AMBARI-17175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly updated AMBARI-17175: Description: 1. Deploy ambari secure cluster 2. Enable HSI Expected: llap queue is created by ambari and is set as default for llap Actual: ldap queue is not created and default queue is set for ldap was: 1. Deploy ambari secure cluster 2. Enable HSI Expected: llap queue is created by ambari and is set as default for llap Actual: ldap queue is not created and default queue is set for ldap http://qelog.hortonworks.com/log/os-r6-xilrjs-ambari-hivellap/test-logs/ambari-hivellap/artifacts/screenshots/com.hw.ambari.ui.tests.services.hive_interactive.TestHiveInteractive/test02_enableHiveInteractive/_9_3_10_33_Element_has_not_been_found_within_15_seconds__/blueprints/exported_blueprint.json Attachments BUG-59819.patch 1.0 kB10/Jun/16 4:07 PM exported_blueprint_llap_capacity_scheduler_properties.json 501 kB09/Jun/16 12:54 PM os-r6-xilrjs-ambari-hivellap-1.openstacklocal.tar.lzma 268 kB09/Jun/16 12:51 PM os-r6-xilrjs-ambari-hivellap-3.openstacklocal.tar.lzma 371 kB09/Jun/16 12:51 PM os-r6-xilrjs-ambari-hivellap-5.openstacklocal.tar.lzma 459 kB09/Jun/16 12:51 PM screenshot_yarn_memory_per_daemon_blank.png screenshot_yarn_memory_per_daemon_blank.png 188 kB09/Jun/16 12:50 PM Screen Shot 2016-06-10 at 11.28.53 AM.png Screen Shot 2016-06-10 at 11.28.53 AM.png 477 kB10/Jun/16 11:29 AM Screen Shot 2016-06-10 at 11.31.17 AM.png Screen Shot 2016-06-10 at 11.31.17 AM.png 461 kB10/Jun/16 11:32 AM Screen Shot 2016-06-10 at 11.34.56 AM.png Screen Shot 2016-06-10 at 11.34.56 AM.png 181 kB10/Jun/16 11:37 AM Screen Shot 2016-06-10 at 11.36.09 AM.png Screen Shot 2016-06-10 at 11.36.09 AM.png 119 kB10/Jun/16 11:36 AM test_video_part1.flv 4.68 MB09/Jun/16 12:51 PM Add LinkIssue Links is duplicated by Bug - A problem which impairs or prevents the functions of the product. BUG-59713 Cannot enable Interactive Query on HiveServer2 Major - Major loss of function. RESOLVED Activity Comment People Assignee:jaimin Jaimin Jetly Assign to me Reporter:ssumit Shraddha Sumit QEAssignee: unassigned Votes: 0 Watchers: 2 Stop watching this issue Dates Created:Yesterday 12:51 PM Updated:Today 4:09 PM Who's Looking? Agile Active Sprint: Ambari: Sprint 162 ends 13/Jun/16 View on Board HipChat discussions > On Enabling HS Interactive default queue shown for llap is 'default' queue > -- > > Key: AMBARI-17175 > URL: https://issues.apache.org/jira/browse/AMBARI-17175 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: ambari-2.4.0 >Reporter: Shraddha Sumit >Priority: Critical > Fix For: ambari-2.4.0 > > > 1. Deploy ambari secure cluster > 2. Enable HSI > Expected: llap queue is created by ambari and is set as default for llap > Actual: ldap queue is not created and default queue is set for ldap -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17175) On Enabling HS Interactive default queue shown for llap is 'default' queue
Shraddha Sumit created AMBARI-17175: --- Summary: On Enabling HS Interactive default queue shown for llap is 'default' queue Key: AMBARI-17175 URL: https://issues.apache.org/jira/browse/AMBARI-17175 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: ambari-2.4.0 Reporter: Shraddha Sumit Priority: Critical Fix For: ambari-2.4.0 1. Deploy ambari secure cluster 2. Enable HSI Expected: llap queue is created by ambari and is set as default for llap Actual: ldap queue is not created and default queue is set for ldap http://qelog.hortonworks.com/log/os-r6-xilrjs-ambari-hivellap/test-logs/ambari-hivellap/artifacts/screenshots/com.hw.ambari.ui.tests.services.hive_interactive.TestHiveInteractive/test02_enableHiveInteractive/_9_3_10_33_Element_has_not_been_found_within_15_seconds__/blueprints/exported_blueprint.json Attachments BUG-59819.patch 1.0 kB10/Jun/16 4:07 PM exported_blueprint_llap_capacity_scheduler_properties.json 501 kB09/Jun/16 12:54 PM os-r6-xilrjs-ambari-hivellap-1.openstacklocal.tar.lzma 268 kB09/Jun/16 12:51 PM os-r6-xilrjs-ambari-hivellap-3.openstacklocal.tar.lzma 371 kB09/Jun/16 12:51 PM os-r6-xilrjs-ambari-hivellap-5.openstacklocal.tar.lzma 459 kB09/Jun/16 12:51 PM screenshot_yarn_memory_per_daemon_blank.png screenshot_yarn_memory_per_daemon_blank.png 188 kB09/Jun/16 12:50 PM Screen Shot 2016-06-10 at 11.28.53 AM.png Screen Shot 2016-06-10 at 11.28.53 AM.png 477 kB10/Jun/16 11:29 AM Screen Shot 2016-06-10 at 11.31.17 AM.png Screen Shot 2016-06-10 at 11.31.17 AM.png 461 kB10/Jun/16 11:32 AM Screen Shot 2016-06-10 at 11.34.56 AM.png Screen Shot 2016-06-10 at 11.34.56 AM.png 181 kB10/Jun/16 11:37 AM Screen Shot 2016-06-10 at 11.36.09 AM.png Screen Shot 2016-06-10 at 11.36.09 AM.png 119 kB10/Jun/16 11:36 AM test_video_part1.flv 4.68 MB09/Jun/16 12:51 PM Add LinkIssue Links is duplicated by Bug - A problem which impairs or prevents the functions of the product. BUG-59713 Cannot enable Interactive Query on HiveServer2 Major - Major loss of function. RESOLVED Activity Comment People Assignee:jaimin Jaimin Jetly Assign to me Reporter:ssumit Shraddha Sumit QEAssignee: unassigned Votes: 0 Watchers: 2 Stop watching this issue Dates Created:Yesterday 12:51 PM Updated:Today 4:09 PM Who's Looking? Agile Active Sprint: Ambari: Sprint 162 ends 13/Jun/16 View on Board HipChat discussions -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16220) No INSTALL commands
[
https://issues.apache.org/jira/browse/AMBARI-16220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15325448#comment-15325448
]
Hadoop QA commented on AMBARI-16220:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12809486/AMBARI-16220.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:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.state.ServicePropertiesTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7304//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7304//console
This message is automatically generated.
> No INSTALL commands
> ---
>
> Key: AMBARI-16220
> URL: https://issues.apache.org/jira/browse/AMBARI-16220
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Sebastian Toader
>Assignee: Sandor Magyari
> Fix For: 2.5.0
>
> Attachments: AMBARI-16220.patch
>
>
> In case packages.pre.installed=true is set in ambari.properties, Blueprint
> based deployments will not create INSTALL commands for service components.
> Normally START command should call configure, but we must ensure this is true
> for all used components. For client components INSTALL will be still
> generated.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17164) Handle Ranger upgrade scenario in Kerberized env
[
https://issues.apache.org/jira/browse/AMBARI-17164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srimanth Gunturi updated AMBARI-17164:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk and branch-2.4
> Handle Ranger upgrade scenario in Kerberized env
>
>
> Key: AMBARI-17164
> URL: https://issues.apache.org/jira/browse/AMBARI-17164
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
> Fix For: 2.4.0
>
> Attachments: AMBARI-17164.patch
>
>
> Add this property to ranger-admin-site.xm:
> {code}
> ranger.plugins.{component}.serviceuser=service_user
> {code}
> Add spnego principal and keytab if cluster is kerberized to below properties:
> {code}
> ranger.spnego.kerberos.principal
> ranger.spnego.kerberos.keytab
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17171) Falcon to create data-mirroring directory in HDFS if extensions is supported
[ https://issues.apache.org/jira/browse/AMBARI-17171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-17171: - Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to trunk, commit 38bfa42e027a47a3ecbdb57d0453f8140ef7f92f branch-2.4, commit defe34218751fd80264bc7690c5ac1964f7d5c10 > Falcon to create data-mirroring directory in HDFS if extensions is supported > > > Key: AMBARI-17171 > URL: https://issues.apache.org/jira/browse/AMBARI-17171 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: Murali Ramasami >Assignee: Alejandro Fernandez > Fix For: trunk, 2.4.0 > > Attachments: AMBARI-17171.branch-2.4.patch, AMBARI-17171.trunk.patch > > > If Falcon extensions is supported, Ambari still needs to create the > /apps/data-mirroring directory in HDFS. > Also, RU/EU does not need to explicitly create the extensions directory in > the pre_upgrade_restart function since the start function will create it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17118) Incorrect formated external url in ranger configuration - causes Namenode startup failure
[
https://issues.apache.org/jira/browse/AMBARI-17118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srimanth Gunturi updated AMBARI-17118:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk and branch-2.4
> Incorrect formated external url in ranger configuration - causes Namenode
> startup failure
> -
>
> Key: AMBARI-17118
> URL: https://issues.apache.org/jira/browse/AMBARI-17118
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.1.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
> Fix For: 2.4.0
>
> Attachments: AMBARI-17118.1.patch, AMBARI-17118.patch
>
>
> STR:
> 1. install ambari and HDP with HDFS,YARN,HIVE
> 2. install ranger and configure *External URL*
> https://c6401.ambari.apache.org:6182/ ( means slash at the end of the URL
> which is allowed without any problem and installation is done successfully)
> 3. enable ranger plugin in hdfs config and restart it
> Result: NN startup fails and even after failure , error message in stack
> trace is confusing
> ERROR:
> ==
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/ranger_functions.py",
> line 108, in create_ranger_repository
> raise Fail('Ambari admin username and password are blank ')
> resource_management.core.exceptions.Fail: Ambari admin username and password
> are blank
> but actual reason is a slash at the end of the External URL,
> it fails the following point in
> usr/lib/python2.6/site-packages/resource_management/libraries/functions/ranger_functions.py:
> result = urllib2.urlopen(request)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17174) Ambari 2.4 with HDF management pack Ranger Service page : Domain Name(Only for AD)
[ https://issues.apache.org/jira/browse/AMBARI-17174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srimanth Gunturi updated AMBARI-17174: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.4 > Ambari 2.4 with HDF management pack Ranger Service page : Domain Name(Only > for AD) > -- > > Key: AMBARI-17174 > URL: https://issues.apache.org/jira/browse/AMBARI-17174 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Srimanth Gunturi >Assignee: Srimanth Gunturi > Fix For: 2.4.0 > > Attachments: AMBARI-17174.patch, Screen Shot 2016-05-18 at 11.21.48 > PM.png > > > This Jira issue is for Ambari 2.4 with HDF management pack. > Please feel free to change to the right project/component. > While testing HDF 2.0 deployment using Ambari GUI, need to add Ranger service. > In the Customize Service page of Ranger, in the "Advance" tab of Ranger > Service, there is one mandatory field called "Domain Name(Only for AD)". > The GUI automation test breaks due to this field. > 1. Is this a new feature? > 2. For internal testing, what should be the right value for this field? > Screenshot is attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17174) Ambari 2.4 with HDF management pack Ranger Service page : Domain Name(Only for AD)
[ https://issues.apache.org/jira/browse/AMBARI-17174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15325370#comment-15325370 ] Jaimin D Jetly commented on AMBARI-17174: - +1 for the patch. > Ambari 2.4 with HDF management pack Ranger Service page : Domain Name(Only > for AD) > -- > > Key: AMBARI-17174 > URL: https://issues.apache.org/jira/browse/AMBARI-17174 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Srimanth Gunturi >Assignee: Srimanth Gunturi > Fix For: 2.4.0 > > Attachments: AMBARI-17174.patch, Screen Shot 2016-05-18 at 11.21.48 > PM.png > > > This Jira issue is for Ambari 2.4 with HDF management pack. > Please feel free to change to the right project/component. > While testing HDF 2.0 deployment using Ambari GUI, need to add Ranger service. > In the Customize Service page of Ranger, in the "Advance" tab of Ranger > Service, there is one mandatory field called "Domain Name(Only for AD)". > The GUI automation test breaks due to this field. > 1. Is this a new feature? > 2. For internal testing, what should be the right value for this field? > Screenshot is attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17173) Allow option to skip duplicate URL checking when creating VDF
[ https://issues.apache.org/jira/browse/AMBARI-17173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15325335#comment-15325335 ] Hudson commented on AMBARI-17173: - FAILURE: Integrated in Ambari-trunk-Commit #5055 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5055/]) AMBARI-17173. Allow option to skip duplicate URL checking when creating (ncole: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=bf07707eac7a84aa7dcf833d94a11b865fb32e6e]) * ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RepositoryVersionResourceProvider.java * ambari-server/src/test/java/org/apache/ambari/server/controller/internal/VersionDefinitionResourceProviderTest.java * ambari-server/src/main/java/org/apache/ambari/server/controller/internal/VersionDefinitionResourceProvider.java * ambari-server/src/main/java/org/apache/ambari/server/api/resources/VersionDefinitionResourceDefinition.java > Allow option to skip duplicate URL checking when creating VDF > - > > Key: AMBARI-17173 > URL: https://issues.apache.org/jira/browse/AMBARI-17173 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole > Fix For: 2.4.0 > > > When creating a VDF, it may be desirable to skip dupe base URL checking. > This is implemented as a Create Directive. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17151) Blueprint deployments fail when services manually removed from stack definitions
[ https://issues.apache.org/jira/browse/AMBARI-17151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Nettleton updated AMBARI-17151: -- Resolution: Fixed Status: Resolved (was: Patch Available) Patch merged to trunk and branch-2.4 > Blueprint deployments fail when services manually removed from stack > definitions > > > Key: AMBARI-17151 > URL: https://issues.apache.org/jira/browse/AMBARI-17151 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Robert Nettleton >Assignee: Robert Nettleton >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17151.patch > > Original Estimate: 24h > Remaining Estimate: 24h > > In certain custom use cases, an Ambari user may choose to customize the > Ambari stack definitions by manually removing services. > This can cause some failures during a Blueprint deployment, particularly in > the area of "excluded" configurations. > When an "excluded" configuration type is found, the Blueprint processor > attempts to add this configuration, and queries the Stack APIs to determine > the service associated with this configuration type. > If this particular service has been manually deleted from the stacks, the > Stack APIs will throw a runtime exception, which causes the entire Blueprint > deployment to fail. > Example: > If Ambari Metrics is included in a Blueprint, the "storm-site" configuration > type is considered an "excluded-configuration" by the stack definitions. In > this case, if the "STORM" service definitions have been removed, then the > following exception will result when a cluster deployment based on a > Blueprint is attempted: > java.lang.IllegalArgumentException: Specified configuration type is not > associated with any service: storm-site > at > org.apache.ambari.server.controller.internal.Stack.getServiceForConfigType(Stack.java:485) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.addExcludedConfigProperties(BlueprintConfigurationProcessor.java:2781) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.setMissingConfigurations(BlueprintConfigurationProcessor.java:2751) > at > org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doUpdateForClusterCreate(BlueprintConfigurationProcessor.java:335) > at > org.apache.ambari.server.topology.ClusterConfigurationRequest.process(ClusterConfigurationRequest.java:153) > at > org.apache.ambari.server.topology.TopologyManager$ConfigureClusterTask.call(TopologyManager.java:780) > at > org.apache.ambari.server.topology.TopologyManager$ConfigureClusterTask.call(TopologyManager.java:754) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > ... > In these custom deployments, the Blueprints processor should be more lenient > with respect to error handling. > If a matching service is not found for a given "excluded" configuration type, > the Blueprint processor should log this as a WARNING, indicating that the > stacks have likely been modified outside of Ambari. > I'm working on a fix for this, and will be submitting a patch soon. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17171) Falcon to create data-mirroring directory in HDFS if extensions is supported
[ https://issues.apache.org/jira/browse/AMBARI-17171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-17171: - Description: If Falcon extensions is supported, Ambari still needs to create the /apps/data-mirroring directory in HDFS. Also, RU/EU does not need to explicitly create the extensions directory in the pre_upgrade_restart function since the start function will create it. was: If Falcon extensions is supported, Ambari still needs to create the /apps/falcon/data-mirroring directory in HDFS. Also, RU/EU does not need to explicitly create the extensions directory in the pre_upgrade_restart function since the start function will create it. > Falcon to create data-mirroring directory in HDFS if extensions is supported > > > Key: AMBARI-17171 > URL: https://issues.apache.org/jira/browse/AMBARI-17171 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: Murali Ramasami >Assignee: Alejandro Fernandez > Fix For: trunk, 2.4.0 > > Attachments: AMBARI-17171.branch-2.4.patch, AMBARI-17171.trunk.patch > > > If Falcon extensions is supported, Ambari still needs to create the > /apps/data-mirroring directory in HDFS. > Also, RU/EU does not need to explicitly create the extensions directory in > the pre_upgrade_restart function since the start function will create it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16220) No INSTALL commands
[ https://issues.apache.org/jira/browse/AMBARI-16220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Magyari updated AMBARI-16220: Attachment: AMBARI-16220.patch > No INSTALL commands > --- > > Key: AMBARI-16220 > URL: https://issues.apache.org/jira/browse/AMBARI-16220 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Sebastian Toader >Assignee: Sandor Magyari > Fix For: 2.5.0 > > Attachments: AMBARI-16220.patch > > > In case packages.pre.installed=true is set in ambari.properties, Blueprint > based deployments will not create INSTALL commands for service components. > Normally START command should call configure, but we must ensure this is true > for all used components. For client components INSTALL will be still > generated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16220) No INSTALL commands
[ https://issues.apache.org/jira/browse/AMBARI-16220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Magyari updated AMBARI-16220: Attachment: (was: AMBARI-16220.patch) > No INSTALL commands > --- > > Key: AMBARI-16220 > URL: https://issues.apache.org/jira/browse/AMBARI-16220 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Sebastian Toader >Assignee: Sandor Magyari > Fix For: 2.5.0 > > > In case packages.pre.installed=true is set in ambari.properties, Blueprint > based deployments will not create INSTALL commands for service components. > Normally START command should call configure, but we must ensure this is true > for all used components. For client components INSTALL will be still > generated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16220) No INSTALL commands
[ https://issues.apache.org/jira/browse/AMBARI-16220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Magyari updated AMBARI-16220: Attachment: AMBARI-16220.patch > No INSTALL commands > --- > > Key: AMBARI-16220 > URL: https://issues.apache.org/jira/browse/AMBARI-16220 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Sebastian Toader >Assignee: Sandor Magyari > Fix For: 2.5.0 > > Attachments: AMBARI-16220.patch > > > In case packages.pre.installed=true is set in ambari.properties, Blueprint > based deployments will not create INSTALL commands for service components. > Normally START command should call configure, but we must ensure this is true > for all used components. For client components INSTALL will be still > generated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16220) No INSTALL commands
[ https://issues.apache.org/jira/browse/AMBARI-16220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Magyari updated AMBARI-16220: Attachment: (was: AMBARI-16220.patch) > No INSTALL commands > --- > > Key: AMBARI-16220 > URL: https://issues.apache.org/jira/browse/AMBARI-16220 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Sebastian Toader >Assignee: Sandor Magyari > Fix For: 2.5.0 > > Attachments: AMBARI-16220.patch > > > In case packages.pre.installed=true is set in ambari.properties, Blueprint > based deployments will not create INSTALL commands for service components. > Normally START command should call configure, but we must ensure this is true > for all used components. For client components INSTALL will be still > generated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16998) Fix intermittent unit test failure in TestMpacks
[
https://issues.apache.org/jira/browse/AMBARI-16998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15325267#comment-15325267
]
Hadoop QA commented on AMBARI-16998:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12809504/AMBARI-16998.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/7303//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7303//console
This message is automatically generated.
> Fix intermittent unit test failure in TestMpacks
>
>
> Key: AMBARI-16998
> URL: https://issues.apache.org/jira/browse/AMBARI-16998
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-16998.patch
>
>
> {code}
> Running tests for ambari-server
> Traceback (most recent call last):
> File "unitTests.py", line 298, in
> sys.exit(main())
> File "unitTests.py", line 250, in main
> File ambari.properties not found in search path $AMBARI_CONF_DIR:
> /etc/ambari-server/conf
> suites = [unittest.defaultTestLoader.loadTestsFromName(name) for name in
> modules]
> File "/usr/lib/python2.7/unittest/loader.py", line 91, in loadTestsFromName
> module = __import__('.'.join(parts_copy))
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/test/python/TestMpacks.py",
> line 21, in
> from ambari_server.setupMpacks import install_mpack, upgrade_mpack,
> replay_mpack_logs, purge_stacks_and_mpacks, \
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/setupMpacks.py",
> line 31, in
> from ambari_server.serverConfiguration import get_ambari_properties,
> get_ambari_version, get_stack_location, \
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverConfiguration.py",
> line 537, in
> configDefaults = ServerConfigDefaults()
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverConfiguration.py",
> line 456, in __init__
> super(ServerConfigDefaultsLinux, self).__init__()
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverConfiguration.py",
> line 327, in __init__
> properties = get_ambari_properties()
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverConfiguration.py",
> line 225, in get_ambari_properties
> conf_file = find_properties_file()
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverConfiguration.py",
> line 218, in find_properties_file
> raise FatalException(1, err)
> ambari_commons.exceptions.FatalException: 'Fatal exception: File
> ambari.properties not found in search path $AMBARI_CONF_DIR:
> /etc/ambari-server/conf, exit code 1'
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17174) Ambari 2.4 with HDF management pack Ranger Service page : Domain Name(Only for AD)
[ https://issues.apache.org/jira/browse/AMBARI-17174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srimanth Gunturi updated AMBARI-17174: -- Attachment: AMBARI-17174.patch > Ambari 2.4 with HDF management pack Ranger Service page : Domain Name(Only > for AD) > -- > > Key: AMBARI-17174 > URL: https://issues.apache.org/jira/browse/AMBARI-17174 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Srimanth Gunturi >Assignee: Srimanth Gunturi > Fix For: 2.4.0 > > Attachments: AMBARI-17174.patch, Screen Shot 2016-05-18 at 11.21.48 > PM.png > > > This Jira issue is for Ambari 2.4 with HDF management pack. > Please feel free to change to the right project/component. > While testing HDF 2.0 deployment using Ambari GUI, need to add Ranger service. > In the Customize Service page of Ranger, in the "Advance" tab of Ranger > Service, there is one mandatory field called "Domain Name(Only for AD)". > The GUI automation test breaks due to this field. > 1. Is this a new feature? > 2. For internal testing, what should be the right value for this field? > Screenshot is attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17174) Ambari 2.4 with HDF management pack Ranger Service page : Domain Name(Only for AD)
[ https://issues.apache.org/jira/browse/AMBARI-17174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srimanth Gunturi updated AMBARI-17174: -- Status: Patch Available (was: Open) > Ambari 2.4 with HDF management pack Ranger Service page : Domain Name(Only > for AD) > -- > > Key: AMBARI-17174 > URL: https://issues.apache.org/jira/browse/AMBARI-17174 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Srimanth Gunturi >Assignee: Srimanth Gunturi > Fix For: 2.4.0 > > Attachments: AMBARI-17174.patch, Screen Shot 2016-05-18 at 11.21.48 > PM.png > > > This Jira issue is for Ambari 2.4 with HDF management pack. > Please feel free to change to the right project/component. > While testing HDF 2.0 deployment using Ambari GUI, need to add Ranger service. > In the Customize Service page of Ranger, in the "Advance" tab of Ranger > Service, there is one mandatory field called "Domain Name(Only for AD)". > The GUI automation test breaks due to this field. > 1. Is this a new feature? > 2. For internal testing, what should be the right value for this field? > Screenshot is attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17174) Ambari 2.4 with HDF management Pack Ranger Service Page : Domain Name(Only for AD)
[ https://issues.apache.org/jira/browse/AMBARI-17174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srimanth Gunturi updated AMBARI-17174: -- Summary: Ambari 2.4 with HDF management Pack Ranger Service Page : Domain Name(Only for AD) (was: Ambari 2.4 with HDF management Pack : Ranger Service Page : Domain Name(Only for AD)) > Ambari 2.4 with HDF management Pack Ranger Service Page : Domain Name(Only > for AD) > -- > > Key: AMBARI-17174 > URL: https://issues.apache.org/jira/browse/AMBARI-17174 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Srimanth Gunturi >Assignee: Srimanth Gunturi > Fix For: 2.4.0 > > Attachments: Screen Shot 2016-05-18 at 11.21.48 PM.png > > > This Jira issue is for Ambari 2.4 with HDF management pack. > Please feel free to change to the right project/component. > While testing HDF 2.0 deployment using Ambari GUI, need to add Ranger service. > In the Customize Service page of Ranger, in the "Advance" tab of Ranger > Service, there is one mandatory field called "Domain Name(Only for AD)". > The GUI automation test breaks due to this field. > 1. Is this a new feature? > 2. For internal testing, what should be the right value for this field? > Screenshot is attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17174) Ambari 2.4 with HDF management pack Ranger Service Page : Domain Name(Only for AD)
[ https://issues.apache.org/jira/browse/AMBARI-17174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srimanth Gunturi updated AMBARI-17174: -- Summary: Ambari 2.4 with HDF management pack Ranger Service Page : Domain Name(Only for AD) (was: Ambari 2.4 with HDF management Pack Ranger Service Page : Domain Name(Only for AD)) > Ambari 2.4 with HDF management pack Ranger Service Page : Domain Name(Only > for AD) > -- > > Key: AMBARI-17174 > URL: https://issues.apache.org/jira/browse/AMBARI-17174 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Srimanth Gunturi >Assignee: Srimanth Gunturi > Fix For: 2.4.0 > > Attachments: Screen Shot 2016-05-18 at 11.21.48 PM.png > > > This Jira issue is for Ambari 2.4 with HDF management pack. > Please feel free to change to the right project/component. > While testing HDF 2.0 deployment using Ambari GUI, need to add Ranger service. > In the Customize Service page of Ranger, in the "Advance" tab of Ranger > Service, there is one mandatory field called "Domain Name(Only for AD)". > The GUI automation test breaks due to this field. > 1. Is this a new feature? > 2. For internal testing, what should be the right value for this field? > Screenshot is attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17174) Ambari 2.4 with HDF management pack Ranger Service page : Domain Name(Only for AD)
[ https://issues.apache.org/jira/browse/AMBARI-17174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srimanth Gunturi updated AMBARI-17174: -- Summary: Ambari 2.4 with HDF management pack Ranger Service page : Domain Name(Only for AD) (was: Ambari 2.4 with HDF management pack Ranger Service Page : Domain Name(Only for AD)) > Ambari 2.4 with HDF management pack Ranger Service page : Domain Name(Only > for AD) > -- > > Key: AMBARI-17174 > URL: https://issues.apache.org/jira/browse/AMBARI-17174 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Srimanth Gunturi >Assignee: Srimanth Gunturi > Fix For: 2.4.0 > > Attachments: Screen Shot 2016-05-18 at 11.21.48 PM.png > > > This Jira issue is for Ambari 2.4 with HDF management pack. > Please feel free to change to the right project/component. > While testing HDF 2.0 deployment using Ambari GUI, need to add Ranger service. > In the Customize Service page of Ranger, in the "Advance" tab of Ranger > Service, there is one mandatory field called "Domain Name(Only for AD)". > The GUI automation test breaks due to this field. > 1. Is this a new feature? > 2. For internal testing, what should be the right value for this field? > Screenshot is attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17174) Ambari 2.4 with HDF management Pack : Ranger Service Page : Domain Name(Only for AD)
[ https://issues.apache.org/jira/browse/AMBARI-17174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srimanth Gunturi updated AMBARI-17174: -- Attachment: Screen Shot 2016-05-18 at 11.21.48 PM.png > Ambari 2.4 with HDF management Pack : Ranger Service Page : Domain Name(Only > for AD) > > > Key: AMBARI-17174 > URL: https://issues.apache.org/jira/browse/AMBARI-17174 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Srimanth Gunturi >Assignee: Srimanth Gunturi > Fix For: 2.4.0 > > Attachments: Screen Shot 2016-05-18 at 11.21.48 PM.png > > > This Jira issue is for Ambari 2.4 with HDF management pack. > Please feel free to change to the right project/component. > While testing HDF 2.0 deployment using Ambari GUI, need to add Ranger service. > In the Customize Service page of Ranger, in the "Advance" tab of Ranger > Service, there is one mandatory field called "Domain Name(Only for AD)". > The GUI automation test breaks due to this field. > 1. Is this a new feature? > 2. For internal testing, what should be the right value for this field? > Screenshot is attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17174) Ambari 2.4 with HDF management Pack : Ranger Service Page : Domain Name(Only for AD)
Srimanth Gunturi created AMBARI-17174: - Summary: Ambari 2.4 with HDF management Pack : Ranger Service Page : Domain Name(Only for AD) Key: AMBARI-17174 URL: https://issues.apache.org/jira/browse/AMBARI-17174 Project: Ambari Issue Type: Bug Affects Versions: 2.4.0 Reporter: Srimanth Gunturi Assignee: Srimanth Gunturi Fix For: 2.4.0 This Jira issue is for Ambari 2.4 with HDF management pack. Please feel free to change to the right project/component. While testing HDF 2.0 deployment using Ambari GUI, need to add Ranger service. In the Customize Service page of Ranger, in the "Advance" tab of Ranger Service, there is one mandatory field called "Domain Name(Only for AD)". The GUI automation test breaks due to this field. 1. Is this a new feature? 2. For internal testing, what should be the right value for this field? Screenshot is attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (AMBARI-17113) Add user home directory verification as part of Service Check
[ https://issues.apache.org/jira/browse/AMBARI-17113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty reopened AMBARI-17113: > Add user home directory verification as part of Service Check > - > > Key: AMBARI-17113 > URL: https://issues.apache.org/jira/browse/AMBARI-17113 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Pallav Kulshreshtha >Assignee: Pallav Kulshreshtha > Fix For: 2.4.0 > > Attachments: AMBARI-17113_branch-2.4-2.patch > > > Add a check at the time of loading the view for presence of home directory > and provide error message if absent. Prompt the user to verify this before he > starts using this. Following views: > - Pig > - Hive -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17171) Falcon to create data-mirroring directory in HDFS if extensions is supported
[
https://issues.apache.org/jira/browse/AMBARI-17171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15325238#comment-15325238
]
Hadoop QA commented on AMBARI-17171:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12809525/AMBARI-17171.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:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7302//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7302//console
This message is automatically generated.
> Falcon to create data-mirroring directory in HDFS if extensions is supported
>
>
> Key: AMBARI-17171
> URL: https://issues.apache.org/jira/browse/AMBARI-17171
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.4.0
>Reporter: Murali Ramasami
>Assignee: Alejandro Fernandez
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-17171.branch-2.4.patch, AMBARI-17171.trunk.patch
>
>
> If Falcon extensions is supported, Ambari still needs to create the
> /apps/falcon/data-mirroring directory in HDFS.
> Also, RU/EU does not need to explicitly create the extensions directory in
> the pre_upgrade_restart function since the start function will create it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17054) Configure Atlas Ranger Plugin
[ https://issues.apache.org/jira/browse/AMBARI-17054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srimanth Gunturi updated AMBARI-17054: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed patches to trunk and branch-2.4 > Configure Atlas Ranger Plugin > - > > Key: AMBARI-17054 > URL: https://issues.apache.org/jira/browse/AMBARI-17054 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Gautam Borad >Assignee: Gautam Borad > Fix For: 2.4.0 > > Attachments: AMBARI-17054.1.patch, AMBARI-17054.2.patch, > AMBARI-17054.3.patch, AMBARI-17054_trunk.1.patch, AMBARI-17054_trunk.patch > > > Need to do following changes to support Ranger Atlas Plugin from Ambari: > 1) Check stack support and provide smart config section to Enable / disable > ranger atlas plugin > 2) Stack advisor changes to suggest recommended configs on enable / disable > plugin actions. > 3) Ranger service creation on Enable plugin action from Ambari. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17155) Accumulo Tracer principal causes OneFS permissions conflict
[
https://issues.apache.org/jira/browse/AMBARI-17155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Ketcherside updated AMBARI-17155:
Description:
The default principal for trace.user
{code:|borderStyle=solid}tracer-${cluster-name}@${realm}{code} causes Accumulo
Tracer to be unable to start once Kerberos is enabled in an environment where
the NameNode and DataNode are an EMC/Isilon OneFS cluster.
Unlike the Apache NameNode, OneFS doesn't have a user-defined auto_to_local
mapping for principals to local users. It just takes the root of the principal
and looks for a local user of the same name.
Tracer uses its upn in order to auth to hdfs and read the value of the file
within the "instance_id" directory, and the name of the directory within
"version" under apps/accumulo/data. If these steps fail, the component dies.
Currently Isilon is advising customers to switch the principal name to
{code:|borderStyle=solid}${accumulo-env/accumulo_user}@${realm}{code}. The
Accumulo user already has read access to the contents of the data directory.
(Hence, this issue is filed as minor; there is a work around.)
An admin could also resolve the permissions issue for the tracer principal by
giving o+r permissions recursively to the accumulo directory; or by creating a
tracer user, adding it to a group like hadoop, and changing group ownership of
the apps/accumulo direcotry to o+r recursively.
I'm filing this JIRA to ask for a resolution to be investigated on the Apache
side. Here are a few ideas, though they might not be valid courses of action:
- Use an Accumulo upn or spn for kerberized trace.user. SPN is indicated as
default in the Accumulo manual,
https://accumulo.apache.org/1.7/accumulo_user_manual#_kerberos .
- Have Accumulo Tracer check hdfs as a different principal.
- Remove Accumulo Tracer's requirement to read information from the file system
as a prerequisite to service start.
See
https://community.emc.com/community/products/isilon/blog/2016/06/03/onefs-ambari-and-accumulo-tracer
for more details.
was:
The default principal for trace.user (tracer-${cluster-name}@${realm}) causes
Accumulo Tracer to be unable to start once Kerberos is enabled in an
environment where the NameNode and DataNode are an EMC/Isilon OneFS cluster.
Unlike the Apache NameNode, OneFS doesn't have a user-defined auto_to_local
mapping for principals to local users. It just takes the root of the principal
and looks for a local user of the same name.
Tracer uses its upn in order to auth to hdfs and read the value of the file
within the "instance_id" directory, and the name of the directory within
"version" under apps/accumulo/data. If these steps fail, the component dies.
Currently Isilon is advising customers to switch the principal name to
${accumulo-env/accumulo_user}@${realm}. The Accumulo user already has read
access to the contents of the data directory. (Hence, this issue is filed as
minor; there is a work around.)
An admin could also resolve the permissions issue for the tracer principal by
giving o+r permissions recursively to the accumulo directory; or by creating a
tracer user, adding it to a group like hadoop, and changing group ownership of
the apps/accumulo direcotry to o+r recursively.
I'm filing this JIRA to ask for a resolution to be investigated on the Apache
side. Here are a few ideas, though they might not be valid courses of action:
- Use an Accumulo upn or spn for kerberized trace.user. SPN is indicated as
default in the Accumulo manual,
https://accumulo.apache.org/1.7/accumulo_user_manual#_kerberos .
- Have Accumulo Tracer check hdfs as a different principal.
- Remove Accumulo Tracer's requirement to read information from the file system
as a prerequisite to service start.
See
https://community.emc.com/community/products/isilon/blog/2016/06/03/onefs-ambari-and-accumulo-tracer
for more details.
> Accumulo Tracer principal causes OneFS permissions conflict
> ---
>
> Key: AMBARI-17155
> URL: https://issues.apache.org/jira/browse/AMBARI-17155
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
> Environment: Ambari 2.2.2, HDP 2.4.2, OneFS 8.0.0.1
>Reporter: Robert Ketcherside
>Priority: Minor
>
> The default principal for trace.user
> {code:|borderStyle=solid}tracer-${cluster-name}@${realm}{code} causes
> Accumulo Tracer to be unable to start once Kerberos is enabled in an
> environment where the NameNode and DataNode are an EMC/Isilon OneFS cluster.
> Unlike the Apache NameNode, OneFS doesn't have a user-defined auto_to_local
> mapping for principals to local users. It just takes the root of the
> principal and looks for a local user of the same name.
> Tracer uses its upn in order to auth to hdfs
[jira] [Commented] (AMBARI-17169) RBAC: Roles show "empty" group after delete
[
https://issues.apache.org/jira/browse/AMBARI-17169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15325207#comment-15325207
]
Hadoop QA commented on AMBARI-17169:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12809465/AMBARI-17169.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-admin.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7301//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7301//console
This message is automatically generated.
> RBAC: Roles show "empty" group after delete
> ---
>
> Key: AMBARI-17169
> URL: https://issues.apache.org/jira/browse/AMBARI-17169
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17169.patch
>
>
> 1. Created a group 'test'
> 2. set role to cluster admin
> 3. deleted group 'test'
> 4. when go to roles and see an "empty" space where the group was in the role.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (AMBARI-17173) Allow option to skip duplicate URL checking when creating VDF
[ https://issues.apache.org/jira/browse/AMBARI-17173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole resolved AMBARI-17173. Resolution: Fixed > Allow option to skip duplicate URL checking when creating VDF > - > > Key: AMBARI-17173 > URL: https://issues.apache.org/jira/browse/AMBARI-17173 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole > Fix For: 2.4.0 > > > When creating a VDF, it may be desirable to skip dupe base URL checking. > This is implemented as a Create Directive. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17165) Handle Java patches execution during Ranger upgrade
[
https://issues.apache.org/jira/browse/AMBARI-17165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15325184#comment-15325184
]
Hadoop QA commented on AMBARI-17165:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12809448/AMBARI-17165.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7300//console
This message is automatically generated.
> Handle Java patches execution during Ranger upgrade
> ---
>
> Key: AMBARI-17165
> URL: https://issues.apache.org/jira/browse/AMBARI-17165
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0, 2.2.2
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
> Fix For: 2.4.0
>
> Attachments: AMBARI-17165.patch
>
>
> Revisiting implementation of java patches during upgrade for Ranger Service
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17164) Handle Ranger upgrade scenario in Kerberized env
[
https://issues.apache.org/jira/browse/AMBARI-17164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15325181#comment-15325181
]
Hadoop QA commented on AMBARI-17164:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12809447/AMBARI-17164.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/7299//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7299//console
This message is automatically generated.
> Handle Ranger upgrade scenario in Kerberized env
>
>
> Key: AMBARI-17164
> URL: https://issues.apache.org/jira/browse/AMBARI-17164
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
> Fix For: 2.4.0
>
> Attachments: AMBARI-17164.patch
>
>
> Add this property to ranger-admin-site.xm:
> {code}
> ranger.plugins.{component}.serviceuser=service_user
> {code}
> Add spnego principal and keytab if cluster is kerberized to below properties:
> {code}
> ranger.spnego.kerberos.principal
> ranger.spnego.kerberos.keytab
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17149) HadoopTimelineMetricsSink from AMS prevents process shutdown
[ https://issues.apache.org/jira/browse/AMBARI-17149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15325178#comment-15325178 ] Hudson commented on AMBARI-17149: - FAILURE: Integrated in Ambari-trunk-Commit #5054 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5054/]) AMBARI-17149 : HadoopTimelineMetricsSink from AMS prevents HBase RS (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=c1789e2553862463d8864912f64afad71f9d792a]) * ambari-metrics/ambari-metrics-hadoop-sink/src/main/java/org/apache/hadoop/metrics2/sink/timeline/HadoopTimelineMetricsSink.java > HadoopTimelineMetricsSink from AMS prevents process shutdown > > > Key: AMBARI-17149 > URL: https://issues.apache.org/jira/browse/AMBARI-17149 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17149.patch > > > HadoopTimelineMetricsSink has and ExecutorService thread which is not a > daemon thread. The executor is not shutdown, and thread is not interrupted > while the sink stops. This causes region server process to hang although the > rest of the threads have all exited. > The new thread should be marked as a daemon thread, and also call shutdown() > or shutdownNow() on the executor in sink close. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Deleted] (AMBARI-17172) Kadmin operations can leak the admin password in ps output
[
https://issues.apache.org/jira/browse/AMBARI-17172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yusaku Sako deleted AMBARI-17172:
-
> Kadmin operations can leak the admin password in ps output
> --
>
> Key: AMBARI-17172
> URL: https://issues.apache.org/jira/browse/AMBARI-17172
> Project: Ambari
> Issue Type: Bug
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Labels: kerberos
>
> add_principal operations pass the password in the command line, so users on
> the system can run {{ps aux | grep kadmin}} and be able to see the admin
> users password in ps output. This can turn into a security issue that would
> allow non privileged users to obtain this password and use it to escalate
> their privileges.
> We need to find a way to prevent passing this password as a CLI option.
> *Solution*
> Pass the admin and user passwords to {{kadmin}} via the process's STDIN
> channel rather than the via the command line.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17172) Kadmin operations can leak the admin password in ps output
[
https://issues.apache.org/jira/browse/AMBARI-17172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-17172:
--
Attachment: AMBARI-17172_trunk_01.patch
AMBARI-17172_branch-2.4_01.patch
> Kadmin operations can leak the admin password in ps output
> --
>
> Key: AMBARI-17172
> URL: https://issues.apache.org/jira/browse/AMBARI-17172
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Labels: kerberos
> Fix For: 2.4.0
>
> Attachments: AMBARI-17172_branch-2.4_01.patch,
> AMBARI-17172_trunk_01.patch
>
>
> add_principal operations pass the password in the command line, so users on
> the system can run {{ps aux | grep kadmin}} and be able to see the admin
> users password in ps output. This can turn into a security issue that would
> allow non privileged users to obtain this password and use it to escalate
> their privileges.
> We need to find a way to prevent passing this password as a CLI option.
> *Solution*
> Pass the admin and user passwords to {{kadmin}} via the process's STDIN
> channel rather than the via the command line.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-17173) Allow option to skip duplicate URL checking when creating VDF
Nate Cole created AMBARI-17173: -- Summary: Allow option to skip duplicate URL checking when creating VDF Key: AMBARI-17173 URL: https://issues.apache.org/jira/browse/AMBARI-17173 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole Fix For: 2.4.0 When creating a VDF, it may be desirable to skip dupe base URL checking. This is implemented as a Create Directive. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17171) Falcon to create data-mirroring directory in HDFS if extensions is supported
[ https://issues.apache.org/jira/browse/AMBARI-17171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-17171: - Status: Patch Available (was: Open) > Falcon to create data-mirroring directory in HDFS if extensions is supported > > > Key: AMBARI-17171 > URL: https://issues.apache.org/jira/browse/AMBARI-17171 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: Murali Ramasami >Assignee: Alejandro Fernandez > Fix For: trunk, 2.4.0 > > Attachments: AMBARI-17171.branch-2.4.patch, AMBARI-17171.trunk.patch > > > If Falcon extensions is supported, Ambari still needs to create the > /apps/falcon/data-mirroring directory in HDFS. > Also, RU/EU does not need to explicitly create the extensions directory in > the pre_upgrade_restart function since the start function will create it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17172) Kadmin operations can leak the admin password in ps output
Robert Levas created AMBARI-17172:
-
Summary: Kadmin operations can leak the admin password in ps output
Key: AMBARI-17172
URL: https://issues.apache.org/jira/browse/AMBARI-17172
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.0.0
Reporter: Robert Levas
Assignee: Robert Levas
Priority: Critical
Fix For: 2.4.0
add_principal operations pass the password in the command line, so users on the
system can run {{ps aux | grep kadmin}} and be able to see the admin users
password in ps output. This can turn into a security issue that would allow non
privileged users to obtain this password and use it to escalate their
privileges.
We need to find a way to prevent passing this password as a CLI option.
*Solution*
Pass the admin and user passwords to {{kadmin}} via the process's STDIN channel
rather than the via the command line.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17171) Falcon to create data-mirroring directory in HDFS if extensions is supported
[ https://issues.apache.org/jira/browse/AMBARI-17171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-17171: - Attachment: AMBARI-17171.trunk.patch AMBARI-17171.branch-2.4.patch > Falcon to create data-mirroring directory in HDFS if extensions is supported > > > Key: AMBARI-17171 > URL: https://issues.apache.org/jira/browse/AMBARI-17171 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: Murali Ramasami >Assignee: Alejandro Fernandez > Fix For: trunk, 2.4.0 > > Attachments: AMBARI-17171.branch-2.4.patch, AMBARI-17171.trunk.patch > > > If Falcon extensions is supported, Ambari still needs to create the > /apps/falcon/data-mirroring directory in HDFS. > Also, RU/EU does not need to explicitly create the extensions directory in > the pre_upgrade_restart function since the start function will create it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17171) Falcon to create data-mirroring directory in HDFS if extensions is supported
[ https://issues.apache.org/jira/browse/AMBARI-17171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-17171: - Fix Version/s: trunk > Falcon to create data-mirroring directory in HDFS if extensions is supported > > > Key: AMBARI-17171 > URL: https://issues.apache.org/jira/browse/AMBARI-17171 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: Murali Ramasami >Assignee: Alejandro Fernandez > Fix For: trunk, 2.4.0 > > Attachments: AMBARI-17171.branch-2.4.patch, AMBARI-17171.trunk.patch > > > If Falcon extensions is supported, Ambari still needs to create the > /apps/falcon/data-mirroring directory in HDFS. > Also, RU/EU does not need to explicitly create the extensions directory in > the pre_upgrade_restart function since the start function will create it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17171) Falcon to create data-mirroring directory in HDFS if extensions is supported
Alejandro Fernandez created AMBARI-17171: Summary: Falcon to create data-mirroring directory in HDFS if extensions is supported Key: AMBARI-17171 URL: https://issues.apache.org/jira/browse/AMBARI-17171 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 2.4.0 Reporter: Murali Ramasami Assignee: Alejandro Fernandez Fix For: 2.4.0 If Falcon extensions is supported, Ambari still needs to create the /apps/falcon/data-mirroring directory in HDFS. Also, RU/EU does not need to explicitly create the extensions directory in the pre_upgrade_restart function since the start function will create it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16998) Fix intermittent unit test failure in TestMpacks
[
https://issues.apache.org/jira/browse/AMBARI-16998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15324977#comment-15324977
]
Aravindan Vijayan commented on AMBARI-16998:
+1
> Fix intermittent unit test failure in TestMpacks
>
>
> Key: AMBARI-16998
> URL: https://issues.apache.org/jira/browse/AMBARI-16998
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-16998.patch
>
>
> {code}
> Running tests for ambari-server
> Traceback (most recent call last):
> File "unitTests.py", line 298, in
> sys.exit(main())
> File "unitTests.py", line 250, in main
> File ambari.properties not found in search path $AMBARI_CONF_DIR:
> /etc/ambari-server/conf
> suites = [unittest.defaultTestLoader.loadTestsFromName(name) for name in
> modules]
> File "/usr/lib/python2.7/unittest/loader.py", line 91, in loadTestsFromName
> module = __import__('.'.join(parts_copy))
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/test/python/TestMpacks.py",
> line 21, in
> from ambari_server.setupMpacks import install_mpack, upgrade_mpack,
> replay_mpack_logs, purge_stacks_and_mpacks, \
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/setupMpacks.py",
> line 31, in
> from ambari_server.serverConfiguration import get_ambari_properties,
> get_ambari_version, get_stack_location, \
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverConfiguration.py",
> line 537, in
> configDefaults = ServerConfigDefaults()
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverConfiguration.py",
> line 456, in __init__
> super(ServerConfigDefaultsLinux, self).__init__()
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverConfiguration.py",
> line 327, in __init__
> properties = get_ambari_properties()
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverConfiguration.py",
> line 225, in get_ambari_properties
> conf_file = find_properties_file()
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverConfiguration.py",
> line 218, in find_properties_file
> raise FatalException(1, err)
> ambari_commons.exceptions.FatalException: 'Fatal exception: File
> ambari.properties not found in search path $AMBARI_CONF_DIR:
> /etc/ambari-server/conf, exit code 1'
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17151) Blueprint deployments fail when services manually removed from stack definitions
[
https://issues.apache.org/jira/browse/AMBARI-17151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15324961#comment-15324961
]
Hadoop QA commented on AMBARI-17151:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12809453/AMBARI-17151.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:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.controller.internal.ConfigGroupResourceProviderTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7298//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7298//console
This message is automatically generated.
> Blueprint deployments fail when services manually removed from stack
> definitions
>
>
> Key: AMBARI-17151
> URL: https://issues.apache.org/jira/browse/AMBARI-17151
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Nettleton
>Assignee: Robert Nettleton
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17151.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> In certain custom use cases, an Ambari user may choose to customize the
> Ambari stack definitions by manually removing services.
> This can cause some failures during a Blueprint deployment, particularly in
> the area of "excluded" configurations.
> When an "excluded" configuration type is found, the Blueprint processor
> attempts to add this configuration, and queries the Stack APIs to determine
> the service associated with this configuration type.
> If this particular service has been manually deleted from the stacks, the
> Stack APIs will throw a runtime exception, which causes the entire Blueprint
> deployment to fail.
> Example:
> If Ambari Metrics is included in a Blueprint, the "storm-site" configuration
> type is considered an "excluded-configuration" by the stack definitions. In
> this case, if the "STORM" service definitions have been removed, then the
> following exception will result when a cluster deployment based on a
> Blueprint is attempted:
> java.lang.IllegalArgumentException: Specified configuration type is not
> associated with any service: storm-site
> at
> org.apache.ambari.server.controller.internal.Stack.getServiceForConfigType(Stack.java:485)
> at
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.addExcludedConfigProperties(BlueprintConfigurationProcessor.java:2781)
> at
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.setMissingConfigurations(BlueprintConfigurationProcessor.java:2751)
> at
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doUpdateForClusterCreate(BlueprintConfigurationProcessor.java:335)
> at
> org.apache.ambari.server.topology.ClusterConfigurationRequest.process(ClusterConfigurationRequest.java:153)
> at
> org.apache.ambari.server.topology.TopologyManager$ConfigureClusterTask.call(TopologyManager.java:780)
> at
> org.apache.ambari.server.topology.TopologyManager$ConfigureClusterTask.call(TopologyManager.java:754)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> ...
> In these custom deployments, the Blueprints processor should be more lenient
> with respect to error handling.
> If a matching service is not found for a given "excluded" configuration type,
> the Blueprint processor should log this as a WARNING, indicating that the
> stacks have likely been modified outside of Ambari.
> I'm working on a fix for this, and will be submitting a patch soon.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17168) Kerberization of a cluster deletes ATS service
[ https://issues.apache.org/jira/browse/AMBARI-17168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15324953#comment-15324953 ] Hudson commented on AMBARI-17168: - FAILURE: Integrated in Ambari-trunk-Commit #5053 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5053/]) AMBARI-17168 Kerberization of a cluster deletes ATS service (dsen) (dsen: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e9270ab75bc8b514703138b1d2ab70894de1905a]) * ambari-server/src/main/resources/stacks/HDP/2.3/services/YARN/metainfo.xml > Kerberization of a cluster deletes ATS service > -- > > Key: AMBARI-17168 > URL: https://issues.apache.org/jira/browse/AMBARI-17168 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17168.patch > > > Its likely because APP_TIMELINE_SERVER component (due to AMBARI-17111) become > an optional component. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17166) Atlas Integration : HBase table name 'titan' to be configurable via Atlas properties
[ https://issues.apache.org/jira/browse/AMBARI-17166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15324954#comment-15324954 ] Hudson commented on AMBARI-17166: - FAILURE: Integrated in Ambari-trunk-Commit #5053 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5053/]) AMBARI-17166 - Atlas Integration : HBase table name 'titan' to be (tbeerbower: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=08f1365a470b1bf508c82fb6ec77641f5bbdcb7e]) * ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/configuration/atlas-log4j.xml * ambari-server/src/main/resources/stacks/HDP/2.5/services/ATLAS/configuration/application-properties.xml > Atlas Integration : HBase table name 'titan' to be configurable via Atlas > properties > > > Key: AMBARI-17166 > URL: https://issues.apache.org/jira/browse/AMBARI-17166 > Project: Ambari > Issue Type: Bug >Reporter: Tom Beerbower >Assignee: Tom Beerbower > > Currently Atlas Hbase table name is 'titan' and there is no option to > configure the table name. > We can add a property in Atlas advanced configuration on Ambari UI to specify > the table name. > The following property in atlas-application.properties allows us to configure > Hbase table name > atlas.graph.storage.hbase.table : "atlas_titan" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17141) "Settings" button shown to cluster administrator
[ https://issues.apache.org/jira/browse/AMBARI-17141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15324952#comment-15324952 ] Hudson commented on AMBARI-17141: - FAILURE: Integrated in Ambari-trunk-Commit #5053 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5053/]) AMBARI-17141 "Settings" button shown to cluster administrator, second (atkach: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=adb1ca4509f6fe15ec3f8cbd04842ebb58aca5ff]) * ambari-web/app/utils/host_progress_popup.js * ambari-web/app/templates/common/modal_popup.hbs * ambari-web/app/templates/common/host_progress_popup_footer.hbs > "Settings" button shown to cluster administrator > > > Key: AMBARI-17141 > URL: https://issues.apache.org/jira/browse/AMBARI-17141 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17141.patch, AMBARI-17141_2.patch, Ambari - > Dropdown Menu.png, Screen Shot 2016-06-08 at 11.04.03 AM.png > > > The button "Settings" in the drop down of the "admin" tab in ambari shouldn't > be shown for cluster administrator. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16998) Fix intermittent unit test failure in TestMpacks
[
https://issues.apache.org/jira/browse/AMBARI-16998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15324939#comment-15324939
]
Jayush Luniya commented on AMBARI-16998:
mvn clean test -DskipSurefireTests
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 1:03.505s
[INFO] Finished at: Fri Jun 10 10:44:09 PDT 2016
[INFO] Final Memory: 63M/1333M
[INFO]
> Fix intermittent unit test failure in TestMpacks
>
>
> Key: AMBARI-16998
> URL: https://issues.apache.org/jira/browse/AMBARI-16998
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-16998.patch
>
>
> {code}
> Running tests for ambari-server
> Traceback (most recent call last):
> File "unitTests.py", line 298, in
> sys.exit(main())
> File "unitTests.py", line 250, in main
> File ambari.properties not found in search path $AMBARI_CONF_DIR:
> /etc/ambari-server/conf
> suites = [unittest.defaultTestLoader.loadTestsFromName(name) for name in
> modules]
> File "/usr/lib/python2.7/unittest/loader.py", line 91, in loadTestsFromName
> module = __import__('.'.join(parts_copy))
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/test/python/TestMpacks.py",
> line 21, in
> from ambari_server.setupMpacks import install_mpack, upgrade_mpack,
> replay_mpack_logs, purge_stacks_and_mpacks, \
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/setupMpacks.py",
> line 31, in
> from ambari_server.serverConfiguration import get_ambari_properties,
> get_ambari_version, get_stack_location, \
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverConfiguration.py",
> line 537, in
> configDefaults = ServerConfigDefaults()
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverConfiguration.py",
> line 456, in __init__
> super(ServerConfigDefaultsLinux, self).__init__()
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverConfiguration.py",
> line 327, in __init__
> properties = get_ambari_properties()
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverConfiguration.py",
> line 225, in get_ambari_properties
> conf_file = find_properties_file()
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverConfiguration.py",
> line 218, in find_properties_file
> raise FatalException(1, err)
> ambari_commons.exceptions.FatalException: 'Fatal exception: File
> ambari.properties not found in search path $AMBARI_CONF_DIR:
> /etc/ambari-server/conf, exit code 1'
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-16998) Fix intermittent unit test failure in TestMpacks
[
https://issues.apache.org/jira/browse/AMBARI-16998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15324930#comment-15324930
]
Jayush Luniya commented on AMBARI-16998:
Verified
Running tests for ambari-server
/Users/jluniya/trunk/ambari/ambari-common/src/main/python/ambari_jinja2/ambari_jinja2/__init__.py:32:
UserWarning: Unbuilt egg for wsgiref [unknown version]
(/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7)
.get_distribution('Jinja2').version
test_install_addon_service_mpack (TestMpacks.TestMpacks) ... ok
test_install_mpack_with_invalid_mpack_path (TestMpacks.TestMpacks) ... ok
test_install_mpack_with_malformed_mpack (TestMpacks.TestMpacks) ... ok
test_install_mpack_with_no_mpack_path (TestMpacks.TestMpacks) ... ok
test_install_stack_mpack (TestMpacks.TestMpacks) ... ok
test_purge_stacks_and_mpacks (TestMpacks.TestMpacks) ... ok
test_replay_mpack_logs (TestMpacks.TestMpacks) ... ok
test_upgrade_stack_mpack (TestMpacks.TestMpacks) ... ok
> Fix intermittent unit test failure in TestMpacks
>
>
> Key: AMBARI-16998
> URL: https://issues.apache.org/jira/browse/AMBARI-16998
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-16998.patch
>
>
> {code}
> Running tests for ambari-server
> Traceback (most recent call last):
> File "unitTests.py", line 298, in
> sys.exit(main())
> File "unitTests.py", line 250, in main
> File ambari.properties not found in search path $AMBARI_CONF_DIR:
> /etc/ambari-server/conf
> suites = [unittest.defaultTestLoader.loadTestsFromName(name) for name in
> modules]
> File "/usr/lib/python2.7/unittest/loader.py", line 91, in loadTestsFromName
> module = __import__('.'.join(parts_copy))
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/test/python/TestMpacks.py",
> line 21, in
> from ambari_server.setupMpacks import install_mpack, upgrade_mpack,
> replay_mpack_logs, purge_stacks_and_mpacks, \
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/setupMpacks.py",
> line 31, in
> from ambari_server.serverConfiguration import get_ambari_properties,
> get_ambari_version, get_stack_location, \
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverConfiguration.py",
> line 537, in
> configDefaults = ServerConfigDefaults()
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverConfiguration.py",
> line 456, in __init__
> super(ServerConfigDefaultsLinux, self).__init__()
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverConfiguration.py",
> line 327, in __init__
> properties = get_ambari_properties()
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverConfiguration.py",
> line 225, in get_ambari_properties
> conf_file = find_properties_file()
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverConfiguration.py",
> line 218, in find_properties_file
> raise FatalException(1, err)
> ambari_commons.exceptions.FatalException: 'Fatal exception: File
> ambari.properties not found in search path $AMBARI_CONF_DIR:
> /etc/ambari-server/conf, exit code 1'
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16998) Fix intermittent unit test failure in TestMpacks
[
https://issues.apache.org/jira/browse/AMBARI-16998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-16998:
---
Status: Patch Available (was: In Progress)
> Fix intermittent unit test failure in TestMpacks
>
>
> Key: AMBARI-16998
> URL: https://issues.apache.org/jira/browse/AMBARI-16998
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-16998.patch
>
>
> {code}
> Running tests for ambari-server
> Traceback (most recent call last):
> File "unitTests.py", line 298, in
> sys.exit(main())
> File "unitTests.py", line 250, in main
> File ambari.properties not found in search path $AMBARI_CONF_DIR:
> /etc/ambari-server/conf
> suites = [unittest.defaultTestLoader.loadTestsFromName(name) for name in
> modules]
> File "/usr/lib/python2.7/unittest/loader.py", line 91, in loadTestsFromName
> module = __import__('.'.join(parts_copy))
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/test/python/TestMpacks.py",
> line 21, in
> from ambari_server.setupMpacks import install_mpack, upgrade_mpack,
> replay_mpack_logs, purge_stacks_and_mpacks, \
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/setupMpacks.py",
> line 31, in
> from ambari_server.serverConfiguration import get_ambari_properties,
> get_ambari_version, get_stack_location, \
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverConfiguration.py",
> line 537, in
> configDefaults = ServerConfigDefaults()
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverConfiguration.py",
> line 456, in __init__
> super(ServerConfigDefaultsLinux, self).__init__()
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverConfiguration.py",
> line 327, in __init__
> properties = get_ambari_properties()
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverConfiguration.py",
> line 225, in get_ambari_properties
> conf_file = find_properties_file()
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverConfiguration.py",
> line 218, in find_properties_file
> raise FatalException(1, err)
> ambari_commons.exceptions.FatalException: 'Fatal exception: File
> ambari.properties not found in search path $AMBARI_CONF_DIR:
> /etc/ambari-server/conf, exit code 1'
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16998) Fix intermittent unit test failure in TestMpacks
[
https://issues.apache.org/jira/browse/AMBARI-16998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-16998:
---
Attachment: AMBARI-16998.patch
> Fix intermittent unit test failure in TestMpacks
>
>
> Key: AMBARI-16998
> URL: https://issues.apache.org/jira/browse/AMBARI-16998
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-16998.patch
>
>
> {code}
> Running tests for ambari-server
> Traceback (most recent call last):
> File "unitTests.py", line 298, in
> sys.exit(main())
> File "unitTests.py", line 250, in main
> File ambari.properties not found in search path $AMBARI_CONF_DIR:
> /etc/ambari-server/conf
> suites = [unittest.defaultTestLoader.loadTestsFromName(name) for name in
> modules]
> File "/usr/lib/python2.7/unittest/loader.py", line 91, in loadTestsFromName
> module = __import__('.'.join(parts_copy))
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/test/python/TestMpacks.py",
> line 21, in
> from ambari_server.setupMpacks import install_mpack, upgrade_mpack,
> replay_mpack_logs, purge_stacks_and_mpacks, \
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/setupMpacks.py",
> line 31, in
> from ambari_server.serverConfiguration import get_ambari_properties,
> get_ambari_version, get_stack_location, \
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverConfiguration.py",
> line 537, in
> configDefaults = ServerConfigDefaults()
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverConfiguration.py",
> line 456, in __init__
> super(ServerConfigDefaultsLinux, self).__init__()
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverConfiguration.py",
> line 327, in __init__
> properties = get_ambari_properties()
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverConfiguration.py",
> line 225, in get_ambari_properties
> conf_file = find_properties_file()
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverConfiguration.py",
> line 218, in find_properties_file
> raise FatalException(1, err)
> ambari_commons.exceptions.FatalException: 'Fatal exception: File
> ambari.properties not found in search path $AMBARI_CONF_DIR:
> /etc/ambari-server/conf, exit code 1'
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16998) Fix intermittent unit test failure in TestMpacks
[
https://issues.apache.org/jira/browse/AMBARI-16998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-16998:
---
Attachment: (was: AMBARI-16998.patch)
> Fix intermittent unit test failure in TestMpacks
>
>
> Key: AMBARI-16998
> URL: https://issues.apache.org/jira/browse/AMBARI-16998
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.4.0
>
>
> {code}
> Running tests for ambari-server
> Traceback (most recent call last):
> File "unitTests.py", line 298, in
> sys.exit(main())
> File "unitTests.py", line 250, in main
> File ambari.properties not found in search path $AMBARI_CONF_DIR:
> /etc/ambari-server/conf
> suites = [unittest.defaultTestLoader.loadTestsFromName(name) for name in
> modules]
> File "/usr/lib/python2.7/unittest/loader.py", line 91, in loadTestsFromName
> module = __import__('.'.join(parts_copy))
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/test/python/TestMpacks.py",
> line 21, in
> from ambari_server.setupMpacks import install_mpack, upgrade_mpack,
> replay_mpack_logs, purge_stacks_and_mpacks, \
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/setupMpacks.py",
> line 31, in
> from ambari_server.serverConfiguration import get_ambari_properties,
> get_ambari_version, get_stack_location, \
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverConfiguration.py",
> line 537, in
> configDefaults = ServerConfigDefaults()
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverConfiguration.py",
> line 456, in __init__
> super(ServerConfigDefaultsLinux, self).__init__()
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverConfiguration.py",
> line 327, in __init__
> properties = get_ambari_properties()
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverConfiguration.py",
> line 225, in get_ambari_properties
> conf_file = find_properties_file()
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverConfiguration.py",
> line 218, in find_properties_file
> raise FatalException(1, err)
> ambari_commons.exceptions.FatalException: 'Fatal exception: File
> ambari.properties not found in search path $AMBARI_CONF_DIR:
> /etc/ambari-server/conf, exit code 1'
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16998) Fix intermittent unit test failure in TestMpacks
[
https://issues.apache.org/jira/browse/AMBARI-16998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-16998:
---
Status: Open (was: Patch Available)
> Fix intermittent unit test failure in TestMpacks
>
>
> Key: AMBARI-16998
> URL: https://issues.apache.org/jira/browse/AMBARI-16998
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.4.0
>
>
> {code}
> Running tests for ambari-server
> Traceback (most recent call last):
> File "unitTests.py", line 298, in
> sys.exit(main())
> File "unitTests.py", line 250, in main
> File ambari.properties not found in search path $AMBARI_CONF_DIR:
> /etc/ambari-server/conf
> suites = [unittest.defaultTestLoader.loadTestsFromName(name) for name in
> modules]
> File "/usr/lib/python2.7/unittest/loader.py", line 91, in loadTestsFromName
> module = __import__('.'.join(parts_copy))
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/test/python/TestMpacks.py",
> line 21, in
> from ambari_server.setupMpacks import install_mpack, upgrade_mpack,
> replay_mpack_logs, purge_stacks_and_mpacks, \
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/setupMpacks.py",
> line 31, in
> from ambari_server.serverConfiguration import get_ambari_properties,
> get_ambari_version, get_stack_location, \
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverConfiguration.py",
> line 537, in
> configDefaults = ServerConfigDefaults()
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverConfiguration.py",
> line 456, in __init__
> super(ServerConfigDefaultsLinux, self).__init__()
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverConfiguration.py",
> line 327, in __init__
> properties = get_ambari_properties()
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverConfiguration.py",
> line 225, in get_ambari_properties
> conf_file = find_properties_file()
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverConfiguration.py",
> line 218, in find_properties_file
> raise FatalException(1, err)
> ambari_commons.exceptions.FatalException: 'Fatal exception: File
> ambari.properties not found in search path $AMBARI_CONF_DIR:
> /etc/ambari-server/conf, exit code 1'
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15659) HortonWorks Zeppelin SUSE Install issue in HDP 2.4
[ https://issues.apache.org/jira/browse/AMBARI-15659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15324898#comment-15324898 ] Ali Bajwa commented on AMBARI-15659: Sorry missed this earlier. Seems like suse11 package dependencies were listed twice and seems wrong one was picked up. Have fixed this now https://github.com/hortonworks-gallery/ambari-zeppelin-service/commit/8d5ce600bf8f22c71a041b3cf80732734affb57e These are the only packages that should be picked up now for SuSe11: https://github.com/hortonworks-gallery/ambari-zeppelin-service/blob/master/metainfo.xml#L97-L116 [~jaromir.martina...@teradata.com] if you replace the contents of the updated metainfo.xml above, and restart ambari-server, it should be able to pick up correct package name on install > HortonWorks Zeppelin SUSE Install issue in HDP 2.4 > -- > > Key: AMBARI-15659 > URL: https://issues.apache.org/jira/browse/AMBARI-15659 > Project: Ambari > Issue Type: Bug > Environment: SLES11 SP4 >Reporter: Arun Singh > > Issue 2: Zeppelin. Zeppelin is a new component in Tech Preview in the latest > HDP stack (2.4). I've been following this guide: > http://hortonworks.com/hadoop-tutorial/apache-zeppelin-hdp-2-4/ >When installing Zeppelin through the Ambari interface, it errors out with > a message saying it can't install the package gcc-gfortran > >If you open the file: > /var/lib/ambari-server/resources/stacks/HDP/2.4/services/ZEPPELIN/metainfo.xml > > Line 72: > > redhat7,redhat6,redhat5,suse11 > > > gcc-gfortran > > > blas-devel > > > lapack-devel > > > python-devel > > > python-pip > > > zeppelin > > > > This list packages to install on SUSE11, but you don't find these packages on > SUSE11 as they have different names than the RHEL ones... > Eg: > RHEL: gcc-gfortran > SUSE: gcc-fortran > RHEL: blas-devel > SUSE: libblas3 ? > RHEL: lapack-devel > SUSE: liblapack3 ? > RHEL: python-dev > SUSE: python-devel > RHEL: python-pip > SUSE: doesn't seem to be part of the standard repo > Solution: Make a custom for SUSE 11, with the > correct named packages as they are named on SUSE 11 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16220) No INSTALL commands
[ https://issues.apache.org/jira/browse/AMBARI-16220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Magyari updated AMBARI-16220: Attachment: AMBARI-16220.patch > No INSTALL commands > --- > > Key: AMBARI-16220 > URL: https://issues.apache.org/jira/browse/AMBARI-16220 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Sebastian Toader >Assignee: Sandor Magyari > Fix For: 2.5.0 > > Attachments: AMBARI-16220.patch > > > In case packages.pre.installed=true is set in ambari.properties, Blueprint > based deployments will not create INSTALL commands for service components. > Normally START command should call configure, but we must ensure this is true > for all used components. For client components INSTALL will be still > generated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16220) No INSTALL commands
[ https://issues.apache.org/jira/browse/AMBARI-16220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Magyari updated AMBARI-16220: Status: Patch Available (was: Open) > No INSTALL commands > --- > > Key: AMBARI-16220 > URL: https://issues.apache.org/jira/browse/AMBARI-16220 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Sebastian Toader >Assignee: Sandor Magyari > Fix For: 2.5.0 > > Attachments: AMBARI-16220.patch > > > In case packages.pre.installed=true is set in ambari.properties, Blueprint > based deployments will not create INSTALL commands for service components. > Normally START command should call configure, but we must ensure this is true > for all used components. For client components INSTALL will be still > generated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17149) HadoopTimelineMetricsSink from AMS prevents process shutdown
[ https://issues.apache.org/jira/browse/AMBARI-17149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-17149: --- Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to trunk and branch-2.4 > HadoopTimelineMetricsSink from AMS prevents process shutdown > > > Key: AMBARI-17149 > URL: https://issues.apache.org/jira/browse/AMBARI-17149 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17149.patch > > > HadoopTimelineMetricsSink has and ExecutorService thread which is not a > daemon thread. The executor is not shutdown, and thread is not interrupted > while the sink stops. This causes region server process to hang although the > rest of the threads have all exited. > The new thread should be marked as a daemon thread, and also call shutdown() > or shutdownNow() on the executor in sink close. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17118) Incorrect formated external url in ranger configuration - causes Namenode startup failure
[
https://issues.apache.org/jira/browse/AMBARI-17118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15324699#comment-15324699
]
Hadoop QA commented on AMBARI-17118:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12809455/AMBARI-17118.1.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/7297//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7297//console
This message is automatically generated.
> Incorrect formated external url in ranger configuration - causes Namenode
> startup failure
> -
>
> Key: AMBARI-17118
> URL: https://issues.apache.org/jira/browse/AMBARI-17118
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.1.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
> Fix For: 2.4.0
>
> Attachments: AMBARI-17118.1.patch, AMBARI-17118.patch
>
>
> STR:
> 1. install ambari and HDP with HDFS,YARN,HIVE
> 2. install ranger and configure *External URL*
> https://c6401.ambari.apache.org:6182/ ( means slash at the end of the URL
> which is allowed without any problem and installation is done successfully)
> 3. enable ranger plugin in hdfs config and restart it
> Result: NN startup fails and even after failure , error message in stack
> trace is confusing
> ERROR:
> ==
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/ranger_functions.py",
> line 108, in create_ranger_repository
> raise Fail('Ambari admin username and password are blank ')
> resource_management.core.exceptions.Fail: Ambari admin username and password
> are blank
> but actual reason is a slash at the end of the External URL,
> it fails the following point in
> usr/lib/python2.6/site-packages/resource_management/libraries/functions/ranger_functions.py:
> result = urllib2.urlopen(request)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16220) No INSTALL commands
[ https://issues.apache.org/jira/browse/AMBARI-16220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-16220: -- Fix Version/s: (was: 2.4.1) 2.5.0 > No INSTALL commands > --- > > Key: AMBARI-16220 > URL: https://issues.apache.org/jira/browse/AMBARI-16220 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Sebastian Toader >Assignee: Sandor Magyari > Fix For: 2.5.0 > > > In case packages.pre.installed=true is set in ambari.properties, Blueprint > based deployments will not create INSTALL commands for service components. > Normally START command should call configure, but we must ensure this is true > for all used components. For client components INSTALL will be still > generated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16220) No INSTALL commands
[ https://issues.apache.org/jira/browse/AMBARI-16220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Magyari updated AMBARI-16220: Description: In case packages.pre.installed=true is set in ambari.properties, Blueprint based deployments will not create INSTALL commands for service components. Normally START command should call configure, but we must ensure this is true for all used components. For client components INSTALL will be still generated. (was: Get rid of install commands. Currently, install commands are needed for two purposes: * Satisfy the state transition requirements * Install clients (HDFS_CLIENT, HIVE_CLIENT, etc) The first one is a simpler where the server can help auto transition to INSTALLED and then issue START. The second one will require either issue INSTALL command only for Client components or create a CONFIGURE command that does the same for the Client components that can precede the Start commands. It can go in as a stage in for the START tasks themselves.) > No INSTALL commands > --- > > Key: AMBARI-16220 > URL: https://issues.apache.org/jira/browse/AMBARI-16220 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Sebastian Toader >Assignee: Sandor Magyari > Fix For: 2.4.1 > > > In case packages.pre.installed=true is set in ambari.properties, Blueprint > based deployments will not create INSTALL commands for service components. > Normally START command should call configure, but we must ensure this is true > for all used components. For client components INSTALL will be still > generated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17162) View config- Allows remote cluster creation using a user having no permissions on the cluster
[
https://issues.apache.org/jira/browse/AMBARI-17162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15324660#comment-15324660
]
Hadoop QA commented on AMBARI-17162:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12809444/AMBARI-17162_branch-2.4.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/7296//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7296//console
This message is automatically generated.
> View config- Allows remote cluster creation using a user having no
> permissions on the cluster
> -
>
> Key: AMBARI-17162
> URL: https://issues.apache.org/jira/browse/AMBARI-17162
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.4.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: AMBARI-17162_branch-2.4.patch
>
>
> Created a user with no permission on cluster 'viewUser' on Remote Cluster.
> On View server, created remote cluster with the above user credentials
> Result:
> Remote cluster get created.
> Expected: remote cluster should only be created with cluster/ambari admin
> user credential.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17168) Kerberization of a cluster deletes ATS service
[ https://issues.apache.org/jira/browse/AMBARI-17168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-17168: Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.4 > Kerberization of a cluster deletes ATS service > -- > > Key: AMBARI-17168 > URL: https://issues.apache.org/jira/browse/AMBARI-17168 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17168.patch > > > Its likely because APP_TIMELINE_SERVER component (due to AMBARI-17111) become > an optional component. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17160) Extra spinner on assign masters
[ https://issues.apache.org/jira/browse/AMBARI-17160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15324621#comment-15324621 ] Oleg Nechiporenko commented on AMBARI-17160: Patch was already committed > Extra spinner on assign masters > --- > > Key: AMBARI-17160 > URL: https://issues.apache.org/jira/browse/AMBARI-17160 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 2.4.0 > > Attachments: AMBARI-17160.patch, Screen Shot 2016-06-08 at 7.05.04 > AM.png > > > Looks like the other parts of the wizard include spinner in the button (looks > good). But on the Assign Master step, it also have spinner to left, which > seems unnecessary. > See attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17169) RBAC: Roles show "empty" group after delete
[ https://issues.apache.org/jira/browse/AMBARI-17169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-17169: - Status: Patch Available (was: Open) > RBAC: Roles show "empty" group after delete > --- > > Key: AMBARI-17169 > URL: https://issues.apache.org/jira/browse/AMBARI-17169 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17169.patch > > > 1. Created a group 'test' > 2. set role to cluster admin > 3. deleted group 'test' > 4. when go to roles and see an "empty" space where the group was in the role. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17167) Atlas Integration : Excessive logs: default log level should be set to 'info'; currently it is 'debug'
[ https://issues.apache.org/jira/browse/AMBARI-17167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Beerbower updated AMBARI-17167: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Atlas Integration : Excessive logs: default log level should be set to > 'info'; currently it is 'debug' > -- > > Key: AMBARI-17167 > URL: https://issues.apache.org/jira/browse/AMBARI-17167 > Project: Ambari > Issue Type: Bug >Reporter: Tom Beerbower >Assignee: Tom Beerbower > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17166) Atlas Integration : HBase table name 'titan' to be configurable via Atlas properties
[ https://issues.apache.org/jira/browse/AMBARI-17166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Beerbower updated AMBARI-17166: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Atlas Integration : HBase table name 'titan' to be configurable via Atlas > properties > > > Key: AMBARI-17166 > URL: https://issues.apache.org/jira/browse/AMBARI-17166 > Project: Ambari > Issue Type: Bug >Reporter: Tom Beerbower >Assignee: Tom Beerbower > > Currently Atlas Hbase table name is 'titan' and there is no option to > configure the table name. > We can add a property in Atlas advanced configuration on Ambari UI to specify > the table name. > The following property in atlas-application.properties allows us to configure > Hbase table name > atlas.graph.storage.hbase.table : "atlas_titan" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17169) RBAC: Roles show "empty" group after delete
[ https://issues.apache.org/jira/browse/AMBARI-17169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15324571#comment-15324571 ] Andrii Tkach commented on AMBARI-17169: --- +1 for the patch > RBAC: Roles show "empty" group after delete > --- > > Key: AMBARI-17169 > URL: https://issues.apache.org/jira/browse/AMBARI-17169 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17169.patch > > > 1. Created a group 'test' > 2. set role to cluster admin > 3. deleted group 'test' > 4. when go to roles and see an "empty" space where the group was in the role. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17170) Logfeeder should read every ambari logs with non-root user
Olivér Szabó created AMBARI-17170: - Summary: Logfeeder should read every ambari logs with non-root user Key: AMBARI-17170 URL: https://issues.apache.org/jira/browse/AMBARI-17170 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.4.1 ambari logs generated with ambari-server user / ambari-server group permissions. In case of non-root ambari server installs, ambari-server user should be in Hadoop service group, although that happens, most of the logs still in ambari-server group (not in hadoop), so does not matter logfeeder and ambari-server on the same group, if the ambari server log files are not in the common hadoop group -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17169) RBAC: Roles show "empty" group after delete
[ https://issues.apache.org/jira/browse/AMBARI-17169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-17169: - Attachment: AMBARI-17169.patch > RBAC: Roles show "empty" group after delete > --- > > Key: AMBARI-17169 > URL: https://issues.apache.org/jira/browse/AMBARI-17169 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17169.patch > > > 1. Created a group 'test' > 2. set role to cluster admin > 3. deleted group 'test' > 4. when go to roles and see an "empty" space where the group was in the role. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17169) RBAC: Roles show "empty" group after delete
[ https://issues.apache.org/jira/browse/AMBARI-17169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-17169: - Fix Version/s: 2.4.0 > RBAC: Roles show "empty" group after delete > --- > > Key: AMBARI-17169 > URL: https://issues.apache.org/jira/browse/AMBARI-17169 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.4.0 > > > 1. Created a group 'test' > 2. set role to cluster admin > 3. deleted group 'test' > 4. when go to roles and see an "empty" space where the group was in the role. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17169) RBAC: Roles show "empty" group after delete
Aleksandr Kovalenko created AMBARI-17169: Summary: RBAC: Roles show "empty" group after delete Key: AMBARI-17169 URL: https://issues.apache.org/jira/browse/AMBARI-17169 Project: Ambari Issue Type: Bug Components: ambari-web Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Priority: Critical 1. Created a group 'test' 2. set role to cluster admin 3. deleted group 'test' 4. when go to roles and see an "empty" space where the group was in the role. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17169) RBAC: Roles show "empty" group after delete
[ https://issues.apache.org/jira/browse/AMBARI-17169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-17169: - Affects Version/s: 2.4.0 > RBAC: Roles show "empty" group after delete > --- > > Key: AMBARI-17169 > URL: https://issues.apache.org/jira/browse/AMBARI-17169 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.4.0 > > > 1. Created a group 'test' > 2. set role to cluster admin > 3. deleted group 'test' > 4. when go to roles and see an "empty" space where the group was in the role. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17168) Kerberization of a cluster deletes ATS service
[ https://issues.apache.org/jira/browse/AMBARI-17168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-17168: Status: Patch Available (was: Open) > Kerberization of a cluster deletes ATS service > -- > > Key: AMBARI-17168 > URL: https://issues.apache.org/jira/browse/AMBARI-17168 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17168.patch > > > Its likely because APP_TIMELINE_SERVER component (due to AMBARI-17111) become > an optional component. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17168) Kerberization of a cluster deletes ATS service
[ https://issues.apache.org/jira/browse/AMBARI-17168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-17168: Attachment: AMBARI-17168.patch > Kerberization of a cluster deletes ATS service > -- > > Key: AMBARI-17168 > URL: https://issues.apache.org/jira/browse/AMBARI-17168 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17168.patch > > > Its likely because APP_TIMELINE_SERVER component (due to AMBARI-17111) become > an optional component. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17168) Kerberization of a cluster deletes ATS service
Dmytro Sen created AMBARI-17168: --- Summary: Kerberization of a cluster deletes ATS service Key: AMBARI-17168 URL: https://issues.apache.org/jira/browse/AMBARI-17168 Project: Ambari Issue Type: Bug Affects Versions: 2.4.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Priority: Blocker Fix For: 2.4.0 Its likely because APP_TIMELINE_SERVER component (due to AMBARI-17111) become an optional component. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17141) "Settings" button shown to cluster administrator
[ https://issues.apache.org/jira/browse/AMBARI-17141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-17141: -- Resolution: Fixed Status: Resolved (was: Patch Available) > "Settings" button shown to cluster administrator > > > Key: AMBARI-17141 > URL: https://issues.apache.org/jira/browse/AMBARI-17141 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17141.patch, AMBARI-17141_2.patch, Ambari - > Dropdown Menu.png, Screen Shot 2016-06-08 at 11.04.03 AM.png > > > The button "Settings" in the drop down of the "admin" tab in ambari shouldn't > be shown for cluster administrator. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17141) "Settings" button shown to cluster administrator
[ https://issues.apache.org/jira/browse/AMBARI-17141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15324526#comment-15324526 ] Andrii Tkach commented on AMBARI-17141: --- second patch committed to trunk and branch-2.4 > "Settings" button shown to cluster administrator > > > Key: AMBARI-17141 > URL: https://issues.apache.org/jira/browse/AMBARI-17141 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17141.patch, AMBARI-17141_2.patch, Ambari - > Dropdown Menu.png, Screen Shot 2016-06-08 at 11.04.03 AM.png > > > The button "Settings" in the drop down of the "admin" tab in ambari shouldn't > be shown for cluster administrator. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17163) Wildcards shouldn't be used for package installation
[
https://issues.apache.org/jira/browse/AMBARI-17163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15324501#comment-15324501
]
Hudson commented on AMBARI-17163:
-
SUCCESS: Integrated in Ambari-trunk-Commit #5051 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5051/])
AMBARI-17163. Wildcards shouldn't be used for package installation (aonishuk:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d58382a877ba1b6f5ca210c5cad961cd24586038])
* ambari-common/src/main/python/resource_management/libraries/script/script.py
> Wildcards shouldn't be used for package installation
>
>
> Key: AMBARI-17163
> URL: https://issues.apache.org/jira/browse/AMBARI-17163
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-17163.patch
>
>
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/STORM/0.9.1/package/scripts/supervisor.py",
> line 112, in
> Supervisor().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 257, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/STORM/0.9.1/package/scripts/supervisor.py",
> line 43, in install
> self.configure(env)
> File
> "/var/lib/ambari-agent/cache/common-services/STORM/0.9.1/package/scripts/supervisor.py",
> line 48, in configure
> storm("supervisor")
> File
> "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py", line 89,
> in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/STORM/0.9.1/package/scripts/storm.py",
> line 76, in storm
> cd_access="a",
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line
> 155, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 185, in action_create
> sudo.makedirs(path, self.resource.mode or 0755)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/sudo.py", line
> 174, in makedirs
> shell.checked_call(["mkdir", "-p", path], sudo=True)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 70, in inner
> result = function(command, **kwargs)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 92, in checked_call
> tries=tries, try_sleep=try_sleep)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 140, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 293, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'mkdir -p
> /usr/hdp/current/storm-supervisor/conf' returned 1. mkdir: cannot create
> directory `/usr/hdp/current/storm-supervisor': File exists
>
> **Reason:**
> The problem happens because we install packages with *
> Which causes a skip for storm-* because storm-*-slider is installed
>
>
> 2016-06-09 10:10:43,490 - Package['storm_2_5_0_0_*']
> {'retry_on_repo_unavailability': False, 'retry_count': 5}
> 2016-06-09 10:10:43,864 - Skipping installation of existing package
> storm_2_5_0_0_*
>
>
>
> # rpm -qa | grep storm
> storm_2_5_0_0_688-slider-client-1.0.1.2.5.0.0-688.el6.x86_6
>
> **Solution**:
> RE should do the change in manifests. To not propagate wildcards in package-
> version.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17163) Wildcards shouldn't be used for package installation
[
https://issues.apache.org/jira/browse/AMBARI-17163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15324479#comment-15324479
]
Hadoop QA commented on AMBARI-17163:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12809443/AMBARI-17163.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/7295//console
This message is automatically generated.
> Wildcards shouldn't be used for package installation
>
>
> Key: AMBARI-17163
> URL: https://issues.apache.org/jira/browse/AMBARI-17163
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-17163.patch
>
>
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/STORM/0.9.1/package/scripts/supervisor.py",
> line 112, in
> Supervisor().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 257, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/STORM/0.9.1/package/scripts/supervisor.py",
> line 43, in install
> self.configure(env)
> File
> "/var/lib/ambari-agent/cache/common-services/STORM/0.9.1/package/scripts/supervisor.py",
> line 48, in configure
> storm("supervisor")
> File
> "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py", line 89,
> in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/STORM/0.9.1/package/scripts/storm.py",
> line 76, in storm
> cd_access="a",
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line
> 155, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 185, in action_create
> sudo.makedirs(path, self.resource.mode or 0755)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/sudo.py", line
> 174, in makedirs
> shell.checked_call(["mkdir", "-p", path], sudo=True)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 70, in inner
> result = function(command, **kwargs)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 92, in checked_call
> tries=tries, try_sleep=try_sleep)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 140, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 293, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'mkdir -p
> /usr/hdp/current/storm-supervisor/conf' returned 1. mkdir: cannot create
> directory `/usr/hdp/current/storm-supervisor': File exists
>
> **Reason:**
> The problem happens because we install packages with *
> Which causes a skip for storm-* because storm-*-slider is installed
>
>
> 2016-06-09 10:10:43,490 - Package['storm_2_5_0_0_*']
> {'retry_on_repo_unavailability': False, 'retry_count': 5}
> 2016-06-09 10:10:43,864 - Skipping installation of existing package
> storm_2_5_0_0_*
>
>
>
> # rpm -qa | grep storm
> storm_2_5_0_0_688-slider-client-1.0.1.2.5.0.0-688.el6.x86_6
>
> **Solution**:
> RE should do the change in manifests. To not propagate wildcards in package-
> version.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17141) "Settings" button shown to cluster administrator
[
https://issues.apache.org/jira/browse/AMBARI-17141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15324478#comment-15324478
]
Hadoop QA commented on AMBARI-17141:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12809430/AMBARI-17141_2.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/7294//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7294//console
This message is automatically generated.
> "Settings" button shown to cluster administrator
>
>
> Key: AMBARI-17141
> URL: https://issues.apache.org/jira/browse/AMBARI-17141
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17141.patch, AMBARI-17141_2.patch, Ambari -
> Dropdown Menu.png, Screen Shot 2016-06-08 at 11.04.03 AM.png
>
>
> The button "Settings" in the drop down of the "admin" tab in ambari shouldn't
> be shown for cluster administrator.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17159) Upon successful start, log the process id for daemons started
[
https://issues.apache.org/jira/browse/AMBARI-17159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15324458#comment-15324458
]
Hadoop QA commented on AMBARI-17159:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12809380/AMBARI-17159.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/7293//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7293//console
This message is automatically generated.
> Upon successful start, log the process id for daemons started
> -
>
> Key: AMBARI-17159
> URL: https://issues.apache.org/jira/browse/AMBARI-17159
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.4.0
>Reporter: Myroslav Papirkovskyi
>Assignee: Myroslav Papirkovskyi
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17159.patch
>
>
> As part of successful start commands, lets log the process id of the daemons
> that started. One option could be to call the status() from start() with a
> parameter that lets the implementation log all details.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
