Discussion of the Puppet configuration management framework

[Puppet Users] ANNOUNCE: Puppet 2.7.3

As stated a few days ago [1], the 2.7.2 series died in the
Thunderdome[2], as per our release process.  August has brought about
2.7.3.  This includes all fixes from the 2.7.2, series as well as
several new fixes and enhancements.  This is also the first
release of the 2.7 (Statler) series, that includes the roll-up fixes
from 2.6.9.

Puppet 2.7.3 is available.  Changelog entries are available below.
More detailed information is available in on our Release Notes page.

Release Notes have been updated:
https://projects.puppetlabs.com/projects/puppet/wiki/Release_Notes#2.7.3

This release is available for download at:
http://puppetlabs.com/downloads/puppet/puppet-2.7.3.tar.gz

See the Verifying Puppet Download section at:
http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet

Please report feedback via the Puppet Labs Redmine site, using an
affected puppet version of 2.7.3
http://projects.puppetlabs.com/projects/puppet/

2.7.3 merges up all changes in the 2.6.9 release that were unable to be
merged into 2.7.{0,1} due to 2.7 being frozen in release candidate
state.  It also includes changes introduced in the never-released
2.7.2 series of puppet.

CHANGELOG
===

(Continue reading)

headers

David L Ballenger | 16 Aug 03:22

Re: [Puppet Users] ANNOUNCE: Puppet 2.7.3

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.

The puppet agent and master were running on the same node which is running Mac OS X 10.6.8. I also restarted
the master after removing my custom types and providers.

Any suggestion as to how to track this down.

Thanks - David

$ sudo puppet agent --test --debug
debug: Failed to load library 'selinux' for feature 'selinux'
debug: Failed to load library 'shadow' for feature 'libshadow'
debug: Failed to load library 'ldap' for feature 'ldap'
debug: Puppet::Type::User::ProviderLdap: feature ldap is missing
debug: Puppet::Type::User::ProviderUser_role_add: file rolemod does not exist
debug: Puppet::Type::User::ProviderUseradd: file userdel does not exist
debug: Puppet::Type::User::ProviderPw: file pw does not exist
debug: Puppet::Type::User::ProviderDirectoryservice: Executing '/usr/bin/dscl -plist . -list /Users'
debug: Puppet::Type::User::ProviderDirectoryservice: Executing '/usr/bin/dscl -plist . -read /Users/puppet'
debug: Puppet::Type::File::ProviderMicrosoft_windows: feature microsoft_windows is missing

(Continue reading)

headers

jcbollinger | 16 Aug 16:56

[Puppet Users] Re: ANNOUNCE: Puppet 2.7.3

On Aug 15, 8:22 pm, David L Ballenger <d...@davidlballenger.com>
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 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.

I would generally expect (perhaps unjustifiedly) that any 2.7.x client

(Continue reading)

headers

David L Ballenger | 16 Aug 18:48

Re: [Puppet Users] Re: ANNOUNCE: Puppet 2.7.3


On Aug 16, 2011, at 7:56 AM, jcbollinger wrote:

> 
> 
> On Aug 15, 8:22 pm, David L Ballenger <d...@davidlballenger.com>
> 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.

(Continue reading)

headers

Nigel Kersten | 16 Aug 19:48

Re: [Puppet Users] ANNOUNCE: Puppet 2.7.3

On Mon, Aug 15, 2011 at 6:22 PM, David L Ballenger <dlb <at> davidlballenger.com> 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

Can you generate a catalog with the older version and the newer and compare them?

Does --debug --trace add any more info ?

--
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 <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-users+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.

headers

David L Ballenger | 17 Aug 01:00

Re: [Puppet Users] ANNOUNCE: Puppet 2.7.3

On Aug 16, 2011, at 10:48 AM, Nigel Kersten wrote:

On Mon, Aug 15, 2011 at 6:22 PM, David L Ballenger <dlb <at> davidlballenger.com> 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

Can you generate a catalog with the older version and the newer and compare them?

Does --debug --trace add any more info ?

Thanks for the suggestion about --trace, I didn't see that in the puppet help info.

With --trace on I got:

/Library/Ruby/Gems/1.8/gems/puppet-2.7.3/lib/puppet/type/ssh_authorized_key.rb:95:in `unsafe_validate'

......

followed by more trace info. So it looks like I am having an issue with the ssh_authorized_key option parameter. When I looked at the line specified in the trace I found:

validate do |value|

raise Puppet::Error, "Options must be provided as an array, not a comma separated list" if value != :absent and

value.include?(',')

end

I think the "value.Include?(',')" is a little too "inclusive". It is catching a comma within a string that is part of a "from" option for the ssh_authorized_key to limit the systems from which the key will allow connections. For example:

"from=\"a.b.com,x.y.org\""

I also tried 'from="a.b.com,x.y.org"' with the same results.

This was working in 2.7.1.

Thanks - David

headers

Nigel Kersten | 17 Aug 01:08

Re: [Puppet Users] ANNOUNCE: Puppet 2.7.3

On Tue, Aug 16, 2011 at 4:00 PM, David L Ballenger <dlb <at> davidlballenger.com> wrote:

On Aug 16, 2011, at 10:48 AM, Nigel Kersten wrote:

On Mon, Aug 15, 2011 at 6:22 PM, David L Ballenger <dlb <at> davidlballenger.com> 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

Can you generate a catalog with the older version and the newer and compare them?

Does --debug --trace add any more info ?

Thanks for the suggestion about --trace, I didn't see that in the puppet help info.

With --trace on I got:

/Library/Ruby/Gems/1.8/gems/puppet-2.7.3/lib/puppet/type/ssh_authorized_key.rb:95:in `unsafe_validate'

......

followed by more trace info. So it looks like I am having an issue with the ssh_authorized_key option parameter. When I looked at the line specified in the trace I found:

validate do |value|

raise Puppet::Error, "Options must be provided as an array, not a comma separated list" if value != :absent and

value.include?(',')

end

I think the "value.Include?(',')" is a little too "inclusive". It is catching a comma within a string that is part of a "from" option for the ssh_authorized_key to limit the systems from which the key will allow connections. For example:

"from=\"a.b.com,x.y.org\""

I also tried 'from="a.b.com,x.y.org"' with the same results.

This was working in 2.7.1.

Ugh. I can't see an obvious test to distinguish this from a comma-separated string. Maybe if an "=" exists as well? I wonder what other options would pass/fail that test....

We definitely have enough for a bug report here if you wouldn't mind filing one, and we may have to abandon whatever it was that led us to have to implement that check.

--
Nigel Kersten
Product Manager, Puppet Labs

Join us for PuppetConf

<http://www.bit.ly/puppetconfsig>

Sept 22/23 Portland, Oregon, USA.

headers

David L Ballenger | 17 Aug 01:16

Re: [Puppet Users] ANNOUNCE: Puppet 2.7.3

Okay, I'll file a bug report on this later today. I seem to be having problems contacting the bug tracker right now.

On Aug 16, 2011, at 4:08 PM, Nigel Kersten wrote:

On Tue, Aug 16, 2011 at 4:00 PM, David L Ballenger <dlb <at> davidlballenger.com> wrote:

On Aug 16, 2011, at 10:48 AM, Nigel Kersten wrote:

On Mon, Aug 15, 2011 at 6:22 PM, David L Ballenger <dlb <at> davidlballenger.com> 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

Can you generate a catalog with the older version and the newer and compare them?

Does --debug --trace add any more info ?

Thanks for the suggestion about --trace, I didn't see that in the puppet help info.

With --trace on I got:

/Library/Ruby/Gems/1.8/gems/puppet-2.7.3/lib/puppet/type/ssh_authorized_key.rb:95:in `unsafe_validate'

......

followed by more trace info. So it looks like I am having an issue with the ssh_authorized_key option parameter. When I looked at the line specified in the trace I found:

validate do |value|

raise Puppet::Error, "Options must be provided as an array, not a comma separated list" if value != :absent and

value.include?(',')

end

I think the "value.Include?(',')" is a little too "inclusive". It is catching a comma within a string that is part of a "from" option for the ssh_authorized_key to limit the systems from which the key will allow connections. For example:

"from=\"a.b.com,x.y.org\""

I also tried 'from="a.b.com,x.y.org"' with the same results.

This was working in 2.7.1.

Ugh. I can't see an obvious test to distinguish this from a comma-separated string. Maybe if an "=" exists as well? I wonder what other options would pass/fail that test....

We definitely have enough for a bug report here if you wouldn't mind filing one, and we may have to abandon whatever it was that led us to have to implement that check.

--
Nigel Kersten
Product Manager, Puppet Labs

Join us for PuppetConf

<http://www.bit.ly/puppetconfsig>

Sept 22/23 Portland, Oregon, USA.

headers

Jacob Helwig | 17 Aug 01:19

Re: [Puppet Users] ANNOUNCE: Puppet 2.7.3

It's not just you. Unfortunately, it's down right now. Seems to be a hosting issue, so hopefully they'll get things sorted out quickly.

On Tue, Aug 16, 2011 at 16:16, David L Ballenger <dlb <at> davidlballenger.com> wrote:

Okay, I'll file a bug report on this later today. I seem to be having problems contacting the bug tracker right now.

On Aug 16, 2011, at 4:08 PM, Nigel Kersten wrote:

On Tue, Aug 16, 2011 at 4:00 PM, David L Ballenger <dlb <at> davidlballenger.com> wrote:

On Aug 16, 2011, at 10:48 AM, Nigel Kersten wrote:

On Mon, Aug 15, 2011 at 6:22 PM, David L Ballenger <dlb <at> davidlballenger.com> 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

Can you generate a catalog with the older version and the newer and compare them?

Does --debug --trace add any more info ?

Thanks for the suggestion about --trace, I didn't see that in the puppet help info.

With --trace on I got:

/Library/Ruby/Gems/1.8/gems/puppet-2.7.3/lib/puppet/type/ssh_authorized_key.rb:95:in `unsafe_validate'

......

followed by more trace info. So it looks like I am having an issue with the ssh_authorized_key option parameter. When I looked at the line specified in the trace I found:

validate do |value|

raise Puppet::Error, "Options must be provided as an array, not a comma separated list" if value != :absent and

value.include?(',')

end

I think the "value.Include?(',')" is a little too "inclusive". It is catching a comma within a string that is part of a "from" option for the ssh_authorized_key to limit the systems from which the key will allow connections. For example:

"from=\"a.b.com,x.y.org\""

I also tried 'from="a.b.com,x.y.org"' with the same results.

This was working in 2.7.1.

Ugh. I can't see an obvious test to distinguish this from a comma-separated string. Maybe if an "=" exists as well? I wonder what other options would pass/fail that test....

We definitely have enough for a bug report here if you wouldn't mind filing one, and we may have to abandon whatever it was that led us to have to implement that check.

--
Nigel Kersten
Product Manager, Puppet Labs

Join us for PuppetConf

<http://www.bit.ly/puppetconfsig>

Sept 22/23 Portland, Oregon, USA.

--
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 <at> googlegroups.com.
To unsubscribe from this group, send email to puppet-users+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.

headers

Peter Meier | 3 Sep 15:03

Re: ANNOUNCE: Puppet 2.7.3


> c315da0 Fix #1886 - Add node cleanup capability

unfortunately this capability was introduced only partially... :(

~pete