[jira] [Commented] (AMBARI-19277) Assemblies page: fix issues after upgraded to bootstrap 3.x
[
https://issues.apache.org/jira/browse/AMBARI-19277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15769414#comment-15769414
]
Hadoop QA commented on AMBARI-19277:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12844342/AMBARI-19227.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/9778//console
This message is automatically generated.
> Assemblies page: fix issues after upgraded to bootstrap 3.x
> ---
>
> Key: AMBARI-19277
> URL: https://issues.apache.org/jira/browse/AMBARI-19277
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Xi Wang
>Assignee: Xi Wang
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-19227.patch, Assemblies page Correct 2.png,
> Assemblies page Correct small screen.png, Assemblies page Correct.png,
> Assemblies page Current - fix content.png, Assemblies page Current - fix
> outlines.png, Assemblies page Current.png, Assemblies page patch applied
> .png, Assemblies page patch applied 2 .png
>
>
> Attached are original Assemblies page and current pages after upgraded to
> bootstrap 3.0.
> Issues to fix:
> *Outline:*
> * Background of whole page should be grey.
> * Top bar
> * Left menu
> *Apps and Details:*
> * The black large image is not shown completely
> * Should display 5 apps each row
> * Details for each app
> Also Make sure everything looks good on small screen as well
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19275) Single API to download all client configs
[
https://issues.apache.org/jira/browse/AMBARI-19275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15769504#comment-15769504
]
Hadoop QA commented on AMBARI-19275:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12844318/AMBARI-19275.1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9779//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9779//console
This message is automatically generated.
> Single API to download all client configs
> --
>
> Key: AMBARI-19275
> URL: https://issues.apache.org/jira/browse/AMBARI-19275
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jaimin Jetly
>Assignee: Jaimin Jetly
> Fix For: 2.5.0
>
> Attachments: AMBARI-19275.1.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19228) Knox doesn't redirect to Atlas after entering correct credentials, when Atlas is setup with Knox-SSO
[ https://issues.apache.org/jira/browse/AMBARI-19228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15769565#comment-15769565 ] Hudson commented on AMBARI-19228: - ABORTED: Integrated in Jenkins build Ambari-branch-2.5 #567 (See [https://builds.apache.org/job/Ambari-branch-2.5/567/]) AMBARI-19228 : Knox doesn't redirect to Atlas after entering correct (mugdha: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=fa4dab96db0e7dab7f6d46dab5a91b53cd69a0ca]) * (edit) ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/package/scripts/params.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/ATLAS/themes/theme_version_2.json * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/ATLAS/configuration/application-properties.xml > Knox doesn't redirect to Atlas after entering correct credentials, when Atlas > is setup with Knox-SSO > > > Key: AMBARI-19228 > URL: https://issues.apache.org/jira/browse/AMBARI-19228 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19228.patch > > > After enabling Atlas with Knox-SSO, user is not able to sign-in. but lands > back on the login page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19265) Zeppelin fails to install when hive-site.xml does not exist in spark conf directory
[ https://issues.apache.org/jira/browse/AMBARI-19265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15769618#comment-15769618 ] Hudson commented on AMBARI-19265: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #568 (See [https://builds.apache.org/job/Ambari-branch-2.5/568/]) AMBARI-19265 Zeppelin fails to install when hive-site.xml does not (renjith.kamath: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=66cb2f3bd14e39a6468b07981eba7fe3f5cf2e48]) * (edit) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py > Zeppelin fails to install when hive-site.xml does not exist in spark conf > directory > --- > > Key: AMBARI-19265 > URL: https://issues.apache.org/jira/browse/AMBARI-19265 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Renjith Kamath >Assignee: Renjith Kamath > Fix For: 2.5.0 > > Attachments: AMBARI-19265-branch-2.5-v1.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19267) NN HA Namespace input "jumps" when invalid value provided
[ https://issues.apache.org/jira/browse/AMBARI-19267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15769644#comment-15769644 ] Oleg Nechiporenko commented on AMBARI-19267: Patch was already committed > NN HA Namespace input "jumps" when invalid value provided > - > > Key: AMBARI-19267 > URL: https://issues.apache.org/jira/browse/AMBARI-19267 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > Attachments: AMBARI-19267.patch > > > Namespace input becomes full-width when some invalid value provided. Input > should always look the same. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19267) NN HA Namespace input "jumps" when invalid value provided
[ https://issues.apache.org/jira/browse/AMBARI-19267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko updated AMBARI-19267: --- Resolution: Fixed Status: Resolved (was: Patch Available) > NN HA Namespace input "jumps" when invalid value provided > - > > Key: AMBARI-19267 > URL: https://issues.apache.org/jira/browse/AMBARI-19267 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > Attachments: AMBARI-19267.patch > > > Namespace input becomes full-width when some invalid value provided. Input > should always look the same. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19267) NN HA Namespace input "jumps" when invalid value provided
[
https://issues.apache.org/jira/browse/AMBARI-19267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15769643#comment-15769643
]
Oleg Nechiporenko commented on AMBARI-19267:
Build failed not because of this patch
{noformat}
[INFO] Ambari Web . SUCCESS [04:26 min]
[INFO] Ambari Server .. FAILURE [16:56 min]
{noformat}
> NN HA Namespace input "jumps" when invalid value provided
> -
>
> Key: AMBARI-19267
> URL: https://issues.apache.org/jira/browse/AMBARI-19267
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-19267.patch
>
>
> Namespace input becomes full-width when some invalid value provided. Input
> should always look the same.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19279) AHW Configurations page looks not like any other wizard page
Oleg Nechiporenko created AMBARI-19279: -- Summary: AHW Configurations page looks not like any other wizard page Key: AMBARI-19279 URL: https://issues.apache.org/jira/browse/AMBARI-19279 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Oleg Nechiporenko Assignee: Oleg Nechiporenko Fix For: 3.0.0 Configurations page on AHW wasn't updated when Ambari Theme was created. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19279) AHW Configurations page looks not like any other wizard page
[ https://issues.apache.org/jira/browse/AMBARI-19279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko updated AMBARI-19279: --- Attachment: AMBARI-19279.patch > AHW Configurations page looks not like any other wizard page > > > Key: AMBARI-19279 > URL: https://issues.apache.org/jira/browse/AMBARI-19279 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > Attachments: AMBARI-19279.patch > > > Configurations page on AHW wasn't updated when Ambari Theme was created. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19078) Atlas service check reports false positive
[
https://issues.apache.org/jira/browse/AMBARI-19078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Toader updated AMBARI-19078:
--
Assignee: Andrew Onischuk
> Atlas service check reports false positive
> --
>
> Key: AMBARI-19078
> URL: https://issues.apache.org/jira/browse/AMBARI-19078
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Ayub Khan
>Assignee: Andrew Onischuk
>
> Atlas service check is successful even if the service does not return 200 ok.
> {noformat}
> 2016-12-05 07:24:23,768 - Stack Feature Version Info: stack_version=2.5,
> version=None, current_cluster_version=2.5.3.0-35 -> 2.5
> 2016-12-05 07:24:23,777 - Using hadoop conf dir:
> /usr/hdp/current/hadoop-client/conf
> 2016-12-05 07:24:23,795 - Execute['/usr/bin/kinit -kt
> /etc/security/keytabs/smokeuser.headless.keytab ambari-qa-...@example.com']
> {'user': 'ambari-qa'}
> 2016-12-05 07:24:23,899 - Execute['curl --negotiate -u : -b ~/cookiejar.txt
> -c ~/cookiejar.txt -s -o /dev/null -w "%{http_code}"
> https://ctr-e61-1479789298070-4849-01-03.hwx.site:21443/'] {'tries': 5,
> 'user': 'ambari-qa', 'try_sleep': 10}
> 2016-12-05 07:24:24,162 - Retrying after 10 seconds. Reason: Execution of
> 'curl --negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null
> -w "%{http_code}"
> https://ctr-e61-1479789298070-4849-01-03.hwx.site:21443/' returned 60. 000
> 2016-12-05 07:24:34,451 - Retrying after 10 seconds. Reason: Execution of
> 'curl --negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null
> -w "%{http_code}"
> https://ctr-e61-1479789298070-4849-01-03.hwx.site:21443/' returned 60. 000
> 2016-12-05 07:24:44,714 - Retrying after 10 seconds. Reason: Execution of
> 'curl --negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null
> -w "%{http_code}"
> https://ctr-e61-1479789298070-4849-01-03.hwx.site:21443/' returned 60. 000
> 2016-12-05 07:24:55,031 - Retrying after 10 seconds. Reason: Execution of
> 'curl --negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null
> -w "%{http_code}"
> https://ctr-e61-1479789298070-4849-01-03.hwx.site:21443/' returned 60. 000
> Command completed successfully!
> {noformat}
> And ideally this should check for this API "/api/atlas/admin/status" and
> return true if the http response code is 200 OK.
> CC; [~mneethiraj] [~skoneru]
> {noformat}
> [root@ctr-e61-1479789298070-4849-01-03 scripts]# rpm -qa | grep
> ambari-server
> ambari-server-2.4.2.0-136.x86_64
> [root@ctr-e61-1479789298070-4849-01-03 scripts]# rpm -qa | grep atlas
> atlas-metadata_2_5_3_0_35-0.7.0.2.5.3.0-35.el6.noarch
> ranger_2_5_3_0_35-atlas-plugin-0.6.0.2.5.3.0-35.el6.x86_64
> atlas-metadata_2_5_3_0_35-hive-plugin-0.7.0.2.5.3.0-35.el6.noarch
> atlas-3.10.1-10.el7.x86_64
> [root@ctr-e61-1479789298070-4849-01-03 scripts]#
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19078) Atlas service check reports false positive
[
https://issues.apache.org/jira/browse/AMBARI-19078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Toader updated AMBARI-19078:
--
Fix Version/s: 2.5.0
> Atlas service check reports false positive
> --
>
> Key: AMBARI-19078
> URL: https://issues.apache.org/jira/browse/AMBARI-19078
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Ayub Khan
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
>
> Atlas service check is successful even if the service does not return 200 ok.
> {noformat}
> 2016-12-05 07:24:23,768 - Stack Feature Version Info: stack_version=2.5,
> version=None, current_cluster_version=2.5.3.0-35 -> 2.5
> 2016-12-05 07:24:23,777 - Using hadoop conf dir:
> /usr/hdp/current/hadoop-client/conf
> 2016-12-05 07:24:23,795 - Execute['/usr/bin/kinit -kt
> /etc/security/keytabs/smokeuser.headless.keytab ambari-qa-...@example.com']
> {'user': 'ambari-qa'}
> 2016-12-05 07:24:23,899 - Execute['curl --negotiate -u : -b ~/cookiejar.txt
> -c ~/cookiejar.txt -s -o /dev/null -w "%{http_code}"
> https://ctr-e61-1479789298070-4849-01-03.hwx.site:21443/'] {'tries': 5,
> 'user': 'ambari-qa', 'try_sleep': 10}
> 2016-12-05 07:24:24,162 - Retrying after 10 seconds. Reason: Execution of
> 'curl --negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null
> -w "%{http_code}"
> https://ctr-e61-1479789298070-4849-01-03.hwx.site:21443/' returned 60. 000
> 2016-12-05 07:24:34,451 - Retrying after 10 seconds. Reason: Execution of
> 'curl --negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null
> -w "%{http_code}"
> https://ctr-e61-1479789298070-4849-01-03.hwx.site:21443/' returned 60. 000
> 2016-12-05 07:24:44,714 - Retrying after 10 seconds. Reason: Execution of
> 'curl --negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null
> -w "%{http_code}"
> https://ctr-e61-1479789298070-4849-01-03.hwx.site:21443/' returned 60. 000
> 2016-12-05 07:24:55,031 - Retrying after 10 seconds. Reason: Execution of
> 'curl --negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null
> -w "%{http_code}"
> https://ctr-e61-1479789298070-4849-01-03.hwx.site:21443/' returned 60. 000
> Command completed successfully!
> {noformat}
> And ideally this should check for this API "/api/atlas/admin/status" and
> return true if the http response code is 200 OK.
> CC; [~mneethiraj] [~skoneru]
> {noformat}
> [root@ctr-e61-1479789298070-4849-01-03 scripts]# rpm -qa | grep
> ambari-server
> ambari-server-2.4.2.0-136.x86_64
> [root@ctr-e61-1479789298070-4849-01-03 scripts]# rpm -qa | grep atlas
> atlas-metadata_2_5_3_0_35-0.7.0.2.5.3.0-35.el6.noarch
> ranger_2_5_3_0_35-atlas-plugin-0.6.0.2.5.3.0-35.el6.x86_64
> atlas-metadata_2_5_3_0_35-hive-plugin-0.7.0.2.5.3.0-35.el6.noarch
> atlas-3.10.1-10.el7.x86_64
> [root@ctr-e61-1479789298070-4849-01-03 scripts]#
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (AMBARI-19078) Atlas service check reports false positive
[
https://issues.apache.org/jira/browse/AMBARI-19078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Toader resolved AMBARI-19078.
---
Resolution: Fixed
This has been already fixed by AMBARI-18428 for trunk. The fix is committed to
2.5 now
commit e675c63bc9adbc6fc2cf961aa24fac4254543f29
> Atlas service check reports false positive
> --
>
> Key: AMBARI-19078
> URL: https://issues.apache.org/jira/browse/AMBARI-19078
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Ayub Khan
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
>
> Atlas service check is successful even if the service does not return 200 ok.
> {noformat}
> 2016-12-05 07:24:23,768 - Stack Feature Version Info: stack_version=2.5,
> version=None, current_cluster_version=2.5.3.0-35 -> 2.5
> 2016-12-05 07:24:23,777 - Using hadoop conf dir:
> /usr/hdp/current/hadoop-client/conf
> 2016-12-05 07:24:23,795 - Execute['/usr/bin/kinit -kt
> /etc/security/keytabs/smokeuser.headless.keytab ambari-qa-...@example.com']
> {'user': 'ambari-qa'}
> 2016-12-05 07:24:23,899 - Execute['curl --negotiate -u : -b ~/cookiejar.txt
> -c ~/cookiejar.txt -s -o /dev/null -w "%{http_code}"
> https://ctr-e61-1479789298070-4849-01-03.hwx.site:21443/'] {'tries': 5,
> 'user': 'ambari-qa', 'try_sleep': 10}
> 2016-12-05 07:24:24,162 - Retrying after 10 seconds. Reason: Execution of
> 'curl --negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null
> -w "%{http_code}"
> https://ctr-e61-1479789298070-4849-01-03.hwx.site:21443/' returned 60. 000
> 2016-12-05 07:24:34,451 - Retrying after 10 seconds. Reason: Execution of
> 'curl --negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null
> -w "%{http_code}"
> https://ctr-e61-1479789298070-4849-01-03.hwx.site:21443/' returned 60. 000
> 2016-12-05 07:24:44,714 - Retrying after 10 seconds. Reason: Execution of
> 'curl --negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null
> -w "%{http_code}"
> https://ctr-e61-1479789298070-4849-01-03.hwx.site:21443/' returned 60. 000
> 2016-12-05 07:24:55,031 - Retrying after 10 seconds. Reason: Execution of
> 'curl --negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null
> -w "%{http_code}"
> https://ctr-e61-1479789298070-4849-01-03.hwx.site:21443/' returned 60. 000
> Command completed successfully!
> {noformat}
> And ideally this should check for this API "/api/atlas/admin/status" and
> return true if the http response code is 200 OK.
> CC; [~mneethiraj] [~skoneru]
> {noformat}
> [root@ctr-e61-1479789298070-4849-01-03 scripts]# rpm -qa | grep
> ambari-server
> ambari-server-2.4.2.0-136.x86_64
> [root@ctr-e61-1479789298070-4849-01-03 scripts]# rpm -qa | grep atlas
> atlas-metadata_2_5_3_0_35-0.7.0.2.5.3.0-35.el6.noarch
> ranger_2_5_3_0_35-atlas-plugin-0.6.0.2.5.3.0-35.el6.x86_64
> atlas-metadata_2_5_3_0_35-hive-plugin-0.7.0.2.5.3.0-35.el6.noarch
> atlas-3.10.1-10.el7.x86_64
> [root@ctr-e61-1479789298070-4849-01-03 scripts]#
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19279) AHW Configurations page looks not like any other wizard page
[ https://issues.apache.org/jira/browse/AMBARI-19279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15769727#comment-15769727 ] Oleg Nechiporenko commented on AMBARI-19279: +1 by [~akovalenko] on the review board > AHW Configurations page looks not like any other wizard page > > > Key: AMBARI-19279 > URL: https://issues.apache.org/jira/browse/AMBARI-19279 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > Attachments: AMBARI-19279.patch > > > Configurations page on AHW wasn't updated when Ambari Theme was created. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19268) ulimit override missing from upgrade catalogs
[
https://issues.apache.org/jira/browse/AMBARI-19268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen updated AMBARI-19268:
Attachment: AMBARI-19268_5.patch
> ulimit override missing from upgrade catalogs
> -
>
> Key: AMBARI-19268
> URL: https://issues.apache.org/jira/browse/AMBARI-19268
> Project: Ambari
> Issue Type: Bug
> Components: ambari-upgrade
>Affects Versions: 2.2.2
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19268_5.patch
>
>
> After upgrade from 2.0.0 hadoop-env doesn't contain:
> {noformat}
> {% if is_datanode_max_locked_memory_set %}
> # Fix temporary bug, when ulimit from conf files is not picked up, without
> full relogin.
> # Makes sense to fix only when runing DN as root
> if [ "$command" == "datanode" ] && [ "$EUID" -eq 0 ] && [ -n
> "$HADOOP_SECURE_DN_USER" ]; then
> ulimit -l {{datanode_max_locked_memory}}
> fi
> {% endif %}
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19268) ulimit override missing from upgrade catalogs
[
https://issues.apache.org/jira/browse/AMBARI-19268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen updated AMBARI-19268:
Status: Patch Available (was: Open)
> ulimit override missing from upgrade catalogs
> -
>
> Key: AMBARI-19268
> URL: https://issues.apache.org/jira/browse/AMBARI-19268
> Project: Ambari
> Issue Type: Bug
> Components: ambari-upgrade
>Affects Versions: 2.2.2
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19268_5.patch
>
>
> After upgrade from 2.0.0 hadoop-env doesn't contain:
> {noformat}
> {% if is_datanode_max_locked_memory_set %}
> # Fix temporary bug, when ulimit from conf files is not picked up, without
> full relogin.
> # Makes sense to fix only when runing DN as root
> if [ "$command" == "datanode" ] && [ "$EUID" -eq 0 ] && [ -n
> "$HADOOP_SECURE_DN_USER" ]; then
> ulimit -l {{datanode_max_locked_memory}}
> fi
> {% endif %}
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19268) ulimit override missing from upgrade catalogs
[
https://issues.apache.org/jira/browse/AMBARI-19268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen updated AMBARI-19268:
Status: Open (was: Patch Available)
> ulimit override missing from upgrade catalogs
> -
>
> Key: AMBARI-19268
> URL: https://issues.apache.org/jira/browse/AMBARI-19268
> Project: Ambari
> Issue Type: Bug
> Components: ambari-upgrade
>Affects Versions: 2.2.2
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19268_5.patch
>
>
> After upgrade from 2.0.0 hadoop-env doesn't contain:
> {noformat}
> {% if is_datanode_max_locked_memory_set %}
> # Fix temporary bug, when ulimit from conf files is not picked up, without
> full relogin.
> # Makes sense to fix only when runing DN as root
> if [ "$command" == "datanode" ] && [ "$EUID" -eq 0 ] && [ -n
> "$HADOOP_SECURE_DN_USER" ]; then
> ulimit -l {{datanode_max_locked_memory}}
> fi
> {% endif %}
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19268) ulimit override missing from upgrade catalogs
[
https://issues.apache.org/jira/browse/AMBARI-19268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen updated AMBARI-19268:
Attachment: (was: AMBARI-19268_4.patch)
> ulimit override missing from upgrade catalogs
> -
>
> Key: AMBARI-19268
> URL: https://issues.apache.org/jira/browse/AMBARI-19268
> Project: Ambari
> Issue Type: Bug
> Components: ambari-upgrade
>Affects Versions: 2.2.2
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19268_5.patch
>
>
> After upgrade from 2.0.0 hadoop-env doesn't contain:
> {noformat}
> {% if is_datanode_max_locked_memory_set %}
> # Fix temporary bug, when ulimit from conf files is not picked up, without
> full relogin.
> # Makes sense to fix only when runing DN as root
> if [ "$command" == "datanode" ] && [ "$EUID" -eq 0 ] && [ -n
> "$HADOOP_SECURE_DN_USER" ]; then
> ulimit -l {{datanode_max_locked_memory}}
> fi
> {% endif %}
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18428) Atlas service check never fails
[ https://issues.apache.org/jira/browse/AMBARI-18428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15769772#comment-15769772 ] Hudson commented on AMBARI-18428: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #569 (See [https://builds.apache.org/job/Ambari-branch-2.5/569/]) AMBARI-18428. Atlas service check never fails (aonishuk) (stoader: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=e675c63bc9adbc6fc2cf961aa24fac4254543f29]) * (edit) ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/package/scripts/params.py * (edit) ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/package/scripts/service_check.py > Atlas service check never fails > --- > > Key: AMBARI-18428 > URL: https://issues.apache.org/jira/browse/AMBARI-18428 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 3.0.0 > > Attachments: AMBARI-18428.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19279) AHW Configurations page looks not like any other wizard page
[ https://issues.apache.org/jira/browse/AMBARI-19279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko updated AMBARI-19279: --- Status: Patch Available (was: Open) > AHW Configurations page looks not like any other wizard page > > > Key: AMBARI-19279 > URL: https://issues.apache.org/jira/browse/AMBARI-19279 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > Attachments: AMBARI-19279.patch > > > Configurations page on AHW wasn't updated when Ambari Theme was created. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19280) Cover global controllers with unit tests
Andrii Tkach created AMBARI-19280: - Summary: Cover global controllers with unit tests Key: AMBARI-19280 URL: https://issues.apache.org/jira/browse/AMBARI-19280 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 3.0.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Fix For: 3.0.0 Cover following files: * /ambari-web/app/controllers/global/background_operations_controller.js * /ambari-web/app/controllers/global/cluster_controller.js * /ambari-web/app/controllers/global/configuration_controller.js * /ambari-web/app/controllers/global/errors_handler_controller.js * /ambari-web/app/controllers/global/update_controller.js * /ambari-web/app/controllers/global/user_settings_controller.js * /ambari-web/app/controllers/global/wizard_watcher_controller.js -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19280) Cover global controllers with unit tests
[ https://issues.apache.org/jira/browse/AMBARI-19280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-19280: -- Attachment: AMBARI-19280.patch > Cover global controllers with unit tests > > > Key: AMBARI-19280 > URL: https://issues.apache.org/jira/browse/AMBARI-19280 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-19280.patch > > > Cover following files: > * /ambari-web/app/controllers/global/background_operations_controller.js > * /ambari-web/app/controllers/global/cluster_controller.js > * /ambari-web/app/controllers/global/configuration_controller.js > * /ambari-web/app/controllers/global/errors_handler_controller.js > * /ambari-web/app/controllers/global/update_controller.js > * /ambari-web/app/controllers/global/user_settings_controller.js > * /ambari-web/app/controllers/global/wizard_watcher_controller.js -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19280) Cover global controllers with unit tests
[ https://issues.apache.org/jira/browse/AMBARI-19280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15769816#comment-15769816 ] Andrii Tkach commented on AMBARI-19280: --- 19847 passing (26s) 153 pending > Cover global controllers with unit tests > > > Key: AMBARI-19280 > URL: https://issues.apache.org/jira/browse/AMBARI-19280 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-19280.patch > > > Cover following files: > * /ambari-web/app/controllers/global/background_operations_controller.js > * /ambari-web/app/controllers/global/cluster_controller.js > * /ambari-web/app/controllers/global/configuration_controller.js > * /ambari-web/app/controllers/global/errors_handler_controller.js > * /ambari-web/app/controllers/global/update_controller.js > * /ambari-web/app/controllers/global/user_settings_controller.js > * /ambari-web/app/controllers/global/wizard_watcher_controller.js -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19280) Cover global controllers with unit tests
[ https://issues.apache.org/jira/browse/AMBARI-19280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-19280: -- Status: Patch Available (was: Open) > Cover global controllers with unit tests > > > Key: AMBARI-19280 > URL: https://issues.apache.org/jira/browse/AMBARI-19280 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-19280.patch > > > Cover following files: > * /ambari-web/app/controllers/global/background_operations_controller.js > * /ambari-web/app/controllers/global/cluster_controller.js > * /ambari-web/app/controllers/global/configuration_controller.js > * /ambari-web/app/controllers/global/errors_handler_controller.js > * /ambari-web/app/controllers/global/update_controller.js > * /ambari-web/app/controllers/global/user_settings_controller.js > * /ambari-web/app/controllers/global/wizard_watcher_controller.js -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19268) ulimit override missing from upgrade catalogs
[
https://issues.apache.org/jira/browse/AMBARI-19268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15769846#comment-15769846
]
Hadoop QA commented on AMBARI-19268:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12844380/AMBARI-19268_5.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.topology.AsyncCallableServiceTest
org.apache.ambari.server.state.cluster.ClusterDeadlockTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9781//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9781//console
This message is automatically generated.
> ulimit override missing from upgrade catalogs
> -
>
> Key: AMBARI-19268
> URL: https://issues.apache.org/jira/browse/AMBARI-19268
> Project: Ambari
> Issue Type: Bug
> Components: ambari-upgrade
>Affects Versions: 2.2.2
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19268_5.patch
>
>
> After upgrade from 2.0.0 hadoop-env doesn't contain:
> {noformat}
> {% if is_datanode_max_locked_memory_set %}
> # Fix temporary bug, when ulimit from conf files is not picked up, without
> full relogin.
> # Makes sense to fix only when runing DN as root
> if [ "$command" == "datanode" ] && [ "$EUID" -eq 0 ] && [ -n
> "$HADOOP_SECURE_DN_USER" ]; then
> ulimit -l {{datanode_max_locked_memory}}
> fi
> {% endif %}
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19255) Add some properties for Oozie 4.3.0
[ https://issues.apache.org/jira/browse/AMBARI-19255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pingwang updated AMBARI-19255: -- Summary: Add some properties for Oozie 4.3.0 (was: Add RM/JT and NN properties for Oozie 4.3.0 ) > Add some properties for Oozie 4.3.0 > > > Key: AMBARI-19255 > URL: https://issues.apache.org/jira/browse/AMBARI-19255 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.2 >Reporter: pingwang > Attachments: AMBARI-19255.patch > > > In Oozie new release 4.3.0, OOZIE-2187 added configuration properties to > oozie-site that would let users specify a default RM/JT and NN to use. > I created this JIRA to add the two properties into Ambari Oozie configuration > settings. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19255) Add some properties for Oozie 4.3.0
[ https://issues.apache.org/jira/browse/AMBARI-19255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pingwang updated AMBARI-19255: -- Attachment: (was: AMBARI-19255.patch) > Add some properties for Oozie 4.3.0 > > > Key: AMBARI-19255 > URL: https://issues.apache.org/jira/browse/AMBARI-19255 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.2 >Reporter: pingwang > > In Oozie new release 4.3.0: > OOZIE-2187 added configuration properties to oozie-site that would let users > specify a default RM/JT and NN to use. > OOZIE-2185 add new oozie-client-env.sh file for users defining environment > variables and can have the oozie cli source them. > I created this JIRA to add the properties into Ambari Oozie configuration > settings. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19255) Add some properties for Oozie 4.3.0
[ https://issues.apache.org/jira/browse/AMBARI-19255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pingwang updated AMBARI-19255: -- Description: In Oozie new release 4.3.0: OOZIE-2187 added configuration properties to oozie-site that would let users specify a default RM/JT and NN to use. OOZIE-2185 add new oozie-client-env.sh file for users defining environment variables and can have the oozie cli source them. I created this JIRA to add the properties into Ambari Oozie configuration settings. was: In Oozie new release 4.3.0, OOZIE-2187 added configuration properties to oozie-site that would let users specify a default RM/JT and NN to use. I created this JIRA to add the two properties into Ambari Oozie configuration settings. > Add some properties for Oozie 4.3.0 > > > Key: AMBARI-19255 > URL: https://issues.apache.org/jira/browse/AMBARI-19255 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.2 >Reporter: pingwang > > In Oozie new release 4.3.0: > OOZIE-2187 added configuration properties to oozie-site that would let users > specify a default RM/JT and NN to use. > OOZIE-2185 add new oozie-client-env.sh file for users defining environment > variables and can have the oozie cli source them. > I created this JIRA to add the properties into Ambari Oozie configuration > settings. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19279) AHW Configurations page looks not like any other wizard page
[ https://issues.apache.org/jira/browse/AMBARI-19279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15769927#comment-15769927 ] Hudson commented on AMBARI-19279: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6279 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6279/]) AMBARI-19279. AHW Configurations page looks not like any other wizard (onechiporenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=bd3df7db06d43c78067df43e53209fd8aa1fac87]) * (edit) ambari-web/app/templates/main/host/addHost/step4.hbs > AHW Configurations page looks not like any other wizard page > > > Key: AMBARI-19279 > URL: https://issues.apache.org/jira/browse/AMBARI-19279 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 3.0.0 > > Attachments: AMBARI-19279.patch > > > Configurations page on AHW wasn't updated when Ambari Theme was created. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19281) Display properties for all affected services before adding or deleting ZooKeeper Server
Andrii Babiichuk created AMBARI-19281: - Summary: Display properties for all affected services before adding or deleting ZooKeeper Server Key: AMBARI-19281 URL: https://issues.apache.org/jira/browse/AMBARI-19281 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.5.0 Reporter: Andrii Babiichuk Assignee: Andrii Babiichuk Priority: Critical Fix For: 2.5.0 Only the changes for Storm configs are displayed inside the confirmation popup before adding and deleting ZooKeeper server. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19281) Display properties for all affected services before adding or deleting ZooKeeper Server
[ https://issues.apache.org/jira/browse/AMBARI-19281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-19281: -- Attachment: AMBARI-19281_trunk.patch > Display properties for all affected services before adding or deleting > ZooKeeper Server > --- > > Key: AMBARI-19281 > URL: https://issues.apache.org/jira/browse/AMBARI-19281 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19281_trunk.patch > > > Only the changes for Storm configs are displayed inside the confirmation > popup before adding and deleting ZooKeeper server. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19281) Display properties for all affected services before adding or deleting ZooKeeper Server
[ https://issues.apache.org/jira/browse/AMBARI-19281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-19281: -- Status: Patch Available (was: Open) > Display properties for all affected services before adding or deleting > ZooKeeper Server > --- > > Key: AMBARI-19281 > URL: https://issues.apache.org/jira/browse/AMBARI-19281 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19281_trunk.patch > > > Only the changes for Storm configs are displayed inside the confirmation > popup before adding and deleting ZooKeeper server. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19264) Zeppelin Notebook Component is not able start after reboot
[ https://issues.apache.org/jira/browse/AMBARI-19264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Renjith Kamath updated AMBARI-19264: Assignee: Renjith Kamath Fix Version/s: 2.5.0 Status: Patch Available (was: Open) > Zeppelin Notebook Component is not able start after reboot > --- > > Key: AMBARI-19264 > URL: https://issues.apache.org/jira/browse/AMBARI-19264 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Pradarttana >Assignee: Renjith Kamath > Fix For: 2.5.0 > > > Steps to reproduce:- > 1. reboot one of the host in ambari-cluster where zeppelin notebook is > installed > 2. Zeppelin Notebook start will failed saying "mkdir: cannot create directory > `/var/run/zeppelin': Permission denied" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19264) Zeppelin Notebook Component is not able start after reboot
[ https://issues.apache.org/jira/browse/AMBARI-19264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Renjith Kamath updated AMBARI-19264: Attachment: AMBARI-19264-branch-2.5-v1.patch > Zeppelin Notebook Component is not able start after reboot > --- > > Key: AMBARI-19264 > URL: https://issues.apache.org/jira/browse/AMBARI-19264 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Pradarttana >Assignee: Renjith Kamath > Fix For: 2.5.0 > > Attachments: AMBARI-19264-branch-2.5-v1.patch > > > Steps to reproduce:- > 1. reboot one of the host in ambari-cluster where zeppelin notebook is > installed > 2. Zeppelin Notebook start will failed saying "mkdir: cannot create directory > `/var/run/zeppelin': Permission denied" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19281) Display properties for all affected services before adding or deleting ZooKeeper Server
[
https://issues.apache.org/jira/browse/AMBARI-19281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15770038#comment-15770038
]
Hadoop QA commented on AMBARI-19281:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12844391/AMBARI-19281_trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9787//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9787//console
This message is automatically generated.
> Display properties for all affected services before adding or deleting
> ZooKeeper Server
> ---
>
> Key: AMBARI-19281
> URL: https://issues.apache.org/jira/browse/AMBARI-19281
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19281_trunk.patch
>
>
> Only the changes for Storm configs are displayed inside the confirmation
> popup before adding and deleting ZooKeeper server.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19281) Display properties for all affected services before adding or deleting ZooKeeper Server
[ https://issues.apache.org/jira/browse/AMBARI-19281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15770047#comment-15770047 ] Andrii Babiichuk commented on AMBARI-19281: --- Committed to trunk > Display properties for all affected services before adding or deleting > ZooKeeper Server > --- > > Key: AMBARI-19281 > URL: https://issues.apache.org/jira/browse/AMBARI-19281 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19281_trunk.patch > > > Only the changes for Storm configs are displayed inside the confirmation > popup before adding and deleting ZooKeeper server. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19268) ulimit override missing from upgrade catalogs
[
https://issues.apache.org/jira/browse/AMBARI-19268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen updated AMBARI-19268:
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk and branch-2.5
> ulimit override missing from upgrade catalogs
> -
>
> Key: AMBARI-19268
> URL: https://issues.apache.org/jira/browse/AMBARI-19268
> Project: Ambari
> Issue Type: Bug
> Components: ambari-upgrade
>Affects Versions: 2.2.2
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19268_5.patch
>
>
> After upgrade from 2.0.0 hadoop-env doesn't contain:
> {noformat}
> {% if is_datanode_max_locked_memory_set %}
> # Fix temporary bug, when ulimit from conf files is not picked up, without
> full relogin.
> # Makes sense to fix only when runing DN as root
> if [ "$command" == "datanode" ] && [ "$EUID" -eq 0 ] && [ -n
> "$HADOOP_SECURE_DN_USER" ]; then
> ulimit -l {{datanode_max_locked_memory}}
> fi
> {% endif %}
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19281) Display properties for all affected services before adding or deleting ZooKeeper Server
[ https://issues.apache.org/jira/browse/AMBARI-19281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15770114#comment-15770114 ] Hudson commented on AMBARI-19281: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6280 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6280/]) AMBARI-19281 Display properties for all affected services before adding (ababiichuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=0111c847ddc2367b8b1046f74d6ce65d6bbb331e]) * (edit) ambari-web/app/controllers/main/host/details.js * (edit) ambari-web/app/templates/main/host/details/addDeleteComponentPopup.hbs * (edit) ambari-web/test/controllers/main/host/details_test.js > Display properties for all affected services before adding or deleting > ZooKeeper Server > --- > > Key: AMBARI-19281 > URL: https://issues.apache.org/jira/browse/AMBARI-19281 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19281_trunk.patch > > > Only the changes for Storm configs are displayed inside the confirmation > popup before adding and deleting ZooKeeper server. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19280) Cover global controllers with unit tests
[
https://issues.apache.org/jira/browse/AMBARI-19280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15770118#comment-15770118
]
Hadoop QA commented on AMBARI-19280:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12844383/AMBARI-19280.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 6 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9788//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9788//console
This message is automatically generated.
> Cover global controllers with unit tests
>
>
> Key: AMBARI-19280
> URL: https://issues.apache.org/jira/browse/AMBARI-19280
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-19280.patch
>
>
> Cover following files:
> * /ambari-web/app/controllers/global/background_operations_controller.js
> * /ambari-web/app/controllers/global/cluster_controller.js
> * /ambari-web/app/controllers/global/configuration_controller.js
> * /ambari-web/app/controllers/global/errors_handler_controller.js
> * /ambari-web/app/controllers/global/update_controller.js
> * /ambari-web/app/controllers/global/user_settings_controller.js
> * /ambari-web/app/controllers/global/wizard_watcher_controller.js
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19268) ulimit override missing from upgrade catalogs
[
https://issues.apache.org/jira/browse/AMBARI-19268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15770165#comment-15770165
]
Hudson commented on AMBARI-19268:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #570 (See
[https://builds.apache.org/job/Ambari-branch-2.5/570/])
AMBARI-19268 ulimit override missing from upgrade catalogs (dsen) (dsen:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=762b86ef45461aecd7e730897a4e9dae01b50777])
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java
> ulimit override missing from upgrade catalogs
> -
>
> Key: AMBARI-19268
> URL: https://issues.apache.org/jira/browse/AMBARI-19268
> Project: Ambari
> Issue Type: Bug
> Components: ambari-upgrade
>Affects Versions: 2.2.2
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19268_5.patch
>
>
> After upgrade from 2.0.0 hadoop-env doesn't contain:
> {noformat}
> {% if is_datanode_max_locked_memory_set %}
> # Fix temporary bug, when ulimit from conf files is not picked up, without
> full relogin.
> # Makes sense to fix only when runing DN as root
> if [ "$command" == "datanode" ] && [ "$EUID" -eq 0 ] && [ -n
> "$HADOOP_SECURE_DN_USER" ]; then
> ulimit -l {{datanode_max_locked_memory}}
> fi
> {% endif %}
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19268) ulimit override missing from upgrade catalogs
[
https://issues.apache.org/jira/browse/AMBARI-19268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15770180#comment-15770180
]
Hudson commented on AMBARI-19268:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6281 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6281/])
AMBARI-19268 ulimit override missing from upgrade catalogs (dsen) (dsen:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=633ac3bd532654ea0eec9159d666f9cb43446b5d])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java
> ulimit override missing from upgrade catalogs
> -
>
> Key: AMBARI-19268
> URL: https://issues.apache.org/jira/browse/AMBARI-19268
> Project: Ambari
> Issue Type: Bug
> Components: ambari-upgrade
>Affects Versions: 2.2.2
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19268_5.patch
>
>
> After upgrade from 2.0.0 hadoop-env doesn't contain:
> {noformat}
> {% if is_datanode_max_locked_memory_set %}
> # Fix temporary bug, when ulimit from conf files is not picked up, without
> full relogin.
> # Makes sense to fix only when runing DN as root
> if [ "$command" == "datanode" ] && [ "$EUID" -eq 0 ] && [ -n
> "$HADOOP_SECURE_DN_USER" ]; then
> ulimit -l {{datanode_max_locked_memory}}
> fi
> {% endif %}
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (AMBARI-19278) Typo in the PostgreSQL database name for druid service
[ https://issues.apache.org/jira/browse/AMBARI-19278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Magyar reassigned AMBARI-19278: -- Assignee: Attila Magyar > Typo in the PostgreSQL database name for druid service > -- > > Key: AMBARI-19278 > URL: https://issues.apache.org/jira/browse/AMBARI-19278 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: slim bouguerra >Assignee: Attila Magyar > Attachments: AMBARI-19278.patch > > > Typo in the value of postgresql metadata storage. > it should be postgesql instead of postgres -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19280) Cover global controllers with unit tests
[ https://issues.apache.org/jira/browse/AMBARI-19280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-19280: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Cover global controllers with unit tests > > > Key: AMBARI-19280 > URL: https://issues.apache.org/jira/browse/AMBARI-19280 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-19280.patch > > > Cover following files: > * /ambari-web/app/controllers/global/background_operations_controller.js > * /ambari-web/app/controllers/global/cluster_controller.js > * /ambari-web/app/controllers/global/configuration_controller.js > * /ambari-web/app/controllers/global/errors_handler_controller.js > * /ambari-web/app/controllers/global/update_controller.js > * /ambari-web/app/controllers/global/user_settings_controller.js > * /ambari-web/app/controllers/global/wizard_watcher_controller.js -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19280) Cover global controllers with unit tests
[ https://issues.apache.org/jira/browse/AMBARI-19280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15770196#comment-15770196 ] Andrii Tkach commented on AMBARI-19280: --- committed to trunk > Cover global controllers with unit tests > > > Key: AMBARI-19280 > URL: https://issues.apache.org/jira/browse/AMBARI-19280 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-19280.patch > > > Cover following files: > * /ambari-web/app/controllers/global/background_operations_controller.js > * /ambari-web/app/controllers/global/cluster_controller.js > * /ambari-web/app/controllers/global/configuration_controller.js > * /ambari-web/app/controllers/global/errors_handler_controller.js > * /ambari-web/app/controllers/global/update_controller.js > * /ambari-web/app/controllers/global/user_settings_controller.js > * /ambari-web/app/controllers/global/wizard_watcher_controller.js -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19278) Typo in the PostgreSQL database name for druid service
[ https://issues.apache.org/jira/browse/AMBARI-19278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Magyar updated AMBARI-19278: --- Attachment: AMBARI-19278.patch Probably the previous patch was created inside an ambari-server directory instead of the project root. > Typo in the PostgreSQL database name for druid service > -- > > Key: AMBARI-19278 > URL: https://issues.apache.org/jira/browse/AMBARI-19278 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: slim bouguerra >Assignee: Attila Magyar > Attachments: AMBARI-19278.patch, AMBARI-19278.patch > > > Typo in the value of postgresql metadata storage. > it should be postgesql instead of postgres -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (AMBARI-19278) Typo in the PostgreSQL database name for druid service
[ https://issues.apache.org/jira/browse/AMBARI-19278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15770197#comment-15770197 ] Attila Magyar edited comment on AMBARI-19278 at 12/22/16 2:55 PM: -- Probably the previous patch was created inside an ambari-server directory instead of the project root. [~bslim] could you delete it? I uploaded a new one. was (Author: amagyar): Probably the previous patch was created inside an ambari-server directory instead of the project root. > Typo in the PostgreSQL database name for druid service > -- > > Key: AMBARI-19278 > URL: https://issues.apache.org/jira/browse/AMBARI-19278 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: slim bouguerra >Assignee: Attila Magyar > Attachments: AMBARI-19278.patch, AMBARI-19278.patch > > > Typo in the value of postgresql metadata storage. > it should be postgesql instead of postgres -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19278) Typo in the PostgreSQL database name for druid service
[ https://issues.apache.org/jira/browse/AMBARI-19278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra updated AMBARI-19278: Attachment: (was: AMBARI-19278.patch) > Typo in the PostgreSQL database name for druid service > -- > > Key: AMBARI-19278 > URL: https://issues.apache.org/jira/browse/AMBARI-19278 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: slim bouguerra >Assignee: Attila Magyar > Attachments: AMBARI-19278.patch > > > Typo in the value of postgresql metadata storage. > it should be postgesql instead of postgres -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19278) Typo in the PostgreSQL database name for druid service
[ https://issues.apache.org/jira/browse/AMBARI-19278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15770216#comment-15770216 ] slim bouguerra commented on AMBARI-19278: - [~amagyar] your patch is exactly the same to mine not sure what you mean by created inside an ambari-server ? > Typo in the PostgreSQL database name for druid service > -- > > Key: AMBARI-19278 > URL: https://issues.apache.org/jira/browse/AMBARI-19278 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: slim bouguerra >Assignee: Attila Magyar > Attachments: AMBARI-19278.patch > > > Typo in the value of postgresql metadata storage. > it should be postgesql instead of postgres -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19249) Adding custom config property say radio button fields etc needs hardcoding in various places
[ https://issues.apache.org/jira/browse/AMBARI-19249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15770225#comment-15770225 ] Antonenko Alexander commented on AMBARI-19249: -- [~sjampa] In order to fix JS error that you see in your console, you should remove your changes. p.s. also the app.js file that you are looking at is a concatenated file, please look at the source files here https://github.com/apache/ambari/tree/branch-2.5/ambari-web/app > Adding custom config property say radio button fields etc needs hardcoding in > various places > > > Key: AMBARI-19249 > URL: https://issues.apache.org/jira/browse/AMBARI-19249 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.2.2 >Reporter: sjampa > Fix For: 2.5.0 > > > Steps for creating a configuration property with radio button options. > Something similar to what we have it for “hive database” selection under hive > config tab. This needs hard-coding in multiple places like say i want to add > a field like below with radio options: > Example: > custom_database: > o Mysql > o Postgres > o Mssql > The below link will give info on customizing only the first Tab: > https://cwiki.apache.org/confluence/display/AMBARI/Enhanced+Configs > For Advanced Tab: > So far I found one file with references to the fields under Advanced Tab: > “/opt/apache-ambari-2.2.2-src/ambari-web/public/javascripts/app.js” > Its better to have some documentation steps as an initial draft for the users > to add these fields, also about the "test connection" button. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19282) HA HDFS propreties may be written in different case, which prevents operations
[
https://issues.apache.org/jira/browse/AMBARI-19282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-19282:
-
Status: Patch Available (was: Open)
> HA HDFS propreties may be written in different case, which prevents operations
> --
>
> Key: AMBARI-19282
> URL: https://issues.apache.org/jira/browse/AMBARI-19282
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-19282.patch
>
>
> In the command json file the hostname is in lower case, while in HA mode the
> hdfs-site property dfs.namenode.rpc-address.{dfs_ha_nameservices}.{nn_id} may
> have upper case parts, which prevents the /common-
> services/HDFS//package/scripts/params_linux.py file at line 300 from
> identifying the namenode_id, as it tries to find the hostname in the proprety,
> and their case doesn't match.
> Either it should be fixed that the dfs.namenode.rpc-
> address.{dfs_ha_nameservices}.{nn_id} should be always in lower case too or
> the params_linux.py should identify the namenode_id by trying to find the
> hostname in the property ignoring case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19282) HA HDFS propreties may be written in different case, which prevents operations
[
https://issues.apache.org/jira/browse/AMBARI-19282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-19282:
-
Attachment: AMBARI-19282.patch
> HA HDFS propreties may be written in different case, which prevents operations
> --
>
> Key: AMBARI-19282
> URL: https://issues.apache.org/jira/browse/AMBARI-19282
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-19282.patch
>
>
> In the command json file the hostname is in lower case, while in HA mode the
> hdfs-site property dfs.namenode.rpc-address.{dfs_ha_nameservices}.{nn_id} may
> have upper case parts, which prevents the /common-
> services/HDFS//package/scripts/params_linux.py file at line 300 from
> identifying the namenode_id, as it tries to find the hostname in the proprety,
> and their case doesn't match.
> Either it should be fixed that the dfs.namenode.rpc-
> address.{dfs_ha_nameservices}.{nn_id} should be always in lower case too or
> the params_linux.py should identify the namenode_id by trying to find the
> hostname in the property ignoring case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19282) HA HDFS propreties may be written in different case, which prevents operations
Andrew Onischuk created AMBARI-19282:
Summary: HA HDFS propreties may be written in different case,
which prevents operations
Key: AMBARI-19282
URL: https://issues.apache.org/jira/browse/AMBARI-19282
Project: Ambari
Issue Type: Bug
Reporter: Andrew Onischuk
Assignee: Andrew Onischuk
Fix For: 2.5.0
Attachments: AMBARI-19282.patch
In the command json file the hostname is in lower case, while in HA mode the
hdfs-site property dfs.namenode.rpc-address.{dfs_ha_nameservices}.{nn_id} may
have upper case parts, which prevents the /common-
services/HDFS//package/scripts/params_linux.py file at line 300 from
identifying the namenode_id, as it tries to find the hostname in the proprety,
and their case doesn't match.
Either it should be fixed that the dfs.namenode.rpc-
address.{dfs_ha_nameservices}.{nn_id} should be always in lower case too or
the params_linux.py should identify the namenode_id by trying to find the
hostname in the property ignoring case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (AMBARI-19171) Configuring YARN with custom queues leads to misleading errors in Stack Advisor
[ https://issues.apache.org/jira/browse/AMBARI-19171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko reassigned AMBARI-19171: Assignee: Dmytro Grinenko > Configuring YARN with custom queues leads to misleading errors in Stack > Advisor > --- > > Key: AMBARI-19171 > URL: https://issues.apache.org/jira/browse/AMBARI-19171 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Sharma >Assignee: Dmytro Grinenko >Priority: Critical > Labels: ui > Fix For: 2.5.0 > > Attachments: yarn1.png, yarn2.png > > > Configure custom (non-default) YARN queues as per this link > (http://hortonworks.com/hadoop-tutorial/configuring-yarn-capacity-scheduler-ambari/) > Result: Stack Advisor gives errors related to deletion of 'default' queue > (check screenshots - yarn1, yarn2) for various service configs like YARN, > Hive, Tez, MR, Spark -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19278) Typo in the PostgreSQL database name for druid service
[
https://issues.apache.org/jira/browse/AMBARI-19278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15770303#comment-15770303
]
Hadoop QA commented on AMBARI-19278:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12844406/AMBARI-19278.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9789//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9789//console
This message is automatically generated.
> Typo in the PostgreSQL database name for druid service
> --
>
> Key: AMBARI-19278
> URL: https://issues.apache.org/jira/browse/AMBARI-19278
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: slim bouguerra
>Assignee: Attila Magyar
> Attachments: AMBARI-19278.patch
>
>
> Typo in the value of postgresql metadata storage.
> it should be postgesql instead of postgres
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19280) Cover global controllers with unit tests
[ https://issues.apache.org/jira/browse/AMBARI-19280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15770313#comment-15770313 ] Hudson commented on AMBARI-19280: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6282 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6282/]) AMBARI-19280 Cover global controllers with unit tests. (atkach) (atkach: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=98a83c5f909b5fe5b8debe249496978bd3c6c7d2]) * (edit) ambari-web/test/controllers/global/errors_handler_controller_test.js * (edit) ambari-web/test/controllers/global/user_settings_controller_test.js * (edit) ambari-web/app/controllers/global/cluster_controller.js * (edit) ambari-web/test/controllers/global/cluster_controller_test.js * (edit) ambari-web/test/controllers/global/configuration_controller_test.js * (edit) ambari-web/test/controllers/global/update_controller_test.js * (edit) ambari-web/app/controllers/global/background_operations_controller.js * (edit) ambari-web/app/controllers/global/configuration_controller.js * (edit) ambari-web/app/controllers/global/update_controller.js * (edit) ambari-web/app/controllers/global/user_settings_controller.js * (edit) ambari-web/test/controllers/global/background_operations_test.js > Cover global controllers with unit tests > > > Key: AMBARI-19280 > URL: https://issues.apache.org/jira/browse/AMBARI-19280 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-19280.patch > > > Cover following files: > * /ambari-web/app/controllers/global/background_operations_controller.js > * /ambari-web/app/controllers/global/cluster_controller.js > * /ambari-web/app/controllers/global/configuration_controller.js > * /ambari-web/app/controllers/global/errors_handler_controller.js > * /ambari-web/app/controllers/global/update_controller.js > * /ambari-web/app/controllers/global/user_settings_controller.js > * /ambari-web/app/controllers/global/wizard_watcher_controller.js -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19268) ulimit override missing from upgrade catalogs
[
https://issues.apache.org/jira/browse/AMBARI-19268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15770326#comment-15770326
]
Dmytro Sen commented on AMBARI-19268:
-
Failed python unit tests are not related to this patch
> ulimit override missing from upgrade catalogs
> -
>
> Key: AMBARI-19268
> URL: https://issues.apache.org/jira/browse/AMBARI-19268
> Project: Ambari
> Issue Type: Bug
> Components: ambari-upgrade
>Affects Versions: 2.2.2
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19268_5.patch
>
>
> After upgrade from 2.0.0 hadoop-env doesn't contain:
> {noformat}
> {% if is_datanode_max_locked_memory_set %}
> # Fix temporary bug, when ulimit from conf files is not picked up, without
> full relogin.
> # Makes sense to fix only when runing DN as root
> if [ "$command" == "datanode" ] && [ "$EUID" -eq 0 ] && [ -n
> "$HADOOP_SECURE_DN_USER" ]; then
> ulimit -l {{datanode_max_locked_memory}}
> fi
> {% endif %}
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19278) Typo in the PostgreSQL database name for druid service
[ https://issues.apache.org/jira/browse/AMBARI-19278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra updated AMBARI-19278: Attachment: AMBARI-19278.patch > Typo in the PostgreSQL database name for druid service > -- > > Key: AMBARI-19278 > URL: https://issues.apache.org/jira/browse/AMBARI-19278 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: slim bouguerra >Assignee: Attila Magyar > Attachments: AMBARI-19278.patch, AMBARI-19278.patch > > > Typo in the value of postgresql metadata storage. > it should be postgesql instead of postgres -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19282) HA HDFS propreties may be written in different case, which prevents operations
[
https://issues.apache.org/jira/browse/AMBARI-19282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15770372#comment-15770372
]
Hadoop QA commented on AMBARI-19282:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12844408/AMBARI-19282.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9790//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9790//console
This message is automatically generated.
> HA HDFS propreties may be written in different case, which prevents operations
> --
>
> Key: AMBARI-19282
> URL: https://issues.apache.org/jira/browse/AMBARI-19282
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-19282.patch
>
>
> In the command json file the hostname is in lower case, while in HA mode the
> hdfs-site property dfs.namenode.rpc-address.{dfs_ha_nameservices}.{nn_id} may
> have upper case parts, which prevents the /common-
> services/HDFS//package/scripts/params_linux.py file at line 300 from
> identifying the namenode_id, as it tries to find the hostname in the proprety,
> and their case doesn't match.
> Either it should be fixed that the dfs.namenode.rpc-
> address.{dfs_ha_nameservices}.{nn_id} should be always in lower case too or
> the params_linux.py should identify the namenode_id by trying to find the
> hostname in the property ignoring case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19278) Typo in the PostgreSQL database name for druid service
[
https://issues.apache.org/jira/browse/AMBARI-19278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15770374#comment-15770374
]
Hadoop QA commented on AMBARI-19278:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12844412/AMBARI-19278.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/9791//console
This message is automatically generated.
> Typo in the PostgreSQL database name for druid service
> --
>
> Key: AMBARI-19278
> URL: https://issues.apache.org/jira/browse/AMBARI-19278
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: slim bouguerra
>Assignee: Attila Magyar
> Attachments: AMBARI-19278.patch, AMBARI-19278.patch
>
>
> Typo in the value of postgresql metadata storage.
> it should be postgesql instead of postgres
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19278) Typo in the PostgreSQL database name for druid service
[ https://issues.apache.org/jira/browse/AMBARI-19278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Magyar updated AMBARI-19278: --- Attachment: (was: AMBARI-19278.patch) > Typo in the PostgreSQL database name for druid service > -- > > Key: AMBARI-19278 > URL: https://issues.apache.org/jira/browse/AMBARI-19278 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: slim bouguerra >Assignee: Attila Magyar > Attachments: AMBARI-19278.patch > > > Typo in the value of postgresql metadata storage. > it should be postgesql instead of postgres -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19278) Typo in the PostgreSQL database name for druid service
[ https://issues.apache.org/jira/browse/AMBARI-19278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra updated AMBARI-19278: Attachment: AMBARI-19278.patch > Typo in the PostgreSQL database name for druid service > -- > > Key: AMBARI-19278 > URL: https://issues.apache.org/jira/browse/AMBARI-19278 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: slim bouguerra >Assignee: Attila Magyar > Attachments: AMBARI-19278.patch > > > Typo in the value of postgresql metadata storage. > it should be postgesql instead of postgres -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19278) Typo in the PostgreSQL database name for druid service
[ https://issues.apache.org/jira/browse/AMBARI-19278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra updated AMBARI-19278: Attachment: (was: AMBARI-19278.patch) > Typo in the PostgreSQL database name for druid service > -- > > Key: AMBARI-19278 > URL: https://issues.apache.org/jira/browse/AMBARI-19278 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: slim bouguerra >Assignee: Attila Magyar > Attachments: AMBARI-19278.patch > > > Typo in the value of postgresql metadata storage. > it should be postgesql instead of postgres -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19278) Typo in the PostgreSQL database name for druid service
[ https://issues.apache.org/jira/browse/AMBARI-19278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra updated AMBARI-19278: Attachment: (was: AMBARI-19278.patch) > Typo in the PostgreSQL database name for druid service > -- > > Key: AMBARI-19278 > URL: https://issues.apache.org/jira/browse/AMBARI-19278 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: slim bouguerra >Assignee: Attila Magyar > > Typo in the value of postgresql metadata storage. > it should be postgesql instead of postgres -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19278) Typo in the PostgreSQL database name for druid service
[ https://issues.apache.org/jira/browse/AMBARI-19278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra updated AMBARI-19278: Attachment: AMABARI-17981.patch > Typo in the PostgreSQL database name for druid service > -- > > Key: AMBARI-19278 > URL: https://issues.apache.org/jira/browse/AMBARI-19278 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: slim bouguerra >Assignee: Attila Magyar > Attachments: AMABARI-17981.patch > > > Typo in the value of postgresql metadata storage. > it should be postgesql instead of postgres -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19278) Typo in the PostgreSQL database name for druid service
[ https://issues.apache.org/jira/browse/AMBARI-19278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Magyar updated AMBARI-19278: --- Assignee: (was: Attila Magyar) > Typo in the PostgreSQL database name for druid service > -- > > Key: AMBARI-19278 > URL: https://issues.apache.org/jira/browse/AMBARI-19278 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: slim bouguerra > > Typo in the value of postgresql metadata storage. > it should be postgesql instead of postgres -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19283) Ambari agent doesn't find alert scripts in a stack extension
Diego Santesteban created AMBARI-19283: -- Summary: Ambari agent doesn't find alert scripts in a stack extension Key: AMBARI-19283 URL: https://issues.apache.org/jira/browse/AMBARI-19283 Project: Ambari Issue Type: Bug Components: alerts Affects Versions: 2.4.2 Reporter: Diego Santesteban Fix For: 2.5.0 When a service in a stack extension includes alerts, Ambari cannot find the scripts for the alerts. It's only looking in the cache/stacks and cache/host_scripts directories. Ambari needs to check the cache/extensions directory as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19278) Typo in the PostgreSQL database name for druid service
[ https://issues.apache.org/jira/browse/AMBARI-19278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra updated AMBARI-19278: Attachment: (was: AMABARI-17981.patch) > Typo in the PostgreSQL database name for druid service > -- > > Key: AMBARI-19278 > URL: https://issues.apache.org/jira/browse/AMBARI-19278 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: slim bouguerra > > Typo in the value of postgresql metadata storage. > it should be postgesql instead of postgres -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19278) Typo in the PostgreSQL database name for druid service
[ https://issues.apache.org/jira/browse/AMBARI-19278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra updated AMBARI-19278: Attachment: AMBARI-19278.patch > Typo in the PostgreSQL database name for druid service > -- > > Key: AMBARI-19278 > URL: https://issues.apache.org/jira/browse/AMBARI-19278 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: slim bouguerra > Attachments: AMBARI-19278.patch > > > Typo in the value of postgresql metadata storage. > it should be postgesql instead of postgres -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19284) Zeppelin Notebook start fails after reboot
[ https://issues.apache.org/jira/browse/AMBARI-19284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-19284: - Attachment: AMBARI-19284.patch > Zeppelin Notebook start fails after reboot > -- > > Key: AMBARI-19284 > URL: https://issues.apache.org/jira/browse/AMBARI-19284 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.5.0 > > Attachments: AMBARI-19284.patch > > > Traceback (most recent call last): > File > "/var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py", > line 361, in > Master().execute() > File > "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", > line 287, in execute > method(env) > File > "/var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py", > line 191, in start > + params.zeppelin_log_file, user=params.zeppelin_user) > File > "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line > 155, in __init__ > self.env.run() > File > "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", > line 160, in run > self.run_action(resource, action) > File > "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", > line 124, in run_action > provider_action() > File > "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py", > line 262, in action_run > tries=self.resource.tries, try_sleep=self.resource.try_sleep) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 72, in inner > result = function(command, **kwargs) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 102, in checked_call > tries=tries, try_sleep=try_sleep, > timeout_kill_strategy=timeout_kill_strategy) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 150, in _call_wrapper > result = _call(command, **kwargs_copy) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 303, in _call > raise ExecutionFailed(err_msg, code, out, err) > resource_management.core.exceptions.ExecutionFailed: Execution of > '/usr/hdp/current/zeppelin-server/bin/zeppelin-daemon.sh restart >> > /grid/0/log/zeppelin/zeppelin-setup.log' returned 1. Hortonworks > # > This is MOTD message, added for testing in qe infra > mkdir: cannot create directory `/var/run/zeppelin': Permission denied > /usr/hdp/current/zeppelin-server/bin/zeppelin-daemon.sh: line 192: > /var/run/zeppelin/zeppelin-zeppelin-nat-d7-rrws-ambari-autostart-1-5.pid: No > such file or directory > cat: > /var/run/zeppelin/zeppelin-zeppelin-nat-d7-rrws-ambari-autostart-1-5.pid: No > such file or directory > > Explanation: > 1\. /var/run/zeppelin created only during install stage > 2\. Reboot pc. So that /var/run is cleaned. > 3\. Zeppelin fails to start because /var/run/zeppelin is absent -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19284) Zeppelin Notebook start fails after reboot
Andrew Onischuk created AMBARI-19284: Summary: Zeppelin Notebook start fails after reboot Key: AMBARI-19284 URL: https://issues.apache.org/jira/browse/AMBARI-19284 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.5.0 Attachments: AMBARI-19284.patch Traceback (most recent call last): File "/var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py", line 361, in Master().execute() File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 287, in execute method(env) File "/var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py", line 191, in start + params.zeppelin_log_file, user=params.zeppelin_user) File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line 155, in __init__ self.env.run() File "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", line 160, in run self.run_action(resource, action) File "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", line 124, in run_action provider_action() File "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py", line 262, in action_run tries=self.resource.tries, try_sleep=self.resource.try_sleep) File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 72, in inner result = function(command, **kwargs) File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 102, in checked_call tries=tries, try_sleep=try_sleep, timeout_kill_strategy=timeout_kill_strategy) File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 150, in _call_wrapper result = _call(command, **kwargs_copy) File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 303, in _call raise ExecutionFailed(err_msg, code, out, err) resource_management.core.exceptions.ExecutionFailed: Execution of '/usr/hdp/current/zeppelin-server/bin/zeppelin-daemon.sh restart >> /grid/0/log/zeppelin/zeppelin-setup.log' returned 1. Hortonworks # This is MOTD message, added for testing in qe infra mkdir: cannot create directory `/var/run/zeppelin': Permission denied /usr/hdp/current/zeppelin-server/bin/zeppelin-daemon.sh: line 192: /var/run/zeppelin/zeppelin-zeppelin-nat-d7-rrws-ambari-autostart-1-5.pid: No such file or directory cat: /var/run/zeppelin/zeppelin-zeppelin-nat-d7-rrws-ambari-autostart-1-5.pid: No such file or directory Explanation: 1\. /var/run/zeppelin created only during install stage 2\. Reboot pc. So that /var/run is cleaned. 3\. Zeppelin fails to start because /var/run/zeppelin is absent -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19284) Zeppelin Notebook start fails after reboot
[ https://issues.apache.org/jira/browse/AMBARI-19284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-19284: - Status: Patch Available (was: Open) > Zeppelin Notebook start fails after reboot > -- > > Key: AMBARI-19284 > URL: https://issues.apache.org/jira/browse/AMBARI-19284 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.5.0 > > Attachments: AMBARI-19284.patch > > > Traceback (most recent call last): > File > "/var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py", > line 361, in > Master().execute() > File > "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", > line 287, in execute > method(env) > File > "/var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py", > line 191, in start > + params.zeppelin_log_file, user=params.zeppelin_user) > File > "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line > 155, in __init__ > self.env.run() > File > "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", > line 160, in run > self.run_action(resource, action) > File > "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", > line 124, in run_action > provider_action() > File > "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py", > line 262, in action_run > tries=self.resource.tries, try_sleep=self.resource.try_sleep) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 72, in inner > result = function(command, **kwargs) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 102, in checked_call > tries=tries, try_sleep=try_sleep, > timeout_kill_strategy=timeout_kill_strategy) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 150, in _call_wrapper > result = _call(command, **kwargs_copy) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 303, in _call > raise ExecutionFailed(err_msg, code, out, err) > resource_management.core.exceptions.ExecutionFailed: Execution of > '/usr/hdp/current/zeppelin-server/bin/zeppelin-daemon.sh restart >> > /grid/0/log/zeppelin/zeppelin-setup.log' returned 1. Hortonworks > # > This is MOTD message, added for testing in qe infra > mkdir: cannot create directory `/var/run/zeppelin': Permission denied > /usr/hdp/current/zeppelin-server/bin/zeppelin-daemon.sh: line 192: > /var/run/zeppelin/zeppelin-zeppelin-nat-d7-rrws-ambari-autostart-1-5.pid: No > such file or directory > cat: > /var/run/zeppelin/zeppelin-zeppelin-nat-d7-rrws-ambari-autostart-1-5.pid: No > such file or directory > > Explanation: > 1\. /var/run/zeppelin created only during install stage > 2\. Reboot pc. So that /var/run is cleaned. > 3\. Zeppelin fails to start because /var/run/zeppelin is absent -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19282) HA HDFS propreties may be written in different case, which prevents operations
[
https://issues.apache.org/jira/browse/AMBARI-19282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15770438#comment-15770438
]
Hadoop QA commented on AMBARI-19282:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12844408/AMBARI-19282.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9792//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9792//console
This message is automatically generated.
> HA HDFS propreties may be written in different case, which prevents operations
> --
>
> Key: AMBARI-19282
> URL: https://issues.apache.org/jira/browse/AMBARI-19282
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-19282.patch
>
>
> In the command json file the hostname is in lower case, while in HA mode the
> hdfs-site property dfs.namenode.rpc-address.{dfs_ha_nameservices}.{nn_id} may
> have upper case parts, which prevents the /common-
> services/HDFS//package/scripts/params_linux.py file at line 300 from
> identifying the namenode_id, as it tries to find the hostname in the proprety,
> and their case doesn't match.
> Either it should be fixed that the dfs.namenode.rpc-
> address.{dfs_ha_nameservices}.{nn_id} should be always in lower case too or
> the params_linux.py should identify the namenode_id by trying to find the
> hostname in the property ignoring case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19281) Display properties for all affected services before adding or deleting ZooKeeper Server
[
https://issues.apache.org/jira/browse/AMBARI-19281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15770441#comment-15770441
]
Hadoop QA commented on AMBARI-19281:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12844391/AMBARI-19281_trunk.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/9793//console
This message is automatically generated.
> Display properties for all affected services before adding or deleting
> ZooKeeper Server
> ---
>
> Key: AMBARI-19281
> URL: https://issues.apache.org/jira/browse/AMBARI-19281
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19281_trunk.patch
>
>
> Only the changes for Storm configs are displayed inside the confirmation
> popup before adding and deleting ZooKeeper server.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19284) Zeppelin Notebook start fails after reboot
[ https://issues.apache.org/jira/browse/AMBARI-19284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-19284: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.5 > Zeppelin Notebook start fails after reboot > -- > > Key: AMBARI-19284 > URL: https://issues.apache.org/jira/browse/AMBARI-19284 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.5.0 > > Attachments: AMBARI-19284.patch > > > Traceback (most recent call last): > File > "/var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py", > line 361, in > Master().execute() > File > "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", > line 287, in execute > method(env) > File > "/var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py", > line 191, in start > + params.zeppelin_log_file, user=params.zeppelin_user) > File > "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line > 155, in __init__ > self.env.run() > File > "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", > line 160, in run > self.run_action(resource, action) > File > "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", > line 124, in run_action > provider_action() > File > "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py", > line 262, in action_run > tries=self.resource.tries, try_sleep=self.resource.try_sleep) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 72, in inner > result = function(command, **kwargs) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 102, in checked_call > tries=tries, try_sleep=try_sleep, > timeout_kill_strategy=timeout_kill_strategy) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 150, in _call_wrapper > result = _call(command, **kwargs_copy) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 303, in _call > raise ExecutionFailed(err_msg, code, out, err) > resource_management.core.exceptions.ExecutionFailed: Execution of > '/usr/hdp/current/zeppelin-server/bin/zeppelin-daemon.sh restart >> > /grid/0/log/zeppelin/zeppelin-setup.log' returned 1. Hortonworks > # > This is MOTD message, added for testing in qe infra > mkdir: cannot create directory `/var/run/zeppelin': Permission denied > /usr/hdp/current/zeppelin-server/bin/zeppelin-daemon.sh: line 192: > /var/run/zeppelin/zeppelin-zeppelin-nat-d7-rrws-ambari-autostart-1-5.pid: No > such file or directory > cat: > /var/run/zeppelin/zeppelin-zeppelin-nat-d7-rrws-ambari-autostart-1-5.pid: No > such file or directory > > Explanation: > 1\. /var/run/zeppelin created only during install stage > 2\. Reboot pc. So that /var/run is cleaned. > 3\. Zeppelin fails to start because /var/run/zeppelin is absent -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19282) HA HDFS propreties may be written in different case, which prevents operations
[
https://issues.apache.org/jira/browse/AMBARI-19282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-19282:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk and branch-2.5
> HA HDFS propreties may be written in different case, which prevents operations
> --
>
> Key: AMBARI-19282
> URL: https://issues.apache.org/jira/browse/AMBARI-19282
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-19282.patch
>
>
> In the command json file the hostname is in lower case, while in HA mode the
> hdfs-site property dfs.namenode.rpc-address.{dfs_ha_nameservices}.{nn_id} may
> have upper case parts, which prevents the /common-
> services/HDFS//package/scripts/params_linux.py file at line 300 from
> identifying the namenode_id, as it tries to find the hostname in the proprety,
> and their case doesn't match.
> Either it should be fixed that the dfs.namenode.rpc-
> address.{dfs_ha_nameservices}.{nn_id} should be always in lower case too or
> the params_linux.py should identify the namenode_id by trying to find the
> hostname in the property ignoring case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19264) Zeppelin Notebook Component is not able start after reboot
[
https://issues.apache.org/jira/browse/AMBARI-19264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15770519#comment-15770519
]
Hadoop QA commented on AMBARI-19264:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12844396/AMBARI-19264-branch-2.5-v1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9794//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9794//console
This message is automatically generated.
> Zeppelin Notebook Component is not able start after reboot
> ---
>
> Key: AMBARI-19264
> URL: https://issues.apache.org/jira/browse/AMBARI-19264
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Pradarttana
>Assignee: Renjith Kamath
> Fix For: 2.5.0
>
> Attachments: AMBARI-19264-branch-2.5-v1.patch
>
>
> Steps to reproduce:-
> 1. reboot one of the host in ambari-cluster where zeppelin notebook is
> installed
> 2. Zeppelin Notebook start will failed saying "mkdir: cannot create directory
> `/var/run/zeppelin': Permission denied"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19279) AHW Configurations page looks not like any other wizard page
[
https://issues.apache.org/jira/browse/AMBARI-19279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15770523#comment-15770523
]
Hadoop QA commented on AMBARI-19279:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12844371/AMBARI-19279.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/9795//console
This message is automatically generated.
> AHW Configurations page looks not like any other wizard page
>
>
> Key: AMBARI-19279
> URL: https://issues.apache.org/jira/browse/AMBARI-19279
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-19279.patch
>
>
> Configurations page on AHW wasn't updated when Ambari Theme was created.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19284) Zeppelin Notebook start fails after reboot
[
https://issues.apache.org/jira/browse/AMBARI-19284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15770527#comment-15770527
]
Hadoop QA commented on AMBARI-19284:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12844421/AMBARI-19284.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/9796//console
This message is automatically generated.
> Zeppelin Notebook start fails after reboot
> --
>
> Key: AMBARI-19284
> URL: https://issues.apache.org/jira/browse/AMBARI-19284
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-19284.patch
>
>
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py",
> line 361, in
> Master().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 287, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py",
> line 191, in start
> + params.zeppelin_log_file, user=params.zeppelin_user)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line
> 155, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 262, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 72, in inner
> result = function(command, **kwargs)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 303, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of
> '/usr/hdp/current/zeppelin-server/bin/zeppelin-daemon.sh restart >>
> /grid/0/log/zeppelin/zeppelin-setup.log' returned 1. Hortonworks
> #
> This is MOTD message, added for testing in qe infra
> mkdir: cannot create directory `/var/run/zeppelin': Permission denied
> /usr/hdp/current/zeppelin-server/bin/zeppelin-daemon.sh: line 192:
> /var/run/zeppelin/zeppelin-zeppelin-nat-d7-rrws-ambari-autostart-1-5.pid: No
> such file or directory
> cat:
> /var/run/zeppelin/zeppelin-zeppelin-nat-d7-rrws-ambari-autostart-1-5.pid: No
> such file or directory
>
> Explanation:
> 1\. /var/run/zeppelin created only during install stage
> 2\. Reboot pc. So that /var/run is cleaned.
> 3\. Zeppelin fails to start because /var/run/zeppelin is absent
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19285) HOU pre-checks indicate HA as a requirement
Jonathan Hurley created AMBARI-19285:
Summary: HOU pre-checks indicate HA as a requirement
Key: AMBARI-19285
URL: https://issues.apache.org/jira/browse/AMBARI-19285
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.5.0
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Priority: Critical
Fix For: 2.5.0
Host Ordered Upgrades do not require the cluster services to be installed in HA
mode. However, when executing:
{code}
GET
api/v1/clusters/c1/rolling_upgrades_check?fields=*&UpgradeChecks/repository_version=2.5.3.0-37&UpgradeChecks/upgrade_type=HOST_ORDERED"
{code}
HA-only upgrade checks (like Secondary NameNode Removal and NameNode HA) are
running and failing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19187) Disable security hook
[ https://issues.apache.org/jira/browse/AMBARI-19187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Magyar updated AMBARI-19187: --- Attachment: AMBARI-19187_trunk.patch AMBARI-19187_branch-2.5.patch > Disable security hook > - > > Key: AMBARI-19187 > URL: https://issues.apache.org/jira/browse/AMBARI-19187 > Project: Ambari > Issue Type: New Feature > Components: ambari-agent, ambari-server >Affects Versions: 2.5.0 >Reporter: Attila Magyar >Assignee: Attila Magyar > Fix For: 2.5.0 > > Attachments: AMBARI-19187_branch-2.5.patch, AMBARI-19187_trunk.patch > > > Hadoop components need to establish a secure connection with ZooKeeper when > Kerberos is enabled. This involves the setup of the correct authentication > (JAAS config file) and authorization (per-component Kerberos-backed ACLs on > the znodes) between the service and ZooKeeper. Most services are able to set > these ACLs based on their config when the user enable kerberos. > When we disable kerberos again, the sasl ACL should be removed otherwise the > services won't be able to access their znodes. > This issue is about introducing a new command (DISABLE_SECURITY) that will be > sent by the ambari server to the services upon the dekerberiztion process. > When a service receives this command it will be able to do the zookeeper > secure to unsecure migration process (e.g. removing sasl ACLs). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19286) Handle permissions for setting service auto start in FE
Antonenko Alexander created AMBARI-19286: Summary: Handle permissions for setting service auto start in FE Key: AMBARI-19286 URL: https://issues.apache.org/jira/browse/AMBARI-19286 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Antonenko Alexander Assignee: Antonenko Alexander Priority: Critical Fix For: 2.5.0 The UI needs to be updated to handle permissions to manage cluster- and service-level auto start settings. If authorization failure occurs, the UI takes the user to the login screen and then to the dashboard. The following roles should be able to toggle auto-start at the cluster level (permission: CLUSTER.MANAGE_AUTO_START): * Ambari Administrator * Cluster Administrator * Cluster Operator The following roles should be able to toggle auto-start at the service level (permission: SERVICE.MANAGE_AUTO_START): * Ambari Administrator * Cluster Administrator * Cluster Operator * Service Administrator -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19286) Handle permissions for setting service auto start in FE
[ https://issues.apache.org/jira/browse/AMBARI-19286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-19286: - Attachment: AMBARI-19286.patch > Handle permissions for setting service auto start in FE > --- > > Key: AMBARI-19286 > URL: https://issues.apache.org/jira/browse/AMBARI-19286 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19286.patch > > > The UI needs to be updated to handle permissions to manage cluster- and > service-level auto start settings. > If authorization failure occurs, the UI takes the user to the login screen > and then to the dashboard. > The following roles should be able to toggle auto-start at the cluster level > (permission: CLUSTER.MANAGE_AUTO_START): > * Ambari Administrator > * Cluster Administrator > * Cluster Operator > The following roles should be able to toggle auto-start at the service level > (permission: SERVICE.MANAGE_AUTO_START): > * Ambari Administrator > * Cluster Administrator > * Cluster Operator > * Service Administrator -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19286) Handle permissions for setting service auto start in FE
[ https://issues.apache.org/jira/browse/AMBARI-19286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-19286: - Status: Patch Available (was: Open) > Handle permissions for setting service auto start in FE > --- > > Key: AMBARI-19286 > URL: https://issues.apache.org/jira/browse/AMBARI-19286 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19286.patch > > > The UI needs to be updated to handle permissions to manage cluster- and > service-level auto start settings. > If authorization failure occurs, the UI takes the user to the login screen > and then to the dashboard. > The following roles should be able to toggle auto-start at the cluster level > (permission: CLUSTER.MANAGE_AUTO_START): > * Ambari Administrator > * Cluster Administrator > * Cluster Operator > The following roles should be able to toggle auto-start at the service level > (permission: SERVICE.MANAGE_AUTO_START): > * Ambari Administrator > * Cluster Administrator > * Cluster Operator > * Service Administrator -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19282) HA HDFS propreties may be written in different case, which prevents operations
[
https://issues.apache.org/jira/browse/AMBARI-19282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15770599#comment-15770599
]
Hudson commented on AMBARI-19282:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #571 (See
[https://builds.apache.org/job/Ambari-branch-2.5/571/])
AMBARI-19282. HA HDFS propreties may be written in different case, which
(aonishuk:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=0dd6356a6efab73d1c4381346165aab258a4b4d2])
* (edit)
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/params_windows.py
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-START/scripts/params.py
* (edit)
ambari-server/src/main/resources/common-services/KNOX/0.5.0.2.2/package/scripts/params_linux.py
* (edit)
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/params_linux.py
> HA HDFS propreties may be written in different case, which prevents operations
> --
>
> Key: AMBARI-19282
> URL: https://issues.apache.org/jira/browse/AMBARI-19282
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-19282.patch
>
>
> In the command json file the hostname is in lower case, while in HA mode the
> hdfs-site property dfs.namenode.rpc-address.{dfs_ha_nameservices}.{nn_id} may
> have upper case parts, which prevents the /common-
> services/HDFS//package/scripts/params_linux.py file at line 300 from
> identifying the namenode_id, as it tries to find the hostname in the proprety,
> and their case doesn't match.
> Either it should be fixed that the dfs.namenode.rpc-
> address.{dfs_ha_nameservices}.{nn_id} should be always in lower case too or
> the params_linux.py should identify the namenode_id by trying to find the
> hostname in the property ignoring case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19284) Zeppelin Notebook start fails after reboot
[ https://issues.apache.org/jira/browse/AMBARI-19284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15770598#comment-15770598 ] Hudson commented on AMBARI-19284: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #571 (See [https://builds.apache.org/job/Ambari-branch-2.5/571/]) AMBARI-19284. Zeppelin Notebook start fails after reboot (aonishuk) (aonishuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=c6fae7b7f5d5c2d0bd9c38d2ceb5ff70d05609eb]) * (edit) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py > Zeppelin Notebook start fails after reboot > -- > > Key: AMBARI-19284 > URL: https://issues.apache.org/jira/browse/AMBARI-19284 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.5.0 > > Attachments: AMBARI-19284.patch > > > Traceback (most recent call last): > File > "/var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py", > line 361, in > Master().execute() > File > "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", > line 287, in execute > method(env) > File > "/var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py", > line 191, in start > + params.zeppelin_log_file, user=params.zeppelin_user) > File > "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line > 155, in __init__ > self.env.run() > File > "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", > line 160, in run > self.run_action(resource, action) > File > "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", > line 124, in run_action > provider_action() > File > "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py", > line 262, in action_run > tries=self.resource.tries, try_sleep=self.resource.try_sleep) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 72, in inner > result = function(command, **kwargs) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 102, in checked_call > tries=tries, try_sleep=try_sleep, > timeout_kill_strategy=timeout_kill_strategy) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 150, in _call_wrapper > result = _call(command, **kwargs_copy) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 303, in _call > raise ExecutionFailed(err_msg, code, out, err) > resource_management.core.exceptions.ExecutionFailed: Execution of > '/usr/hdp/current/zeppelin-server/bin/zeppelin-daemon.sh restart >> > /grid/0/log/zeppelin/zeppelin-setup.log' returned 1. Hortonworks > # > This is MOTD message, added for testing in qe infra > mkdir: cannot create directory `/var/run/zeppelin': Permission denied > /usr/hdp/current/zeppelin-server/bin/zeppelin-daemon.sh: line 192: > /var/run/zeppelin/zeppelin-zeppelin-nat-d7-rrws-ambari-autostart-1-5.pid: No > such file or directory > cat: > /var/run/zeppelin/zeppelin-zeppelin-nat-d7-rrws-ambari-autostart-1-5.pid: No > such file or directory > > Explanation: > 1\. /var/run/zeppelin created only during install stage > 2\. Reboot pc. So that /var/run is cleaned. > 3\. Zeppelin fails to start because /var/run/zeppelin is absent -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19284) Zeppelin Notebook start fails after reboot
[ https://issues.apache.org/jira/browse/AMBARI-19284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15770615#comment-15770615 ] Hudson commented on AMBARI-19284: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6283 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6283/]) AMBARI-19284. Zeppelin Notebook start fails after reboot (aonishuk) (aonishuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a100c0b3ee1f480f4721586084de8f8d0639b6c0]) * (edit) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py > Zeppelin Notebook start fails after reboot > -- > > Key: AMBARI-19284 > URL: https://issues.apache.org/jira/browse/AMBARI-19284 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.5.0 > > Attachments: AMBARI-19284.patch > > > Traceback (most recent call last): > File > "/var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py", > line 361, in > Master().execute() > File > "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", > line 287, in execute > method(env) > File > "/var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py", > line 191, in start > + params.zeppelin_log_file, user=params.zeppelin_user) > File > "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line > 155, in __init__ > self.env.run() > File > "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", > line 160, in run > self.run_action(resource, action) > File > "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", > line 124, in run_action > provider_action() > File > "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py", > line 262, in action_run > tries=self.resource.tries, try_sleep=self.resource.try_sleep) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 72, in inner > result = function(command, **kwargs) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 102, in checked_call > tries=tries, try_sleep=try_sleep, > timeout_kill_strategy=timeout_kill_strategy) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 150, in _call_wrapper > result = _call(command, **kwargs_copy) > File > "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line > 303, in _call > raise ExecutionFailed(err_msg, code, out, err) > resource_management.core.exceptions.ExecutionFailed: Execution of > '/usr/hdp/current/zeppelin-server/bin/zeppelin-daemon.sh restart >> > /grid/0/log/zeppelin/zeppelin-setup.log' returned 1. Hortonworks > # > This is MOTD message, added for testing in qe infra > mkdir: cannot create directory `/var/run/zeppelin': Permission denied > /usr/hdp/current/zeppelin-server/bin/zeppelin-daemon.sh: line 192: > /var/run/zeppelin/zeppelin-zeppelin-nat-d7-rrws-ambari-autostart-1-5.pid: No > such file or directory > cat: > /var/run/zeppelin/zeppelin-zeppelin-nat-d7-rrws-ambari-autostart-1-5.pid: No > such file or directory > > Explanation: > 1\. /var/run/zeppelin created only during install stage > 2\. Reboot pc. So that /var/run is cleaned. > 3\. Zeppelin fails to start because /var/run/zeppelin is absent -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19282) HA HDFS propreties may be written in different case, which prevents operations
[
https://issues.apache.org/jira/browse/AMBARI-19282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15770616#comment-15770616
]
Hudson commented on AMBARI-19282:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6283 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6283/])
AMBARI-19282. HA HDFS propreties may be written in different case, which
(aonishuk:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=bc1b7ab8c0f290879ce878a9c8cd028ecb51d45f])
* (edit)
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/params_linux.py
* (edit)
ambari-server/src/main/resources/common-services/KNOX/0.5.0.2.2/package/scripts/params_linux.py
* (edit)
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/params_windows.py
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-START/scripts/params.py
> HA HDFS propreties may be written in different case, which prevents operations
> --
>
> Key: AMBARI-19282
> URL: https://issues.apache.org/jira/browse/AMBARI-19282
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-19282.patch
>
>
> In the command json file the hostname is in lower case, while in HA mode the
> hdfs-site property dfs.namenode.rpc-address.{dfs_ha_nameservices}.{nn_id} may
> have upper case parts, which prevents the /common-
> services/HDFS//package/scripts/params_linux.py file at line 300 from
> identifying the namenode_id, as it tries to find the hostname in the proprety,
> and their case doesn't match.
> Either it should be fixed that the dfs.namenode.rpc-
> address.{dfs_ha_nameservices}.{nn_id} should be always in lower case too or
> the params_linux.py should identify the namenode_id by trying to find the
> hostname in the property ignoring case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19286) Handle permissions for setting service auto start in FE
[
https://issues.apache.org/jira/browse/AMBARI-19286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15770652#comment-15770652
]
Hadoop QA commented on AMBARI-19286:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12844432/AMBARI-19286.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9797//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9797//console
This message is automatically generated.
> Handle permissions for setting service auto start in FE
> ---
>
> Key: AMBARI-19286
> URL: https://issues.apache.org/jira/browse/AMBARI-19286
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19286.patch
>
>
> The UI needs to be updated to handle permissions to manage cluster- and
> service-level auto start settings.
> If authorization failure occurs, the UI takes the user to the login screen
> and then to the dashboard.
> The following roles should be able to toggle auto-start at the cluster level
> (permission: CLUSTER.MANAGE_AUTO_START):
> * Ambari Administrator
> * Cluster Administrator
> * Cluster Operator
> The following roles should be able to toggle auto-start at the service level
> (permission: SERVICE.MANAGE_AUTO_START):
> * Ambari Administrator
> * Cluster Administrator
> * Cluster Operator
> * Service Administrator
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19278) Typo in the PostgreSQL database name for druid service
[ https://issues.apache.org/jira/browse/AMBARI-19278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-19278: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Typo in the PostgreSQL database name for druid service > -- > > Key: AMBARI-19278 > URL: https://issues.apache.org/jira/browse/AMBARI-19278 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: slim bouguerra >Assignee: Attila Magyar > Attachments: AMBARI-19278.patch > > > Typo in the value of postgresql metadata storage. > it should be postgesql instead of postgres -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19278) Typo in the PostgreSQL database name for druid service
[ https://issues.apache.org/jira/browse/AMBARI-19278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-19278: -- Assignee: Attila Magyar > Typo in the PostgreSQL database name for druid service > -- > > Key: AMBARI-19278 > URL: https://issues.apache.org/jira/browse/AMBARI-19278 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: slim bouguerra >Assignee: Attila Magyar > Attachments: AMBARI-19278.patch > > > Typo in the value of postgresql metadata storage. > it should be postgesql instead of postgres -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19273) Refine AmbariServer Metrics service and enable JVM metrics source by default.
[ https://issues.apache.org/jira/browse/AMBARI-19273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-19273: --- Attachment: AMBARI-19273-2.patch > Refine AmbariServer Metrics service and enable JVM metrics source by default. > -- > > Key: AMBARI-19273 > URL: https://issues.apache.org/jira/browse/AMBARI-19273 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.5.0 > > Attachments: AMBARI-19273-2.patch > > > Enable AmbariServer metrics by default. Currently, the metrics.properties > file is not part of the rpm and hence the Metrics system does not do start > up. > Also, have a global flag in ambari.properties for disabling AmbariServer > metrics altogether. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19141) Refinements for AMS whitelisting.
[ https://issues.apache.org/jira/browse/AMBARI-19141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-19141: --- Attachment: AMBARI-19141-4.patch > Refinements for AMS whitelisting. > - > > Key: AMBARI-19141 > URL: https://issues.apache.org/jira/browse/AMBARI-19141 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.5.0 > > Attachments: AMBARI-19141-4.patch > > > Ability to specify metric expressions for whitelisting. > Ability to whitelist/blacklist metrics from entire sources (APP_IDs) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19273) Refine AmbariServer Metrics service and enable JVM metrics source by default.
[ https://issues.apache.org/jira/browse/AMBARI-19273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-19273: --- Status: Open (was: Patch Available) > Refine AmbariServer Metrics service and enable JVM metrics source by default. > -- > > Key: AMBARI-19273 > URL: https://issues.apache.org/jira/browse/AMBARI-19273 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.5.0 > > Attachments: AMBARI-19273-2.patch > > > Enable AmbariServer metrics by default. Currently, the metrics.properties > file is not part of the rpm and hence the Metrics system does not do start > up. > Also, have a global flag in ambari.properties for disabling AmbariServer > metrics altogether. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19141) Refinements for AMS whitelisting.
[ https://issues.apache.org/jira/browse/AMBARI-19141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-19141: --- Status: Patch Available (was: Open) > Refinements for AMS whitelisting. > - > > Key: AMBARI-19141 > URL: https://issues.apache.org/jira/browse/AMBARI-19141 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.5.0 > > Attachments: AMBARI-19141-4.patch > > > Ability to specify metric expressions for whitelisting. > Ability to whitelist/blacklist metrics from entire sources (APP_IDs) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19278) Typo in the PostgreSQL database name for druid service
[ https://issues.apache.org/jira/browse/AMBARI-19278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15770685#comment-15770685 ] Hudson commented on AMBARI-19278: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #572 (See [https://builds.apache.org/job/Ambari-branch-2.5/572/]) AMBARI-19278. Typo in the PostgreSQL database name for druid service. (stoader: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=532673b04e030bd09401a7097d1e6a9ba2165fd2]) * (edit) ambari-server/src/test/python/stacks/2.6/common/test_stack_advisor.py * (edit) ambari-server/src/main/resources/common-services/DRUID/0.9.2/configuration/druid-common.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/stack_advisor.py > Typo in the PostgreSQL database name for druid service > -- > > Key: AMBARI-19278 > URL: https://issues.apache.org/jira/browse/AMBARI-19278 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: slim bouguerra >Assignee: Attila Magyar > Attachments: AMBARI-19278.patch > > > Typo in the value of postgresql metadata storage. > it should be postgesql instead of postgres -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19283) Ambari agent doesn't find alert scripts in a stack extension
[ https://issues.apache.org/jira/browse/AMBARI-19283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15770687#comment-15770687 ] ASF GitHub Bot commented on AMBARI-19283: - GitHub user dsantesteban opened a pull request: https://github.com/apache/ambari/pull/45 Resolution for AMBARI-19283 These changes will allow Ambari stack extensions to use alert scripts. You can merge this pull request into a Git repository by running: $ git pull https://github.com/dsantesteban/ambari trunk Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ambari/pull/45.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #45 commit 35d210de808e5884bd5bf12b0de0aa1a654cd4a3 Author: Diego Santesteban Date: 2016-12-22T18:01:30Z Changes to resolve AMBARI-19283 commit a1d093b03d0ef5de9ded9902cd89a0254917acfc Author: Diego Santesteban Date: 2016-12-22T18:04:59Z One more change (keeping function params within column 80) > Ambari agent doesn't find alert scripts in a stack extension > > > Key: AMBARI-19283 > URL: https://issues.apache.org/jira/browse/AMBARI-19283 > Project: Ambari > Issue Type: Bug > Components: alerts >Affects Versions: 2.4.2 >Reporter: Diego Santesteban > Fix For: 2.5.0 > > Original Estimate: 4h > Remaining Estimate: 4h > > When a service in a stack extension includes alerts, Ambari cannot find the > scripts for the alerts. It's only looking in the cache/stacks and > cache/host_scripts directories. Ambari needs to check the cache/extensions > directory as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19273) Refine AmbariServer Metrics service and enable JVM metrics source by default.
[ https://issues.apache.org/jira/browse/AMBARI-19273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-19273: --- Status: Patch Available (was: Open) > Refine AmbariServer Metrics service and enable JVM metrics source by default. > -- > > Key: AMBARI-19273 > URL: https://issues.apache.org/jira/browse/AMBARI-19273 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.5.0 > > Attachments: AMBARI-19273-2.patch > > > Enable AmbariServer metrics by default. Currently, the metrics.properties > file is not part of the rpm and hence the Metrics system does not do start > up. > Also, have a global flag in ambari.properties for disabling AmbariServer > metrics altogether. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19278) Typo in the PostgreSQL database name for druid service
[ https://issues.apache.org/jira/browse/AMBARI-19278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15770709#comment-15770709 ] Hudson commented on AMBARI-19278: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6284 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6284/]) AMBARI-19278. Typo in the PostgreSQL database name for druid service. (stoader: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=c695e50a71eb6afa2f4fbc4ed2ee65da8f276aed]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/services/stack_advisor.py * (edit) ambari-server/src/test/python/stacks/2.6/common/test_stack_advisor.py * (edit) ambari-server/src/main/resources/common-services/DRUID/0.9.2/configuration/druid-common.xml > Typo in the PostgreSQL database name for druid service > -- > > Key: AMBARI-19278 > URL: https://issues.apache.org/jira/browse/AMBARI-19278 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: slim bouguerra >Assignee: Attila Magyar > Attachments: AMBARI-19278.patch > > > Typo in the value of postgresql metadata storage. > it should be postgesql instead of postgres -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19286) Handle permissions for setting service auto start in FE
[
https://issues.apache.org/jira/browse/AMBARI-19286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15770730#comment-15770730
]
Hadoop QA commented on AMBARI-19286:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12844432/AMBARI-19286.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9798//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9798//console
This message is automatically generated.
> Handle permissions for setting service auto start in FE
> ---
>
> Key: AMBARI-19286
> URL: https://issues.apache.org/jira/browse/AMBARI-19286
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19286.patch
>
>
> The UI needs to be updated to handle permissions to manage cluster- and
> service-level auto start settings.
> If authorization failure occurs, the UI takes the user to the login screen
> and then to the dashboard.
> The following roles should be able to toggle auto-start at the cluster level
> (permission: CLUSTER.MANAGE_AUTO_START):
> * Ambari Administrator
> * Cluster Administrator
> * Cluster Operator
> The following roles should be able to toggle auto-start at the service level
> (permission: SERVICE.MANAGE_AUTO_START):
> * Ambari Administrator
> * Cluster Administrator
> * Cluster Operator
> * Service Administrator
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19283) Ambari agent doesn't find alert scripts in a stack extension
[ https://issues.apache.org/jira/browse/AMBARI-19283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15770813#comment-15770813 ] ASF GitHub Bot commented on AMBARI-19283: - Github user dsantesteban closed the pull request at: https://github.com/apache/ambari/pull/45 > Ambari agent doesn't find alert scripts in a stack extension > > > Key: AMBARI-19283 > URL: https://issues.apache.org/jira/browse/AMBARI-19283 > Project: Ambari > Issue Type: Bug > Components: alerts >Affects Versions: 2.4.2 >Reporter: Diego Santesteban > Fix For: 2.5.0 > > Original Estimate: 4h > Remaining Estimate: 4h > > When a service in a stack extension includes alerts, Ambari cannot find the > scripts for the alerts. It's only looking in the cache/stacks and > cache/host_scripts directories. Ambari needs to check the cache/extensions > directory as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19285) HOU pre-checks indicate HA as a requirement
[
https://issues.apache.org/jira/browse/AMBARI-19285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-19285:
-
Status: Patch Available (was: Open)
> HOU pre-checks indicate HA as a requirement
> ---
>
> Key: AMBARI-19285
> URL: https://issues.apache.org/jira/browse/AMBARI-19285
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
>
> Host Ordered Upgrades do not require the cluster services to be installed in
> HA mode. However, when executing:
> {code}
> GET
> api/v1/clusters/c1/rolling_upgrades_check?fields=*&UpgradeChecks/repository_version=2.5.3.0-37&UpgradeChecks/upgrade_type=HOST_ORDERED"
> {code}
> HA-only upgrade checks (like Secondary NameNode Removal and NameNode HA) are
> running and failing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
