incubator-bigtop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roman Shaposhnik (Assigned) (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (BIGTOP-312) Puppet resource dependency syntax used in hadoop/manifests/init.pp doesn't always work
Date Wed, 25 Jan 2012 02:42:45 GMT

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

Roman Shaposhnik reassigned BIGTOP-312:
---------------------------------------

    Assignee: Roman Shaposhnik
    
> 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
>            Assignee: Roman Shaposhnik
>              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

        

Mime
View raw message