Hi, I was hoping someone has run into the following issues and can help me out.
I'm using puppet 0.25.5 and am using exported resources (with expiry) in order to construct configuration for a reverse proxy. There are two issues that I wonder if anyone has run into. Here is a high level of the setup: I have a webserver class that exports a resource that I have defined in order to configuration fragments in files. I have a loadbalancer class that collects these fragments and combines them into a config. The host that is assigned the loadbalancer class is not assigned a webserver class. My first question is whether there is any way to check whether the number of collected resources is greater than zero (a la defined() builtin for reqular variables) so that I don't get the following type of error: >> Could not retrieve catalog from remote server: Error 400 on SERVER: Could >> not find resource type 'Expiringwebserver' on node loadbalancer.blah.blah If no webservers are up this causes the loadbalancer machine to not get updated since it uses it's cached catalog. My second question is that after a restart of the puppet master, if the collecting host connects before any of the exporting hosts, I get the same error as above even if my resources have not expired. Why I think this is strange is that after the first exporting host updates all the exporting hosts resources are visible to the collecting host. Did I miss a bit of configuration that wouldn't require the update from one of the webservers to happen before the loadbalancer updates itself? Would an upgrade fix both these issues? Any help would be greatly appreciated!! -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
