On Mon, Sep 21, 2009 at 12:19:39PM -0500, Chris Blumentritt wrote:
> I have a separate class that includes the my_project::project_env for all
> of my app servers. �I can verify that it is working since the apache conf
> file for site is there. �I have been banging my head on a wall with this
> one. �I have been dropping notice functions all over the place to figure
> out what is going on. �
> In my create_project define I have added the following notices:
> notice("secondary ip address is ${secondary_ip}")
> notice("project network interface is ${project_network_interface}")
> and get the following output on the server:
> notice: Scope(S_project[my_project-env]):�secondary ip address is x.x.x.x
> notice: Scope(S_project[my_project-env]):�project network interface is
> I guess I am running into a scope issue or something. �I have also tried
> to move the assignment of�project_network_interface in front of the "call"
> to the create_project define.
> Does the behavior I am seeing make sense? �I don't know what I can do
> different.
> ChrisI'm having a very similar problem. I have a couple custom facts, set in a 'custom' module (as per the latest wiki docs), that I use in a couple different modules (more coming). However, it doesn't seem to download the 'custom' module (thus inserting the facts) before the modules that depend on it. Commenting out the two templates, letting puppet run, then uncommenting them works, but is obviously not the solution. Without uncommenting them, compiling the template fails, so compiling the catalog fails, so the custom module is never pushed and I'm caught in a catch-22... In short, how do you declare one module dependent on another, to the extent that the first needs to be "run" first? David
signature.asc
Description: Digital signature
