On Aug 16, 2011, at 7:56 AM, jcbollinger wrote: > > > On Aug 15, 8:22 pm, David L Ballenger <[email protected]> > wrote: >> Since upgrading for Puppet 2.7.1 to 2.7.3 I have been getting the following >> error whenever a Puppet agent runs: >> >> err: Failed to apply catalog: Parameter options failed: Options must be >> provided as an array, not a comma separated list >> >> I ran the puppet agent with --test and --debug and got the output below. >> You'll notice that the error seems to occur when it's attempting to load >> service providers. I was doing some work on some custom types and providers >> and thought maybe there was a problem with one of those. So I removed them >> from /var/lib/puppet and the from the modules tree of the puppet master >> configuration so they wouldn't be reinstalled. I got the same results as >> below, so I'm guessing it's something else, but the error message isn't very >> helpful in figuring that out. I didn't see anything related in the release >> notes. > > > It strikes me oddly that the master appears to have successfully > compiled the catalog, but the agent doesn't like the result. Is the > node running a newer version of Puppet than the master? Even 2.7.3 > vs. 2.7.1? Even if you upgraded the master at the same time you > updated the client, you might need to restart the puppetmaster service > to actually get the new version running.
The agent and master are on the same system. In the course of trying to track down the problem I restarted the master, several times. > > The error message itself appears to be complaining about a resource > poperty named 'options'. The only two built-in resource types that > are documented to have such a property are 'mount' and > 'ssh_authorized_key'. The latter resource explicitly specifies that > multiple options must be provided as an array, which aligns pretty > well with the error message you received. No uses of the mount resource, but three uses of ssh_authorized_key. Only one ssh_authorized_key had multiple options and these were specified as an array, the other two had a single option specified as a string. I changed those two to specify the option as a single element array, but that didn't help. I'll try a few more things to see if I can narrow things down to an offending module, then submit a bug report. > > I would generally expect (perhaps unjustifiedly) that any 2.7.x client > would work correctly with any 2.7.x master. If, therefore, the > behavior change indeed arose from the upgrade then it is worthwhile > filing a bug report, if only for documentary purposes. > > > John > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
