From issues-return-65684-archive-asf-public=cust-asf.ponee.io@ambari.apache.org Thu Jan 18 19:27:12 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 32254180654 for ; Thu, 18 Jan 2018 19:27:12 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 2240D160C4C; Thu, 18 Jan 2018 18:27:12 +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 6A287160C26 for ; Thu, 18 Jan 2018 19:27:11 +0100 (CET) Received: (qmail 36636 invoked by uid 500); 18 Jan 2018 18:27:10 -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 36611 invoked by uid 99); 18 Jan 2018 18:27:10 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Jan 2018 18:27:10 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 134391A752A for ; Thu, 18 Jan 2018 18:27:09 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.21 X-Spam-Level: X-Spam-Status: No, score=-100.21 tagged_above=-999 required=6.31 tests=[KAM_NUMSUBJECT=0.5, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id fjgcqeHtQ3bn for ; Thu, 18 Jan 2018 18:27:07 +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 519EC5F640 for ; Thu, 18 Jan 2018 18:27:07 +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 AD8DCE2578 for ; Thu, 18 Jan 2018 18:27:05 +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 4DD3921305 for ; Thu, 18 Jan 2018 18:27:03 +0000 (UTC) Date: Thu, 18 Jan 2018 18:27:03 +0000 (UTC) From: "Hudson (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-22665) Livy2 Does Not Start On HDP 2.6.0 to 2.6.3 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Auto-Submitted: auto-generated [ https://issues.apache.org/jira/browse/AMBARI-22665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16330936#comment-16330936 ] Hudson commented on AMBARI-22665: --------------------------------- FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8613 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8613/]) AMBARI-22665 - Livy2 Does Not Start On HDP 2.6.0 to 2.6.3 (rlevas: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=df19a69364b470b063e0790847af640c99262daa]) * (edit) ambari-server/src/main/resources/custom_actions/scripts/install_packages.py * (edit) ambari-common/src/main/python/resource_management/libraries/functions/conf_select.py > Livy2 Does Not Start On HDP 2.6.0 to 2.6.3 > ------------------------------------------ > > Key: AMBARI-22665 > URL: https://issues.apache.org/jira/browse/AMBARI-22665 > Project: Ambari > Issue Type: Bug > Affects Versions: 2.6.1 > Reporter: Jonathan Hurley > Assignee: Jonathan Hurley > Priority: Blocker > Fix For: 2.6.2 > > Attachments: AMBARI-22665.patch > > > Livy2 was added as a component in HDP 2.6, starting with HDP 2.6.0.0. However, there was no stack-select or conf-select support for some reason. stack-select and conf-select was built into HDP 2.6.4.0. > Ambari added {{livy2}} as a known conf-select to the HDP 2.6 stack. On deployments of HDP 2.6.4+, this is correct and the server can properly start. > However, when using Ambari to deploy Livy2 on HDP 2.6.0 - 2.6.3, we see the following: > {code} > 2017-12-18 14:53:52,711 - Checking to see which directories will be created for livy2 on version 2.6.0.0-334 > 2017-12-18 14:53:52,711 - call[('ambari-python-wrap', '/usr/bin/conf-select', 'dry-run-create', '--package', 'livy2', '--stack-version', '2.6.0.0-334', '--conf-version', '0')] {'logoutput': False, 'sudo': True, 'quiet': False, 'stderr': -1} > 2017-12-18 14:53:52,734 - call returned (1, 'livy2 not installed or incorrect package name', '') > 2017-12-18 14:53:52,735 - Creating /etc/livy2/2.6.0.0-334/0 if it does not exist > 2017-12-18 14:53:52,736 - call[('ambari-python-wrap', '/usr/bin/conf-select', 'create-conf-dir', '--package', 'livy2', '--stack-version', '2.6.0.0-334', '--conf-version', '0')] {'logoutput': False, 'sudo': True, 'quiet': False, 'stderr': -1} > 2017-12-18 14:53:52,765 - call returned (1, 'livy2 not installed or incorrect package name', '') > 2017-12-18 14:53:52,766 - checked_call[('ambari-python-wrap', '/usr/bin/conf-select', 'set-conf-dir', '--package', 'livy2', '--stack-version', '2.6.0.0-334', '--conf-version', '0')] {'logoutput': False, 'sudo': True, 'quiet': False} > 2017-12-18 14:53:52,795 - Could not select the directory for package livy2. Error: Execution of 'ambari-python-wrap /usr/bin/conf-select set-conf-dir --package livy2 --stack-version 2.6.0.0-334 --conf-version 0' returned 1. livy2 not installed or incorrect package name > 2017-12-18 14:53:52,796 - /etc/livy2/conf is a directory - it must be converted into a symlink > {code} > Essentially, Ambari is trying to setup the configuration pointers, but it is ignoring the dry-run result code. At the end of the day, we end up with Livy2 not starting b/c we're manipulated the configuration pointers, but {{conf-select}} failed to properly create a versioned configuration directory. > The solution is to check the dry-run result code and do nothing if conf-select doesn't support the package. -- This message was sent by Atlassian JIRA (v7.6.3#76005)