Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id DC965200C04 for ; Tue, 24 Jan 2017 21:55:31 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id DB18D160B3E; Tue, 24 Jan 2017 20:55:31 +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 31890160B38 for ; Tue, 24 Jan 2017 21:55:31 +0100 (CET) Received: (qmail 39764 invoked by uid 500); 24 Jan 2017 20:55:30 -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 39755 invoked by uid 99); 24 Jan 2017 20:55:30 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Jan 2017 20:55:30 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id E22CBC0D33 for ; Tue, 24 Jan 2017 20:55:29 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.199 X-Spam-Level: X-Spam-Status: No, score=-1.199 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id fCj8r2dU76dx for ; Tue, 24 Jan 2017 20:55:29 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id AC5085F46D for ; Tue, 24 Jan 2017 20:55:28 +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 AD0BBE0389 for ; Tue, 24 Jan 2017 20:55:27 +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 BC06E2528B for ; Tue, 24 Jan 2017 20:55:26 +0000 (UTC) Date: Tue, 24 Jan 2017 20:55:26 +0000 (UTC) From: "Hadoop QA (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-19695) Remove thrown exceptions while validating Kerberos Authentication configuration MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 24 Jan 2017 20:55:32 -0000 [ https://issues.apache.org/jira/browse/AMBARI-19695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15836623#comment-15836623 ] Hadoop QA commented on AMBARI-19695: ------------------------------------ {color:green}+1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12849132/AMBARI-19695.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 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 ambari-server. Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/10231//testReport/ Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/10231//console This message is automatically generated. > Remove thrown exceptions while validating Kerberos Authentication configuration > ------------------------------------------------------------------------------- > > Key: AMBARI-19695 > URL: https://issues.apache.org/jira/browse/AMBARI-19695 > Project: Ambari > Issue Type: Bug > Components: ambari-server > Affects Versions: 2.5.0 > Reporter: Eugene Chekanskiy > Assignee: Eugene Chekanskiy > Fix For: 2.5.0 > > Attachments: AMBARI-19695.2.5.patch, AMBARI-19695.trunk.patch > > > When starting Ambari where Kerberos authentication is enabled (authentication.kerberos.enabled=true), Ambari validates the relevant configuration properties. If a sever issue is found, an exception is thrown. This causes issues in installations where Ambari is expected to be able to perform Kerberos authentication but all of the data is available for since this is it expected to be provided later. For example, the SPNEGO keytab file will be created when Kerberos is enabled sometime after Ambari starts up. > To prevent Ambari from shutting down when all the required data is not available, thrown exceptions should be removed from org.apache.ambari.server.configuration.Configuration#createKerberosAuthenticationProperties. -- This message was sent by Atlassian JIRA (v6.3.4#6332)