From issues-return-65748-archive-asf-public=cust-asf.ponee.io@ambari.apache.org Sat Jan 20 21:28:03 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id DD81918066D for ; Sat, 20 Jan 2018 21:28:03 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id CDA4C160C38; Sat, 20 Jan 2018 20:28:03 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 1F6B1160C28 for ; Sat, 20 Jan 2018 21:28:02 +0100 (CET) Received: (qmail 6074 invoked by uid 500); 20 Jan 2018 20:28:02 -0000 Mailing-List: contact issues-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 issues@ambari.apache.org Received: (qmail 6065 invoked by uid 99); 20 Jan 2018 20:28:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 20 Jan 2018 20:28:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id E816AC095A for ; Sat, 20 Jan 2018 20:28:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -108.711 X-Spam-Level: X-Spam-Status: No, score=-108.711 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id yX9TsZgBwV13 for ; Sat, 20 Jan 2018 20:28:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id EDB0F5F3F0 for ; Sat, 20 Jan 2018 20:28:00 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 74AABE095C for ; Sat, 20 Jan 2018 20:28:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 1620420DF3 for ; Sat, 20 Jan 2018 20:28:00 +0000 (UTC) Date: Sat, 20 Jan 2018 20:28:00 +0000 (UTC) From: "Doroszlai, Attila (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-22805) Blueprints do not handle some failures properly MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBARI-22805?page=3Dcom.atlass= ian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-22805: --------------------------------------- Fix Version/s: 3.0.0 > Blueprints do not handle some failures properly > ----------------------------------------------- > > Key: AMBARI-22805 > URL: https://issues.apache.org/jira/browse/AMBARI-22805 > Project: Ambari > Issue Type: Bug > Components: ambari-server > Reporter: Doroszlai, Attila > Assignee: Doroszlai, Attila > Priority: Critical > Labels: blueprints, pull-request-available > Fix For: 3.0.0, 2.6.2 > > Time Spent: 50m > Remaining Estimate: 0h > > Failures in the=C2=A0cluster configuration task and topology host tasks d= uring blueprint cluster deployment or upscaling are not visible via request= status. The logical request stays PENDING even after Ambari Server gave up= retrying. Both the fact that it no longer makes progress and any reason of= the failure can be seen only in {{ambari-server.log}}. > Some ways to reproduce (all via blueprints): > * Create cluster with ZooKeeper and HDFS, but omit the NAMENODE componen= t > * Create a secure cluster with wrong Kerberos credentials > * Create a secure cluster without storing Kerberos credentials, restart = Ambari Server, add a new node -- This message was sent by Atlassian JIRA (v7.6.3#76005)