You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Antonenko Alexander (JIRA)" <ji...@apache.org> on 2015/01/30 17:11:34 UTC

[jira] [Updated] (AMBARI-9417) Incorrect target hosts values allowable for moving HiveServer2 via service actions

     [ https://issues.apache.org/jira/browse/AMBARI-9417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Antonenko Alexander updated AMBARI-9417:
----------------------------------------
    Attachment: hs2-target-host-bug.jpg

> 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: 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)