ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-9417) Incorrect target hosts values allowable for moving HiveServer2 via service actions
Date Fri, 30 Jan 2015 16:36:34 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-9417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14298825#comment-14298825
] 

Hadoop QA commented on AMBARI-9417:
-----------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12695548/AMBARI-9417.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 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/1538//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/1538//console

This message is automatically generated.

> Incorrect target hosts values allowable for moving HiveServer2 via service actions
> ----------------------------------------------------------------------------------
>
>                 Key: AMBARI-9417
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9417
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.0.0
>            Reporter: Antonenko Alexander
>            Assignee: Antonenko Alexander
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-9417.patch, hs2-target-host-bug.jpg
>
>
> HiveServer2 is installed on 2 of 3 hosts in the cluster. After launching HiveServer2
Move Wizard from Hive service page, default target host for both components is the same one
(see the screenshot atached). User is allowed to proceed nevertheless. Later, target host
value is not passed, so Configure Component step fails because of 400 error on {{api/v1/clusters/<clusterName>/host_components?HostRoles/component_name=HIVE_SERVER&HostRoles/host_name.in()&fields=HostRoles/host_name&minimal_response=true}}
GET request. Also, rollback fails with 404 error on {{api/v1/clusters/<clusterName>/hosts//host_components/HIVE_SERVER}}
PUT request.
> Can be reproduced also if all hosts have HiveServer2 installed, both via host and service
actions.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message