[jira] [Commented] (AMBARI-22768) Update Welcome page style
[
https://issues.apache.org/jira/browse/AMBARI-22768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322567#comment-16322567
]
Hadoop QA commented on AMBARI-22768:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12905708/AMBARI-22768.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-admin ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12950//console
This message is automatically generated.
> Update Welcome page style
> -
>
> Key: AMBARI-22768
> URL: https://issues.apache.org/jira/browse/AMBARI-22768
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-22768.patch
>
>
> Update layout Welcome page on Admin View.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22706) Ranger installation fails
[
https://issues.apache.org/jira/browse/AMBARI-22706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322518#comment-16322518
]
Hadoop QA commented on AMBARI-22706:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12903900/AMBARI-22706.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/12949//console
This message is automatically generated.
> Ranger installation fails
> -
>
> Key: AMBARI-22706
> URL: https://issues.apache.org/jira/browse/AMBARI-22706
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-22706.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22767) Kerberos wizard. Advanced kerberos-env password properties should be visible only if the KDC type is "Active Directory"
[
https://issues.apache.org/jira/browse/AMBARI-22767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322361#comment-16322361
]
Hadoop QA commented on AMBARI-22767:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12905684/AMBARI-22767.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:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12948//console
This message is automatically generated.
> Kerberos wizard. Advanced kerberos-env password properties should be visible
> only if the KDC type is "Active Directory"
>
>
> Key: AMBARI-22767
> URL: https://issues.apache.org/jira/browse/AMBARI-22767
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 3.0.0
>
> Attachments: AMBARI-22767.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22759) [Hive Views 2.0] Deleting a Saved query is Buggy when Mutliple Queries exist in same Name
[
https://issues.apache.org/jira/browse/AMBARI-22759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322238#comment-16322238
]
Hadoop QA commented on AMBARI-22759:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12905640/AMBARI-22759-trunk.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:red}-1 core tests{color}. The test build failed in
[contrib/views/hive20|https://builds.apache.org/job/Ambari-trunk-test-patch/12947//artifact/patch-work/testrun_hive20.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12947//console
This message is automatically generated.
> [Hive Views 2.0] Deleting a Saved query is Buggy when Mutliple Queries exist
> in same Name
> -
>
> Key: AMBARI-22759
> URL: https://issues.apache.org/jira/browse/AMBARI-22759
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.2
> Environment: ambari 2.5.2
>Reporter: Akhil S Naik
> Labels: newbie, patch, usability
> Fix For: 3.0.0
>
> Attachments: AMBARI-22759-trunk.patch,
> hive_duplicate_saved_query_issue.png
>
>
> Reproduction scenario :
> Save some queries under same name .
> !https://issues.apache.org/jira/secure/attachment/12905639/hive_duplicate_saved_query_issue.png!
> delete one of the saved query
> *hive views is deleting some other query randomly and the query i deleted
> still exists in saved query even after refresh of page.*
> Root Cause :
> After the Fix of AMBARI-19958, Hive views is querying the saved Queries with
> FilterBy queryId and server is responding mutiple queries as all the queries
> has same name,
> then Web client is deleting the first record from these savedQueries due to
> which this issue is happening.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22762) Can not stop one single flume agent when deployed on the same host
[
https://issues.apache.org/jira/browse/AMBARI-22762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322198#comment-16322198
]
Hadoop QA commented on AMBARI-22762:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12905657/AMBARI-22762.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:red}-1 core tests{color}. The test build failed in
[ambari-server|https://builds.apache.org/job/Ambari-trunk-test-patch/12946//artifact/patch-work/testrun_ambari-server.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12946//console
This message is automatically generated.
> Can not stop one single flume agent when deployed on the same host
> --
>
> Key: AMBARI-22762
> URL: https://issues.apache.org/jira/browse/AMBARI-22762
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
> Environment: ambari 2.5.2,
> flume 1.8
>Reporter: mathildaMa09
> Attachments: AMBARI-22762.patch
>
>
> I'm using ambari 2.5.2, flume 1.8, when i install one more agents on same
> host, once try stop agent, other agents stop also.
> notice: one agent named 'a', the other name 'b'
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22764) NN HA wizard is broken due to recent commit for config compare
[
https://issues.apache.org/jira/browse/AMBARI-22764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322177#comment-16322177
]
Hadoop QA commented on AMBARI-22764:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12905665/AMBARI-22764.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12945//console
This message is automatically generated.
> NN HA wizard is broken due to recent commit for config compare
> --
>
> Key: AMBARI-22764
> URL: https://issues.apache.org/jira/browse/AMBARI-22764
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-22764.patch, log1.png, log2.png
>
>
> Save button on NN HA wizard step3 is disabled.
> Screenshots attached.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22764) NN HA wizard is broken due to recent commit for config compare
[
https://issues.apache.org/jira/browse/AMBARI-22764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322146#comment-16322146
]
Hadoop QA commented on AMBARI-22764:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12905665/AMBARI-22764.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12944//console
This message is automatically generated.
> NN HA wizard is broken due to recent commit for config compare
> --
>
> Key: AMBARI-22764
> URL: https://issues.apache.org/jira/browse/AMBARI-22764
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-22764.patch, log1.png, log2.png
>
>
> Save button on NN HA wizard step3 is disabled.
> Screenshots attached.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22764) NN HA wizard is broken due to recent commit for config compare
[
https://issues.apache.org/jira/browse/AMBARI-22764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322106#comment-16322106
]
Hadoop QA commented on AMBARI-22764:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12905665/AMBARI-22764.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:red}-1 core tests{color}. The test build failed in
[ambari-web|https://builds.apache.org/job/Ambari-trunk-test-patch/12943//artifact/patch-work/testrun_ambari-web.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12943//console
This message is automatically generated.
> NN HA wizard is broken due to recent commit for config compare
> --
>
> Key: AMBARI-22764
> URL: https://issues.apache.org/jira/browse/AMBARI-22764
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-22764.patch, log1.png, log2.png
>
>
> Save button on NN HA wizard step3 is disabled.
> Screenshots attached.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22757) Log Search UI: implement query manipulation from resources diagram
[
https://issues.apache.org/jira/browse/AMBARI-22757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16320833#comment-16320833
]
Hadoop QA commented on AMBARI-22757:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12905516/AMBARI-22757.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/12942//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12942//console
This message is automatically generated.
> Log Search UI: implement query manipulation from resources diagram
> --
>
> Key: AMBARI-22757
> URL: https://issues.apache.org/jira/browse/AMBARI-22757
> Project: Ambari
> Issue Type: Task
> Components: ambari-logsearch
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-22757.patch
>
>
> User should be able to add or exclude resources from access logs query from
> diagram on Summary tab.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22756) Post-install: Reduce navigation width in wizard
[
https://issues.apache.org/jira/browse/AMBARI-22756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16320155#comment-16320155
]
Hadoop QA commented on AMBARI-22756:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12905442/AMBARI-22756.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/12940//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12940//console
This message is automatically generated.
> Post-install: Reduce navigation width in wizard
> ---
>
> Key: AMBARI-22756
> URL: https://issues.apache.org/jira/browse/AMBARI-22756
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Minor
> Fix For: 3.0.0
>
> Attachments: AMBARI-22756.patch
>
>
> Reduce width of navigation and make it fixed in wizards.
> Step of the wizard should be ignored in breadcrumbs.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22409) Store the user input at step 3 for custom HDP and HDP-UTILS repo URLs
[
https://issues.apache.org/jira/browse/AMBARI-22409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16318692#comment-16318692
]
Hadoop QA commented on AMBARI-22409:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12905252/AMBARI-22409.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/12939//console
This message is automatically generated.
> Store the user input at step 3 for custom HDP and HDP-UTILS repo URLs
> -
>
> Key: AMBARI-22409
> URL: https://issues.apache.org/jira/browse/AMBARI-22409
> Project: Ambari
> Issue Type: Sub-task
> Components: ambari-web
>Reporter: Yussuf Shaikh
>Assignee: Yussuf Shaikh
> Attachments: AMBARI-22409.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22656) Add slot info for Hosts page
[
https://issues.apache.org/jira/browse/AMBARI-22656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317238#comment-16317238
]
Hadoop QA commented on AMBARI-22656:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12905072/AMBARI-22656.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified test files.
{color:green}+1 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 patch failed these unit tests in
ambari-agent ambari-server ambari-web:
org.apache.ambari.server.topology.BlueprintImplTest
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12938//console
This message is automatically generated.
> Add slot info for Hosts page
>
>
> Key: AMBARI-22656
> URL: https://issues.apache.org/jira/browse/AMBARI-22656
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-agent, ambari-server, ambari-web
>Affects Versions: 2.5.2
>Reporter: mathildaMa09
> Fix For: 2.5.2
>
> Attachments: AMBARI-22656.patch
>
>
> In Hosts Page lists info about hosts like Rack、IP、Cores、DiskUsage .etc, but I
> need more details about my hosts’ physical position, like slot for instance,
> to know exactly where my machine locates. So, in hosts page, we can add slot
> info to describe their location.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22740) Fix integration test for HBase in branch-3.0-ams due to UUID changes
[
https://issues.apache.org/jira/browse/AMBARI-22740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314180#comment-16314180
]
Hadoop QA commented on AMBARI-22740:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12904853/AMBARI-22740.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/12937//console
This message is automatically generated.
> Fix integration test for HBase in branch-3.0-ams due to UUID changes
>
>
> Key: AMBARI-22740
> URL: https://issues.apache.org/jira/browse/AMBARI-22740
> Project: Ambari
> Issue Type: Task
> Components: ambari-metrics
>Affects Versions: 3.0.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-22740.patch
>
>
> Fixing all integration tests in AMS timeline-service module.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22741) Log Search UI: implement graph for access logs
[
https://issues.apache.org/jira/browse/AMBARI-22741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16314114#comment-16314114
]
Hadoop QA commented on AMBARI-22741:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12904845/AMBARI-22741.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-logsearch/ambari-logsearch-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12936//console
This message is automatically generated.
> Log Search UI: implement graph for access logs
> --
>
> Key: AMBARI-22741
> URL: https://issues.apache.org/jira/browse/AMBARI-22741
> Project: Ambari
> Issue Type: Task
> Components: ambari-logsearch
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-22741.patch
>
>
> Line chart with time-dependent counts of access events from different sources
> should be implemented.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22741) Log Search UI: implement graph for access logs
[
https://issues.apache.org/jira/browse/AMBARI-22741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16313749#comment-16313749
]
Hadoop QA commented on AMBARI-22741:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12904845/AMBARI-22741.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:red}-1 javac{color}. The patch appears to cause the [build to
fail|https://builds.apache.org/job/Ambari-trunk-test-patch/12935//artifact/patch-work/patchJavacWarnings.txt].
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12935//console
This message is automatically generated.
> Log Search UI: implement graph for access logs
> --
>
> Key: AMBARI-22741
> URL: https://issues.apache.org/jira/browse/AMBARI-22741
> Project: Ambari
> Issue Type: Task
> Components: ambari-logsearch
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-22741.patch
>
>
> Line chart with time-dependent counts of access events from different sources
> should be implemented.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22121) Create mpack for Isilon OneFS
[
https://issues.apache.org/jira/browse/AMBARI-22121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16313589#comment-16313589
]
Hadoop QA commented on AMBARI-22121:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12904815/AMBARI-22121.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/12934//console
This message is automatically generated.
> Create mpack for Isilon OneFS
> -
>
> Key: AMBARI-22121
> URL: https://issues.apache.org/jira/browse/AMBARI-22121
> Project: Ambari
> Issue Type: Task
> Components: contrib
>Affects Versions: 3.0.0
>Reporter: Attila Magyar
>Assignee: Attila Magyar
> Fix For: 3.0.0
>
> Attachments: AMBARI-22121.patch, AMBARI-22121_2.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22736) Filter of Config Versions should be case insensitive
[
https://issues.apache.org/jira/browse/AMBARI-22736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16313450#comment-16313450
]
Hadoop QA commented on AMBARI-22736:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12904817/AMBARI-22736.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 2 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:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12932//console
This message is automatically generated.
> Filter of Config Versions should be case insensitive
>
>
> Key: AMBARI-22736
> URL: https://issues.apache.org/jira/browse/AMBARI-22736
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Minor
> Fix For: 3.0.0
>
> Attachments: AMBARI-22736.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22656) Add slot info for Hosts page
[
https://issues.apache.org/jira/browse/AMBARI-22656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16313296#comment-16313296
]
Hadoop QA commented on AMBARI-22656:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12904719/AMBARI-22656.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/12931//console
This message is automatically generated.
> Add slot info for Hosts page
>
>
> Key: AMBARI-22656
> URL: https://issues.apache.org/jira/browse/AMBARI-22656
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-agent, ambari-server, ambari-web
>Affects Versions: 2.5.2
>Reporter: mathildaMa09
> Fix For: 2.5.2
>
> Attachments: AMBARI-22656.patch
>
>
> In Hosts Page lists info about hosts like Rack、IP、Cores、DiskUsage .etc, but I
> need more details about my hosts’ physical position, like slot for instance,
> to know exactly where my machine locates. So, in hosts page, we can add slot
> info to describe their location.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22449) Improved service/component dependency support
[
https://issues.apache.org/jira/browse/AMBARI-22449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16313294#comment-16313294
]
Hadoop QA commented on AMBARI-22449:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12904774/AMBARI-22449_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 2 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:green}+1 core tests{color}. The patch passed unit tests in
ambari-server ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12930//console
This message is automatically generated.
> Improved service/component dependency support
> -
>
> Key: AMBARI-22449
> URL: https://issues.apache.org/jira/browse/AMBARI-22449
> Project: Ambari
> Issue Type: Task
> Components: ambari-server, ambari-web
>Affects Versions: 3.0.0
>Reporter: Attila Magyar
>Assignee: Attila Magyar
> Fix For: 3.0.0
>
> Attachments: AMBARI-22449.patch, AMBARI-22449_2.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22732) Make Select Metric dropdown in Create Widget wizard wider
[
https://issues.apache.org/jira/browse/AMBARI-22732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16313179#comment-16313179
]
Hadoop QA commented on AMBARI-22732:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12904799/AMBARI-22732.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12928//console
This message is automatically generated.
> Make Select Metric dropdown in Create Widget wizard wider
> -
>
> Key: AMBARI-22732
> URL: https://issues.apache.org/jira/browse/AMBARI-22732
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Minor
> Fix For: 3.0.0
>
> Attachments: AMBARI-22732.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22725) Update Hadoop RPC Encryption Properties During Kerberization and Upgrade
[
https://issues.apache.org/jira/browse/AMBARI-22725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16312724#comment-16312724
]
Hadoop QA commented on AMBARI-22725:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12904672/AMBARI-22725.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified test files.
{color:green}+1 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/12927//artifact/patch-work/testrun_ambari-server.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12927//console
This message is automatically generated.
> Update Hadoop RPC Encryption Properties During Kerberization and Upgrade
>
>
> Key: AMBARI-22725
> URL: https://issues.apache.org/jira/browse/AMBARI-22725
> Project: Ambari
> Issue Type: Task
>Affects Versions: 2.6.2
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.6.2
>
> Attachments: AMBARI-22725.patch
>
>
> Clients should have the ability to choose encrypted communication over RPC
> when talking to core hadoop components. Today, the properties that control
> this are:
> - {{core-site.xml : hadoop.rpc.protection = authentication}}
> - {{hdfs-site.xml : dfs.data.transfer.protection = authentication}}
> The new value of {{privacy}} enables clients to choose an encrypted means of
> communication. By keeping {{authentication}} first, it will be taken as the
> default mechanism so that wire encryption is not automatically enabled by
> accident.
> The following properties should be changed to add {{privacy}}:
> - {{core-site.xml : hadoop.rpc.protection = authentication,privacy}}
> - {{hdfs-site.xml : dfs.data.transfer.protection = authentication,privacy}}
> The following are cases when this needs to be performed:
> - During Kerberization, the above two properties should be automatically
> reconfigured.
> - During a stack upgrade to any version of HDP 2.6, they should be
> automatically merged
> Blueprint deployment is not a scenario being covered here.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22419) Ambari upgrade failed
[
https://issues.apache.org/jira/browse/AMBARI-22419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16312660#comment-16312660
]
Hadoop QA commented on AMBARI-22419:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12904731/AMBARI-22419.trunk.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12925//console
This message is automatically generated.
> Ambari upgrade failed
> -
>
> Key: AMBARI-22419
> URL: https://issues.apache.org/jira/browse/AMBARI-22419
> Project: Ambari
> Issue Type: Bug
> Components: ambari-sever
>Affects Versions: 2.6.0
>Reporter: amarnath reddy pappu
>Assignee: Dmytro Grinenko
> Fix For: 2.6.2
>
> Attachments: AMBARI-22419.branch-2.6.patch, AMBARI-22419.trunk.patch
>
>
> Ambari upgrade would fail during the DMLStatements execution if there is no
> service definition in the stacks.
> For example: Customer database has entry for GANGLIA in alert_definition
> table but there is no stack definition - hence its getting failed with below
> exception.
> {noformat}
> org.apache.ambari.server.AmbariException: Service not found,
> clusterName=comcastdrcluster, serviceName=GANGLIA
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:234)
>
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:424)
>
> Caused by: org.apache.ambari.server.ServiceNotFoundException: Service not
> found, clusterName=comcastdrcluster, serviceName=GANGLIA
> at
> org.apache.ambari.server.state.cluster.ClusterImpl.getService(ClusterImpl.java:864)
>
> at
> org.apache.ambari.server.api.services.AmbariMetaInfo.reconcileAlertDefinitions(AmbariMetaInfo.java:1240)
>
> at
> org.apache.ambari.server.upgrade.UpdateAlertScriptPaths.executeDMLUpdates(UpdateAlertScriptPaths.java:46)
>
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:938)
>
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:231)
>
> ... 1 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22656) Add slot info for Hosts page
[
https://issues.apache.org/jira/browse/AMBARI-22656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16312664#comment-16312664
]
Hadoop QA commented on AMBARI-22656:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12904738/AMBARI-22656_branch-2.5.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/12926//console
This message is automatically generated.
> Add slot info for Hosts page
>
>
> Key: AMBARI-22656
> URL: https://issues.apache.org/jira/browse/AMBARI-22656
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-agent, ambari-server, ambari-web
>Affects Versions: 2.5.2
>Reporter: mathildaMa09
> Fix For: 2.5.2
>
> Attachments: AMBARI-22656.patch, AMBARI-22656_branch-2.5.patch
>
>
> In Hosts Page lists info about hosts like Rack、IP、Cores、DiskUsage .etc, but I
> need more details about my hosts’ physical position, like slot for instance,
> to know exactly where my machine locates. So, in hosts page, we can add slot
> info to describe their location.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22419) Ambari upgrade failed
[
https://issues.apache.org/jira/browse/AMBARI-22419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16312641#comment-16312641
]
Hadoop QA commented on AMBARI-22419:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12904731/AMBARI-22419.trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12924//console
This message is automatically generated.
> Ambari upgrade failed
> -
>
> Key: AMBARI-22419
> URL: https://issues.apache.org/jira/browse/AMBARI-22419
> Project: Ambari
> Issue Type: Bug
> Components: ambari-sever
>Affects Versions: 2.6.0
>Reporter: amarnath reddy pappu
>Assignee: Dmytro Grinenko
> Fix For: 2.6.2
>
> Attachments: AMBARI-22419.branch-2.6.patch, AMBARI-22419.trunk.patch
>
>
> Ambari upgrade would fail during the DMLStatements execution if there is no
> service definition in the stacks.
> For example: Customer database has entry for GANGLIA in alert_definition
> table but there is no stack definition - hence its getting failed with below
> exception.
> {noformat}
> org.apache.ambari.server.AmbariException: Service not found,
> clusterName=comcastdrcluster, serviceName=GANGLIA
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:234)
>
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:424)
>
> Caused by: org.apache.ambari.server.ServiceNotFoundException: Service not
> found, clusterName=comcastdrcluster, serviceName=GANGLIA
> at
> org.apache.ambari.server.state.cluster.ClusterImpl.getService(ClusterImpl.java:864)
>
> at
> org.apache.ambari.server.api.services.AmbariMetaInfo.reconcileAlertDefinitions(AmbariMetaInfo.java:1240)
>
> at
> org.apache.ambari.server.upgrade.UpdateAlertScriptPaths.executeDMLUpdates(UpdateAlertScriptPaths.java:46)
>
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:938)
>
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:231)
>
> ... 1 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22699) Update FE to initiate regenerate keytab file operations for a service and a host
[
https://issues.apache.org/jira/browse/AMBARI-22699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16311741#comment-16311741
]
Hadoop QA commented on AMBARI-22699:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12904615/AMBARI-22699.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/12923//console
This message is automatically generated.
> Update FE to initiate regenerate keytab file operations for a service and a
> host
>
>
> Key: AMBARI-22699
> URL: https://issues.apache.org/jira/browse/AMBARI-22699
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 3.0.0
>
> Attachments: AMBARI-22699.patch
>
>
> Update FE to initiate regenerate keytab file operations for a service and a
> host.
> An option needs to be added to the Actions menu of a service to regenerate
> all keytab file for that service. The Ambari REST API call to initiate this
> is:
> {code}
> PUT
> /api/v1/clusters/CLUSTERNAME?regenerate_keytabs=all_components=SERVICENAME:*
> {
> "Clusters": {
> "security_type" : "KERBEROS"
> }
> }
> {code}
> NOTE: CLUSTERNAME and SERVICENAME need to be replaced with the appropriate
> values.
> An option needs to be added to the Host Actions menu of a host to regenerate
> all keytab file for that host. The Ambari REST API call to initiate this is:
> {code}
> PUT
> /api/v1/clusters/CLUSTERNAME?regenerate_keytabs=all_hosts=HOSTNAME:*
> {
> "Clusters": {
> "security_type" : "KERBEROS"
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22723) Ambari Upgrade failed in case if database have no cluster_version table already. The issue with idempotence
[
https://issues.apache.org/jira/browse/AMBARI-22723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16311739#comment-16311739
]
Hadoop QA commented on AMBARI-22723:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12904605/AMBARI-22723.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/12922//console
This message is automatically generated.
> Ambari Upgrade failed in case if database have no cluster_version table
> already. The issue with idempotence
> ---
>
> Key: AMBARI-22723
> URL: https://issues.apache.org/jira/browse/AMBARI-22723
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.1
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Fix For: 2.6.2
>
> Attachments: AMBARI-22723.patch
>
>
> AMBARI-21728 and AMBARI-22469 make the upgrade broken in case of several
> upgrade tries, failing to follow the Idempotent upgrade paradigm.
> Issue is with:
> {code}
> protected void executeDDLUpdates() throws AmbariException, SQLException {
> Integer currentVersionID = getCurrentVersionID();<--
> dropBrokenFK();
> updateServiceComponentDesiredStateTable(currentVersionID);
> <--
> updateServiceDesiredStateTable(currentVersionID); <--
> addSelectedCollumsToClusterconfigTable();
> updateHostComponentDesiredStateTable();
> updateHostComponentStateTable();
> dropStaleTables(); <--
> updateUpgradeTable();
> createUpgradeHistoryTable();
> updateRepositoryVersionTable();
> renameServiceDeletedColumn();
> addLegacyColumn();
> expandUpgradeItemItemTextColumn();
> addViewUrlPKConstraint();
> removeStaleConstraints();
> }
> {code}
> {{getCurrentVersionID()}} trying to query non-existing table and failing
> whole upgrade
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22699) Update FE to initiate regenerate keytab file operations for a service and a host
[
https://issues.apache.org/jira/browse/AMBARI-22699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16311537#comment-16311537
]
Hadoop QA commented on AMBARI-22699:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12904615/AMBARI-22699.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:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12921//console
This message is automatically generated.
> Update FE to initiate regenerate keytab file operations for a service and a
> host
>
>
> Key: AMBARI-22699
> URL: https://issues.apache.org/jira/browse/AMBARI-22699
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 3.0.0
>
> Attachments: AMBARI-22699.patch
>
>
> Update FE to initiate regenerate keytab file operations for a service and a
> host.
> An option needs to be added to the Actions menu of a service to regenerate
> all keytab file for that service. The Ambari REST API call to initiate this
> is:
> {code}
> PUT
> /api/v1/clusters/CLUSTERNAME?regenerate_keytabs=all_components=SERVICENAME:*
> {
> "Clusters": {
> "security_type" : "KERBEROS"
> }
> }
> {code}
> NOTE: CLUSTERNAME and SERVICENAME need to be replaced with the appropriate
> values.
> An option needs to be added to the Host Actions menu of a host to regenerate
> all keytab file for that host. The Ambari REST API call to initiate this is:
> {code}
> PUT
> /api/v1/clusters/CLUSTERNAME?regenerate_keytabs=all_hosts=HOSTNAME:*
> {
> "Clusters": {
> "security_type" : "KERBEROS"
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22699) Update FE to initiate regenerate keytab file operations for a service and a host
[
https://issues.apache.org/jira/browse/AMBARI-22699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16311472#comment-16311472
]
Hadoop QA commented on AMBARI-22699:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12904610/AMBARI-22699.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:red}-1 core tests{color}. The test build failed in
[ambari-web|https://builds.apache.org/job/Ambari-trunk-test-patch/12920//artifact/patch-work/testrun_ambari-web.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12920//console
This message is automatically generated.
> Update FE to initiate regenerate keytab file operations for a service and a
> host
>
>
> Key: AMBARI-22699
> URL: https://issues.apache.org/jira/browse/AMBARI-22699
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 3.0.0
>
> Attachments: AMBARI-22699.patch
>
>
> Update FE to initiate regenerate keytab file operations for a service and a
> host.
> An option needs to be added to the Actions menu of a service to regenerate
> all keytab file for that service. The Ambari REST API call to initiate this
> is:
> {code}
> PUT
> /api/v1/clusters/CLUSTERNAME?regenerate_keytabs=all_components=SERVICENAME:*
> {
> "Clusters": {
> "security_type" : "KERBEROS"
> }
> }
> {code}
> NOTE: CLUSTERNAME and SERVICENAME need to be replaced with the appropriate
> values.
> An option needs to be added to the Host Actions menu of a host to regenerate
> all keytab file for that host. The Ambari REST API call to initiate this is:
> {code}
> PUT
> /api/v1/clusters/CLUSTERNAME?regenerate_keytabs=all_hosts=HOSTNAME:*
> {
> "Clusters": {
> "security_type" : "KERBEROS"
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22656) Add slot info for Hosts page
[
https://issues.apache.org/jira/browse/AMBARI-22656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16311384#comment-16311384
]
Hadoop QA commented on AMBARI-22656:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12904510/AMBARI-22656.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/12919//console
This message is automatically generated.
> Add slot info for Hosts page
>
>
> Key: AMBARI-22656
> URL: https://issues.apache.org/jira/browse/AMBARI-22656
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-agent, ambari-server, ambari-web
>Affects Versions: 2.5.2
>Reporter: mathildaMa09
> Fix For: 2.5.2
>
> Attachments: AMBARI-22656.patch
>
>
> In Hosts Page lists info about hosts like Rack、IP、Cores、DiskUsage .etc, but I
> need more details about my hosts’ physical position, like slot for instance,
> to know exactly where my machine locates. So, in hosts page, we can add slot
> info to describe their location.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22419) Ambari upgrade failed
[
https://issues.apache.org/jira/browse/AMBARI-22419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16311380#comment-16311380
]
Hadoop QA commented on AMBARI-22419:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12904555/AMBARI-22419.branch-2.6.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:red}-1 javac{color}. The patch appears to cause the [build to
fail|https://builds.apache.org/job/Ambari-trunk-test-patch/12918//artifact/patch-work/patchJavacWarnings.txt].
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12918//console
This message is automatically generated.
> Ambari upgrade failed
> -
>
> Key: AMBARI-22419
> URL: https://issues.apache.org/jira/browse/AMBARI-22419
> Project: Ambari
> Issue Type: Bug
> Components: ambari-sever
>Affects Versions: 2.6.0
>Reporter: amarnath reddy pappu
>Assignee: Dmytro Grinenko
> Fix For: 2.6.2
>
> Attachments: AMBARI-22419.branch-2.6.patch
>
>
> Ambari upgrade would fail during the DMLStatements execution if there is no
> service definition in the stacks.
> For example: Customer database has entry for GANGLIA in alert_definition
> table but there is no stack definition - hence its getting failed with below
> exception.
> {noformat}
> org.apache.ambari.server.AmbariException: Service not found,
> clusterName=comcastdrcluster, serviceName=GANGLIA
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:234)
>
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:424)
>
> Caused by: org.apache.ambari.server.ServiceNotFoundException: Service not
> found, clusterName=comcastdrcluster, serviceName=GANGLIA
> at
> org.apache.ambari.server.state.cluster.ClusterImpl.getService(ClusterImpl.java:864)
>
> at
> org.apache.ambari.server.api.services.AmbariMetaInfo.reconcileAlertDefinitions(AmbariMetaInfo.java:1240)
>
> at
> org.apache.ambari.server.upgrade.UpdateAlertScriptPaths.executeDMLUpdates(UpdateAlertScriptPaths.java:46)
>
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:938)
>
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:231)
>
> ... 1 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22716) zeppelin.livy.url is not getting updated after moving livy to a new host
[
https://issues.apache.org/jira/browse/AMBARI-22716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16309540#comment-16309540
]
Hadoop QA commented on AMBARI-22716:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12904267/0AMBARI-22716_branch-2.6_v1.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/12917//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12917//console
This message is automatically generated.
> zeppelin.livy.url is not getting updated after moving livy to a new host
>
>
> Key: AMBARI-22716
> URL: https://issues.apache.org/jira/browse/AMBARI-22716
> Project: Ambari
> Issue Type: Bug
> Components: ambari-sever
>Affects Versions: 2.6.1
> Environment: ambari-server --version 2.6.1.0-137
> HDP-2.6.4.0-86
>Reporter: Supreeth Sharma
>Assignee: Prabhjyot Singh
>Priority: Critical
> Fix For: 2.6.1
>
> Attachments: 0AMBARI-22716_branch-2.6_v1.patch,
> 0AMBARI-22716_trunk_v1.patch
>
>
> zeppelin.livy.url is not getting updated after moving livy to a new host
> Steps to reproduce :
> 1) Create a cluster with both Spark and Spark2 component
> 2) Delete livy component from current host.
> 3) Add the livy component on a new host
> 4) Restart zeppelin server.
> 5) Now check the zeppelin interpreter settings. zeppelin.livy.url is still
> referring to older livy host.
> Its not reflecting the new livy server address.
> Note 1 : If I restart zeppelin server after step1 (ie after deleting the livy
> host) before performing rest of the steps, then changes are getting reflected
> properly. System test was mistakenly doing this step so didn't fail during
> nightly run
> Note 2 : Issue is happening only when both Spark and Spark2 are installed. If
> cluster contains only Spark2, this feature works as expected.
> Issue is coming if I add Spark(version 1) to it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22403) Read the JAVA_HOME depending on the OS family during Service install (action & command) and upgrade
[
https://issues.apache.org/jira/browse/AMBARI-22403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16309538#comment-16309538
]
Hadoop QA commented on AMBARI-22403:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12904349/AMBARI-22403.001.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 8 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:red}-1 javac{color}. The patch appears to cause the [build to
fail|https://builds.apache.org/job/Ambari-trunk-test-patch/12916//artifact/patch-work/patchJavacWarnings.txt].
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12916//console
This message is automatically generated.
> Read the JAVA_HOME depending on the OS family during Service install (action
> & command) and upgrade
> ---
>
> Key: AMBARI-22403
> URL: https://issues.apache.org/jira/browse/AMBARI-22403
> Project: Ambari
> Issue Type: Sub-task
> Components: ambari-server
>Reporter: Yussuf Shaikh
>Assignee: Yussuf Shaikh
> Attachments: AMBARI-22403.001.patch
>
>
> Use of proper java_home value during service install and configuration base
> on host OS type.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22718) Cannot set security.inter.broker.protocol: SASL_SSL via Blueprint with Kerberos
[
https://issues.apache.org/jira/browse/AMBARI-22718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16309523#comment-16309523
]
Hadoop QA commented on AMBARI-22718:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12904364/AMBARI-22718.trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 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:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12915//console
This message is automatically generated.
> Cannot set security.inter.broker.protocol: SASL_SSL via Blueprint with
> Kerberos
> ---
>
> Key: AMBARI-22718
> URL: https://issues.apache.org/jira/browse/AMBARI-22718
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.6.1
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0, 2.6.2
>
> Attachments: AMBARI-22718.branch-2.6.patch, AMBARI-22718.trunk.patch
>
>
> STR:
> # Install Ambari 2.6.1
> # Tweak {{stack_features.json}} to lower {{min_version}} for
> {{kafka_extended_sasl_support}}
> # Create secure cluster via blueprint (ZooKeeper + Kafka) with
> {{security.inter.broker.protocol: SASL_SSL}}
> Result: Kafka Brokers stopped due to missing {{kafka_jaas.conf}}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22406) UI for verifying if repo exist for new OS family and user prompt for entering HDP and HDP-UTILs repo URLs
[
https://issues.apache.org/jira/browse/AMBARI-22406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16308307#comment-16308307
]
Hadoop QA commented on AMBARI-22406:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12904234/AMBARI-22406.002.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-web|https://builds.apache.org/job/Ambari-trunk-test-patch/12914//artifact/patch-work/testrun_ambari-web.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12914//console
This message is automatically generated.
> UI for verifying if repo exist for new OS family and user prompt for entering
> HDP and HDP-UTILs repo URLs
> -
>
> Key: AMBARI-22406
> URL: https://issues.apache.org/jira/browse/AMBARI-22406
> Project: Ambari
> Issue Type: Sub-task
> Components: ambari-web
>Reporter: Yussuf Shaikh
>Assignee: Yussuf Shaikh
> Attachments: AMBARI-22406.002.patch, AMBARI-22406.patch
>
>
> This will include UI changes in ambari-web to check if the repo is selected
> or provide prompt to the user to enter the HDP and HDP-utils repo URL's.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22711) Ambari Versions Page is having JS error When using redhat satellite server for repos
[
https://issues.apache.org/jira/browse/AMBARI-22711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16308232#comment-16308232
]
Hadoop QA commented on AMBARI-22711:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12904228/AMBARI-22711.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:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12913//console
This message is automatically generated.
> Ambari Versions Page is having JS error When using redhat satellite server
> for repos
> --
>
> Key: AMBARI-22711
> URL: https://issues.apache.org/jira/browse/AMBARI-22711
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.2
> Environment: upgraded ambari Server from 2.4.2 to 2.5.2
>Reporter: Akhil S Naik
> Fix For: 3.0.0
>
> Attachments: AMBARI-22711.patch, Ambari_versions_page.png
>
>
> Ambari Versions page not updating when using Redhat satellite server for repos
> Versions page was showing up like below
> !https://issues.apache.org/jira/secure/attachment/12904190/Ambari_versions_page.png!
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22712) Update install Wizard layout
[
https://issues.apache.org/jira/browse/AMBARI-22712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16308179#comment-16308179
]
Hadoop QA commented on AMBARI-22712:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12904227/AMBARI-22712_fixed.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-web|https://builds.apache.org/job/Ambari-trunk-test-patch/12912//artifact/patch-work/testrun_ambari-web.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12912//console
This message is automatically generated.
> Update install Wizard layout
>
>
> Key: AMBARI-22712
> URL: https://issues.apache.org/jira/browse/AMBARI-22712
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-22712.patch, AMBARI-22712_fixed.patch
>
>
> Fix styles and markup issues.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22713) TestZeppelin070.test_start_secured UT failing on trunk
[
https://issues.apache.org/jira/browse/AMBARI-22713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16308125#comment-16308125
]
Hadoop QA commented on AMBARI-22713:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12904213/AMBARI-22713.trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 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/12911//artifact/patch-work/testrun_ambari-server.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12911//console
This message is automatically generated.
> TestZeppelin070.test_start_secured UT failing on trunk
> --
>
> Key: AMBARI-22713
> URL: https://issues.apache.org/jira/browse/AMBARI-22713
> Project: Ambari
> Issue Type: Bug
> Components: ambari-sever
>Affects Versions: trunk
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-22713.trunk.patch
>
>
> {code}
> Failure
> Traceback (most recent call last):
> File "/usr/lib/python2.7/unittest/case.py", line 329, in run
> testMethod()
> File
> "/opt/TeamCity/work/794a9bdcb9f19074/ambari-common/src/test/python/mock/mock.py",
> line 1199, in patched
> return func(*args, **keywargs)
> File
> "/opt/TeamCity/work/794a9bdcb9f19074/ambari-server/src/test/python/stacks/2.6/ZEPPELIN/test_zeppelin_070.py",
> line 239, in test_start_secured
> recursive_chmod=True
> File
> "/opt/TeamCity/work/794a9bdcb9f19074/ambari-server/src/test/python/stacks/utils/RMFTestCase.py",
> line 343, in assertResourceCalled
> self.assertEquals(kwargs, resource.arguments)
> File "/usr/lib/python2.7/unittest/case.py", line 513, in assertEqual
> assertion_func(first, second, msg=msg)
> File "/usr/lib/python2.7/unittest/case.py", line 835, in assertDictEqual
> self.fail(self._formatMessage(msg, standardMsg))
> File "/usr/lib/python2.7/unittest/case.py", line 410, in fail
> raise self.failureException(msg)
> AssertionError: {'security_enabled': False, 'hadoop_conf_dir':
> '/usr/hdp/2.5.0.0-1235/hadoop/con [truncated]... != {'security_enabled':
> False, 'hadoop_bin_dir': '/usr/hdp/current/hadoop-client/bi [truncated]...
> {'action': ['create_on_execute'],
>'default_fs': u'hdfs://c6401.ambari.apache.org:8020',
> - 'hadoop_bin_dir': '/usr/hdp/2.5.0.0-1235/hadoop/bin',
> ?
> + 'hadoop_bin_dir': '/usr/hdp/current/hadoop-client/bin',
> ? ^^^ +++
> - 'hadoop_conf_dir': '/usr/hdp/2.5.0.0-1235/hadoop/conf',
> ?
> + 'hadoop_conf_dir': '/usr/hdp/current/hadoop-client/conf',
> ? ^^^ +++
>'hdfs_resource_ignore_file':
> '/var/lib/ambari-agent/data/.hdfs_resource_ignore',
>'hdfs_site': {u'a': u'b'},
> - 'keytab': UnknownConfigurationMock(),
> ?
> + 'keytab': UnknownConfiguration(),
>'kinit_path_local': '/usr/bin/kinit',
> - 'owner': 'zeppelin',
> + 'owner': u'zeppelin',
> ? +
> - 'principal_name': UnknownConfigurationMock(),
> ?
> + 'principal_name': UnknownConfiguration(),
>'recursive_chmod': True,
>'recursive_chown': True,
>'security_enabled': False,
>'type': 'directory',
> - 'user': 'hdfs'}
> + 'user': u'hdfs'}
> ? +
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22714) Log Search UI: implement Summary tab for Access Logs page
[
https://issues.apache.org/jira/browse/AMBARI-22714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16308088#comment-16308088
]
Hadoop QA commented on AMBARI-22714:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12904221/AMBARI-22714.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-logsearch/ambari-logsearch-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12910//console
This message is automatically generated.
> Log Search UI: implement Summary tab for Access Logs page
> -
>
> Key: AMBARI-22714
> URL: https://issues.apache.org/jira/browse/AMBARI-22714
> Project: Ambari
> Issue Type: Task
> Components: ambari-logsearch
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-22714.patch
>
>
> Implement Summary tab with two diagrams: Top 6 users and Top 10 resources.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22714) Log Search UI: implement Summary tab for Access Logs page
[
https://issues.apache.org/jira/browse/AMBARI-22714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16308053#comment-16308053
]
Hadoop QA commented on AMBARI-22714:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12904221/AMBARI-22714.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-logsearch/ambari-logsearch-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12909//console
This message is automatically generated.
> Log Search UI: implement Summary tab for Access Logs page
> -
>
> Key: AMBARI-22714
> URL: https://issues.apache.org/jira/browse/AMBARI-22714
> Project: Ambari
> Issue Type: Task
> Components: ambari-logsearch
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-22714.patch
>
>
> Implement Summary tab with two diagrams: Top 6 users and Top 10 resources.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22713) TestZeppelin070.test_start_secured UT failing on trunk
[
https://issues.apache.org/jira/browse/AMBARI-22713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16307963#comment-16307963
]
Hadoop QA commented on AMBARI-22713:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12904213/AMBARI-22713.trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 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/12908//artifact/patch-work/testrun_ambari-server.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12908//console
This message is automatically generated.
> TestZeppelin070.test_start_secured UT failing on trunk
> --
>
> Key: AMBARI-22713
> URL: https://issues.apache.org/jira/browse/AMBARI-22713
> Project: Ambari
> Issue Type: Bug
> Components: ambari-sever
>Affects Versions: trunk
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-22713.trunk.patch
>
>
> {code}
> Failure
> Traceback (most recent call last):
> File "/usr/lib/python2.7/unittest/case.py", line 329, in run
> testMethod()
> File
> "/opt/TeamCity/work/794a9bdcb9f19074/ambari-common/src/test/python/mock/mock.py",
> line 1199, in patched
> return func(*args, **keywargs)
> File
> "/opt/TeamCity/work/794a9bdcb9f19074/ambari-server/src/test/python/stacks/2.6/ZEPPELIN/test_zeppelin_070.py",
> line 239, in test_start_secured
> recursive_chmod=True
> File
> "/opt/TeamCity/work/794a9bdcb9f19074/ambari-server/src/test/python/stacks/utils/RMFTestCase.py",
> line 343, in assertResourceCalled
> self.assertEquals(kwargs, resource.arguments)
> File "/usr/lib/python2.7/unittest/case.py", line 513, in assertEqual
> assertion_func(first, second, msg=msg)
> File "/usr/lib/python2.7/unittest/case.py", line 835, in assertDictEqual
> self.fail(self._formatMessage(msg, standardMsg))
> File "/usr/lib/python2.7/unittest/case.py", line 410, in fail
> raise self.failureException(msg)
> AssertionError: {'security_enabled': False, 'hadoop_conf_dir':
> '/usr/hdp/2.5.0.0-1235/hadoop/con [truncated]... != {'security_enabled':
> False, 'hadoop_bin_dir': '/usr/hdp/current/hadoop-client/bi [truncated]...
> {'action': ['create_on_execute'],
>'default_fs': u'hdfs://c6401.ambari.apache.org:8020',
> - 'hadoop_bin_dir': '/usr/hdp/2.5.0.0-1235/hadoop/bin',
> ?
> + 'hadoop_bin_dir': '/usr/hdp/current/hadoop-client/bin',
> ? ^^^ +++
> - 'hadoop_conf_dir': '/usr/hdp/2.5.0.0-1235/hadoop/conf',
> ?
> + 'hadoop_conf_dir': '/usr/hdp/current/hadoop-client/conf',
> ? ^^^ +++
>'hdfs_resource_ignore_file':
> '/var/lib/ambari-agent/data/.hdfs_resource_ignore',
>'hdfs_site': {u'a': u'b'},
> - 'keytab': UnknownConfigurationMock(),
> ?
> + 'keytab': UnknownConfiguration(),
>'kinit_path_local': '/usr/bin/kinit',
> - 'owner': 'zeppelin',
> + 'owner': u'zeppelin',
> ? +
> - 'principal_name': UnknownConfigurationMock(),
> ?
> + 'principal_name': UnknownConfiguration(),
>'recursive_chmod': True,
>'recursive_chown': True,
>'security_enabled': False,
>'type': 'directory',
> - 'user': 'hdfs'}
> + 'user': u'hdfs'}
> ? +
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22712) Update install Wizard layout
[
https://issues.apache.org/jira/browse/AMBARI-22712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16307937#comment-16307937
]
Hadoop QA commented on AMBARI-22712:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12904210/AMBARI-22712.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/12907//console
This message is automatically generated.
> Update install Wizard layout
>
>
> Key: AMBARI-22712
> URL: https://issues.apache.org/jira/browse/AMBARI-22712
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-22712.patch
>
>
> Fix styles and markup issues.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22711) Ambari Versions Page is having JS error When using redhat satellite server for repos
[
https://issues.apache.org/jira/browse/AMBARI-22711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16307936#comment-16307936
]
Hadoop QA commented on AMBARI-22711:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12904193/AMBARI-22711.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:red}-1 core tests{color}. The test build failed in
[ambari-web|https://builds.apache.org/job/Ambari-trunk-test-patch/12906//artifact/patch-work/testrun_ambari-web.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12906//console
This message is automatically generated.
> Ambari Versions Page is having JS error When using redhat satellite server
> for repos
> --
>
> Key: AMBARI-22711
> URL: https://issues.apache.org/jira/browse/AMBARI-22711
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.2
> Environment: upgraded ambari Server from 2.4.2 to 2.5.2
>Reporter: Akhil S Naik
> Fix For: 3.0.0
>
> Attachments: AMBARI-22711.patch, Ambari_versions_page.png
>
>
> Ambari Versions page not updating when using Redhat satellite server for repos
> Versions page was showing up like below
> !https://issues.apache.org/jira/secure/attachment/12904190/Ambari_versions_page.png!
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22698) Custom zeppelin interpreter properties are getting removed after moving zeppelin to a different host
[
https://issues.apache.org/jira/browse/AMBARI-22698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16306440#comment-16306440
]
Hadoop QA commented on AMBARI-22698:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12903894/AMBARI-22698_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 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12905//console
This message is automatically generated.
> Custom zeppelin interpreter properties are getting removed after moving
> zeppelin to a different host
>
>
> Key: AMBARI-22698
> URL: https://issues.apache.org/jira/browse/AMBARI-22698
> Project: Ambari
> Issue Type: Bug
> Components: ambari-sever
>Affects Versions: 2.6.1
> Environment: ambari-server --version 2.6.1.0-136
> HDP-2.6.4.0-85
>Reporter: Supreeth Sharma
>Assignee: Prabhjyot Singh
>Priority: Blocker
> Attachments: AMBARI-22698_trunk_v1.patch
>
>
> Custom zeppelin interpreter properties are getting lost after moving zeppelin
> to a different host
> Live Cluster : https://172.27.12.130:8443
> Steps to reproduce :
> 1) Modify interpreter settings
> a) Add new custom properties
> b) Modify existing properties
> Changes are getting saved in HDFS path /user/zeppelin/conf/interpreter.json
> and they are getting synced to local path /etc/zeppelin/conf/interpreter.json
> after zeppelin restart.
> 2) Delete zeppelin server
> 3) Install zeppelin server on a different host
> 4) Modifications done in step 1 are lost.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22704) Stack unit test fixes
[
https://issues.apache.org/jira/browse/AMBARI-22704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16306420#comment-16306420
]
Hadoop QA commented on AMBARI-22704:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12903889/AMBARI-22704.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/12904//console
This message is automatically generated.
> Stack unit test fixes
> -
>
> Key: AMBARI-22704
> URL: https://issues.apache.org/jira/browse/AMBARI-22704
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-22704.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22706) Ranger installation fails
[
https://issues.apache.org/jira/browse/AMBARI-22706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16306418#comment-16306418
]
Hadoop QA commented on AMBARI-22706:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12903900/AMBARI-22706.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/12903//console
This message is automatically generated.
> Ranger installation fails
> -
>
> Key: AMBARI-22706
> URL: https://issues.apache.org/jira/browse/AMBARI-22706
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-22706.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22656) Add slot info for Hosts page
[
https://issues.apache.org/jira/browse/AMBARI-22656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16306417#comment-16306417
]
Hadoop QA commented on AMBARI-22656:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12903991/AMBARI-22656_branch-2.5.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/12902//console
This message is automatically generated.
> Add slot info for Hosts page
>
>
> Key: AMBARI-22656
> URL: https://issues.apache.org/jira/browse/AMBARI-22656
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-agent, ambari-server, ambari-web
>Affects Versions: 2.5.2
>Reporter: mathildaMa09
> Fix For: 2.5.2
>
> Attachments: AMBARI-22656.patch, AMBARI-22656_branch-2.5.patch
>
>
> In Hosts Page lists info about hosts like Rack、IP、Cores、DiskUsage .etc, but I
> need more details about my hosts’ physical position, like slot for instance,
> to know exactly where my machine locates. So, in hosts page, we can add slot
> info to describe their location.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22710) Post-install: Create Widget wizard style fixes
[
https://issues.apache.org/jira/browse/AMBARI-22710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16306306#comment-16306306
]
Hadoop QA commented on AMBARI-22710:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12904014/AMBARI-22710.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12901//console
This message is automatically generated.
> Post-install: Create Widget wizard style fixes
> --
>
> Key: AMBARI-22710
> URL: https://issues.apache.org/jira/browse/AMBARI-22710
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-22710.patch
>
>
> Issues:
> # Show whole metric name in dropdown Add Metric
> # Hide breadcrumb of step for Create Widget wizard
> # Add shadow in Widget Browser modal
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22625) Non DFS Used from HDFS Namenode UI and HDFS summary in Ambari is different
[
https://issues.apache.org/jira/browse/AMBARI-22625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16304668#comment-16304668
]
Hadoop QA commented on AMBARI-22625:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12903811/AMBARI-22625-trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12900//console
This message is automatically generated.
> Non DFS Used from HDFS Namenode UI and HDFS summary in Ambari is different
> ---
>
> Key: AMBARI-22625
> URL: https://issues.apache.org/jira/browse/AMBARI-22625
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.2
>Reporter: Akhil S Naik
>Priority: Minor
> Fix For: 2.6.0
>
> Attachments: AMBARI-22625-trunk.patch, ambari-2.png, namenode.png
>
>
> 'NON DFS Used' value in Services -> HDFS -> Summary if different from the
> Value shown in NameNode UI (see Picture).
> in NAMENODE UI -->
> !https://issues.apache.org/jira/secure/attachment/12901501/namenode.png!
> In Services -> HDFS -> Summary
> !https://issues.apache.org/jira/secure/attachment/12901499/ambari-2.png!
> In NameNode UI the Non DFS Used is taken from 'NonDfsUsedSpace' variable from
> REST API call :
> http://host1:50070/jmx?qry=Hadoop:service=NameNode,name=NameNodeInfo
> Where host1 is the Name Node Server FQDN
> but in Ambari we are calculating the same value from (Total Allocated - DFS
> USed - DFS Remaining) .
> due to which this issue is happening.
> as a Fix we need to use the 'capacityNonDfsUsed' which comes from Server in
> NameNode metrics
> 'FSNamesystem > CapacityNonDFSUsed'
> attached the patch in the JIRA.
> Please fix this bug
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22693) UpgradeUserKerberosDescriptor is not executed during stack upgrade due to missing target stack data
[
https://issues.apache.org/jira/browse/AMBARI-22693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16304648#comment-16304648
]
Hadoop QA commented on AMBARI-22693:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12903816/AMBARI-22693_branch-2.6.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/12899//console
This message is automatically generated.
> UpgradeUserKerberosDescriptor is not executed during stack upgrade due to
> missing target stack data
> ---
>
> Key: AMBARI-22693
> URL: https://issues.apache.org/jira/browse/AMBARI-22693
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0, 2.6.1
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Fix For: 2.6.2
>
> Attachments: AMBARI-22693_branch-2.6.patch
>
>
> UpgradeUserKerberosDescriptor is not executed during stack upgrade due to
> missing target stack data.
> *Steps to reproduce*
> # Deploy cluster with Ambari version 2.6.0 and HDP version 2.4
> ** Storm should be installed to guarantee an error
> # Do Express upgrade to HDP version 2.6
> # Regenerate Keytabs.
> Upon restarting Storm the following error is encountered
> {code:java}
> Exception in thread "main" java.lang.ExceptionInInitializerError
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at clojure.lang.RT.classForName(RT.java:2154)
> at clojure.lang.RT.classForName(RT.java:2163)
> at clojure.lang.RT.loadClassForName(RT.java:2182)
> at clojure.lang.RT.load(RT.java:436)
> at clojure.lang.RT.load(RT.java:412)
> at clojure.core$load$fn__5448.invoke(core.clj:5866)
> at clojure.core$load.doInvoke(core.clj:5865)
> at clojure.lang.RestFn.invoke(RestFn.java:408)
> at clojure.core$load_one.invoke(core.clj:5671)
> at clojure.core$load_lib$fn__5397.invoke(core.clj:5711)
> at clojure.core$load_lib.doInvoke(core.clj:5710)
> at clojure.lang.RestFn.applyTo(RestFn.java:142)
> at clojure.core$apply.invoke(core.clj:632)
> at clojure.core$load_libs.doInvoke(core.clj:5749)
> at clojure.lang.RestFn.applyTo(RestFn.java:137)
> at clojure.core$apply.invoke(core.clj:632)
> at clojure.core$require.doInvoke(core.clj:5832)
> at clojure.lang.RestFn.invoke(RestFn.java:408)
> at
> org.apache.storm.daemon.nimbus$loading__5340__auto982.invoke(nimbus.clj:16)
> at org.apache.storm.daemon.nimbus__init.load(Unknown Source)
> at org.apache.storm.daemon.nimbus__init.(Unknown Source)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at clojure.lang.RT.classForName(RT.java:2154)
> at clojure.lang.RT.classForName(RT.java:2163)
> at clojure.lang.RT.loadClassForName(RT.java:2182)
> at clojure.lang.RT.load(RT.java:436)
> at clojure.lang.RT.load(RT.java:412)
> at clojure.core$load$fn__5448.invoke(core.clj:5866)
> at clojure.core$load.doInvoke(core.clj:5865)
> at clojure.lang.RestFn.invoke(RestFn.java:408)
> at clojure.lang.Var.invoke(Var.java:379)
> at org.apache.storm.daemon.nimbus.(Unknown Source)
> Caused by: java.lang.RuntimeException: java.lang.ClassNotFoundException:
> backtype.storm.security.auth.KerberosPrincipalToLocal
> at
> org.apache.storm.security.auth.AuthUtils.GetPrincipalToLocalPlugin(AuthUtils.java:125)
> at
> org.apache.storm.security.auth.authorizer.ImpersonationAuthorizer.prepare(ImpersonationAuthorizer.java:54)
> at
> org.apache.storm.daemon.common$mk_authorization_handler.invoke(common.clj:417)
> at org.apache.storm.ui.core__init.load(Unknown Source)
> at org.apache.storm.ui.core__init.(Unknown Source)
> ... 35 more
> Caused by: java.lang.ClassNotFoundException:
> backtype.storm.security.auth.KerberosPrincipalToLocal
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at
> org.apache.storm.security.auth.AuthUtils.GetPrincipalToLocalPlugin(AuthUtils.java:121)
> ... 39 more
> {code}
> *Cause*
> In the following code snip, {{targetStackID}} is {null}}:
>
[jira] [Commented] (AMBARI-22700) Post-install: UI style fixes
[
https://issues.apache.org/jira/browse/AMBARI-22700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16304599#comment-16304599
]
Hadoop QA commented on AMBARI-22700:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12903814/AMBARI-22700.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12897//console
This message is automatically generated.
> Post-install: UI style fixes
>
>
> Key: AMBARI-22700
> URL: https://issues.apache.org/jira/browse/AMBARI-22700
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-22700.patch
>
>
> Issues:
> # Unknown color of service in navigation should be yellow
> # Remove left-right pad from Background Operations content
> # Status dropdown in Background Operations should be styled
> # Clicking on cluster name shouldn't open Background Operations
> # Align dropdowns on Configs page
> # Accordions in Compare mode missing arrow icon
> # Restart required icons thrown on the next line in firefox
> # Equalize padding of widget title
> # Add padding for wizard modals
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22625) Non DFS Used from HDFS Namenode UI and HDFS summary in Ambari is different
[
https://issues.apache.org/jira/browse/AMBARI-22625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16304574#comment-16304574
]
Hadoop QA commented on AMBARI-22625:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12903811/AMBARI-22625-trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12895//console
This message is automatically generated.
> Non DFS Used from HDFS Namenode UI and HDFS summary in Ambari is different
> ---
>
> Key: AMBARI-22625
> URL: https://issues.apache.org/jira/browse/AMBARI-22625
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.2
>Reporter: Akhil S Naik
>Priority: Minor
> Fix For: 2.6.0
>
> Attachments: AMBARI-22625-trunk.patch, ambari-2.png, namenode.png
>
>
> 'NON DFS Used' value in Services -> HDFS -> Summary if different from the
> Value shown in NameNode UI (see Picture).
> in NAMENODE UI -->
> !https://issues.apache.org/jira/secure/attachment/12901501/namenode.png!
> In Services -> HDFS -> Summary
> !https://issues.apache.org/jira/secure/attachment/12901499/ambari-2.png!
> In NameNode UI the Non DFS Used is taken from 'NonDfsUsedSpace' variable from
> REST API call :
> http://host1:50070/jmx?qry=Hadoop:service=NameNode,name=NameNodeInfo
> Where host1 is the Name Node Server FQDN
> but in Ambari we are calculating the same value from (Total Allocated - DFS
> USed - DFS Remaining) .
> due to which this issue is happening.
> as a Fix we need to use the 'capacityNonDfsUsed' which comes from Server in
> NameNode metrics
> 'FSNamesystem > CapacityNonDFSUsed'
> attached the patch in the JIRA.
> Please fix this bug
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22696) Whitelist execute latency from Storm Ambari metrics
[
https://issues.apache.org/jira/browse/AMBARI-22696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16303475#comment-16303475
]
Hadoop QA commented on AMBARI-22696:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12903609/AMBARI-22696-branch-2.6.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/12894//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12894//console
This message is automatically generated.
> Whitelist execute latency from Storm Ambari metrics
> ---
>
> Key: AMBARI-22696
> URL: https://issues.apache.org/jira/browse/AMBARI-22696
> Project: Ambari
> Issue Type: Bug
>Affects Versions: trunk, 2.6.2
>Reporter: Arun Mahadevan
>Assignee: Jungtaek Lim
> Attachments: AMBARI-22696-branch-2.6.patch, AMBARI-22696.patch
>
>
> Whitelist execute latency from Storm Ambari metrics
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22697) Throw exception when keytab creation fails due to wrong configuration of key encryption types
[
https://issues.apache.org/jira/browse/AMBARI-22697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16303469#comment-16303469
]
Hadoop QA commented on AMBARI-22697:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12903678/AMBARI-22697.001.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/12893//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12893//console
This message is automatically generated.
> Throw exception when keytab creation fails due to wrong configuration of key
> encryption types
> --
>
> Key: AMBARI-22697
> URL: https://issues.apache.org/jira/browse/AMBARI-22697
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Reporter: Akira Ajisaka
>Assignee: Akira Ajisaka
>Priority: Minor
> Attachments: AMBARI-22697.001.patch
>
>
> When kerberos key encryption type is wrong, kerberos service check fails by
> kinit failure. Now it is difficult to find that the root cause
> (misconfiguration of key encryption type) because keytabs look to be created
> successfully. (Actually keytabs are not created successfully, they are only
> 2-byte files)
> I'm thinking we should display error message or throw exception when keytab
> creation fails due to wrong key encryption type.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22687) Bulk host delete and component add & delete scenarios
[
https://issues.apache.org/jira/browse/AMBARI-22687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16301866#comment-16301866
]
Hadoop QA commented on AMBARI-22687:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12903452/AMBARI-22687.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/12892//console
This message is automatically generated.
> Bulk host delete and component add & delete scenarios
> -
>
> Key: AMBARI-22687
> URL: https://issues.apache.org/jira/browse/AMBARI-22687
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Ishan Bhatt
>Assignee: Ishan Bhatt
> Fix For: 3.0.0
>
> Attachments: AMBARI-22687.patch
>
>
> Implement various scenarios under which Bulk Deletion of Hosts and bulk
> addition and deletion of host components is allowed and display the related
> messages
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22692) JS error when switching focus of filters in combo search
[
https://issues.apache.org/jira/browse/AMBARI-22692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16301736#comment-16301736
]
Hadoop QA commented on AMBARI-22692:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12903419/AMBARI-22692.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/12891//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12891//console
This message is automatically generated.
> JS error when switching focus of filters in combo search
>
>
> Key: AMBARI-22692
> URL: https://issues.apache.org/jira/browse/AMBARI-22692
> Project: Ambari
> Issue Type: Bug
> Components: ambari-admin
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-22692.patch
>
>
> Error:
> {noformat}
> main.js:6165 Uncaught TypeError: Cannot read property 'id' of undefined
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22685) Stack OS/repos removed from cluster installation UI showed up on the Versions tab after cluster is installed
[
https://issues.apache.org/jira/browse/AMBARI-22685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16301513#comment-16301513
]
Hadoop QA commented on AMBARI-22685:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12903310/AMBARI-22685.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/12890//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12890//console
This message is automatically generated.
> Stack OS/repos removed from cluster installation UI showed up on the Versions
> tab after cluster is installed
>
>
> Key: AMBARI-22685
> URL: https://issues.apache.org/jira/browse/AMBARI-22685
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-22685.patch
>
>
> Even when a user had remove say Diebian , SLES OS/repos from cluster
> installation UI after selecting a stack, they still showed up on the Versions
> tab after cluster was installed.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22689) Restart agent command sent by server
[
https://issues.apache.org/jira/browse/AMBARI-22689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16301450#comment-16301450
]
Hadoop QA commented on AMBARI-22689:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12903352/AMBARI-22689.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/12889//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12889//console
This message is automatically generated.
> Restart agent command sent by server
>
>
> Key: AMBARI-22689
> URL: https://issues.apache.org/jira/browse/AMBARI-22689
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: trunk
>Reporter: Xianghao Lu
> Labels: patch
> Attachments: AMBARI-22689.patch
>
>
> When ambari agent get a heartbeat response from ambari server, agent will
> convert the string data to JSON object, and, response['restartAgent'] will be
> a bool value not string.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22679) RU: Service action failed with NullPointer on Downgrade after RU
[
https://issues.apache.org/jira/browse/AMBARI-22679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16301433#comment-16301433
]
Hadoop QA commented on AMBARI-22679:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12903362/AMBARI-22679.trunk.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/12888//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12888//console
This message is automatically generated.
> RU: Service action failed with NullPointer on Downgrade after RU
>
>
> Key: AMBARI-22679
> URL: https://issues.apache.org/jira/browse/AMBARI-22679
> Project: Ambari
> Issue Type: Bug
> Components: ambari-sever
>Affects Versions: trunk, 2.6.2
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Critical
> Fix For: trunk, 2.6.2
>
> Attachments: AMBARI-22679.branch-2.6.patch, AMBARI-22679.trunk.patch
>
>
> STR:
> - Install Ambari
> - Deploy HDP 2.5 with HDFS HA, YARN, MR, ZK
> - Install HDP 2.6 stack
> - Upgrade stack, on finalization initiate downgrade.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22674) ServiceAdvisor for OneFS
[
https://issues.apache.org/jira/browse/AMBARI-22674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16301424#comment-16301424
]
Hadoop QA commented on AMBARI-22674:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12903373/AMBARI-22674.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/12887//console
This message is automatically generated.
> ServiceAdvisor for OneFS
>
>
> Key: AMBARI-22674
> URL: https://issues.apache.org/jira/browse/AMBARI-22674
> Project: Ambari
> Issue Type: Task
> Components: ambari-agent
>Affects Versions: 3.0.0
>Reporter: Attila Magyar
>Assignee: Attila Magyar
> Fix For: 3.0.0
>
> Attachments: AMBARI-22674.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22690) Registering existing hdp version failed with sql exception
[
https://issues.apache.org/jira/browse/AMBARI-22690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16301421#comment-16301421
]
Hadoop QA commented on AMBARI-22690:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12903376/AMBARI-22690.branch-2.6.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/12886//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12886//console
This message is automatically generated.
> Registering existing hdp version failed with sql exception
> --
>
> Key: AMBARI-22690
> URL: https://issues.apache.org/jira/browse/AMBARI-22690
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.2
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Critical
> Fix For: 2.6.2
>
> Attachments: AMBARI-22690.branch-2.6.patch
>
>
> While trying to register existing HDP version below sql exception were
> noticed.
> STR:
> - Register HDP version 2.6.4 via manage versions screen of Ambari.
> - Try re-registering the same version again. Below exception is thrown.
> {code}
> ERROR [ambari-client-thread-3696] AmbariJpaLocalTxnInterceptor:180 -
> [DETAILED ERROR] Rollback reason:
> Local Exception Stack:
> Exception [EclipseLink-4002] (Eclipse Persistence Services -
> 2.6.2.v20151217-774c696): org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception: org.postgresql.util.PSQLException: ERROR: duplicate key
> value violates unique constraint "uq_repo_version_stack_id"
> Error Code: 0
> Call: INSERT INTO repo_version (repo_version_id, display_name, hidden,
> legacy, repositories, resolved, repo_type, version, version_url, version_xml,
> version_xsd, parent_id, stack_id) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?,
> ?)
> bind => [13 parameters bound]
> at
> org.eclipse.persistence.exceptions.DatabaseException.sqlException(DatabaseException.java:340)
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.processExceptionForCommError(DatabaseAccessor.java:1620)
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeDirectNoSelect(DatabaseAccessor.java:900)
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeNoSelect(DatabaseAccessor.java:964)
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java:633)
> at
> org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.executeBatch(ParameterizedSQLBatchWritingMechanism.java:149)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22691) JS error on Version edit page in Admin View
[
https://issues.apache.org/jira/browse/AMBARI-22691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16301363#comment-16301363
]
Hadoop QA commented on AMBARI-22691:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12903400/AMBARI-22691.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/12884//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12884//console
This message is automatically generated.
> JS error on Version edit page in Admin View
> ---
>
> Key: AMBARI-22691
> URL: https://issues.apache.org/jira/browse/AMBARI-22691
> Project: Ambari
> Issue Type: Bug
> Components: ambari-admin
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-22691.patch
>
>
> Go to Admin View and open any stack version page.
> JS error:
> {noformat}
> TypeError: Cannot read property 'gpl.license.accepted' of undefined
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22691) JS error on Version edit page in Admin View
[
https://issues.apache.org/jira/browse/AMBARI-22691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16301317#comment-16301317
]
Hadoop QA commented on AMBARI-22691:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12903400/AMBARI-22691.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/12883//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12883//console
This message is automatically generated.
> JS error on Version edit page in Admin View
> ---
>
> Key: AMBARI-22691
> URL: https://issues.apache.org/jira/browse/AMBARI-22691
> Project: Ambari
> Issue Type: Bug
> Components: ambari-admin
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-22691.patch
>
>
> Go to Admin View and open any stack version page.
> JS error:
> {noformat}
> TypeError: Cannot read property 'gpl.license.accepted' of undefined
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22687) Bulk host delete and component add & delete scenarios
[
https://issues.apache.org/jira/browse/AMBARI-22687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300817#comment-16300817
]
Hadoop QA commented on AMBARI-22687:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12903321/AMBARI-22687.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/12882//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12882//console
This message is automatically generated.
> Bulk host delete and component add & delete scenarios
> -
>
> Key: AMBARI-22687
> URL: https://issues.apache.org/jira/browse/AMBARI-22687
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Ishan Bhatt
>Assignee: Ishan Bhatt
> Fix For: 3.0.0
>
> Attachments: AMBARI-22687.patch
>
>
> Implement various scenarios under which Bulk Deletion of Hosts and bulk
> addition and deletion of host components is allowed and display the related
> messages
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22686) Disabled stack still appears in the UI if VDF is available
[
https://issues.apache.org/jira/browse/AMBARI-22686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300561#comment-16300561
]
Hadoop QA commented on AMBARI-22686:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12903311/AMBARI-22686.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/12881//console
This message is automatically generated.
> Disabled stack still appears in the UI if VDF is available
> --
>
> Key: AMBARI-22686
> URL: https://issues.apache.org/jira/browse/AMBARI-22686
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.1
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
>Priority: Critical
> Fix For: 2.6.2
>
> Attachments: AMBARI-22686.patch
>
>
> Ambari-2.6.1, Ambari UI still shows HDP-2.3 as a stack that is active
> although the stack definition marks this as disabled.
> Seems like the UI does not make any calls to check stack active/in-active.
> The stacks returned from VDF endpoint are then used to get the repo URLs
> because the VDF returns the stack def as sub-resource which included the
> in-active stack.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22679) RU: Service action failed with NullPointer on Downgrade after RU
[
https://issues.apache.org/jira/browse/AMBARI-22679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300550#comment-16300550
]
Hadoop QA commented on AMBARI-22679:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12903295/AMBARI-22679.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/12880//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12880//console
This message is automatically generated.
> RU: Service action failed with NullPointer on Downgrade after RU
>
>
> Key: AMBARI-22679
> URL: https://issues.apache.org/jira/browse/AMBARI-22679
> Project: Ambari
> Issue Type: Bug
> Components: ambari-sever
>Affects Versions: trunk, 2.6.2
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Critical
> Fix For: trunk, 2.6.2
>
> Attachments: AMBARI-22679.patch
>
>
> STR:
> - Install Ambari
> - Deploy HDP 2.5 with HDFS HA, YARN, MR, ZK
> - Install HDP 2.6 stack
> - Upgrade stack, on finalization initiate downgrade.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22394) Store and retrieve the ambari repo urls for os family during bootstrap
[
https://issues.apache.org/jira/browse/AMBARI-22394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300339#comment-16300339
]
Hadoop QA commented on AMBARI-22394:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12903272/AMBARI-22394.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/12878//console
This message is automatically generated.
> Store and retrieve the ambari repo urls for os family during bootstrap
> --
>
> Key: AMBARI-22394
> URL: https://issues.apache.org/jira/browse/AMBARI-22394
> Project: Ambari
> Issue Type: Sub-task
> Components: ambari-server, ambari-web
>Reporter: Yussuf Shaikh
>Assignee: Yussuf Shaikh
> Attachments: AMBARI-22394.patch
>
>
> ambari configuration will have list of repo urls for each os type
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22680) Ambari web UI does not fail an invalid repo base URL during cluster installation
[
https://issues.apache.org/jira/browse/AMBARI-22680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300336#comment-16300336
]
Hadoop QA commented on AMBARI-22680:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12903099/AMBARI-22680.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:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12877//console
This message is automatically generated.
> Ambari web UI does not fail an invalid repo base URL during cluster
> installation
>
>
> Key: AMBARI-22680
> URL: https://issues.apache.org/jira/browse/AMBARI-22680
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-22680.patch
>
>
> This is because the Ambari server backend never validated anything. It just
> simply sent back HTTP 200 as a dummy response.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22681) Ambari web UI failed to update stack repo directly from the Versions tab.
[
https://issues.apache.org/jira/browse/AMBARI-22681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300260#comment-16300260
]
Hadoop QA commented on AMBARI-22681:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12903103/AMBARI-22681.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12876//console
This message is automatically generated.
> Ambari web UI failed to update stack repo directly from the Versions tab.
> -
>
> Key: AMBARI-22681
> URL: https://issues.apache.org/jira/browse/AMBARI-22681
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-22681.patch
>
>
> REST API calls from the web got rejected by the ambari server with a missing
> property error.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22656) Add slot info for Hosts page
[
https://issues.apache.org/jira/browse/AMBARI-22656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300225#comment-16300225
]
Hadoop QA commented on AMBARI-22656:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12903182/AMBARI-22656.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 patch failed these unit tests in
ambari-agent ambari-server ambari-web:
org.apache.ambari.server.utils.StageUtilsTest
org.apache.ambari.server.controller.KerberosHelperTest
org.apache.ambari.server.serveraction.upgrades.PreconfigureKerberosActionTest
org.apache.ambari.server.orm.db.DDLTests
org.apache.ambari.server.controller.internal.HostResourceProviderTest
The test build failed in
[ambari-web|https://builds.apache.org/job/Ambari-trunk-test-patch/12875//artifact/patch-work/testrun_ambari-web.txt]
[ambari-agent|https://builds.apache.org/job/Ambari-trunk-test-patch/12875//artifact/patch-work/testrun_ambari-agent.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12875//console
This message is automatically generated.
> Add slot info for Hosts page
>
>
> Key: AMBARI-22656
> URL: https://issues.apache.org/jira/browse/AMBARI-22656
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-agent, ambari-server, ambari-web
>Affects Versions: 2.5.2
>Reporter: mathildaMa09
> Fix For: 2.5.2
>
> Attachments: AMBARI-22656.patch, AMBARI-22656_branch-2.5.patch
>
>
> In Hosts Page lists info about hosts like Rack、IP、Cores、DiskUsage .etc, but I
> need more details about my hosts’ physical position, like slot for instance,
> to know exactly where my machine locates. So, in hosts page, we can add slot
> info to describe their location.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22406) UI for verifying if repo exist for new OS family and user prompt for entering HDP and HDP-UTILs repo URLs
[
https://issues.apache.org/jira/browse/AMBARI-22406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300169#comment-16300169
]
Hadoop QA commented on AMBARI-22406:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12903226/AMBARI-22406.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:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12874//console
This message is automatically generated.
> UI for verifying if repo exist for new OS family and user prompt for entering
> HDP and HDP-UTILs repo URLs
> -
>
> Key: AMBARI-22406
> URL: https://issues.apache.org/jira/browse/AMBARI-22406
> Project: Ambari
> Issue Type: Sub-task
> Components: ambari-web
>Reporter: Yussuf Shaikh
>Assignee: Yussuf Shaikh
> Attachments: AMBARI-22406.patch
>
>
> This will include UI changes in ambari-web to check if the repo is selected
> or provide prompt to the user to enter the HDP and HDP-utils repo URL's.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22404) Set java.home. in ambari-server setup script for server OS family
[
https://issues.apache.org/jira/browse/AMBARI-22404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300133#comment-16300133
]
Hadoop QA commented on AMBARI-22404:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12903227/AMBARI-22404.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/12873//console
This message is automatically generated.
> Set java.home. in ambari-server setup script for server OS family
>
>
> Key: AMBARI-22404
> URL: https://issues.apache.org/jira/browse/AMBARI-22404
> Project: Ambari
> Issue Type: Sub-task
> Components: ambari-server
>Reporter: Yussuf Shaikh
>Assignee: Yussuf Shaikh
> Attachments: AMBARI-22404.patch
>
>
> Changes to ambari-server setup script for accepting user values for java_home
> for OS type.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22680) Ambari web UI does not fail an invalid repo base URL during cluster installation
[
https://issues.apache.org/jira/browse/AMBARI-22680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300130#comment-16300130
]
Hadoop QA commented on AMBARI-22680:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12903099/AMBARI-22680.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:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12872//console
This message is automatically generated.
> Ambari web UI does not fail an invalid repo base URL during cluster
> installation
>
>
> Key: AMBARI-22680
> URL: https://issues.apache.org/jira/browse/AMBARI-22680
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-22680.patch
>
>
> This is because the Ambari server backend never validated anything. It just
> simply sent back HTTP 200 as a dummy response.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22682) Ambari 3.0 Admin View: Add visual-search box to all pages
[
https://issues.apache.org/jira/browse/AMBARI-22682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300069#comment-16300069
]
Hadoop QA commented on AMBARI-22682:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12903236/AMBARI-22682.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 6 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-admin.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12871//console
This message is automatically generated.
> Ambari 3.0 Admin View: Add visual-search box to all pages
> -
>
> Key: AMBARI-22682
> URL: https://issues.apache.org/jira/browse/AMBARI-22682
> Project: Ambari
> Issue Type: Task
> Components: ambari-admin
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-22682.patch
>
>
> Add visual-search box to Users, Groups, Remote Clusters and Versions page.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22678) Fix Broken Symlinks on Stack Distribution
[
https://issues.apache.org/jira/browse/AMBARI-22678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16298704#comment-16298704
]
Hadoop QA commented on AMBARI-22678:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12903063/AMBARI-22678.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/12870//console
This message is automatically generated.
> Fix Broken Symlinks on Stack Distribution
> -
>
> Key: AMBARI-22678
> URL: https://issues.apache.org/jira/browse/AMBARI-22678
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.2
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Fix For: 2.6.2
>
> Attachments: AMBARI-22678.patch
>
>
> There are two scenarios to cover here:
> # Ambari never conf-select'd a component (maybe because of a bug or because
> the component didn't support it)
> # The conf pointers of a component are broken
> In either event, when distributing a new stack, the code detects this problem
> (as it would on a first-time install) and tries to fix it:
> {code}
> /etc/component/conf (directory)
> /usr/hdp/current/component -> /usr/hdp/v1/component
> /usr/hdp/v1/component -> /etc/component/conf
> {code}
> The stack distribution thinks this is a first-time installed and tries to fix
> the symlinks. We end up with:
> {code}
> /etc/component/conf -> /usr/hdp/current/component
> /usr/hdp/current/component -> /usr/hdp/v1/component
> /usr/hdp/v1/component -> /etc/component/conf
> /usr/hdp/v2/component -> /etc/component/v2/0
> {code}
> Because we're only conf-selecting v2, v1 never gets corrected since it's
> already installed. Thus, we have a circular symlink.
> Most likely the proper fix will be:
> - Iterate over the entire known conf-select structure
> - Check to see the state /etc/component/conf - if it's bad, fix it to defaults
> Chances are we can do this directly in
> {{conf_select.convert_conf_directories_to_symlinks}}:
> {code}
> stack_name = Script.get_stack_name()
> for directory_struct in dirs:
> if not os.path.exists(directory_struct['conf_dir']):
> Logger.info("Skipping the conf-select tool on {0} since {1} does not
> exist.".format(
> package, directory_struct['conf_dir']))
> return
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22676) [Patch Hive]webhcat: test_sqoop fails with hdfs:///hdp/apps/2.6.*/sqoop/sqoop.tar.gz does not exist
[
https://issues.apache.org/jira/browse/AMBARI-22676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16298530#comment-16298530
]
Hadoop QA commented on AMBARI-22676:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12902930/AMBARI-22676.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12869//console
This message is automatically generated.
> [Patch Hive]webhcat: test_sqoop fails with
> hdfs:///hdp/apps/2.6.*/sqoop/sqoop.tar.gz does not exist
> ---
>
> Key: AMBARI-22676
> URL: https://issues.apache.org/jira/browse/AMBARI-22676
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.6.2
>
> Attachments: AMBARI-22676.patch
>
>
> Tie HIVE and SQOOP for upgrades in order to make sure the sqoop tarball gets
> uploaded on the new version.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22656) Add slot info for Hosts page
[
https://issues.apache.org/jira/browse/AMBARI-22656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16298481#comment-16298481
]
Hadoop QA commented on AMBARI-22656:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12902983/AMBARI-22656_branch-2.5.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/12868//console
This message is automatically generated.
> Add slot info for Hosts page
>
>
> Key: AMBARI-22656
> URL: https://issues.apache.org/jira/browse/AMBARI-22656
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-agent, ambari-server, ambari-web
>Affects Versions: 2.5.2
>Reporter: mathildaMa09
> Fix For: 2.5.2
>
> Attachments: AMBARI-22656_branch-2.5.patch
>
>
> In Hosts Page lists info about hosts like Rack、IP、Cores、DiskUsage .etc, but I
> need more details about my hosts’ physical position, like slot for instance,
> to know exactly where my machine locates. So, in hosts page, we can add slot
> info to describe their location.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22673) UI hangs on step 2 of security wizard
[
https://issues.apache.org/jira/browse/AMBARI-22673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16297152#comment-16297152
]
Hadoop QA commented on AMBARI-22673:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12902867/AMBARI-22673.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/12867//console
This message is automatically generated.
> UI hangs on step 2 of security wizard
> -
>
> Key: AMBARI-22673
> URL: https://issues.apache.org/jira/browse/AMBARI-22673
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-22673.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22675) LogSearch Title Bar Fixes
[
https://issues.apache.org/jira/browse/AMBARI-22675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16297140#comment-16297140
]
Hadoop QA commented on AMBARI-22675:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12902896/AMBARI-22675.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-logsearch/ambari-logsearch-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12866//console
This message is automatically generated.
> LogSearch Title Bar Fixes
> -
>
> Key: AMBARI-22675
> URL: https://issues.apache.org/jira/browse/AMBARI-22675
> Project: Ambari
> Issue Type: Task
> Components: ambari-logsearch
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Istvan Tobias
> Fix For: 3.0.0
>
> Attachments: AMBARI-22675.patch
>
>
> The top LogSearch Title bar is currently fixed in size and shown during
> scrolling. It's better to have a limited set of search controls displayed in
> the LogSearch title bar, to provide a way to show the existing search, and
> also allow the user to modify the search while in the middle of searching
> results.
> The search bar instead of the title bar should be sticky at the top.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22673) UI hangs on step 2 of security wizard
[
https://issues.apache.org/jira/browse/AMBARI-22673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16296915#comment-16296915
]
Hadoop QA commented on AMBARI-22673:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12902867/AMBARI-22673.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/12865//console
This message is automatically generated.
> UI hangs on step 2 of security wizard
> -
>
> Key: AMBARI-22673
> URL: https://issues.apache.org/jira/browse/AMBARI-22673
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-22673.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22656) Add slot info for Hosts page
[
https://issues.apache.org/jira/browse/AMBARI-22656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16296913#comment-16296913
]
Hadoop QA commented on AMBARI-22656:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12902752/AMBARI-22656-branch-2.5.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/12864//console
This message is automatically generated.
> Add slot info for Hosts page
>
>
> Key: AMBARI-22656
> URL: https://issues.apache.org/jira/browse/AMBARI-22656
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-agent, ambari-server, ambari-web
>Affects Versions: 2.5.2
>Reporter: mathildaMa09
> Fix For: 2.5.2
>
> Attachments: AMBARI-22656-branch-2.5.patch
>
>
> In Hosts Page lists info about hosts like Rack、IP、Cores、DiskUsage .etc, but I
> need more details about my hosts’ physical position, like slot for instance,
> to know exactly where my machine locates. So, in hosts page, we can add slot
> info to describe their location.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22669) Ranger stack script changes to fix missing directory failure for blueprint installation
[
https://issues.apache.org/jira/browse/AMBARI-22669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16296910#comment-16296910
]
Hadoop QA commented on AMBARI-22669:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12902823/AMBARI-22669.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:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12863//console
This message is automatically generated.
> Ranger stack script changes to fix missing directory failure for blueprint
> installation
> ---
>
> Key: AMBARI-22669
> URL: https://issues.apache.org/jira/browse/AMBARI-22669
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
> Fix For: 3.0.0
>
> Attachments: AMBARI-22669.patch
>
>
> Updating stack scripts code to remove use of {{commandParams/version}} to
> build system path. For upgrade, using upgrade_summary module to get
> upgrade-to version ie (target version).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22625) Non DFS Used from HDFS Namenode UI and HDFS summary in Ambari is different
[
https://issues.apache.org/jira/browse/AMBARI-22625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16296857#comment-16296857
]
Hadoop QA commented on AMBARI-22625:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12901504/trunk.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:red}-1 core tests{color}. The test build failed in
[ambari-web|https://builds.apache.org/job/Ambari-trunk-test-patch/12862//artifact/patch-work/testrun_ambari-web.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12862//console
This message is automatically generated.
> Non DFS Used from HDFS Namenode UI and HDFS summary in Ambari is different
> ---
>
> Key: AMBARI-22625
> URL: https://issues.apache.org/jira/browse/AMBARI-22625
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.2
>Reporter: Akhil S Naik
>Priority: Minor
> Fix For: 2.6.0
>
> Attachments: ambari-2.png, namenode.png, release2.5.2.patch,
> trunk.patch
>
>
> 'NON DFS Used' value in Services -> HDFS -> Summary if different from the
> Value shown in NameNode UI (see Picture).
> in NAMENODE UI -->
> !https://issues.apache.org/jira/secure/attachment/12901501/namenode.png!
> In Services -> HDFS -> Summary
> !https://issues.apache.org/jira/secure/attachment/12901499/ambari-2.png!
> In NameNode UI the Non DFS Used is taken from 'NonDfsUsedSpace' variable from
> REST API call :
> http://host1:50070/jmx?qry=Hadoop:service=NameNode,name=NameNodeInfo
> Where host1 is the Name Node Server FQDN
> but in Ambari we are calculating the same value from (Total Allocated - DFS
> USed - DFS Remaining) .
> due to which this issue is happening.
> as a Fix we need to use the 'capacityNonDfsUsed' which comes from Server in
> NameNode metrics
> 'FSNamesystem > CapacityNonDFSUsed'
> attached the patch in the JIRA.
> Please fix this bug
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22672) Error on add version view in web admin
[
https://issues.apache.org/jira/browse/AMBARI-22672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16296813#comment-16296813
]
Hadoop QA commented on AMBARI-22672:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12902855/AMBARI-22672.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-admin.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12861//console
This message is automatically generated.
> Error on add version view in web admin
> --
>
> Key: AMBARI-22672
> URL: https://issues.apache.org/jira/browse/AMBARI-22672
> Project: Ambari
> Issue Type: Bug
> Components: ambari-admin
>Affects Versions: 3.0.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 3.0.0
>
> Attachments: AMBARI-22672.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22672) Error on add version view in web admin
[
https://issues.apache.org/jira/browse/AMBARI-22672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16296757#comment-16296757
]
Hadoop QA commented on AMBARI-22672:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12902855/AMBARI-22672.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-admin.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12860//console
This message is automatically generated.
> Error on add version view in web admin
> --
>
> Key: AMBARI-22672
> URL: https://issues.apache.org/jira/browse/AMBARI-22672
> Project: Ambari
> Issue Type: Bug
> Components: ambari-admin
>Affects Versions: 3.0.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 3.0.0
>
> Attachments: AMBARI-22672.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22670) Ambari 3.0: Implement new design for Admin View: Integrate visual-search box
[
https://issues.apache.org/jira/browse/AMBARI-22670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16296730#comment-16296730
]
Hadoop QA commented on AMBARI-22670:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12902848/AMBARI-22670.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 2 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:green}+1 core tests{color}. The patch passed unit tests in
ambari-admin.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12859//console
This message is automatically generated.
> Ambari 3.0: Implement new design for Admin View: Integrate visual-search box
>
>
> Key: AMBARI-22670
> URL: https://issues.apache.org/jira/browse/AMBARI-22670
> Project: Ambari
> Issue Type: Task
> Components: ambari-admin
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-22670.patch
>
>
> * Integrate visual-search box
> * Remove titles from above the table
> * Hide pagination when total number of items less than 10
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22671) Stack unit tests fixes
[
https://issues.apache.org/jira/browse/AMBARI-22671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16296683#comment-16296683
]
Hadoop QA commented on AMBARI-22671:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12902844/AMBARI-22671.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/12858//console
This message is automatically generated.
> Stack unit tests fixes
> ---
>
> Key: AMBARI-22671
> URL: https://issues.apache.org/jira/browse/AMBARI-22671
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-22671.patch
>
>
> Fix ~100 UT.
> Before:
>
>
> Total run:1210
> Total errors:195
> Total failures:44
>
> After:
>
>
> Total run:1210
> Total errors:83
> Total failures:67
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22656) Add slot info for Hosts page
[
https://issues.apache.org/jira/browse/AMBARI-22656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16296194#comment-16296194
]
Hadoop QA commented on AMBARI-22656:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12902754/hostDetails.png
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/12857//console
This message is automatically generated.
> Add slot info for Hosts page
>
>
> Key: AMBARI-22656
> URL: https://issues.apache.org/jira/browse/AMBARI-22656
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-agent, ambari-server, ambari-web
>Affects Versions: 2.5.2
>Reporter: mathildaMa09
> Fix For: 2.5.2
>
> Attachments: AMBARI-22656-branch-2.5.patch, hostDetails.png,
> hostPage.png
>
>
> In Hosts Page lists info about hosts like Rack、IP、Cores、DiskUsage .etc, but I
> need more details about my hosts’ physical position, like slot for instance,
> to know exactly where my machine locates. So, in hosts page, we can add slot
> info to describe their location.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22665) Livy2 Does Not Start On HDP 2.6.0 to 2.6.3
[
https://issues.apache.org/jira/browse/AMBARI-22665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16295747#comment-16295747
]
Hadoop QA commented on AMBARI-22665:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12902686/AMBARI-22665.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/12856//console
This message is automatically generated.
> Livy2 Does Not Start On HDP 2.6.0 to 2.6.3
> --
>
> Key: AMBARI-22665
> URL: https://issues.apache.org/jira/browse/AMBARI-22665
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.1
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.6.2
>
> Attachments: AMBARI-22665.patch
>
>
> Livy2 was added as a component in HDP 2.6, starting with HDP 2.6.0.0.
> However, there was no stack-select or conf-select support for some reason.
> stack-select and conf-select was built into HDP 2.6.4.0.
> Ambari added {{livy2}} as a known conf-select to the HDP 2.6 stack. On
> deployments of HDP 2.6.4+, this is correct and the server can properly start.
> However, when using Ambari to deploy Livy2 on HDP 2.6.0 - 2.6.3, we see the
> following:
> {code}
> 2017-12-18 14:53:52,711 - Checking to see which directories will be created
> for livy2 on version 2.6.0.0-334
> 2017-12-18 14:53:52,711 - call[('ambari-python-wrap', '/usr/bin/conf-select',
> 'dry-run-create', '--package', 'livy2', '--stack-version', '2.6.0.0-334',
> '--conf-version', '0')] {'logoutput': False, 'sudo': True, 'quiet': False,
> 'stderr': -1}
> 2017-12-18 14:53:52,734 - call returned (1, 'livy2 not installed or incorrect
> package name', '')
> 2017-12-18 14:53:52,735 - Creating /etc/livy2/2.6.0.0-334/0 if it does not
> exist
> 2017-12-18 14:53:52,736 - call[('ambari-python-wrap', '/usr/bin/conf-select',
> 'create-conf-dir', '--package', 'livy2', '--stack-version', '2.6.0.0-334',
> '--conf-version', '0')] {'logoutput': False, 'sudo': True, 'quiet': False,
> 'stderr': -1}
> 2017-12-18 14:53:52,765 - call returned (1, 'livy2 not installed or incorrect
> package name', '')
> 2017-12-18 14:53:52,766 - checked_call[('ambari-python-wrap',
> '/usr/bin/conf-select', 'set-conf-dir', '--package', 'livy2',
> '--stack-version', '2.6.0.0-334', '--conf-version', '0')] {'logoutput':
> False, 'sudo': True, 'quiet': False}
> 2017-12-18 14:53:52,795 - Could not select the directory for package livy2.
> Error: Execution of 'ambari-python-wrap /usr/bin/conf-select set-conf-dir
> --package livy2 --stack-version 2.6.0.0-334 --conf-version 0' returned 1.
> livy2 not installed or incorrect package name
> 2017-12-18 14:53:52,796 - /etc/livy2/conf is a directory - it must be
> converted into a symlink
> {code}
> Essentially, Ambari is trying to setup the configuration pointers, but it is
> ignoring the dry-run result code. At the end of the day, we end up with Livy2
> not starting b/c we're manipulated the configuration pointers, but
> {{conf-select}} failed to properly create a versioned configuration directory.
> The solution is to check the dry-run result code and do nothing if
> conf-select doesn't support the package.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22665) Livy2 Does Not Start On HDP 2.6.0 to 2.6.3
[
https://issues.apache.org/jira/browse/AMBARI-22665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16295310#comment-16295310
]
Hadoop QA commented on AMBARI-22665:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12902684/AMBARI-22665.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/12855//console
This message is automatically generated.
> Livy2 Does Not Start On HDP 2.6.0 to 2.6.3
> --
>
> Key: AMBARI-22665
> URL: https://issues.apache.org/jira/browse/AMBARI-22665
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.1
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.6.2
>
> Attachments: AMBARI-22665.patch
>
>
> Livy2 was added as a component in HDP 2.6, starting with HDP 2.6.0.0.
> However, there was no stack-select or conf-select support for some reason.
> stack-select and conf-select was built into HDP 2.6.4.0.
> Ambari added {{livy2}} as a known conf-select to the HDP 2.6 stack. On
> deployments of HDP 2.6.4+, this is correct and the server can properly start.
> However, when using Ambari to deploy Livy2 on HDP 2.6.0 - 2.6.3, we see the
> following:
> {code}
> 2017-12-18 14:53:52,711 - Checking to see which directories will be created
> for livy2 on version 2.6.0.0-334
> 2017-12-18 14:53:52,711 - call[('ambari-python-wrap', '/usr/bin/conf-select',
> 'dry-run-create', '--package', 'livy2', '--stack-version', '2.6.0.0-334',
> '--conf-version', '0')] {'logoutput': False, 'sudo': True, 'quiet': False,
> 'stderr': -1}
> 2017-12-18 14:53:52,734 - call returned (1, 'livy2 not installed or incorrect
> package name', '')
> 2017-12-18 14:53:52,735 - Creating /etc/livy2/2.6.0.0-334/0 if it does not
> exist
> 2017-12-18 14:53:52,736 - call[('ambari-python-wrap', '/usr/bin/conf-select',
> 'create-conf-dir', '--package', 'livy2', '--stack-version', '2.6.0.0-334',
> '--conf-version', '0')] {'logoutput': False, 'sudo': True, 'quiet': False,
> 'stderr': -1}
> 2017-12-18 14:53:52,765 - call returned (1, 'livy2 not installed or incorrect
> package name', '')
> 2017-12-18 14:53:52,766 - checked_call[('ambari-python-wrap',
> '/usr/bin/conf-select', 'set-conf-dir', '--package', 'livy2',
> '--stack-version', '2.6.0.0-334', '--conf-version', '0')] {'logoutput':
> False, 'sudo': True, 'quiet': False}
> 2017-12-18 14:53:52,795 - Could not select the directory for package livy2.
> Error: Execution of 'ambari-python-wrap /usr/bin/conf-select set-conf-dir
> --package livy2 --stack-version 2.6.0.0-334 --conf-version 0' returned 1.
> livy2 not installed or incorrect package name
> 2017-12-18 14:53:52,796 - /etc/livy2/conf is a directory - it must be
> converted into a symlink
> {code}
> Essentially, Ambari is trying to setup the configuration pointers, but it is
> ignoring the dry-run result code. At the end of the day, we end up with Livy2
> not starting b/c we're manipulated the configuration pointers, but
> {{conf-select}} failed to properly create a versioned configuration directory.
> The solution is to check the dry-run result code and do nothing if
> conf-select doesn't support the package.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22664) Fix unit test failures caused by old json format
[
https://issues.apache.org/jira/browse/AMBARI-22664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16294959#comment-16294959
]
Hadoop QA commented on AMBARI-22664:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12902642/AMBARI-22664.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/12854//console
This message is automatically generated.
> Fix unit test failures caused by old json format
>
>
> Key: AMBARI-22664
> URL: https://issues.apache.org/jira/browse/AMBARI-22664
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-22664.patch
>
>
> This fixes around 100 of failed unit tests due to old format of input json
> files.
> Before the fix:
>
>
> Total run:1206
> Total errors:281
> Total failures:41
>
> After the fix:
>
>
> Total run:1210
> Total errors:195
> Total failures:44
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22634) Kerberos support for OneFS
[
https://issues.apache.org/jira/browse/AMBARI-22634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16294894#comment-16294894
]
Hadoop QA commented on AMBARI-22634:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12902605/AMBARI-22634.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/12853//console
This message is automatically generated.
> Kerberos support for OneFS
> --
>
> Key: AMBARI-22634
> URL: https://issues.apache.org/jira/browse/AMBARI-22634
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Attila Magyar
>Assignee: Attila Magyar
> Fix For: 3.0.0
>
> Attachments: AMBARI-22634.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22663) Log Search UI: incorrect caption for graph gap in weeks
[
https://issues.apache.org/jira/browse/AMBARI-22663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16294880#comment-16294880
]
Hadoop QA commented on AMBARI-22663:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12902627/AMBARI-22663.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-logsearch/ambari-logsearch-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12851//console
This message is automatically generated.
> Log Search UI: incorrect caption for graph gap in weeks
> ---
>
> Key: AMBARI-22663
> URL: https://issues.apache.org/jira/browse/AMBARI-22663
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-22663.patch
>
>
> There's a text reflecting the gap between values of the graph. It's incorrect
> when the unit is week (caption is not defined).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22661) Storm service check fails with StormAtlasHook CNF after cluster deploy
[
https://issues.apache.org/jira/browse/AMBARI-22661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16293887#comment-16293887
]
Hadoop QA commented on AMBARI-22661:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12902502/AMBARI-22661.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/12850//console
This message is automatically generated.
> Storm service check fails with StormAtlasHook CNF after cluster deploy
> --
>
> Key: AMBARI-22661
> URL: https://issues.apache.org/jira/browse/AMBARI-22661
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.2
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Critical
> Fix For: 2.6.2
>
> Attachments: AMBARI-22661.patch
>
>
> STR:
> deploy cluster with HDFS, YARN, Tez, Hive, HBase, Pig, ZK, Storm, Ambari
> Infra, Atlas, Kafka, Slider using at least 5 hosts
> make sure that Supervisor , Atlas and Clients r on different hosts.
> Supervisor is the host, where most likely would run Storm SC.
> Check Storm SC
> Storm SC failed as Atlas class loader were not linked in storm extlib
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22571) Handle passwords/sensitive data in Ambari configuration properties
[
https://issues.apache.org/jira/browse/AMBARI-22571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16292894#comment-16292894
]
Hadoop QA commented on AMBARI-22571:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12902256/AMBARI_22571_trunk_01.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:red}-1 javac{color}. The applied patch generated 587 javac
compiler warnings (more than the trunk's current 534 warnings).
{color:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.topology.BlueprintImplTest
Javac warnings:
https://builds.apache.org/job/Ambari-trunk-test-patch/12849//artifact/patch-work/diffJavacWarnings.txt
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12849//console
This message is automatically generated.
> Handle passwords/sensitive data in Ambari configuration properties
> --
>
> Key: AMBARI-22571
> URL: https://issues.apache.org/jira/browse/AMBARI-22571
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Sandor Molnar
>Assignee: Sandor Molnar
>Priority: Minor
> Labels: config, security
> Fix For: trunk
>
> Attachments: AMBARI_22571_trunk_01.patch
>
>
> Passwords and other sensitive data stored as values to properties in Ambari
> configurations need to be masked or not stored in cleartext.
> For example,
> {{ldap-configuration/ambari.ldap.connectivity.trust_store.password}} and
> ldap-{{configuration/ambari.ldap.connectivity.bind_password}}.
> If the Ambari credential store is enabled (which might be by default as of
> Ambari 3.0.0), the sensitive date can be stored there like we do when
> sensitive data is to be stored in the ambari.properties file - see
> {{org.apache.ambari.server.security.encryption.CredentialStoreService}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22404) Set java.home. in ambari-server setup script for server OS family
[
https://issues.apache.org/jira/browse/AMBARI-22404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16292807#comment-16292807
]
Hadoop QA commented on AMBARI-22404:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12902307/AMBARI-22404_branch-feature-AMBARI-21674_01.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:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12848//console
This message is automatically generated.
> Set java.home. in ambari-server setup script for server OS family
>
>
> Key: AMBARI-22404
> URL: https://issues.apache.org/jira/browse/AMBARI-22404
> Project: Ambari
> Issue Type: Sub-task
> Components: ambari-server
>Reporter: Yussuf Shaikh
>Assignee: Yussuf Shaikh
> Attachments: AMBARI-22404.patch,
> AMBARI-22404_branch-feature-AMBARI-21674_01.patch
>
>
> Changes to ambari-server setup script for accepting user values for java_home
> for OS type.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22658) Cannot write krbPasswordExpiry in FreeIPA
[
https://issues.apache.org/jira/browse/AMBARI-22658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16292750#comment-16292750
]
Hadoop QA commented on AMBARI-22658:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12902393/IPKerberosOperationHandler-for-FreeIPA-4.3.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/12847//console
This message is automatically generated.
> Cannot write krbPasswordExpiry in FreeIPA
> -
>
> Key: AMBARI-22658
> URL: https://issues.apache.org/jira/browse/AMBARI-22658
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
> Environment: Ubuntu 16.04 LTS with FreeIPA 4.3.1
>Reporter: Tobias Hofer
> Attachments: IPKerberosOperationHandler-for-FreeIPA-4.3.patch
>
>
> Ambari Server fails to change the krbPasswordExpiry date because of an
> invalid date format.
> IPA fails to update the user by IPAKerberosOperationHandler.
> {code:java}
> user-mod %s --setattr krbPasswordExpiration=%s
> {code}
> The used format
> {noformat}
> MMddHHmmss.SSS'Z'
> {noformat}
> needs to be
> {noformat}
> MMddHHmmss'Z'
> {noformat}
> at least for the FreeIPA version distributed with Ubuntu 16.04.
> It would be great if Ambari is going to support FreeIPA 4.3.1 as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22635) Ambari should create a dummy core-site.xml for Ranger plugins when namenode is not installed
[
https://issues.apache.org/jira/browse/AMBARI-22635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16291873#comment-16291873
]
Hadoop QA commented on AMBARI-22635:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12902073/AMBARI-22635-branch-2.6.2.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/12846//console
This message is automatically generated.
> Ambari should create a dummy core-site.xml for Ranger plugins when namenode
> is not installed
>
>
> Key: AMBARI-22635
> URL: https://issues.apache.org/jira/browse/AMBARI-22635
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0, 2.6.1
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
> Fix For: trunk, 2.6.2
>
> Attachments: AMBARI-22635-branch-2.6.1.patch,
> AMBARI-22635-branch-2.6.2.patch, AMBARI-22635-branch-2.6.patch,
> AMBARI-22635-trunk.1-addendum.patch, AMBARI-22635-trunk.1.patch,
> AMBARI-22635-trunk.patch
>
>
> For Ranger plugins to work properly in kerberised environments where HDFS is
> not installed. We need to create a core-site.xml for Storm and Kafka plugins
> so that the plugins can work to fetch latest policies from with kerberised
> calls from Ranger.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22642) LDAPS sync Connection Refused
[
https://issues.apache.org/jira/browse/AMBARI-22642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16291871#comment-16291871
]
Hadoop QA commented on AMBARI-22642:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12902088/ambari-22642.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12845//console
This message is automatically generated.
> LDAPS sync Connection Refused
> --
>
> Key: AMBARI-22642
> URL: https://issues.apache.org/jira/browse/AMBARI-22642
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
> Environment: java version "1.8.0_121"
> Java(TM) SE Runtime Environment (build 1.8.0_121-tdc1-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode)
> AD Domain Controllers
> LDAP v.3
> 2012 R2 OS
>Reporter: David F. Quiroga
>Priority: Minor
> Labels: easyfix, patch
> Attachments: ambari-22642.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Ambari server configured to use "secure" ldap authentication.
> authentication.ldap.primaryUrl=:636
> authentication.ldap.useSSL=true
> We call the ldap_sync_events REST endpoint frequently to synchronize
> existing groups and a specific list groups. We had no issues with this until
> mid-October at which point we began to see:
> {code}
> "status" : "ERROR",
> "status_detail" : "Caught exception running LDAP sync. simple bind
> failed: **:636; nested exception is
> javax.naming.CommunicationException: simple bind failed: **:636 [Root
> exception is java.net.SocketException: Connection reset]",
> {code}
> Troubleshooting:
> * We saw random success and failure when attempting to sync a single group.
> * With useSSL=false and an updated port ldap sync was consistently successful.
> Cause:
> * By default, ldap connection only uses pooled connections when connecting to
> a directory server over LDAP. Enabling SSL causes it to disable the pooling,
> resulting in poorer performance and failures due to connection resets.
> * Around mid-October we increased the number of groups defined on the system
> (50+), this pushed us outside the "safe zone".
> Fix:
> Enable the SSL connections pooling by adding the below argument to startup
> options.
> -Dcom.sun.jndi.ldap.connect.pool.protocol='plain ssl'
> Reference:
> [https://confluence.atlassian.com/jirakb/connecting-jira-to-active-directory-over-ldaps-fails-with-connection-reset-763004137.htm]
> [https://docs.oracle.com/javase/jndi/tutorial/ldap/connect/config.html]
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22629) Disabling Kerberos after enabled during Blueprint install fails with missing data directory error
[
https://issues.apache.org/jira/browse/AMBARI-22629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16291848#comment-16291848
]
Hadoop QA commented on AMBARI-22629:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12902106/AMBARI-22629.branch-2.6.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/12844//console
This message is automatically generated.
> Disabling Kerberos after enabled during Blueprint install fails with missing
> data directory error
> -
>
> Key: AMBARI-22629
> URL: https://issues.apache.org/jira/browse/AMBARI-22629
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Robert Levas
>Assignee: Eugene Chekanskiy
> Labels: blueprints, kerberos
> Fix For: 2.6.2
>
> Attachments: AMBARI-22629.branch-2.6.patch,
> blueprint_single_node_zk.json, cluster_template_single_node_zk.json,
> screenshot-error-dialog.png
>
>
> Disabling Kerberos after enabled during Blueprint install fails with missing
> data directory error:
> {noformat}
> The data directory has not been set. Generated data can not be stored.
> {noformat}
> !screenshot-error-dialog.png!
> This is caused by an invalid security state set for the installed components
> since the appropriate state is not set while enabling Kerberos during the
> installation process:
> {noformat}
> ambari=> select * from hostcomponentstate;
> id | cluster_id | component_name | version| current_state | host_id
> | service_name | upgrade_state | security_state
> ++--+--+---+-+--+---+
> 1 | 2 | KERBEROS_CLIENT | UNKNOWN | INSTALLED | 1
> | KERBEROS | NONE | UNSECURED
> 2 | 2 | ZOOKEEPER_CLIENT | 2.5.0.0-1245 | INSTALLED | 1
> | ZOOKEEPER| NONE | UNSECURED
> 3 | 2 | ZOOKEEPER_SERVER | 2.5.0.0-1245 | STARTED | 1
> | ZOOKEEPER| NONE | UNSECURED
> {noformat}
> The expected state for each component is {{SECURED}}, not {{UNSECURED}}.
> Because of this, Ambari _thinks_ there is no work to be done, causing this
> issue.
> *Steps to reproduce*:
> # Setup Ambari, ensure KDC is installed on some host and Kerberos client libs
> are installed on the Ambari server host with the krb5.conf setup properly
> # Install Blueprint - [^blueprint_single_node_zk.json]
> # Create clister - [^cluster_template_single_node_zk.json]
> # When cluster is created, Kerberos should be enabled and all services up
> # Disable Kerberos - error occurs during Unkerberize Cluster task.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22577) Migrate user data for upgrade to improved user account management
[
https://issues.apache.org/jira/browse/AMBARI-22577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16290765#comment-16290765
]
Hadoop QA commented on AMBARI-22577:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12901950/AMBARI-22577_branch-feature-AMBARI-20859_02.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/12843//console
This message is automatically generated.
> Migrate user data for upgrade to improved user account management
> -
>
> Key: AMBARI-22577
> URL: https://issues.apache.org/jira/browse/AMBARI-22577
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-22577_branch-feature-AMBARI-20859_01.patch,
> AMBARI-22577_branch-feature-AMBARI-20859_02.patch,
> user_management_db_schema_upgrade.png
>
>
> Migrate data from the {{users}} table (pre-Ambari 3.0.0) to the updated
> {{users}} table and {{user_authentication}} tables.
> See [^user_management_db_schema_upgrade.png]
> !user_management_db_schema_upgrade.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
