[jira] [Created] (AMBARI-19456) RU: Falcon LR job failed (upgrade-downgrade)
Dmytro Grinenko created AMBARI-19456:
Summary: RU: Falcon LR job failed (upgrade-downgrade)
Key: AMBARI-19456
URL: https://issues.apache.org/jira/browse/AMBARI-19456
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: trunk, 2.5.0
Reporter: Dmytro Grinenko
Assignee: Dmytro Grinenko
Priority: Critical
Fix For: trunk, 2.5.0
{code}
2016-12-19 06:20:52,811|INFO|MainThread|machine.py:139 - run()|ERROR: Unable to
initialize Falcon Client object
2016-12-19 06:20:52,866|INFO|MainThread|ruUpgrade.py:67 -
reportProgress()|[FAILED][Falcon] Warning (ignoreError=True): Non-zero exit
code when running command admin -version as user falcon
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19455) RU: Falcon LR job failed (upgrade-downgrade)
Dmytro Grinenko created AMBARI-19455:
Summary: RU: Falcon LR job failed (upgrade-downgrade)
Key: AMBARI-19455
URL: https://issues.apache.org/jira/browse/AMBARI-19455
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: trunk, 2.5.0
Reporter: Dmytro Grinenko
Assignee: Dmytro Grinenko
Priority: Critical
Fix For: trunk, 2.5.0
{code}
2016-12-19 06:20:52,811|INFO|MainThread|machine.py:139 - run()|ERROR: Unable to
initialize Falcon Client object
2016-12-19 06:20:52,866|INFO|MainThread|ruUpgrade.py:67 -
reportProgress()|[FAILED][Falcon] Warning (ignoreError=True): Non-zero exit
code when running command admin -version as user falcon
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19454) Label changes and missing fields for action nodes
M Madhan Mohan Reddy created AMBARI-19454: - Summary: Label changes and missing fields for action nodes Key: AMBARI-19454 URL: https://issues.apache.org/jira/browse/AMBARI-19454 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: M Madhan Mohan Reddy Assignee: M Madhan Mohan Reddy Fix For: 2.5.0 Need below label changes for below action nodes : 1) Spark : a) 'Job Tracker' should be changed to 'Resource Manager' b) Change the 'Name' to 'Application Name' c) 'Mode' field which is part of the xsd is missing. 2) Java : a) Java opts to 'java Options' b) Provide hidden label for 'Java opt' input field. (Required for automation) 3) Email : a) 'Content Type' and 'Attachment' fields missing in email node 4) SSH a) Provide label for 'args' radio group. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19440) Need ability to upload and download action asset from HDFS
[ https://issues.apache.org/jira/browse/AMBARI-19440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] M Madhan Mohan Reddy updated AMBARI-19440: -- Attachment: (was: 0001-AMBARI-19440.-Need-ability-to-upload-and-download-ac.patch) > Need ability to upload and download action asset from HDFS > -- > > Key: AMBARI-19440 > URL: https://issues.apache.org/jira/browse/AMBARI-19440 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: M Madhan Mohan Reddy >Assignee: M Madhan Mohan Reddy > Labels: WFD > Fix For: 2.5.0 > > Attachments: AMBARI-19440_trunk.patch > > > Need ability to upload asset to a HDFS location and download later. > a) This helps in using assets across views. > b) Also users may upload the saved asset into git for others to use. > This is based on inputs from Artem Ervits. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19440) Need ability to upload and download action asset from HDFS
[ https://issues.apache.org/jira/browse/AMBARI-19440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] M Madhan Mohan Reddy updated AMBARI-19440: -- Attachment: AMBARI-19440_trunk.patch > Need ability to upload and download action asset from HDFS > -- > > Key: AMBARI-19440 > URL: https://issues.apache.org/jira/browse/AMBARI-19440 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: M Madhan Mohan Reddy >Assignee: M Madhan Mohan Reddy > Labels: WFD > Fix For: 2.5.0 > > Attachments: AMBARI-19440_trunk.patch > > > Need ability to upload asset to a HDFS location and download later. > a) This helps in using assets across views. > b) Also users may upload the saved asset into git for others to use. > This is based on inputs from Artem Ervits. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19453) Dashboard should display appropriate message if workflow data fetching api fails
[ https://issues.apache.org/jira/browse/AMBARI-19453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] M Madhan Mohan Reddy updated AMBARI-19453: -- Status: Patch Available (was: Open) > Dashboard should display appropriate message if workflow data fetching api > fails > > > Key: AMBARI-19453 > URL: https://issues.apache.org/jira/browse/AMBARI-19453 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: M Madhan Mohan Reddy >Assignee: M Madhan Mohan Reddy > Labels: WFD > Fix For: 2.5.0 > > Attachments: AMBARI-19453_trunk.patch > > > Dashboard should display appropriate message if workflow data fetching api > fails. Currently dashboard shows empty table without any error message. This > provides the user wrong impression that no workflow is being run. Instead its > better to show error message explicitly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19453) Dashboard should display appropriate message if workflow data fetching api fails
[ https://issues.apache.org/jira/browse/AMBARI-19453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] M Madhan Mohan Reddy updated AMBARI-19453: -- Attachment: AMBARI-19453_trunk.patch > Dashboard should display appropriate message if workflow data fetching api > fails > > > Key: AMBARI-19453 > URL: https://issues.apache.org/jira/browse/AMBARI-19453 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: M Madhan Mohan Reddy >Assignee: M Madhan Mohan Reddy > Labels: WFD > Fix For: 2.5.0 > > Attachments: AMBARI-19453_trunk.patch > > > Dashboard should display appropriate message if workflow data fetching api > fails. Currently dashboard shows empty table without any error message. This > provides the user wrong impression that no workflow is being run. Instead its > better to show error message explicitly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (AMBARI-19452) Metrics of flume shows same values for all channels,sinks or sources in host
[ https://issues.apache.org/jira/browse/AMBARI-19452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangjianfei updated AMBARI-19452: - Comment: was deleted (was: Thr url:/api/v1/clusters/bch/hosts/hcontrol-1/host_components/FLUME_HANDLER?fields=metrics/flume/flume/CHANNEL/ch1/EventTakeAttemptCount[1484110458,1484114058,15],metrics/flume/flume/CHANNEL/ch2/EventTakeAttemptCount[1484110458,1484114058,15]&_=1484114096164 return the same metric values for both ch1 and ch2.) > Metrics of flume shows same values for all channels,sinks or sources in host > > > Key: AMBARI-19452 > URL: https://issues.apache.org/jira/browse/AMBARI-19452 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: wangjianfei > Fix For: 2.5.0 > > Attachments: Error.png > > > When configuring multiply Channels-Sinks-Sources in flume,the flume > metric of hosts always shows the same metric for all the Channels. > Take Channel for example,actually,if configure Channel.ch1 and > Channel.ch2,when retrive metrics of both ch1 and ch2 of the host,it returns > the same metric values(values of last metric) for both ch1 and ch2。 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19452) Metrics of flume shows same values for all channels,sinks or sources in host
[ https://issues.apache.org/jira/browse/AMBARI-19452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangjianfei updated AMBARI-19452: - Attachment: Error.png Thr url:/api/v1/clusters/bch/hosts/hcontrol-1/host_components/FLUME_HANDLER?fields=metrics/flume/flume/CHANNEL/ch1/EventTakeAttemptCount[1484110458,1484114058,15],metrics/flume/flume/CHANNEL/ch2/EventTakeAttemptCount[1484110458,1484114058,15]&_=1484114096164 return the same metric values for both ch1 and ch2. > Metrics of flume shows same values for all channels,sinks or sources in host > > > Key: AMBARI-19452 > URL: https://issues.apache.org/jira/browse/AMBARI-19452 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: wangjianfei > Fix For: 2.5.0 > > Attachments: Error.png > > > When configuring multiply Channels-Sinks-Sources in flume,the flume > metric of hosts always shows the same metric for all the Channels. > Take Channel for example,actually,if configure Channel.ch1 and > Channel.ch2,when retrive metrics of both ch1 and ch2 of the host,it returns > the same metric values(values of last metric) for both ch1 and ch2。 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19452) Metrics of flume shows same values for all channels,sinks or sources in host
wangjianfei created AMBARI-19452: Summary: Metrics of flume shows same values for all channels,sinks or sources in host Key: AMBARI-19452 URL: https://issues.apache.org/jira/browse/AMBARI-19452 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: wangjianfei Fix For: 2.5.0 When configuring multiply Channels-Sinks-Sources in flume,the flume metric of hosts always shows the same metric for all the Channels. Take Channel for example,actually,if configure Channel.ch1 and Channel.ch2,when retrive metrics of both ch1 and ch2 of the host,it returns the same metric values(values of last metric) for both ch1 and ch2。 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19444) Log Feeder should be restarted after configuration change
[ https://issues.apache.org/jira/browse/AMBARI-19444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15817269#comment-15817269 ] Hudson commented on AMBARI-19444: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6403 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6403/]) AMBARI-19444 Log Feeder should be restarted after configuration change (mgergely: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7f09e4c6a7751004132e41d1ccd9ec7e48998231]) * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/properties/input.config-ambari.json.j2 * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/metainfo.xml > Log Feeder should be restarted after configuration change > -- > > Key: AMBARI-19444 > URL: https://issues.apache.org/jira/browse/AMBARI-19444 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.5.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.5.0 > > Attachments: AMBARI-19444.patch > > > If any of the -logsearch-conf property is modified then the > logfeeders should be restarted to work with the updated configs -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17470) Refactor Ambari service def configurations for Zeppelin
[ https://issues.apache.org/jira/browse/AMBARI-17470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15817270#comment-15817270 ] Hudson commented on AMBARI-17470: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6403 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6403/]) AMBARI-17470 Refactor Ambari service def configurations for Zeppelin (renjith.kamath: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ac66085b35b69264c6d161a00fc866b5e1a828da]) * (edit) ambari-server/src/test/python/stacks/2.5/configs/default.json * (add) ambari-server/src/main/resources/stacks/HDP/2.6/services/ZEPPELIN/configuration/zeppelin-env.xml * (edit) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/metainfo.xml * (edit) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/params.py * (add) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/configuration/zeppelin-log4j-properties.xml * (edit) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/configuration/zeppelin-env.xml * (edit) ambari-server/src/test/python/stacks/2.5/configs/secured.json * (add) ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/config-upgrade.xml * (add) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/configuration/zeppelin-shiro-ini.xml * (edit) ambari-server/src/test/python/stacks/2.5/ZEPPELIN/test_zeppelin_master.py > Refactor Ambari service def configurations for Zeppelin > --- > > Key: AMBARI-17470 > URL: https://issues.apache.org/jira/browse/AMBARI-17470 > Project: Ambari > Issue Type: Improvement > Components: stacks >Reporter: Yesha Vora >Assignee: Renjith Kamath > Fix For: 2.5.0 > > Attachments: AMBARI-17470-branch-2.5-v1.patch, > AMBARI-17470-branch-2.5-v2.patch, AMBARI-17470-trunk-v1.patch > > > Zeppelin has below configuration files : > * zeppelin-env.sh > * zeppelin-site.xml > * log4j.properties > Amabri UI shows zeppelin-env.sh and zeppelin-site.xml in config page. It > should also add log4j.properties file in Ambari config page. > - Move shiro.ini and log4j.properties out of zeppelin-env configuration. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19451) When defining yarn.scheduler.capacity..accessible-node-labels with space, Yarn Queue Manager shows error for the queue
[ https://issues.apache.org/jira/browse/AMBARI-19451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-19451: Attachment: YarnConfig.jpg Error.jpg > When defining yarn.scheduler.capacity..accessible-node-labels > with space, Yarn Queue Manager shows error for the queue > -- > > Key: AMBARI-19451 > URL: https://issues.apache.org/jira/browse/AMBARI-19451 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > Attachments: Error.jpg, YarnConfig.jpg > > > Per the Apache documentation for Yarn Node Labels > (http://hadoop.apache.org/docs/r2.7.3/hadoop-yarn/hadoop-yarn-site/NodeLabel.html), > queues that can only access nodes without labels are defined by setting the > property "yarn.scheduler.capacity..accessible-node-labels" with > space as the value. > Reproduction Steps: > 1. In the Capacity Scheduler view (Yarn Queue Manager), create queues q1,q2, > and set accessible node labels for root,q1,q2 but not for default queue > 2. Since there is no way to specify a "space" as the value for accessible > node labels via Yarn Queue Manager, add this property manually via yarn > configs. i.e. In Yarn -> Configs -> Scheduler, manually add > yarn.scheduler.capacity.root.default.accessible-node-labels= (space after the > =) > 3. Save the configuration and restart Resource Manager as required > 4. Return to Yarn Queue Manager, and click the default queue. It shows an > error - Label is not exist on cluster. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19451) When defining yarn.scheduler.capacity..accessible-node-labels with space, Yarn Queue Manager shows error for the queue
[ https://issues.apache.org/jira/browse/AMBARI-19451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-19451: Description: Per the Apache documentation for Yarn Node Labels (http://hadoop.apache.org/docs/r2.7.3/hadoop-yarn/hadoop-yarn-site/NodeLabel.html), queues that can only access nodes without labels are defined by setting the property "yarn.scheduler.capacity..accessible-node-labels" with space as the value. Reproduction Steps: 1. In the Capacity Scheduler view (Yarn Queue Manager), create queues q1,q2, and set accessible node labels for root,q1,q2 but not for default queue 2. Since there is no way to specify a "space" as the value for accessible node labels via Yarn Queue Manager, add this property manually via yarn configs. i.e. In Yarn -> Configs -> Scheduler, manually add yarn.scheduler.capacity.root.default.accessible-node-labels= (space after the =) 3. Save the configuration and restart Resource Manager as required 4. Return to Yarn Queue Manager, and click the default queue. It shows an error - Label is not exist on cluster. > When defining yarn.scheduler.capacity..accessible-node-labels > with space, Yarn Queue Manager shows error for the queue > -- > > Key: AMBARI-19451 > URL: https://issues.apache.org/jira/browse/AMBARI-19451 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > > Per the Apache documentation for Yarn Node Labels > (http://hadoop.apache.org/docs/r2.7.3/hadoop-yarn/hadoop-yarn-site/NodeLabel.html), > queues that can only access nodes without labels are defined by setting the > property "yarn.scheduler.capacity..accessible-node-labels" with > space as the value. > Reproduction Steps: > 1. In the Capacity Scheduler view (Yarn Queue Manager), create queues q1,q2, > and set accessible node labels for root,q1,q2 but not for default queue > 2. Since there is no way to specify a "space" as the value for accessible > node labels via Yarn Queue Manager, add this property manually via yarn > configs. i.e. In Yarn -> Configs -> Scheduler, manually add > yarn.scheduler.capacity.root.default.accessible-node-labels= (space after the > =) > 3. Save the configuration and restart Resource Manager as required > 4. Return to Yarn Queue Manager, and click the default queue. It shows an > error - Label is not exist on cluster. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19451) When defining yarn.scheduler.capacity..accessible-node-labels with space, Yarn Queue Manager shows error for the queue
Sangeeta Ravindran created AMBARI-19451: --- Summary: When defining yarn.scheduler.capacity..accessible-node-labels with space, Yarn Queue Manager shows error for the queue Key: AMBARI-19451 URL: https://issues.apache.org/jira/browse/AMBARI-19451 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Environment: Per the Apache documentation for Yarn Node Labels (http://hadoop.apache.org/docs/r2.7.3/hadoop-yarn/hadoop-yarn-site/NodeLabel.html), queues that can only access nodes without labels are defined by setting the property "yarn.scheduler.capacity..accessible-node-labels" with space as the value. Reproduction Steps: 1. In the Capacity Scheduler view (Yarn Queue Manager), create queues q1,q2, and set accessible node labels for root,q1,q2 but not for default queue 2. Since there is no way to specify a "space" as the value for accessible node labels via Yarn Queue Manager, add this property manually via yarn configs. i.e. In Yarn -> Configs -> Scheduler, manually add yarn.scheduler.capacity.root.default.accessible-node-labels= (space after the =) 3. Save the configuration and restart Resource Manager as required 4. Return to Yarn Queue Manager, and click the default queue. It shows an error - Label is not exist on cluster. Reporter: Sangeeta Ravindran Assignee: Sangeeta Ravindran -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19248) Add Livy to HDP 2.6 as slave component of Spark2
[ https://issues.apache.org/jira/browse/AMBARI-19248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15817197#comment-15817197 ] Hudson commented on AMBARI-19248: - ABORTED: Integrated in Jenkins build Ambari-trunk-Commit #6402 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6402/]) AMBARI-19248. Add Livy to HDP 2.6 as slave component of Spark2 (Mingjie (afernandez: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=fecc9b80a83535734f1fbc9db8c35f48f6f7fc4b]) * (edit) ambari-server/src/main/resources/common-services/SPARK2/2.0.0/package/scripts/service_check.py * (add) ambari-server/src/main/resources/common-services/SPARK2/2.0.0/package/scripts/livy2_service.py * (edit) ambari-server/src/main/resources/common-services/SPARK2/2.0.0/package/scripts/params.py * (add) ambari-server/src/test/python/stacks/2.6/SPARK2/test_spark_livy2.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py * (add) ambari-server/src/main/resources/stacks/HDP/2.6/services/SPARK2/configuration/livy2-log4j-properties.xml * (add) ambari-server/src/main/resources/stacks/HDP/2.6/services/SPARK2/configuration/livy2-env.xml * (edit) ambari-common/src/main/python/resource_management/libraries/functions/constants.py * (add) ambari-server/src/main/resources/common-services/SPARK2/2.0.0/package/scripts/setup_livy2.py * (add) ambari-server/src/main/resources/stacks/HDP/2.6/services/SPARK2/configuration/livy2-spark-blacklist.xml * (add) ambari-server/src/main/resources/stacks/HDP/2.6/services/SPARK2/configuration/livy2-conf.xml * (add) ambari-server/src/main/resources/stacks/HDP/2.6/services/SPARK2/kerberos.json * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/SPARK2/metainfo.xml * (edit) ambari-server/src/test/python/stacks/2.6/configs/default.json * (edit) ambari-server/src/main/resources/common-services/SPARK2/2.0.0/package/scripts/status_params.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/properties/stack_features.json * (add) ambari-server/src/main/resources/common-services/SPARK2/2.0.0/package/scripts/livy2_server.py > Add Livy to HDP 2.6 as slave component of Spark2 > > > Key: AMBARI-19248 > URL: https://issues.apache.org/jira/browse/AMBARI-19248 > Project: Ambari > Issue Type: New Feature > Components: stacks >Affects Versions: 2.5.0 >Reporter: mingjie tang >Assignee: mingjie tang > Fix For: 2.5.0 > > Attachments: AMBARI-19248.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19442) Ownership is changed before the creation of directory in ZEPPELIN master.py
[
https://issues.apache.org/jira/browse/AMBARI-19442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Renjith Kamath updated AMBARI-19442:
Attachment: AMBARI-19442-trunk-v1.patch
> Ownership is changed before the creation of directory in ZEPPELIN master.py
> ---
>
> Key: AMBARI-19442
> URL: https://issues.apache.org/jira/browse/AMBARI-19442
> Project: Ambari
> Issue Type: Bug
>Reporter: Pradarttana
>Assignee: Renjith Kamath
>Priority: Blocker
> Attachments: AMBARI-19442-branch-2.5-v1.patch,
> AMBARI-19442-trunk-v1.patch
>
>
> ownership is changed before the creation of directory in ZEPPELIN master.py
> file :-
> /var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py
> {code}
> def configure(self, env):
> import params
> import status_params
> env.set_params(params)
> env.set_params(status_params)
> self.create_zeppelin_log_dir(env)
> self.chown_zeppelin_pid_dir(env)
> # create the pid and zeppelin dirs
> Directory([params.zeppelin_pid_dir, params.zeppelin_dir],
> owner=params.zeppelin_user,
> group=params.zeppelin_group,
> cd_access="a",
> create_parents=True,
> mode=0755
> )
> # write out zeppelin-site.xml
> XmlConfig("zeppelin-site.xml",
> conf_dir=params.conf_dir,
>
> configurations=params.config['configurations']['zeppelin-config'],
> owner=params.zeppelin_user,
> group=params.zeppelin_group
> {code}
> The Failure message :-
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py",
> line 375, in
> Master().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 287, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py",
> line 172, in start
> self.configure(env)
> File
> "/var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py",
> line 119, in configure
> self.chown_zeppelin_pid_dir(env)
> File
> "/var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py",
> line 111, in chown_zeppelin_pid_dir
> sudo=True)
> 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 262, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 72, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 303, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of 'chown -R
> cstm-zeppelin:cstm-zeppelin /var/run/zeppelin' returned 1. chown: cannot
> access '/var/run/zeppelin': No such file or directory
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19413) Support Ceph for Ambari Service
[ https://issues.apache.org/jira/browse/AMBARI-19413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated AMBARI-19413: --- Description: Allow Ceph to be installed via Ambari I'm trying to do http://www.redoop.org/OpenStorage/Ceph-service/src/newcode was: Allow Ceph to be installed via Ambari I'm trying to do http://www.redoop.org/OpenStorage/Ceph-service.git > Support Ceph for Ambari Service > --- > > Key: AMBARI-19413 > URL: https://issues.apache.org/jira/browse/AMBARI-19413 > Project: Ambari > Issue Type: New Feature > Components: ambari-server >Affects Versions: 2.3.0 > Environment: CentOS 6 >Reporter: Gavin > Labels: ambari, ceph > Fix For: 2.3.0 > > > Allow Ceph to be installed via Ambari > I'm trying to do > http://www.redoop.org/OpenStorage/Ceph-service/src/newcode -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19450) Host version incorrectly reported as OUT_OF_SYNC
[
https://issues.apache.org/jira/browse/AMBARI-19450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15817058#comment-15817058
]
Hadoop QA commented on AMBARI-19450:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12846708/AMBARI-19450.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/9993//console
This message is automatically generated.
> Host version incorrectly reported as OUT_OF_SYNC
>
>
> Key: AMBARI-19450
> URL: https://issues.apache.org/jira/browse/AMBARI-19450
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19450.patch
>
>
> After installing a cluster, and there are no versionable components on a
> Host, the BE is incorrectly reporting the host version as OUT_OF_SYNC. This
> is incorrect as we should be reporting NOT_REQUIRED.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19444) Log Feeder should be restarted after configuration change
[ https://issues.apache.org/jira/browse/AMBARI-19444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15817036#comment-15817036 ] Hudson commented on AMBARI-19444: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #683 (See [https://builds.apache.org/job/Ambari-branch-2.5/683/]) AMBARI-19444 Log Feeder should be restarted after configuration change (mgergely: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=a96880fb91e8ef67450b9055389e29e1cc5998fc]) * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/metainfo.xml * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/properties/input.config-ambari.json.j2 > Log Feeder should be restarted after configuration change > -- > > Key: AMBARI-19444 > URL: https://issues.apache.org/jira/browse/AMBARI-19444 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.5.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.5.0 > > Attachments: AMBARI-19444.patch > > > If any of the -logsearch-conf property is modified then the > logfeeders should be restarted to work with the updated configs -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19434) Changing Capacity-scheduler configs while llap is enabled should warn the user if llap is affected
[
https://issues.apache.org/jira/browse/AMBARI-19434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15817010#comment-15817010
]
Hadoop QA commented on AMBARI-19434:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12846714/AMBARI-19434.v1.branch-2.5.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/9992//console
This message is automatically generated.
> Changing Capacity-scheduler configs while llap is enabled should warn the
> user if llap is affected
> --
>
> Key: AMBARI-19434
> URL: https://issues.apache.org/jira/browse/AMBARI-19434
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 2.5.0
>
> Attachments: AMBARI-19434.v1.branch-2.5.patch, Screen Shot 2017-01-09
> at 3.15.39 PM.png
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17470) Refactor Ambari service def configurations for Zeppelin
[ https://issues.apache.org/jira/browse/AMBARI-17470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Renjith Kamath updated AMBARI-17470: Resolution: Fixed Status: Resolved (was: Patch Available) committed to branch-2.5 and trunk with tests > Refactor Ambari service def configurations for Zeppelin > --- > > Key: AMBARI-17470 > URL: https://issues.apache.org/jira/browse/AMBARI-17470 > Project: Ambari > Issue Type: Improvement > Components: stacks >Reporter: Yesha Vora >Assignee: Renjith Kamath > Fix For: 2.5.0 > > Attachments: AMBARI-17470-branch-2.5-v1.patch, > AMBARI-17470-branch-2.5-v2.patch, AMBARI-17470-trunk-v1.patch > > > Zeppelin has below configuration files : > * zeppelin-env.sh > * zeppelin-site.xml > * log4j.properties > Amabri UI shows zeppelin-env.sh and zeppelin-site.xml in config page. It > should also add log4j.properties file in Ambari config page. > - Move shiro.ini and log4j.properties out of zeppelin-env configuration. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19248) Add Livy to HDP 2.6 as slave component of Spark2
[ https://issues.apache.org/jira/browse/AMBARI-19248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15816797#comment-15816797 ] Hudson commented on AMBARI-19248: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #682 (See [https://builds.apache.org/job/Ambari-branch-2.5/682/]) AMBARI-19248. Add Livy to HDP 2.6 as slave component of Spark2 (Mingjie (afernandez: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=fab12b505a2ddfa662910888cbd43512967a84dc]) * (edit) ambari-server/src/main/resources/common-services/SPARK2/2.0.0/package/scripts/params.py * (edit) ambari-server/src/main/resources/common-services/SPARK2/2.0.0/package/scripts/status_params.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/SPARK2/metainfo.xml * (add) ambari-server/src/main/resources/common-services/SPARK2/2.0.0/package/scripts/setup_livy2.py * (add) ambari-server/src/main/resources/stacks/HDP/2.6/services/SPARK2/configuration/livy2-conf.xml * (add) ambari-server/src/main/resources/stacks/HDP/2.6/services/SPARK2/configuration/livy2-env.xml * (add) ambari-server/src/main/resources/common-services/SPARK2/2.0.0/package/scripts/livy2_service.py * (add) ambari-server/src/main/resources/stacks/HDP/2.6/services/SPARK2/kerberos.json * (edit) ambari-server/src/main/resources/common-services/SPARK2/2.0.0/package/scripts/service_check.py * (edit) ambari-common/src/main/python/resource_management/libraries/functions/constants.py * (add) ambari-server/src/main/resources/stacks/HDP/2.6/services/SPARK2/configuration/livy2-log4j-properties.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/role_command_order.json * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py * (add) ambari-server/src/test/python/stacks/2.6/SPARK2/test_spark_livy2.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/properties/stack_features.json * (edit) ambari-server/src/test/python/stacks/2.6/configs/default.json * (add) ambari-server/src/main/resources/stacks/HDP/2.6/services/SPARK2/configuration/livy2-spark-blacklist.xml * (add) ambari-server/src/main/resources/common-services/SPARK2/2.0.0/package/scripts/livy2_server.py > Add Livy to HDP 2.6 as slave component of Spark2 > > > Key: AMBARI-19248 > URL: https://issues.apache.org/jira/browse/AMBARI-19248 > Project: Ambari > Issue Type: New Feature > Components: stacks >Affects Versions: 2.5.0 >Reporter: mingjie tang >Assignee: mingjie tang > Fix For: 2.5.0 > > Attachments: AMBARI-19248.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17470) Refactor Ambari service def configurations for Zeppelin
[ https://issues.apache.org/jira/browse/AMBARI-17470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Renjith Kamath updated AMBARI-17470: Attachment: AMBARI-17470-trunk-v1.patch > Refactor Ambari service def configurations for Zeppelin > --- > > Key: AMBARI-17470 > URL: https://issues.apache.org/jira/browse/AMBARI-17470 > Project: Ambari > Issue Type: Improvement > Components: stacks >Reporter: Yesha Vora >Assignee: Renjith Kamath > Fix For: 2.5.0 > > Attachments: AMBARI-17470-branch-2.5-v1.patch, > AMBARI-17470-branch-2.5-v2.patch, AMBARI-17470-trunk-v1.patch > > > Zeppelin has below configuration files : > * zeppelin-env.sh > * zeppelin-site.xml > * log4j.properties > Amabri UI shows zeppelin-env.sh and zeppelin-site.xml in config page. It > should also add log4j.properties file in Ambari config page. > - Move shiro.ini and log4j.properties out of zeppelin-env configuration. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19444) Log Feeder should be restarted after configuration change
[ https://issues.apache.org/jira/browse/AMBARI-19444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-19444: Resolution: Fixed Status: Resolved (was: Patch Available) > Log Feeder should be restarted after configuration change > -- > > Key: AMBARI-19444 > URL: https://issues.apache.org/jira/browse/AMBARI-19444 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.5.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.5.0 > > Attachments: AMBARI-19444.patch > > > If any of the -logsearch-conf property is modified then the > logfeeders should be restarted to work with the updated configs -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19444) Log Feeder should be restarted after configuration change
[
https://issues.apache.org/jira/browse/AMBARI-19444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15816738#comment-15816738
]
Miklos Gergely commented on AMBARI-19444:
-
committed to trunk:
{code:java}
commit 7f09e4c6a7751004132e41d1ccd9ec7e48998231
Author: Miklos Gergely
Date: Wed Jan 11 02:12:56 2017 +0100
AMBARI-19444 Log Feeder should be restarted after configuration change
(mgergely)
Change-Id: Id8653c1fb81332c8bfd47140d430b70580f65c4f
{code}
committed to branch-2.5:
{code:java}
commit a96880fb91e8ef67450b9055389e29e1cc5998fc
Author: Miklos Gergely
Date: Wed Jan 11 02:14:47 2017 +0100
AMBARI-19444 Log Feeder should be restarted after configuration change
(mgergely)
Change-Id: Ib9e65454182aa52b3fc09f4dbbbc4328284dcf62
{code}
> Log Feeder should be restarted after configuration change
> --
>
> Key: AMBARI-19444
> URL: https://issues.apache.org/jira/browse/AMBARI-19444
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.5.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
> Fix For: 2.5.0
>
> Attachments: AMBARI-19444.patch
>
>
> If any of the -logsearch-conf property is modified then the
> logfeeders should be restarted to work with the updated configs
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19444) Log Feeder should be restarted after configuration change
[ https://issues.apache.org/jira/browse/AMBARI-19444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-19444: Attachment: (was: AMBARI-19444.patch) > Log Feeder should be restarted after configuration change > -- > > Key: AMBARI-19444 > URL: https://issues.apache.org/jira/browse/AMBARI-19444 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.5.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.5.0 > > Attachments: AMBARI-19444.patch > > > If any of the -logsearch-conf property is modified then the > logfeeders should be restarted to work with the updated configs -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19444) Log Feeder should be restarted after configuration change
[ https://issues.apache.org/jira/browse/AMBARI-19444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-19444: Attachment: AMBARI-19444.patch > Log Feeder should be restarted after configuration change > -- > > Key: AMBARI-19444 > URL: https://issues.apache.org/jira/browse/AMBARI-19444 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.5.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 2.5.0 > > Attachments: AMBARI-19444.patch > > > If any of the -logsearch-conf property is modified then the > logfeeders should be restarted to work with the updated configs -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-19248) Add Livy to HDP 2.6 as slave component of Spark2
[ https://issues.apache.org/jira/browse/AMBARI-19248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez resolved AMBARI-19248. -- Resolution: Fixed Pushed to branch-2.5, commit fab12b505a2ddfa662910888cbd43512967a84dc trunk, commit fecc9b80a83535734f1fbc9db8c35f48f6f7fc4b > Add Livy to HDP 2.6 as slave component of Spark2 > > > Key: AMBARI-19248 > URL: https://issues.apache.org/jira/browse/AMBARI-19248 > Project: Ambari > Issue Type: New Feature > Components: stacks >Affects Versions: 2.5.0 >Reporter: mingjie tang >Assignee: mingjie tang > Fix For: 2.5.0 > > Attachments: AMBARI-19248.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19248) Add Livy to HDP 2.6 as slave component of Spark2
[ https://issues.apache.org/jira/browse/AMBARI-19248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-19248: - Attachment: AMBARI-19248.patch > Add Livy to HDP 2.6 as slave component of Spark2 > > > Key: AMBARI-19248 > URL: https://issues.apache.org/jira/browse/AMBARI-19248 > Project: Ambari > Issue Type: New Feature > Components: stacks >Affects Versions: 2.5.0 >Reporter: mingjie tang >Assignee: mingjie tang > Fix For: 2.5.0 > > Attachments: AMBARI-19248.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19434) Changing Capacity-scheduler configs while llap is enabled should warn the user if llap is affected
[ https://issues.apache.org/jira/browse/AMBARI-19434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-19434: Attachment: Screen Shot 2017-01-09 at 3.15.39 PM.png > Changing Capacity-scheduler configs while llap is enabled should warn the > user if llap is affected > -- > > Key: AMBARI-19434 > URL: https://issues.apache.org/jira/browse/AMBARI-19434 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-19434.v1.branch-2.5.patch, Screen Shot 2017-01-09 > at 3.15.39 PM.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19434) Changing Capacity-scheduler configs while llap is enabled should warn the user if llap is affected
[ https://issues.apache.org/jira/browse/AMBARI-19434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-19434: Status: Patch Available (was: Open) > Changing Capacity-scheduler configs while llap is enabled should warn the > user if llap is affected > -- > > Key: AMBARI-19434 > URL: https://issues.apache.org/jira/browse/AMBARI-19434 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-19434.v1.branch-2.5.patch, Screen Shot 2017-01-09 > at 3.15.39 PM.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19434) Changing Capacity-scheduler configs while llap is enabled should warn the user if llap is affected
[ https://issues.apache.org/jira/browse/AMBARI-19434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-19434: Attachment: AMBARI-19434.v1.branch-2.5.patch > Changing Capacity-scheduler configs while llap is enabled should warn the > user if llap is affected > -- > > Key: AMBARI-19434 > URL: https://issues.apache.org/jira/browse/AMBARI-19434 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-19434.v1.branch-2.5.patch, Screen Shot 2017-01-09 > at 3.15.39 PM.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19411) Metrics Sink for Atlas
[
https://issues.apache.org/jira/browse/AMBARI-19411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15816582#comment-15816582
]
Hadoop QA commented on AMBARI-19411:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12846692/AMBARI-19411.v2.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/9991//console
This message is automatically generated.
> Metrics Sink for Atlas
> --
>
> Key: AMBARI-19411
> URL: https://issues.apache.org/jira/browse/AMBARI-19411
> Project: Ambari
> Issue Type: Improvement
>Affects Versions: 2.5.0
>Reporter: Apoorv Naik
> Fix For: 2.5.0
>
> Attachments: 0001-AMBARI-19411-Atlas-AMS-support.patch,
> AMBARI-19411.v1.patch, AMBARI-19411.v2.patch
>
>
> Currently atlas has no way of publishing metrics/insights to AMS. This change
> adds a Atlas sink that will periodically collect and emit metrics.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19450) Host version incorrectly reported as OUT_OF_SYNC
[ https://issues.apache.org/jira/browse/AMBARI-19450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-19450: --- Status: Patch Available (was: Open) > Host version incorrectly reported as OUT_OF_SYNC > > > Key: AMBARI-19450 > URL: https://issues.apache.org/jira/browse/AMBARI-19450 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19450.patch > > > After installing a cluster, and there are no versionable components on a > Host, the BE is incorrectly reporting the host version as OUT_OF_SYNC. This > is incorrect as we should be reporting NOT_REQUIRED. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19423) Change HostStackVersionResourceProvider to be able to install packages on single host not belonging to any cluster
[
https://issues.apache.org/jira/browse/AMBARI-19423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15816568#comment-15816568
]
Hadoop QA commented on AMBARI-19423:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12846696/AMBARI-19423.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/9990//console
This message is automatically generated.
> Change HostStackVersionResourceProvider to be able to install packages on
> single host not belonging to any cluster
> --
>
> Key: AMBARI-19423
> URL: https://issues.apache.org/jira/browse/AMBARI-19423
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Reporter: Sandor Magyari
>Assignee: Sandor Magyari
> Fix For: 2.5.0
>
> Attachments: AMBARI-19423.patch
>
>
> This improvement will create the possibility of preinstalling packages on a
> host before the host is added to a cluster for given stack and components. A
> new request parameter 'components' has to be added to
> HostStackVersionResourceProvider to be able to pass the list of components we
> want to install packages for.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19423) Change HostStackVersionResourceProvider to be able to install packages on single host not belonging to any cluster
[ https://issues.apache.org/jira/browse/AMBARI-19423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Magyari updated AMBARI-19423: Attachment: (was: AMBARI-19423.patch) > Change HostStackVersionResourceProvider to be able to install packages on > single host not belonging to any cluster > -- > > Key: AMBARI-19423 > URL: https://issues.apache.org/jira/browse/AMBARI-19423 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Reporter: Sandor Magyari >Assignee: Sandor Magyari > Fix For: 2.5.0 > > Attachments: AMBARI-19423.patch > > > This improvement will create the possibility of preinstalling packages on a > host before the host is added to a cluster for given stack and components. A > new request parameter 'components' has to be added to > HostStackVersionResourceProvider to be able to pass the list of components we > want to install packages for. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19423) Change HostStackVersionResourceProvider to be able to install packages on single host not belonging to any cluster
[ https://issues.apache.org/jira/browse/AMBARI-19423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Magyari updated AMBARI-19423: Attachment: AMBARI-19423.patch > Change HostStackVersionResourceProvider to be able to install packages on > single host not belonging to any cluster > -- > > Key: AMBARI-19423 > URL: https://issues.apache.org/jira/browse/AMBARI-19423 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Reporter: Sandor Magyari >Assignee: Sandor Magyari > Fix For: 2.5.0 > > Attachments: AMBARI-19423.patch > > > This improvement will create the possibility of preinstalling packages on a > host before the host is added to a cluster for given stack and components. A > new request parameter 'components' has to be added to > HostStackVersionResourceProvider to be able to pass the list of components we > want to install packages for. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19411) Metrics Sink for Atlas
[ https://issues.apache.org/jira/browse/AMBARI-19411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Naik updated AMBARI-19411: - Attachment: AMBARI-19411.v2.patch > Metrics Sink for Atlas > -- > > Key: AMBARI-19411 > URL: https://issues.apache.org/jira/browse/AMBARI-19411 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.5.0 >Reporter: Apoorv Naik > Fix For: 2.5.0 > > Attachments: 0001-AMBARI-19411-Atlas-AMS-support.patch, > AMBARI-19411.v1.patch, AMBARI-19411.v2.patch > > > Currently atlas has no way of publishing metrics/insights to AMS. This change > adds a Atlas sink that will periodically collect and emit metrics. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19432) Improve "Install Wizard step 1" after new guidelines
[ https://issues.apache.org/jira/browse/AMBARI-19432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-19432: - Resolution: Fixed Status: Resolved (was: Patch Available) Commited to trunk > Improve "Install Wizard step 1" after new guidelines > > > Key: AMBARI-19432 > URL: https://issues.apache.org/jira/browse/AMBARI-19432 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > Attachments: AMBARI-19432.patch, AMBARI-19432.patch > > > Should do the following adjustments to integrate with the new style > guidelines: > As for the contents inside of the white panel: > 1. Make tabs in a horizontal view. > 2. Select stack button changed from blue to white. > 3. Repositories should be the title of the following section, so move the > radio buttons under that. > 4. Make two radio buttons in horizontal view. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19248) Add Livy to HDP 2.6 as slave component of Spark2
[ https://issues.apache.org/jira/browse/AMBARI-19248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-19248: - Fix Version/s: 2.5.0 > Add Livy to HDP 2.6 as slave component of Spark2 > > > Key: AMBARI-19248 > URL: https://issues.apache.org/jira/browse/AMBARI-19248 > Project: Ambari > Issue Type: New Feature > Components: stacks >Affects Versions: 2.5.0 >Reporter: mingjie tang >Assignee: mingjie tang > Fix For: 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19248) Add Livy to HDP 2.6 as slave component of Spark2
[ https://issues.apache.org/jira/browse/AMBARI-19248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-19248: - Affects Version/s: 2.5.0 > Add Livy to HDP 2.6 as slave component of Spark2 > > > Key: AMBARI-19248 > URL: https://issues.apache.org/jira/browse/AMBARI-19248 > Project: Ambari > Issue Type: New Feature > Components: stacks >Affects Versions: 2.5.0 >Reporter: mingjie tang >Assignee: mingjie tang > Fix For: 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19248) Add Livy to HDP 2.6 as slave component of Spark2
[ https://issues.apache.org/jira/browse/AMBARI-19248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-19248: - Component/s: stacks > Add Livy to HDP 2.6 as slave component of Spark2 > > > Key: AMBARI-19248 > URL: https://issues.apache.org/jira/browse/AMBARI-19248 > Project: Ambari > Issue Type: New Feature > Components: stacks >Affects Versions: 2.5.0 >Reporter: mingjie tang >Assignee: mingjie tang > Fix For: 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19449) Enable cartesian product edge by default for hive interactive in HDP 2.6 stack
[ https://issues.apache.org/jira/browse/AMBARI-19449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15816133#comment-15816133 ] Sumit Mohanty commented on AMBARI-19449: LGTM +1. > Enable cartesian product edge by default for hive interactive in HDP 2.6 stack > -- > > Key: AMBARI-19449 > URL: https://issues.apache.org/jira/browse/AMBARI-19449 > Project: Ambari > Issue Type: Task > Components: stacks >Reporter: Zhiyuan Yang >Assignee: Zhiyuan Yang > Fix For: 2.5.0 > > Attachments: AMBARI-19449.1.patch, AMBARI-19449.2.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19449) Enable cartesian product edge by default for hive interactive in HDP 2.6 stack
[ https://issues.apache.org/jira/browse/AMBARI-19449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiyuan Yang updated AMBARI-19449: -- Attachment: AMBARI-19449.2.patch Thanks [~sumitmohanty] for review! It's only supposed to be for HDP-2.6. UpgradeCatalog250.java changes are removed in new patch. > Enable cartesian product edge by default for hive interactive in HDP 2.6 stack > -- > > Key: AMBARI-19449 > URL: https://issues.apache.org/jira/browse/AMBARI-19449 > Project: Ambari > Issue Type: Task > Components: stacks >Reporter: Zhiyuan Yang >Assignee: Zhiyuan Yang > Fix For: 2.5.0 > > Attachments: AMBARI-19449.1.patch, AMBARI-19449.2.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19449) Enable cartesian product edge by default for hive interactive in HDP 2.6 stack
[
https://issues.apache.org/jira/browse/AMBARI-19449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15816110#comment-15816110
]
Sumit Mohanty commented on AMBARI-19449:
The {{UpgradeCatalog250.java}} change seems unconditional - as it it will
update even if HDP-2.5 is deployed where as the configuration is only added for
HDP-2.6.
CC - [~sseth]
> Enable cartesian product edge by default for hive interactive in HDP 2.6 stack
> --
>
> Key: AMBARI-19449
> URL: https://issues.apache.org/jira/browse/AMBARI-19449
> Project: Ambari
> Issue Type: Task
> Components: stacks
>Reporter: Zhiyuan Yang
>Assignee: Zhiyuan Yang
> Fix For: 2.5.0
>
> Attachments: AMBARI-19449.1.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19449) Enable cartesian product edge by default for hive interactive in HDP 2.6 stack
[ https://issues.apache.org/jira/browse/AMBARI-19449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-19449: --- Assignee: Zhiyuan Yang > Enable cartesian product edge by default for hive interactive in HDP 2.6 stack > -- > > Key: AMBARI-19449 > URL: https://issues.apache.org/jira/browse/AMBARI-19449 > Project: Ambari > Issue Type: Task > Components: stacks >Reporter: Zhiyuan Yang >Assignee: Zhiyuan Yang > Fix For: 2.5.0 > > Attachments: AMBARI-19449.1.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19427) Ambari-server: Annotate PASSWORD properties with an attribute to indicate that they are credential store aware properties
[
https://issues.apache.org/jira/browse/AMBARI-19427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15816029#comment-15816029
]
Hudson commented on AMBARI-19427:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #681 (See
[https://builds.apache.org/job/Ambari-branch-2.5/681/])
AMBARI-19427: Ambari-server - Annotate PASSWORD properties with an
(nsomasundaram:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=b2541ddb5441938fe9e2ce766559c4a92fdb])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/ConfigHelper.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/ValueAttributesInfo.java
> Ambari-server: Annotate PASSWORD properties with an attribute to indicate
> that they are credential store aware properties
> -
>
> Key: AMBARI-19427
> URL: https://issues.apache.org/jira/browse/AMBARI-19427
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb55348.patch
>
>
> In service configuration files, password properties are of type PASSWORD.
> When credential store usage is enabled for the feature, all such properties
> will be encrypted and placed in the configuration's JCEKS provider and will
> not be available in plain text in the command JSON.
> However, there are situations where certain password properties should not be
> moved into the configuration's JCEKS provider but left as plain text in the
> command JSON for clients which are not credential store aware to consume.
> To take of this, password properties that are to be moved to JCEKS provider
> should be annotated with a new attribute, "keystore" to explicitly indicate
> that these properties are credential store aware.
> {code}
>
> oozie.service.JPAService.jdbc.password
>
> Database Password
> PASSWORD
>
> DB user password.
> IMPORTANT: if password is emtpy leave a 1 space string, the service
> trims the value,
> if empty Configuration assumes it is NULL.
>
>
> password
> false
> *true*
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19447) Handle cancelling of add/delete component by user
[ https://issues.apache.org/jira/browse/AMBARI-19447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15815962#comment-15815962 ] Hudson commented on AMBARI-19447: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6400 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6400/]) AMBARI-19447 Handle cancelling of add/delete component by user. (ababiichuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=8f8582bb81b18e703c83b7f634ee489fab8f1f71]) * (edit) ambari-web/test/controllers/main/host/details_test.js * (edit) ambari-web/app/controllers/main/host/details.js > Handle cancelling of add/delete component by user > - > > Key: AMBARI-19447 > URL: https://issues.apache.org/jira/browse/AMBARI-19447 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19447_trunk.patch > > > *STR* > # Attempt to add/delete any host component that potentially requires configs > changes. > # Close confirmation popup before configs request is complete. > # Repeat (1) for other component that potentially requires configs changes. > *Result* > Properties affected by the first component are displayed inside the > confirmation popup for the second one. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19449) Enable cartesian product edge by default for hive interactive in HDP 2.6 stack
[ https://issues.apache.org/jira/browse/AMBARI-19449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiyuan Yang updated AMBARI-19449: -- Attachment: AMBARI-19449.1.patch [~sumitmohanty] How can I assign this jira to myself? Also would you mind giving it a review? Thanks! > Enable cartesian product edge by default for hive interactive in HDP 2.6 stack > -- > > Key: AMBARI-19449 > URL: https://issues.apache.org/jira/browse/AMBARI-19449 > Project: Ambari > Issue Type: Task > Components: stacks >Reporter: Zhiyuan Yang > Fix For: 2.5.0 > > Attachments: AMBARI-19449.1.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19427) Ambari-server: Annotate PASSWORD properties with an attribute to indicate that they are credential store aware properties
[
https://issues.apache.org/jira/browse/AMBARI-19427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nahappan Somasundaram updated AMBARI-19427:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Ambari-server: Annotate PASSWORD properties with an attribute to indicate
> that they are credential store aware properties
> -
>
> Key: AMBARI-19427
> URL: https://issues.apache.org/jira/browse/AMBARI-19427
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb55348.patch
>
>
> In service configuration files, password properties are of type PASSWORD.
> When credential store usage is enabled for the feature, all such properties
> will be encrypted and placed in the configuration's JCEKS provider and will
> not be available in plain text in the command JSON.
> However, there are situations where certain password properties should not be
> moved into the configuration's JCEKS provider but left as plain text in the
> command JSON for clients which are not credential store aware to consume.
> To take of this, password properties that are to be moved to JCEKS provider
> should be annotated with a new attribute, "keystore" to explicitly indicate
> that these properties are credential store aware.
> {code}
>
> oozie.service.JPAService.jdbc.password
>
> Database Password
> PASSWORD
>
> DB user password.
> IMPORTANT: if password is emtpy leave a 1 space string, the service
> trims the value,
> if empty Configuration assumes it is NULL.
>
>
> password
> false
> *true*
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19449) Enable cartesian product edge by default for hive interactive in HDP 2.6 stack
[ https://issues.apache.org/jira/browse/AMBARI-19449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiyuan Yang updated AMBARI-19449: -- Fix Version/s: 2.5.0 > Enable cartesian product edge by default for hive interactive in HDP 2.6 stack > -- > > Key: AMBARI-19449 > URL: https://issues.apache.org/jira/browse/AMBARI-19449 > Project: Ambari > Issue Type: Task > Components: stacks >Reporter: Zhiyuan Yang > Fix For: 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19449) Enable cartesian product edge by default for hive interactive in HDP 2.6 stack
[ https://issues.apache.org/jira/browse/AMBARI-19449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiyuan Yang updated AMBARI-19449: -- Component/s: stacks > Enable cartesian product edge by default for hive interactive in HDP 2.6 stack > -- > > Key: AMBARI-19449 > URL: https://issues.apache.org/jira/browse/AMBARI-19449 > Project: Ambari > Issue Type: Task > Components: stacks >Reporter: Zhiyuan Yang > Fix For: 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19449) Enable cartesian product edge by default for hive interactive in HDP 2.6 stack
Zhiyuan Yang created AMBARI-19449: - Summary: Enable cartesian product edge by default for hive interactive in HDP 2.6 stack Key: AMBARI-19449 URL: https://issues.apache.org/jira/browse/AMBARI-19449 Project: Ambari Issue Type: Task Reporter: Zhiyuan Yang -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19427) Ambari-server: Annotate PASSWORD properties with an attribute to indicate that they are credential store aware properties
[
https://issues.apache.org/jira/browse/AMBARI-19427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15815883#comment-15815883
]
Hudson commented on AMBARI-19427:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6399 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6399/])
AMBARI-19427: Ambari-server - Annotate PASSWORD properties with an
(nsomasundaram:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e65996f94d5c5d7d2b398f76fda18f4e01a4bf00])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/ConfigHelper.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/ValueAttributesInfo.java
> Ambari-server: Annotate PASSWORD properties with an attribute to indicate
> that they are credential store aware properties
> -
>
> Key: AMBARI-19427
> URL: https://issues.apache.org/jira/browse/AMBARI-19427
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb55348.patch
>
>
> In service configuration files, password properties are of type PASSWORD.
> When credential store usage is enabled for the feature, all such properties
> will be encrypted and placed in the configuration's JCEKS provider and will
> not be available in plain text in the command JSON.
> However, there are situations where certain password properties should not be
> moved into the configuration's JCEKS provider but left as plain text in the
> command JSON for clients which are not credential store aware to consume.
> To take of this, password properties that are to be moved to JCEKS provider
> should be annotated with a new attribute, "keystore" to explicitly indicate
> that these properties are credential store aware.
> {code}
>
> oozie.service.JPAService.jdbc.password
>
> Database Password
> PASSWORD
>
> DB user password.
> IMPORTANT: if password is emtpy leave a 1 space string, the service
> trims the value,
> if empty Configuration assumes it is NULL.
>
>
> password
> false
> *true*
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19248) Add Livy to HDP 2.6 as slave component of Spark2
[ https://issues.apache.org/jira/browse/AMBARI-19248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-19248: - Assignee: mingjie tang > Add Livy to HDP 2.6 as slave component of Spark2 > > > Key: AMBARI-19248 > URL: https://issues.apache.org/jira/browse/AMBARI-19248 > Project: Ambari > Issue Type: New Feature >Reporter: mingjie tang >Assignee: mingjie tang > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19447) Handle cancelling of add/delete component by user
[ https://issues.apache.org/jira/browse/AMBARI-19447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15815812#comment-15815812 ] Andrii Babiichuk commented on AMBARI-19447: --- Committed to trunk > Handle cancelling of add/delete component by user > - > > Key: AMBARI-19447 > URL: https://issues.apache.org/jira/browse/AMBARI-19447 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19447_trunk.patch > > > *STR* > # Attempt to add/delete any host component that potentially requires configs > changes. > # Close confirmation popup before configs request is complete. > # Repeat (1) for other component that potentially requires configs changes. > *Result* > Properties affected by the first component are displayed inside the > confirmation popup for the second one. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19439) Warning message when user tries to close a designer tab.
[ https://issues.apache.org/jira/browse/AMBARI-19439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15815774#comment-15815774 ] Hudson commented on AMBARI-19439: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6398 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6398/]) AMBARI-19439. Warning message when user tries to close a designer tab. (pallavkul: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f5c573a367e280cb761cbc9003283c751aac5823]) * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/designer-workspace.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/designer-workspace.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/routes/design.js > Warning message when user tries to close a designer tab. > > > Key: AMBARI-19439 > URL: https://issues.apache.org/jira/browse/AMBARI-19439 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj > Labels: WFD > Fix For: 2.5.0 > > Attachments: AMBARI-19439_trunk.patch > > > User should be warned when designer tab is closed accidentally. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19435) NodeManager restart fails during HOU if it is on same host as RM
[
https://issues.apache.org/jira/browse/AMBARI-19435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15815773#comment-15815773
]
Hudson commented on AMBARI-19435:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6398 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6398/])
AMBARI-19435 - NodeManager restart fails during HOU if it is on same (jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e10f6922eb972c581102b75d7fa50eabe0487fa2])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/ControllerModule.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/state/cluster/ClusterEffectiveVersionTest.java
* (add)
ambari-server/src/test/resources/stacks/HDP/2.1.1/services/HBASE/metainfo.xml
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/StageWrapper.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/agent/AgentResourceTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/HostOrderGrouping.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/StackUpgradeConfigurationMergeTest.java
* (edit) ambari-server/src/main/java/org/apache/ambari/server/state/Cluster.java
* (add)
ambari-server/src/main/java/org/apache/ambari/server/state/UpgradeContextFactory.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/KerberosHelperTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/metadata/RoleGraphTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/stageplanner/RoleGraph.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/UpgradeContext.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/TaskWrapper.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ActiveWidgetLayoutResourceProviderTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/state/UpgradeHelperTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/UserAuthorizationResourceProviderTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/UserResourceProviderTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java
> NodeManager restart fails during HOU if it is on same host as RM
>
>
> Key: AMBARI-19435
> URL: https://issues.apache.org/jira/browse/AMBARI-19435
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19435.patch
>
>
> *Steps*
> # Deploy HDP-2.5.0.0 cluster with Ambari-2.5.0.0 - 4 node cluster with
> NodeManager installed on all hosts, NN HA is enabled, RM HA is not enabled
> # Register 2.5.3.0 version and install the bits
> # Start HOU using API and accept manual prompts to sys-prep the hosts.
> Observe the wizard at restart task of host that runs RM and NM together
> *Result:*
> At the task to Restart Node Manager on the RM host, observed below failure:
> {code}
> 2016-12-20 18:32:39,446 -
> File['/var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid'] {'action':
> ['delete'], 'not_if': 'ambari-sudo.sh -H -E test -f
> /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid && ambari-sudo.sh -H -E
> pgrep -F /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid'}
> 2016-12-20 18:32:39,459 - Execute['ulimit -c unlimited; export
> HADOOP_LIBEXEC_DIR=/usr/hdp/2.5.3.0-37/hadoop/libexec &&
> /usr/hdp/current/hadoop-yarn-nodemanager/sbin/yarn-daemon.sh --config
> /usr/hdp/2.5.3.0-37/hadoop/conf start nodemanager'] {'not_if':
> 'ambari-sudo.sh -H -E test -f
> /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid && ambari-sudo.sh -H -E
> pgrep -F /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid', 'user': 'yarn'}
> 2016-12-20 18:32:40,558 - Execute['ambari-sudo.sh -H -E test -f
> /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid && ambari-sudo.sh -H -E
> pgrep -F /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid'] {'not_if':
> 'ambari-sudo.sh -H -E test -f
> /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid && ambari-sudo.sh -H -E
> pgrep -F /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid', 'tries': 5,
> 'try_sleep': 1}
> 2016-12-20 18:32:40,576 - Skipping Execute['ambari-sudo.sh -H -E test -f
> /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid && ambari-sudo.sh -H -E
> pgrep -F
[jira] [Commented] (AMBARI-19316) Zeppelin stop failed during EU while deleting pid file with customized service user
[
https://issues.apache.org/jira/browse/AMBARI-19316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15815776#comment-15815776
]
Hudson commented on AMBARI-19316:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6398 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6398/])
AMBARI-19316 Zeppelin stop failed during EU while deleting pid file with
(renjith.kamath:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=0b6b67024212dd559cd646b51e1cab27300e74d4])
* (edit)
ambari-server/src/test/python/stacks/2.5/ZEPPELIN/test_zeppelin_master.py
* (edit)
ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py
> Zeppelin stop failed during EU while deleting pid file with customized
> service user
> ---
>
> Key: AMBARI-19316
> URL: https://issues.apache.org/jira/browse/AMBARI-19316
> Project: Ambari
> Issue Type: Bug
> Components: ambari-upgrade
>Affects Versions: 2.5.0
>Reporter: Vivek Sharma
>Assignee: Renjith Kamath
>Priority: Critical
> Labels: express_upgrade
> Fix For: 2.5.0
>
> Attachments: AMBARI-19316-branch-2.5-v1.patch,
> AMBARI-19316-trunk-v1.patch
>
>
> *Steps*
> # Deploy HDP-2.5.0.0 cluster with Ambari-2.5.0.0 (customized service users
> enabled for all services including Zeppelin)
> # Start Express Upgrade to 2.6.0.0-267
> *Result:*
> Observed error while stopping Zeppelin notebook
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py",
> line 361, in
> Master().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 287, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py",
> line 159, in stop
> user=params.zeppelin_user)
> 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 262, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 72, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 303, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of
> '/usr/hdp/current/zeppelin-server/bin/zeppelin-daemon.sh stop >>
> /grid/0/log/zeppelin/zeppelin-setup.log' returned 1. Hortonworks
> #
> This is MOTD message, added for testing in qe infra
> rm: cannot remove
> ‘/var/run/zeppelin/zeppelin-cstm-zeppelin-ctr-e85-1482808692054-0723-01-03.hwx.site.pid’:
> Permission denied
> rm: cannot remove
> ‘/var/run/zeppelin/zeppelin-cstm-zeppelin-ctr-e85-1482808692054-0723-01-03.hwx.site.pid’:
> Permission denied
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17470) Refactor Ambari service def configurations for Zeppelin
[ https://issues.apache.org/jira/browse/AMBARI-17470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15815778#comment-15815778 ] Hudson commented on AMBARI-17470: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6398 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6398/]) AMBARI-17470 Refactor Ambari service def configurations for Zeppelin (renjith.kamath: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7244c701aff560fac24210c45b061b0c0b3ad83c]) * (edit) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/params.py * (add) ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/metainfo.xml * (add) ambari-server/src/main/resources/stacks/HDP/2.6/services/ZEPPELIN/configuration/zeppelin-env.xml * (edit) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/configuration/zeppelin-env.xml * (add) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/configuration/zeppelin-log4j-properties.xml * (add) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/configuration/zeppelin-shiro-ini.xml Revert "AMBARI-17470 Refactor Ambari service def configurations for (renjith.kamath: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e15531981541372de74f94b1588edd7398ce91f5]) * (edit) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/metainfo.xml * (delete) ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/config-upgrade.xml * (delete) ambari-server/src/main/resources/stacks/HDP/2.6/services/ZEPPELIN/configuration/zeppelin-env.xml * (delete) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/configuration/zeppelin-log4j-properties.xml * (edit) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/params.py * (edit) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/configuration/zeppelin-env.xml * (delete) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/configuration/zeppelin-shiro-ini.xml > Refactor Ambari service def configurations for Zeppelin > --- > > Key: AMBARI-17470 > URL: https://issues.apache.org/jira/browse/AMBARI-17470 > Project: Ambari > Issue Type: Improvement > Components: stacks >Reporter: Yesha Vora >Assignee: Renjith Kamath > Fix For: 2.5.0 > > Attachments: AMBARI-17470-branch-2.5-v1.patch, > AMBARI-17470-branch-2.5-v2.patch > > > Zeppelin has below configuration files : > * zeppelin-env.sh > * zeppelin-site.xml > * log4j.properties > Amabri UI shows zeppelin-env.sh and zeppelin-site.xml in config page. It > should also add log4j.properties file in Ambari config page. > - Move shiro.ini and log4j.properties out of zeppelin-env configuration. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19436) Need ability to upload a file in HDFS browser.
[ https://issues.apache.org/jira/browse/AMBARI-19436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15815775#comment-15815775 ] Hudson commented on AMBARI-19436: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6398 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6398/]) AMBARI-19436. Need ability to upload a file in HDFS browser. (Padma (pallavkul: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=38b6f22eb42bf1b19c3553c2d1509b2b56983807]) * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/hdfs-browser.hbs * (add) contrib/views/wfmanager/src/main/resources/ui/tests/unit/services/hdfs-file-uploader-test.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/file-upload.js * (edit) contrib/views/wfmanager/src/main/resources/ui/externaladdons/hdfs-directory-viewer/addon/components/directory-viewer.js * (add) contrib/views/wfmanager/src/main/resources/ui/app/services/hdfs-file-uploader.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/hdfs-browser.js > Need ability to upload a file in HDFS browser. > -- > > Key: AMBARI-19436 > URL: https://issues.apache.org/jira/browse/AMBARI-19436 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj > Labels: WFD > Fix For: 2.5.0 > > Attachments: AMBARI-19436_trunk.patch > > > Need ability to upload a file in HDFS browser. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19424) Hive View 2.0: Introduction of worksheets for query editor
[ https://issues.apache.org/jira/browse/AMBARI-19424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15815771#comment-15815771 ] Hudson commented on AMBARI-19424: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6398 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6398/]) AMBARI-19424. Hive View 2.0: Introduction of worksheets for query editor (pallavkul: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d97b9d5f1c18c1467519490b42d8eceb05bba8b3]) * (edit) contrib/views/hive20/src/main/resources/ui/app/router.js * (edit) contrib/views/hive20/src/main/resources/ui/app/templates/query.hbs * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/query.js * (add) contrib/views/hive20/src/main/resources/ui/app/routes/queries.js * (edit) contrib/views/hive20/src/main/resources/ui/app/templates/components/query-result-table.hbs * (edit) contrib/views/hive20/src/main/resources/ui/app/components/query-editor.js * (edit) contrib/views/hive20/src/main/resources/ui/app/configs/top-level-tabs.js * (add) contrib/views/hive20/src/main/resources/ui/app/models/worksheet.js * (edit) contrib/views/hive20/src/main/resources/ui/app/styles/app.scss * (edit) contrib/views/hive20/src/main/resources/ui/app/components/multiple-database-search-bar.js * (add) contrib/views/hive20/src/main/resources/ui/app/templates/queries/query.hbs * (edit) contrib/views/hive20/src/main/resources/ui/app/templates/components/multiple-database-search-bar.hbs * (add) contrib/views/hive20/src/main/resources/ui/app/routes/queries/query.js * (add) contrib/views/hive20/src/main/resources/ui/app/routes/queries/index.js * (add) contrib/views/hive20/src/main/resources/ui/app/templates/queries.hbs > Hive View 2.0: Introduction of worksheets for query editor > -- > > Key: AMBARI-19424 > URL: https://issues.apache.org/jira/browse/AMBARI-19424 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Pallav Kulshreshtha >Assignee: Pallav Kulshreshtha > Fix For: 2.5.0 > > Attachments: AMBARI-19424_trunk.patch > > > Introduction of worksheets for query editor. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19248) Add Livy to HDP 2.6 as slave component of Spark2
[ https://issues.apache.org/jira/browse/AMBARI-19248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15815772#comment-15815772 ] Hudson commented on AMBARI-19248: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6398 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6398/]) AMBARI-19248. druid user does not have cd_access on historical nodes (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=5134c2dcc8d8034dea381051518e32e7936184d3]) * (edit) ambari-server/src/test/python/stacks/2.6/DRUID/test_druid.py * (edit) ambari-server/src/main/resources/common-services/DRUID/0.9.2/package/scripts/druid.py > Add Livy to HDP 2.6 as slave component of Spark2 > > > Key: AMBARI-19248 > URL: https://issues.apache.org/jira/browse/AMBARI-19248 > Project: Ambari > Issue Type: New Feature >Reporter: mingjie tang > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19251) Ambari capacity queue manager only accepts values in integers i.e not decimal values like 0.5
[ https://issues.apache.org/jira/browse/AMBARI-19251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15815777#comment-15815777 ] Hudson commented on AMBARI-19251: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6398 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6398/]) AMBARI-19251. Ambari capacity queue manager only accepts values in (pallavkul: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=6b87b44de1e2b7aefec5c6d399b0a8615608a70b]) * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/serializers.js * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/components/capacityInput.js * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/templates/capacityEditForm.hbs * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/templates/components/editLabelCapacity.hbs * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/templates/components/editQueueCapacity.hbs * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/styles/application.less > Ambari capacity queue manager only accepts values in integers i.e not decimal > values like 0.5 > - > > Key: AMBARI-19251 > URL: https://issues.apache.org/jira/browse/AMBARI-19251 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.2.0 >Reporter: Akhil PB >Assignee: Akhil PB > Fix For: 2.5.0 > > Attachments: AMBARI-19251_trunk.01.patch, > AMBARI-19251_trunk.02.patch, AMBARI-19251_trunk.03.patch, > AMBARI-19251_trunk.04.patch > > > Ambari yarn queue manager accepts only integer capacity values. > This JIRA is to enable decimal capacity support. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19445) Add macros `existsInByKey` and `notExistsInByKey`
[ https://issues.apache.org/jira/browse/AMBARI-19445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15815769#comment-15815769 ] Hudson commented on AMBARI-19445: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6398 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6398/]) AMBARI-19445. Add macros `existsInByKey` and `notExistsInByKey` (onechiporenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=67d17f060e87530b1ad7ffe47bee9eba8ce43652]) * (edit) ambari-web/test/views/main/alerts/definition_details_view_test.js * (edit) ambari-web/test/init_computed_aliases.js * (add) ambari-web/test/aliases/computed/notExistsInByKey.js * (edit) ambari-web/app/views/main/service/menu.js * (edit) ambari-web/test/app_test.js * (edit) ambari-web/app/views/main/alerts/definition_details_view.js * (edit) ambari-web/test/utils/ember_computed_test.js * (edit) ambari-web/test/views/main/host/details/host_component_view_test.js * (edit) ambari-web/app/views/main/host/details/host_component_view.js * (edit) ambari-web/test/views/main/service/menu_test.js * (edit) ambari-web/app/utils/ember_computed.js * (add) ambari-web/test/aliases/computed/existsInByKey.js > Add macros `existsInByKey` and `notExistsInByKey` > - > > Key: AMBARI-19445 > URL: https://issues.apache.org/jira/browse/AMBARI-19445 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > Attachments: AMBARI-19445.patch > > > ||existsInByKey||notExistsInByKey|| > |A computed property that returns true if dependent property exists in the > property with needed values|A computed property that returns true if > dependent property doesn't exist in the property with needed values| -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19447) Handle cancelling of add/delete component by user
[ https://issues.apache.org/jira/browse/AMBARI-19447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15815716#comment-15815716 ] Andrii Babiichuk commented on AMBARI-19447: --- Failure is not caused with the attached patch. Tested locally, ambari-web UT passed: 20389 tests complete (33 seconds) 153 tests pending > Handle cancelling of add/delete component by user > - > > Key: AMBARI-19447 > URL: https://issues.apache.org/jira/browse/AMBARI-19447 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19447_trunk.patch > > > *STR* > # Attempt to add/delete any host component that potentially requires configs > changes. > # Close confirmation popup before configs request is complete. > # Repeat (1) for other component that potentially requires configs changes. > *Result* > Properties affected by the first component are displayed inside the > confirmation popup for the second one. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19447) Handle cancelling of add/delete component by user
[
https://issues.apache.org/jira/browse/AMBARI-19447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15815703#comment-15815703
]
Hadoop QA commented on AMBARI-19447:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12846614/AMBARI-19447_trunk.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/9989//console
This message is automatically generated.
> Handle cancelling of add/delete component by user
> -
>
> Key: AMBARI-19447
> URL: https://issues.apache.org/jira/browse/AMBARI-19447
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19447_trunk.patch
>
>
> *STR*
> # Attempt to add/delete any host component that potentially requires configs
> changes.
> # Close confirmation popup before configs request is complete.
> # Repeat (1) for other component that potentially requires configs changes.
> *Result*
> Properties affected by the first component are displayed inside the
> confirmation popup for the second one.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19448) Role Command Order For HOU Is Different For Some Components
Jonathan Hurley created AMBARI-19448:
Summary: Role Command Order For HOU Is Different For Some
Components
Key: AMBARI-19448
URL: https://issues.apache.org/jira/browse/AMBARI-19448
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.5.0
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Priority: Critical
Fix For: 2.5.0
As of AMBARI-19435, HOU now uses the role command ordering to determine how to
start components on a host. This is because some components (such as
NodeManager and DataNode) require their masters to be online first in order to
register correctly. When co-located on the same host, masters and slaves must
be started in the correct order.
However, some ordering defined on the stack will not work for HOU. For example,
the stack doesn't enforce that NameNode start before DataNode. This is because
in a normal start command, the DataNode can wait for up to 30 minutes for the
NameNode to come online. During an upgrade, the upgrade logic waits to ensure
that the DataNode is online and registered before moving on. Since the role
ordering allows DataNode to start first, this start always fails during an
upgrade.
There are several ways of implementing this:
-
{code:title="Adding a new section to existing role_command_order.json}
{
"_comment" : "Record format:",
"_comment" : "blockedRole-blockedCommand: [blockerRole1-blockerCommand1 ... ",
"general_deps" : {
...
},
"host_ordered_upgrade" : {
"DATANODE-START": ["NAMENODE-START"]
}
{code}
-
{code:title="JSON directly in the upgrade pack}
true
"DATANODE-START": ["NAMENODE-START"]
{code}
- {code:title="A separate JSON file to keep the JSON out of the upgrade pack
and the stack role_command_order.json}
true
[jira] [Commented] (AMBARI-19435) NodeManager restart fails during HOU if it is on same host as RM
[
https://issues.apache.org/jira/browse/AMBARI-19435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15815697#comment-15815697
]
Hudson commented on AMBARI-19435:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #680 (See
[https://builds.apache.org/job/Ambari-branch-2.5/680/])
AMBARI-19435 - NodeManager restart fails during HOU if it is on same (jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=432ebb2b9123da5817c8c4b8a83485fc07c96562])
* (edit) ambari-server/src/main/java/org/apache/ambari/server/state/Cluster.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/UserResourceProviderTest.java
* (add)
ambari-server/src/test/resources/stacks/HDP/2.1.1/services/HBASE/metainfo.xml
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/state/UpgradeHelperTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/StackUpgradeConfigurationMergeTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/UpgradeContext.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/TaskWrapper.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/ControllerModule.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/stageplanner/RoleGraph.java
* (add)
ambari-server/src/main/java/org/apache/ambari/server/state/UpgradeContextFactory.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ActiveWidgetLayoutResourceProviderTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/metadata/RoleGraphTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/StageWrapper.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/HostOrderGrouping.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/UserAuthorizationResourceProviderTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/KerberosHelperTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/agent/AgentResourceTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/state/cluster/ClusterEffectiveVersionTest.java
> NodeManager restart fails during HOU if it is on same host as RM
>
>
> Key: AMBARI-19435
> URL: https://issues.apache.org/jira/browse/AMBARI-19435
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19435.patch
>
>
> *Steps*
> # Deploy HDP-2.5.0.0 cluster with Ambari-2.5.0.0 - 4 node cluster with
> NodeManager installed on all hosts, NN HA is enabled, RM HA is not enabled
> # Register 2.5.3.0 version and install the bits
> # Start HOU using API and accept manual prompts to sys-prep the hosts.
> Observe the wizard at restart task of host that runs RM and NM together
> *Result:*
> At the task to Restart Node Manager on the RM host, observed below failure:
> {code}
> 2016-12-20 18:32:39,446 -
> File['/var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid'] {'action':
> ['delete'], 'not_if': 'ambari-sudo.sh -H -E test -f
> /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid && ambari-sudo.sh -H -E
> pgrep -F /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid'}
> 2016-12-20 18:32:39,459 - Execute['ulimit -c unlimited; export
> HADOOP_LIBEXEC_DIR=/usr/hdp/2.5.3.0-37/hadoop/libexec &&
> /usr/hdp/current/hadoop-yarn-nodemanager/sbin/yarn-daemon.sh --config
> /usr/hdp/2.5.3.0-37/hadoop/conf start nodemanager'] {'not_if':
> 'ambari-sudo.sh -H -E test -f
> /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid && ambari-sudo.sh -H -E
> pgrep -F /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid', 'user': 'yarn'}
> 2016-12-20 18:32:40,558 - Execute['ambari-sudo.sh -H -E test -f
> /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid && ambari-sudo.sh -H -E
> pgrep -F /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid'] {'not_if':
> 'ambari-sudo.sh -H -E test -f
> /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid && ambari-sudo.sh -H -E
> pgrep -F /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid', 'tries': 5,
> 'try_sleep': 1}
> 2016-12-20 18:32:40,576 - Skipping Execute['ambari-sudo.sh -H -E test -f
> /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid && ambari-sudo.sh -H -E
> pgrep -F /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid'] due
[jira] [Commented] (AMBARI-19423) Change HostStackVersionResourceProvider to be able to install packages on single host not belonging to any cluster
[
https://issues.apache.org/jira/browse/AMBARI-19423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15815676#comment-15815676
]
Hadoop QA commented on AMBARI-19423:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12846618/AMBARI-19423.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/9987//console
This message is automatically generated.
> Change HostStackVersionResourceProvider to be able to install packages on
> single host not belonging to any cluster
> --
>
> Key: AMBARI-19423
> URL: https://issues.apache.org/jira/browse/AMBARI-19423
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Reporter: Sandor Magyari
>Assignee: Sandor Magyari
> Fix For: 2.5.0
>
> Attachments: AMBARI-19423.patch
>
>
> This improvement will create the possibility of preinstalling packages on a
> host before the host is added to a cluster for given stack and components. A
> new request parameter 'components' has to be added to
> HostStackVersionResourceProvider to be able to pass the list of components we
> want to install packages for.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19447) Handle cancelling of add/delete component by user
[
https://issues.apache.org/jira/browse/AMBARI-19447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15815661#comment-15815661
]
Hadoop QA commented on AMBARI-19447:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12846614/AMBARI-19447_trunk.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/9986//console
This message is automatically generated.
> Handle cancelling of add/delete component by user
> -
>
> Key: AMBARI-19447
> URL: https://issues.apache.org/jira/browse/AMBARI-19447
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19447_trunk.patch
>
>
> *STR*
> # Attempt to add/delete any host component that potentially requires configs
> changes.
> # Close confirmation popup before configs request is complete.
> # Repeat (1) for other component that potentially requires configs changes.
> *Result*
> Properties affected by the first component are displayed inside the
> confirmation popup for the second one.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19446) Able to skip writing configuration files when the config type doesn't exist in the command JSON file
[
https://issues.apache.org/jira/browse/AMBARI-19446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15815645#comment-15815645
]
Hadoop QA commented on AMBARI-19446:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12846608/AMBARI-19446.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/9985//console
This message is automatically generated.
> Able to skip writing configuration files when the config type doesn't exist
> in the command JSON file
>
>
> Key: AMBARI-19446
> URL: https://issues.apache.org/jira/browse/AMBARI-19446
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-19446.patch
>
>
> Able to skip writing configuration files when the config type doesn't exist
> in the command JSON file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19437) Remove anonymous bind option for Ranger User sync for LDAP/AD
[
https://issues.apache.org/jira/browse/AMBARI-19437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15815624#comment-15815624
]
Hadoop QA commented on AMBARI-19437:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12846512/AMBARI-19437.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/9984//console
This message is automatically generated.
> Remove anonymous bind option for Ranger User sync for LDAP/AD
> -
>
> Key: AMBARI-19437
> URL: https://issues.apache.org/jira/browse/AMBARI-19437
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
> Fix For: 2.5.0
>
> Attachments: AMBARI-19437.patch
>
>
> Remove config {{bind_anonymous/ranger-env.xml}} from Ranger configs as it is
> not supported.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17470) Refactor Ambari service def configurations for Zeppelin
[ https://issues.apache.org/jira/browse/AMBARI-17470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15815605#comment-15815605 ] Hudson commented on AMBARI-17470: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #679 (See [https://builds.apache.org/job/Ambari-branch-2.5/679/]) AMBARI-17470 Refactor Ambari service def configurations for Zeppelin (renjith.kamath: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e82de87947fce4b42735c7b8bebd527fa263c54d]) * (edit) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/metainfo.xml * (add) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/configuration/zeppelin-log4j-properties.xml * (add) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/configuration/zeppelin-shiro-ini.xml * (edit) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/configuration/zeppelin-env.xml * (add) ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/params.py * (add) ambari-server/src/main/resources/stacks/HDP/2.6/services/ZEPPELIN/configuration/zeppelin-env.xml > Refactor Ambari service def configurations for Zeppelin > --- > > Key: AMBARI-17470 > URL: https://issues.apache.org/jira/browse/AMBARI-17470 > Project: Ambari > Issue Type: Improvement > Components: stacks >Reporter: Yesha Vora >Assignee: Renjith Kamath > Fix For: 2.5.0 > > Attachments: AMBARI-17470-branch-2.5-v1.patch, > AMBARI-17470-branch-2.5-v2.patch > > > Zeppelin has below configuration files : > * zeppelin-env.sh > * zeppelin-site.xml > * log4j.properties > Amabri UI shows zeppelin-env.sh and zeppelin-site.xml in config page. It > should also add log4j.properties file in Ambari config page. > - Move shiro.ini and log4j.properties out of zeppelin-env configuration. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19438) Add enable delta sync property for Ranger
[
https://issues.apache.org/jira/browse/AMBARI-19438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15815604#comment-15815604
]
Hadoop QA commented on AMBARI-19438:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12846514/AMBARI-19438.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/9983//console
This message is automatically generated.
> Add enable delta sync property for Ranger
> -
>
> Key: AMBARI-19438
> URL: https://issues.apache.org/jira/browse/AMBARI-19438
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
> Fix For: 2.5.0
>
> Attachments: AMBARI-19438.patch
>
>
> Add new property {{ranger.usersync.ldap.deltasync}} under ranger-ugsync-site
> config type to enable delta-sync. Need to show it under existing Smart Config
> Tab Ranger Usersync for LDAP/AD Sub Tab.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19171) Configuring YARN with custom queues leads to misleading errors in Stack Advisor
[
https://issues.apache.org/jira/browse/AMBARI-19171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15815585#comment-15815585
]
Hadoop QA commented on AMBARI-19171:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12846551/AMBARI-19171-trunk.patch.1
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/9982//console
This message is automatically generated.
> Configuring YARN with custom queues leads to misleading errors in Stack
> Advisor
> ---
>
> Key: AMBARI-19171
> URL: https://issues.apache.org/jira/browse/AMBARI-19171
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Vivek Sharma
>Assignee: Dmytro Grinenko
>Priority: Critical
> Labels: ui
> Fix For: 2.5.0
>
> Attachments: AMBARI-19171-branch-2.5.patch.1,
> AMBARI-19171-trunk.patch, AMBARI-19171-trunk.patch.1, AMBARI-19171.patch,
> yarn1.png, yarn2.png
>
>
> Configure custom (non-default) YARN queues as per this link
> (http://hortonworks.com/hadoop-tutorial/configuring-yarn-capacity-scheduler-ambari/)
> Result: Stack Advisor gives errors related to deletion of 'default' queue
> (check screenshots - yarn1, yarn2) for various service configs like YARN,
> Hive, Tez, MR, Spark
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19440) Need ability to upload and download action asset from HDFS
[
https://issues.apache.org/jira/browse/AMBARI-19440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15815568#comment-15815568
]
Hadoop QA commented on AMBARI-19440:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12846557/0001-AMBARI-19440.-Need-ability-to-upload-and-download-ac.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/9981//console
This message is automatically generated.
> Need ability to upload and download action asset from HDFS
> --
>
> Key: AMBARI-19440
> URL: https://issues.apache.org/jira/browse/AMBARI-19440
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: M Madhan Mohan Reddy
>Assignee: M Madhan Mohan Reddy
> Labels: WFD
> Fix For: 2.5.0
>
> Attachments:
> 0001-AMBARI-19440.-Need-ability-to-upload-and-download-ac.patch
>
>
> Need ability to upload asset to a HDFS location and download later.
> a) This helps in using assets across views.
> b) Also users may upload the saved asset into git for others to use.
> This is based on inputs from Artem Ervits.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19443) Hive View 2.0: Ability to delete a database from UI
[
https://issues.apache.org/jira/browse/AMBARI-19443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15815542#comment-15815542
]
Hadoop QA commented on AMBARI-19443:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12846585/AMBARI-19443.branch-2.5.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/9980//console
This message is automatically generated.
> Hive View 2.0: Ability to delete a database from UI
> ---
>
> Key: AMBARI-19443
> URL: https://issues.apache.org/jira/browse/AMBARI-19443
> Project: Ambari
> Issue Type: Bug
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
> Fix For: 2.5.0
>
> Attachments: AMBARI-19443.branch-2.5.patch
>
>
> We should have the ability to drop a database from UI.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19435) NodeManager restart fails during HOU if it is on same host as RM
[
https://issues.apache.org/jira/browse/AMBARI-19435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-19435:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> NodeManager restart fails during HOU if it is on same host as RM
>
>
> Key: AMBARI-19435
> URL: https://issues.apache.org/jira/browse/AMBARI-19435
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19435.patch
>
>
> *Steps*
> # Deploy HDP-2.5.0.0 cluster with Ambari-2.5.0.0 - 4 node cluster with
> NodeManager installed on all hosts, NN HA is enabled, RM HA is not enabled
> # Register 2.5.3.0 version and install the bits
> # Start HOU using API and accept manual prompts to sys-prep the hosts.
> Observe the wizard at restart task of host that runs RM and NM together
> *Result:*
> At the task to Restart Node Manager on the RM host, observed below failure:
> {code}
> 2016-12-20 18:32:39,446 -
> File['/var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid'] {'action':
> ['delete'], 'not_if': 'ambari-sudo.sh -H -E test -f
> /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid && ambari-sudo.sh -H -E
> pgrep -F /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid'}
> 2016-12-20 18:32:39,459 - Execute['ulimit -c unlimited; export
> HADOOP_LIBEXEC_DIR=/usr/hdp/2.5.3.0-37/hadoop/libexec &&
> /usr/hdp/current/hadoop-yarn-nodemanager/sbin/yarn-daemon.sh --config
> /usr/hdp/2.5.3.0-37/hadoop/conf start nodemanager'] {'not_if':
> 'ambari-sudo.sh -H -E test -f
> /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid && ambari-sudo.sh -H -E
> pgrep -F /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid', 'user': 'yarn'}
> 2016-12-20 18:32:40,558 - Execute['ambari-sudo.sh -H -E test -f
> /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid && ambari-sudo.sh -H -E
> pgrep -F /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid'] {'not_if':
> 'ambari-sudo.sh -H -E test -f
> /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid && ambari-sudo.sh -H -E
> pgrep -F /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid', 'tries': 5,
> 'try_sleep': 1}
> 2016-12-20 18:32:40,576 - Skipping Execute['ambari-sudo.sh -H -E test -f
> /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid && ambari-sudo.sh -H -E
> pgrep -F /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid'] due to not_if
> 2016-12-20 18:32:40,576 - Executing NodeManager Stack Upgrade post-restart
> 2016-12-20 18:32:40,578 - NodeManager executing "yarn node -list
> -states=RUNNING" to verify the node has rejoined the cluster...
> 2016-12-20 18:32:40,578 - checked_call['yarn node -list -states=RUNNING']
> {'user': 'yarn'}
> Command failed after 1 tries
> {code}
> A retry of the failed task is successful.
> The issue looks due to the fact that RM is still down while we try to start
> NM on the host. While starting NM, we run below command to verify if NM has
> come up
> {code}
> yarn node -list -states=RUNNING
> {code}
> The command fails since it tries to connect to RM, resulting in timeout
> As a possible fix, we may need to adjust the order in HOU upgrade pack so as
> to start RM before NM in such cases.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19423) Change HostStackVersionResourceProvider to be able to install packages on single host not belonging to any cluster
[ https://issues.apache.org/jira/browse/AMBARI-19423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Magyari updated AMBARI-19423: Attachment: AMBARI-19423.patch > Change HostStackVersionResourceProvider to be able to install packages on > single host not belonging to any cluster > -- > > Key: AMBARI-19423 > URL: https://issues.apache.org/jira/browse/AMBARI-19423 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Reporter: Sandor Magyari >Assignee: Sandor Magyari > Fix For: 2.5.0 > > Attachments: AMBARI-19423.patch > > > This improvement will create the possibility of preinstalling packages on a > host before the host is added to a cluster for given stack and components. A > new request parameter 'components' has to be added to > HostStackVersionResourceProvider to be able to pass the list of components we > want to install packages for. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19423) Change HostStackVersionResourceProvider to be able to install packages on single host not belonging to any cluster
[ https://issues.apache.org/jira/browse/AMBARI-19423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Magyari updated AMBARI-19423: Status: Patch Available (was: Open) > Change HostStackVersionResourceProvider to be able to install packages on > single host not belonging to any cluster > -- > > Key: AMBARI-19423 > URL: https://issues.apache.org/jira/browse/AMBARI-19423 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Reporter: Sandor Magyari >Assignee: Sandor Magyari > Fix For: 2.5.0 > > Attachments: AMBARI-19423.patch > > > This improvement will create the possibility of preinstalling packages on a > host before the host is added to a cluster for given stack and components. A > new request parameter 'components' has to be added to > HostStackVersionResourceProvider to be able to pass the list of components we > want to install packages for. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19435) NodeManager restart fails during HOU if it is on same host as RM
[
https://issues.apache.org/jira/browse/AMBARI-19435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-19435:
-
Attachment: AMBARI-19435.patch
> NodeManager restart fails during HOU if it is on same host as RM
>
>
> Key: AMBARI-19435
> URL: https://issues.apache.org/jira/browse/AMBARI-19435
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19435.patch
>
>
> *Steps*
> # Deploy HDP-2.5.0.0 cluster with Ambari-2.5.0.0 - 4 node cluster with
> NodeManager installed on all hosts, NN HA is enabled, RM HA is not enabled
> # Register 2.5.3.0 version and install the bits
> # Start HOU using API and accept manual prompts to sys-prep the hosts.
> Observe the wizard at restart task of host that runs RM and NM together
> *Result:*
> At the task to Restart Node Manager on the RM host, observed below failure:
> {code}
> 2016-12-20 18:32:39,446 -
> File['/var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid'] {'action':
> ['delete'], 'not_if': 'ambari-sudo.sh -H -E test -f
> /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid && ambari-sudo.sh -H -E
> pgrep -F /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid'}
> 2016-12-20 18:32:39,459 - Execute['ulimit -c unlimited; export
> HADOOP_LIBEXEC_DIR=/usr/hdp/2.5.3.0-37/hadoop/libexec &&
> /usr/hdp/current/hadoop-yarn-nodemanager/sbin/yarn-daemon.sh --config
> /usr/hdp/2.5.3.0-37/hadoop/conf start nodemanager'] {'not_if':
> 'ambari-sudo.sh -H -E test -f
> /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid && ambari-sudo.sh -H -E
> pgrep -F /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid', 'user': 'yarn'}
> 2016-12-20 18:32:40,558 - Execute['ambari-sudo.sh -H -E test -f
> /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid && ambari-sudo.sh -H -E
> pgrep -F /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid'] {'not_if':
> 'ambari-sudo.sh -H -E test -f
> /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid && ambari-sudo.sh -H -E
> pgrep -F /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid', 'tries': 5,
> 'try_sleep': 1}
> 2016-12-20 18:32:40,576 - Skipping Execute['ambari-sudo.sh -H -E test -f
> /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid && ambari-sudo.sh -H -E
> pgrep -F /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid'] due to not_if
> 2016-12-20 18:32:40,576 - Executing NodeManager Stack Upgrade post-restart
> 2016-12-20 18:32:40,578 - NodeManager executing "yarn node -list
> -states=RUNNING" to verify the node has rejoined the cluster...
> 2016-12-20 18:32:40,578 - checked_call['yarn node -list -states=RUNNING']
> {'user': 'yarn'}
> Command failed after 1 tries
> {code}
> A retry of the failed task is successful.
> The issue looks due to the fact that RM is still down while we try to start
> NM on the host. While starting NM, we run below command to verify if NM has
> come up
> {code}
> yarn node -list -states=RUNNING
> {code}
> The command fails since it tries to connect to RM, resulting in timeout
> As a possible fix, we may need to adjust the order in HOU upgrade pack so as
> to start RM before NM in such cases.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19444) Log Feeder should be restarted after configuration change
[
https://issues.apache.org/jira/browse/AMBARI-19444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15815521#comment-15815521
]
Hadoop QA commented on AMBARI-19444:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12846591/AMBARI-19444.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9979//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9979//console
This message is automatically generated.
> Log Feeder should be restarted after configuration change
> --
>
> Key: AMBARI-19444
> URL: https://issues.apache.org/jira/browse/AMBARI-19444
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.5.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
> Fix For: 2.5.0
>
> Attachments: AMBARI-19444.patch
>
>
> If any of the -logsearch-conf property is modified then the
> logfeeders should be restarted to work with the updated configs
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19435) NodeManager restart fails during HOU if it is on same host as RM
[
https://issues.apache.org/jira/browse/AMBARI-19435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-19435:
-
Status: Patch Available (was: Open)
> NodeManager restart fails during HOU if it is on same host as RM
>
>
> Key: AMBARI-19435
> URL: https://issues.apache.org/jira/browse/AMBARI-19435
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
>
> *Steps*
> # Deploy HDP-2.5.0.0 cluster with Ambari-2.5.0.0 - 4 node cluster with
> NodeManager installed on all hosts, NN HA is enabled, RM HA is not enabled
> # Register 2.5.3.0 version and install the bits
> # Start HOU using API and accept manual prompts to sys-prep the hosts.
> Observe the wizard at restart task of host that runs RM and NM together
> *Result:*
> At the task to Restart Node Manager on the RM host, observed below failure:
> {code}
> 2016-12-20 18:32:39,446 -
> File['/var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid'] {'action':
> ['delete'], 'not_if': 'ambari-sudo.sh -H -E test -f
> /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid && ambari-sudo.sh -H -E
> pgrep -F /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid'}
> 2016-12-20 18:32:39,459 - Execute['ulimit -c unlimited; export
> HADOOP_LIBEXEC_DIR=/usr/hdp/2.5.3.0-37/hadoop/libexec &&
> /usr/hdp/current/hadoop-yarn-nodemanager/sbin/yarn-daemon.sh --config
> /usr/hdp/2.5.3.0-37/hadoop/conf start nodemanager'] {'not_if':
> 'ambari-sudo.sh -H -E test -f
> /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid && ambari-sudo.sh -H -E
> pgrep -F /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid', 'user': 'yarn'}
> 2016-12-20 18:32:40,558 - Execute['ambari-sudo.sh -H -E test -f
> /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid && ambari-sudo.sh -H -E
> pgrep -F /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid'] {'not_if':
> 'ambari-sudo.sh -H -E test -f
> /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid && ambari-sudo.sh -H -E
> pgrep -F /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid', 'tries': 5,
> 'try_sleep': 1}
> 2016-12-20 18:32:40,576 - Skipping Execute['ambari-sudo.sh -H -E test -f
> /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid && ambari-sudo.sh -H -E
> pgrep -F /var/run/hadoop-yarn/yarn/yarn-yarn-nodemanager.pid'] due to not_if
> 2016-12-20 18:32:40,576 - Executing NodeManager Stack Upgrade post-restart
> 2016-12-20 18:32:40,578 - NodeManager executing "yarn node -list
> -states=RUNNING" to verify the node has rejoined the cluster...
> 2016-12-20 18:32:40,578 - checked_call['yarn node -list -states=RUNNING']
> {'user': 'yarn'}
> Command failed after 1 tries
> {code}
> A retry of the failed task is successful.
> The issue looks due to the fact that RM is still down while we try to start
> NM on the host. While starting NM, we run below command to verify if NM has
> come up
> {code}
> yarn node -list -states=RUNNING
> {code}
> The command fails since it tries to connect to RM, resulting in timeout
> As a possible fix, we may need to adjust the order in HOU upgrade pack so as
> to start RM before NM in such cases.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19447) Handle cancelling of add/delete component by user
[ https://issues.apache.org/jira/browse/AMBARI-19447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-19447: -- Status: Patch Available (was: Open) > Handle cancelling of add/delete component by user > - > > Key: AMBARI-19447 > URL: https://issues.apache.org/jira/browse/AMBARI-19447 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19447_trunk.patch > > > *STR* > # Attempt to add/delete any host component that potentially requires configs > changes. > # Close confirmation popup before configs request is complete. > # Repeat (1) for other component that potentially requires configs changes. > *Result* > Properties affected by the first component are displayed inside the > confirmation popup for the second one. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19447) Handle cancelling of add/delete component by user
[ https://issues.apache.org/jira/browse/AMBARI-19447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-19447: -- Attachment: AMBARI-19447_trunk.patch > Handle cancelling of add/delete component by user > - > > Key: AMBARI-19447 > URL: https://issues.apache.org/jira/browse/AMBARI-19447 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19447_trunk.patch > > > *STR* > # Attempt to add/delete any host component that potentially requires configs > changes. > # Close confirmation popup before configs request is complete. > # Repeat (1) for other component that potentially requires configs changes. > *Result* > Properties affected by the first component are displayed inside the > confirmation popup for the second one. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19427) Ambari-server: Annotate PASSWORD properties with an attribute to indicate that they are credential store aware properties
[
https://issues.apache.org/jira/browse/AMBARI-19427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nahappan Somasundaram updated AMBARI-19427:
---
Status: Patch Available (was: Open)
> Ambari-server: Annotate PASSWORD properties with an attribute to indicate
> that they are credential store aware properties
> -
>
> Key: AMBARI-19427
> URL: https://issues.apache.org/jira/browse/AMBARI-19427
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb55348.patch
>
>
> In service configuration files, password properties are of type PASSWORD.
> When credential store usage is enabled for the feature, all such properties
> will be encrypted and placed in the configuration's JCEKS provider and will
> not be available in plain text in the command JSON.
> However, there are situations where certain password properties should not be
> moved into the configuration's JCEKS provider but left as plain text in the
> command JSON for clients which are not credential store aware to consume.
> To take of this, password properties that are to be moved to JCEKS provider
> should be annotated with a new attribute, "keystore" to explicitly indicate
> that these properties are credential store aware.
> {code}
>
> oozie.service.JPAService.jdbc.password
>
> Database Password
> PASSWORD
>
> DB user password.
> IMPORTANT: if password is emtpy leave a 1 space string, the service
> trims the value,
> if empty Configuration assumes it is NULL.
>
>
> password
> false
> *true*
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19248) Add Livy to HDP 2.6 as slave component of Spark2
[ https://issues.apache.org/jira/browse/AMBARI-19248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15815512#comment-15815512 ] Hudson commented on AMBARI-19248: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #678 (See [https://builds.apache.org/job/Ambari-branch-2.5/678/]) AMBARI-19248. druid user does not have cd_access on historical nodes (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=b1bfb25fe4ac5e61041bb1ed046a63b97f77c31f]) * (edit) ambari-server/src/main/resources/common-services/DRUID/0.9.2/package/scripts/druid.py * (edit) ambari-server/src/test/python/stacks/2.6/DRUID/test_druid.py > Add Livy to HDP 2.6 as slave component of Spark2 > > > Key: AMBARI-19248 > URL: https://issues.apache.org/jira/browse/AMBARI-19248 > Project: Ambari > Issue Type: New Feature >Reporter: mingjie tang > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19427) Ambari-server: Annotate PASSWORD properties with an attribute to indicate that they are credential store aware properties
[
https://issues.apache.org/jira/browse/AMBARI-19427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nahappan Somasundaram updated AMBARI-19427:
---
Attachment: rb55348.patch
> Ambari-server: Annotate PASSWORD properties with an attribute to indicate
> that they are credential store aware properties
> -
>
> Key: AMBARI-19427
> URL: https://issues.apache.org/jira/browse/AMBARI-19427
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb55348.patch
>
>
> In service configuration files, password properties are of type PASSWORD.
> When credential store usage is enabled for the feature, all such properties
> will be encrypted and placed in the configuration's JCEKS provider and will
> not be available in plain text in the command JSON.
> However, there are situations where certain password properties should not be
> moved into the configuration's JCEKS provider but left as plain text in the
> command JSON for clients which are not credential store aware to consume.
> To take of this, password properties that are to be moved to JCEKS provider
> should be annotated with a new attribute, "keystore" to explicitly indicate
> that these properties are credential store aware.
> {code}
>
> oozie.service.JPAService.jdbc.password
>
> Database Password
> PASSWORD
>
> DB user password.
> IMPORTANT: if password is emtpy leave a 1 space string, the service
> trims the value,
> if empty Configuration assumes it is NULL.
>
>
> password
> false
> *true*
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19447) Handle cancelling of add/delete component by user
Andrii Babiichuk created AMBARI-19447: - Summary: Handle cancelling of add/delete component by user Key: AMBARI-19447 URL: https://issues.apache.org/jira/browse/AMBARI-19447 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.5.0 Reporter: Andrii Babiichuk Assignee: Andrii Babiichuk Priority: Critical Fix For: 2.5.0 *STR* # Attempt to add/delete any host component that potentially requires configs changes. # Close confirmation popup before configs request is complete. # Repeat (1) for other component that potentially requires configs changes. *Result* Properties affected by the first component are displayed inside the confirmation popup for the second one. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19044) Install & configure Ranger plugin components independently of Ranger admin components
[
https://issues.apache.org/jira/browse/AMBARI-19044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15815449#comment-15815449
]
Hadoop QA commented on AMBARI-19044:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12846595/AMBARI-19044.1.trunk.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 23 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 ambari-web:
org.apache.ambari.server.state.cluster.AlertDataManagerTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9978//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9978//console
This message is automatically generated.
> Install & configure Ranger plugin components independently of Ranger admin
> components
> -
>
> Key: AMBARI-19044
> URL: https://issues.apache.org/jira/browse/AMBARI-19044
> Project: Ambari
> Issue Type: New Feature
> Components: ambari-server
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-19044.1.patch, AMBARI-19044.1.trunk.patch,
> AMBARI-19044.patch
>
>
> Currently, Ambari provides a single toggle button to enable Ranger plugins
> for a component. Plugin enabled results in a bunch of configuration which are
> created on backend which are tighly coupled with Ranger admin installed on
> the same cluster.
> Need to make sure plugins communicate to Ranger admin which is installed on
> separate cluster.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19428) druid user does not have cd_access on historical nodes segment cache directory
[ https://issues.apache.org/jira/browse/AMBARI-19428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-19428: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.5 > druid user does not have cd_access on historical nodes segment cache directory > -- > > Key: AMBARI-19428 > URL: https://issues.apache.org/jira/browse/AMBARI-19428 > Project: Ambari > Issue Type: Bug >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-19428.patch > > > this is a regression after the changes in AMBARI-19328. > If the parent directories are created by ambari and does not already have > cd_access for druid user, ambari fails to set proper permissions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AMBARI-19442) Ownership is changed before the creation of directory in ZEPPELIN master.py
[
https://issues.apache.org/jira/browse/AMBARI-19442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Renjith Kamath reassigned AMBARI-19442:
---
Assignee: Renjith Kamath
> Ownership is changed before the creation of directory in ZEPPELIN master.py
> ---
>
> Key: AMBARI-19442
> URL: https://issues.apache.org/jira/browse/AMBARI-19442
> Project: Ambari
> Issue Type: Bug
>Reporter: Pradarttana
>Assignee: Renjith Kamath
>Priority: Blocker
>
> ownership is changed before the creation of directory in ZEPPELIN master.py
> file :-
> /var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py
> {code}
> def configure(self, env):
> import params
> import status_params
> env.set_params(params)
> env.set_params(status_params)
> self.create_zeppelin_log_dir(env)
> self.chown_zeppelin_pid_dir(env)
> # create the pid and zeppelin dirs
> Directory([params.zeppelin_pid_dir, params.zeppelin_dir],
> owner=params.zeppelin_user,
> group=params.zeppelin_group,
> cd_access="a",
> create_parents=True,
> mode=0755
> )
> # write out zeppelin-site.xml
> XmlConfig("zeppelin-site.xml",
> conf_dir=params.conf_dir,
>
> configurations=params.config['configurations']['zeppelin-config'],
> owner=params.zeppelin_user,
> group=params.zeppelin_group
> {code}
> The Failure message :-
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py",
> line 375, in
> Master().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 287, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py",
> line 172, in start
> self.configure(env)
> File
> "/var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py",
> line 119, in configure
> self.chown_zeppelin_pid_dir(env)
> File
> "/var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py",
> line 111, in chown_zeppelin_pid_dir
> sudo=True)
> 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 262, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 72, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 303, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of 'chown -R
> cstm-zeppelin:cstm-zeppelin /var/run/zeppelin' returned 1. chown: cannot
> access '/var/run/zeppelin': No such file or directory
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19316) Zeppelin stop failed during EU while deleting pid file with customized service user
[
https://issues.apache.org/jira/browse/AMBARI-19316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15815421#comment-15815421
]
Renjith Kamath commented on AMBARI-19316:
-
committed the new patch to trunk
0b6b67024212dd559cd646b51e1cab27300e74d4
Date: Tue Jan 10 21:56:17 2017 +0530
> Zeppelin stop failed during EU while deleting pid file with customized
> service user
> ---
>
> Key: AMBARI-19316
> URL: https://issues.apache.org/jira/browse/AMBARI-19316
> Project: Ambari
> Issue Type: Bug
> Components: ambari-upgrade
>Affects Versions: 2.5.0
>Reporter: Vivek Sharma
>Assignee: Renjith Kamath
>Priority: Critical
> Labels: express_upgrade
> Fix For: 2.5.0
>
> Attachments: AMBARI-19316-branch-2.5-v1.patch,
> AMBARI-19316-trunk-v1.patch
>
>
> *Steps*
> # Deploy HDP-2.5.0.0 cluster with Ambari-2.5.0.0 (customized service users
> enabled for all services including Zeppelin)
> # Start Express Upgrade to 2.6.0.0-267
> *Result:*
> Observed error while stopping Zeppelin notebook
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py",
> line 361, in
> Master().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 287, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py",
> line 159, in stop
> user=params.zeppelin_user)
> 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 262, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 72, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 303, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of
> '/usr/hdp/current/zeppelin-server/bin/zeppelin-daemon.sh stop >>
> /grid/0/log/zeppelin/zeppelin-setup.log' returned 1. Hortonworks
> #
> This is MOTD message, added for testing in qe infra
> rm: cannot remove
> ‘/var/run/zeppelin/zeppelin-cstm-zeppelin-ctr-e85-1482808692054-0723-01-03.hwx.site.pid’:
> Permission denied
> rm: cannot remove
> ‘/var/run/zeppelin/zeppelin-cstm-zeppelin-ctr-e85-1482808692054-0723-01-03.hwx.site.pid’:
> Permission denied
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19428) druid user does not have cd_access on historical nodes segment cache directory
[ https://issues.apache.org/jira/browse/AMBARI-19428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15815425#comment-15815425 ] Sumit Mohanty commented on AMBARI-19428: LGTM, +1 > druid user does not have cd_access on historical nodes segment cache directory > -- > > Key: AMBARI-19428 > URL: https://issues.apache.org/jira/browse/AMBARI-19428 > Project: Ambari > Issue Type: Bug >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-19428.patch > > > this is a regression after the changes in AMBARI-19328. > If the parent directories are created by ambari and does not already have > cd_access for druid user, ambari fails to set proper permissions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-19316) Zeppelin stop failed during EU while deleting pid file with customized service user
[
https://issues.apache.org/jira/browse/AMBARI-19316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Renjith Kamath resolved AMBARI-19316.
-
Resolution: Fixed
> Zeppelin stop failed during EU while deleting pid file with customized
> service user
> ---
>
> Key: AMBARI-19316
> URL: https://issues.apache.org/jira/browse/AMBARI-19316
> Project: Ambari
> Issue Type: Bug
> Components: ambari-upgrade
>Affects Versions: 2.5.0
>Reporter: Vivek Sharma
>Assignee: Renjith Kamath
>Priority: Critical
> Labels: express_upgrade
> Fix For: 2.5.0
>
> Attachments: AMBARI-19316-branch-2.5-v1.patch,
> AMBARI-19316-trunk-v1.patch
>
>
> *Steps*
> # Deploy HDP-2.5.0.0 cluster with Ambari-2.5.0.0 (customized service users
> enabled for all services including Zeppelin)
> # Start Express Upgrade to 2.6.0.0-267
> *Result:*
> Observed error while stopping Zeppelin notebook
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py",
> line 361, in
> Master().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 287, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py",
> line 159, in stop
> user=params.zeppelin_user)
> 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 262, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 72, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 303, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of
> '/usr/hdp/current/zeppelin-server/bin/zeppelin-daemon.sh stop >>
> /grid/0/log/zeppelin/zeppelin-setup.log' returned 1. Hortonworks
> #
> This is MOTD message, added for testing in qe infra
> rm: cannot remove
> ‘/var/run/zeppelin/zeppelin-cstm-zeppelin-ctr-e85-1482808692054-0723-01-03.hwx.site.pid’:
> Permission denied
> rm: cannot remove
> ‘/var/run/zeppelin/zeppelin-cstm-zeppelin-ctr-e85-1482808692054-0723-01-03.hwx.site.pid’:
> Permission denied
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19251) Ambari capacity queue manager only accepts values in integers i.e not decimal values like 0.5
[ https://issues.apache.org/jira/browse/AMBARI-19251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15815382#comment-15815382 ] Hudson commented on AMBARI-19251: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #677 (See [https://builds.apache.org/job/Ambari-branch-2.5/677/]) AMBARI-19251. Ambari capacity queue manager only accepts values in (pallavkul: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=bb66b4be1cc4b8db47b8f879688f406ebf7c42d5]) * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/styles/application.less * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/templates/components/editQueueCapacity.hbs * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/templates/capacityEditForm.hbs * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/templates/components/editLabelCapacity.hbs * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/serializers.js * (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/components/capacityInput.js > Ambari capacity queue manager only accepts values in integers i.e not decimal > values like 0.5 > - > > Key: AMBARI-19251 > URL: https://issues.apache.org/jira/browse/AMBARI-19251 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.2.0 >Reporter: Akhil PB >Assignee: Akhil PB > Fix For: 2.5.0 > > Attachments: AMBARI-19251_trunk.01.patch, > AMBARI-19251_trunk.02.patch, AMBARI-19251_trunk.03.patch, > AMBARI-19251_trunk.04.patch > > > Ambari yarn queue manager accepts only integer capacity values. > This JIRA is to enable decimal capacity support. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19436) Need ability to upload a file in HDFS browser.
[ https://issues.apache.org/jira/browse/AMBARI-19436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15815381#comment-15815381 ] Hudson commented on AMBARI-19436: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #677 (See [https://builds.apache.org/job/Ambari-branch-2.5/677/]) AMBARI-19436. Need ability to upload a file in HDFS browser. (Padma (pallavkul: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=2bdc93db2532a9e624d64d6d10359f69a555c7db]) * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/hdfs-browser.js * (add) contrib/views/wfmanager/src/main/resources/ui/app/services/hdfs-file-uploader.js * (edit) contrib/views/wfmanager/src/main/resources/ui/externaladdons/hdfs-directory-viewer/addon/components/directory-viewer.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/file-upload.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/hdfs-browser.hbs * (add) contrib/views/wfmanager/src/main/resources/ui/tests/unit/services/hdfs-file-uploader-test.js > Need ability to upload a file in HDFS browser. > -- > > Key: AMBARI-19436 > URL: https://issues.apache.org/jira/browse/AMBARI-19436 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj > Labels: WFD > Fix For: 2.5.0 > > Attachments: AMBARI-19436_trunk.patch > > > Need ability to upload a file in HDFS browser. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19439) Warning message when user tries to close a designer tab.
[ https://issues.apache.org/jira/browse/AMBARI-19439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15815380#comment-15815380 ] Hudson commented on AMBARI-19439: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #677 (See [https://builds.apache.org/job/Ambari-branch-2.5/677/]) AMBARI-19439. Warning message when user tries to close a designer tab. (pallavkul: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=6127c77c9b6416db2d74668029535451c864bdaa]) * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/designer-workspace.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/routes/design.js * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/designer-workspace.hbs > Warning message when user tries to close a designer tab. > > > Key: AMBARI-19439 > URL: https://issues.apache.org/jira/browse/AMBARI-19439 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Padma Priya Nagaraj >Assignee: Padma Priya Nagaraj > Labels: WFD > Fix For: 2.5.0 > > Attachments: AMBARI-19439_trunk.patch > > > User should be warned when designer tab is closed accidentally. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
