From issues-return-65085-archive-asf-public=cust-asf.ponee.io@ambari.apache.org Thu Jan 4 17:44:07 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 193EE180657 for ; Thu, 4 Jan 2018 17:44:07 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 092DC160C3A; Thu, 4 Jan 2018 16:44:07 +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 49493160C28 for ; Thu, 4 Jan 2018 17:44:06 +0100 (CET) Received: (qmail 38379 invoked by uid 500); 4 Jan 2018 16:44:05 -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 38369 invoked by uid 99); 4 Jan 2018 16:44:05 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Jan 2018 16:44:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 7AE74180893 for ; Thu, 4 Jan 2018 16:44:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -107.211 X-Spam-Level: X-Spam-Status: No, score=-107.211 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_NONE=-0.0001, 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-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id zXmwO5piDQKj for ; Thu, 4 Jan 2018 16:44:03 +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 E722F5F2F0 for ; Thu, 4 Jan 2018 16:44:02 +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 6EEC5E105A for ; Thu, 4 Jan 2018 16:44:01 +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 399C324102 for ; Thu, 4 Jan 2018 16:44:00 +0000 (UTC) Date: Thu, 4 Jan 2018 16:44:00 +0000 (UTC) From: "Dmitry Lysnichenko (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (AMBARI-22678) Fix Broken Symlinks on Stack Distribution 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-22678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16311511#comment-16311511 ] Dmitry Lysnichenko edited comment on AMBARI-22678 at 1/4/18 4:43 PM: --------------------------------------------------------------------- Committed 6e58eccdfc..41c362eb97 branch-2.6 -> branch-2.6 dfb9785519..72812bd2bd trunk -> trunk was (Author: dmitriusan): Committed 6e58eccdfc..41c362eb97 branch-2.6 -> branch-2.6 > Fix Broken Symlinks on Stack Distribution > ----------------------------------------- > > Key: AMBARI-22678 > URL: https://issues.apache.org/jira/browse/AMBARI-22678 > Project: Ambari > Issue Type: Bug > Components: ambari-server > Affects Versions: 2.6.2 > Reporter: Dmitry Lysnichenko > Assignee: Dmitry Lysnichenko > Priority: Blocker > Fix For: 2.6.2 > > Attachments: AMBARI-22678.patch > > > There are two scenarios to cover here: > # Ambari never conf-select'd a component (maybe because of a bug or because the component didn't support it) > # The conf pointers of a component are broken > In either event, when distributing a new stack, the code detects this problem (as it would on a first-time install) and tries to fix it: > {code} > /etc/component/conf (directory) > /usr/hdp/current/component -> /usr/hdp/v1/component > /usr/hdp/v1/component -> /etc/component/conf > {code} > The stack distribution thinks this is a first-time installed and tries to fix the symlinks. We end up with: > {code} > /etc/component/conf -> /usr/hdp/current/component > /usr/hdp/current/component -> /usr/hdp/v1/component > /usr/hdp/v1/component -> /etc/component/conf > /usr/hdp/v2/component -> /etc/component/v2/0 > {code} > Because we're only conf-selecting v2, v1 never gets corrected since it's already installed. Thus, we have a circular symlink. > Most likely the proper fix will be: > - Iterate over the entire known conf-select structure > - Check to see the state /etc/component/conf - if it's bad, fix it to defaults > Chances are we can do this directly in {{conf_select.convert_conf_directories_to_symlinks}}: > {code} > stack_name = Script.get_stack_name() > for directory_struct in dirs: > if not os.path.exists(directory_struct['conf_dir']): > Logger.info("Skipping the conf-select tool on {0} since {1} does not exist.".format( > package, directory_struct['conf_dir'])) > return > {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029)