Return-Path: X-Original-To: apmail-ambari-dev-archive@www.apache.org Delivered-To: apmail-ambari-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 219581791B for ; Fri, 30 Jan 2015 16:16:34 +0000 (UTC) Received: (qmail 94961 invoked by uid 500); 30 Jan 2015 16:16:34 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 94930 invoked by uid 500); 30 Jan 2015 16:16:34 -0000 Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list dev@ambari.apache.org Received: (qmail 94919 invoked by uid 99); 30 Jan 2015 16:16:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Jan 2015 16:16:34 +0000 Date: Fri, 30 Jan 2015 16:16:34 +0000 (UTC) From: "Antonenko Alexander (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-9417) Incorrect target hosts values allowable for moving HiveServer2 via service actions MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBARI-9417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-9417: ---------------------------------------- Attachment: AMBARI-9417.patch > 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//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//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)