[jira] [Updated] (AMBARI-21505) Add Exporting Hosts when Registering Host and Adding Host
[ https://issues.apache.org/jira/browse/AMBARI-21505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] JiXiang updated AMBARI-21505: - Status: Patch Available (was: Open) > Add Exporting Hosts when Registering Host and Adding Host > - > > Key: AMBARI-21505 > URL: https://issues.apache.org/jira/browse/AMBARI-21505 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Affects Versions: trunk >Reporter: JiXiang > Fix For: trunk > > Attachments: AMBARI-21505.patch, export_all_hosts.png, > export_failed_hosts.png > > > On a big cluster (e.g. on a 1000-node cluster), it's necessary to filter > hosts based on status when registering host and adding host. So add one > button to export running-hosts, registering-hosts, registered-hosts, > failed-hosts and all-hosts. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21505) Add Exporting Hosts when Registering Host and Adding Host
[ https://issues.apache.org/jira/browse/AMBARI-21505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] JiXiang updated AMBARI-21505: - Attachment: AMBARI-21505.patch export_all_hosts.png export_failed_hosts.png > Add Exporting Hosts when Registering Host and Adding Host > - > > Key: AMBARI-21505 > URL: https://issues.apache.org/jira/browse/AMBARI-21505 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Affects Versions: trunk >Reporter: JiXiang > Fix For: trunk > > Attachments: AMBARI-21505.patch, export_all_hosts.png, > export_failed_hosts.png > > > On a big cluster (e.g. on a 1000-node cluster), it's necessary to filter > hosts based on status when registering host and adding host. So add one > button to export running-hosts, registering-hosts, registered-hosts, > failed-hosts and all-hosts. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21505) Add Exporting Hosts when Registering Host and Adding Host
[ https://issues.apache.org/jira/browse/AMBARI-21505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] JiXiang updated AMBARI-21505: - Description: On a big cluster (e.g. on a 1000-node cluster), it's necessary to filter hosts based on status when registering host and adding host. So add one button to export running-hosts, registering-hosts, registered-hosts, failed-hosts and all-hosts. (was: On a big cluster (e.g. on a 1000-node cluster), it's necessary to filter hosts based on status when registering hosts. So add one button to export running-hosts, registering-hosts, registered-hosts, failed-hosts and all-hosts.) > Add Exporting Hosts when Registering Host and Adding Host > - > > Key: AMBARI-21505 > URL: https://issues.apache.org/jira/browse/AMBARI-21505 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Affects Versions: trunk >Reporter: JiXiang > Fix For: trunk > > > On a big cluster (e.g. on a 1000-node cluster), it's necessary to filter > hosts based on status when registering host and adding host. So add one > button to export running-hosts, registering-hosts, registered-hosts, > failed-hosts and all-hosts. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21505) Add Exporting Hosts when Registering Host and Adding Host
[ https://issues.apache.org/jira/browse/AMBARI-21505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] JiXiang updated AMBARI-21505: - Summary: Add Exporting Hosts when Registering Host and Adding Host (was: Add Exporting Hosts when Registering Hosts) > Add Exporting Hosts when Registering Host and Adding Host > - > > Key: AMBARI-21505 > URL: https://issues.apache.org/jira/browse/AMBARI-21505 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Affects Versions: trunk >Reporter: JiXiang > Fix For: trunk > > > On a big cluster (e.g. on a 1000-node cluster), it's necessary to filter > hosts based on status when registering hosts. So add one button to export > running-hosts, registering-hosts, registered-hosts, failed-hosts and > all-hosts. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-8706) [Building] got error npm ERR! phantomjs@1.9.12 install while building ambari-web
[
https://issues.apache.org/jira/browse/AMBARI-8706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16091043#comment-16091043
]
Ci Song commented on AMBARI-8706:
-
Did soled this problem via manually installing the phantomjs[thanks to this
comment|https://issues.apache.org/jira/browse/AMBARI-8706?focusedCommentId=14245968=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14245968].
But this problem is more a DNS configuration problem. See this post
[configuring DNS for
jvm|https://slackhacker.com/2010/07/21/how-to-set-a-custom-dns-server-with-java-system-properties/]
> [Building] got error npm ERR! phantomjs@1.9.12 install while building
> ambari-web
>
>
> Key: AMBARI-8706
> URL: https://issues.apache.org/jira/browse/AMBARI-8706
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 1.7.0
> Environment: my host os version : ubuntu12.04.5
> building ambari from source in docker platform with centos6.6
> docker version: Docker version 1.3.1, build 4e9bbfa
> CentOS version: CentOS release 6.6 (Final)
>Reporter: Fuqing Yang
>
> I try to build ambari server from source in docker platform with Centos6.6.
> I do the building with reference at
> https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Development .
> Tools needed to build Ambari have been installed sucessfully.
> I do the building as following:
> AMBARI_VERSION=1.7.0.0
> mvn versions:set -DnewVersion=${AMBARI_VERSION}
> (building command on CentOS)
> mvn -B clean install package rpm:rpm -DnewVersion=${AMBARI_VERSION}
> -DskipTests -Dpython.ver="python >= 2.6" -Preplaceurl
> =>error mesage:
> [exec] > phantomjs@1.9.12 install
> /docker_vol01/data/datadir_github/ambari/ambari-web/node_modules/phantomjs
> [exec] > node install.js
> [exec]
> [exec] Downloading
> https://bitbucket.org/ariya/phantomjs/downloads/phantomjs-1.9.8-linux-x86_64.tar.bz2
> [exec] Saving to
> /docker_vol01/data/datadir_github/ambari/ambari-web/node_modules/phantomjs/phantomjs/phantomjs-1.9.8-linux-x86_64.tar.bz2
> [exec] Receiving...
> [exec] Error making request.
> [exec] Error: connect ETIMEDOUT
> [exec] at errnoException (net.js:904:11)
> [exec] at Object.afterConnect [as oncomplete] (net.js:895:19)
> [exec]
> [exec] Please report this full log at https://github.com/Medium/phantomjs
> [exec]
> [exec]
> [exec] > ws@0.4.32 install
> /docker_vol01/data/datadir_github/ambari/ambari-web/node_modules/karma/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws
> [exec] > (node-gyp rebuild 2> builderror.log) || (exit 0)
> [exec]
> [exec] make: Entering directory
> `/docker_vol01/data/datadir_github/ambari/ambari-web/node_modules/karma/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws/build'
> [exec] CXX(target) Release/obj.target/bufferutil/src/bufferutil.o
> [exec] SOLINK_MODULE(target) Release/obj.target/bufferutil.node
> [exec] SOLINK_MODULE(target) Release/obj.target/bufferutil.node:
> Finished
> [exec] COPY Release/bufferutil.node
> [exec] CXX(target) Release/obj.target/validation/src/validation.o
> [exec] SOLINK_MODULE(target) Release/obj.target/validation.node
> [exec] npm ERR! phantomjs@1.9.12 install: `node install.js`
> [exec] npm ERR! Exit status 1
> [exec] npm ERR!
> [exec] npm ERR! Failed at the phantomjs@1.9.12 install script.
> [exec] npm ERR! This is most likely a problem with the phantomjs package,
> [exec] npm ERR! not with npm itself.
> [exec] npm ERR! Tell the author that this fails on your system:
> [exec] npm ERR! node install.js
> [exec] npm ERR! You can get their info via:
> [exec] npm ERR! npm owner ls phantomjs
> [exec] npm ERR! There is likely additional logging output above.
> [exec]
> [exec] npm ERR! System Linux 3.13.0-32-generic
> [exec] npm ERR! command "/docker_vol01/app/node-v0.10.33-bin/bin/node"
> "/docker_vol01/app/node-v0.10.33-bin/bin/npm" "install"
> [exec] npm ERR! cwd /docker_vol01/data/datadir_github/ambari/ambari-web
> [exec] npm ERR! node -v v0.10.33
> [exec] npm ERR! npm -v 1.4.28
> [exec] npm ERR! code ELIFECYCLE
> [exec] SOLINK_MODULE(target) Release/obj.target/validation.node:
> Finished
> [exec] COPY Release/validation.node
> [exec] make: Leaving directory
> `/docker_vol01/data/datadir_github/ambari/ambari-web/node_modules/karma/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws/build'
> [exec]
> [exec] > ember-precompiler-brunch@1.4.1 postinstall
>
[jira] [Created] (AMBARI-21505) Add Exporting Hosts when Registering Hosts
JiXiang created AMBARI-21505: Summary: Add Exporting Hosts when Registering Hosts Key: AMBARI-21505 URL: https://issues.apache.org/jira/browse/AMBARI-21505 Project: Ambari Issue Type: Improvement Components: ambari-web Affects Versions: trunk Reporter: JiXiang Fix For: trunk On a big cluster (e.g. on a 1000-node cluster), it's necessary to filter hosts based on status when registering hosts. So add one button to export running-hosts, registering-hosts, registered-hosts, failed-hosts and all-hosts. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21097) Edit notifications options are always grey but can click and open a popup
[ https://issues.apache.org/jira/browse/AMBARI-21097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-21097: - Status: Patch Available (was: Reopened) > Edit notifications options are always grey but can click and open a popup > - > > Key: AMBARI-21097 > URL: https://issues.apache.org/jira/browse/AMBARI-21097 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Yao Lei >Assignee: Yao Lei > Fix For: 2.5.3 > > Attachments: AMBARI-21097.2.patch, AMBARI-21097.patch, > notification-2.png, notification.png > > > Two Problems > Steps to reproduce problem one (see notifiction.png): > 1.Open Alerts / Actions / Manage Alert Notifications > 2.Create an alert notification named test > 3.Select the created notification and click gear icon, you will find > Edit/Duplicate items are always grey but you can click and open a popup. > Steps to reproduce problem two(see notification-2.png): > 1.Open Alerts / Actions / Manage Alert Notifications and delete all > notifications if exit > 2.Firstly click the gear icon and then click Edit(Duplicate) item,some errors > ouput in browser console. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Reopened] (AMBARI-21097) Edit notifications options are always grey but can click and open a popup
[ https://issues.apache.org/jira/browse/AMBARI-21097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei reopened AMBARI-21097: -- > Edit notifications options are always grey but can click and open a popup > - > > Key: AMBARI-21097 > URL: https://issues.apache.org/jira/browse/AMBARI-21097 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Yao Lei >Assignee: Yao Lei > Fix For: 2.5.3 > > Attachments: AMBARI-21097.2.patch, AMBARI-21097.patch, > notification-2.png, notification.png > > > Two Problems > Steps to reproduce problem one (see notifiction.png): > 1.Open Alerts / Actions / Manage Alert Notifications > 2.Create an alert notification named test > 3.Select the created notification and click gear icon, you will find > Edit/Duplicate items are always grey but you can click and open a popup. > Steps to reproduce problem two(see notification-2.png): > 1.Open Alerts / Actions / Manage Alert Notifications and delete all > notifications if exit > 2.Firstly click the gear icon and then click Edit(Duplicate) item,some errors > ouput in browser console. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21097) Edit notifications options are always grey but can click and open a popup
[ https://issues.apache.org/jira/browse/AMBARI-21097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-21097: - Fix Version/s: (was: 2.5.2) 2.5.3 > Edit notifications options are always grey but can click and open a popup > - > > Key: AMBARI-21097 > URL: https://issues.apache.org/jira/browse/AMBARI-21097 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Yao Lei >Assignee: Yao Lei > Fix For: 2.5.3 > > Attachments: AMBARI-21097.2.patch, AMBARI-21097.patch, > notification-2.png, notification.png > > > Two Problems > Steps to reproduce problem one (see notifiction.png): > 1.Open Alerts / Actions / Manage Alert Notifications > 2.Create an alert notification named test > 3.Select the created notification and click gear icon, you will find > Edit/Duplicate items are always grey but you can click and open a popup. > Steps to reproduce problem two(see notification-2.png): > 1.Open Alerts / Actions / Manage Alert Notifications and delete all > notifications if exit > 2.Firstly click the gear icon and then click Edit(Duplicate) item,some errors > ouput in browser console. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21498) DB consistency checker throws errors for missing 'product-info' configs after Ambari upgrade
[
https://issues.apache.org/jira/browse/AMBARI-21498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16090955#comment-16090955
]
Hadoop QA commented on AMBARI-21498:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12877606/AMBARI-21498.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 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11805//console
This message is automatically generated.
> DB consistency checker throws errors for missing 'product-info' configs after
> Ambari upgrade
>
>
> Key: AMBARI-21498
> URL: https://issues.apache.org/jira/browse/AMBARI-21498
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Fix For: 2.5.3
>
> Attachments: AMBARI-21498.patch
>
>
> DB consistency checker throws errors for missing 'product-info' configs after
> Ambari upgrade
> AMBARI-21364 fixed the missing 'parquet-logging' but 'product-info' is still
> missing for Smartsense
> STR
> Deployed cluster with Ambari version: 2.5.1.0-159 and HDP version: 2.6.1.0-129
> Upgrade Ambari to 2.5.2.0-105
> Run "ambari-server start"
> Live openstack cluster : 172.22.124.150 (Ambari Server)
> ambari-server-check-database.log
> {code}
> 2017-07-07 18:09:05,678 ERROR - Required config(s): product-info is(are) not
> available for service SMARTSENSE with service config version 1 in cluster cl1
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21501) Make HSI's 'hive.llap.zk.sm.keytab' and 'hive.service.keytab' group readable.
[ https://issues.apache.org/jira/browse/AMBARI-21501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16090952#comment-16090952 ] Hudson commented on AMBARI-21501: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit # (See [https://builds.apache.org/job/Ambari-trunk-Commit//]) AMBARI-21501. Make HSI's 'hive.llap.zk.sm.keytab' and (sshridhar: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f450eba5c23c0d35ab9181d531d9e1ef84cbf3e8]) * (delete) ambari-server/src/main/resources/stacks/HDP/2.6/services/HIVE/kerberos.json * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/YARN/kerberos.json > Make HSI's 'hive.llap.zk.sm.keytab' and 'hive.service.keytab' group readable. > - > > Key: AMBARI-21501 > URL: https://issues.apache.org/jira/browse/AMBARI-21501 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.1 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Blocker > Fix For: trunk, 2.5.2 > > Attachments: AMBARI-21501.patch > > > As part of multiple fixes in AMBARI-21445, HSI's 'hive.llap.zk.sm.keytab' and > 'hive.service.keytab' were made non-group readable, which caused LLAP > deployment failures. > Reverting this specific sub change. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21502) Cross-stack migration from BigInsights to HDP, EU needs to set hive-site custom.hive.warehouse.mode to 0770
[ https://issues.apache.org/jira/browse/AMBARI-21502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16090942#comment-16090942 ] Hudson commented on AMBARI-21502: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1706 (See [https://builds.apache.org/job/Ambari-branch-2.5/1706/]) AMBARI-21502. Cross-stack migration from BigInsights to HDP, EU needs to (afernandez: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d8a5bad1b4b67367818646e7b65a2419021bb420]) * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.2.5/upgrades/nonrolling-upgrade-to-hdp-2.6.xml * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.2.5/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.2/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.2/upgrades/nonrolling-upgrade-to-hdp-2.6.xml > Cross-stack migration from BigInsights to HDP, EU needs to set hive-site > custom.hive.warehouse.mode to 0770 > --- > > Key: AMBARI-21502 > URL: https://issues.apache.org/jira/browse/AMBARI-21502 > Project: Ambari > Issue Type: Bug > Components: express-upgrade, stacks >Affects Versions: 2.5.2 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez >Priority: Blocker > Labels: AMBARI-21348 > Fix For: 2.5.2 > > Attachments: AMBARI-21502.patch > > > During cross stack upgrade from BigInsights, if user has not set > custom.hive.warehouse.mode in hive-site, as the default value is changed in > HDFS from BigInsights default (0770) to HDP default (0777). > EU should set the value of custom.hive.warehouse.mode to 0770. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21501) Make HSI's 'hive.llap.zk.sm.keytab' and 'hive.service.keytab' group readable.
[ https://issues.apache.org/jira/browse/AMBARI-21501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16090941#comment-16090941 ] Hudson commented on AMBARI-21501: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1706 (See [https://builds.apache.org/job/Ambari-branch-2.5/1706/]) AMBARI-21501. Make HSI's 'hive.llap.zk.sm.keytab' and (sshridhar: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=9cd7fbe0af5fc3dba0a6bd553b55ceb7ae8b70cf]) * (delete) ambari-server/src/main/resources/stacks/HDP/2.6/services/HIVE/kerberos.json * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/YARN/kerberos.json > Make HSI's 'hive.llap.zk.sm.keytab' and 'hive.service.keytab' group readable. > - > > Key: AMBARI-21501 > URL: https://issues.apache.org/jira/browse/AMBARI-21501 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.1 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Blocker > Fix For: trunk, 2.5.2 > > Attachments: AMBARI-21501.patch > > > As part of multiple fixes in AMBARI-21445, HSI's 'hive.llap.zk.sm.keytab' and > 'hive.service.keytab' were made non-group readable, which caused LLAP > deployment failures. > Reverting this specific sub change. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21504) Restart of MR2 History Server failed due to null in immutable_paths
[
https://issues.apache.org/jira/browse/AMBARI-21504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16090906#comment-16090906
]
Hadoop QA commented on AMBARI-21504:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12877662/AMBARI-21504.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11804//console
This message is automatically generated.
> Restart of MR2 History Server failed due to null in immutable_paths
> ---
>
> Key: AMBARI-21504
> URL: https://issues.apache.org/jira/browse/AMBARI-21504
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.5.2
>
> Attachments: AMBARI-21504.patch
>
>
> Steps:
> * Installed Ambari 2.2 with Slider and services it required
> * Upgraded Ambari to 2.5.2.0-134
> * Registered HDP 2.6.1.0 repo, installed packages
> * Restarted services that needed restart
> * Ran service checks
> * Started upgrade
> Result: _Restarting History Server_ step failed with
> {noformat:title=errors-91.txt}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/historyserver.py",
> line 134, in
> HistoryServer().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 329, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 841, in restart
> self.pre_upgrade_restart(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/historyserver.py",
> line 85, in pre_upgrade_restart
> copy_to_hdfs("mapreduce", params.user_group, params.hdfs_user,
> skip=params.sysprep_skip_copy_tarballs_hdfs)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/copy_tarball.py",
> line 256, in copy_to_hdfs
> mode=0555
> 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/libraries/providers/hdfs_resource.py",
> line 560, in action_create_on_execute
> self.action_delayed("create")
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 550, in action_delayed
> parsed_not_managed_paths = [HdfsResourceProvider.parse_path(path) for
> path in self.resource.immutable_paths]
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 519, in parse_path
> math_with_protocol_and_nn_url = re.match("[a-zA-Z]+://[^/]+(/.+)", path)
> File "/usr/lib64/python2.7/re.py", line 137, in match
> return _compile(pattern, flags).match(string)
> TypeError: expected string or buffer
> {noformat}
> {noformat:title=command-91.json}
> "hostLevelParams": {
> ...
> "not_managed_hdfs_path_list": "[null,\"/mr-history/done\",\"/app-logs\"]",
> ...
> }
> {noformat}
> Failure seems to be due to {{null}} value in the list.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21502) Cross-stack migration from BigInsights to HDP, EU needs to set hive-site custom.hive.warehouse.mode to 0770
[ https://issues.apache.org/jira/browse/AMBARI-21502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-21502: - Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to branch-2.5, commit d8a5bad1b4b67367818646e7b65a2419021bb420 > Cross-stack migration from BigInsights to HDP, EU needs to set hive-site > custom.hive.warehouse.mode to 0770 > --- > > Key: AMBARI-21502 > URL: https://issues.apache.org/jira/browse/AMBARI-21502 > Project: Ambari > Issue Type: Bug > Components: express-upgrade, stacks >Affects Versions: 2.5.2 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez >Priority: Blocker > Labels: AMBARI-21348 > Fix For: 2.5.2 > > Attachments: AMBARI-21502.patch > > > During cross stack upgrade from BigInsights, if user has not set > custom.hive.warehouse.mode in hive-site, as the default value is changed in > HDFS from BigInsights default (0770) to HDP default (0777). > EU should set the value of custom.hive.warehouse.mode to 0770. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21325) Ability to switch Quick Links to use Service URL through Knox or given proxy
[ https://issues.apache.org/jira/browse/AMBARI-21325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16090667#comment-16090667 ] Chandana Mirashi commented on AMBARI-21325: --- [~bsari] I have not yet created review board request as one of ambari-web test failed for the previous patch. > Ability to switch Quick Links to use Service URL through Knox or given proxy > > > Key: AMBARI-21325 > URL: https://issues.apache.org/jira/browse/AMBARI-21325 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk >Reporter: Jeffrey E Rodriguez >Assignee: Chandana Mirashi > Attachments: AMBARI-21325.patch > > Original Estimate: 336h > Remaining Estimate: 336h > > Knox has the ability to proxy Hadoop user interfaces URL. Having the ability > to setup Quicklinks through Knox so instead of for example going to "Hbase > Master UI" directly we can proxy through Knox for example: > http://hdpjeff1.fyre.ibm.com:16010/master-status > can be instead go through: > https://hdpjeff1.fyre.ibm.com:8443/gateway/default/hbase/hbaseui/master-status > Here https://hdpjeff1.fyre.ibm.com:8443/gateway is the Knox gateway URL. > This will bring authentication to the UI access and would secure the UI > access. > Ideally this behavior can be set as secure going through proxy by default or > it can be turn off to go directly by Ambari Admin. > Changes added: > 1. Add new json properties knox_url, knox_path, supports_knox >a. knox_url: template to be used for urls that are proxied through Knox >b. knox_path: Knox gateway path that will be added to the proxy url. >c. supports_knox: whether link will be redirected through Knox > 2. Add above json properties to quicklinks.json > 3. Add HDFSUI & DATANODE,YARNUI & NODEUI, JOBHISTORYUI, HBASEUI, OOZIEUI, > SPARKUI services to Knox topology template. > 4. Automate protocol and port added to Knox topology file. Based on whether > SSL is enabled for the services listed above, the port and protocol in > params_linux.py will be updated. > 5. Update quick_view_link_view.js so that when Knox is installed and > support_knox is true, quicklink url follows knox url template specified in > the quicklinks.json for the service/component. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21481) Upgrading IOP cluster with Spark2 to Ambari 2.5.2 fails on start because config mapping spark2-javaopts-properties is never selected
[
https://issues.apache.org/jira/browse/AMBARI-21481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16090662#comment-16090662
]
Hudson commented on AMBARI-21481:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1705 (See
[https://builds.apache.org/job/Ambari-branch-2.5/1705/])
AMBARI-21481. Upgrading IOP cluster with Spark2 to Ambari 2.5.2 fails on
(afernandez:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=0ed09cd5342cfc4cac0d6061a7b7b9a3cef127c1])
* (edit)
ambari-server/src/main/resources/stacks/BigInsights/4.2.5/services/SPARK2/metainfo.xml
* (edit)
ambari-server/src/main/resources/stacks/BigInsights/4.2/services/SPARK/configuration/spark-javaopts-properties.xml
* (edit)
ambari-server/src/main/resources/stacks/BigInsights/4.2.5/services/SPARK2/configuration/spark2-javaopts-properties.xml
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog252.java
* (edit)
ambari-server/src/main/resources/stacks/BigInsights/4.0/services/SPARK/configuration/spark-javaopts-properties.xml
> Upgrading IOP cluster with Spark2 to Ambari 2.5.2 fails on start because
> config mapping spark2-javaopts-properties is never selected
>
>
> Key: AMBARI-21481
> URL: https://issues.apache.org/jira/browse/AMBARI-21481
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, stacks
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Labels: AMBARI-21348
> Fix For: 2.5.2
>
> Attachments: AMBARI-21481.patch
>
>
> STR:
> * Install BigInsights 4.2.5 with Spark2
> * Upgrade to Ambari 2.5.2
> * Start Ambari, which will fail in the DB consistency check
> {code}
> 2017-07-07 01:07:01,881 ERROR - You have non selected configs:
> spark2-javaopts-properties for service SPARK2 from cluster c1!
> {code}
> Looks like this config is never selected,
> {noformat}
> ambari=> SELECT sc.service_name, sc.version, sc.user_name,
> TO_TIMESTAMP(sc.create_timestamp/1000), sc.stack_id, sc.note,
> c.version AS type_version, c.version_tag, c.type_name, c.stack_id,
> TO_TIMESTAMP(c.create_timestamp/1000) AS clusterconfig_created,
> TO_TIMESTAMP(ccm.create_timestamp/1000) AS clusterconfigmapping_created,
> ccm.selected, ccm.user_name
> FROM serviceconfig sc JOIN serviceconfigmapping m ON sc.service_config_id =
> m.service_config_id
> JOIN clusterconfig c ON m.config_id = c.config_id
> JOIN clusterconfigmapping ccm ON c.type_name = ccm.type_name AND
> c.version_tag = ccm.version_tag
> WHERE sc.service_name = 'SPARK2' and c.type_name =
> 'spark2-javaopts-properties'
> ORDER BY sc.version, c.type_name;
> service_name | version | user_name| to_timestamp | stack_id
> | note| type_version | version_tag |
> type_name | stack_id | clusterconfig_created |
> clusterconfigmapping_created | selected | user_name
> --+-+++--+---+--+-++--++--+--+---
> SPARK2 | 1 | admin | 2017-07-11 20:17:01+00 |3
> | Initial configurations for Spark2 |1 | version1|
> spark2-javaopts-properties |3 | 2017-07-11 20:17:00+00 | 2017-07-11
> 20:17:01+00 |0 | admin
> SPARK2 | 2 | ambari-upgrade | 2017-07-13 20:33:50+00 |3
> | |1 | version1|
> spark2-javaopts-properties |3 | 2017-07-11 20:17:00+00 | 2017-07-11
> 20:17:01+00 |0 | admin
> (2 rows)
> {noformat}
> This is because the config type has a single config with an empty value, so
> perhaps UI never selects it.
> {code}
>
>
> content
> Spark2-javaopts-properties
>
>
>
>
> {code}
> Fix will be for Ambari 2.5.2 upgrade to select exactly once config for each
> config type if none are selected.
> The only config type to hit this issue is spark2-javaopts-properties
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21325) Ability to switch Quick Links to use Service URL through Knox or given proxy
[ https://issues.apache.org/jira/browse/AMBARI-21325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandana Mirashi updated AMBARI-21325: -- Description: Knox has the ability to proxy Hadoop user interfaces URL. Having the ability to setup Quicklinks through Knox so instead of for example going to "Hbase Master UI" directly we can proxy through Knox for example: http://hdpjeff1.fyre.ibm.com:16010/master-status can be instead go through: https://hdpjeff1.fyre.ibm.com:8443/gateway/default/hbase/hbaseui/master-status Here https://hdpjeff1.fyre.ibm.com:8443/gateway is the Knox gateway URL. This will bring authentication to the UI access and would secure the UI access. Ideally this behavior can be set as secure going through proxy by default or it can be turn off to go directly by Ambari Admin. Changes added: 1. Add new json properties knox_url, knox_path, supports_knox a. knox_url: template to be used for urls that are proxied through Knox b. knox_path: Knox gateway path that will be added to the proxy url. c. supports_knox: whether link will be redirected through Knox 2. Add above json properties to quicklinks.json 3. Add HDFSUI & DATANODE,YARNUI & NODEUI, JOBHISTORYUI, HBASEUI, OOZIEUI, SPARKUI services to Knox topology template. 4. Automate protocol and port added to Knox topology file. Based on whether SSL is enabled for the services listed above, the port and protocol in params_linux.py will be updated. 5. Update quick_view_link_view.js so that when Knox is installed and support_knox is true, quicklink url follows knox url template specified in the quicklinks.json for the service/component. was: Knox has the ability to proxy Hadoop user interfaces URL. Having the ability to setup Quicklinks through Knox so instead of for example going to "Hbase Master UI" directly we can proxy through Knox for example: http://hdpjeff1.fyre.ibm.com:16010/master-status can be instead go through: https://hdpjeff1.fyre.ibm.com:8443/gateway/default/hbase/hbaseui/master-status Here https://hdpjeff1.fyre.ibm.com:8443/gateway is the Knox gateway URL. This will bring authentication to the UI access and would secure the UI access. Ideally this behavior can be set as secure going through proxy by default or it can be turn off to go directly by Ambari Admin. Changes added: 1. Add new json properties knox_url, knox_path, supports_knox a. knox_url: template to be used for urls that are proxied through Knox b. knox_path: Knox gateway path that will be added to the proxy url. c. supports_knox: whether link will be redirected through Knox 2. Add above json properties to quicklinks.json 3. Add HDFSUI & DATANODE,YARNUI & NODEUI, JOBHISTORYUI, HBASEUI, OOZIEUI, SPARKUI services to Knox topology template. 4. Automate protocol and port added to Knox topology file. Based on whether SSL is enabled for the services listed above, the port and protocol in params_linux.py will be updated. 5. Update quick_view_link_view.js so that when Knox is installed and support_knox is true, quicklink url follows knox url template specified in the quicklinks.json for the service/component. > Ability to switch Quick Links to use Service URL through Knox or given proxy > > > Key: AMBARI-21325 > URL: https://issues.apache.org/jira/browse/AMBARI-21325 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk >Reporter: Jeffrey E Rodriguez >Assignee: Chandana Mirashi > Attachments: AMBARI-21325.patch > > Original Estimate: 336h > Remaining Estimate: 336h > > Knox has the ability to proxy Hadoop user interfaces URL. Having the ability > to setup Quicklinks through Knox so instead of for example going to "Hbase > Master UI" directly we can proxy through Knox for example: > http://hdpjeff1.fyre.ibm.com:16010/master-status > can be instead go through: > https://hdpjeff1.fyre.ibm.com:8443/gateway/default/hbase/hbaseui/master-status > Here https://hdpjeff1.fyre.ibm.com:8443/gateway is the Knox gateway URL. > This will bring authentication to the UI access and would secure the UI > access. > Ideally this behavior can be set as secure going through proxy by default or > it can be turn off to go directly by Ambari Admin. > Changes added: > 1. Add new json properties knox_url, knox_path, supports_knox >a. knox_url: template to be used for urls that are proxied through Knox >b. knox_path: Knox gateway path that will be added to the proxy url. >c. supports_knox: whether link will be redirected through Knox > 2. Add above json properties to quicklinks.json > 3. Add HDFSUI & DATANODE,YARNUI & NODEUI, JOBHISTORYUI, HBASEUI, OOZIEUI, > SPARKUI services to Knox topology template. > 4. Automate protocol and port added to Knox topology file. Based on whether >
[jira] [Resolved] (AMBARI-21501) Make HSI's 'hive.llap.zk.sm.keytab' and 'hive.service.keytab' group readable.
[ https://issues.apache.org/jira/browse/AMBARI-21501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar resolved AMBARI-21501. -- Resolution: Fixed > Make HSI's 'hive.llap.zk.sm.keytab' and 'hive.service.keytab' group readable. > - > > Key: AMBARI-21501 > URL: https://issues.apache.org/jira/browse/AMBARI-21501 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.1 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Blocker > Fix For: trunk, 2.5.2 > > Attachments: AMBARI-21501.patch > > > As part of multiple fixes in AMBARI-21445, HSI's 'hive.llap.zk.sm.keytab' and > 'hive.service.keytab' were made non-group readable, which caused LLAP > deployment failures. > Reverting this specific sub change. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21501) Make HSI's 'hive.llap.zk.sm.keytab' and 'hive.service.keytab' group readable.
[
https://issues.apache.org/jira/browse/AMBARI-21501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16090658#comment-16090658
]
Swapan Shridhar commented on AMBARI-21501:
--
commit
trunk:
{code}
commit f450eba5c23c0d35ab9181d531d9e1ef84cbf3e8
Author: Swapan Shridhar
Date: Mon Jul 17 15:04:37 2017 -0700
AMBARI-21501. Make HSI's 'hive.llap.zk.sm.keytab' and 'hive.service.keytab'
group readable.
{code}
branch-2.5:
{code}
commit 9cd7fbe0af5fc3dba0a6bd553b55ceb7ae8b70cf
Author: Swapan Shridhar
Date: Mon Jul 17 12:15:19 2017 -0700
AMBARI-21501. Make HSI's 'hive.llap.zk.sm.keytab' and 'hive.service.keytab'
group readable.
{code}
> Make HSI's 'hive.llap.zk.sm.keytab' and 'hive.service.keytab' group readable.
> -
>
> Key: AMBARI-21501
> URL: https://issues.apache.org/jira/browse/AMBARI-21501
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.5.1
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Blocker
> Fix For: trunk, 2.5.2
>
> Attachments: AMBARI-21501.patch
>
>
> As part of multiple fixes in AMBARI-21445, HSI's 'hive.llap.zk.sm.keytab' and
> 'hive.service.keytab' were made non-group readable, which caused LLAP
> deployment failures.
> Reverting this specific sub change.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21501) Make HSI's 'hive.llap.zk.sm.keytab' and 'hive.service.keytab' group readable.
[ https://issues.apache.org/jira/browse/AMBARI-21501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16090646#comment-16090646 ] Sumit Mohanty commented on AMBARI-21501: Patch looks good, +1. > Make HSI's 'hive.llap.zk.sm.keytab' and 'hive.service.keytab' group readable. > - > > Key: AMBARI-21501 > URL: https://issues.apache.org/jira/browse/AMBARI-21501 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.1 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Blocker > Fix For: trunk, 2.5.2 > > Attachments: AMBARI-21501.patch > > > As part of multiple fixes in AMBARI-21445, HSI's 'hive.llap.zk.sm.keytab' and > 'hive.service.keytab' were made non-group readable, which caused LLAP > deployment failures. > Reverting this specific sub change. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21502) Cross-stack migration from BigInsights to HDP, EU needs to set hive-site custom.hive.warehouse.mode to 0770
[ https://issues.apache.org/jira/browse/AMBARI-21502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-21502: - Attachment: AMBARI-21502.patch > Cross-stack migration from BigInsights to HDP, EU needs to set hive-site > custom.hive.warehouse.mode to 0770 > --- > > Key: AMBARI-21502 > URL: https://issues.apache.org/jira/browse/AMBARI-21502 > Project: Ambari > Issue Type: Bug > Components: express-upgrade, stacks >Affects Versions: 2.5.2 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez >Priority: Blocker > Labels: AMBARI-21348 > Fix For: 2.5.2 > > Attachments: AMBARI-21502.patch > > > During cross stack upgrade from BigInsights, if user has not set > custom.hive.warehouse.mode in hive-site, as the default value is changed in > HDFS from BigInsights default (0770) to HDP default (0777). > EU should set the value of custom.hive.warehouse.mode to 0770. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21502) Cross-stack migration from BigInsights to HDP, EU needs to set hive-site custom.hive.warehouse.mode to 0770
[ https://issues.apache.org/jira/browse/AMBARI-21502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-21502: - Attachment: (was: AMBARI-21502.patch) > Cross-stack migration from BigInsights to HDP, EU needs to set hive-site > custom.hive.warehouse.mode to 0770 > --- > > Key: AMBARI-21502 > URL: https://issues.apache.org/jira/browse/AMBARI-21502 > Project: Ambari > Issue Type: Bug > Components: express-upgrade, stacks >Affects Versions: 2.5.2 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez >Priority: Blocker > Labels: AMBARI-21348 > Fix For: 2.5.2 > > Attachments: AMBARI-21502.patch > > > During cross stack upgrade from BigInsights, if user has not set > custom.hive.warehouse.mode in hive-site, as the default value is changed in > HDFS from BigInsights default (0770) to HDP default (0777). > EU should set the value of custom.hive.warehouse.mode to 0770. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21481) Upgrading IOP cluster with Spark2 to Ambari 2.5.2 fails on start because config mapping spark2-javaopts-properties is never selected
[
https://issues.apache.org/jira/browse/AMBARI-21481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21481:
-
Attachment: AMBARI-21481.patch
> Upgrading IOP cluster with Spark2 to Ambari 2.5.2 fails on start because
> config mapping spark2-javaopts-properties is never selected
>
>
> Key: AMBARI-21481
> URL: https://issues.apache.org/jira/browse/AMBARI-21481
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, stacks
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Labels: AMBARI-21348
> Fix For: 2.5.2
>
> Attachments: AMBARI-21481.patch
>
>
> STR:
> * Install BigInsights 4.2.5 with Spark2
> * Upgrade to Ambari 2.5.2
> * Start Ambari, which will fail in the DB consistency check
> {code}
> 2017-07-07 01:07:01,881 ERROR - You have non selected configs:
> spark2-javaopts-properties for service SPARK2 from cluster c1!
> {code}
> Looks like this config is never selected,
> {noformat}
> ambari=> SELECT sc.service_name, sc.version, sc.user_name,
> TO_TIMESTAMP(sc.create_timestamp/1000), sc.stack_id, sc.note,
> c.version AS type_version, c.version_tag, c.type_name, c.stack_id,
> TO_TIMESTAMP(c.create_timestamp/1000) AS clusterconfig_created,
> TO_TIMESTAMP(ccm.create_timestamp/1000) AS clusterconfigmapping_created,
> ccm.selected, ccm.user_name
> FROM serviceconfig sc JOIN serviceconfigmapping m ON sc.service_config_id =
> m.service_config_id
> JOIN clusterconfig c ON m.config_id = c.config_id
> JOIN clusterconfigmapping ccm ON c.type_name = ccm.type_name AND
> c.version_tag = ccm.version_tag
> WHERE sc.service_name = 'SPARK2' and c.type_name =
> 'spark2-javaopts-properties'
> ORDER BY sc.version, c.type_name;
> service_name | version | user_name| to_timestamp | stack_id
> | note| type_version | version_tag |
> type_name | stack_id | clusterconfig_created |
> clusterconfigmapping_created | selected | user_name
> --+-+++--+---+--+-++--++--+--+---
> SPARK2 | 1 | admin | 2017-07-11 20:17:01+00 |3
> | Initial configurations for Spark2 |1 | version1|
> spark2-javaopts-properties |3 | 2017-07-11 20:17:00+00 | 2017-07-11
> 20:17:01+00 |0 | admin
> SPARK2 | 2 | ambari-upgrade | 2017-07-13 20:33:50+00 |3
> | |1 | version1|
> spark2-javaopts-properties |3 | 2017-07-11 20:17:00+00 | 2017-07-11
> 20:17:01+00 |0 | admin
> (2 rows)
> {noformat}
> This is because the config type has a single config with an empty value, so
> perhaps UI never selects it.
> {code}
>
>
> content
> Spark2-javaopts-properties
>
>
>
>
> {code}
> Fix will be for Ambari 2.5.2 upgrade to select exactly once config for each
> config type if none are selected.
> The only config type to hit this issue is spark2-javaopts-properties
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21481) Upgrading IOP cluster with Spark2 to Ambari 2.5.2 fails on start because config mapping spark2-javaopts-properties is never selected
[
https://issues.apache.org/jira/browse/AMBARI-21481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21481:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Pushed to branch-2.5, commit 0ed09cd5342cfc4cac0d6061a7b7b9a3cef127c1
> Upgrading IOP cluster with Spark2 to Ambari 2.5.2 fails on start because
> config mapping spark2-javaopts-properties is never selected
>
>
> Key: AMBARI-21481
> URL: https://issues.apache.org/jira/browse/AMBARI-21481
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, stacks
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Labels: AMBARI-21348
> Fix For: 2.5.2
>
> Attachments: AMBARI-21481.patch
>
>
> STR:
> * Install BigInsights 4.2.5 with Spark2
> * Upgrade to Ambari 2.5.2
> * Start Ambari, which will fail in the DB consistency check
> {code}
> 2017-07-07 01:07:01,881 ERROR - You have non selected configs:
> spark2-javaopts-properties for service SPARK2 from cluster c1!
> {code}
> Looks like this config is never selected,
> {noformat}
> ambari=> SELECT sc.service_name, sc.version, sc.user_name,
> TO_TIMESTAMP(sc.create_timestamp/1000), sc.stack_id, sc.note,
> c.version AS type_version, c.version_tag, c.type_name, c.stack_id,
> TO_TIMESTAMP(c.create_timestamp/1000) AS clusterconfig_created,
> TO_TIMESTAMP(ccm.create_timestamp/1000) AS clusterconfigmapping_created,
> ccm.selected, ccm.user_name
> FROM serviceconfig sc JOIN serviceconfigmapping m ON sc.service_config_id =
> m.service_config_id
> JOIN clusterconfig c ON m.config_id = c.config_id
> JOIN clusterconfigmapping ccm ON c.type_name = ccm.type_name AND
> c.version_tag = ccm.version_tag
> WHERE sc.service_name = 'SPARK2' and c.type_name =
> 'spark2-javaopts-properties'
> ORDER BY sc.version, c.type_name;
> service_name | version | user_name| to_timestamp | stack_id
> | note| type_version | version_tag |
> type_name | stack_id | clusterconfig_created |
> clusterconfigmapping_created | selected | user_name
> --+-+++--+---+--+-++--++--+--+---
> SPARK2 | 1 | admin | 2017-07-11 20:17:01+00 |3
> | Initial configurations for Spark2 |1 | version1|
> spark2-javaopts-properties |3 | 2017-07-11 20:17:00+00 | 2017-07-11
> 20:17:01+00 |0 | admin
> SPARK2 | 2 | ambari-upgrade | 2017-07-13 20:33:50+00 |3
> | |1 | version1|
> spark2-javaopts-properties |3 | 2017-07-11 20:17:00+00 | 2017-07-11
> 20:17:01+00 |0 | admin
> (2 rows)
> {noformat}
> This is because the config type has a single config with an empty value, so
> perhaps UI never selects it.
> {code}
>
>
> content
> Spark2-javaopts-properties
>
>
>
>
> {code}
> Fix will be for Ambari 2.5.2 upgrade to select exactly once config for each
> config type if none are selected.
> The only config type to hit this issue is spark2-javaopts-properties
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21481) Upgrading IOP cluster with Spark2 to Ambari 2.5.2 fails on start because config mapping spark2-javaopts-properties is never selected
[
https://issues.apache.org/jira/browse/AMBARI-21481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21481:
-
Attachment: (was: AMBARI-21481.patch)
> Upgrading IOP cluster with Spark2 to Ambari 2.5.2 fails on start because
> config mapping spark2-javaopts-properties is never selected
>
>
> Key: AMBARI-21481
> URL: https://issues.apache.org/jira/browse/AMBARI-21481
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, stacks
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Labels: AMBARI-21348
> Fix For: 2.5.2
>
>
> STR:
> * Install BigInsights 4.2.5 with Spark2
> * Upgrade to Ambari 2.5.2
> * Start Ambari, which will fail in the DB consistency check
> {code}
> 2017-07-07 01:07:01,881 ERROR - You have non selected configs:
> spark2-javaopts-properties for service SPARK2 from cluster c1!
> {code}
> Looks like this config is never selected,
> {noformat}
> ambari=> SELECT sc.service_name, sc.version, sc.user_name,
> TO_TIMESTAMP(sc.create_timestamp/1000), sc.stack_id, sc.note,
> c.version AS type_version, c.version_tag, c.type_name, c.stack_id,
> TO_TIMESTAMP(c.create_timestamp/1000) AS clusterconfig_created,
> TO_TIMESTAMP(ccm.create_timestamp/1000) AS clusterconfigmapping_created,
> ccm.selected, ccm.user_name
> FROM serviceconfig sc JOIN serviceconfigmapping m ON sc.service_config_id =
> m.service_config_id
> JOIN clusterconfig c ON m.config_id = c.config_id
> JOIN clusterconfigmapping ccm ON c.type_name = ccm.type_name AND
> c.version_tag = ccm.version_tag
> WHERE sc.service_name = 'SPARK2' and c.type_name =
> 'spark2-javaopts-properties'
> ORDER BY sc.version, c.type_name;
> service_name | version | user_name| to_timestamp | stack_id
> | note| type_version | version_tag |
> type_name | stack_id | clusterconfig_created |
> clusterconfigmapping_created | selected | user_name
> --+-+++--+---+--+-++--++--+--+---
> SPARK2 | 1 | admin | 2017-07-11 20:17:01+00 |3
> | Initial configurations for Spark2 |1 | version1|
> spark2-javaopts-properties |3 | 2017-07-11 20:17:00+00 | 2017-07-11
> 20:17:01+00 |0 | admin
> SPARK2 | 2 | ambari-upgrade | 2017-07-13 20:33:50+00 |3
> | |1 | version1|
> spark2-javaopts-properties |3 | 2017-07-11 20:17:00+00 | 2017-07-11
> 20:17:01+00 |0 | admin
> (2 rows)
> {noformat}
> This is because the config type has a single config with an empty value, so
> perhaps UI never selects it.
> {code}
>
>
> content
> Spark2-javaopts-properties
>
>
>
>
> {code}
> Fix will be for Ambari 2.5.2 upgrade to select exactly once config for each
> config type if none are selected.
> The only config type to hit this issue is spark2-javaopts-properties
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21500) Support SPARK2 upgrade for BI 4.2.5 to HDP 2.6.2
[
https://issues.apache.org/jira/browse/AMBARI-21500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16090502#comment-16090502
]
Hudson commented on AMBARI-21500:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1704 (See
[https://builds.apache.org/job/Ambari-branch-2.5/1704/])
AMBARI-21500 - Support SPARK2 upgrade for BI 4.2.5 to HDP 2.6.2 (jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=13bcea0b0148d4296f7354c4ca5ba49f719caec6])
* (edit)
ambari-server/src/main/resources/stacks/BigInsights/4.2.5/upgrades/config-upgrade.xml
* (edit)
ambari-server/src/main/resources/stacks/BigInsights/4.2.5/upgrades/nonrolling-upgrade-to-hdp-2.6.xml
> Support SPARK2 upgrade for BI 4.2.5 to HDP 2.6.2
>
>
> Key: AMBARI-21500
> URL: https://issues.apache.org/jira/browse/AMBARI-21500
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.2
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.2
>
> Attachments: AMBARI-21500.patch
>
>
> SPARK2 is missing from the upgrade pack for BI 4.2.5 resulting in finalize
> operation error:
> {code}
> The following components were found to have version mismatches. Finalize
> will not complete successfully:
> c7302.ambari.apache.org: SPARK2/SPARK2_THRIFTSERVER reports 4.2.5.0-
> c7302.ambari.apache.org: SPARK2/SPARK2_CLIENT reports 4.2.5.0-
> c7302.ambari.apache.org: SPARK2/SPARK2_JOBHISTORYSERVER reports 4.2.5.0-
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21504) Restart of MR2 History Server failed due to null in immutable_paths
[
https://issues.apache.org/jira/browse/AMBARI-21504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-21504:
---
Status: Patch Available (was: Open)
> Restart of MR2 History Server failed due to null in immutable_paths
> ---
>
> Key: AMBARI-21504
> URL: https://issues.apache.org/jira/browse/AMBARI-21504
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.5.2
>
> Attachments: AMBARI-21504.patch
>
>
> Steps:
> * Installed Ambari 2.2 with Slider and services it required
> * Upgraded Ambari to 2.5.2.0-134
> * Registered HDP 2.6.1.0 repo, installed packages
> * Restarted services that needed restart
> * Ran service checks
> * Started upgrade
> Result: _Restarting History Server_ step failed with
> {noformat:title=errors-91.txt}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/historyserver.py",
> line 134, in
> HistoryServer().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 329, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 841, in restart
> self.pre_upgrade_restart(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/historyserver.py",
> line 85, in pre_upgrade_restart
> copy_to_hdfs("mapreduce", params.user_group, params.hdfs_user,
> skip=params.sysprep_skip_copy_tarballs_hdfs)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/copy_tarball.py",
> line 256, in copy_to_hdfs
> mode=0555
> 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/libraries/providers/hdfs_resource.py",
> line 560, in action_create_on_execute
> self.action_delayed("create")
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 550, in action_delayed
> parsed_not_managed_paths = [HdfsResourceProvider.parse_path(path) for
> path in self.resource.immutable_paths]
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 519, in parse_path
> math_with_protocol_and_nn_url = re.match("[a-zA-Z]+://[^/]+(/.+)", path)
> File "/usr/lib64/python2.7/re.py", line 137, in match
> return _compile(pattern, flags).match(string)
> TypeError: expected string or buffer
> {noformat}
> {noformat:title=command-91.json}
> "hostLevelParams": {
> ...
> "not_managed_hdfs_path_list": "[null,\"/mr-history/done\",\"/app-logs\"]",
> ...
> }
> {noformat}
> Failure seems to be due to {{null}} value in the list.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21504) Restart of MR2 History Server failed due to null in immutable_paths
[
https://issues.apache.org/jira/browse/AMBARI-21504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-21504:
---
Attachment: AMBARI-21504.patch
> Restart of MR2 History Server failed due to null in immutable_paths
> ---
>
> Key: AMBARI-21504
> URL: https://issues.apache.org/jira/browse/AMBARI-21504
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.5.2
>
> Attachments: AMBARI-21504.patch
>
>
> Steps:
> * Installed Ambari 2.2 with Slider and services it required
> * Upgraded Ambari to 2.5.2.0-134
> * Registered HDP 2.6.1.0 repo, installed packages
> * Restarted services that needed restart
> * Ran service checks
> * Started upgrade
> Result: _Restarting History Server_ step failed with
> {noformat:title=errors-91.txt}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/historyserver.py",
> line 134, in
> HistoryServer().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 329, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 841, in restart
> self.pre_upgrade_restart(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/historyserver.py",
> line 85, in pre_upgrade_restart
> copy_to_hdfs("mapreduce", params.user_group, params.hdfs_user,
> skip=params.sysprep_skip_copy_tarballs_hdfs)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/copy_tarball.py",
> line 256, in copy_to_hdfs
> mode=0555
> 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/libraries/providers/hdfs_resource.py",
> line 560, in action_create_on_execute
> self.action_delayed("create")
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 550, in action_delayed
> parsed_not_managed_paths = [HdfsResourceProvider.parse_path(path) for
> path in self.resource.immutable_paths]
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
> line 519, in parse_path
> math_with_protocol_and_nn_url = re.match("[a-zA-Z]+://[^/]+(/.+)", path)
> File "/usr/lib64/python2.7/re.py", line 137, in match
> return _compile(pattern, flags).match(string)
> TypeError: expected string or buffer
> {noformat}
> {noformat:title=command-91.json}
> "hostLevelParams": {
> ...
> "not_managed_hdfs_path_list": "[null,\"/mr-history/done\",\"/app-logs\"]",
> ...
> }
> {noformat}
> Failure seems to be due to {{null}} value in the list.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-21504) Restart of MR2 History Server failed due to null in immutable_paths
Vitaly Brodetskyi created AMBARI-21504:
--
Summary: Restart of MR2 History Server failed due to null in
immutable_paths
Key: AMBARI-21504
URL: https://issues.apache.org/jira/browse/AMBARI-21504
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.5.2
Reporter: Vitaly Brodetskyi
Assignee: Vitaly Brodetskyi
Priority: Blocker
Fix For: 2.5.2
Steps:
* Installed Ambari 2.2 with Slider and services it required
* Upgraded Ambari to 2.5.2.0-134
* Registered HDP 2.6.1.0 repo, installed packages
* Restarted services that needed restart
* Ran service checks
* Started upgrade
Result: _Restarting History Server_ step failed with
{noformat:title=errors-91.txt}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/historyserver.py",
line 134, in
HistoryServer().execute()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 329, in execute
method(env)
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 841, in restart
self.pre_upgrade_restart(env, upgrade_type=upgrade_type)
File
"/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/historyserver.py",
line 85, in pre_upgrade_restart
copy_to_hdfs("mapreduce", params.user_group, params.hdfs_user,
skip=params.sysprep_skip_copy_tarballs_hdfs)
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/functions/copy_tarball.py",
line 256, in copy_to_hdfs
mode=0555
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/libraries/providers/hdfs_resource.py",
line 560, in action_create_on_execute
self.action_delayed("create")
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
line 550, in action_delayed
parsed_not_managed_paths = [HdfsResourceProvider.parse_path(path) for path
in self.resource.immutable_paths]
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
line 519, in parse_path
math_with_protocol_and_nn_url = re.match("[a-zA-Z]+://[^/]+(/.+)", path)
File "/usr/lib64/python2.7/re.py", line 137, in match
return _compile(pattern, flags).match(string)
TypeError: expected string or buffer
{noformat}
{noformat:title=command-91.json}
"hostLevelParams": {
...
"not_managed_hdfs_path_list": "[null,\"/mr-history/done\",\"/app-logs\"]",
...
}
{noformat}
Failure seems to be due to {{null}} value in the list.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21325) Ability to switch Quick Links to use Service URL through Knox or given proxy
[ https://issues.apache.org/jira/browse/AMBARI-21325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16090449#comment-16090449 ] Balázs Bence Sári commented on AMBARI-21325: Hey [~cmirashi], could you please add a review board link? > Ability to switch Quick Links to use Service URL through Knox or given proxy > > > Key: AMBARI-21325 > URL: https://issues.apache.org/jira/browse/AMBARI-21325 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk >Reporter: Jeffrey E Rodriguez >Assignee: Chandana Mirashi > Attachments: AMBARI-21325.patch > > Original Estimate: 336h > Remaining Estimate: 336h > > Knox has the ability to proxy Hadoop user interfaces URL. Having the ability > to setup Quicklinks through Knox so instead of for example going to "Hbase > Master UI" directly we can proxy through Knox for example: > http://hdpjeff1.fyre.ibm.com:16010/master-status > can be instead go through: > https://hdpjeff1.fyre.ibm.com:8443/gateway/default/hbase/hbaseui/master-status > Here https://hdpjeff1.fyre.ibm.com:8443/gateway is the Knox gateway URL. > This will bring authentication to the UI access and would secure the UI > access. > Ideally this behavior can be set as secure going through proxy by default or > it can be turn off to go directly by Ambari Admin. > Changes added: > 1. Add new json properties knox_url, knox_path, supports_knox >a. knox_url: template to be used for urls that are proxied through Knox >b. knox_path: Knox gateway path that will be added to the proxy url. >c. supports_knox: whether link will be redirected through Knox > 2. Add above json properties to quicklinks.json > 3. Add HDFSUI & DATANODE,YARNUI & NODEUI, JOBHISTORYUI, HBASEUI, OOZIEUI, > SPARKUI services to Knox topology template. > 4. Automate protocol and port added to Knox topology file. Based on whether > SSL is enabled for the services listed above, the port and protocol in > params_linux.py will be updated. > 5. Update quick_view_link_view.js so that when Knox is installed and > support_knox is true, quicklink url follows knox url template specified in > the quicklinks.json for the service/component. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21500) Support SPARK2 upgrade for BI 4.2.5 to HDP 2.6.2
[
https://issues.apache.org/jira/browse/AMBARI-21500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-21500:
-
Attachment: AMBARI-21500.patch
> Support SPARK2 upgrade for BI 4.2.5 to HDP 2.6.2
>
>
> Key: AMBARI-21500
> URL: https://issues.apache.org/jira/browse/AMBARI-21500
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.2
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.2
>
> Attachments: AMBARI-21500.patch
>
>
> SPARK2 is missing from the upgrade pack for BI 4.2.5 resulting in finalize
> operation error:
> {code}
> The following components were found to have version mismatches. Finalize
> will not complete successfully:
> c7302.ambari.apache.org: SPARK2/SPARK2_THRIFTSERVER reports 4.2.5.0-
> c7302.ambari.apache.org: SPARK2/SPARK2_CLIENT reports 4.2.5.0-
> c7302.ambari.apache.org: SPARK2/SPARK2_JOBHISTORYSERVER reports 4.2.5.0-
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21500) Support SPARK2 upgrade for BI 4.2.5 to HDP 2.6.2
[
https://issues.apache.org/jira/browse/AMBARI-21500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-21500:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Support SPARK2 upgrade for BI 4.2.5 to HDP 2.6.2
>
>
> Key: AMBARI-21500
> URL: https://issues.apache.org/jira/browse/AMBARI-21500
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.2
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.2
>
> Attachments: AMBARI-21500.patch
>
>
> SPARK2 is missing from the upgrade pack for BI 4.2.5 resulting in finalize
> operation error:
> {code}
> The following components were found to have version mismatches. Finalize
> will not complete successfully:
> c7302.ambari.apache.org: SPARK2/SPARK2_THRIFTSERVER reports 4.2.5.0-
> c7302.ambari.apache.org: SPARK2/SPARK2_CLIENT reports 4.2.5.0-
> c7302.ambari.apache.org: SPARK2/SPARK2_JOBHISTORYSERVER reports 4.2.5.0-
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21500) Support SPARK2 upgrade for BI 4.2.5 to HDP 2.6.2
[
https://issues.apache.org/jira/browse/AMBARI-21500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-21500:
-
Status: Patch Available (was: Open)
> Support SPARK2 upgrade for BI 4.2.5 to HDP 2.6.2
>
>
> Key: AMBARI-21500
> URL: https://issues.apache.org/jira/browse/AMBARI-21500
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.2
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.2
>
>
> SPARK2 is missing from the upgrade pack for BI 4.2.5 resulting in finalize
> operation error:
> {code}
> The following components were found to have version mismatches. Finalize
> will not complete successfully:
> c7302.ambari.apache.org: SPARK2/SPARK2_THRIFTSERVER reports 4.2.5.0-
> c7302.ambari.apache.org: SPARK2/SPARK2_CLIENT reports 4.2.5.0-
> c7302.ambari.apache.org: SPARK2/SPARK2_JOBHISTORYSERVER reports 4.2.5.0-
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21501) Make HSI's 'hive.llap.zk.sm.keytab' and 'hive.service.keytab' group readable.
[ https://issues.apache.org/jira/browse/AMBARI-21501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16090431#comment-16090431 ] Swapan Shridhar commented on AMBARI-21501: -- [~sumitmohanty] | [~afernandez] Patch AMBARI-21501.patch for review. > Make HSI's 'hive.llap.zk.sm.keytab' and 'hive.service.keytab' group readable. > - > > Key: AMBARI-21501 > URL: https://issues.apache.org/jira/browse/AMBARI-21501 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.1 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Blocker > Fix For: trunk, 2.5.2 > > Attachments: AMBARI-21501.patch > > > As part of multiple fixes in AMBARI-21445, HSI's 'hive.llap.zk.sm.keytab' and > 'hive.service.keytab' were made non-group readable, which caused LLAP > deployment failures. > Reverting this specific sub change. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (AMBARI-21501) Make HSI's 'hive.llap.zk.sm.keytab' and 'hive.service.keytab' group readable.
[ https://issues.apache.org/jira/browse/AMBARI-21501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16090431#comment-16090431 ] Swapan Shridhar edited comment on AMBARI-21501 at 7/17/17 7:41 PM: --- [~sumitmohanty] | [~afernandez] Patch [^AMBARI-21501.patch] for review. was (Author: swapanshridhar): [~sumitmohanty] | [~afernandez] Patch AMBARI-21501.patch for review. > Make HSI's 'hive.llap.zk.sm.keytab' and 'hive.service.keytab' group readable. > - > > Key: AMBARI-21501 > URL: https://issues.apache.org/jira/browse/AMBARI-21501 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.1 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Blocker > Fix For: trunk, 2.5.2 > > Attachments: AMBARI-21501.patch > > > As part of multiple fixes in AMBARI-21445, HSI's 'hive.llap.zk.sm.keytab' and > 'hive.service.keytab' were made non-group readable, which caused LLAP > deployment failures. > Reverting this specific sub change. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21501) Make HSI's 'hive.llap.zk.sm.keytab' and 'hive.service.keytab' group readable.
[ https://issues.apache.org/jira/browse/AMBARI-21501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-21501: - Description: As part of multiple fixes in AMBARI-21445, HSI's 'hive.llap.zk.sm.keytab' and 'hive.service.keytab' were made non-group readable, which caused LLAP deployment failures. Reverting this specific sub change. was: As part of multiple fixes in AMBARI-21445, HSI's 'hive.llap.zk.sm.keytab' and 'hive.service.keytab' were made non-group readable, which cause LLAP deployment failures. Reverting this specific sub change. > Make HSI's 'hive.llap.zk.sm.keytab' and 'hive.service.keytab' group readable. > - > > Key: AMBARI-21501 > URL: https://issues.apache.org/jira/browse/AMBARI-21501 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.1 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Blocker > Fix For: trunk, 2.5.2 > > Attachments: AMBARI-21501.patch > > > As part of multiple fixes in AMBARI-21445, HSI's 'hive.llap.zk.sm.keytab' and > 'hive.service.keytab' were made non-group readable, which caused LLAP > deployment failures. > Reverting this specific sub change. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21501) Make HSI's 'hive.llap.zk.sm.keytab' and 'hive.service.keytab' group readable.
[ https://issues.apache.org/jira/browse/AMBARI-21501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-21501: - Description: As part of multiple fixes in AMBARI-21445, HSI's 'hive.llap.zk.sm.keytab' and 'hive.service.keytab' were made non-group readable, which cause LLAP deployment failures. Reverting this specific sub change. was: As part of multiple fixes in AMBARI-21445, Make HSI's 'hive.llap.zk.sm.keytab' and 'hive.service.keytab' were made non-group readable, which cause LLAP deployment failures. Reverting this specific sub change. > Make HSI's 'hive.llap.zk.sm.keytab' and 'hive.service.keytab' group readable. > - > > Key: AMBARI-21501 > URL: https://issues.apache.org/jira/browse/AMBARI-21501 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.1 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Blocker > Fix For: trunk, 2.5.2 > > Attachments: AMBARI-21501.patch > > > As part of multiple fixes in AMBARI-21445, HSI's 'hive.llap.zk.sm.keytab' and > 'hive.service.keytab' were made non-group readable, which cause LLAP > deployment failures. > Reverting this specific sub change. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21501) Make HSI's 'hive.llap.zk.sm.keytab' and 'hive.service.keytab' group readable.
[ https://issues.apache.org/jira/browse/AMBARI-21501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-21501: - Attachment: AMBARI-21501.patch > Make HSI's 'hive.llap.zk.sm.keytab' and 'hive.service.keytab' group readable. > - > > Key: AMBARI-21501 > URL: https://issues.apache.org/jira/browse/AMBARI-21501 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.1 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Blocker > Fix For: trunk, 2.5.2 > > Attachments: AMBARI-21501.patch > > > As part of multiple fixes in AMBARI-21445, Make HSI's > 'hive.llap.zk.sm.keytab' and 'hive.service.keytab' were made non-group > readable, which cause LLAP deployment failures. > Reverting this specific sub change. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21503) Add JanusGraph Service
Christopher Jackson created AMBARI-21503: Summary: Add JanusGraph Service Key: AMBARI-21503 URL: https://issues.apache.org/jira/browse/AMBARI-21503 Project: Ambari Issue Type: New Feature Reporter: Christopher Jackson Would be nice to have JanusGraph as a common-service in Ambari. Information for JanusGraph can be found at: http://janusgraph.org/ Required Services: HBASE, SOLR (create SOLR service as well, or leverage AMBARI_INFRA?) JanusGraph is a fork from Titan, IOP (IBM Open Platform) supported Titan 1.0.0 as a service in the BigInsights 4.2.5.0 stack. This work can most likely be used as a starting point for creating a janus service. Similarly BigInsights 4.2.5.0 had a standalone SOLR (6.3.0) service. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21502) Cross-stack migration from BigInsights to HDP, EU needs to set hive-site custom.hive.warehouse.mode to 0770
[ https://issues.apache.org/jira/browse/AMBARI-21502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-21502: - Attachment: AMBARI-21502.patch > Cross-stack migration from BigInsights to HDP, EU needs to set hive-site > custom.hive.warehouse.mode to 0770 > --- > > Key: AMBARI-21502 > URL: https://issues.apache.org/jira/browse/AMBARI-21502 > Project: Ambari > Issue Type: Bug > Components: express-upgrade, stacks >Affects Versions: 2.5.2 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez >Priority: Blocker > Labels: AMBARI-21348 > Fix For: 2.5.2 > > Attachments: AMBARI-21502.patch > > > During cross stack upgrade from BigInsights, if user has not set > custom.hive.warehouse.mode in hive-site, as the default value is changed in > HDFS from BigInsights default (0770) to HDP default (0777). > EU should set the value of custom.hive.warehouse.mode to 0770. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21502) Cross-stack migration from BigInsights to HDP, EU needs to set hive-site custom.hive.warehouse.mode to 0770
[ https://issues.apache.org/jira/browse/AMBARI-21502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-21502: - Status: Patch Available (was: Open) > Cross-stack migration from BigInsights to HDP, EU needs to set hive-site > custom.hive.warehouse.mode to 0770 > --- > > Key: AMBARI-21502 > URL: https://issues.apache.org/jira/browse/AMBARI-21502 > Project: Ambari > Issue Type: Bug > Components: express-upgrade, stacks >Affects Versions: 2.5.2 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez >Priority: Blocker > Labels: AMBARI-21348 > Fix For: 2.5.2 > > Attachments: AMBARI-21502.patch > > > During cross stack upgrade from BigInsights, if user has not set > custom.hive.warehouse.mode in hive-site, as the default value is changed in > HDFS from BigInsights default (0770) to HDP default (0777). > EU should set the value of custom.hive.warehouse.mode to 0770. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21502) Cross-stack migration from BigInsights to HDP, EU needs to set hive-site custom.hive.warehouse.mode to 0770
Alejandro Fernandez created AMBARI-21502: Summary: Cross-stack migration from BigInsights to HDP, EU needs to set hive-site custom.hive.warehouse.mode to 0770 Key: AMBARI-21502 URL: https://issues.apache.org/jira/browse/AMBARI-21502 Project: Ambari Issue Type: Bug Components: express-upgrade, stacks Affects Versions: 2.5.2 Reporter: Alejandro Fernandez Assignee: Alejandro Fernandez Priority: Blocker Fix For: 2.5.2 During cross stack upgrade from BigInsights, if user has not set custom.hive.warehouse.mode in hive-site, as the default value is changed in HDFS from BigInsights default (0770) to HDP default (0777). EU should set the value of custom.hive.warehouse.mode to 0770. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21481) Upgrading IOP cluster with Spark2 to Ambari 2.5.2 fails on start because config mapping spark2-javaopts-properties is never selected
[
https://issues.apache.org/jira/browse/AMBARI-21481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21481:
-
Attachment: AMBARI-21481.patch
> Upgrading IOP cluster with Spark2 to Ambari 2.5.2 fails on start because
> config mapping spark2-javaopts-properties is never selected
>
>
> Key: AMBARI-21481
> URL: https://issues.apache.org/jira/browse/AMBARI-21481
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, stacks
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Labels: AMBARI-21348
> Fix For: 2.5.2
>
> Attachments: AMBARI-21481.patch
>
>
> STR:
> * Install BigInsights 4.2.5 with Spark2
> * Upgrade to Ambari 2.5.2
> * Start Ambari, which will fail in the DB consistency check
> {code}
> 2017-07-07 01:07:01,881 ERROR - You have non selected configs:
> spark2-javaopts-properties for service SPARK2 from cluster c1!
> {code}
> Looks like this config is never selected,
> {noformat}
> ambari=> SELECT sc.service_name, sc.version, sc.user_name,
> TO_TIMESTAMP(sc.create_timestamp/1000), sc.stack_id, sc.note,
> c.version AS type_version, c.version_tag, c.type_name, c.stack_id,
> TO_TIMESTAMP(c.create_timestamp/1000) AS clusterconfig_created,
> TO_TIMESTAMP(ccm.create_timestamp/1000) AS clusterconfigmapping_created,
> ccm.selected, ccm.user_name
> FROM serviceconfig sc JOIN serviceconfigmapping m ON sc.service_config_id =
> m.service_config_id
> JOIN clusterconfig c ON m.config_id = c.config_id
> JOIN clusterconfigmapping ccm ON c.type_name = ccm.type_name AND
> c.version_tag = ccm.version_tag
> WHERE sc.service_name = 'SPARK2' and c.type_name =
> 'spark2-javaopts-properties'
> ORDER BY sc.version, c.type_name;
> service_name | version | user_name| to_timestamp | stack_id
> | note| type_version | version_tag |
> type_name | stack_id | clusterconfig_created |
> clusterconfigmapping_created | selected | user_name
> --+-+++--+---+--+-++--++--+--+---
> SPARK2 | 1 | admin | 2017-07-11 20:17:01+00 |3
> | Initial configurations for Spark2 |1 | version1|
> spark2-javaopts-properties |3 | 2017-07-11 20:17:00+00 | 2017-07-11
> 20:17:01+00 |0 | admin
> SPARK2 | 2 | ambari-upgrade | 2017-07-13 20:33:50+00 |3
> | |1 | version1|
> spark2-javaopts-properties |3 | 2017-07-11 20:17:00+00 | 2017-07-11
> 20:17:01+00 |0 | admin
> (2 rows)
> {noformat}
> This is because the config type has a single config with an empty value, so
> perhaps UI never selects it.
> {code}
>
>
> content
> Spark2-javaopts-properties
>
>
>
>
> {code}
> Fix will be for Ambari 2.5.2 upgrade to select exactly once config for each
> config type if none are selected.
> The only config type to hit this issue is spark2-javaopts-properties
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21481) Upgrading IOP cluster with Spark2 to Ambari 2.5.2 fails on start because config mapping spark2-javaopts-properties is never selected
[
https://issues.apache.org/jira/browse/AMBARI-21481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21481:
-
Attachment: (was: AMBARI-21481.patch)
> Upgrading IOP cluster with Spark2 to Ambari 2.5.2 fails on start because
> config mapping spark2-javaopts-properties is never selected
>
>
> Key: AMBARI-21481
> URL: https://issues.apache.org/jira/browse/AMBARI-21481
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, stacks
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Labels: AMBARI-21348
> Fix For: 2.5.2
>
>
> STR:
> * Install BigInsights 4.2.5 with Spark2
> * Upgrade to Ambari 2.5.2
> * Start Ambari, which will fail in the DB consistency check
> {code}
> 2017-07-07 01:07:01,881 ERROR - You have non selected configs:
> spark2-javaopts-properties for service SPARK2 from cluster c1!
> {code}
> Looks like this config is never selected,
> {noformat}
> ambari=> SELECT sc.service_name, sc.version, sc.user_name,
> TO_TIMESTAMP(sc.create_timestamp/1000), sc.stack_id, sc.note,
> c.version AS type_version, c.version_tag, c.type_name, c.stack_id,
> TO_TIMESTAMP(c.create_timestamp/1000) AS clusterconfig_created,
> TO_TIMESTAMP(ccm.create_timestamp/1000) AS clusterconfigmapping_created,
> ccm.selected, ccm.user_name
> FROM serviceconfig sc JOIN serviceconfigmapping m ON sc.service_config_id =
> m.service_config_id
> JOIN clusterconfig c ON m.config_id = c.config_id
> JOIN clusterconfigmapping ccm ON c.type_name = ccm.type_name AND
> c.version_tag = ccm.version_tag
> WHERE sc.service_name = 'SPARK2' and c.type_name =
> 'spark2-javaopts-properties'
> ORDER BY sc.version, c.type_name;
> service_name | version | user_name| to_timestamp | stack_id
> | note| type_version | version_tag |
> type_name | stack_id | clusterconfig_created |
> clusterconfigmapping_created | selected | user_name
> --+-+++--+---+--+-++--++--+--+---
> SPARK2 | 1 | admin | 2017-07-11 20:17:01+00 |3
> | Initial configurations for Spark2 |1 | version1|
> spark2-javaopts-properties |3 | 2017-07-11 20:17:00+00 | 2017-07-11
> 20:17:01+00 |0 | admin
> SPARK2 | 2 | ambari-upgrade | 2017-07-13 20:33:50+00 |3
> | |1 | version1|
> spark2-javaopts-properties |3 | 2017-07-11 20:17:00+00 | 2017-07-11
> 20:17:01+00 |0 | admin
> (2 rows)
> {noformat}
> This is because the config type has a single config with an empty value, so
> perhaps UI never selects it.
> {code}
>
>
> content
> Spark2-javaopts-properties
>
>
>
>
> {code}
> Fix will be for Ambari 2.5.2 upgrade to select exactly once config for each
> config type if none are selected.
> The only config type to hit this issue is spark2-javaopts-properties
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21501) Make HSI's 'hive.llap.zk.sm.keytab' and 'hive.service.keytab' group readable.
[ https://issues.apache.org/jira/browse/AMBARI-21501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-21501: - Description: As part of multiple fixes in AMBARI-21445, Make HSI's 'hive.llap.zk.sm.keytab' and 'hive.service.keytab' were made non-group readable, which cause LLAP deployment failures. Reverting this specific sub change. was:As part of AMBARI-21445, > Make HSI's 'hive.llap.zk.sm.keytab' and 'hive.service.keytab' group readable. > - > > Key: AMBARI-21501 > URL: https://issues.apache.org/jira/browse/AMBARI-21501 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.1 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Blocker > Fix For: trunk, 2.5.2 > > > As part of multiple fixes in AMBARI-21445, Make HSI's > 'hive.llap.zk.sm.keytab' and 'hive.service.keytab' were made non-group > readable, which cause LLAP deployment failures. > Reverting this specific sub change. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21501) Make HSI's 'hive.llap.zk.sm.keytab' and 'hive.service.keytab' group readable.
[ https://issues.apache.org/jira/browse/AMBARI-21501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-21501: - Description: As part of AMBARI-21445, > Make HSI's 'hive.llap.zk.sm.keytab' and 'hive.service.keytab' group readable. > - > > Key: AMBARI-21501 > URL: https://issues.apache.org/jira/browse/AMBARI-21501 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.1 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Blocker > Fix For: trunk, 2.5.2 > > > As part of AMBARI-21445, -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21481) Upgrading IOP cluster with Spark2 to Ambari 2.5.2 fails on start because config mapping spark2-javaopts-properties is never selected
[
https://issues.apache.org/jira/browse/AMBARI-21481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21481:
-
Status: Open (was: Patch Available)
> Upgrading IOP cluster with Spark2 to Ambari 2.5.2 fails on start because
> config mapping spark2-javaopts-properties is never selected
>
>
> Key: AMBARI-21481
> URL: https://issues.apache.org/jira/browse/AMBARI-21481
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, stacks
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Labels: AMBARI-21348
> Fix For: 2.5.2
>
> Attachments: AMBARI-21481.patch
>
>
> STR:
> * Install BigInsights 4.2.5 with Spark2
> * Upgrade to Ambari 2.5.2
> * Start Ambari, which will fail in the DB consistency check
> {code}
> 2017-07-07 01:07:01,881 ERROR - You have non selected configs:
> spark2-javaopts-properties for service SPARK2 from cluster c1!
> {code}
> Looks like this config is never selected,
> {noformat}
> ambari=> SELECT sc.service_name, sc.version, sc.user_name,
> TO_TIMESTAMP(sc.create_timestamp/1000), sc.stack_id, sc.note,
> c.version AS type_version, c.version_tag, c.type_name, c.stack_id,
> TO_TIMESTAMP(c.create_timestamp/1000) AS clusterconfig_created,
> TO_TIMESTAMP(ccm.create_timestamp/1000) AS clusterconfigmapping_created,
> ccm.selected, ccm.user_name
> FROM serviceconfig sc JOIN serviceconfigmapping m ON sc.service_config_id =
> m.service_config_id
> JOIN clusterconfig c ON m.config_id = c.config_id
> JOIN clusterconfigmapping ccm ON c.type_name = ccm.type_name AND
> c.version_tag = ccm.version_tag
> WHERE sc.service_name = 'SPARK2' and c.type_name =
> 'spark2-javaopts-properties'
> ORDER BY sc.version, c.type_name;
> service_name | version | user_name| to_timestamp | stack_id
> | note| type_version | version_tag |
> type_name | stack_id | clusterconfig_created |
> clusterconfigmapping_created | selected | user_name
> --+-+++--+---+--+-++--++--+--+---
> SPARK2 | 1 | admin | 2017-07-11 20:17:01+00 |3
> | Initial configurations for Spark2 |1 | version1|
> spark2-javaopts-properties |3 | 2017-07-11 20:17:00+00 | 2017-07-11
> 20:17:01+00 |0 | admin
> SPARK2 | 2 | ambari-upgrade | 2017-07-13 20:33:50+00 |3
> | |1 | version1|
> spark2-javaopts-properties |3 | 2017-07-11 20:17:00+00 | 2017-07-11
> 20:17:01+00 |0 | admin
> (2 rows)
> {noformat}
> This is because the config type has a single config with an empty value, so
> perhaps UI never selects it.
> {code}
>
>
> content
> Spark2-javaopts-properties
>
>
>
>
> {code}
> Fix will be for Ambari 2.5.2 upgrade to select exactly once config for each
> config type if none are selected.
> The only config type to hit this issue is spark2-javaopts-properties
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21481) Upgrading IOP cluster with Spark2 to Ambari 2.5.2 fails on start because config mapping spark2-javaopts-properties is never selected
[
https://issues.apache.org/jira/browse/AMBARI-21481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21481:
-
Status: Patch Available (was: Open)
> Upgrading IOP cluster with Spark2 to Ambari 2.5.2 fails on start because
> config mapping spark2-javaopts-properties is never selected
>
>
> Key: AMBARI-21481
> URL: https://issues.apache.org/jira/browse/AMBARI-21481
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, stacks
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Labels: AMBARI-21348
> Fix For: 2.5.2
>
> Attachments: AMBARI-21481.patch
>
>
> STR:
> * Install BigInsights 4.2.5 with Spark2
> * Upgrade to Ambari 2.5.2
> * Start Ambari, which will fail in the DB consistency check
> {code}
> 2017-07-07 01:07:01,881 ERROR - You have non selected configs:
> spark2-javaopts-properties for service SPARK2 from cluster c1!
> {code}
> Looks like this config is never selected,
> {noformat}
> ambari=> SELECT sc.service_name, sc.version, sc.user_name,
> TO_TIMESTAMP(sc.create_timestamp/1000), sc.stack_id, sc.note,
> c.version AS type_version, c.version_tag, c.type_name, c.stack_id,
> TO_TIMESTAMP(c.create_timestamp/1000) AS clusterconfig_created,
> TO_TIMESTAMP(ccm.create_timestamp/1000) AS clusterconfigmapping_created,
> ccm.selected, ccm.user_name
> FROM serviceconfig sc JOIN serviceconfigmapping m ON sc.service_config_id =
> m.service_config_id
> JOIN clusterconfig c ON m.config_id = c.config_id
> JOIN clusterconfigmapping ccm ON c.type_name = ccm.type_name AND
> c.version_tag = ccm.version_tag
> WHERE sc.service_name = 'SPARK2' and c.type_name =
> 'spark2-javaopts-properties'
> ORDER BY sc.version, c.type_name;
> service_name | version | user_name| to_timestamp | stack_id
> | note| type_version | version_tag |
> type_name | stack_id | clusterconfig_created |
> clusterconfigmapping_created | selected | user_name
> --+-+++--+---+--+-++--++--+--+---
> SPARK2 | 1 | admin | 2017-07-11 20:17:01+00 |3
> | Initial configurations for Spark2 |1 | version1|
> spark2-javaopts-properties |3 | 2017-07-11 20:17:00+00 | 2017-07-11
> 20:17:01+00 |0 | admin
> SPARK2 | 2 | ambari-upgrade | 2017-07-13 20:33:50+00 |3
> | |1 | version1|
> spark2-javaopts-properties |3 | 2017-07-11 20:17:00+00 | 2017-07-11
> 20:17:01+00 |0 | admin
> (2 rows)
> {noformat}
> This is because the config type has a single config with an empty value, so
> perhaps UI never selects it.
> {code}
>
>
> content
> Spark2-javaopts-properties
>
>
>
>
> {code}
> Fix will be for Ambari 2.5.2 upgrade to select exactly once config for each
> config type if none are selected.
> The only config type to hit this issue is spark2-javaopts-properties
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21501) Make HSI's 'hive.llap.zk.sm.keytab' and 'hive.service.keytab' group readable.
[ https://issues.apache.org/jira/browse/AMBARI-21501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-21501: - Fix Version/s: 2.5.2 trunk > Make HSI's 'hive.llap.zk.sm.keytab' and 'hive.service.keytab' group readable. > - > > Key: AMBARI-21501 > URL: https://issues.apache.org/jira/browse/AMBARI-21501 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.1 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Blocker > Fix For: trunk, 2.5.2 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21481) Upgrading IOP cluster with Spark2 to Ambari 2.5.2 fails on start because config mapping spark2-javaopts-properties is never selected
[
https://issues.apache.org/jira/browse/AMBARI-21481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21481:
-
Attachment: (was: AMBARI-21481.patch)
> Upgrading IOP cluster with Spark2 to Ambari 2.5.2 fails on start because
> config mapping spark2-javaopts-properties is never selected
>
>
> Key: AMBARI-21481
> URL: https://issues.apache.org/jira/browse/AMBARI-21481
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, stacks
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Labels: AMBARI-21348
> Fix For: 2.5.2
>
> Attachments: AMBARI-21481.patch
>
>
> STR:
> * Install BigInsights 4.2.5 with Spark2
> * Upgrade to Ambari 2.5.2
> * Start Ambari, which will fail in the DB consistency check
> {code}
> 2017-07-07 01:07:01,881 ERROR - You have non selected configs:
> spark2-javaopts-properties for service SPARK2 from cluster c1!
> {code}
> Looks like this config is never selected,
> {noformat}
> ambari=> SELECT sc.service_name, sc.version, sc.user_name,
> TO_TIMESTAMP(sc.create_timestamp/1000), sc.stack_id, sc.note,
> c.version AS type_version, c.version_tag, c.type_name, c.stack_id,
> TO_TIMESTAMP(c.create_timestamp/1000) AS clusterconfig_created,
> TO_TIMESTAMP(ccm.create_timestamp/1000) AS clusterconfigmapping_created,
> ccm.selected, ccm.user_name
> FROM serviceconfig sc JOIN serviceconfigmapping m ON sc.service_config_id =
> m.service_config_id
> JOIN clusterconfig c ON m.config_id = c.config_id
> JOIN clusterconfigmapping ccm ON c.type_name = ccm.type_name AND
> c.version_tag = ccm.version_tag
> WHERE sc.service_name = 'SPARK2' and c.type_name =
> 'spark2-javaopts-properties'
> ORDER BY sc.version, c.type_name;
> service_name | version | user_name| to_timestamp | stack_id
> | note| type_version | version_tag |
> type_name | stack_id | clusterconfig_created |
> clusterconfigmapping_created | selected | user_name
> --+-+++--+---+--+-++--++--+--+---
> SPARK2 | 1 | admin | 2017-07-11 20:17:01+00 |3
> | Initial configurations for Spark2 |1 | version1|
> spark2-javaopts-properties |3 | 2017-07-11 20:17:00+00 | 2017-07-11
> 20:17:01+00 |0 | admin
> SPARK2 | 2 | ambari-upgrade | 2017-07-13 20:33:50+00 |3
> | |1 | version1|
> spark2-javaopts-properties |3 | 2017-07-11 20:17:00+00 | 2017-07-11
> 20:17:01+00 |0 | admin
> (2 rows)
> {noformat}
> This is because the config type has a single config with an empty value, so
> perhaps UI never selects it.
> {code}
>
>
> content
> Spark2-javaopts-properties
>
>
>
>
> {code}
> Fix will be for Ambari 2.5.2 upgrade to select exactly once config for each
> config type if none are selected.
> The only config type to hit this issue is spark2-javaopts-properties
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21482) Blueprints: HSI config 'num_llap_nodes' and 'num_llap_nodes_for_llap_daemons' should be calculated and recommended via Stack Advisor during Blueprint install only if 'n
[ https://issues.apache.org/jira/browse/AMBARI-21482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-21482: - Fix Version/s: 2.5.2 trunk > Blueprints: HSI config 'num_llap_nodes' and 'num_llap_nodes_for_llap_daemons' > should be calculated and recommended via Stack Advisor during Blueprint > install only if 'num_llap_nodes' config value is not provided in Blueprint. > - > > Key: AMBARI-21482 > URL: https://issues.apache.org/jira/browse/AMBARI-21482 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.1 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: trunk, 2.5.2 > > Attachments: AMBARI-21482.patch > > > *Current:* HSI config *'num_llap_nodes_for_llap_daemons*' is calculated and > recommended via Stack Advisor during Blueprint install and > *''num_llap_nodes''* value is not used for > *'num_llap_nodes_for_llap_daemons*' calculation, if available in Blueprint. > *Issue* : This creates the problem of calculating value for > *'num_llap_nodes_for_llap_daemons'*, in which calculation doesn't includes > using the *'num_llap_nodes'* value. > We need to use *'num_llap_nodes'* config value (if provided in BP) while > calculating value for *'num_llap_nodes_for_llap_daemons'* during cluster > creation call to Stack Advisor. > *Fix* : During BP cluster install call to SA, recommendation for > *'num_llap_nodes_for_llap_daemons'* should use value of *'num_llap_nodes'* > config if specified in the cluster BP call. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21481) Upgrading IOP cluster with Spark2 to Ambari 2.5.2 fails on start because config mapping spark2-javaopts-properties is never selected
[
https://issues.apache.org/jira/browse/AMBARI-21481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21481:
-
Attachment: AMBARI-21481.patch
> Upgrading IOP cluster with Spark2 to Ambari 2.5.2 fails on start because
> config mapping spark2-javaopts-properties is never selected
>
>
> Key: AMBARI-21481
> URL: https://issues.apache.org/jira/browse/AMBARI-21481
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, stacks
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Labels: AMBARI-21348
> Fix For: 2.5.2
>
> Attachments: AMBARI-21481.patch
>
>
> STR:
> * Install BigInsights 4.2.5 with Spark2
> * Upgrade to Ambari 2.5.2
> * Start Ambari, which will fail in the DB consistency check
> {code}
> 2017-07-07 01:07:01,881 ERROR - You have non selected configs:
> spark2-javaopts-properties for service SPARK2 from cluster c1!
> {code}
> Looks like this config is never selected,
> {noformat}
> ambari=> SELECT sc.service_name, sc.version, sc.user_name,
> TO_TIMESTAMP(sc.create_timestamp/1000), sc.stack_id, sc.note,
> c.version AS type_version, c.version_tag, c.type_name, c.stack_id,
> TO_TIMESTAMP(c.create_timestamp/1000) AS clusterconfig_created,
> TO_TIMESTAMP(ccm.create_timestamp/1000) AS clusterconfigmapping_created,
> ccm.selected, ccm.user_name
> FROM serviceconfig sc JOIN serviceconfigmapping m ON sc.service_config_id =
> m.service_config_id
> JOIN clusterconfig c ON m.config_id = c.config_id
> JOIN clusterconfigmapping ccm ON c.type_name = ccm.type_name AND
> c.version_tag = ccm.version_tag
> WHERE sc.service_name = 'SPARK2' and c.type_name =
> 'spark2-javaopts-properties'
> ORDER BY sc.version, c.type_name;
> service_name | version | user_name| to_timestamp | stack_id
> | note| type_version | version_tag |
> type_name | stack_id | clusterconfig_created |
> clusterconfigmapping_created | selected | user_name
> --+-+++--+---+--+-++--++--+--+---
> SPARK2 | 1 | admin | 2017-07-11 20:17:01+00 |3
> | Initial configurations for Spark2 |1 | version1|
> spark2-javaopts-properties |3 | 2017-07-11 20:17:00+00 | 2017-07-11
> 20:17:01+00 |0 | admin
> SPARK2 | 2 | ambari-upgrade | 2017-07-13 20:33:50+00 |3
> | |1 | version1|
> spark2-javaopts-properties |3 | 2017-07-11 20:17:00+00 | 2017-07-11
> 20:17:01+00 |0 | admin
> (2 rows)
> {noformat}
> This is because the config type has a single config with an empty value, so
> perhaps UI never selects it.
> {code}
>
>
> content
> Spark2-javaopts-properties
>
>
>
>
> {code}
> Fix will be for Ambari 2.5.2 upgrade to select exactly once config for each
> config type if none are selected.
> The only config type to hit this issue is spark2-javaopts-properties
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21501) Make HSI's 'hive.llap.zk.sm.keytab' and 'hive.service.keytab' group readable.
[ https://issues.apache.org/jira/browse/AMBARI-21501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-21501: - Affects Version/s: trunk > Make HSI's 'hive.llap.zk.sm.keytab' and 'hive.service.keytab' group readable. > - > > Key: AMBARI-21501 > URL: https://issues.apache.org/jira/browse/AMBARI-21501 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.1 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Blocker > Fix For: trunk, 2.5.2 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21482) Blueprints: HSI config 'num_llap_nodes' and 'num_llap_nodes_for_llap_daemons' should be calculated and recommended via Stack Advisor during Blueprint install only if 'n
[ https://issues.apache.org/jira/browse/AMBARI-21482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-21482: - Component/s: ambari-server > Blueprints: HSI config 'num_llap_nodes' and 'num_llap_nodes_for_llap_daemons' > should be calculated and recommended via Stack Advisor during Blueprint > install only if 'num_llap_nodes' config value is not provided in Blueprint. > - > > Key: AMBARI-21482 > URL: https://issues.apache.org/jira/browse/AMBARI-21482 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.1 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: trunk, 2.5.2 > > Attachments: AMBARI-21482.patch > > > *Current:* HSI config *'num_llap_nodes_for_llap_daemons*' is calculated and > recommended via Stack Advisor during Blueprint install and > *''num_llap_nodes''* value is not used for > *'num_llap_nodes_for_llap_daemons*' calculation, if available in Blueprint. > *Issue* : This creates the problem of calculating value for > *'num_llap_nodes_for_llap_daemons'*, in which calculation doesn't includes > using the *'num_llap_nodes'* value. > We need to use *'num_llap_nodes'* config value (if provided in BP) while > calculating value for *'num_llap_nodes_for_llap_daemons'* during cluster > creation call to Stack Advisor. > *Fix* : During BP cluster install call to SA, recommendation for > *'num_llap_nodes_for_llap_daemons'* should use value of *'num_llap_nodes'* > config if specified in the cluster BP call. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21501) Make HSI's 'hive.llap.zk.sm.keytab' and 'hive.service.keytab' group readable.
Swapan Shridhar created AMBARI-21501: Summary: Make HSI's 'hive.llap.zk.sm.keytab' and 'hive.service.keytab' group readable. Key: AMBARI-21501 URL: https://issues.apache.org/jira/browse/AMBARI-21501 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.5.1 Reporter: Swapan Shridhar Assignee: Swapan Shridhar Priority: Blocker -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21482) Blueprints: HSI config 'num_llap_nodes' and 'num_llap_nodes_for_llap_daemons' should be calculated and recommended via Stack Advisor during Blueprint install only if 'n
[ https://issues.apache.org/jira/browse/AMBARI-21482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-21482: - Affects Version/s: 2.5.1 trunk > Blueprints: HSI config 'num_llap_nodes' and 'num_llap_nodes_for_llap_daemons' > should be calculated and recommended via Stack Advisor during Blueprint > install only if 'num_llap_nodes' config value is not provided in Blueprint. > - > > Key: AMBARI-21482 > URL: https://issues.apache.org/jira/browse/AMBARI-21482 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.5.1 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Attachments: AMBARI-21482.patch > > > *Current:* HSI config *'num_llap_nodes_for_llap_daemons*' is calculated and > recommended via Stack Advisor during Blueprint install and > *''num_llap_nodes''* value is not used for > *'num_llap_nodes_for_llap_daemons*' calculation, if available in Blueprint. > *Issue* : This creates the problem of calculating value for > *'num_llap_nodes_for_llap_daemons'*, in which calculation doesn't includes > using the *'num_llap_nodes'* value. > We need to use *'num_llap_nodes'* config value (if provided in BP) while > calculating value for *'num_llap_nodes_for_llap_daemons'* during cluster > creation call to Stack Advisor. > *Fix* : During BP cluster install call to SA, recommendation for > *'num_llap_nodes_for_llap_daemons'* should use value of *'num_llap_nodes'* > config if specified in the cluster BP call. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21499) Move Stack-Specific Custom Actions Under the Stack Dropdown
[ https://issues.apache.org/jira/browse/AMBARI-21499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16090170#comment-16090170 ] Hudson commented on AMBARI-21499: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1703 (See [https://builds.apache.org/job/Ambari-branch-2.5/1703/]) AMBARI-21499 Move Stack-Specific Custom Actions Under the Stack (atkach: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=15349983ed14804b83f99281b344a2339dcbf8c8]) * (edit) ambari-web/app/views/main/admin/stack_upgrade/upgrade_version_box_view.js * (edit) ambari-web/test/views/main/admin/stack_upgrade/version_view_test.js * (edit) ambari-web/app/templates/main/admin/stack_upgrade/versions.hbs * (edit) ambari-web/app/views/main/admin/stack_upgrade/versions_view.js * (edit) ambari-web/app/controllers/main/admin/stack_and_upgrade_controller.js * (edit) ambari-web/test/controllers/main/admin/stack_and_upgrade_controller_test.js > Move Stack-Specific Custom Actions Under the Stack Dropdown > --- > > Key: AMBARI-21499 > URL: https://issues.apache.org/jira/browse/AMBARI-21499 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.2 > > Attachments: AMBARI-21499.patch > > > Instead of having the "Remove IOP Select" button floating on the page, it > should be moved into the stack-specific drop-downs alongside "Upgrade" and > "Install". -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21500) Support SPARK2 upgrade for BI 4.2.5 to HDP 2.6.2
Jonathan Hurley created AMBARI-21500:
Summary: Support SPARK2 upgrade for BI 4.2.5 to HDP 2.6.2
Key: AMBARI-21500
URL: https://issues.apache.org/jira/browse/AMBARI-21500
Project: Ambari
Issue Type: Bug
Affects Versions: 2.5.2
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Priority: Critical
Fix For: 2.5.2
SPARK2 is missing from the upgrade pack for BI 4.2.5 resulting in finalize
operation error:
{code}
The following components were found to have version mismatches. Finalize will
not complete successfully:
c7302.ambari.apache.org: SPARK2/SPARK2_THRIFTSERVER reports 4.2.5.0-
c7302.ambari.apache.org: SPARK2/SPARK2_CLIENT reports 4.2.5.0-
c7302.ambari.apache.org: SPARK2/SPARK2_JOBHISTORYSERVER reports 4.2.5.0-
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21486) Remove IOP Select button declares success even if command fails
[ https://issues.apache.org/jira/browse/AMBARI-21486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16090095#comment-16090095 ] Hudson commented on AMBARI-21486: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1702 (See [https://builds.apache.org/job/Ambari-branch-2.5/1702/]) AMBARI-21486 Remove IOP Select button declares success even if command (atkach: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=061467bae47c4218437b0fed97d814ce4d43222b]) * (edit) ambari-web/app/messages.js * (edit) ambari-web/app/views/main/admin/stack_upgrade/versions_view.js > Remove IOP Select button declares success even if command fails > --- > > Key: AMBARI-21486 > URL: https://issues.apache.org/jira/browse/AMBARI-21486 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.2 > > Attachments: AMBARI-21486.patch, Screen Shot 2017-07-13 at 1.48.01 > PM.png, Screen Shot 2017-07-13 at 1.48.09 PM.png > > > "Remove IOP Select" button shows a message that it completed successfully > immediately after attempting to launch the command, but it can still fail. > To repro, stop the ambari agents and click the "Remove IOP Select" button. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21499) Move Stack-Specific Custom Actions Under the Stack Dropdown
[ https://issues.apache.org/jira/browse/AMBARI-21499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21499: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Move Stack-Specific Custom Actions Under the Stack Dropdown > --- > > Key: AMBARI-21499 > URL: https://issues.apache.org/jira/browse/AMBARI-21499 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.2 > > Attachments: AMBARI-21499.patch > > > Instead of having the "Remove IOP Select" button floating on the page, it > should be moved into the stack-specific drop-downs alongside "Upgrade" and > "Install". -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21499) Move Stack-Specific Custom Actions Under the Stack Dropdown
[ https://issues.apache.org/jira/browse/AMBARI-21499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16090084#comment-16090084 ] Andrii Tkach commented on AMBARI-21499: --- committed to branch-2.5 > Move Stack-Specific Custom Actions Under the Stack Dropdown > --- > > Key: AMBARI-21499 > URL: https://issues.apache.org/jira/browse/AMBARI-21499 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.2 > > Attachments: AMBARI-21499.patch > > > Instead of having the "Remove IOP Select" button floating on the page, it > should be moved into the stack-specific drop-downs alongside "Upgrade" and > "Install". -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21499) Move Stack-Specific Custom Actions Under the Stack Dropdown
[ https://issues.apache.org/jira/browse/AMBARI-21499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16090076#comment-16090076 ] Aleksandr Kovalenko commented on AMBARI-21499: -- +1 for the patch > Move Stack-Specific Custom Actions Under the Stack Dropdown > --- > > Key: AMBARI-21499 > URL: https://issues.apache.org/jira/browse/AMBARI-21499 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.2 > > Attachments: AMBARI-21499.patch > > > Instead of having the "Remove IOP Select" button floating on the page, it > should be moved into the stack-specific drop-downs alongside "Upgrade" and > "Install". -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21499) Move Stack-Specific Custom Actions Under the Stack Dropdown
[ https://issues.apache.org/jira/browse/AMBARI-21499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21499: -- Status: Patch Available (was: Open) > Move Stack-Specific Custom Actions Under the Stack Dropdown > --- > > Key: AMBARI-21499 > URL: https://issues.apache.org/jira/browse/AMBARI-21499 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.2 > > Attachments: AMBARI-21499.patch > > > Instead of having the "Remove IOP Select" button floating on the page, it > should be moved into the stack-specific drop-downs alongside "Upgrade" and > "Install". -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21499) Move Stack-Specific Custom Actions Under the Stack Dropdown
[ https://issues.apache.org/jira/browse/AMBARI-21499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16090052#comment-16090052 ] Andrii Tkach commented on AMBARI-21499: --- 30386 passing (27s) 157 pending > Move Stack-Specific Custom Actions Under the Stack Dropdown > --- > > Key: AMBARI-21499 > URL: https://issues.apache.org/jira/browse/AMBARI-21499 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.2 > > Attachments: AMBARI-21499.patch > > > Instead of having the "Remove IOP Select" button floating on the page, it > should be moved into the stack-specific drop-downs alongside "Upgrade" and > "Install". -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21499) Move Stack-Specific Custom Actions Under the Stack Dropdown
[ https://issues.apache.org/jira/browse/AMBARI-21499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21499: -- Attachment: AMBARI-21499.patch > Move Stack-Specific Custom Actions Under the Stack Dropdown > --- > > Key: AMBARI-21499 > URL: https://issues.apache.org/jira/browse/AMBARI-21499 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.2 > > Attachments: AMBARI-21499.patch > > > Instead of having the "Remove IOP Select" button floating on the page, it > should be moved into the stack-specific drop-downs alongside "Upgrade" and > "Install". -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21499) Move Stack-Specific Custom Actions Under the Stack Dropdown
Andrii Tkach created AMBARI-21499: - Summary: Move Stack-Specific Custom Actions Under the Stack Dropdown Key: AMBARI-21499 URL: https://issues.apache.org/jira/browse/AMBARI-21499 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.2 Reporter: Andrii Tkach Assignee: Andrii Tkach Priority: Critical Fix For: 2.5.2 Instead of having the "Remove IOP Select" button floating on the page, it should be moved into the stack-specific drop-downs alongside "Upgrade" and "Install". -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21490) Ambari Schema Upgrade fails : Unknown column 'from_version' in 'field list'
[
https://issues.apache.org/jira/browse/AMBARI-21490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16090027#comment-16090027
]
Hudson commented on AMBARI-21490:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1701 (See
[https://builds.apache.org/job/Ambari-branch-2.5/1701/])
AMBARI-21490 Ambari Schema Upgrade fails : Unknown column 'from_version'
(hapylestat:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=651fe3d706185992e107486ee69059ec8eccf909])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/DBAccessor.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog220.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/DBAccessorImpl.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog252.java
> Ambari Schema Upgrade fails : Unknown column 'from_version' in 'field list'
> ---
>
> Key: AMBARI-21490
> URL: https://issues.apache.org/jira/browse/AMBARI-21490
> Project: Ambari
> Issue Type: Bug
> Components: ambari-sever
>Affects Versions: trunk, 2.5.2
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Blocker
> Fix For: trunk, 2.5.2
>
> Attachments: AMBARI-21490-branch-2.5.patch
>
>
> {code}
> 2017-07-12 07:51:24,251 WARN
> com.hw.ambari.ui.tests.upgrade.AmbariUpgradeOnly.upgradeCluster(): Detected
> ambari-server version build is:
> 2017-07-12 07:51:24,860 WARN
> com.hw.ambari.ui.tests.upgrade.AmbariUpgradeOnly.upgradeCluster(): Detected
> ambari-server version hash is:
> {code}
> {code}
> 2017-07-12 07:51:26,092 INFO
> com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence():
> Sending command [ambari-server upgrade --verbose]
> 2017-07-12 07:51:26,092 INFO
> com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence():
> Sending command []
> 2017-07-12 07:52:02,688 INFO
> com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence():
> [OUTPUT STREAM]
> Using python /usr/bin/python
> Upgrading ambari-server
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Upgrade Ambari Server
> INFO: Updating Ambari Server properties in ambari.properties ...
> INFO: Updating Ambari Server properties in ambari-env.sh ...
> WARNING: Original file ambari-env.sh kept
> WARNING: Original file krb5JAASLogin.conf kept
> INFO: File krb5JAASLogin.conf updated.
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: No mpack replay logs found. Skipping replaying mpack commands
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Fixing database objects owner
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> Ambari Server configured for MySQL. Confirm you have made a backup of the
> Ambari Server database [y/n] (y)? INFO: Loading properties from
> /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Upgrading database schema
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: AMBARI_SERVER_LIB is not set, using default /usr/lib/ambari-server
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: about to run command: /usr/jdk64/jdk1.7.0_67/bin/java -cp
> '/etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/mysql-connector-java.jar'
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper >
> /var/log/ambari-server/ambari-server.out 2>&1
> INFO:
> process_pid=22161
> INFO: Return code from schema upgrade command, retcode = 1
> ERROR: Error executing schema upgrade, please check the server logs.
> ERROR: Error output from schema upgrade command:
> ERROR: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown
> column 'from_version' in 'field list'
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> at com.mysql.jdbc.Util.handleNewInstance(Util.java:377)
> at
[jira] [Commented] (AMBARI-21386) After install packages, upgrade button does not work
[ https://issues.apache.org/jira/browse/AMBARI-21386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1608#comment-1608 ] Hudson commented on AMBARI-21386: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7776 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7776/]) AMBARI-21386. After install packages, upgrade button does not work (hiveww: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=01d60f4f8b8c32238ba840e109e7b7e8b9de1774]) * (edit) ambari-web/app/utils/ajax/ajax.js > After install packages, upgrade button does not work > > > Key: AMBARI-21386 > URL: https://issues.apache.org/jira/browse/AMBARI-21386 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 3.0.0 > > Attachments: AMBARI-21386.patch, Screen Shot 2017-06-22 at 2.40.51 > PM.png > > > After adding a Patch-type repository and installing packages, clicking the > Upgrade button does not work. See screenshots. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21490) Ambari Schema Upgrade fails : Unknown column 'from_version' in 'field list'
[
https://issues.apache.org/jira/browse/AMBARI-21490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-21490:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Ambari Schema Upgrade fails : Unknown column 'from_version' in 'field list'
> ---
>
> Key: AMBARI-21490
> URL: https://issues.apache.org/jira/browse/AMBARI-21490
> Project: Ambari
> Issue Type: Bug
> Components: ambari-sever
>Affects Versions: trunk, 2.5.2
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Blocker
> Fix For: trunk, 2.5.2
>
> Attachments: AMBARI-21490-branch-2.5.patch
>
>
> {code}
> 2017-07-12 07:51:24,251 WARN
> com.hw.ambari.ui.tests.upgrade.AmbariUpgradeOnly.upgradeCluster(): Detected
> ambari-server version build is:
> 2017-07-12 07:51:24,860 WARN
> com.hw.ambari.ui.tests.upgrade.AmbariUpgradeOnly.upgradeCluster(): Detected
> ambari-server version hash is:
> {code}
> {code}
> 2017-07-12 07:51:26,092 INFO
> com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence():
> Sending command [ambari-server upgrade --verbose]
> 2017-07-12 07:51:26,092 INFO
> com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence():
> Sending command []
> 2017-07-12 07:52:02,688 INFO
> com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence():
> [OUTPUT STREAM]
> Using python /usr/bin/python
> Upgrading ambari-server
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Upgrade Ambari Server
> INFO: Updating Ambari Server properties in ambari.properties ...
> INFO: Updating Ambari Server properties in ambari-env.sh ...
> WARNING: Original file ambari-env.sh kept
> WARNING: Original file krb5JAASLogin.conf kept
> INFO: File krb5JAASLogin.conf updated.
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: No mpack replay logs found. Skipping replaying mpack commands
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Fixing database objects owner
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> Ambari Server configured for MySQL. Confirm you have made a backup of the
> Ambari Server database [y/n] (y)? INFO: Loading properties from
> /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Upgrading database schema
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: AMBARI_SERVER_LIB is not set, using default /usr/lib/ambari-server
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: about to run command: /usr/jdk64/jdk1.7.0_67/bin/java -cp
> '/etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/mysql-connector-java.jar'
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper >
> /var/log/ambari-server/ambari-server.out 2>&1
> INFO:
> process_pid=22161
> INFO: Return code from schema upgrade command, retcode = 1
> ERROR: Error executing schema upgrade, please check the server logs.
> ERROR: Error output from schema upgrade command:
> ERROR: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown
> column 'from_version' in 'field list'
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> at com.mysql.jdbc.Util.handleNewInstance(Util.java:377)
> at com.mysql.jdbc.Util.getInstance(Util.java:360)
> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:978)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3887)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3823)
> at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2435)
> at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2582)
> at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2526)
> at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2484)
> at com.mysql.jdbc.StatementImpl.executeQuery(StatementImpl.java:1446)
> at
>
[jira] [Updated] (AMBARI-21498) DB consistency checker throws errors for missing 'product-info' configs after Ambari upgrade
[
https://issues.apache.org/jira/browse/AMBARI-21498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-21498:
Fix Version/s: 2.5.3
> DB consistency checker throws errors for missing 'product-info' configs after
> Ambari upgrade
>
>
> Key: AMBARI-21498
> URL: https://issues.apache.org/jira/browse/AMBARI-21498
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Fix For: 2.5.3
>
> Attachments: AMBARI-21498.patch
>
>
> DB consistency checker throws errors for missing 'product-info' configs after
> Ambari upgrade
> AMBARI-21364 fixed the missing 'parquet-logging' but 'product-info' is still
> missing for Smartsense
> STR
> Deployed cluster with Ambari version: 2.5.1.0-159 and HDP version: 2.6.1.0-129
> Upgrade Ambari to 2.5.2.0-105
> Run "ambari-server start"
> Live openstack cluster : 172.22.124.150 (Ambari Server)
> ambari-server-check-database.log
> {code}
> 2017-07-07 18:09:05,678 ERROR - Required config(s): product-info is(are) not
> available for service SMARTSENSE with service config version 1 in cluster cl1
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21498) DB consistency checker throws errors for missing 'product-info' configs after Ambari upgrade
[
https://issues.apache.org/jira/browse/AMBARI-21498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-21498:
Component/s: ambari-server
> DB consistency checker throws errors for missing 'product-info' configs after
> Ambari upgrade
>
>
> Key: AMBARI-21498
> URL: https://issues.apache.org/jira/browse/AMBARI-21498
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Attachments: AMBARI-21498.patch
>
>
> DB consistency checker throws errors for missing 'product-info' configs after
> Ambari upgrade
> AMBARI-21364 fixed the missing 'parquet-logging' but 'product-info' is still
> missing for Smartsense
> STR
> Deployed cluster with Ambari version: 2.5.1.0-159 and HDP version: 2.6.1.0-129
> Upgrade Ambari to 2.5.2.0-105
> Run "ambari-server start"
> Live openstack cluster : 172.22.124.150 (Ambari Server)
> ambari-server-check-database.log
> {code}
> 2017-07-07 18:09:05,678 ERROR - Required config(s): product-info is(are) not
> available for service SMARTSENSE with service config version 1 in cluster cl1
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-21498) DB consistency checker throws errors for missing 'product-info' configs after Ambari upgrade
Dmitry Lysnichenko created AMBARI-21498:
---
Summary: DB consistency checker throws errors for missing
'product-info' configs after Ambari upgrade
Key: AMBARI-21498
URL: https://issues.apache.org/jira/browse/AMBARI-21498
Project: Ambari
Issue Type: Bug
Reporter: Dmitry Lysnichenko
Assignee: Dmitry Lysnichenko
Priority: Blocker
DB consistency checker throws errors for missing 'product-info' configs after
Ambari upgrade
AMBARI-21364 fixed the missing 'parquet-logging' but 'product-info' is still
missing for Smartsense
STR
Deployed cluster with Ambari version: 2.5.1.0-159 and HDP version: 2.6.1.0-129
Upgrade Ambari to 2.5.2.0-105
Run "ambari-server start"
Live openstack cluster : 172.22.124.150 (Ambari Server)
ambari-server-check-database.log
{code}
2017-07-07 18:09:05,678 ERROR - Required config(s): product-info is(are) not
available for service SMARTSENSE with service config version 1 in cluster cl1
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21498) DB consistency checker throws errors for missing 'product-info' configs after Ambari upgrade
[
https://issues.apache.org/jira/browse/AMBARI-21498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-21498:
Status: Patch Available (was: Open)
> DB consistency checker throws errors for missing 'product-info' configs after
> Ambari upgrade
>
>
> Key: AMBARI-21498
> URL: https://issues.apache.org/jira/browse/AMBARI-21498
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Attachments: AMBARI-21498.patch
>
>
> DB consistency checker throws errors for missing 'product-info' configs after
> Ambari upgrade
> AMBARI-21364 fixed the missing 'parquet-logging' but 'product-info' is still
> missing for Smartsense
> STR
> Deployed cluster with Ambari version: 2.5.1.0-159 and HDP version: 2.6.1.0-129
> Upgrade Ambari to 2.5.2.0-105
> Run "ambari-server start"
> Live openstack cluster : 172.22.124.150 (Ambari Server)
> ambari-server-check-database.log
> {code}
> 2017-07-07 18:09:05,678 ERROR - Required config(s): product-info is(are) not
> available for service SMARTSENSE with service config version 1 in cluster cl1
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21498) DB consistency checker throws errors for missing 'product-info' configs after Ambari upgrade
[
https://issues.apache.org/jira/browse/AMBARI-21498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-21498:
Attachment: AMBARI-21498.patch
> DB consistency checker throws errors for missing 'product-info' configs after
> Ambari upgrade
>
>
> Key: AMBARI-21498
> URL: https://issues.apache.org/jira/browse/AMBARI-21498
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Attachments: AMBARI-21498.patch
>
>
> DB consistency checker throws errors for missing 'product-info' configs after
> Ambari upgrade
> AMBARI-21364 fixed the missing 'parquet-logging' but 'product-info' is still
> missing for Smartsense
> STR
> Deployed cluster with Ambari version: 2.5.1.0-159 and HDP version: 2.6.1.0-129
> Upgrade Ambari to 2.5.2.0-105
> Run "ambari-server start"
> Live openstack cluster : 172.22.124.150 (Ambari Server)
> ambari-server-check-database.log
> {code}
> 2017-07-07 18:09:05,678 ERROR - Required config(s): product-info is(are) not
> available for service SMARTSENSE with service config version 1 in cluster cl1
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21490) Ambari Schema Upgrade fails : Unknown column 'from_version' in 'field list'
[
https://issues.apache.org/jira/browse/AMBARI-21490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-21490:
-
Attachment: AMBARI-21490-branch-2.5.patch
> Ambari Schema Upgrade fails : Unknown column 'from_version' in 'field list'
> ---
>
> Key: AMBARI-21490
> URL: https://issues.apache.org/jira/browse/AMBARI-21490
> Project: Ambari
> Issue Type: Bug
> Components: ambari-sever
>Affects Versions: trunk, 2.5.2
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Blocker
> Fix For: trunk, 2.5.2
>
> Attachments: AMBARI-21490-branch-2.5.patch
>
>
> {code}
> 2017-07-12 07:51:24,251 WARN
> com.hw.ambari.ui.tests.upgrade.AmbariUpgradeOnly.upgradeCluster(): Detected
> ambari-server version build is:
> 2017-07-12 07:51:24,860 WARN
> com.hw.ambari.ui.tests.upgrade.AmbariUpgradeOnly.upgradeCluster(): Detected
> ambari-server version hash is:
> {code}
> {code}
> 2017-07-12 07:51:26,092 INFO
> com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence():
> Sending command [ambari-server upgrade --verbose]
> 2017-07-12 07:51:26,092 INFO
> com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence():
> Sending command []
> 2017-07-12 07:52:02,688 INFO
> com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence():
> [OUTPUT STREAM]
> Using python /usr/bin/python
> Upgrading ambari-server
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Upgrade Ambari Server
> INFO: Updating Ambari Server properties in ambari.properties ...
> INFO: Updating Ambari Server properties in ambari-env.sh ...
> WARNING: Original file ambari-env.sh kept
> WARNING: Original file krb5JAASLogin.conf kept
> INFO: File krb5JAASLogin.conf updated.
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: No mpack replay logs found. Skipping replaying mpack commands
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Fixing database objects owner
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> Ambari Server configured for MySQL. Confirm you have made a backup of the
> Ambari Server database [y/n] (y)? INFO: Loading properties from
> /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Upgrading database schema
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: AMBARI_SERVER_LIB is not set, using default /usr/lib/ambari-server
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: about to run command: /usr/jdk64/jdk1.7.0_67/bin/java -cp
> '/etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/mysql-connector-java.jar'
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper >
> /var/log/ambari-server/ambari-server.out 2>&1
> INFO:
> process_pid=22161
> INFO: Return code from schema upgrade command, retcode = 1
> ERROR: Error executing schema upgrade, please check the server logs.
> ERROR: Error output from schema upgrade command:
> ERROR: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown
> column 'from_version' in 'field list'
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> at com.mysql.jdbc.Util.handleNewInstance(Util.java:377)
> at com.mysql.jdbc.Util.getInstance(Util.java:360)
> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:978)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3887)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3823)
> at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2435)
> at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2582)
> at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2526)
> at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2484)
> at com.mysql.jdbc.StatementImpl.executeQuery(StatementImpl.java:1446)
> at
>
[jira] [Resolved] (AMBARI-21386) After install packages, upgrade button does not work
[ https://issues.apache.org/jira/browse/AMBARI-21386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander resolved AMBARI-21386. -- Resolution: Fixed committed to trunk > After install packages, upgrade button does not work > > > Key: AMBARI-21386 > URL: https://issues.apache.org/jira/browse/AMBARI-21386 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 3.0.0 > > Attachments: AMBARI-21386.patch, Screen Shot 2017-06-22 at 2.40.51 > PM.png > > > After adding a Patch-type repository and installing packages, clicking the > Upgrade button does not work. See screenshots. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Reopened] (AMBARI-21386) After install packages, upgrade button does not work
[ https://issues.apache.org/jira/browse/AMBARI-21386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reopened AMBARI-21386: -- > After install packages, upgrade button does not work > > > Key: AMBARI-21386 > URL: https://issues.apache.org/jira/browse/AMBARI-21386 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 3.0.0 > > Attachments: AMBARI-21386.patch, Screen Shot 2017-06-22 at 2.40.51 > PM.png > > > After adding a Patch-type repository and installing packages, clicking the > Upgrade button does not work. See screenshots. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21386) After install packages, upgrade button does not work
[ https://issues.apache.org/jira/browse/AMBARI-21386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16089958#comment-16089958 ] Antonenko Alexander commented on AMBARI-21386: -- reopening since it needs to be committed to trunk > After install packages, upgrade button does not work > > > Key: AMBARI-21386 > URL: https://issues.apache.org/jira/browse/AMBARI-21386 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 3.0.0 > > Attachments: AMBARI-21386.patch, Screen Shot 2017-06-22 at 2.40.51 > PM.png > > > After adding a Patch-type repository and installing packages, clicking the > Upgrade button does not work. See screenshots. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21496) Fix HDP base services to handle changed config paths
[
https://issues.apache.org/jira/browse/AMBARI-21496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16089959#comment-16089959
]
Hadoop QA commented on AMBARI-21496:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12877596/AMBARI-21496.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11803//console
This message is automatically generated.
> Fix HDP base services to handle changed config paths
>
>
> Key: AMBARI-21496
> URL: https://issues.apache.org/jira/browse/AMBARI-21496
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-21496.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21494) BI 4.2 Ranger Needs Properties Added on Ambari Upgrade
[ https://issues.apache.org/jira/browse/AMBARI-21494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16089948#comment-16089948 ] Hudson commented on AMBARI-21494: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1700 (See [https://builds.apache.org/job/Ambari-branch-2.5/1700/]) AMBARI-21494 - BI 4.2 Ranger Needs Properties Added on Ambari Upgrade (jhurley: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=606c5cabf6ea734e0c2e2928521f56394edb4f77]) * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.2/services/RANGER/configuration/ranger-admin-site.xml > BI 4.2 Ranger Needs Properties Added on Ambari Upgrade > -- > > Key: AMBARI-21494 > URL: https://issues.apache.org/jira/browse/AMBARI-21494 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.2 >Reporter: Jonathan Hurley >Assignee: Jonathan Hurley >Priority: Blocker > Fix For: 2.5.2 > > Attachments: AMBARI-21494.patch > > > The following two properties were added to Ranger 0.5.0 for Ambari 2.5.0. > However, since BigInsight 4.2.0 doesn't extend common services, these need to > be added for the upgrade from Ambari 2.4.2 to 2.5: > - ranger.ldap.binddn.credential.alias > - ranger.ldap.ad.binddn.credential.alias > Reference commit: > https://github.com/apache/ambari/commit/0d9d31fe3f8ace4a7ad710df34fe5ccba4b66df1#diff-1ae96dddc715cc510335ca0bcb698c23 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21497) Conflicts in the ambari config groups
Andrii Tkach created AMBARI-21497: - Summary: Conflicts in the ambari config groups Key: AMBARI-21497 URL: https://issues.apache.org/jira/browse/AMBARI-21497 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.1 Reporter: Andrii Tkach Assignee: Andrii Tkach Priority: Critical Ambari is arbitrarily changing settings for different config groups when pushing changes to other config groups. This is causing yarn to have settings for RAM that well exceed system limits, which causes other processes to run out of RAM and then become unavailable. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21494) BI 4.2 Ranger Needs Properties Added on Ambari Upgrade
[ https://issues.apache.org/jira/browse/AMBARI-21494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-21494: - Resolution: Fixed Status: Resolved (was: Patch Available) > BI 4.2 Ranger Needs Properties Added on Ambari Upgrade > -- > > Key: AMBARI-21494 > URL: https://issues.apache.org/jira/browse/AMBARI-21494 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.2 >Reporter: Jonathan Hurley >Assignee: Jonathan Hurley >Priority: Blocker > Fix For: 2.5.2 > > Attachments: AMBARI-21494.patch > > > The following two properties were added to Ranger 0.5.0 for Ambari 2.5.0. > However, since BigInsight 4.2.0 doesn't extend common services, these need to > be added for the upgrade from Ambari 2.4.2 to 2.5: > - ranger.ldap.binddn.credential.alias > - ranger.ldap.ad.binddn.credential.alias > Reference commit: > https://github.com/apache/ambari/commit/0d9d31fe3f8ace4a7ad710df34fe5ccba4b66df1#diff-1ae96dddc715cc510335ca0bcb698c23 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21496) Fix HDP base services to handle changed config paths
[
https://issues.apache.org/jira/browse/AMBARI-21496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16089893#comment-16089893
]
Hadoop QA commented on AMBARI-21496:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12877596/AMBARI-21496.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11802//console
This message is automatically generated.
> Fix HDP base services to handle changed config paths
>
>
> Key: AMBARI-21496
> URL: https://issues.apache.org/jira/browse/AMBARI-21496
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-21496.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21496) Fix HDP base services to handle changed config paths
[ https://issues.apache.org/jira/browse/AMBARI-21496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-21496: - Attachment: AMBARI-21496.patch > Fix HDP base services to handle changed config paths > > > Key: AMBARI-21496 > URL: https://issues.apache.org/jira/browse/AMBARI-21496 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 3.0.0 > > Attachments: AMBARI-21496.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21496) Fix HDP base services to handle changed config paths
[ https://issues.apache.org/jira/browse/AMBARI-21496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-21496: - Status: Patch Available (was: Open) > Fix HDP base services to handle changed config paths > > > Key: AMBARI-21496 > URL: https://issues.apache.org/jira/browse/AMBARI-21496 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 3.0.0 > > Attachments: AMBARI-21496.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21496) Fix HDP base services to handle changed config paths
Andrew Onischuk created AMBARI-21496: Summary: Fix HDP base services to handle changed config paths Key: AMBARI-21496 URL: https://issues.apache.org/jira/browse/AMBARI-21496 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21495) Show only warnings against all nodes hiding cause when Schema Registry fails to bootstrap during HDF 3.0 cluster install
[ https://issues.apache.org/jira/browse/AMBARI-21495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hari Sekhon updated AMBARI-21495: - Attachment: Ambari_post_install_shows_the_failure_correctly.png > Show only warnings against all nodes hiding cause when Schema Registry fails > to bootstrap during HDF 3.0 cluster install > > > Key: AMBARI-21495 > URL: https://issues.apache.org/jira/browse/AMBARI-21495 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.1 > Environment: HDF 3.0 >Reporter: Hari Sekhon > Attachments: Ambari_all_warnings.png, > Ambari_all_warnings_random_services2.png, > Ambari_all_warnings_random_services3.png, > Ambari_all_warnings_random_services4_culprit.png, > Ambari_all_warnings_random_services.png, > Ambari_post_install_shows_the_failure_correctly.png > > > Ambari marks all nodes with warnings including component failure which should > have been shown as red failure. > This was caused by a failure to bootstrap the Registry Schema (AMBARI-21492), > but Ambari showed only warnings against all cluster hosts, while each host > had a blank warning against random components where it had aborted but there > was nothing wrong with those components so no error outputs. > The failure during Registry Startup bootstrap script should have been shown > as red failure not yellow warning as the only way I could find the root cause > was to go through the nodes one by one, which luckily this is a small 9 node > cluster a not a 50 - 100+ cluster as I might not have found it otherwise. > Post cluster install the Ops screen does show the red failure correctly, this > appears to only be a bug with the cluster installer. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21493) Fix PERF stack scripts to handle changed config paths
[ https://issues.apache.org/jira/browse/AMBARI-21493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-21493: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-3.0-perf > Fix PERF stack scripts to handle changed config paths > - > > Key: AMBARI-21493 > URL: https://issues.apache.org/jira/browse/AMBARI-21493 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 3.0.0 > > Attachments: AMBARI-21493.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21495) Show only warnings against all nodes hiding cause when Schema Registry fails to bootstrap during HDF 3.0 cluster install
[ https://issues.apache.org/jira/browse/AMBARI-21495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hari Sekhon updated AMBARI-21495: - Description: Ambari marks all nodes with warnings including component failure which should have been shown as red failure. This was caused by a failure to bootstrap the Registry Schema (AMBARI-21492), but Ambari showed only warnings against all cluster hosts, while each host had a blank warning against random components where it had aborted but there was nothing wrong with those components so no error outputs. The failure during Registry Startup bootstrap script should have been shown as red failure not yellow warning as the only way I could find the root cause was to go through the nodes one by one, which luckily this is a small 9 node cluster a not a 50 - 100+ cluster as I might not have found it otherwise. Post cluster install the Ops screen does show the red failure correctly, this appears to only be a bug with the cluster installer. was: Ambari marks all nodes with warnings including component failure which should have been shown as red failure. This was caused by a failure to bootstrap the Registry Schema (AMBARI-21492), but Ambari showed only warnings against all cluster hosts, while each host had a blank warning against random components where it had aborted but there was nothing wrong with those components so no error outputs. The failure during Registry Startup bootstrap script should have been shown as red failure not yellow warning as the only way I could find the root cause was to go through the nodes one by one, which luckily this is a small 9 node cluster a not a 50 - 100+ cluster as I might not have found it otherwise. > Show only warnings against all nodes hiding cause when Schema Registry fails > to bootstrap during HDF 3.0 cluster install > > > Key: AMBARI-21495 > URL: https://issues.apache.org/jira/browse/AMBARI-21495 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.1 > Environment: HDF 3.0 >Reporter: Hari Sekhon > Attachments: Ambari_all_warnings.png, > Ambari_all_warnings_random_services2.png, > Ambari_all_warnings_random_services3.png, > Ambari_all_warnings_random_services4_culprit.png, > Ambari_all_warnings_random_services.png > > > Ambari marks all nodes with warnings including component failure which should > have been shown as red failure. > This was caused by a failure to bootstrap the Registry Schema (AMBARI-21492), > but Ambari showed only warnings against all cluster hosts, while each host > had a blank warning against random components where it had aborted but there > was nothing wrong with those components so no error outputs. > The failure during Registry Startup bootstrap script should have been shown > as red failure not yellow warning as the only way I could find the root cause > was to go through the nodes one by one, which luckily this is a small 9 node > cluster a not a 50 - 100+ cluster as I might not have found it otherwise. > Post cluster install the Ops screen does show the red failure correctly, this > appears to only be a bug with the cluster installer. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21495) Show only warnings against all nodes hiding cause when Schema Registry fails to bootstrap during HDF 3.0 cluster install
Hari Sekhon created AMBARI-21495: Summary: Show only warnings against all nodes hiding cause when Schema Registry fails to bootstrap during HDF 3.0 cluster install Key: AMBARI-21495 URL: https://issues.apache.org/jira/browse/AMBARI-21495 Project: Ambari Issue Type: Bug Affects Versions: 2.5.1 Environment: HDF 3.0 Reporter: Hari Sekhon Ambari marks all nodes with warnings including component failure which should have been shown as red failure. This was caused by a failure to bootstrap the Registry Schema (AMBARI-21492), but Ambari showed only warnings against all cluster hosts, while each host had a blank warning against random components where it had aborted but there was nothing wrong with those components so no error outputs. The failure during Registry Startup bootstrap script should have been shown as red failure not yellow warning as the only way I could find the root cause was to go through the nodes one by one, which luckily this is a small 9 node cluster a not a 50 - 100+ cluster as I might not have found it otherwise. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21495) Show only warnings against all nodes hiding cause when Schema Registry fails to bootstrap during HDF 3.0 cluster install
[ https://issues.apache.org/jira/browse/AMBARI-21495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hari Sekhon updated AMBARI-21495: - Attachment: Ambari_all_warnings_random_services3.png Ambari_all_warnings_random_services2.png Ambari_all_warnings_random_services.png Ambari_all_warnings.png Ambari_all_warnings_random_services4_culprit.png > Show only warnings against all nodes hiding cause when Schema Registry fails > to bootstrap during HDF 3.0 cluster install > > > Key: AMBARI-21495 > URL: https://issues.apache.org/jira/browse/AMBARI-21495 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.1 > Environment: HDF 3.0 >Reporter: Hari Sekhon > Attachments: Ambari_all_warnings.png, > Ambari_all_warnings_random_services2.png, > Ambari_all_warnings_random_services3.png, > Ambari_all_warnings_random_services4_culprit.png, > Ambari_all_warnings_random_services.png > > > Ambari marks all nodes with warnings including component failure which should > have been shown as red failure. > This was caused by a failure to bootstrap the Registry Schema (AMBARI-21492), > but Ambari showed only warnings against all cluster hosts, while each host > had a blank warning against random components where it had aborted but there > was nothing wrong with those components so no error outputs. > The failure during Registry Startup bootstrap script should have been shown > as red failure not yellow warning as the only way I could find the root cause > was to go through the nodes one by one, which luckily this is a small 9 node > cluster a not a 50 - 100+ cluster as I might not have found it otherwise. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21490) Ambari Schema Upgrade fails : Unknown column 'from_version' in 'field list'
[
https://issues.apache.org/jira/browse/AMBARI-21490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-21490:
-
Status: Patch Available (was: In Progress)
> Ambari Schema Upgrade fails : Unknown column 'from_version' in 'field list'
> ---
>
> Key: AMBARI-21490
> URL: https://issues.apache.org/jira/browse/AMBARI-21490
> Project: Ambari
> Issue Type: Bug
> Components: ambari-sever
>Affects Versions: trunk, 2.5.2
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Blocker
> Fix For: trunk, 2.5.2
>
>
> {code}
> 2017-07-12 07:51:24,251 WARN
> com.hw.ambari.ui.tests.upgrade.AmbariUpgradeOnly.upgradeCluster(): Detected
> ambari-server version build is:
> 2017-07-12 07:51:24,860 WARN
> com.hw.ambari.ui.tests.upgrade.AmbariUpgradeOnly.upgradeCluster(): Detected
> ambari-server version hash is:
> {code}
> {code}
> 2017-07-12 07:51:26,092 INFO
> com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence():
> Sending command [ambari-server upgrade --verbose]
> 2017-07-12 07:51:26,092 INFO
> com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence():
> Sending command []
> 2017-07-12 07:52:02,688 INFO
> com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence():
> [OUTPUT STREAM]
> Using python /usr/bin/python
> Upgrading ambari-server
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Upgrade Ambari Server
> INFO: Updating Ambari Server properties in ambari.properties ...
> INFO: Updating Ambari Server properties in ambari-env.sh ...
> WARNING: Original file ambari-env.sh kept
> WARNING: Original file krb5JAASLogin.conf kept
> INFO: File krb5JAASLogin.conf updated.
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: No mpack replay logs found. Skipping replaying mpack commands
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Fixing database objects owner
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> Ambari Server configured for MySQL. Confirm you have made a backup of the
> Ambari Server database [y/n] (y)? INFO: Loading properties from
> /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Upgrading database schema
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: AMBARI_SERVER_LIB is not set, using default /usr/lib/ambari-server
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: about to run command: /usr/jdk64/jdk1.7.0_67/bin/java -cp
> '/etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/mysql-connector-java.jar'
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper >
> /var/log/ambari-server/ambari-server.out 2>&1
> INFO:
> process_pid=22161
> INFO: Return code from schema upgrade command, retcode = 1
> ERROR: Error executing schema upgrade, please check the server logs.
> ERROR: Error output from schema upgrade command:
> ERROR: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown
> column 'from_version' in 'field list'
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> at com.mysql.jdbc.Util.handleNewInstance(Util.java:377)
> at com.mysql.jdbc.Util.getInstance(Util.java:360)
> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:978)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3887)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3823)
> at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2435)
> at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2582)
> at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2526)
> at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2484)
> at com.mysql.jdbc.StatementImpl.executeQuery(StatementImpl.java:1446)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog220.populateUpgradeTable(UpgradeCatalog220.java:517)
> at
[jira] [Commented] (AMBARI-21488) Default Base URL should be there for OS_TYPE=redhat-ppc6 in IBM Power and change the OS _TYPE to redhat7-ppc64
[
https://issues.apache.org/jira/browse/AMBARI-21488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16089843#comment-16089843
]
Hudson commented on AMBARI-21488:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7775 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7775/])
AMBARI-21488 Default Base URL should be there for OS_TYPE=redhat-ppc6 in
(atkach:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ba2a29fd1da5aa264e7873e306c9320e0d3b2a45])
* (edit)
ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/stackVersions/StackVersionsCreateCtrl.js
> Default Base URL should be there for OS_TYPE=redhat-ppc6 in IBM Power and
> change the OS _TYPE to redhat7-ppc64
> --
>
> Key: AMBARI-21488
> URL: https://issues.apache.org/jira/browse/AMBARI-21488
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.2
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.5.2
>
> Attachments: AMBARI-21488.patch, image-2017-07-10-17-12-04-754.png
>
>
> Default HDP-UTILS repo can be
> {code}
> HDP-UTILS-1.1.0.21
> http://public-repo-1.hortonworks.com/HDP-UTILS-1.1.0.21/repos/ppc64le
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21494) BI 4.2 Ranger Needs Properties Added on Ambari Upgrade
[ https://issues.apache.org/jira/browse/AMBARI-21494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-21494: - Status: Patch Available (was: Open) > BI 4.2 Ranger Needs Properties Added on Ambari Upgrade > -- > > Key: AMBARI-21494 > URL: https://issues.apache.org/jira/browse/AMBARI-21494 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.2 >Reporter: Jonathan Hurley >Assignee: Jonathan Hurley >Priority: Blocker > Fix For: 2.5.2 > > Attachments: AMBARI-21494.patch > > > The following two properties were added to Ranger 0.5.0 for Ambari 2.5.0. > However, since BigInsight 4.2.0 doesn't extend common services, these need to > be added for the upgrade from Ambari 2.4.2 to 2.5: > - ranger.ldap.binddn.credential.alias > - ranger.ldap.ad.binddn.credential.alias > Reference commit: > https://github.com/apache/ambari/commit/0d9d31fe3f8ace4a7ad710df34fe5ccba4b66df1#diff-1ae96dddc715cc510335ca0bcb698c23 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21494) BI 4.2 Ranger Needs Properties Added on Ambari Upgrade
[ https://issues.apache.org/jira/browse/AMBARI-21494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-21494: - Attachment: AMBARI-21494.patch > BI 4.2 Ranger Needs Properties Added on Ambari Upgrade > -- > > Key: AMBARI-21494 > URL: https://issues.apache.org/jira/browse/AMBARI-21494 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.2 >Reporter: Jonathan Hurley >Assignee: Jonathan Hurley >Priority: Blocker > Fix For: 2.5.2 > > Attachments: AMBARI-21494.patch > > > The following two properties were added to Ranger 0.5.0 for Ambari 2.5.0. > However, since BigInsight 4.2.0 doesn't extend common services, these need to > be added for the upgrade from Ambari 2.4.2 to 2.5: > - ranger.ldap.binddn.credential.alias > - ranger.ldap.ad.binddn.credential.alias > Reference commit: > https://github.com/apache/ambari/commit/0d9d31fe3f8ace4a7ad710df34fe5ccba4b66df1#diff-1ae96dddc715cc510335ca0bcb698c23 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21488) Default Base URL should be there for OS_TYPE=redhat-ppc6 in IBM Power and change the OS _TYPE to redhat7-ppc64
[
https://issues.apache.org/jira/browse/AMBARI-21488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16089833#comment-16089833
]
Hudson commented on AMBARI-21488:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1698 (See
[https://builds.apache.org/job/Ambari-branch-2.5/1698/])
AMBARI-21488 Default Base URL should be there for OS_TYPE=redhat-ppc6 in
(atkach:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=55da4262661dc1b3d123a9d3230a220e6d2bd9bf])
* (edit)
ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/stackVersions/StackVersionsCreateCtrl.js
> Default Base URL should be there for OS_TYPE=redhat-ppc6 in IBM Power and
> change the OS _TYPE to redhat7-ppc64
> --
>
> Key: AMBARI-21488
> URL: https://issues.apache.org/jira/browse/AMBARI-21488
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.2
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.5.2
>
> Attachments: AMBARI-21488.patch, image-2017-07-10-17-12-04-754.png
>
>
> Default HDP-UTILS repo can be
> {code}
> HDP-UTILS-1.1.0.21
> http://public-repo-1.hortonworks.com/HDP-UTILS-1.1.0.21/repos/ppc64le
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21492) HDF 3.0 Schema Registry support for offline install, mysql-connector-java.jar bootstrap fails to fetch from internet
[ https://issues.apache.org/jira/browse/AMBARI-21492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16089830#comment-16089830 ] Hari Sekhon commented on AMBARI-21492: -- Technically it's the Registry start phase that the bootstrap exists in so there is no install retry, Ambari only gives the next button option to complete regardless. > HDF 3.0 Schema Registry support for offline install, mysql-connector-java.jar > bootstrap fails to fetch from internet > > > Key: AMBARI-21492 > URL: https://issues.apache.org/jira/browse/AMBARI-21492 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.1 > Environment: HDF 3.0 on Suse 12 >Reporter: Hari Sekhon > Attachments: > Ambari_Schema_Registry_failure_fetching_mysql_connector.txt > > > Add support for offline install of Schema Registry. > When doing an offline install of HDF 3.0 via Ambari 2.5.1 it fails to set up > the Registry service as it assumes internet access and tries to pull down the > mysql-connector-java-5.1.40.zip from dev.mysql.com directly which fails. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21494) BI 4.2 Ranger Needs Properties Added on Ambari Upgrade
Jonathan Hurley created AMBARI-21494: Summary: BI 4.2 Ranger Needs Properties Added on Ambari Upgrade Key: AMBARI-21494 URL: https://issues.apache.org/jira/browse/AMBARI-21494 Project: Ambari Issue Type: Bug Affects Versions: 2.5.2 Reporter: Jonathan Hurley Assignee: Jonathan Hurley Priority: Blocker Fix For: 2.5.2 The following two properties were added to Ranger 0.5.0 for Ambari 2.5.0. However, since BigInsight 4.2.0 doesn't extend common services, these need to be added for the upgrade from Ambari 2.4.2 to 2.5: - ranger.ldap.binddn.credential.alias - ranger.ldap.ad.binddn.credential.alias Reference commit: https://github.com/apache/ambari/commit/0d9d31fe3f8ace4a7ad710df34fe5ccba4b66df1#diff-1ae96dddc715cc510335ca0bcb698c23 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21493) Fix PERF stack scripts to handle changed config paths
[
https://issues.apache.org/jira/browse/AMBARI-21493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16089826#comment-16089826
]
Hadoop QA commented on AMBARI-21493:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12877584/AMBARI-21493.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11801//console
This message is automatically generated.
> Fix PERF stack scripts to handle changed config paths
> -
>
> Key: AMBARI-21493
> URL: https://issues.apache.org/jira/browse/AMBARI-21493
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-21493.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
