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
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 <
> d...@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 <
>> 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
>>>
>>>
>> 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 *
>
> 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@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.
>
--
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.
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
> wrote:
>
> On Aug 16, 2011, at 10:48 AM, Nigel Kersten wrote:
>
>>
>>
>> On Mon, Aug 15, 2011 at 6:22 PM, David L Ballenger
>> 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
>
> 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@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.
Re: [Puppet Users] ANNOUNCE: Puppet 2.7.3
On Tue, Aug 16, 2011 at 4:00 PM, David L Ballenger
wrote:
>
> On Aug 16, 2011, at 10:48 AM, Nigel Kersten wrote:
>
>
>
> On Mon, Aug 15, 2011 at 6: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
>>
>>
> 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 *
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@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.
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
> 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
--
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.
Re: [Puppet Users] ANNOUNCE: Puppet 2.7.3
On Mon, Aug 15, 2011 at 6:22 PM, David L Ballenger 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@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.
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 debug: /File[/var/lib/puppet/state/state.yaml]: Autorequiring File[/var/lib/puppet/state] debug: /File[/var/lib/puppet/run]: Autorequiring File[/var/lib/puppet] debug: /File[/etc/puppet/ssl/certs]: Autorequiring File[/etc/puppet/ssl] debug: /File[/var/lib/puppet/state/last_run_report.yaml]: Autorequiring File[/var/lib/puppet/state] debug: /File[/var/lib/puppet/clientbucket]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/client_yaml]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/state/last_run_summary.yaml]: Autorequiring File[/var/lib/puppet/state] debug: /File[/var/lib/puppet/log]: Autorequiring File[/var/lib/puppet] debug: /File[/etc/puppet/ssl/crl.pem]: Autorequiring File[/etc/puppet/ssl] debug: /File[/etc/puppet/ssl]: Autorequiring File[/etc/puppet] debug: /File[/etc/puppet/ssl/private_keys]: Autorequiring File[/etc/puppet/ssl] debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/puppet] debug: /File[/etc/puppet/ssl/public_keys]: Autorequiring File[/etc/puppet/ssl] debug: /File[/var/lib/puppet/state/classes.txt]: Autorequiring File[/var/lib/puppet/state] debug: /File[/etc/puppet/ssl/certs/opus.davidlballenger.net.pem]: Autorequiring File[/etc/puppet/ssl/certs] debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet] debug: /File[/etc/puppet/puppet.conf]: Autorequiring File[/etc/puppet] debug: /File[/etc/puppet/ssl/certificate_requests]: Autorequiring File[/etc/puppet/ssl] debug: /File[/etc/puppet/ssl/certs/ca.pem]: Autorequiring File[/etc/puppet/ssl/certs] debug: /File[/etc/puppet/ssl/private_keys/opus.davidlballenger.net.pem]: Autorequiring File[/etc/puppet/ssl/private_keys] debug: /File[/var/lib/puppet/state/graphs]: Autorequiring File[/var/lib/puppet/state] debug: /File[/etc/puppet/ssl/public_keys/opus.davidlballenger.net.pem]: Autorequiring File[/etc/puppet/ssl/public_keys] debug: /File[/var/lib/puppet/client_data]: Autorequiring File[/var/lib/puppet] debug: /File[/etc/puppet/ssl/private]: Autorequiring File[/etc/puppet/ssl] debug: Finishing transaction 2164622240 debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet] debug: /File[/etc/puppet/ssl/certificate_requests]: Autorequiring File[/etc/puppet/ssl] debug: /File[/etc/puppet/ssl/private]: Autorequiring File[/etc/puppet/ssl] debug: /File[/etc/puppet/ssl/public_keys/opus.davidlballenger.net.pem]: Autorequiring File[/etc/puppet/ssl/public_keys] debug: /File[/etc/puppet/ssl/private_keys]: Autorequiring File[/etc/puppet/ssl] debug: /File[/etc/puppet/ssl/certs]: Autorequiring File[/etc/puppet/ssl] debug: /File[/etc/puppet/ssl/certs/opus.davidlballenger.net.pem]: Autorequiring File[/etc/puppet/ssl/certs] debug: /File[/var/lib/puppet/run]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet] debug: /File[/etc/puppet/ssl/private_keys/opus.davidlballenger.net.pem]: Autorequiring File[/etc/puppet/ssl/private_keys] debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/puppet] debug:
[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
===
7113448 (#4762) Ensure that clients on the moon can successfully connect.
c8835ad Add document outlining preferred contribution methods
ea0f2bf Revert "Merge branch 'vcsrepo'"
94f0b93 (#8704) Give better errors for invalid fileserver.conf
023d959 (#8690) Accept 'global' options in Puppet Faces
c315da0 Fix #1886 - Add node cleanup capability
7e6fc0d Deprecate RestAuthConfig#allowed? in favor of #check_authorization
6401dfe Fix #6026 - security file should support inline comments
0c385f1 Fix #5010 - Allow leading whitespace in auth.conf
8da0486 Fix #5777 - rule interpolation broke auth.conf CIDR rules
1d4acb5 maint: Suggest where to start troubleshooting SSL error message
fb2ffd6 (#8596) Detect resource alias conflicts when titles do not match
778127d maint: Fix cert app to print help and exit if no subcommand
0366b18 (#7293) Set default format for SSL-related faces.
89c021c (#8418) Fix inspect app to have the correct run_mode
3165364 maint: Adding logging to include environment when source fails
f484851 maint: Add debug logging when the master receives a report
10e05ad (#7266) Move Certificate option validation into face.
ae36003 (#7290) Update indirected Faces to avoid unknown options.
82e5fa9 (#8561, #7290) Implement the option contract fully.
77441be (#8561) Unify validation and modification of action arguments.
69b4e70 (#7290) Fail on unknown options.
6bec2df (#8561) Use canonical names for options to actions.
532c4f3 (#7184) Load the core of obsolete versions of Faces.
2cd3bc4 (#7184) Find actions bound to other versions of Faces.
1e0655e (#7184) Centralize "find action for face" into Puppet::Face
0396611 maint: better error reporting when test fails
395c174 (#7123) Make `find` the default action...
fd6a653 (#7123) Support runtime setting of 'default' on actions.
b75b1c1 (#6787) Add `default_to` for options.
c830ab0 (#6789) Port SSL::CertificateAuthority::Interface to a Face
cc311ad maint: SSL::Inventory.serial should report missing names.
72abe6c (#7204) Consolidate Semantic Versioning code.
d02000b (#8401) Document that --detailed-exitcodes is a bitmask
c4848d2 maint: Fix documentation link for fileserver configuration
b268fb3 (#7144) Update Settings#writesub to convert mode to Fixnum
b82f29c (#7699) Help command should only list options once
4a2f22c (maint) Fix platform dection for RHEL
45b3908 (#4142) Fix module check not to fail when empty metadata.json
ae3ef42 (#7699) - Help should only show options once
5826f73 (#8032) Add containment to create_resources
f6882d6 (#8147) Change default reporturl to match newer Dashboard versions
111a4b5 (#6857) Password disclosure when changing a user's password
99330fa (#7224) Reword 'hostname was not match' error message
1d867b0 (#7224) Add a helper to Puppet::SSL::Certificate to retrieve
alternate names
98ba407 (#7127) Stop puppet if a prerun command fails
caca469 (#4416) Ensure types are providified after reloading
413b136 (#4416) Always remove old provider before recreating it
3f0dbb5 (#650) Allow symlinks for configuration directories
1c70f0c (#2128) Add support for setting node name based on a fact
c629958 (#2128) Get facts before retrieving catalog
cd4fe14 (#2128) Add the ability to specify a node name
c02126d (#5966) Add support for hostname regular expressions in auth.conf
75e2764 (#5318) Always notice changes to manifests when compiling.
107b38a maint: Fix pacman provider to work with Ruby 1.9
90eb937 (#7139) Accept '/' as a valid path in filesets
[1]
http://groups.google.com/group/puppet-users/browse_thread/thread/fb68f18b97f39070
[2]
http://groups.google.com/group/puppet-users/browse_thread/thread/3d703849246bd43f/c98d096d51ed221e
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppe
