Mailing-List: contact bigtop-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: bigtop-dev@incubator.apache.org
Date: Mon, 19 Dec 2011 19:55:30 +0000 (UTC)
From: "Patrick Taylor Ramsey (Updated) (JIRA)" <jira@apache.org>
To: bigtop-dev@incubator.apache.org
Message-ID: 
 <405711301.27572.1324324531002.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1148298519.21751.1324084471244.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (BIGTOP-312) Puppet resource dependency syntax
 used in hadoop/manifests/init.pp doesn't always work
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/BIGTOP-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Patrick Taylor Ramsey updated BIGTOP-312:
-----------------------------------------

    Description: 
puppet <- ordering syntax doesn't seem to work when multiple resources are declared at the same time (when the resource name is specified as an array).  So,

foo { "blip": blort => "bloop", } <- flip { $zibble: }

... will break if $zibble turns out to be an array with more than one element.  We do this in a few places in modules/hadoop/manifests/init.pp.  Attaching a patch to fix it

  was:
puppet <- ordering syntax doesn't seem to work when multiple resources are declared at the same time (when the resource name is specified as an array).  So,

foo { "blip": blort => "bloop", } -> flip { $zibble: }

... will break if $zibble turns out to be an array with more than one element.  We do this in a few places in modules/hadoop/manifests/init.pp.  Attaching a patch to fix it

    
> Puppet resource dependency syntax used in hadoop/manifests/init.pp doesn't always work
> --------------------------------------------------------------------------------------
>
>                 Key: BIGTOP-312
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-312
>             Project: Bigtop
>          Issue Type: Bug
>          Components: Deployment
>            Reporter: Patrick Taylor Ramsey
>              Labels: deploy, deployment, puppet
>         Attachments: patch.txt
>
>
> puppet <- ordering syntax doesn't seem to work when multiple resources are declared at the same time (when the resource name is specified as an array).  So,
> foo { "blip": blort => "bloop", } <- flip { $zibble: }
> ... will break if $zibble turns out to be an array with more than one element.  We do this in a few places in modules/hadoop/manifests/init.pp.  Attaching a patch to fix it

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira