[jira] [Commented] (AMBARI-21921) A print_warning_msg() in serverConfiguration.py has too few arguments.
[
https://issues.apache.org/jira/browse/AMBARI-21921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16174801#comment-16174801
]
Hadoop QA commented on AMBARI-21921:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12888289/AMBARI-21921.1.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/12310//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12310//console
This message is automatically generated.
> A print_warning_msg() in serverConfiguration.py has too few arguments.
> --
>
> Key: AMBARI-21921
> URL: https://issues.apache.org/jira/browse/AMBARI-21921
> Project: Ambari
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
>Priority: Minor
> Attachments: AMBARI-21921.0.patch, AMBARI-21921.1.patch
>
>
> {{update_database_name_property}} function which is in
> {{serverConfiguration.py}} uses {{print_warning_msg}} to show a warning when
> {{check_database_name_property}} throws {{FatalException}}.
> {code}
> except FatalException:
> properties = get_ambari_properties()
> if properties == -1:
> err = "Error getting ambari properties"
> raise FatalException(-1, err)
> print_warning_msg("{0} property isn't set in {1} . Setting it to default
> value - {3}".format(JD
> BC_DATABASE_NAME_PROPERTY, AMBARI_PROPERTIES_FILE,
> configDefaults.DEFAULT_DB_NAME))
> properties.process_pair(JDBC_DATABASE_NAME_PROPERTY,
> configDefaults.DEFAULT_DB_NAME)
> conf_file = find_properties_file()
> {code}
> The argument should be use {code}{0}, {1}, {2}{code}, not {code}{0}, {1},
> {3}{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22017) stack advisor recommends all components on single host for HDP-2.6 Ambari trunk build
[
https://issues.apache.org/jira/browse/AMBARI-22017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16174798#comment-16174798
]
Hadoop QA commented on AMBARI-22017:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12888292/AMBARI-22017_2.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/12309//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12309//console
This message is automatically generated.
> stack advisor recommends all components on single host for HDP-2.6 Ambari
> trunk build
> -
>
> Key: AMBARI-22017
> URL: https://issues.apache.org/jira/browse/AMBARI-22017
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: trunk, 3.0.0
>
> Attachments: AMBARI-22017_2.patch, AMBARI-22017.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22017) stack advisor recommends all components on single host for HDP-2.6 Ambari trunk build
[
https://issues.apache.org/jira/browse/AMBARI-22017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16174795#comment-16174795
]
Hadoop QA commented on AMBARI-22017:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12888292/AMBARI-22017_2.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 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 core tests{color}. The test build failed in
[ambari-server|https://builds.apache.org/job/Ambari-trunk-test-patch/12307//artifact/patch-work/testrun_ambari-server.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12307//console
This message is automatically generated.
> stack advisor recommends all components on single host for HDP-2.6 Ambari
> trunk build
> -
>
> Key: AMBARI-22017
> URL: https://issues.apache.org/jira/browse/AMBARI-22017
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: trunk, 3.0.0
>
> Attachments: AMBARI-22017_2.patch, AMBARI-22017.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22023) Upgrade dialog style issues
[ https://issues.apache.org/jira/browse/AMBARI-22023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-22023: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Upgrade dialog style issues > --- > > Key: AMBARI-22023 > URL: https://issues.apache.org/jira/browse/AMBARI-22023 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.0 > > Attachments: 2.png, AMBARI-22023.patch > > > Upgrade dialog should look like this: > !2.png|thumbnail! > # Use placeholder text while we wait for the upgrade to start > # Move the pause button > # Fix alignment > # Use a well for “Now Running..” -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22023) Upgrade dialog style issues
[ https://issues.apache.org/jira/browse/AMBARI-22023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16174782#comment-16174782 ] Andrii Tkach commented on AMBARI-22023: --- committed to branch-2.6 > Upgrade dialog style issues > --- > > Key: AMBARI-22023 > URL: https://issues.apache.org/jira/browse/AMBARI-22023 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.0 > > Attachments: 2.png, AMBARI-22023.patch > > > Upgrade dialog should look like this: > !2.png|thumbnail! > # Use placeholder text while we wait for the upgrade to start > # Move the pause button > # Fix alignment > # Use a well for “Now Running..” -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22022) NullPointerException in ActionScheduler when using DEPENDENCY_ORDERED execution
[
https://issues.apache.org/jira/browse/AMBARI-22022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16174780#comment-16174780
]
Sandor Magyari commented on AMBARI-22022:
-
Patch committed to trunk:
{code}
commit 3e5f60ab9d30761df08923c4e56dd518fc71d271
Author: Sandor Magyari
Date: Thu Sep 21 14:35:51 2017 +0200
AMBARI-22022. NullPointerException in ActionScheduler when using
DEPENDENCY_ORDERED execution (magyari_sandor)
{code}
> NullPointerException in ActionScheduler when using DEPENDENCY_ORDERED
> execution
> ---
>
> Key: AMBARI-22022
> URL: https://issues.apache.org/jira/browse/AMBARI-22022
> Project: Ambari
> Issue Type: Bug
> Components: ambari-sever
>Affects Versions: 3.0.0
>Reporter: Sandor Magyari
>Assignee: Sandor Magyari
> Fix For: 3.0.0
>
> Attachments: AMBARI-22022.patch
>
>
> NullPointerException may occur in ActionScheduler when using
> DEPENDENCY_ORDERED execution.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22022) NullPointerException in ActionScheduler when using DEPENDENCY_ORDERED execution
[ https://issues.apache.org/jira/browse/AMBARI-22022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Magyari updated AMBARI-22022: Resolution: Fixed Status: Resolved (was: Patch Available) > NullPointerException in ActionScheduler when using DEPENDENCY_ORDERED > execution > --- > > Key: AMBARI-22022 > URL: https://issues.apache.org/jira/browse/AMBARI-22022 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: 3.0.0 >Reporter: Sandor Magyari >Assignee: Sandor Magyari > Fix For: 3.0.0 > > Attachments: AMBARI-22022.patch > > > NullPointerException may occur in ActionScheduler when using > DEPENDENCY_ORDERED execution. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22023) Upgrade dialog style issues
[ https://issues.apache.org/jira/browse/AMBARI-22023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-22023: -- Description: Upgrade dialog should look like this: !2.png|thumbnail! # Use placeholder text while we wait for the upgrade to start # Move the pause button # Fix alignment # Use a well for “Now Running..” was: Upgrade dialog: !1.png|thumbnail! should look like this: !2.png|thumbnail! # Use placeholder text while we wait for the upgrade to start # Move the pause button # Fix alignment # Use a well for “Now Running..” > Upgrade dialog style issues > --- > > Key: AMBARI-22023 > URL: https://issues.apache.org/jira/browse/AMBARI-22023 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.0 > > Attachments: 2.png, AMBARI-22023.patch > > > Upgrade dialog should look like this: > !2.png|thumbnail! > # Use placeholder text while we wait for the upgrade to start > # Move the pause button > # Fix alignment > # Use a well for “Now Running..” -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22023) Upgrade dialog style issues
[ https://issues.apache.org/jira/browse/AMBARI-22023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-22023: -- Attachment: (was: 1.png) > Upgrade dialog style issues > --- > > Key: AMBARI-22023 > URL: https://issues.apache.org/jira/browse/AMBARI-22023 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.0 > > Attachments: 2.png, AMBARI-22023.patch > > > Upgrade dialog: > !1.png|thumbnail! > should look like this: > !2.png|thumbnail! > # Use placeholder text while we wait for the upgrade to start > # Move the pause button > # Fix alignment > # Use a well for “Now Running..” -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22023) Upgrade dialog style issues
[ https://issues.apache.org/jira/browse/AMBARI-22023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16174774#comment-16174774 ] Aleksandr Kovalenko commented on AMBARI-22023: -- +1 for the patch > Upgrade dialog style issues > --- > > Key: AMBARI-22023 > URL: https://issues.apache.org/jira/browse/AMBARI-22023 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.0 > > Attachments: 2.png, AMBARI-22023.patch > > > Upgrade dialog should look like this: > !2.png|thumbnail! > # Use placeholder text while we wait for the upgrade to start > # Move the pause button > # Fix alignment > # Use a well for “Now Running..” -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22023) Upgrade dialog style issues
[ https://issues.apache.org/jira/browse/AMBARI-22023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-22023: -- Attachment: AMBARI-22023.patch > Upgrade dialog style issues > --- > > Key: AMBARI-22023 > URL: https://issues.apache.org/jira/browse/AMBARI-22023 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.0 > > Attachments: 1.png, 2.png, AMBARI-22023.patch > > > Upgrade dialog: > !1.png|thumbnail! > should look like this: > !2.png|thumbnail! > # Use placeholder text while we wait for the upgrade to start > # Move the pause button > # Fix alignment > # Use a well for “Now Running..” -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22023) Upgrade dialog style issues
[ https://issues.apache.org/jira/browse/AMBARI-22023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-22023: -- Status: Patch Available (was: Open) > Upgrade dialog style issues > --- > > Key: AMBARI-22023 > URL: https://issues.apache.org/jira/browse/AMBARI-22023 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.0 > > Attachments: 1.png, 2.png, AMBARI-22023.patch > > > Upgrade dialog: > !1.png|thumbnail! > should look like this: > !2.png|thumbnail! > # Use placeholder text while we wait for the upgrade to start > # Move the pause button > # Fix alignment > # Use a well for “Now Running..” -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22023) Upgrade dialog style issues
[ https://issues.apache.org/jira/browse/AMBARI-22023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16174765#comment-16174765 ] Andrii Tkach commented on AMBARI-22023: --- 30496 passing (29s) 157 pending > Upgrade dialog style issues > --- > > Key: AMBARI-22023 > URL: https://issues.apache.org/jira/browse/AMBARI-22023 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.0 > > Attachments: 1.png, 2.png, AMBARI-22023.patch > > > Upgrade dialog: > !1.png|thumbnail! > should look like this: > !2.png|thumbnail! > # Use placeholder text while we wait for the upgrade to start > # Move the pause button > # Fix alignment > # Use a well for “Now Running..” -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22023) Upgrade dialog style issues
[ https://issues.apache.org/jira/browse/AMBARI-22023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-22023: -- Attachment: (was: AMBARI-22023.patch) > Upgrade dialog style issues > --- > > Key: AMBARI-22023 > URL: https://issues.apache.org/jira/browse/AMBARI-22023 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.0 > > Attachments: 1.png, 2.png > > > Upgrade dialog: > !1.png|thumbnail! > should look like this: > !2.png|thumbnail! > # Use placeholder text while we wait for the upgrade to start > # Move the pause button > # Fix alignment > # Use a well for “Now Running..” -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22023) Upgrade dialog style issues
[ https://issues.apache.org/jira/browse/AMBARI-22023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-22023: -- Attachment: AMBARI-22023.patch > Upgrade dialog style issues > --- > > Key: AMBARI-22023 > URL: https://issues.apache.org/jira/browse/AMBARI-22023 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.0 > > Attachments: 1.png, 2.png, AMBARI-22023.patch > > > Upgrade dialog: > !1.png|thumbnail! > should look like this: > !2.png|thumbnail! > # Use placeholder text while we wait for the upgrade to start > # Move the pause button > # Fix alignment > # Use a well for “Now Running..” -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22017) stack advisor recommends all components on single host for HDP-2.6 Ambari trunk build
[ https://issues.apache.org/jira/browse/AMBARI-22017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-22017: Attachment: AMBARI-22017_2.patch > stack advisor recommends all components on single host for HDP-2.6 Ambari > trunk build > - > > Key: AMBARI-22017 > URL: https://issues.apache.org/jira/browse/AMBARI-22017 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Blocker > Fix For: trunk, 3.0.0 > > Attachments: AMBARI-22017_2.patch, AMBARI-22017.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22023) Upgrade dialog style issues
[ https://issues.apache.org/jira/browse/AMBARI-22023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-22023: -- Attachment: 2.png 1.png > Upgrade dialog style issues > --- > > Key: AMBARI-22023 > URL: https://issues.apache.org/jira/browse/AMBARI-22023 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.0 > > Attachments: 1.png, 2.png > > > Upgrade dialog: > !1.png|thumbnail! > should look like this: > !2.png|thumbnail! > # Use placeholder text while we wait for the upgrade to start > # Move the pause button > # Fix alignment > # Use a well for “Now Running..” -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22023) Upgrade dialog style issues
[ https://issues.apache.org/jira/browse/AMBARI-22023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-22023: -- Attachment: (was: 2.png) > Upgrade dialog style issues > --- > > Key: AMBARI-22023 > URL: https://issues.apache.org/jira/browse/AMBARI-22023 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.0 > > > Upgrade dialog: > !1.png|thumbnail! > should look like this: > !2.png|thumbnail! > # Use placeholder text while we wait for the upgrade to start > # Move the pause button > # Fix alignment > # Use a well for “Now Running..” -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21921) A print_warning_msg() in serverConfiguration.py has too few arguments.
[
https://issues.apache.org/jira/browse/AMBARI-21921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-21921:
-
Attachment: AMBARI-21921.1.patch
> A print_warning_msg() in serverConfiguration.py has too few arguments.
> --
>
> Key: AMBARI-21921
> URL: https://issues.apache.org/jira/browse/AMBARI-21921
> Project: Ambari
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
>Priority: Minor
> Attachments: AMBARI-21921.0.patch, AMBARI-21921.1.patch
>
>
> {{update_database_name_property}} function which is in
> {{serverConfiguration.py}} uses {{print_warning_msg}} to show a warning when
> {{check_database_name_property}} throws {{FatalException}}.
> {code}
> except FatalException:
> properties = get_ambari_properties()
> if properties == -1:
> err = "Error getting ambari properties"
> raise FatalException(-1, err)
> print_warning_msg("{0} property isn't set in {1} . Setting it to default
> value - {3}".format(JD
> BC_DATABASE_NAME_PROPERTY, AMBARI_PROPERTIES_FILE,
> configDefaults.DEFAULT_DB_NAME))
> properties.process_pair(JDBC_DATABASE_NAME_PROPERTY,
> configDefaults.DEFAULT_DB_NAME)
> conf_file = find_properties_file()
> {code}
> The argument should be use {code}{0}, {1}, {2}{code}, not {code}{0}, {1},
> {3}{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22023) Upgrade dialog style issues
[ https://issues.apache.org/jira/browse/AMBARI-22023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-22023: -- Attachment: 1.png 2.png > Upgrade dialog style issues > --- > > Key: AMBARI-22023 > URL: https://issues.apache.org/jira/browse/AMBARI-22023 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.0 > > > Upgrade dialog: > !1.png|thumbnail! > should look like this: > !2.png|thumbnail! > # Use placeholder text while we wait for the upgrade to start > # Move the pause button > # Fix alignment > # Use a well for “Now Running..” -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22023) Upgrade dialog style issues
[ https://issues.apache.org/jira/browse/AMBARI-22023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-22023: -- Attachment: (was: 1.png) > Upgrade dialog style issues > --- > > Key: AMBARI-22023 > URL: https://issues.apache.org/jira/browse/AMBARI-22023 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.0 > > > Upgrade dialog: > !1.png|thumbnail! > should look like this: > !2.png|thumbnail! > # Use placeholder text while we wait for the upgrade to start > # Move the pause button > # Fix alignment > # Use a well for “Now Running..” -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22023) Upgrade dialog style issues
Andrii Tkach created AMBARI-22023: - Summary: Upgrade dialog style issues Key: AMBARI-22023 URL: https://issues.apache.org/jira/browse/AMBARI-22023 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.6.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Priority: Critical Fix For: 2.6.0 Upgrade dialog: !1.png|thumbnail! should look like this: !2.png|thumbnail! # Use placeholder text while we wait for the upgrade to start # Move the pause button # Fix alignment # Use a well for “Now Running..” -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22011) Could not copy tez tarball to HDFS during prepare upgrade (EU)
[
https://issues.apache.org/jira/browse/AMBARI-22011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16174707#comment-16174707
]
Hudson commented on AMBARI-22011:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #262 (See
[https://builds.apache.org/job/Ambari-branch-2.6/262/])
AMBARI-22011. Could not copy tez tarball to HDFS during prepare upgrade (ncole:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=59b25468b24b4a08f3d5eeb9e1fdb02e874540c6])
* (edit)
ambari-server/src/main/resources/stacks/BigInsights/4.2.5/services/OOZIE/package/scripts/oozie.py
* (edit)
ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie.py
* (edit)
ambari-common/src/main/python/resource_management/libraries/functions/copy_tarball.py
> Could not copy tez tarball to HDFS during prepare upgrade (EU)
> --
>
> Key: AMBARI-22011
> URL: https://issues.apache.org/jira/browse/AMBARI-22011
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-22011.patch
>
>
> {code}
> 2017-09-19 11:42:05,103 - Task. Type: EXECUTE, Script: scripts/pre_upgrade.py
> - Function: prepare
> 2017-09-19 11:42:05,738 - Skipping stack-select on RU_EXECUTE_TASKS because
> it does not exist in the stack-select package structure.
> 2017-09-19 11:42:05,739 - Skipping stack-select on RU_EXECUTE_TASKS because
> it does not exist in the stack-select package structure.
> 2017-09-19 11:42:05,739 - An upgrade/downgrade for HDP-2.5.3.0-37 is in
> progress, determining which hadoop conf dir to use.
> 2017-09-19 11:42:05,740 - Skipping stack-select on RU_EXECUTE_TASKS because
> it does not exist in the stack-select package structure.
> 2017-09-19 11:42:05,740 - Hadoop conf dir: /usr/hdp/2.5.3.0-37/hadoop/conf
> 2017-09-19 11:42:05,740 - Using hadoop conf dir:
> /usr/hdp/2.5.3.0-37/hadoop/conf
> 2017-09-19 11:42:05,742 - Before starting Stack Upgrade, check if tez tarball
> has been copied to HDFS.
> 2017-09-19 11:42:05,742 - Stack version 2.6.0.0 is sufficient to check if
> need to copy tez.tar.gz to HDFS.
> 2017-09-19 11:42:05,742 - Called copy_to_hdfs tarball: tez
> 2017-09-19 11:42:05,743 - Stack Feature Version Info: Cluster Stack=2.6,
> Command Stack=None, Command Version=2.5.3.0-37, Upgrade Direction=upgrade ->
> 2.5.3.0-37
> 2017-09-19 11:42:05,743 - Skipping stack-select on RU_EXECUTE_TASKS because
> it does not exist in the stack-select package structure.
> 2017-09-19 11:42:05,743 - Unable to determine the current version of the
> component for this command; unable to copy the tarball
> 2017-09-19 11:42:05,743 - Cannot copy tez tarball to HDFS because stack
> version could be be determined.
> 2017-09-19 11:42:05,743 - Cannot copy tez tarball to HDFS because stack
> version could be be determined.
> 2017-09-19 11:42:05,744 - Could not copy tarball tez due to a missing or
> incorrect parameter.
> 2017-09-19 11:42:05,744 - Could not copy tarball tez due to a missing or
> incorrect parameter.
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/TEZ/0.4.0.2.1/package/scripts/pre_upgrade.py",
> line 58, in
> TezPreUpgrade().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 327, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/TEZ/0.4.0.2.1/package/scripts/pre_upgrade.py",
> line 55, in prepare
> raise Fail("Could not copy tez tarball to HDFS.")
> resource_management.core.exceptions.Fail: Could not copy tez tarball to HDFS.
> Command failed after 1 tries
> {code}
> stderr:-
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/ru_execute_tasks.py",
> line 156, in
> ExecuteUpgradeTasks().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 327, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/ru_execute_tasks.py",
> line 153, in actionexecute
> shell.checked_call(task.command, logoutput=True, quiet=True)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 72, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File
[jira] [Updated] (AMBARI-22021) Livy not working with the default configuration
[
https://issues.apache.org/jira/browse/AMBARI-22021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prabhjyot Singh updated AMBARI-22021:
-
Attachment: AMBARI-22021_trunk_v2.patch
> Livy not working with the default configuration
> ---
>
> Key: AMBARI-22021
> URL: https://issues.apache.org/jira/browse/AMBARI-22021
> Project: Ambari
> Issue Type: Bug
>Reporter: Prabhjyot Singh
> Attachments: AMBARI-22021_trunk_v1.patch, AMBARI-22021_trunk_v2.patch
>
>
> This started failing with ZEPPELIN-2909, which introduces `"className":
> "org.apache.zeppelin.livy.LivySharedInterpreter". and now Livy fails with
> following exception;
> {code:java}
> java.lang.NullPointerException
> at
> org.apache.zeppelin.livy.BaseLivyInterpreter.open(BaseLivyInterpreter.java:109)
> at
> org.apache.zeppelin.interpreter.LazyOpenInterpreter.open(LazyOpenInterpreter.java:69)
> at
> org.apache.zeppelin.interpreter.remote.RemoteInterpreterServer$InterpretJob.jobRun(RemoteInterpreterServer.java:493)
> at org.apache.zeppelin.scheduler.Job.run(Job.java:175)
> at
> org.apache.zeppelin.scheduler.FIFOScheduler$1.run(FIFOScheduler.java:139)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> 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)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22011) Could not copy tez tarball to HDFS during prepare upgrade (EU)
[
https://issues.apache.org/jira/browse/AMBARI-22011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate Cole updated AMBARI-22011:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Could not copy tez tarball to HDFS during prepare upgrade (EU)
> --
>
> Key: AMBARI-22011
> URL: https://issues.apache.org/jira/browse/AMBARI-22011
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-22011.patch
>
>
> {code}
> 2017-09-19 11:42:05,103 - Task. Type: EXECUTE, Script: scripts/pre_upgrade.py
> - Function: prepare
> 2017-09-19 11:42:05,738 - Skipping stack-select on RU_EXECUTE_TASKS because
> it does not exist in the stack-select package structure.
> 2017-09-19 11:42:05,739 - Skipping stack-select on RU_EXECUTE_TASKS because
> it does not exist in the stack-select package structure.
> 2017-09-19 11:42:05,739 - An upgrade/downgrade for HDP-2.5.3.0-37 is in
> progress, determining which hadoop conf dir to use.
> 2017-09-19 11:42:05,740 - Skipping stack-select on RU_EXECUTE_TASKS because
> it does not exist in the stack-select package structure.
> 2017-09-19 11:42:05,740 - Hadoop conf dir: /usr/hdp/2.5.3.0-37/hadoop/conf
> 2017-09-19 11:42:05,740 - Using hadoop conf dir:
> /usr/hdp/2.5.3.0-37/hadoop/conf
> 2017-09-19 11:42:05,742 - Before starting Stack Upgrade, check if tez tarball
> has been copied to HDFS.
> 2017-09-19 11:42:05,742 - Stack version 2.6.0.0 is sufficient to check if
> need to copy tez.tar.gz to HDFS.
> 2017-09-19 11:42:05,742 - Called copy_to_hdfs tarball: tez
> 2017-09-19 11:42:05,743 - Stack Feature Version Info: Cluster Stack=2.6,
> Command Stack=None, Command Version=2.5.3.0-37, Upgrade Direction=upgrade ->
> 2.5.3.0-37
> 2017-09-19 11:42:05,743 - Skipping stack-select on RU_EXECUTE_TASKS because
> it does not exist in the stack-select package structure.
> 2017-09-19 11:42:05,743 - Unable to determine the current version of the
> component for this command; unable to copy the tarball
> 2017-09-19 11:42:05,743 - Cannot copy tez tarball to HDFS because stack
> version could be be determined.
> 2017-09-19 11:42:05,743 - Cannot copy tez tarball to HDFS because stack
> version could be be determined.
> 2017-09-19 11:42:05,744 - Could not copy tarball tez due to a missing or
> incorrect parameter.
> 2017-09-19 11:42:05,744 - Could not copy tarball tez due to a missing or
> incorrect parameter.
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/TEZ/0.4.0.2.1/package/scripts/pre_upgrade.py",
> line 58, in
> TezPreUpgrade().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 327, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/TEZ/0.4.0.2.1/package/scripts/pre_upgrade.py",
> line 55, in prepare
> raise Fail("Could not copy tez tarball to HDFS.")
> resource_management.core.exceptions.Fail: Could not copy tez tarball to HDFS.
> Command failed after 1 tries
> {code}
> stderr:-
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/ru_execute_tasks.py",
> line 156, in
> ExecuteUpgradeTasks().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 327, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/ru_execute_tasks.py",
> line 153, in actionexecute
> shell.checked_call(task.command, logoutput=True, quiet=True)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 72, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 303, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of 'source
> /var/lib/ambari-agent/ambari-env.sh ; /usr/bin/ambari-python-wrap
> /var/lib/ambari-agent/cache/common-services/TEZ/0.4.0.2.1/package/scripts/pre_upgrade.py
> prepare /var/lib/ambari-agent/data/command-380.json
> /var/lib/ambari-agent/cache/custom_actions
> /var/lib/ambari-agent/data/structured-out-380.json INFO
> /var/lib/ambari-agent/tmp' returned 1. 2017-09-19 11:42:05,738 -
[jira] [Updated] (AMBARI-22021) Livy not working with the default configuration
[
https://issues.apache.org/jira/browse/AMBARI-22021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prabhjyot Singh updated AMBARI-22021:
-
Attachment: AMBARI-22021_trunk_v1.patch
> Livy not working with the default configuration
> ---
>
> Key: AMBARI-22021
> URL: https://issues.apache.org/jira/browse/AMBARI-22021
> Project: Ambari
> Issue Type: Bug
>Reporter: Prabhjyot Singh
> Attachments: AMBARI-22021_trunk_v1.patch
>
>
> This started failing with ZEPPELIN-2909, which introduces `"className":
> "org.apache.zeppelin.livy.LivySharedInterpreter". and now Livy fails with
> following exception;
> {code:java}
> java.lang.NullPointerException
> at
> org.apache.zeppelin.livy.BaseLivyInterpreter.open(BaseLivyInterpreter.java:109)
> at
> org.apache.zeppelin.interpreter.LazyOpenInterpreter.open(LazyOpenInterpreter.java:69)
> at
> org.apache.zeppelin.interpreter.remote.RemoteInterpreterServer$InterpretJob.jobRun(RemoteInterpreterServer.java:493)
> at org.apache.zeppelin.scheduler.Job.run(Job.java:175)
> at
> org.apache.zeppelin.scheduler.FIFOScheduler$1.run(FIFOScheduler.java:139)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> 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)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22022) NullPointerException in ActionScheduler when using DEPENDENCY_ORDERED execution
[ https://issues.apache.org/jira/browse/AMBARI-22022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Magyari updated AMBARI-22022: Attachment: AMBARI-22022.patch > NullPointerException in ActionScheduler when using DEPENDENCY_ORDERED > execution > --- > > Key: AMBARI-22022 > URL: https://issues.apache.org/jira/browse/AMBARI-22022 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: 3.0.0 >Reporter: Sandor Magyari >Assignee: Sandor Magyari > Fix For: 3.0.0 > > Attachments: AMBARI-22022.patch > > > NullPointerException may occur in ActionScheduler when using > DEPENDENCY_ORDERED execution. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22022) NullPointerException in ActionScheduler when using DEPENDENCY_ORDERED execution
[ https://issues.apache.org/jira/browse/AMBARI-22022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Magyari updated AMBARI-22022: Status: Patch Available (was: Open) > NullPointerException in ActionScheduler when using DEPENDENCY_ORDERED > execution > --- > > Key: AMBARI-22022 > URL: https://issues.apache.org/jira/browse/AMBARI-22022 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: 3.0.0 >Reporter: Sandor Magyari >Assignee: Sandor Magyari > Fix For: 3.0.0 > > > NullPointerException may occur in ActionScheduler when using > DEPENDENCY_ORDERED execution. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22022) NullPointerException in ActionScheduler when using DEPENDENCY_ORDERED execution
Sandor Magyari created AMBARI-22022: --- Summary: NullPointerException in ActionScheduler when using DEPENDENCY_ORDERED execution Key: AMBARI-22022 URL: https://issues.apache.org/jira/browse/AMBARI-22022 Project: Ambari Issue Type: Bug Components: ambari-sever Affects Versions: 3.0.0 Reporter: Sandor Magyari Assignee: Sandor Magyari Fix For: 3.0.0 NullPointerException may occur in ActionScheduler when using DEPENDENCY_ORDERED execution. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22005) Add host through blueprint failed
[ https://issues.apache.org/jira/browse/AMBARI-22005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16174664#comment-16174664 ] Hudson commented on AMBARI-22005: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #261 (See [https://builds.apache.org/job/Ambari-branch-2.6/261/]) AMBARI-22005. Add host through blueprint failed (magyari_sandor) (smagyari: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4924c697bb8935f95ca106c175377251b18bc710]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/topology/TopologyManagerTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ScaleClusterRequest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ScaleClusterRequestTest.java > Add host through blueprint failed > - > > Key: AMBARI-22005 > URL: https://issues.apache.org/jira/browse/AMBARI-22005 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.0 >Reporter: Sandor Magyari >Assignee: Sandor Magyari >Priority: Blocker > Fix For: 2.6.0 > > Attachments: AMBARI-22005-branch-2.6.patch > > > Add host through blueprint failes with error message: 'nvalid Add Hosts > Template: org.apache.ambari.server.topology.InvalidTopologyTemplateException: > Must specify either host_name or host_count for hostgroup: add-host' -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AMBARI-21864) DEPENDENCY_ORDERED stage execution hangs in case of circular dependencies between role commands
[ https://issues.apache.org/jira/browse/AMBARI-21864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Magyari resolved AMBARI-21864. - Resolution: Fixed > DEPENDENCY_ORDERED stage execution hangs in case of circular dependencies > between role commands > --- > > Key: AMBARI-21864 > URL: https://issues.apache.org/jira/browse/AMBARI-21864 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Sandor Magyari >Assignee: Sandor Magyari >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-21864.patch > > > In case there is a circular dependency after adding transitive dependencies > between role commands, if > server.stage.command.execution_type=DEPENDENCY_ORDERED a role command > depending on same role command will never be executed. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Issue Comment Deleted] (AMBARI-21864) DEPENDENCY_ORDERED stage execution hangs in case of circular dependencies between role commands
[ https://issues.apache.org/jira/browse/AMBARI-21864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Magyari updated AMBARI-21864: Comment: was deleted (was: Find a NullPointerException in ActionScheduler, which need to be fixed.) > DEPENDENCY_ORDERED stage execution hangs in case of circular dependencies > between role commands > --- > > Key: AMBARI-21864 > URL: https://issues.apache.org/jira/browse/AMBARI-21864 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Sandor Magyari >Assignee: Sandor Magyari >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-21864.patch > > > In case there is a circular dependency after adding transitive dependencies > between role commands, if > server.stage.command.execution_type=DEPENDENCY_ORDERED a role command > depending on same role command will never be executed. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22005) Add host through blueprint failed
[ https://issues.apache.org/jira/browse/AMBARI-22005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Magyari updated AMBARI-22005: Resolution: Fixed Status: Resolved (was: Patch Available) > Add host through blueprint failed > - > > Key: AMBARI-22005 > URL: https://issues.apache.org/jira/browse/AMBARI-22005 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.0 >Reporter: Sandor Magyari >Assignee: Sandor Magyari >Priority: Blocker > Fix For: 2.6.0 > > Attachments: AMBARI-22005-branch-2.6.patch > > > Add host through blueprint failes with error message: 'nvalid Add Hosts > Template: org.apache.ambari.server.topology.InvalidTopologyTemplateException: > Must specify either host_name or host_count for hostgroup: add-host' -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22021) Livy not working with the default configuration
[
https://issues.apache.org/jira/browse/AMBARI-22021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prabhjyot Singh updated AMBARI-22021:
-
Status: Patch Available (was: Open)
> Livy not working with the default configuration
> ---
>
> Key: AMBARI-22021
> URL: https://issues.apache.org/jira/browse/AMBARI-22021
> Project: Ambari
> Issue Type: Bug
>Reporter: Prabhjyot Singh
>
> This started failing with ZEPPELIN-2909, which introduces `"className":
> "org.apache.zeppelin.livy.LivySharedInterpreter". and now Livy fails with
> following exception;
> {code:java}
> java.lang.NullPointerException
> at
> org.apache.zeppelin.livy.BaseLivyInterpreter.open(BaseLivyInterpreter.java:109)
> at
> org.apache.zeppelin.interpreter.LazyOpenInterpreter.open(LazyOpenInterpreter.java:69)
> at
> org.apache.zeppelin.interpreter.remote.RemoteInterpreterServer$InterpretJob.jobRun(RemoteInterpreterServer.java:493)
> at org.apache.zeppelin.scheduler.Job.run(Job.java:175)
> at
> org.apache.zeppelin.scheduler.FIFOScheduler$1.run(FIFOScheduler.java:139)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> 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)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22021) Livy not working with the default configuration
Prabhjyot Singh created AMBARI-22021:
Summary: Livy not working with the default configuration
Key: AMBARI-22021
URL: https://issues.apache.org/jira/browse/AMBARI-22021
Project: Ambari
Issue Type: Bug
Reporter: Prabhjyot Singh
This started failing with ZEPPELIN-2909, which introduces `"className":
"org.apache.zeppelin.livy.LivySharedInterpreter". and now Livy fails with
following exception;
{code:java}
java.lang.NullPointerException
at
org.apache.zeppelin.livy.BaseLivyInterpreter.open(BaseLivyInterpreter.java:109)
at
org.apache.zeppelin.interpreter.LazyOpenInterpreter.open(LazyOpenInterpreter.java:69)
at
org.apache.zeppelin.interpreter.remote.RemoteInterpreterServer$InterpretJob.jobRun(RemoteInterpreterServer.java:493)
at org.apache.zeppelin.scheduler.Job.run(Job.java:175)
at
org.apache.zeppelin.scheduler.FIFOScheduler$1.run(FIFOScheduler.java:139)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
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)
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21919) Kerberos identity references should use the "reference" attribute
[
https://issues.apache.org/jira/browse/AMBARI-21919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-21919:
--
Attachment: AMBARI-21919_branch-2.6_02.patch
AMBARI-21919_trunk_02.patch
> Kerberos identity references should use the "reference" attribute
> -
>
> Key: AMBARI-21919
> URL: https://issues.apache.org/jira/browse/AMBARI-21919
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: kerberos_descriptor
> Fix For: 2.6.0
>
> Attachments: AMBARI-21919_branch-2.6_01.patch,
> AMBARI-21919_branch-2.6_02.patch, AMBARI-21919_trunk_01.patch,
> AMBARI-21919_trunk_02.patch
>
>
> Kerberos identity references should use the "reference" attribute rather than
> rely on the "name" attribute to indicate the identity descriptor references
> some other identity descriptor.
> Either method should work on the backend, however the UI appears to not fully
> handle the "named" reference properly.
> The solution is to change
> {code}
> {
> "name": "/HDFS/NAMENODE/namenode_nn",
> "principal": {
> "configuration":
> "ranger-hdfs-audit/xasecure.audit.jaas.Client.option.principal"
> },
> "keytab": {
> "configuration":
> "ranger-hdfs-audit/xasecure.audit.jaas.Client.option.keyTab"
> }
> }
> {code}
> by changing the "name" attribute to "reference" and adding a new "name"
> reference with a unique name relative to the scope of the identity
> descriptor. For example:
> {code}
> {
> "name":"ranger_hdfs_audit"
> "reference": "/HDFS/NAMENODE/namenode_nn",
> "principal": {
> "configuration":
> "ranger-hdfs-audit/xasecure.audit.jaas.Client.option.principal"
> },
> "keytab": {
> "configuration":
> "ranger-hdfs-audit/xasecure.audit.jaas.Client.option.keyTab"
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21406) Refresh configurations without restarting components
[ https://issues.apache.org/jira/browse/AMBARI-21406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Magyari updated AMBARI-21406: Attachment: AMBARI-21406-v5.patch > Refresh configurations without restarting components > > > Key: AMBARI-21406 > URL: https://issues.apache.org/jira/browse/AMBARI-21406 > Project: Ambari > Issue Type: Task > Components: ambari-agent, ambari-server >Reporter: Sandor Magyari >Assignee: Sandor Magyari > Fix For: 3.0.0 > > Attachments: AMBARI-21406-v1.patch, AMBARI-21406-v2.patch, > AMBARI-21406-v3.patch, AMBARI-21406-v4.patch, AMBARI-21406-v5.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Reopened] (AMBARI-21864) DEPENDENCY_ORDERED stage execution hangs in case of circular dependencies between role commands
[ https://issues.apache.org/jira/browse/AMBARI-21864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Magyari reopened AMBARI-21864: - Find a NullPointerException in ActionScheduler, which need to be fixed. > DEPENDENCY_ORDERED stage execution hangs in case of circular dependencies > between role commands > --- > > Key: AMBARI-21864 > URL: https://issues.apache.org/jira/browse/AMBARI-21864 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Sandor Magyari >Assignee: Sandor Magyari >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-21864.patch > > > In case there is a circular dependency after adding transitive dependencies > between role commands, if > server.stage.command.execution_type=DEPENDENCY_ORDERED a role command > depending on same role command will never be executed. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22018) Stack list in the ambari UI select stack page goes out of bounds when HDF is installed with HDP
[ https://issues.apache.org/jira/browse/AMBARI-22018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16174593#comment-16174593 ] Hudson commented on AMBARI-22018: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #260 (See [https://builds.apache.org/job/Ambari-branch-2.6/260/]) AMBARI-22018. Stack list in the ambari UI select stack page goes out of (aantonenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=68e010cbd519768cb23994280bc1ff7c79dc7567]) * (edit) ambari-web/app/styles/application.less > Stack list in the ambari UI select stack page goes out of bounds when HDF is > installed with HDP > --- > > Key: AMBARI-22018 > URL: https://issues.apache.org/jira/browse/AMBARI-22018 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-22018_branch-26.patch > > > The stacks are going out of the bounds of the UI as can be seen in the image. > HDF 2.0 is not seen. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22015) livy2 interpreter errors (unable to impersonate users/ LLAP or Hive CNF issue) due to missing proxy configs
[
https://issues.apache.org/jira/browse/AMBARI-22015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16174590#comment-16174590
]
Hadoop QA commented on AMBARI-22015:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12888190/AMBARI-22015.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12306//console
This message is automatically generated.
> livy2 interpreter errors (unable to impersonate users/ LLAP or Hive CNF
> issue) due to missing proxy configs
> ---
>
> Key: AMBARI-22015
> URL: https://issues.apache.org/jira/browse/AMBARI-22015
> Project: Ambari
> Issue Type: Bug
>Reporter: Mingjie Tang
>Assignee: Mingjie Tang
> Attachments: AMBARI-22015.patch
>
>
> This seems to have regressed in Run ID : 61142, but was working fine in Run
> ID : 60868 (which was Thursday night run). Livy for Spark2 is failing to
> impersonate users
> 17/08/28 17:45:55 INFO ContextLauncher: ERROR:
> org.apache.hadoop.security.authorize.AuthorizationException: User: livy is
> not allowed to impersonate hrt_1
> 17/08/28 17:45:55 WARN ContextLauncher: Child process exited with code 1.
> 17/08/28 17:45:55 ERROR RSCClient: Failed to connect to context.
> java.io.IOException: Child process exited with code 1.
> at
> com.cloudera.livy.rsc.ContextLauncher$ChildProcess$1.run(ContextLauncher.java:416)
> at
> com.cloudera.livy.rsc.ContextLauncher$ChildProcess$2.run(ContextLauncher.java:490)
> at java.lang.Thread.run(Thread.java:748)
> after I setup hadoop.proxyusers.livy.hosts=* and
> hadoop.proxyusers.livy.groups=* in core-site
> it gives following error which is expected because of some other test
> failures on this cluster
> java.lang.IllegalArgumentException: Unable to instantiate SparkSession with
> LLAP support because LLAP or Hive classes are not found.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22013) Add JMX enable/disable option to Infra Solr
[ https://issues.apache.org/jira/browse/AMBARI-22013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16174584#comment-16174584 ] Hudson commented on AMBARI-22013: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8109 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8109/]) AMBARI-22013. Add JMX enable/disable option to Infra Solr (oleewere) (oleewere: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=1a5b4943cbfa42d66d61e5cb29a09e1d3ad9acb7]) * (edit) ambari-server/src/main/resources/common-services/AMBARI_INFRA/0.1.0/properties/infra-solr-env.sh.j2 * (edit) ambari-web/app/data/configs/services/ambari_infra_properties.js * (edit) ambari-server/src/main/resources/common-services/AMBARI_INFRA/0.1.0/configuration/infra-solr-env.xml * (edit) ambari-server/src/main/resources/common-services/AMBARI_INFRA/0.1.0/package/scripts/params.py * (edit) ambari-logsearch/docker/test-config/solr/solr-env.sh * (edit) ambari-logsearch/docker/test-config/solr/solr-env-ssl.sh > Add JMX enable/disable option to Infra Solr > --- > > Key: AMBARI-22013 > URL: https://issues.apache.org/jira/browse/AMBARI-22013 > Project: Ambari > Issue Type: Bug > Components: ambari-infra, ambari-server >Affects Versions: 2.5.2 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 3.0.0 > > Attachments: AMBARI-22013.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AMBARI-22018) Stack list in the ambari UI select stack page goes out of bounds when HDF is installed with HDP
[ https://issues.apache.org/jira/browse/AMBARI-22018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander resolved AMBARI-22018. -- Resolution: Fixed Committed to branch-2.6 > Stack list in the ambari UI select stack page goes out of bounds when HDF is > installed with HDP > --- > > Key: AMBARI-22018 > URL: https://issues.apache.org/jira/browse/AMBARI-22018 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-22018_branch-26.patch > > > The stacks are going out of the bounds of the UI as can be seen in the image. > HDF 2.0 is not seen. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22017) stack advisor recommends all components on single host for HDP-2.6 Ambari trunk build
[
https://issues.apache.org/jira/browse/AMBARI-22017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16174564#comment-16174564
]
Hadoop QA commented on AMBARI-22017:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12888245/AMBARI-22017.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 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 core tests{color}. The test build failed in
[ambari-server|https://builds.apache.org/job/Ambari-trunk-test-patch/12305//artifact/patch-work/testrun_ambari-server.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12305//console
This message is automatically generated.
> stack advisor recommends all components on single host for HDP-2.6 Ambari
> trunk build
> -
>
> Key: AMBARI-22017
> URL: https://issues.apache.org/jira/browse/AMBARI-22017
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: trunk, 3.0.0
>
> Attachments: AMBARI-22017.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22020) Setup tez ats loglevel to TASK_ATTEMPT to enable the filters.
[ https://issues.apache.org/jira/browse/AMBARI-22020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harish Jaiprakash updated AMBARI-22020: --- Attachment: AMBARI-22020.01.patch > Setup tez ats loglevel to TASK_ATTEMPT to enable the filters. > - > > Key: AMBARI-22020 > URL: https://issues.apache.org/jira/browse/AMBARI-22020 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Harish Jaiprakash > Attachments: AMBARI-22020.01.patch > > > tez.history.logging.log.level should be TASK_ATTEMPT so that task kill filter > will work. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22020) Setup tez ats loglevel to TASK_ATTEMPT to enable the filters.
[ https://issues.apache.org/jira/browse/AMBARI-22020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harish Jaiprakash updated AMBARI-22020: --- Status: Patch Available (was: Open) > Setup tez ats loglevel to TASK_ATTEMPT to enable the filters. > - > > Key: AMBARI-22020 > URL: https://issues.apache.org/jira/browse/AMBARI-22020 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Harish Jaiprakash > Attachments: AMBARI-22020.01.patch > > > tez.history.logging.log.level should be TASK_ATTEMPT so that task kill filter > will work. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22020) Setup tez ats loglevel to TASK_ATTEMPT to enable the filters.
Harish Jaiprakash created AMBARI-22020: -- Summary: Setup tez ats loglevel to TASK_ATTEMPT to enable the filters. Key: AMBARI-22020 URL: https://issues.apache.org/jira/browse/AMBARI-22020 Project: Ambari Issue Type: Bug Affects Versions: 2.5.0 Reporter: Harish Jaiprakash tez.history.logging.log.level should be TASK_ATTEMPT so that task kill filter will work. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22018) Stack list in the ambari UI select stack page goes out of bounds when HDF is installed with HDP
[ https://issues.apache.org/jira/browse/AMBARI-22018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16174555#comment-16174555 ] Andrii Tkach commented on AMBARI-22018: --- +1 for the patch > Stack list in the ambari UI select stack page goes out of bounds when HDF is > installed with HDP > --- > > Key: AMBARI-22018 > URL: https://issues.apache.org/jira/browse/AMBARI-22018 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-22018_branch-26.patch > > > The stacks are going out of the bounds of the UI as can be seen in the image. > HDF 2.0 is not seen. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22019) Enable logsearch-web unit tests and make them skippable
[ https://issues.apache.org/jira/browse/AMBARI-22019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-22019: -- Attachment: AMBARI-22019.patch > Enable logsearch-web unit tests and make them skippable > --- > > Key: AMBARI-22019 > URL: https://issues.apache.org/jira/browse/AMBARI-22019 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 3.0.0 > > Attachments: AMBARI-22019.patch > > > enable UT for logseach-web > can be skipped by adding -DskipTests to the mvn command -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22019) Enable logsearch-web unit tests and make them skippable
[ https://issues.apache.org/jira/browse/AMBARI-22019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-22019: -- Status: Patch Available (was: In Progress) > Enable logsearch-web unit tests and make them skippable > --- > > Key: AMBARI-22019 > URL: https://issues.apache.org/jira/browse/AMBARI-22019 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 3.0.0 > > Attachments: AMBARI-22019.patch > > > enable UT for logseach-web > can be skipped by adding -DskipTests to the mvn command -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-22018) Stack list in the ambari UI select stack page goes out of bounds when HDF is installed with HDP
[ https://issues.apache.org/jira/browse/AMBARI-22018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-22018: Assignee: Antonenko Alexander > Stack list in the ambari UI select stack page goes out of bounds when HDF is > installed with HDP > --- > > Key: AMBARI-22018 > URL: https://issues.apache.org/jira/browse/AMBARI-22018 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-22018_branch-26.patch > > > The stacks are going out of the bounds of the UI as can be seen in the image. > HDF 2.0 is not seen. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22019) Enable logsearch-web unit tests and make them skippable
[ https://issues.apache.org/jira/browse/AMBARI-22019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-22019: -- Description: enable UT for logseach-web can be skipped by adding -DskipTests to the mvn command > Enable logsearch-web unit tests and make them skippable > --- > > Key: AMBARI-22019 > URL: https://issues.apache.org/jira/browse/AMBARI-22019 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 3.0.0 > > > enable UT for logseach-web > can be skipped by adding -DskipTests to the mvn command -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22018) Stack list in the ambari UI select stack page goes out of bounds when HDF is installed with HDP
[ https://issues.apache.org/jira/browse/AMBARI-22018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16174553#comment-16174553 ] Antonenko Alexander commented on AMBARI-22018: -- Task is actual only for branch-2.6. Patch is for branch-2.6, manually tested > Stack list in the ambari UI select stack page goes out of bounds when HDF is > installed with HDP > --- > > Key: AMBARI-22018 > URL: https://issues.apache.org/jira/browse/AMBARI-22018 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-22018_branch-26.patch > > > The stacks are going out of the bounds of the UI as can be seen in the image. > HDF 2.0 is not seen. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22018) Stack list in the ambari UI select stack page goes out of bounds when HDF is installed with HDP
[ https://issues.apache.org/jira/browse/AMBARI-22018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-22018: - Attachment: AMBARI-22018_branch-26.patch > Stack list in the ambari UI select stack page goes out of bounds when HDF is > installed with HDP > --- > > Key: AMBARI-22018 > URL: https://issues.apache.org/jira/browse/AMBARI-22018 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-22018_branch-26.patch > > > The stacks are going out of the bounds of the UI as can be seen in the image. > HDF 2.0 is not seen. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22019) Enable logsearch-web unit tests and make them skippable
Olivér Szabó created AMBARI-22019: - Summary: Enable logsearch-web unit tests and make them skippable Key: AMBARI-22019 URL: https://issues.apache.org/jira/browse/AMBARI-22019 Project: Ambari Issue Type: Bug Components: ambari-logsearch Affects Versions: 3.0.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22018) Stack list in the ambari UI select stack page goes out of bounds when HDF is installed with HDP
Antonenko Alexander created AMBARI-22018: Summary: Stack list in the ambari UI select stack page goes out of bounds when HDF is installed with HDP Key: AMBARI-22018 URL: https://issues.apache.org/jira/browse/AMBARI-22018 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.6.0 Reporter: Antonenko Alexander Priority: Critical Fix For: 2.6.0 The stacks are going out of the bounds of the UI as can be seen in the image. HDF 2.0 is not seen. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22017) stack advisor recommends all components on single host for HDP-2.6 Ambari trunk build
[ https://issues.apache.org/jira/browse/AMBARI-22017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16174538#comment-16174538 ] Dmytro Sen commented on AMBARI-22017: - Test failures are not related to the patch > stack advisor recommends all components on single host for HDP-2.6 Ambari > trunk build > - > > Key: AMBARI-22017 > URL: https://issues.apache.org/jira/browse/AMBARI-22017 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Blocker > Fix For: trunk, 3.0.0 > > Attachments: AMBARI-22017.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22013) Add JMX enable/disable option to Infra Solr
[ https://issues.apache.org/jira/browse/AMBARI-22013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-22013: -- Resolution: Fixed Status: Resolved (was: Patch Available) committed to trunk > Add JMX enable/disable option to Infra Solr > --- > > Key: AMBARI-22013 > URL: https://issues.apache.org/jira/browse/AMBARI-22013 > Project: Ambari > Issue Type: Bug > Components: ambari-infra, ambari-server >Affects Versions: 2.5.2 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 3.0.0 > > Attachments: AMBARI-22013.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22017) stack advisor recommends all components on single host for HDP-2.6 Ambari trunk build
[
https://issues.apache.org/jira/browse/AMBARI-22017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16174533#comment-16174533
]
Hadoop QA commented on AMBARI-22017:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12888245/AMBARI-22017.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 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 core tests{color}. The test build failed in
[ambari-server|https://builds.apache.org/job/Ambari-trunk-test-patch/12304//artifact/patch-work/testrun_ambari-server.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12304//console
This message is automatically generated.
> stack advisor recommends all components on single host for HDP-2.6 Ambari
> trunk build
> -
>
> Key: AMBARI-22017
> URL: https://issues.apache.org/jira/browse/AMBARI-22017
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: trunk, 3.0.0
>
> Attachments: AMBARI-22017.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22017) stack advisor recommends all components on single host for HDP-2.6 Ambari trunk build
[ https://issues.apache.org/jira/browse/AMBARI-22017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-22017: Attachment: AMBARI-22017.patch > stack advisor recommends all components on single host for HDP-2.6 Ambari > trunk build > - > > Key: AMBARI-22017 > URL: https://issues.apache.org/jira/browse/AMBARI-22017 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Blocker > Fix For: trunk, 3.0.0 > > Attachments: AMBARI-22017.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22017) stack advisor recommends all components on single host for HDP-2.6 Ambari trunk build
[ https://issues.apache.org/jira/browse/AMBARI-22017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-22017: Status: Patch Available (was: In Progress) > stack advisor recommends all components on single host for HDP-2.6 Ambari > trunk build > - > > Key: AMBARI-22017 > URL: https://issues.apache.org/jira/browse/AMBARI-22017 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Blocker > Fix For: trunk, 3.0.0 > > Attachments: AMBARI-22017.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22017) stack advisor recommends all components on single host for HDP-2.6 Ambari trunk build
Dmytro Sen created AMBARI-22017: --- Summary: stack advisor recommends all components on single host for HDP-2.6 Ambari trunk build Key: AMBARI-22017 URL: https://issues.apache.org/jira/browse/AMBARI-22017 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 3.0.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Priority: Blocker Fix For: trunk, 3.0.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22016) changeToSecureUid.sh might collide with existing user if it is not a local user but a network managed user
Aman Poonia created AMBARI-22016:
Summary: changeToSecureUid.sh might collide with existing user if
it is not a local user but a network managed user
Key: AMBARI-22016
URL: https://issues.apache.org/jira/browse/AMBARI-22016
Project: Ambari
Issue Type: Bug
Components: stacks
Affects Versions: 2.5.2
Environment: Using Centos as the test bed
Reporter: Aman Poonia
Assignee: Aman Poonia
Fix For: 2.6.0
changeToSecureUid.sh might collide with existing user if it is not a local user
but a network managed user
Currently we are doing
{code:java}
function find_available_uid() {
for ((i=1001; i<=2000; i++))
do
grep -q $i /etc/passwd
if [ "$?" -ne 0 ]
then
newUid=$i
break
fi
done
}
{code}
This will only check local user. Network manged users are not directly present
inside passwd file.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
