[jira] [Updated] (AMBARI-17418) Fix for LLAP calculation to happen on invocation by Blueprints and HIVE SERVER INTERACTIVE is ON (1st invocation to Stack Advisor). Also, reverts AMBARI-17283.
[ https://issues.apache.org/jira/browse/AMBARI-17418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-17418: - Resolution: Fixed Status: Resolved (was: Patch Available) > Fix for LLAP calculation to happen on invocation by Blueprints and HIVE > SERVER INTERACTIVE is ON (1st invocation to Stack Advisor). Also, reverts > AMBARI-17283. > --- > > Key: AMBARI-17418 > URL: https://issues.apache.org/jira/browse/AMBARI-17418 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.4.0 > > Attachments: AMBARI-17418.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17418) Fix for LLAP calculation to happen on invocation by Blueprints and HIVE SERVER INTERACTIVE is ON (1st invocation to Stack Advisor). Also, reverts AMBARI-17283.
[ https://issues.apache.org/jira/browse/AMBARI-17418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-17418: - Attachment: AMBARI-17418.patch > Fix for LLAP calculation to happen on invocation by Blueprints and HIVE > SERVER INTERACTIVE is ON (1st invocation to Stack Advisor). Also, reverts > AMBARI-17283. > --- > > Key: AMBARI-17418 > URL: https://issues.apache.org/jira/browse/AMBARI-17418 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.4.0 > > Attachments: AMBARI-17418.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17418) Fix for LLAP calculation to happen on invocation by Blueprints and HIVE SERVER INTERACTIVE is ON (1st invocation to Stack Advisor). Also, reverts AMBARI-17283.
[ https://issues.apache.org/jira/browse/AMBARI-17418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-17418: - Status: Patch Available (was: Open) > Fix for LLAP calculation to happen on invocation by Blueprints and HIVE > SERVER INTERACTIVE is ON (1st invocation to Stack Advisor). Also, reverts > AMBARI-17283. > --- > > Key: AMBARI-17418 > URL: https://issues.apache.org/jira/browse/AMBARI-17418 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.4.0 > > Attachments: AMBARI-17418.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17418) Fix for LLAP calculation to happen on invocation by Blueprints and HIVE SERVER INTERACTIVE is ON (1st invocation to Stack Advisor). Also, reverts AMBARI-17283.
[
https://issues.apache.org/jira/browse/AMBARI-17418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15347884#comment-15347884
]
Swapan Shridhar commented on AMBARI-17418:
--
Commits :
trunk:
{code}
commit b79806ec23350ca5ce293e447cd14f7bba13d1a5
Author: Swapan Shridhar
Date: Thu Jun 23 21:48:37 2016 -0700
AMBARI-17418. Fix for LLAP calculation to happen on invocation by
Blueprints and HIVE SERVER INTERACTIVE is ON (1st invocation to Stack Advisor).
Also, reverts AMBARI-17283.
{code}
branch-2.4
{code}
commit b796932cd52676eb9a1544938a88d00fd07526a6
Author: Swapan Shridhar
Date: Fri Jun 24 00:11:10 2016 -0700
AMBARI-17418. Fix for LLAP calculation to happen on invocation by
Blueprints and HIVE SERVER INTERACTIVE is ON (1st invocation to Stack Advisor).
Also, reverts AMBARI-17283.
{code}
> Fix for LLAP calculation to happen on invocation by Blueprints and HIVE
> SERVER INTERACTIVE is ON (1st invocation to Stack Advisor). Also, reverts
> AMBARI-17283.
> ---
>
> Key: AMBARI-17418
> URL: https://issues.apache.org/jira/browse/AMBARI-17418
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.4.0
>
> Attachments: AMBARI-17418.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17408) Use the correct config for slider AM size 'slider_am_container_mb' to set its value during LLAP config calculations.
[
https://issues.apache.org/jira/browse/AMBARI-17408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15347891#comment-15347891
]
Swapan Shridhar commented on AMBARI-17408:
--
commits :
trunk:
{code}
commit cc9d625d712f4988911af1b821c76c4a40753f5d
Author: Swapan Shridhar
Date: Thu Jun 23 12:45:12 2016 -0700
AMBARI-17408. Use the correct config for slider AM size
'slider_am_container_mb' to set its value during LLAP config calculations.
{code}
branch-2.4:
{code}
commit d43622941b41af34b0f021031d972e803f3a36e5
Author: Swapan Shridhar
Date: Thu Jun 23 12:52:10 2016 -0700
AMBARI-17408. Use the correct config for slider AM size
'slider_am_container_mb' to set its value during LLAP config calculations.
{code}
> Use the correct config for slider AM size 'slider_am_container_mb' to set its
> value during LLAP config calculations.
>
>
> Key: AMBARI-17408
> URL: https://issues.apache.org/jira/browse/AMBARI-17408
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.4.0
>
> Attachments: AMBARI-17408.patch
>
>
> - Currently, it uses config 'slider_am_container_size' which doesn't exist.
> - use correct config name 'slider_am_container_mb'
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17384) Remove '/usr/hdp' hardcoding from HIVE's alert_llap_app_status.py and KNOX's upgrade.py
[ https://issues.apache.org/jira/browse/AMBARI-17384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-17384: - Resolution: Fixed Status: Resolved (was: Patch Available) > Remove '/usr/hdp' hardcoding from HIVE's alert_llap_app_status.py and KNOX's > upgrade.py > --- > > Key: AMBARI-17384 > URL: https://issues.apache.org/jira/browse/AMBARI-17384 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.4.0 > > Attachments: AMBARI-17384.patch > > > - Use 'Script.get_stack_root()'. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17419) Disabling the auto-start for ambari-server and ambari-agent doesn't work on systemd
Sebastian Toader created AMBARI-17419:
-
Summary: Disabling the auto-start for ambari-server and
ambari-agent doesn't work on systemd
Key: AMBARI-17419
URL: https://issues.apache.org/jira/browse/AMBARI-17419
Project: Ambari
Issue Type: Bug
Components: ambari-agent, ambari-server
Reporter: Sebastian Toader
Assignee: Sebastian Toader
Fix For: 2.4.0
Trying do disable auto-start for ambari-server by executing {{update-rc.d
ambari-server disable}} is failing with {{update-rc.d: error: ambari-server
Default-Start contains no runlevels, aborting.}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15966) ambari-web 2.2.1 build error
[ https://issues.apache.org/jira/browse/AMBARI-15966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15347910#comment-15347910 ] poseidon commented on AMBARI-15966: --- Got the same error , looks like some brunch compile file was too old for a new version brunch. > ambari-web 2.2.1 build error > > > Key: AMBARI-15966 > URL: https://issues.apache.org/jira/browse/AMBARI-15966 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.1 >Reporter: skrho >Assignee: Jaimin D Jetly > Fix For: 2.4.0 > > > Hi Everyone~~ > Now I am building the ambari-web 2.2.1 version > My Environment is > npm : 3.8.7 > node : 4.4.3 > brunch : 2.5.3 > I have a problem when building .. > I just command > # $apache-ambari-2.2.1-src/ambari-web]#brunch build -d > There is error message > brunch:config Trying to load brunch-config +0ms > brunch:config Trying to load config +5ms > 19 Apr 08:26:28 - warn: config.files.stylesheets.defaultPaths was removed > 19 Apr 08:26:28 - warn: config.files.templates.defaultPaths was removed > 19 Apr 08:26:28 - error: Initialization error - You probably need to execute > `npm install` to install brunch plugins. SyntaxError: Setter must have > exactly one formal parameter. > at /usr/lib/node_modules/brunch/lib/plugins.js:101:17 > at Array.map (native) > at deps.filter.dependency.map > (/usr/lib/node_modules/brunch/lib/plugins.js:88:8) > at packages.filter.plugins.map.plugin.filter.deps.filter.allPlugins.filter > (/usr/lib/node_modules/brunch/lib/plugins.js:108:19) > at > Object.packages.filter.plugins.map.plugin.filter.deps.filter.exports.init.plugins.filter.map.preCompilers.push.teardownBrunch > [as init] (/usr/lib/node_modules/brunch/lib/plugins.js:131:20) > at /usr/lib/node_modules/brunch/lib/watch.js:101:19 > Please Help me~ > What can I do that? > In advanced Thank you everyone -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17419) Disabling the auto-start for ambari-server and ambari-agent doesn't work on systemd
[
https://issues.apache.org/jira/browse/AMBARI-17419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Toader updated AMBARI-17419:
--
Attachment: AMBARI-17419.v1.patch
> Disabling the auto-start for ambari-server and ambari-agent doesn't work on
> systemd
> ---
>
> Key: AMBARI-17419
> URL: https://issues.apache.org/jira/browse/AMBARI-17419
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-server
>Reporter: Sebastian Toader
>Assignee: Sebastian Toader
> Fix For: 2.4.0
>
> Attachments: AMBARI-17419.v1.patch
>
>
> Trying do disable auto-start for ambari-server by executing {{update-rc.d
> ambari-server disable}} is failing with {{update-rc.d: error: ambari-server
> Default-Start contains no runlevels, aborting.}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17419) Disabling the auto-start for ambari-server and ambari-agent doesn't work on systemd
[
https://issues.apache.org/jira/browse/AMBARI-17419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Toader updated AMBARI-17419:
--
Status: Patch Available (was: In Progress)
> Disabling the auto-start for ambari-server and ambari-agent doesn't work on
> systemd
> ---
>
> Key: AMBARI-17419
> URL: https://issues.apache.org/jira/browse/AMBARI-17419
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-server
>Reporter: Sebastian Toader
>Assignee: Sebastian Toader
> Fix For: 2.4.0
>
> Attachments: AMBARI-17419.v1.patch
>
>
> Trying do disable auto-start for ambari-server by executing {{update-rc.d
> ambari-server disable}} is failing with {{update-rc.d: error: ambari-server
> Default-Start contains no runlevels, aborting.}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17383) User names should be case insensitive
[
https://issues.apache.org/jira/browse/AMBARI-17383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15347922#comment-15347922
]
Hadoop QA commented on AMBARI-17383:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12812985/rb49119%20%281%29.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 5 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/7525//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7525//console
This message is automatically generated.
> User names should be case insensitive
> -
>
> Key: AMBARI-17383
> URL: https://issues.apache.org/jira/browse/AMBARI-17383
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: rb49119 (1).patch
>
>
> User names should be case insensitive. The following usernames are the same:
> VIEWUSER
> viewUser
> viewuser
> Before adding a new user, a case sensitive search is made. Change this to
> case insensitive. Additionally, store user names in the DB in lower case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17416) AMS-Grafana: show 'alias' when there's no datapoint available
[
https://issues.apache.org/jira/browse/AMBARI-17416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15347934#comment-15347934
]
Hadoop QA commented on AMBARI-17416:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12812972/AMBARI-17416-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:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7526//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7526//console
This message is automatically generated.
> AMS-Grafana: show 'alias' when there's no datapoint available
> -
>
> Key: AMBARI-17416
> URL: https://issues.apache.org/jira/browse/AMBARI-17416
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-metrics
>Affects Versions: 2.4.0
>Reporter: Jungtaek Lim
>Priority: Minor
> Attachments: AMBARI-17416-v1.patch
>
>
> When there's no datapoint available, AMS Grafana plugin just ignores alias
> and shows metric name instead. It seems to be not consistent in point of
> view, and not good UX I think.
> It'd be great AMS Grafana shows alias whenever there're datapoints available
> or not.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-17420) Audit log_message field changes for handling search issues.
Dharmesh Makwana created AMBARI-17420: - Summary: Audit log_message field changes for handling search issues. Key: AMBARI-17420 URL: https://issues.apache.org/jira/browse/AMBARI-17420 Project: Ambari Issue Type: Bug Components: ambari-logsearch Affects Versions: 2.4.0 Reporter: Dharmesh Makwana Assignee: Dharmesh Makwana Fix For: 2.4.0 Creating copyField for log_message with tokenizer key_log_message -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17420) Audit log_message field changes for handling search issues.
[ https://issues.apache.org/jira/browse/AMBARI-17420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dharmesh Makwana updated AMBARI-17420: -- Description: Creating copyField for log_message with keyword tokenizer. (was: Creating copyField for log_message with tokenizer key_log_message) > Audit log_message field changes for handling search issues. > --- > > Key: AMBARI-17420 > URL: https://issues.apache.org/jira/browse/AMBARI-17420 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.4.0 >Reporter: Dharmesh Makwana >Assignee: Dharmesh Makwana > Fix For: 2.4.0 > > > Creating copyField for log_message with keyword tokenizer. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17408) Use the correct config for slider AM size 'slider_am_container_mb' to set its value during LLAP config calculations.
[ https://issues.apache.org/jira/browse/AMBARI-17408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348154#comment-15348154 ] Hudson commented on AMBARI-17408: - ABORTED: Integrated in Ambari-trunk-Commit #5152 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5152/]) AMBARI-17408. Use the correct config for slider AM size (sshridhar: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=cc9d625d712f4988911af1b821c76c4a40753f5d]) * ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py * ambari-server/src/test/python/stacks/2.5/common/test_stack_advisor.py > Use the correct config for slider AM size 'slider_am_container_mb' to set its > value during LLAP config calculations. > > > Key: AMBARI-17408 > URL: https://issues.apache.org/jira/browse/AMBARI-17408 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.4.0 > > Attachments: AMBARI-17408.patch > > > - Currently, it uses config 'slider_am_container_size' which doesn't exist. > - use correct config name 'slider_am_container_mb' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17418) Fix for LLAP calculation to happen on invocation by Blueprints and HIVE SERVER INTERACTIVE is ON (1st invocation to Stack Advisor). Also, reverts AMBARI-17283.
[ https://issues.apache.org/jira/browse/AMBARI-17418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348155#comment-15348155 ] Hudson commented on AMBARI-17418: - ABORTED: Integrated in Ambari-trunk-Commit #5152 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5152/]) AMBARI-17418. Fix for LLAP calculation to happen on invocation by (sshridhar: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b79806ec23350ca5ce293e447cd14f7bba13d1a5]) * ambari-server/src/test/python/stacks/2.5/common/test_stack_advisor.py * ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/themes/theme.json * ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/configuration/hive-interactive-site.xml * ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/configuration/hive-interactive-env.xml * ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py > Fix for LLAP calculation to happen on invocation by Blueprints and HIVE > SERVER INTERACTIVE is ON (1st invocation to Stack Advisor). Also, reverts > AMBARI-17283. > --- > > Key: AMBARI-17418 > URL: https://issues.apache.org/jira/browse/AMBARI-17418 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.4.0 > > Attachments: AMBARI-17418.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17421) Hive view : Upload Table feature should support various column and row delimiters
Nitiraj Singh Rathore created AMBARI-17421: -- Summary: Hive view : Upload Table feature should support various column and row delimiters Key: AMBARI-17421 URL: https://issues.apache.org/jira/browse/AMBARI-17421 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.2.2 Reporter: Nitiraj Singh Rathore Assignee: Nitiraj Singh Rathore Fix For: 2.4.0 Currently Uploaded table can have only one CSV format which supports field delimiter as comma and row delimiter as endline. The view should take this as input from User and/or support other standards. Also column values should support endline character etc as input. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17421) Hive view : Upload Table feature should support various column and row delimiters
[ https://issues.apache.org/jira/browse/AMBARI-17421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348162#comment-15348162 ] Nitiraj Singh Rathore commented on AMBARI-17421: Hive only supports endline (\n) as LINES TERMINATED BY char. So hive tables line terminator will to be customized. So for hive TEXTFILE's FIELDS TERMINATED BY char and ESCAPED BY char will be supported. CSV's column delimiter, quote, and escape character will be supported. > Hive view : Upload Table feature should support various column and row > delimiters > - > > Key: AMBARI-17421 > URL: https://issues.apache.org/jira/browse/AMBARI-17421 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.2.2 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.4.0 > > > Currently Uploaded table can have only one CSV format which supports field > delimiter as comma and row delimiter as endline. > The view should take this as input from User and/or support other standards. > Also column values should support endline character etc as input. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17422) Add missing components to LogSearch
Olivér Szabó created AMBARI-17422: - Summary: Add missing components to LogSearch Key: AMBARI-17422 URL: https://issues.apache.org/jira/browse/AMBARI-17422 Project: Ambari Issue Type: Bug Components: ambari-logsearch, ambari-server Affects Versions: 2.4.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 2.4.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17423) Add missing components to LogSearch (part I)
Olivér Szabó created AMBARI-17423: - Summary: Add missing components to LogSearch (part I) Key: AMBARI-17423 URL: https://issues.apache.org/jira/browse/AMBARI-17423 Project: Ambari Issue Type: Technical task Components: ambari-logsearch, ambari-server Affects Versions: 2.4.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 2.4.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17424) Add missing components to LogSearch (part II)
Olivér Szabó created AMBARI-17424: - Summary: Add missing components to LogSearch (part II) Key: AMBARI-17424 URL: https://issues.apache.org/jira/browse/AMBARI-17424 Project: Ambari Issue Type: Bug Components: ambari-logsearch, ambari-server Affects Versions: 2.4.0 Reporter: Olivér Szabó Assignee: Miklos Gergely Fix For: 2.4.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17410) Incorrect error message for invalid category in Host Combo Search Box
[ https://issues.apache.org/jira/browse/AMBARI-17410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-17410: Status: Open (was: Patch Available) > Incorrect error message for invalid category in Host Combo Search Box > - > > Key: AMBARI-17410 > URL: https://issues.apache.org/jira/browse/AMBARI-17410 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-17410.patch, ErrorMessage.jpg, > ErrorMessageWithFix.jpg > > > 1. In the host combo box, if an invalid category is entered, an error is > displayed > [object Object] is not a valid category. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17425) [Hive view] hiveserver service check fails for LDAP configured hive view
Pallav Kulshreshtha created AMBARI-17425: Summary: [Hive view] hiveserver service check fails for LDAP configured hive view Key: AMBARI-17425 URL: https://issues.apache.org/jira/browse/AMBARI-17425 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.4.0 Reporter: Pallav Kulshreshtha Assignee: Pallav Kulshreshtha Fix For: 2.4.0 hiveserver service check fails for LDAP configured hive view. There should be some flow to enter the user LDAP credentials and progress further. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17410) Incorrect error message for invalid category in Host Combo Search Box
[ https://issues.apache.org/jira/browse/AMBARI-17410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-17410: Attachment: AMBARI-17410.patch > Incorrect error message for invalid category in Host Combo Search Box > - > > Key: AMBARI-17410 > URL: https://issues.apache.org/jira/browse/AMBARI-17410 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-17410.patch, ErrorMessage.jpg, > ErrorMessageWithFix.jpg > > > 1. In the host combo box, if an invalid category is entered, an error is > displayed > [object Object] is not a valid category. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17410) Incorrect error message for invalid category in Host Combo Search Box
[ https://issues.apache.org/jira/browse/AMBARI-17410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-17410: Attachment: (was: AMBARI-17410.patch) > Incorrect error message for invalid category in Host Combo Search Box > - > > Key: AMBARI-17410 > URL: https://issues.apache.org/jira/browse/AMBARI-17410 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-17410.patch, ErrorMessage.jpg, > ErrorMessageWithFix.jpg > > > 1. In the host combo box, if an invalid category is entered, an error is > displayed > [object Object] is not a valid category. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17423) Add missing components to LogSearch (part I)
[ https://issues.apache.org/jira/browse/AMBARI-17423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-17423: -- Description: Contain the following components: SPARK SPARK2 METRICS_GRAFANA NFS_GATEWAY SmartSense WEBHCAT_SERVER LIVY > Add missing components to LogSearch (part I) > > > Key: AMBARI-17423 > URL: https://issues.apache.org/jira/browse/AMBARI-17423 > Project: Ambari > Issue Type: Technical task > Components: ambari-logsearch, ambari-server >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 2.4.0 > > > Contain the following components: > SPARK > SPARK2 > METRICS_GRAFANA > NFS_GATEWAY > SmartSense > WEBHCAT_SERVER > LIVY -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17410) Incorrect error message for invalid category in Host Combo Search Box
[ https://issues.apache.org/jira/browse/AMBARI-17410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-17410: Status: Patch Available (was: In Progress) > Incorrect error message for invalid category in Host Combo Search Box > - > > Key: AMBARI-17410 > URL: https://issues.apache.org/jira/browse/AMBARI-17410 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-17410.patch, ErrorMessage.jpg, > ErrorMessageWithFix.jpg > > > 1. In the host combo box, if an invalid category is entered, an error is > displayed > [object Object] is not a valid category. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17422) Add missing components to LogSearch
[ https://issues.apache.org/jira/browse/AMBARI-17422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-17422: -- Description: Add missing service grok patters to Logsearch service > Add missing components to LogSearch > --- > > Key: AMBARI-17422 > URL: https://issues.apache.org/jira/browse/AMBARI-17422 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, ambari-server >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 2.4.0 > > > Add missing service grok patters to Logsearch service -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16756) Update code for Ranger Service to use PID file for status and stop call
[ https://issues.apache.org/jira/browse/AMBARI-16756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-16756: - Attachment: AMBARI-16756.patch > Update code for Ranger Service to use PID file for status and stop call > --- > > Key: AMBARI-16756 > URL: https://issues.apache.org/jira/browse/AMBARI-16756 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16756.patch > > > After getting PID file generated from Ranger code. Need to update ambari > ranger code for stop and status call. > cc [~gautamborad]/[~mehul] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16756) Update code for Ranger Service to use PID file for status and stop call
[ https://issues.apache.org/jira/browse/AMBARI-16756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-16756: - Status: Patch Available (was: In Progress) > Update code for Ranger Service to use PID file for status and stop call > --- > > Key: AMBARI-16756 > URL: https://issues.apache.org/jira/browse/AMBARI-16756 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16756.patch > > > After getting PID file generated from Ranger code. Need to update ambari > ranger code for stop and status call. > cc [~gautamborad]/[~mehul] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17425) [Hive view] hiveserver service check fails for LDAP configured hive view
[ https://issues.apache.org/jira/browse/AMBARI-17425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallav Kulshreshtha updated AMBARI-17425: - Attachment: AMBARI-17425_branch-2.4.patch > [Hive view] hiveserver service check fails for LDAP configured hive view > > > Key: AMBARI-17425 > URL: https://issues.apache.org/jira/browse/AMBARI-17425 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Pallav Kulshreshtha >Assignee: Pallav Kulshreshtha > Fix For: 2.4.0 > > Attachments: AMBARI-17425_branch-2.4.patch > > > hiveserver service check fails for LDAP configured hive view. > There should be some flow to enter the user LDAP credentials and progress > further. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17423) Add missing components to LogSearch (part I)
[ https://issues.apache.org/jira/browse/AMBARI-17423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-17423: -- Attachment: AMBARI-17423.patch > Add missing components to LogSearch (part I) > > > Key: AMBARI-17423 > URL: https://issues.apache.org/jira/browse/AMBARI-17423 > Project: Ambari > Issue Type: Technical task > Components: ambari-logsearch, ambari-server >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 2.4.0 > > Attachments: AMBARI-17423.patch > > > Contain the following components: > SPARK > SPARK2 > METRICS_GRAFANA > NFS_GATEWAY > SmartSense > WEBHCAT_SERVER > LIVY -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17425) [Hive view] hiveserver service check fails for LDAP configured hive view
[ https://issues.apache.org/jira/browse/AMBARI-17425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallav Kulshreshtha updated AMBARI-17425: - Status: Patch Available (was: Open) > [Hive view] hiveserver service check fails for LDAP configured hive view > > > Key: AMBARI-17425 > URL: https://issues.apache.org/jira/browse/AMBARI-17425 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Pallav Kulshreshtha >Assignee: Pallav Kulshreshtha > Fix For: 2.4.0 > > Attachments: AMBARI-17425_branch-2.4.patch > > > hiveserver service check fails for LDAP configured hive view. > There should be some flow to enter the user LDAP credentials and progress > further. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17423) Add missing components to LogSearch (part I)
[ https://issues.apache.org/jira/browse/AMBARI-17423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-17423: -- Attachment: (was: AMBARI-17423.patch) > Add missing components to LogSearch (part I) > > > Key: AMBARI-17423 > URL: https://issues.apache.org/jira/browse/AMBARI-17423 > Project: Ambari > Issue Type: Technical task > Components: ambari-logsearch, ambari-server >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 2.4.0 > > Attachments: AMBARI-17423.patch > > > Contain the following components: > SPARK > SPARK2 > METRICS_GRAFANA > NFS_GATEWAY > SmartSense > WEBHCAT_SERVER > LIVY -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17423) Add missing components to LogSearch (part I)
[ https://issues.apache.org/jira/browse/AMBARI-17423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-17423: -- Attachment: AMBARI-17423.patch > Add missing components to LogSearch (part I) > > > Key: AMBARI-17423 > URL: https://issues.apache.org/jira/browse/AMBARI-17423 > Project: Ambari > Issue Type: Technical task > Components: ambari-logsearch, ambari-server >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 2.4.0 > > Attachments: AMBARI-17423.patch > > > Contain the following components: > SPARK > SPARK2 > METRICS_GRAFANA > NFS_GATEWAY > SmartSense > WEBHCAT_SERVER > LIVY -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17424) Add missing components to LogSearch (part II)
[ https://issues.apache.org/jira/browse/AMBARI-17424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-17424: -- Issue Type: Technical task (was: Bug) Parent: AMBARI-17422 > Add missing components to LogSearch (part II) > - > > Key: AMBARI-17424 > URL: https://issues.apache.org/jira/browse/AMBARI-17424 > Project: Ambari > Issue Type: Technical task > Components: ambari-logsearch, ambari-server >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Miklos Gergely > Fix For: 2.4.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-17368) Quick link to remove browser URL params.
[
https://issues.apache.org/jira/browse/AMBARI-17368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó resolved AMBARI-17368.
---
Resolution: Fixed
{code:java}
commit c98597fd1de21cd547c9fbdc809f136d398ce5db
Author: oleewere
Date: Fri Jun 24 14:28:26 2016 +0200
AMBARI-17368. Log Search: Quick link to remove browser URL params.
(Dharmesh Makwana via oleewere)
{code}
comitted to branch-2.4:
{code:java}
commit 87f7fec4cdd4fa7849f392e9e3a6030369e5cb70
Author: oleewere
Date: Fri Jun 24 14:28:26 2016 +0200
AMBARI-17368. Log Search: Quick link to remove browser URL params.
(Dharmesh Makwana via oleewere)
{code}
> Quick link to remove browser URL params.
>
>
> Key: AMBARI-17368
> URL: https://issues.apache.org/jira/browse/AMBARI-17368
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-logsearch
>Affects Versions: 2.4.0
>Reporter: Dharmesh Makwana
>Assignee: Dharmesh Makwana
> Fix For: 2.4.0
>
>
> Now user can remove browser url params which are locked through quick link.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17426) Ambari server setup failed on debian with postgres local db
[ https://issues.apache.org/jira/browse/AMBARI-17426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-17426: - Attachment: AMBARI-17426.patch > Ambari server setup failed on debian with postgres local db > --- > > Key: AMBARI-17426 > URL: https://issues.apache.org/jira/browse/AMBARI-17426 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.4.0 > > Attachments: AMBARI-17426.patch > > > We have tests where we cleanup existing cluster and reinstall Ambari again - > perform install, setup and start Ambari server. Starting up AMbari server is > failing with the below erro > > > > Using python /usr/bin/python > Starting ambari-server > ERROR: Exiting with exit code 1. > REASON: Unable to detect a system user for Ambari Server. > - If this is a new setup, then run the "ambari-server setup" command to > create the user > - If this is an upgrade of an existing setup, run the "ambari-server > upgrade" command. > Refer to the Ambari documentation for more information on setup and > upgrade. > > Please see the logs [here](http://qelog.hortonworks.com/log/nat-os-d7-luls- > ambari-blueprints-3/test-logs/ambari-blueprints/artifacts/screenshots/com.hw.a > mbari.ui.tests.heavyweights.TestSingleNodeClustersViaBlueprint/testA_PrepareCl > uster/_23_0_54_11_Exceptions_appeared_during_install/test_logs/test_TestSingle > NodeClustersViaBlueprint_debug.log). We can see that at the beginning Ambari > server is up and running fine. BUt after cleanup and reinstall server is not > coming up. Could you please help take a look. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17426) Ambari server setup failed on debian with postgres local db
Andrew Onischuk created AMBARI-17426: Summary: Ambari server setup failed on debian with postgres local db Key: AMBARI-17426 URL: https://issues.apache.org/jira/browse/AMBARI-17426 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.4.0 Attachments: AMBARI-17426.patch We have tests where we cleanup existing cluster and reinstall Ambari again - perform install, setup and start Ambari server. Starting up AMbari server is failing with the below erro Using python /usr/bin/python Starting ambari-server ERROR: Exiting with exit code 1. REASON: Unable to detect a system user for Ambari Server. - If this is a new setup, then run the "ambari-server setup" command to create the user - If this is an upgrade of an existing setup, run the "ambari-server upgrade" command. Refer to the Ambari documentation for more information on setup and upgrade. Please see the logs [here](http://qelog.hortonworks.com/log/nat-os-d7-luls- ambari-blueprints-3/test-logs/ambari-blueprints/artifacts/screenshots/com.hw.a mbari.ui.tests.heavyweights.TestSingleNodeClustersViaBlueprint/testA_PrepareCl uster/_23_0_54_11_Exceptions_appeared_during_install/test_logs/test_TestSingle NodeClustersViaBlueprint_debug.log). We can see that at the beginning Ambari server is up and running fine. BUt after cleanup and reinstall server is not coming up. Could you please help take a look. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17426) Ambari server setup failed on debian with postgres local db
[ https://issues.apache.org/jira/browse/AMBARI-17426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-17426: - Status: Patch Available (was: Open) > Ambari server setup failed on debian with postgres local db > --- > > Key: AMBARI-17426 > URL: https://issues.apache.org/jira/browse/AMBARI-17426 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.4.0 > > Attachments: AMBARI-17426.patch > > > We have tests where we cleanup existing cluster and reinstall Ambari again - > perform install, setup and start Ambari server. Starting up AMbari server is > failing with the below erro > > > > Using python /usr/bin/python > Starting ambari-server > ERROR: Exiting with exit code 1. > REASON: Unable to detect a system user for Ambari Server. > - If this is a new setup, then run the "ambari-server setup" command to > create the user > - If this is an upgrade of an existing setup, run the "ambari-server > upgrade" command. > Refer to the Ambari documentation for more information on setup and > upgrade. > > Please see the logs [here](http://qelog.hortonworks.com/log/nat-os-d7-luls- > ambari-blueprints-3/test-logs/ambari-blueprints/artifacts/screenshots/com.hw.a > mbari.ui.tests.heavyweights.TestSingleNodeClustersViaBlueprint/testA_PrepareCl > uster/_23_0_54_11_Exceptions_appeared_during_install/test_logs/test_TestSingle > NodeClustersViaBlueprint_debug.log). We can see that at the beginning Ambari > server is up and running fine. BUt after cleanup and reinstall server is not > coming up. Could you please help take a look. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17426) Ambari server setup failed on debian with postgres local db
[
https://issues.apache.org/jira/browse/AMBARI-17426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348227#comment-15348227
]
Hadoop QA commented on AMBARI-17426:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12813073/AMBARI-17426.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7527//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7527//console
This message is automatically generated.
> Ambari server setup failed on debian with postgres local db
> ---
>
> Key: AMBARI-17426
> URL: https://issues.apache.org/jira/browse/AMBARI-17426
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-17426.patch
>
>
> We have tests where we cleanup existing cluster and reinstall Ambari again -
> perform install, setup and start Ambari server. Starting up AMbari server is
> failing with the below erro
>
>
>
> Using python /usr/bin/python
> Starting ambari-server
> ERROR: Exiting with exit code 1.
> REASON: Unable to detect a system user for Ambari Server.
> - If this is a new setup, then run the "ambari-server setup" command to
> create the user
> - If this is an upgrade of an existing setup, run the "ambari-server
> upgrade" command.
> Refer to the Ambari documentation for more information on setup and
> upgrade.
>
> Please see the logs [here](http://qelog.hortonworks.com/log/nat-os-d7-luls-
> ambari-blueprints-3/test-logs/ambari-blueprints/artifacts/screenshots/com.hw.a
> mbari.ui.tests.heavyweights.TestSingleNodeClustersViaBlueprint/testA_PrepareCl
> uster/_23_0_54_11_Exceptions_appeared_during_install/test_logs/test_TestSingle
> NodeClustersViaBlueprint_debug.log). We can see that at the beginning Ambari
> server is up and running fine. BUt after cleanup and reinstall server is not
> coming up. Could you please help take a look.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-17427) Support Atlas in kerberized environment, submit Service Check as smokeuser
Dmitry Lysnichenko created AMBARI-17427:
---
Summary: Support Atlas in kerberized environment, submit Service
Check as smokeuser
Key: AMBARI-17427
URL: https://issues.apache.org/jira/browse/AMBARI-17427
Project: Ambari
Issue Type: Bug
Reporter: Dmitry Lysnichenko
Assignee: Dmitry Lysnichenko
Attachments: AMBARI-17427.patch
Atlas Service Check should use smokeuser instead of atlas user.
{code}
2016-06-19 10:46:19,971 - Using hadoop conf dir:
/usr/hdp/current/hadoop-client/conf
2016-06-19 10:46:19,979 - Execute['/usr/bin/kinit -kt
/etc/security/keytabs/smokeuser.headless.keytab ambari-qa-...@example.com']
{'user': 'atlas'}
2016-06-19 10:46:20,198 - Execute['curl --negotiate -u : -b ~/cookiejar.txt -c
~/cookiejar.txt -s -o /dev/null -w "%{http_code}"
http://mneethiraj-0618-1.openstacklocal:21000/'] {'tries': 5, 'user': 'atlas',
'try_sleep': 10}
2016-06-19 10:46:50,438 - Retrying after 10 seconds. Reason: Execution of 'curl
--negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null -w
"%{http_code}" http://mneethiraj-0618-1.openstacklocal:21000/' returned 52. 000
2016-06-19 10:47:30,610 - Retrying after 10 seconds. Reason: Execution of 'curl
--negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null -w
"%{http_code}" http://mneethiraj-0618-1.openstacklocal:21000/' returned 52. 000
2016-06-19 10:48:10,738 - Retrying after 10 seconds. Reason: Execution of 'curl
--negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null -w
"%{http_code}" http://mneethiraj-0618-1.openstacklocal:21000/' returned 52. 000
2016-06-19 10:48:50,863 - Retrying after 10 seconds. Reason: Execution of 'curl
--negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null -w
"%{http_code}" http://mneethiraj-0618-1.openstacklocal:21000/' returned 52. 000
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17427) Support Atlas in kerberized environment, submit Service Check as smokeuser
[
https://issues.apache.org/jira/browse/AMBARI-17427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-17427:
Attachment: AMBARI-17427.patch
> Support Atlas in kerberized environment, submit Service Check as smokeuser
> --
>
> Key: AMBARI-17427
> URL: https://issues.apache.org/jira/browse/AMBARI-17427
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Attachments: AMBARI-17427.patch
>
>
> Atlas Service Check should use smokeuser instead of atlas user.
> {code}
> 2016-06-19 10:46:19,971 - Using hadoop conf dir:
> /usr/hdp/current/hadoop-client/conf
> 2016-06-19 10:46:19,979 - Execute['/usr/bin/kinit -kt
> /etc/security/keytabs/smokeuser.headless.keytab ambari-qa-...@example.com']
> {'user': 'atlas'}
> 2016-06-19 10:46:20,198 - Execute['curl --negotiate -u : -b ~/cookiejar.txt
> -c ~/cookiejar.txt -s -o /dev/null -w "%{http_code}"
> http://mneethiraj-0618-1.openstacklocal:21000/'] {'tries': 5, 'user':
> 'atlas', 'try_sleep': 10}
> 2016-06-19 10:46:50,438 - Retrying after 10 seconds. Reason: Execution of
> 'curl --negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null
> -w "%{http_code}" http://mneethiraj-0618-1.openstacklocal:21000/' returned
> 52. 000
> 2016-06-19 10:47:30,610 - Retrying after 10 seconds. Reason: Execution of
> 'curl --negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null
> -w "%{http_code}" http://mneethiraj-0618-1.openstacklocal:21000/' returned
> 52. 000
> 2016-06-19 10:48:10,738 - Retrying after 10 seconds. Reason: Execution of
> 'curl --negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null
> -w "%{http_code}" http://mneethiraj-0618-1.openstacklocal:21000/' returned
> 52. 000
> 2016-06-19 10:48:50,863 - Retrying after 10 seconds. Reason: Execution of
> 'curl --negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null
> -w "%{http_code}" http://mneethiraj-0618-1.openstacklocal:21000/' returned
> 52. 000
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17427) Support Atlas in kerberized environment, submit Service Check as smokeuser
[
https://issues.apache.org/jira/browse/AMBARI-17427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-17427:
Status: Patch Available (was: Open)
> Support Atlas in kerberized environment, submit Service Check as smokeuser
> --
>
> Key: AMBARI-17427
> URL: https://issues.apache.org/jira/browse/AMBARI-17427
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Attachments: AMBARI-17427.patch
>
>
> Atlas Service Check should use smokeuser instead of atlas user.
> {code}
> 2016-06-19 10:46:19,971 - Using hadoop conf dir:
> /usr/hdp/current/hadoop-client/conf
> 2016-06-19 10:46:19,979 - Execute['/usr/bin/kinit -kt
> /etc/security/keytabs/smokeuser.headless.keytab ambari-qa-...@example.com']
> {'user': 'atlas'}
> 2016-06-19 10:46:20,198 - Execute['curl --negotiate -u : -b ~/cookiejar.txt
> -c ~/cookiejar.txt -s -o /dev/null -w "%{http_code}"
> http://mneethiraj-0618-1.openstacklocal:21000/'] {'tries': 5, 'user':
> 'atlas', 'try_sleep': 10}
> 2016-06-19 10:46:50,438 - Retrying after 10 seconds. Reason: Execution of
> 'curl --negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null
> -w "%{http_code}" http://mneethiraj-0618-1.openstacklocal:21000/' returned
> 52. 000
> 2016-06-19 10:47:30,610 - Retrying after 10 seconds. Reason: Execution of
> 'curl --negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null
> -w "%{http_code}" http://mneethiraj-0618-1.openstacklocal:21000/' returned
> 52. 000
> 2016-06-19 10:48:10,738 - Retrying after 10 seconds. Reason: Execution of
> 'curl --negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null
> -w "%{http_code}" http://mneethiraj-0618-1.openstacklocal:21000/' returned
> 52. 000
> 2016-06-19 10:48:50,863 - Retrying after 10 seconds. Reason: Execution of
> 'curl --negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null
> -w "%{http_code}" http://mneethiraj-0618-1.openstacklocal:21000/' returned
> 52. 000
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17427) Support Atlas in kerberized environment, submit Service Check as smokeuser
[
https://issues.apache.org/jira/browse/AMBARI-17427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-17427:
Component/s: ambari-server
> Support Atlas in kerberized environment, submit Service Check as smokeuser
> --
>
> Key: AMBARI-17427
> URL: https://issues.apache.org/jira/browse/AMBARI-17427
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Attachments: AMBARI-17427.patch
>
>
> Atlas Service Check should use smokeuser instead of atlas user.
> {code}
> 2016-06-19 10:46:19,971 - Using hadoop conf dir:
> /usr/hdp/current/hadoop-client/conf
> 2016-06-19 10:46:19,979 - Execute['/usr/bin/kinit -kt
> /etc/security/keytabs/smokeuser.headless.keytab ambari-qa-...@example.com']
> {'user': 'atlas'}
> 2016-06-19 10:46:20,198 - Execute['curl --negotiate -u : -b ~/cookiejar.txt
> -c ~/cookiejar.txt -s -o /dev/null -w "%{http_code}"
> http://mneethiraj-0618-1.openstacklocal:21000/'] {'tries': 5, 'user':
> 'atlas', 'try_sleep': 10}
> 2016-06-19 10:46:50,438 - Retrying after 10 seconds. Reason: Execution of
> 'curl --negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null
> -w "%{http_code}" http://mneethiraj-0618-1.openstacklocal:21000/' returned
> 52. 000
> 2016-06-19 10:47:30,610 - Retrying after 10 seconds. Reason: Execution of
> 'curl --negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null
> -w "%{http_code}" http://mneethiraj-0618-1.openstacklocal:21000/' returned
> 52. 000
> 2016-06-19 10:48:10,738 - Retrying after 10 seconds. Reason: Execution of
> 'curl --negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null
> -w "%{http_code}" http://mneethiraj-0618-1.openstacklocal:21000/' returned
> 52. 000
> 2016-06-19 10:48:50,863 - Retrying after 10 seconds. Reason: Execution of
> 'curl --negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null
> -w "%{http_code}" http://mneethiraj-0618-1.openstacklocal:21000/' returned
> 52. 000
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17427) Support Atlas in kerberized environment, submit Service Check as smokeuser
[
https://issues.apache.org/jira/browse/AMBARI-17427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-17427:
Affects Version/s: 2.4.0
> Support Atlas in kerberized environment, submit Service Check as smokeuser
> --
>
> Key: AMBARI-17427
> URL: https://issues.apache.org/jira/browse/AMBARI-17427
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-17427.patch
>
>
> Atlas Service Check should use smokeuser instead of atlas user.
> {code}
> 2016-06-19 10:46:19,971 - Using hadoop conf dir:
> /usr/hdp/current/hadoop-client/conf
> 2016-06-19 10:46:19,979 - Execute['/usr/bin/kinit -kt
> /etc/security/keytabs/smokeuser.headless.keytab ambari-qa-...@example.com']
> {'user': 'atlas'}
> 2016-06-19 10:46:20,198 - Execute['curl --negotiate -u : -b ~/cookiejar.txt
> -c ~/cookiejar.txt -s -o /dev/null -w "%{http_code}"
> http://mneethiraj-0618-1.openstacklocal:21000/'] {'tries': 5, 'user':
> 'atlas', 'try_sleep': 10}
> 2016-06-19 10:46:50,438 - Retrying after 10 seconds. Reason: Execution of
> 'curl --negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null
> -w "%{http_code}" http://mneethiraj-0618-1.openstacklocal:21000/' returned
> 52. 000
> 2016-06-19 10:47:30,610 - Retrying after 10 seconds. Reason: Execution of
> 'curl --negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null
> -w "%{http_code}" http://mneethiraj-0618-1.openstacklocal:21000/' returned
> 52. 000
> 2016-06-19 10:48:10,738 - Retrying after 10 seconds. Reason: Execution of
> 'curl --negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null
> -w "%{http_code}" http://mneethiraj-0618-1.openstacklocal:21000/' returned
> 52. 000
> 2016-06-19 10:48:50,863 - Retrying after 10 seconds. Reason: Execution of
> 'curl --negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null
> -w "%{http_code}" http://mneethiraj-0618-1.openstacklocal:21000/' returned
> 52. 000
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17427) Support Atlas in kerberized environment, submit Service Check as smokeuser
[
https://issues.apache.org/jira/browse/AMBARI-17427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-17427:
Fix Version/s: 2.4.0
> Support Atlas in kerberized environment, submit Service Check as smokeuser
> --
>
> Key: AMBARI-17427
> URL: https://issues.apache.org/jira/browse/AMBARI-17427
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-17427.patch
>
>
> Atlas Service Check should use smokeuser instead of atlas user.
> {code}
> 2016-06-19 10:46:19,971 - Using hadoop conf dir:
> /usr/hdp/current/hadoop-client/conf
> 2016-06-19 10:46:19,979 - Execute['/usr/bin/kinit -kt
> /etc/security/keytabs/smokeuser.headless.keytab ambari-qa-...@example.com']
> {'user': 'atlas'}
> 2016-06-19 10:46:20,198 - Execute['curl --negotiate -u : -b ~/cookiejar.txt
> -c ~/cookiejar.txt -s -o /dev/null -w "%{http_code}"
> http://mneethiraj-0618-1.openstacklocal:21000/'] {'tries': 5, 'user':
> 'atlas', 'try_sleep': 10}
> 2016-06-19 10:46:50,438 - Retrying after 10 seconds. Reason: Execution of
> 'curl --negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null
> -w "%{http_code}" http://mneethiraj-0618-1.openstacklocal:21000/' returned
> 52. 000
> 2016-06-19 10:47:30,610 - Retrying after 10 seconds. Reason: Execution of
> 'curl --negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null
> -w "%{http_code}" http://mneethiraj-0618-1.openstacklocal:21000/' returned
> 52. 000
> 2016-06-19 10:48:10,738 - Retrying after 10 seconds. Reason: Execution of
> 'curl --negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null
> -w "%{http_code}" http://mneethiraj-0618-1.openstacklocal:21000/' returned
> 52. 000
> 2016-06-19 10:48:50,863 - Retrying after 10 seconds. Reason: Execution of
> 'curl --negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null
> -w "%{http_code}" http://mneethiraj-0618-1.openstacklocal:21000/' returned
> 52. 000
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-17428) Falcon client install failed
Dmytro Sen created AMBARI-17428:
---
Summary: Falcon client install failed
Key: AMBARI-17428
URL: https://issues.apache.org/jira/browse/AMBARI-17428
Project: Ambari
Issue Type: Bug
Components: stacks
Affects Versions: 2.4.0
Reporter: Dmytro Sen
Assignee: Dmytro Sen
Priority: Blocker
Fix For: 2.4.0
Falcon client failed and is blocking UI installs :
{code}
"Traceback (most recent call last):\n File
\"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/falcon_client.py\",
line 80, in \nFalconClient().execute()\n File
\"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
line 280, in execute\nmethod(env)\n File
\"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/falcon_client.py\",
line 45, in install\nself.configure(env)\n File
\"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/falcon_client.py\",
line 33, in configure\nfalcon('client', action='config')\n File
\"/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py\", line 89,
in thunk\nreturn fn(*args, **kwargs)\n File
\"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/falcon.py\",
line 84, in falcon\nowner = params.falcon_user)\n File
\"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line
155, in __init__\nself.env.run()\n File
\"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
line 160, in run\nself.run_action(resource, action)\n File
\"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
line 124, in run_action\nprovider_action()\n File
\"/usr/lib/python2.6/site-packages/resource_management/libraries/providers/properties_file.py\",
line 54, in action_create\nmode = self.resource.mode\n File
\"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line
155, in __init__\nself.env.run()\n File
\"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
line 160, in run\nself.run_action(resource, action)\n File
\"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
line 124, in run_action\nprovider_action()\n File
\"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
line 123, in action_create\ncontent = self._get_content()\n File
\"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
line 160, in _get_content\nreturn content()\n File
\"/usr/lib/python2.6/site-packages/resource_management/core/source.py\", line
51, in __call__\nreturn self.get_content()\n File
\"/usr/lib/python2.6/site-packages/resource_management/core/source.py\", line
142, in get_content\nrendered = self.template.render(self.context)\n File
\"/usr/lib/python2.6/site-packages/ambari_jinja2/environment.py\", line 891, in
render\nreturn self.environment.handle_exception(exc_info, True)\n File
\"\", line 2, in top-level template code\n File
\"/usr/lib/python2.6/site-packages/ambari_jinja2/filters.py\", line 176, in
do_dictsort\nreturn sorted(value.items(), key=sort_func)\n File
\"/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py\",
line 73, in __getattr__\nraise Fail(\"Configuration parameter '\" +
self.name + \"' was not found in configurations
dictionary!\")\nresource_management.core.exceptions.Fail: Configuration
parameter 'falcon-client.properties' was not found in configurations
dictionary!",
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17428) Falcon client install failed
[
https://issues.apache.org/jira/browse/AMBARI-17428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen updated AMBARI-17428:
Status: Patch Available (was: Open)
> Falcon client install failed
>
>
> Key: AMBARI-17428
> URL: https://issues.apache.org/jira/browse/AMBARI-17428
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.4.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-17428.patch
>
>
> Falcon client failed and is blocking UI installs :
> {code}
> "Traceback (most recent call last):\n File
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/falcon_client.py\",
> line 80, in \nFalconClient().execute()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
> line 280, in execute\nmethod(env)\n File
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/falcon_client.py\",
> line 45, in install\nself.configure(env)\n File
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/falcon_client.py\",
> line 33, in configure\nfalcon('client', action='config')\n File
> \"/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py\", line
> 89, in thunk\nreturn fn(*args, **kwargs)\n File
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/falcon.py\",
> line 84, in falcon\nowner = params.falcon_user)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line
> 155, in __init__\nself.env.run()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
> line 160, in run\nself.run_action(resource, action)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
> line 124, in run_action\nprovider_action()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/providers/properties_file.py\",
> line 54, in action_create\nmode = self.resource.mode\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line
> 155, in __init__\nself.env.run()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
> line 160, in run\nself.run_action(resource, action)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
> line 124, in run_action\nprovider_action()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
> line 123, in action_create\ncontent = self._get_content()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
> line 160, in _get_content\nreturn content()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/source.py\", line
> 51, in __call__\nreturn self.get_content()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/source.py\", line
> 142, in get_content\nrendered = self.template.render(self.context)\n
> File \"/usr/lib/python2.6/site-packages/ambari_jinja2/environment.py\", line
> 891, in render\nreturn self.environment.handle_exception(exc_info,
> True)\n File \"\", line 2, in top-level template code\n File
> \"/usr/lib/python2.6/site-packages/ambari_jinja2/filters.py\", line 176, in
> do_dictsort\nreturn sorted(value.items(), key=sort_func)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py\",
> line 73, in __getattr__\nraise Fail(\"Configuration parameter '\" +
> self.name + \"' was not found in configurations
> dictionary!\")\nresource_management.core.exceptions.Fail: Configuration
> parameter 'falcon-client.properties' was not found in configurations
> dictionary!",
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17428) Falcon client install failed
[
https://issues.apache.org/jira/browse/AMBARI-17428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen updated AMBARI-17428:
Attachment: AMBARI-17428.patch
> Falcon client install failed
>
>
> Key: AMBARI-17428
> URL: https://issues.apache.org/jira/browse/AMBARI-17428
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.4.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-17428.patch
>
>
> Falcon client failed and is blocking UI installs :
> {code}
> "Traceback (most recent call last):\n File
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/falcon_client.py\",
> line 80, in \nFalconClient().execute()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
> line 280, in execute\nmethod(env)\n File
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/falcon_client.py\",
> line 45, in install\nself.configure(env)\n File
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/falcon_client.py\",
> line 33, in configure\nfalcon('client', action='config')\n File
> \"/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py\", line
> 89, in thunk\nreturn fn(*args, **kwargs)\n File
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/falcon.py\",
> line 84, in falcon\nowner = params.falcon_user)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line
> 155, in __init__\nself.env.run()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
> line 160, in run\nself.run_action(resource, action)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
> line 124, in run_action\nprovider_action()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/providers/properties_file.py\",
> line 54, in action_create\nmode = self.resource.mode\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line
> 155, in __init__\nself.env.run()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
> line 160, in run\nself.run_action(resource, action)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
> line 124, in run_action\nprovider_action()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
> line 123, in action_create\ncontent = self._get_content()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
> line 160, in _get_content\nreturn content()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/source.py\", line
> 51, in __call__\nreturn self.get_content()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/source.py\", line
> 142, in get_content\nrendered = self.template.render(self.context)\n
> File \"/usr/lib/python2.6/site-packages/ambari_jinja2/environment.py\", line
> 891, in render\nreturn self.environment.handle_exception(exc_info,
> True)\n File \"\", line 2, in top-level template code\n File
> \"/usr/lib/python2.6/site-packages/ambari_jinja2/filters.py\", line 176, in
> do_dictsort\nreturn sorted(value.items(), key=sort_func)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py\",
> line 73, in __getattr__\nraise Fail(\"Configuration parameter '\" +
> self.name + \"' was not found in configurations
> dictionary!\")\nresource_management.core.exceptions.Fail: Configuration
> parameter 'falcon-client.properties' was not found in configurations
> dictionary!",
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17428) Falcon client install failed
[
https://issues.apache.org/jira/browse/AMBARI-17428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348268#comment-15348268
]
Hadoop QA commented on AMBARI-17428:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12813083/AMBARI-17428.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/7528//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7528//console
This message is automatically generated.
> Falcon client install failed
>
>
> Key: AMBARI-17428
> URL: https://issues.apache.org/jira/browse/AMBARI-17428
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.4.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-17428.patch
>
>
> Falcon client failed and is blocking UI installs :
> {code}
> "Traceback (most recent call last):\n File
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/falcon_client.py\",
> line 80, in \nFalconClient().execute()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
> line 280, in execute\nmethod(env)\n File
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/falcon_client.py\",
> line 45, in install\nself.configure(env)\n File
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/falcon_client.py\",
> line 33, in configure\nfalcon('client', action='config')\n File
> \"/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py\", line
> 89, in thunk\nreturn fn(*args, **kwargs)\n File
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/falcon.py\",
> line 84, in falcon\nowner = params.falcon_user)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line
> 155, in __init__\nself.env.run()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
> line 160, in run\nself.run_action(resource, action)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
> line 124, in run_action\nprovider_action()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/providers/properties_file.py\",
> line 54, in action_create\nmode = self.resource.mode\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line
> 155, in __init__\nself.env.run()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
> line 160, in run\nself.run_action(resource, action)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
> line 124, in run_action\nprovider_action()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
> line 123, in action_create\ncontent = self._get_content()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
> line 160, in _get_content\nreturn content()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/source.py\", line
> 51, in __call__\nreturn self.get_content()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/source.py\", line
> 142, in get_content\nrendered = self.template.render(self.context)\n
> File \"/usr/lib/python2.6/site-packages/ambari_jinja2/environment.py\", line
> 891, in render\nreturn self.environment.handle_exception(exc_info,
> True)\n File \"\", line 2, in top-level template code\n File
> \"/usr/lib/python2.6/site-packages/ambari_jinja2/filters.py\", line 176, in
> do_dictsort\nreturn sorted(value.items(), key=sort_func)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py\",
> line 73, in __getattr__\nraise Fail(\"Configuration parameter '\" +
>
[jira] [Commented] (AMBARI-17428) Falcon client install failed
[
https://issues.apache.org/jira/browse/AMBARI-17428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348269#comment-15348269
]
Hadoop QA commented on AMBARI-17428:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12813083/AMBARI-17428.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7529//console
This message is automatically generated.
> Falcon client install failed
>
>
> Key: AMBARI-17428
> URL: https://issues.apache.org/jira/browse/AMBARI-17428
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.4.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-17428.patch
>
>
> Falcon client failed and is blocking UI installs :
> {code}
> "Traceback (most recent call last):\n File
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/falcon_client.py\",
> line 80, in \nFalconClient().execute()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
> line 280, in execute\nmethod(env)\n File
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/falcon_client.py\",
> line 45, in install\nself.configure(env)\n File
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/falcon_client.py\",
> line 33, in configure\nfalcon('client', action='config')\n File
> \"/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py\", line
> 89, in thunk\nreturn fn(*args, **kwargs)\n File
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/falcon.py\",
> line 84, in falcon\nowner = params.falcon_user)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line
> 155, in __init__\nself.env.run()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
> line 160, in run\nself.run_action(resource, action)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
> line 124, in run_action\nprovider_action()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/providers/properties_file.py\",
> line 54, in action_create\nmode = self.resource.mode\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line
> 155, in __init__\nself.env.run()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
> line 160, in run\nself.run_action(resource, action)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
> line 124, in run_action\nprovider_action()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
> line 123, in action_create\ncontent = self._get_content()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
> line 160, in _get_content\nreturn content()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/source.py\", line
> 51, in __call__\nreturn self.get_content()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/source.py\", line
> 142, in get_content\nrendered = self.template.render(self.context)\n
> File \"/usr/lib/python2.6/site-packages/ambari_jinja2/environment.py\", line
> 891, in render\nreturn self.environment.handle_exception(exc_info,
> True)\n File \"\", line 2, in top-level template code\n File
> \"/usr/lib/python2.6/site-packages/ambari_jinja2/filters.py\", line 176, in
> do_dictsort\nreturn sorted(value.items(), key=sort_func)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py\",
> line 73, in __getattr__\nraise Fail(\"Configuration parameter '\" +
> self.name + \"' was not found in configurations
> dictionary!\")\nresource_management.core.exceptions.Fail: Configuration
> parameter 'falcon-client.properties' was not found in configurations
> dictionary!",
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-17429) Log extension details modal in host details page appends content of previously viewed log modal content
Antonenko Alexander created AMBARI-17429: Summary: Log extension details modal in host details page appends content of previously viewed log modal content Key: AMBARI-17429 URL: https://issues.apache.org/jira/browse/AMBARI-17429 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Antonenko Alexander Assignee: Antonenko Alexander Fix For: 2.4.0 Log extension details modal in host details page appends content of previously viewed log modal content Step 1 : Login to Ambari UI Step 2 : Navigate to Host Details Page >Logs Tab Step 3 : Click on one of the components logs link in extension field link (E.g Kafka_server.log on a host abc) Step 4: verify the logs displayed and Close the modal window Step 5: Open another link for a different component Step 6 : Verify the contents. The content should only display the contents of corresponding component, but displays the content of modal window opened in Step 4 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17429) Log extension details modal in host details page appends content of previously viewed log modal content
[ https://issues.apache.org/jira/browse/AMBARI-17429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-17429: - Status: Patch Available (was: Open) > Log extension details modal in host details page appends content of > previously viewed log modal content > --- > > Key: AMBARI-17429 > URL: https://issues.apache.org/jira/browse/AMBARI-17429 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.4.0 > > Attachments: AMBARI-17429.patch > > > Log extension details modal in host details page appends content of > previously viewed log modal content > Step 1 : Login to Ambari UI > Step 2 : Navigate to Host Details Page >Logs Tab > Step 3 : Click on one of the components logs link in extension field link > (E.g Kafka_server.log on a host abc) > Step 4: verify the logs displayed and Close the modal window > Step 5: Open another link for a different component > Step 6 : Verify the contents. The content should only display the contents of > corresponding component, but displays the content of modal window opened in > Step 4 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17427) Support Atlas in kerberized environment, submit Service Check as smokeuser
[
https://issues.apache.org/jira/browse/AMBARI-17427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-17427:
Resolution: Fixed
Status: Resolved (was: Patch Available)
committed
To https://git-wip-us.apache.org/repos/asf/ambari.git
87f7fec..8349118 branch-2.4 -> branch-2.4
c98597f..d4b4cc9 trunk -> trunk
> Support Atlas in kerberized environment, submit Service Check as smokeuser
> --
>
> Key: AMBARI-17427
> URL: https://issues.apache.org/jira/browse/AMBARI-17427
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-17427.patch
>
>
> Atlas Service Check should use smokeuser instead of atlas user.
> {code}
> 2016-06-19 10:46:19,971 - Using hadoop conf dir:
> /usr/hdp/current/hadoop-client/conf
> 2016-06-19 10:46:19,979 - Execute['/usr/bin/kinit -kt
> /etc/security/keytabs/smokeuser.headless.keytab ambari-qa-...@example.com']
> {'user': 'atlas'}
> 2016-06-19 10:46:20,198 - Execute['curl --negotiate -u : -b ~/cookiejar.txt
> -c ~/cookiejar.txt -s -o /dev/null -w "%{http_code}"
> http://mneethiraj-0618-1.openstacklocal:21000/'] {'tries': 5, 'user':
> 'atlas', 'try_sleep': 10}
> 2016-06-19 10:46:50,438 - Retrying after 10 seconds. Reason: Execution of
> 'curl --negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null
> -w "%{http_code}" http://mneethiraj-0618-1.openstacklocal:21000/' returned
> 52. 000
> 2016-06-19 10:47:30,610 - Retrying after 10 seconds. Reason: Execution of
> 'curl --negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null
> -w "%{http_code}" http://mneethiraj-0618-1.openstacklocal:21000/' returned
> 52. 000
> 2016-06-19 10:48:10,738 - Retrying after 10 seconds. Reason: Execution of
> 'curl --negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null
> -w "%{http_code}" http://mneethiraj-0618-1.openstacklocal:21000/' returned
> 52. 000
> 2016-06-19 10:48:50,863 - Retrying after 10 seconds. Reason: Execution of
> 'curl --negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null
> -w "%{http_code}" http://mneethiraj-0618-1.openstacklocal:21000/' returned
> 52. 000
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17429) Log extension details modal in host details page appends content of previously viewed log modal content
[ https://issues.apache.org/jira/browse/AMBARI-17429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-17429: - Attachment: AMBARI-17429.patch > Log extension details modal in host details page appends content of > previously viewed log modal content > --- > > Key: AMBARI-17429 > URL: https://issues.apache.org/jira/browse/AMBARI-17429 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.4.0 > > Attachments: AMBARI-17429.patch > > > Log extension details modal in host details page appends content of > previously viewed log modal content > Step 1 : Login to Ambari UI > Step 2 : Navigate to Host Details Page >Logs Tab > Step 3 : Click on one of the components logs link in extension field link > (E.g Kafka_server.log on a host abc) > Step 4: verify the logs displayed and Close the modal window > Step 5: Open another link for a different component > Step 6 : Verify the contents. The content should only display the contents of > corresponding component, but displays the content of modal window opened in > Step 4 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17427) Support Atlas in kerberized environment, submit Service Check as smokeuser
[
https://issues.apache.org/jira/browse/AMBARI-17427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348298#comment-15348298
]
Hadoop QA commented on AMBARI-17427:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12813082/AMBARI-17427.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7530//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7530//console
This message is automatically generated.
> Support Atlas in kerberized environment, submit Service Check as smokeuser
> --
>
> Key: AMBARI-17427
> URL: https://issues.apache.org/jira/browse/AMBARI-17427
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-17427.patch
>
>
> Atlas Service Check should use smokeuser instead of atlas user.
> {code}
> 2016-06-19 10:46:19,971 - Using hadoop conf dir:
> /usr/hdp/current/hadoop-client/conf
> 2016-06-19 10:46:19,979 - Execute['/usr/bin/kinit -kt
> /etc/security/keytabs/smokeuser.headless.keytab ambari-qa-...@example.com']
> {'user': 'atlas'}
> 2016-06-19 10:46:20,198 - Execute['curl --negotiate -u : -b ~/cookiejar.txt
> -c ~/cookiejar.txt -s -o /dev/null -w "%{http_code}"
> http://mneethiraj-0618-1.openstacklocal:21000/'] {'tries': 5, 'user':
> 'atlas', 'try_sleep': 10}
> 2016-06-19 10:46:50,438 - Retrying after 10 seconds. Reason: Execution of
> 'curl --negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null
> -w "%{http_code}" http://mneethiraj-0618-1.openstacklocal:21000/' returned
> 52. 000
> 2016-06-19 10:47:30,610 - Retrying after 10 seconds. Reason: Execution of
> 'curl --negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null
> -w "%{http_code}" http://mneethiraj-0618-1.openstacklocal:21000/' returned
> 52. 000
> 2016-06-19 10:48:10,738 - Retrying after 10 seconds. Reason: Execution of
> 'curl --negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null
> -w "%{http_code}" http://mneethiraj-0618-1.openstacklocal:21000/' returned
> 52. 000
> 2016-06-19 10:48:50,863 - Retrying after 10 seconds. Reason: Execution of
> 'curl --negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null
> -w "%{http_code}" http://mneethiraj-0618-1.openstacklocal:21000/' returned
> 52. 000
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17426) Ambari server setup failed on debian with postgres local db
[ https://issues.apache.org/jira/browse/AMBARI-17426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-17426: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.4 > Ambari server setup failed on debian with postgres local db > --- > > Key: AMBARI-17426 > URL: https://issues.apache.org/jira/browse/AMBARI-17426 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.4.0 > > Attachments: AMBARI-17426.patch > > > We have tests where we cleanup existing cluster and reinstall Ambari again - > perform install, setup and start Ambari server. Starting up AMbari server is > failing with the below erro > > > > Using python /usr/bin/python > Starting ambari-server > ERROR: Exiting with exit code 1. > REASON: Unable to detect a system user for Ambari Server. > - If this is a new setup, then run the "ambari-server setup" command to > create the user > - If this is an upgrade of an existing setup, run the "ambari-server > upgrade" command. > Refer to the Ambari documentation for more information on setup and > upgrade. > > Please see the logs [here](http://qelog.hortonworks.com/log/nat-os-d7-luls- > ambari-blueprints-3/test-logs/ambari-blueprints/artifacts/screenshots/com.hw.a > mbari.ui.tests.heavyweights.TestSingleNodeClustersViaBlueprint/testA_PrepareCl > uster/_23_0_54_11_Exceptions_appeared_during_install/test_logs/test_TestSingle > NodeClustersViaBlueprint_debug.log). We can see that at the beginning Ambari > server is up and running fine. BUt after cleanup and reinstall server is not > coming up. Could you please help take a look. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17426) Ambari server setup failed on debian with postgres local db
[
https://issues.apache.org/jira/browse/AMBARI-17426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348324#comment-15348324
]
Hadoop QA commented on AMBARI-17426:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12813073/AMBARI-17426.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7531//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7531//console
This message is automatically generated.
> Ambari server setup failed on debian with postgres local db
> ---
>
> Key: AMBARI-17426
> URL: https://issues.apache.org/jira/browse/AMBARI-17426
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-17426.patch
>
>
> We have tests where we cleanup existing cluster and reinstall Ambari again -
> perform install, setup and start Ambari server. Starting up AMbari server is
> failing with the below erro
>
>
>
> Using python /usr/bin/python
> Starting ambari-server
> ERROR: Exiting with exit code 1.
> REASON: Unable to detect a system user for Ambari Server.
> - If this is a new setup, then run the "ambari-server setup" command to
> create the user
> - If this is an upgrade of an existing setup, run the "ambari-server
> upgrade" command.
> Refer to the Ambari documentation for more information on setup and
> upgrade.
>
> Please see the logs [here](http://qelog.hortonworks.com/log/nat-os-d7-luls-
> ambari-blueprints-3/test-logs/ambari-blueprints/artifacts/screenshots/com.hw.a
> mbari.ui.tests.heavyweights.TestSingleNodeClustersViaBlueprint/testA_PrepareCl
> uster/_23_0_54_11_Exceptions_appeared_during_install/test_logs/test_TestSingle
> NodeClustersViaBlueprint_debug.log). We can see that at the beginning Ambari
> server is up and running fine. BUt after cleanup and reinstall server is not
> coming up. Could you please help take a look.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17428) Falcon client install failed
[
https://issues.apache.org/jira/browse/AMBARI-17428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen updated AMBARI-17428:
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk and branch-2.4
> Falcon client install failed
>
>
> Key: AMBARI-17428
> URL: https://issues.apache.org/jira/browse/AMBARI-17428
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.4.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-17428.patch
>
>
> Falcon client failed and is blocking UI installs :
> {code}
> "Traceback (most recent call last):\n File
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/falcon_client.py\",
> line 80, in \nFalconClient().execute()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
> line 280, in execute\nmethod(env)\n File
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/falcon_client.py\",
> line 45, in install\nself.configure(env)\n File
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/falcon_client.py\",
> line 33, in configure\nfalcon('client', action='config')\n File
> \"/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py\", line
> 89, in thunk\nreturn fn(*args, **kwargs)\n File
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/falcon.py\",
> line 84, in falcon\nowner = params.falcon_user)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line
> 155, in __init__\nself.env.run()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
> line 160, in run\nself.run_action(resource, action)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
> line 124, in run_action\nprovider_action()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/providers/properties_file.py\",
> line 54, in action_create\nmode = self.resource.mode\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line
> 155, in __init__\nself.env.run()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
> line 160, in run\nself.run_action(resource, action)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
> line 124, in run_action\nprovider_action()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
> line 123, in action_create\ncontent = self._get_content()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
> line 160, in _get_content\nreturn content()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/source.py\", line
> 51, in __call__\nreturn self.get_content()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/source.py\", line
> 142, in get_content\nrendered = self.template.render(self.context)\n
> File \"/usr/lib/python2.6/site-packages/ambari_jinja2/environment.py\", line
> 891, in render\nreturn self.environment.handle_exception(exc_info,
> True)\n File \"\", line 2, in top-level template code\n File
> \"/usr/lib/python2.6/site-packages/ambari_jinja2/filters.py\", line 176, in
> do_dictsort\nreturn sorted(value.items(), key=sort_func)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py\",
> line 73, in __getattr__\nraise Fail(\"Configuration parameter '\" +
> self.name + \"' was not found in configurations
> dictionary!\")\nresource_management.core.exceptions.Fail: Configuration
> parameter 'falcon-client.properties' was not found in configurations
> dictionary!",
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17425) [Hive view] hiveserver service check fails for LDAP configured hive view
[
https://issues.apache.org/jira/browse/AMBARI-17425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348345#comment-15348345
]
Hadoop QA commented on AMBARI-17425:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12813066/AMBARI-17425_branch-2.4.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
contrib/views/hive
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7532//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7532//console
This message is automatically generated.
> [Hive view] hiveserver service check fails for LDAP configured hive view
>
>
> Key: AMBARI-17425
> URL: https://issues.apache.org/jira/browse/AMBARI-17425
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.4.0
>Reporter: Pallav Kulshreshtha
>Assignee: Pallav Kulshreshtha
> Fix For: 2.4.0
>
> Attachments: AMBARI-17425_branch-2.4.patch
>
>
> hiveserver service check fails for LDAP configured hive view.
> There should be some flow to enter the user LDAP credentials and progress
> further.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17368) Quick link to remove browser URL params.
[ https://issues.apache.org/jira/browse/AMBARI-17368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348361#comment-15348361 ] Hudson commented on AMBARI-17368: - FAILURE: Integrated in Ambari-trunk-Commit #5153 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5153/]) AMBARI-17368. Log Search: Quick link to remove browser URL params. (oleewere: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=c98597fd1de21cd547c9fbdc809f136d398ce5db]) * ambari-logsearch/ambari-logsearch-portal/src/main/webapp/scripts/utils/Utils.js * ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/manager/UserConfigMgr.java * ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/util/SolrUtil.java * ambari-logsearch/ambari-logsearch-portal/src/main/webapp/templates/common/Header_tmpl.html * ambari-logsearch/ambari-logsearch-portal/src/main/webapp/scripts/views/common/TableLayout.js * ambari-logsearch/ambari-logsearch-portal/src/main/webapp/scripts/views/common/Header.js > Quick link to remove browser URL params. > > > Key: AMBARI-17368 > URL: https://issues.apache.org/jira/browse/AMBARI-17368 > Project: Ambari > Issue Type: Improvement > Components: ambari-logsearch >Affects Versions: 2.4.0 >Reporter: Dharmesh Makwana >Assignee: Dharmesh Makwana > Fix For: 2.4.0 > > > Now user can remove browser url params which are locked through quick link. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17424) Add missing components to LogSearch (part II)
[ https://issues.apache.org/jira/browse/AMBARI-17424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348362#comment-15348362 ] Miklos Gergely commented on AMBARI-17424: - Adding logs for Log Search - Solr HBase - Phoenix Server Flume - Flume Handler Zeppelin - Zeppelin > Add missing components to LogSearch (part II) > - > > Key: AMBARI-17424 > URL: https://issues.apache.org/jira/browse/AMBARI-17424 > Project: Ambari > Issue Type: Technical task > Components: ambari-logsearch, ambari-server >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Miklos Gergely > Fix For: 2.4.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (AMBARI-17424) Add missing components to LogSearch (part II)
[ https://issues.apache.org/jira/browse/AMBARI-17424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-17424: Comment: was deleted (was: Adding logs for Log Search - Solr HBase - Phoenix Server Flume - Flume Handler Zeppelin - Zeppelin) > Add missing components to LogSearch (part II) > - > > Key: AMBARI-17424 > URL: https://issues.apache.org/jira/browse/AMBARI-17424 > Project: Ambari > Issue Type: Technical task > Components: ambari-logsearch, ambari-server >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Miklos Gergely > Fix For: 2.4.0 > > > Adding logs for > Log Search - Solr > HBase - Phoenix Server > Flume - Flume Handler > Zeppelin - Zeppelin -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17424) Add missing components to LogSearch (part II)
[ https://issues.apache.org/jira/browse/AMBARI-17424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-17424: Description: Adding logs for Log Search - Solr HBase - Phoenix Server Flume - Flume Handler Zeppelin - Zeppelin > Add missing components to LogSearch (part II) > - > > Key: AMBARI-17424 > URL: https://issues.apache.org/jira/browse/AMBARI-17424 > Project: Ambari > Issue Type: Technical task > Components: ambari-logsearch, ambari-server >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Miklos Gergely > Fix For: 2.4.0 > > > Adding logs for > Log Search - Solr > HBase - Phoenix Server > Flume - Flume Handler > Zeppelin - Zeppelin -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16756) Update code for Ranger Service to use PID file for status and stop call
[
https://issues.apache.org/jira/browse/AMBARI-16756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348380#comment-15348380
]
Hadoop QA commented on AMBARI-16756:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12813064/AMBARI-16756.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/7533//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7533//console
This message is automatically generated.
> Update code for Ranger Service to use PID file for status and stop call
> ---
>
> Key: AMBARI-16756
> URL: https://issues.apache.org/jira/browse/AMBARI-16756
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-16756.patch
>
>
> After getting PID file generated from Ranger code. Need to update ambari
> ranger code for stop and status call.
> cc [~gautamborad]/[~mehul]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17424) Add missing components to LogSearch (part II)
[ https://issues.apache.org/jira/browse/AMBARI-17424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-17424: Attachment: AMBARI-17424.patch > Add missing components to LogSearch (part II) > - > > Key: AMBARI-17424 > URL: https://issues.apache.org/jira/browse/AMBARI-17424 > Project: Ambari > Issue Type: Technical task > Components: ambari-logsearch, ambari-server >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Miklos Gergely > Fix For: 2.4.0 > > Attachments: AMBARI-17424.patch > > > Adding logs for > Log Search - Solr > HBase - Phoenix Server > Flume - Flume Handler > Zeppelin - Zeppelin -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17424) Add missing components to LogSearch (part II)
[ https://issues.apache.org/jira/browse/AMBARI-17424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-17424: Status: Patch Available (was: In Progress) > Add missing components to LogSearch (part II) > - > > Key: AMBARI-17424 > URL: https://issues.apache.org/jira/browse/AMBARI-17424 > Project: Ambari > Issue Type: Technical task > Components: ambari-logsearch, ambari-server >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Miklos Gergely > Fix For: 2.4.0 > > Attachments: AMBARI-17424.patch > > > Adding logs for > Log Search - Solr > HBase - Phoenix Server > Flume - Flume Handler > Zeppelin - Zeppelin -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17410) Incorrect error message for invalid category in Host Combo Search Box
[
https://issues.apache.org/jira/browse/AMBARI-17410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348402#comment-15348402
]
Hadoop QA commented on AMBARI-17410:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12813062/AMBARI-17410.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/7534//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7534//console
This message is automatically generated.
> Incorrect error message for invalid category in Host Combo Search Box
> -
>
> Key: AMBARI-17410
> URL: https://issues.apache.org/jira/browse/AMBARI-17410
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: trunk
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-17410.patch, ErrorMessage.jpg,
> ErrorMessageWithFix.jpg
>
>
> 1. In the host combo box, if an invalid category is entered, an error is
> displayed
> [object Object] is not a valid category.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17419) Disabling the auto-start for ambari-server and ambari-agent doesn't work on systemd
[
https://issues.apache.org/jira/browse/AMBARI-17419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348403#comment-15348403
]
Hadoop QA commented on AMBARI-17419:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12813018/AMBARI-17419.v1.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/7535//console
This message is automatically generated.
> Disabling the auto-start for ambari-server and ambari-agent doesn't work on
> systemd
> ---
>
> Key: AMBARI-17419
> URL: https://issues.apache.org/jira/browse/AMBARI-17419
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-server
>Reporter: Sebastian Toader
>Assignee: Sebastian Toader
> Fix For: 2.4.0
>
> Attachments: AMBARI-17419.v1.patch
>
>
> Trying do disable auto-start for ambari-server by executing {{update-rc.d
> ambari-server disable}} is failing with {{update-rc.d: error: ambari-server
> Default-Start contains no runlevels, aborting.}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17419) Disabling the auto-start for ambari-server and ambari-agent doesn't work on systemd
[
https://issues.apache.org/jira/browse/AMBARI-17419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Toader updated AMBARI-17419:
--
Attachment: AMBARI-17419.trunk.v1.patch
> Disabling the auto-start for ambari-server and ambari-agent doesn't work on
> systemd
> ---
>
> Key: AMBARI-17419
> URL: https://issues.apache.org/jira/browse/AMBARI-17419
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-server
>Reporter: Sebastian Toader
>Assignee: Sebastian Toader
> Fix For: 2.4.0
>
> Attachments: AMBARI-17419.trunk.v1.patch, AMBARI-17419.v1.patch
>
>
> Trying do disable auto-start for ambari-server by executing {{update-rc.d
> ambari-server disable}} is failing with {{update-rc.d: error: ambari-server
> Default-Start contains no runlevels, aborting.}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17419) Disabling the auto-start for ambari-server and ambari-agent doesn't work on systemd
[
https://issues.apache.org/jira/browse/AMBARI-17419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Toader updated AMBARI-17419:
--
Attachment: (was: AMBARI-17419.v1.patch)
> Disabling the auto-start for ambari-server and ambari-agent doesn't work on
> systemd
> ---
>
> Key: AMBARI-17419
> URL: https://issues.apache.org/jira/browse/AMBARI-17419
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-server
>Reporter: Sebastian Toader
>Assignee: Sebastian Toader
> Fix For: 2.4.0
>
> Attachments: AMBARI-17419.trunk.v1.patch
>
>
> Trying do disable auto-start for ambari-server by executing {{update-rc.d
> ambari-server disable}} is failing with {{update-rc.d: error: ambari-server
> Default-Start contains no runlevels, aborting.}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17383) User names should be case insensitive
[ https://issues.apache.org/jira/browse/AMBARI-17383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-17383: --- Resolution: Fixed Status: Resolved (was: Patch Available) > User names should be case insensitive > - > > Key: AMBARI-17383 > URL: https://issues.apache.org/jira/browse/AMBARI-17383 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram >Priority: Critical > Fix For: 2.4.0 > > Attachments: rb49119 (1).patch > > > User names should be case insensitive. The following usernames are the same: > VIEWUSER > viewUser > viewuser > Before adding a new user, a case sensitive search is made. Change this to > case insensitive. Additionally, store user names in the DB in lower case. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17424) Add missing components to LogSearch (part II)
[ https://issues.apache.org/jira/browse/AMBARI-17424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-17424: Attachment: AMBARI-17424.patch > Add missing components to LogSearch (part II) > - > > Key: AMBARI-17424 > URL: https://issues.apache.org/jira/browse/AMBARI-17424 > Project: Ambari > Issue Type: Technical task > Components: ambari-logsearch, ambari-server >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Miklos Gergely > Fix For: 2.4.0 > > Attachments: AMBARI-17424.patch > > > Adding logs for > Log Search - Solr > HBase - Phoenix Server > Flume - Flume Handler > Zeppelin - Zeppelin -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17424) Add missing components to LogSearch (part II)
[ https://issues.apache.org/jira/browse/AMBARI-17424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-17424: Attachment: (was: AMBARI-17424.patch) > Add missing components to LogSearch (part II) > - > > Key: AMBARI-17424 > URL: https://issues.apache.org/jira/browse/AMBARI-17424 > Project: Ambari > Issue Type: Technical task > Components: ambari-logsearch, ambari-server >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Miklos Gergely > Fix For: 2.4.0 > > Attachments: AMBARI-17424.patch > > > Adding logs for > Log Search - Solr > HBase - Phoenix Server > Flume - Flume Handler > Zeppelin - Zeppelin -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17186) Tez View: Improve proxy logging
[ https://issues.apache.org/jira/browse/AMBARI-17186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348420#comment-15348420 ] Hitesh Shah commented on AMBARI-17186: -- +1 > Tez View: Improve proxy logging > --- > > Key: AMBARI-17186 > URL: https://issues.apache.org/jira/browse/AMBARI-17186 > Project: Ambari > Issue Type: Bug >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17186.1.patch, AMBARI-17186.2.patch, > AMBARI-17186.3.patch, AMBARI-17186.4.patch, AMBARI-17186.5.patch, > AMBARI-17186.6.patch, AMBARI-17186.7.patch > > > More log messages would help us to debug EARs faster. > # Add error log when configuration fetch fails. > # Add debug log when request proxying / redirection succeed > # Add error log when request proxying / redirection fails > With effect from AMBARI-14084, each view would have separate log file. > - For Tez view that is /var/log/ambari-server/tez-view/tez-view.log. > - Debug log would be logged only when the debug mode is enabled. (Set > log4j.logger.org.apache.ambari.view.tez=DEBUG,tezView in > view.log4j.properties for the same) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17429) Log extension details modal in host details page appends content of previously viewed log modal content
[
https://issues.apache.org/jira/browse/AMBARI-17429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348424#comment-15348424
]
Hadoop QA commented on AMBARI-17429:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12813090/AMBARI-17429.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/7536//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7536//console
This message is automatically generated.
> Log extension details modal in host details page appends content of
> previously viewed log modal content
> ---
>
> Key: AMBARI-17429
> URL: https://issues.apache.org/jira/browse/AMBARI-17429
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.4.0
>
> Attachments: AMBARI-17429.patch
>
>
> Log extension details modal in host details page appends content of
> previously viewed log modal content
> Step 1 : Login to Ambari UI
> Step 2 : Navigate to Host Details Page >Logs Tab
> Step 3 : Click on one of the components logs link in extension field link
> (E.g Kafka_server.log on a host abc)
> Step 4: verify the logs displayed and Close the modal window
> Step 5: Open another link for a different component
> Step 6 : Verify the contents. The content should only display the contents of
> corresponding component, but displays the content of modal window opened in
> Step 4
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17186) Tez View: Improve proxy logging
[ https://issues.apache.org/jira/browse/AMBARI-17186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated AMBARI-17186: - Resolution: Fixed Status: Resolved (was: Patch Available) Thanks [~Sreenath]. Committed to trunk and branch 2.4 > Tez View: Improve proxy logging > --- > > Key: AMBARI-17186 > URL: https://issues.apache.org/jira/browse/AMBARI-17186 > Project: Ambari > Issue Type: Bug >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17186.1.patch, AMBARI-17186.2.patch, > AMBARI-17186.3.patch, AMBARI-17186.4.patch, AMBARI-17186.5.patch, > AMBARI-17186.6.patch, AMBARI-17186.7.patch > > > More log messages would help us to debug EARs faster. > # Add error log when configuration fetch fails. > # Add debug log when request proxying / redirection succeed > # Add error log when request proxying / redirection fails > With effect from AMBARI-14084, each view would have separate log file. > - For Tez view that is /var/log/ambari-server/tez-view/tez-view.log. > - Debug log would be logged only when the debug mode is enabled. (Set > log4j.logger.org.apache.ambari.view.tez=DEBUG,tezView in > view.log4j.properties for the same) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17427) Support Atlas in kerberized environment, submit Service Check as smokeuser
[
https://issues.apache.org/jira/browse/AMBARI-17427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348458#comment-15348458
]
Hudson commented on AMBARI-17427:
-
FAILURE: Integrated in Ambari-trunk-Commit #5154 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5154/])
AMBARI-17427. Support Atlas in kerberized environment, submit Service
(dlysnichenko:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=d4b4cc90a51cc7e085f30bf3a89c964a3421c7f9])
*
ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/package/scripts/service_check.py
* ambari-server/src/test/python/stacks/2.3/ATLAS/test_service_check.py
> Support Atlas in kerberized environment, submit Service Check as smokeuser
> --
>
> Key: AMBARI-17427
> URL: https://issues.apache.org/jira/browse/AMBARI-17427
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-17427.patch
>
>
> Atlas Service Check should use smokeuser instead of atlas user.
> {code}
> 2016-06-19 10:46:19,971 - Using hadoop conf dir:
> /usr/hdp/current/hadoop-client/conf
> 2016-06-19 10:46:19,979 - Execute['/usr/bin/kinit -kt
> /etc/security/keytabs/smokeuser.headless.keytab ambari-qa-...@example.com']
> {'user': 'atlas'}
> 2016-06-19 10:46:20,198 - Execute['curl --negotiate -u : -b ~/cookiejar.txt
> -c ~/cookiejar.txt -s -o /dev/null -w "%{http_code}"
> http://mneethiraj-0618-1.openstacklocal:21000/'] {'tries': 5, 'user':
> 'atlas', 'try_sleep': 10}
> 2016-06-19 10:46:50,438 - Retrying after 10 seconds. Reason: Execution of
> 'curl --negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null
> -w "%{http_code}" http://mneethiraj-0618-1.openstacklocal:21000/' returned
> 52. 000
> 2016-06-19 10:47:30,610 - Retrying after 10 seconds. Reason: Execution of
> 'curl --negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null
> -w "%{http_code}" http://mneethiraj-0618-1.openstacklocal:21000/' returned
> 52. 000
> 2016-06-19 10:48:10,738 - Retrying after 10 seconds. Reason: Execution of
> 'curl --negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null
> -w "%{http_code}" http://mneethiraj-0618-1.openstacklocal:21000/' returned
> 52. 000
> 2016-06-19 10:48:50,863 - Retrying after 10 seconds. Reason: Execution of
> 'curl --negotiate -u : -b ~/cookiejar.txt -c ~/cookiejar.txt -s -o /dev/null
> -w "%{http_code}" http://mneethiraj-0618-1.openstacklocal:21000/' returned
> 52. 000
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17426) Ambari server setup failed on debian with postgres local db
[ https://issues.apache.org/jira/browse/AMBARI-17426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348459#comment-15348459 ] Hudson commented on AMBARI-17426: - FAILURE: Integrated in Ambari-trunk-Commit #5154 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5154/]) AMBARI-17426. Ambari server setup failed on debian with postgres local (aonishuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=5efdce84d244e5031934d822355c5303a3e391e2]) * ambari-server/src/main/python/ambari_server/dbConfiguration_linux.py > Ambari server setup failed on debian with postgres local db > --- > > Key: AMBARI-17426 > URL: https://issues.apache.org/jira/browse/AMBARI-17426 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.4.0 > > Attachments: AMBARI-17426.patch > > > We have tests where we cleanup existing cluster and reinstall Ambari again - > perform install, setup and start Ambari server. Starting up AMbari server is > failing with the below erro > > > > Using python /usr/bin/python > Starting ambari-server > ERROR: Exiting with exit code 1. > REASON: Unable to detect a system user for Ambari Server. > - If this is a new setup, then run the "ambari-server setup" command to > create the user > - If this is an upgrade of an existing setup, run the "ambari-server > upgrade" command. > Refer to the Ambari documentation for more information on setup and > upgrade. > > Please see the logs [here](http://qelog.hortonworks.com/log/nat-os-d7-luls- > ambari-blueprints-3/test-logs/ambari-blueprints/artifacts/screenshots/com.hw.a > mbari.ui.tests.heavyweights.TestSingleNodeClustersViaBlueprint/testA_PrepareCl > uster/_23_0_54_11_Exceptions_appeared_during_install/test_logs/test_TestSingle > NodeClustersViaBlueprint_debug.log). We can see that at the beginning Ambari > server is up and running fine. BUt after cleanup and reinstall server is not > coming up. Could you please help take a look. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17424) Add missing components to LogSearch (part II)
[
https://issues.apache.org/jira/browse/AMBARI-17424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348462#comment-15348462
]
Hadoop QA commented on AMBARI-17424:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12813108/AMBARI-17424.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 test build failed in
ambari-logsearch/ambari-logsearch-portal
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7537//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7537//console
This message is automatically generated.
> Add missing components to LogSearch (part II)
> -
>
> Key: AMBARI-17424
> URL: https://issues.apache.org/jira/browse/AMBARI-17424
> Project: Ambari
> Issue Type: Technical task
> Components: ambari-logsearch, ambari-server
>Affects Versions: 2.4.0
>Reporter: Olivér Szabó
>Assignee: Miklos Gergely
> Fix For: 2.4.0
>
> Attachments: AMBARI-17424.patch
>
>
> Adding logs for
> Log Search - Solr
> HBase - Phoenix Server
> Flume - Flume Handler
> Zeppelin - Zeppelin
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17428) Falcon client install failed
[
https://issues.apache.org/jira/browse/AMBARI-17428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348457#comment-15348457
]
Hudson commented on AMBARI-17428:
-
FAILURE: Integrated in Ambari-trunk-Commit #5154 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5154/])
AMBARI-17428 Falcon client install failed (dsen) (dsen:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=fe97cfd52c0e10bcf5e2af3cbf38d5ad3a67bd80])
*
ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/package/scripts/falcon.py
*
ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/configuration/falcon-client.properties.xml
*
ambari-server/src/main/resources/stacks/HDP/2.1.GlusterFS/services/FALCON/metainfo.xml
* ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/metainfo.xml
*
ambari-server/src/main/resources/stacks/HDP/2.1.GlusterFS/services/FALCON/configuration/falcon-client.properties.xml
*
ambari-server/src/main/resources/stacks/HDP/2.1.GlusterFS/services/FALCON/package/scripts/params.py
> Falcon client install failed
>
>
> Key: AMBARI-17428
> URL: https://issues.apache.org/jira/browse/AMBARI-17428
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.4.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-17428.patch
>
>
> Falcon client failed and is blocking UI installs :
> {code}
> "Traceback (most recent call last):\n File
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/falcon_client.py\",
> line 80, in \nFalconClient().execute()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
> line 280, in execute\nmethod(env)\n File
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/falcon_client.py\",
> line 45, in install\nself.configure(env)\n File
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/falcon_client.py\",
> line 33, in configure\nfalcon('client', action='config')\n File
> \"/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py\", line
> 89, in thunk\nreturn fn(*args, **kwargs)\n File
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/falcon.py\",
> line 84, in falcon\nowner = params.falcon_user)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line
> 155, in __init__\nself.env.run()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
> line 160, in run\nself.run_action(resource, action)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
> line 124, in run_action\nprovider_action()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/providers/properties_file.py\",
> line 54, in action_create\nmode = self.resource.mode\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line
> 155, in __init__\nself.env.run()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
> line 160, in run\nself.run_action(resource, action)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
> line 124, in run_action\nprovider_action()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
> line 123, in action_create\ncontent = self._get_content()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
> line 160, in _get_content\nreturn content()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/source.py\", line
> 51, in __call__\nreturn self.get_content()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/source.py\", line
> 142, in get_content\nrendered = self.template.render(self.context)\n
> File \"/usr/lib/python2.6/site-packages/ambari_jinja2/environment.py\", line
> 891, in render\nreturn self.environment.handle_exception(exc_info,
> True)\n File \"\", line 2, in top-level template code\n File
> \"/usr/lib/python2.6/site-packages/ambari_jinja2/filters.py\", line 176, in
> do_dictsort\nreturn sorted(value.items(), key=sort_func)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py\",
> line 73, in __getattr__\nraise Fail(\"Configuration parameter '\" +
> self.name + \"' was not found in configurations
> dictionary!\")\nresource_management.core.exceptions.Fail: Configuration
> parameter 'falcon-client.properties' was not found in configurations
> dictionary!",
> {code}
--
This mes
[jira] [Commented] (AMBARI-17419) Disabling the auto-start for ambari-server and ambari-agent doesn't work on systemd
[
https://issues.apache.org/jira/browse/AMBARI-17419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348489#comment-15348489
]
Hadoop QA commented on AMBARI-17419:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12813104/AMBARI-17419.trunk.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:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7538//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7538//console
This message is automatically generated.
> Disabling the auto-start for ambari-server and ambari-agent doesn't work on
> systemd
> ---
>
> Key: AMBARI-17419
> URL: https://issues.apache.org/jira/browse/AMBARI-17419
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-server
>Reporter: Sebastian Toader
>Assignee: Sebastian Toader
> Fix For: 2.4.0
>
> Attachments: AMBARI-17419.trunk.v1.patch
>
>
> Trying do disable auto-start for ambari-server by executing {{update-rc.d
> ambari-server disable}} is failing with {{update-rc.d: error: ambari-server
> Default-Start contains no runlevels, aborting.}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17428) Falcon client install failed
[
https://issues.apache.org/jira/browse/AMBARI-17428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348505#comment-15348505
]
Dmytro Sen commented on AMBARI-17428:
-
Test failure isn't related to this patch
> Falcon client install failed
>
>
> Key: AMBARI-17428
> URL: https://issues.apache.org/jira/browse/AMBARI-17428
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.4.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-17428.patch
>
>
> Falcon client failed and is blocking UI installs :
> {code}
> "Traceback (most recent call last):\n File
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/falcon_client.py\",
> line 80, in \nFalconClient().execute()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
> line 280, in execute\nmethod(env)\n File
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/falcon_client.py\",
> line 45, in install\nself.configure(env)\n File
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/falcon_client.py\",
> line 33, in configure\nfalcon('client', action='config')\n File
> \"/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py\", line
> 89, in thunk\nreturn fn(*args, **kwargs)\n File
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/falcon.py\",
> line 84, in falcon\nowner = params.falcon_user)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line
> 155, in __init__\nself.env.run()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
> line 160, in run\nself.run_action(resource, action)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
> line 124, in run_action\nprovider_action()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/providers/properties_file.py\",
> line 54, in action_create\nmode = self.resource.mode\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line
> 155, in __init__\nself.env.run()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
> line 160, in run\nself.run_action(resource, action)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\",
> line 124, in run_action\nprovider_action()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
> line 123, in action_create\ncontent = self._get_content()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
> line 160, in _get_content\nreturn content()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/source.py\", line
> 51, in __call__\nreturn self.get_content()\n File
> \"/usr/lib/python2.6/site-packages/resource_management/core/source.py\", line
> 142, in get_content\nrendered = self.template.render(self.context)\n
> File \"/usr/lib/python2.6/site-packages/ambari_jinja2/environment.py\", line
> 891, in render\nreturn self.environment.handle_exception(exc_info,
> True)\n File \"\", line 2, in top-level template code\n File
> \"/usr/lib/python2.6/site-packages/ambari_jinja2/filters.py\", line 176, in
> do_dictsort\nreturn sorted(value.items(), key=sort_func)\n File
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py\",
> line 73, in __getattr__\nraise Fail(\"Configuration parameter '\" +
> self.name + \"' was not found in configurations
> dictionary!\")\nresource_management.core.exceptions.Fail: Configuration
> parameter 'falcon-client.properties' was not found in configurations
> dictionary!",
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17429) Log extension details modal in host details page appends content of previously viewed log modal content
[ https://issues.apache.org/jira/browse/AMBARI-17429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348526#comment-15348526 ] Aleksandr Kovalenko commented on AMBARI-17429: -- +1 for the patch > Log extension details modal in host details page appends content of > previously viewed log modal content > --- > > Key: AMBARI-17429 > URL: https://issues.apache.org/jira/browse/AMBARI-17429 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.4.0 > > Attachments: AMBARI-17429.patch > > > Log extension details modal in host details page appends content of > previously viewed log modal content > Step 1 : Login to Ambari UI > Step 2 : Navigate to Host Details Page >Logs Tab > Step 3 : Click on one of the components logs link in extension field link > (E.g Kafka_server.log on a host abc) > Step 4: verify the logs displayed and Close the modal window > Step 5: Open another link for a different component > Step 6 : Verify the contents. The content should only display the contents of > corresponding component, but displays the content of modal window opened in > Step 4 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17430) Fix serviceconfig NPE in db consistency checker
Vitaly Brodetskyi created AMBARI-17430:
--
Summary: Fix serviceconfig NPE in db consistency checker
Key: AMBARI-17430
URL: https://issues.apache.org/jira/browse/AMBARI-17430
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.4.0
Reporter: Vitaly Brodetskyi
Assignee: Vitaly Brodetskyi
Priority: Critical
Fix For: 2.4.0
During testting discovered this issue:
{code}
2016-06-23 18:07:46,467 ERROR - Unexpected error, database check failed
java.lang.NullPointerException
at
org.apache.ambari.server.checks.DatabaseConsistencyCheckHelper.checkServiceConfigs(DatabaseConsistencyCheckHelper.java:514)
at
org.apache.ambari.server.checks.DatabaseConsistencyChecker.main(DatabaseConsistencyChecker.java:115)
{code}
It should be fixed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17430) Fix serviceconfig NPE in db consistency checker
[
https://issues.apache.org/jira/browse/AMBARI-17430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-17430:
---
Status: Patch Available (was: Open)
> Fix serviceconfig NPE in db consistency checker
> ---
>
> Key: AMBARI-17430
> URL: https://issues.apache.org/jira/browse/AMBARI-17430
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17430.patch
>
>
> During testting discovered this issue:
> {code}
> 2016-06-23 18:07:46,467 ERROR - Unexpected error, database check failed
> java.lang.NullPointerException
> at
> org.apache.ambari.server.checks.DatabaseConsistencyCheckHelper.checkServiceConfigs(DatabaseConsistencyCheckHelper.java:514)
> at
> org.apache.ambari.server.checks.DatabaseConsistencyChecker.main(DatabaseConsistencyChecker.java:115)
> {code}
> It should be fixed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17430) Fix serviceconfig NPE in db consistency checker
[
https://issues.apache.org/jira/browse/AMBARI-17430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-17430:
---
Attachment: AMBARI-17430.patch
> Fix serviceconfig NPE in db consistency checker
> ---
>
> Key: AMBARI-17430
> URL: https://issues.apache.org/jira/browse/AMBARI-17430
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17430.patch
>
>
> During testting discovered this issue:
> {code}
> 2016-06-23 18:07:46,467 ERROR - Unexpected error, database check failed
> java.lang.NullPointerException
> at
> org.apache.ambari.server.checks.DatabaseConsistencyCheckHelper.checkServiceConfigs(DatabaseConsistencyCheckHelper.java:514)
> at
> org.apache.ambari.server.checks.DatabaseConsistencyChecker.main(DatabaseConsistencyChecker.java:115)
> {code}
> It should be fixed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17429) Log extension details modal in host details page appends content of previously viewed log modal content
[ https://issues.apache.org/jira/browse/AMBARI-17429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-17429: - Resolution: Fixed Status: Resolved (was: Patch Available) committed to trunk and brunch-2.4 > Log extension details modal in host details page appends content of > previously viewed log modal content > --- > > Key: AMBARI-17429 > URL: https://issues.apache.org/jira/browse/AMBARI-17429 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.4.0 > > Attachments: AMBARI-17429.patch > > > Log extension details modal in host details page appends content of > previously viewed log modal content > Step 1 : Login to Ambari UI > Step 2 : Navigate to Host Details Page >Logs Tab > Step 3 : Click on one of the components logs link in extension field link > (E.g Kafka_server.log on a host abc) > Step 4: verify the logs displayed and Close the modal window > Step 5: Open another link for a different component > Step 6 : Verify the contents. The content should only display the contents of > corresponding component, but displays the content of modal window opened in > Step 4 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17431) Ambari Is Initializing the Metastore Using the Wrong schematool Binary on HDP 2.5
Jonathan Hurley created AMBARI-17431:
Summary: Ambari Is Initializing the Metastore Using the Wrong
schematool Binary on HDP 2.5
Key: AMBARI-17431
URL: https://issues.apache.org/jira/browse/AMBARI-17431
Project: Ambari
Issue Type: Bug
Reporter: Jonathan Hurley
Priority: Blocker
On HDP 2.5 installations, the {{hive-metastore}} component's {{schematool}} is
being used to create the schema. This is incorrect in that the {{hive2}}
{{schematool}} should be used since it's compatible with Hive LLAP and
{{HiveServer2}}.
{noformat}
mysql> select * from VERSION;
+++---+
| VER_ID | SCHEMA_VERSION | VERSION_COMMENT |
+++---+
| 1 | 1.2.1000 | Hive release version 1.2.1000 |
+++---+
1 row in set (0.00 sec)
{noformat}
{noformat}
ERROR [pool-5-thread-198]: metastore.RetryingHMSHandler
(RetryingHMSHandler.java:invokeInternal(195)) - MetaException(message:Unable to
update transaction database
com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown column
'tc_operation_type' in 'field list'
at sun.reflect.GeneratedConstructorAccessor65.newInstance(Unknown
Source)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at com.mysql.jdbc.Util.handleNewInstance(Util.java:377)
at com.mysql.jdbc.Util.getInstance(Util.java:360)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:978)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3887)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3823)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2435)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2582)
at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2526)
at com.mysql.jdbc.StatementImpl.executeUpdate(StatementImpl.java:1618)
at com.mysql.jdbc.StatementImpl.executeUpdate(StatementImpl.java:1549)
at
com.jolbox.bonecp.StatementHandle.executeUpdate(StatementHandle.java:497)
at
org.apache.hadoop.hive.metastore.txn.TxnHandler.enqueueLockWithRetry(TxnHandler.java:938)
at
org.apache.hadoop.hive.metastore.txn.TxnHandler.lock(TxnHandler.java:795)
at
org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.lock(HiveMetaStore.java:5666)
at sun.reflect.GeneratedMethodAccessor43.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.apache.hadoop.hive.metastore.RetryingHMSHandler.invokeInternal(RetryingHMSHandler.java:139)
at
org.apache.hadoop.hive.metastore.RetryingHMSHandler.invoke(RetryingHMSHandler.java:97)
at com.sun.proxy.$Proxy12.lock(Unknown Source)
at
org.apache.hadoop.hive.metastore.api.ThriftHiveMetastore$Processor$lock.getResult(ThriftHiveMetastore.java:11759)
at
org.apache.hadoop.hive.metastore.api.ThriftHiveMetastore$Processor$lock.getResult(ThriftHiveMetastore.java:11743)
at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:39)
at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39)
at
org.apache.hadoop.hive.thrift.HadoopThriftAuthBridge$Server$TUGIAssumingProcessor$1.run(HadoopThriftAuthBridge.java:551)
at
org.apache.hadoop.hive.thrift.HadoopThriftAuthBridge$Server$TUGIAssumingProcessor$1.run(HadoopThriftAuthBridge.java:546)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:422)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1724)
at
org.apache.hadoop.hive.thrift.HadoopThriftAuthBridge$Server$TUGIAssumingProcessor.process(HadoopThriftAuthBridge.java:546)
at
org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:286)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
)
at
org.apache.hadoop.hive.metastore.txn.TxnHandler.enqueueLockWithRetry(TxnHandler.java:994)
at
org.apache.hadoop.hive.metastore.txn.TxnHandler.lock(TxnHandler.java:795)
at
org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.lock(HiveMetaStore.java:5666)
at sun.reflect.GeneratedMethodAccessor43.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[jira] [Resolved] (AMBARI-17423) Add missing components to LogSearch (part I)
[ https://issues.apache.org/jira/browse/AMBARI-17423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-17423. --- Resolution: Fixed > Add missing components to LogSearch (part I) > > > Key: AMBARI-17423 > URL: https://issues.apache.org/jira/browse/AMBARI-17423 > Project: Ambari > Issue Type: Technical task > Components: ambari-logsearch, ambari-server >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 2.4.0 > > Attachments: AMBARI-17423.patch > > > Contain the following components: > SPARK > SPARK2 > METRICS_GRAFANA > NFS_GATEWAY > SmartSense > WEBHCAT_SERVER > LIVY -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17423) Add missing components to LogSearch (part I)
[
https://issues.apache.org/jira/browse/AMBARI-17423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348635#comment-15348635
]
Olivér Szabó commented on AMBARI-17423:
---
{code:java}
commit 128f77e2f12483890064f515ea7691037b520952
Author: oleewere
Date: Fri Jun 24 17:50:27 2016 +0200
AMBARI-17423. Add missing components to LogSearch Part1 (oleewere)
{code}
comitted to branch-2.4:
{code:java}
commit d370a4467bdebf43d3f32721eae9955d390081c7
Author: oleewere
Date: Fri Jun 24 17:50:27 2016 +0200
AMBARI-17423. Add missing components to LogSearch Part1 (oleewere)
{code}
> Add missing components to LogSearch (part I)
>
>
> Key: AMBARI-17423
> URL: https://issues.apache.org/jira/browse/AMBARI-17423
> Project: Ambari
> Issue Type: Technical task
> Components: ambari-logsearch, ambari-server
>Affects Versions: 2.4.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 2.4.0
>
> Attachments: AMBARI-17423.patch
>
>
> Contain the following components:
> SPARK
> SPARK2
> METRICS_GRAFANA
> NFS_GATEWAY
> SmartSense
> WEBHCAT_SERVER
> LIVY
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17424) Add missing components to LogSearch (part II)
[
https://issues.apache.org/jira/browse/AMBARI-17424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348636#comment-15348636
]
Olivér Szabó commented on AMBARI-17424:
---
{code:java}
commit 4207e60186c42215ead3283285b814af9fe37067
Author: Miklos Gergely
Date: Fri Jun 24 17:18:18 2016 +0200
AMBARI-17424. Add missing components to LogSearch Part 2 (Miklos Gergely
via oleewere)
{code}
comitted to branch-2.4:
{code:java}
Author: Miklos Gergely
Date: Fri Jun 24 17:18:18 2016 +0200
AMBARI-17424. Add missing components to LogSearch Part 2 (Miklos Gergely
via oleewere)
{code}
> Add missing components to LogSearch (part II)
> -
>
> Key: AMBARI-17424
> URL: https://issues.apache.org/jira/browse/AMBARI-17424
> Project: Ambari
> Issue Type: Technical task
> Components: ambari-logsearch, ambari-server
>Affects Versions: 2.4.0
>Reporter: Olivér Szabó
>Assignee: Miklos Gergely
> Fix For: 2.4.0
>
> Attachments: AMBARI-17424.patch
>
>
> Adding logs for
> Log Search - Solr
> HBase - Phoenix Server
> Flume - Flume Handler
> Zeppelin - Zeppelin
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17424) Add missing components to LogSearch (part II)
[ https://issues.apache.org/jira/browse/AMBARI-17424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-17424: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Add missing components to LogSearch (part II) > - > > Key: AMBARI-17424 > URL: https://issues.apache.org/jira/browse/AMBARI-17424 > Project: Ambari > Issue Type: Technical task > Components: ambari-logsearch, ambari-server >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Miklos Gergely > Fix For: 2.4.0 > > Attachments: AMBARI-17424.patch > > > Adding logs for > Log Search - Solr > HBase - Phoenix Server > Flume - Flume Handler > Zeppelin - Zeppelin -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-17422) Add missing components to LogSearch
[ https://issues.apache.org/jira/browse/AMBARI-17422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-17422. --- Resolution: Fixed > Add missing components to LogSearch > --- > > Key: AMBARI-17422 > URL: https://issues.apache.org/jira/browse/AMBARI-17422 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, ambari-server >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 2.4.0 > > > Add missing service grok patters to Logsearch service -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17430) Fix serviceconfig NPE in db consistency checker
[
https://issues.apache.org/jira/browse/AMBARI-17430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348673#comment-15348673
]
Hudson commented on AMBARI-17430:
-
FAILURE: Integrated in Ambari-trunk-Commit #5157 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5157/])
AMBARI-17430. Fix serviceconfig NPE in db consistency (vbrodetskyi:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=3ae844f0a9439cb29945e16c8f9963d4261e7c40])
*
ambari-server/src/main/java/org/apache/ambari/server/checks/DatabaseConsistencyCheckHelper.java
> Fix serviceconfig NPE in db consistency checker
> ---
>
> Key: AMBARI-17430
> URL: https://issues.apache.org/jira/browse/AMBARI-17430
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17430.patch
>
>
> During testting discovered this issue:
> {code}
> 2016-06-23 18:07:46,467 ERROR - Unexpected error, database check failed
> java.lang.NullPointerException
> at
> org.apache.ambari.server.checks.DatabaseConsistencyCheckHelper.checkServiceConfigs(DatabaseConsistencyCheckHelper.java:514)
> at
> org.apache.ambari.server.checks.DatabaseConsistencyChecker.main(DatabaseConsistencyChecker.java:115)
> {code}
> It should be fixed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17387) Changing HDP repo URL does not leads to sending written URL to ambari-server while registering new HDP version
[ https://issues.apache.org/jira/browse/AMBARI-17387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-17387: Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.4 36d1f8659c5c14d65c623c982aabbf63066afc1c > Changing HDP repo URL does not leads to sending written URL to ambari-server > while registering new HDP version > -- > > Key: AMBARI-17387 > URL: https://issues.apache.org/jira/browse/AMBARI-17387 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: 2.4.0 > > Attachments: AMBARI-17387.v0.patch > > > STR: > # Deploy cluster HDP 2.3 > # Register HDP 2.5.0.0 latest (e.g 2.5.0.0-664) > # Try to register 2.5.0.0, but with other URL (e.g for HDP 2.5.0.0-569) > Result: internal server error " Base url > http://s3.amazonaws.com/dev.hortonworks.com/HDP/centos6/2.x/BUILDS/2.5.0.0-664 > is already defined for another repository version" > But in this case we were trying to register > http://s3.amazonaws.com/dev.hortonworks.com/HDP/centos6/2.x/BUILDS/2.5.0.0-569 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17430) Fix serviceconfig NPE in db consistency checker
[
https://issues.apache.org/jira/browse/AMBARI-17430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348710#comment-15348710
]
Hadoop QA commented on AMBARI-17430:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12813113/AMBARI-17430.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/7539//console
This message is automatically generated.
> Fix serviceconfig NPE in db consistency checker
> ---
>
> Key: AMBARI-17430
> URL: https://issues.apache.org/jira/browse/AMBARI-17430
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17430.patch
>
>
> During testting discovered this issue:
> {code}
> 2016-06-23 18:07:46,467 ERROR - Unexpected error, database check failed
> java.lang.NullPointerException
> at
> org.apache.ambari.server.checks.DatabaseConsistencyCheckHelper.checkServiceConfigs(DatabaseConsistencyCheckHelper.java:514)
> at
> org.apache.ambari.server.checks.DatabaseConsistencyChecker.main(DatabaseConsistencyChecker.java:115)
> {code}
> It should be fixed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-17432) Zeppelin does not force Livy to install
Yesha Vora created AMBARI-17432: --- Summary: Zeppelin does not force Livy to install Key: AMBARI-17432 URL: https://issues.apache.org/jira/browse/AMBARI-17432 Project: Ambari Issue Type: Bug Affects Versions: 2.4.0 Reporter: Yesha Vora Scenario: * Install Spark without Livy Server * Install Zeppelin When spark hasn't installed Livy server, Zeppelin does not force to install Livy server. While installing, it skips the "Assigns slave and client" (step3). The zeppelin installs only zeppelin notebook. Zeppelin should enforce Livy server to install and start if Spark does not have Livy server installed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17433) Manage Config groups stops working after creating new group.
Antonenko Alexander created AMBARI-17433:
Summary: Manage Config groups stops working after creating new
group.
Key: AMBARI-17433
URL: https://issues.apache.org/jira/browse/AMBARI-17433
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.4.0
Reporter: Antonenko Alexander
Assignee: Antonenko Alexander
Fix For: 2.4.0
STR:
* Proceed to Customize Services page on Install Wizard or Add Service Wizard
* Create override via "+" icon near config
* Choose *Create New Configuration group* and click on "Ok"
* Click on Manage Config Groups
* Select new group, js error thrown
{noformat}
Uncaught TypeError: Cannot read property 'toWickMap' of undefined
{noformat}
* Close popup
* Click on Manage Config Groups, js error thrown
{noformat}
Uncaught TypeError: Cannot read property 'toWickMap' of undefined
{noformat}
Popup doesn't open.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
