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 A6C2D10C63 for ; Fri, 24 Jan 2014 16:04:44 +0000 (UTC) Received: (qmail 93031 invoked by uid 500); 24 Jan 2014 16:04:40 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 92958 invoked by uid 500); 24 Jan 2014 16:04:39 -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 92910 invoked by uid 99); 24 Jan 2014 16:04:38 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Jan 2014 16:04:38 +0000 Date: Fri, 24 Jan 2014 16:04:38 +0000 (UTC) From: "Dmytro Sen (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-4414) Pig install fails on stack 2.1.1 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-4414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13881088#comment-13881088 ] Dmytro Sen commented on AMBARI-4414: ------------------------------------ +1 > Pig install fails on stack 2.1.1 > -------------------------------- > > Key: AMBARI-4414 > URL: https://issues.apache.org/jira/browse/AMBARI-4414 > Project: Ambari > Issue Type: Bug > Reporter: Andrew Onischuk > Assignee: Andrew Onischuk > Fix For: 1.5.0 > > Attachments: AMBARI-4414.patch > > > Install of Cluster using 2.1.1 as Stack resulted in Warnings at step9 completion. Pig install failed. > Install Summary - Failed. > {noformat} > stderr: > group = params.user_group > File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line 152, in __init__ > self.env.run() > File "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", line 150, in run > self.run_action(resource, action) > File "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", line 116, in run_action > provider_action() > File "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py", line 149, in action_create > raise Fail("Applying %s failed, parent directory %s doesn't exist" % (self.resource, dirname)) > Fail: Applying Directory['/etc/pig/conf'] failed, parent directory /etc/pig doesn't exist > {noformat} > {noformat} > stdout: > group = params.user_group > File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line 152, in __init__ > self.env.run() > File "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", line 150, in run > self.run_action(resource, action) > File "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", line 116, in run_action > provider_action() > File "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py", line 149, in action_create > raise Fail("Applying %s failed, parent directory %s doesn't exist" % (self.resource, dirname)) > Fail: Applying Directory['/etc/pig/conf'] failed, parent directory /etc/pig doesn't exist > {noformat} > Possible, this was happen due fixing of BUG-12454 (blocker on previous Baikal build 1.5.0.8-1) -- This message was sent by Atlassian JIRA (v6.1.5#6160)