Puppet users - Oct 2010 - puppetd 0.25.4 with puppetmaster 0.24.8?

Our puppetmaster runs 0.24.8 on Ubuntu 9.10.  Our clients are either 
Ubuntu 9.10 or Ubuntu 8.04.

We''ve just brought up our first Ubuntu 10.04 machine. This machine 
installs puppetd 0.25.4.

The Ubuntu 10.04 machine can''t seem to present it''s
certificate request
properly.

In my masterhttp.log, I see
[2010-10-20 13:09:06] 174-143-141-55.static.cloud-ips.com - - 
[20/Oct/2010:13:09:05 CDT] "PUT 
/production/certificate_request/edglucid1.newhostingaccount.net 
HTTP/1.1" 404 359  getting a 404.

Also

[2010-10-20 13:24:52] 174-143-141-55.static.cloud-ips.com - - 
[20/Oct/2010:13:24:52 CDT] "GET /production/certificate/ca HTTP/1.1"
404 322

There is no certificate pending to sign.

My command line on the client side was
/usr/sbin/puppetd --no-daemonize --verbose --onetime --server=xxx 
--fqdn=edglucid1.newhostingaccount.net

Am I hitting a version incompatibility, and is there any hope for this 
other than  installing a newer puppetmaster, from source (since Ubuntu 
9.10 doesn''t provide 0.25) or upgrading the puppetmaster server to 
Ubuntu 10.04?




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

If the upgrades are not gonna break your network, you''d better upgrade.
Also
you''d wanna have the masters upgraded first rather than the clients.
But
still you can through the release notes for both the versions and see if you
can work out a solution.

On Thu, Oct 21, 2010 at 12:02 AM, Ed Greenberg <edg@greenberg.org> wrote:
> Our puppetmaster runs 0.24.8 on Ubuntu 9.10.  Our clients are either Ubuntu
> 9.10 or Ubuntu 8.04.
>
> We''ve just brought up our first Ubuntu 10.04 machine. This machine
installs
> puppetd 0.25.4.
>
> The Ubuntu 10.04 machine can''t seem to present it''s
certificate request
> properly.
>
> In my masterhttp.log, I see
> [2010-10-20 13:09:06] 174-143-141-55.static.cloud-ips.com - -
> [20/Oct/2010:13:09:05 CDT] "PUT /production/certificate_request/
> edglucid1.newhostingaccount.net HTTP/1.1" 404 359  getting a 404.
>
> Also
>
> [2010-10-20 13:24:52] 174-143-141-55.static.cloud-ips.com - -
> [20/Oct/2010:13:24:52 CDT] "GET /production/certificate/ca
HTTP/1.1" 404 322
>
> There is no certificate pending to sign.
>
> My command line on the client side was
> /usr/sbin/puppetd --no-daemonize --verbose --onetime --server=xxx
--fqdn> edglucid1.newhostingaccount.net
>
> Am I hitting a version incompatibility, and is there any hope for this
> other than  installing a newer puppetmaster, from source (since Ubuntu 9.10
> doesn''t provide 0.25) or upgrading the puppetmaster server to
Ubuntu 10.04?
>
>
>
>
> --
> 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+unsubscribe@googlegroups.com<puppet-users%2Bunsubscribe@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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Always upgrade the puppetmaster first.  Clients will usually not work with a
server that has an older major version.

I''ve found that using the lucid (10.4) deb files in karmic (9.10) works
fine
if You get all the related ones.  When ever you upgrade puppet, also upgrade
facter.

On Wed, Oct 20, 2010 at 11:32 AM, Ed Greenberg <edg@greenberg.org> wrote:
> Our puppetmaster runs 0.24.8 on Ubuntu 9.10.  Our clients are either Ubuntu
> 9.10 or Ubuntu 8.04.
>
> We''ve just brought up our first Ubuntu 10.04 machine. This machine
installs
> puppetd 0.25.4.
>
> The Ubuntu 10.04 machine can''t seem to present it''s
certificate request
> properly.
>
> In my masterhttp.log, I see
> [2010-10-20 13:09:06] 174-143-141-55.static.cloud-ips.com - -
> [20/Oct/2010:13:09:05 CDT] "PUT /production/certificate_request/
> edglucid1.newhostingaccount.net HTTP/1.1" 404 359  getting a 404.
>
> Also
>
> [2010-10-20 13:24:52] 174-143-141-55.static.cloud-ips.com - -
> [20/Oct/2010:13:24:52 CDT] "GET /production/certificate/ca
HTTP/1.1" 404 322
>
> There is no certificate pending to sign.
>
> My command line on the client side was
> /usr/sbin/puppetd --no-daemonize --verbose --onetime --server=xxx
--fqdn> edglucid1.newhostingaccount.net
>
> Am I hitting a version incompatibility, and is there any hope for this
> other than  installing a newer puppetmaster, from source (since Ubuntu 9.10
> doesn''t provide 0.25) or upgrading the puppetmaster server to
Ubuntu 10.04?
>
>
>
>
> --
> 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+unsubscribe@googlegroups.com<puppet-users%2Bunsubscribe@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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

OK, so I upgraded the puppetmaster server to lucid, which got me the 
puppetmaster 0.25.4.

I am still having issues signing up a new lucid client, and I''ve foudn 
this in the client''s log:
Oct 21 15:32:53 edglucid1 puppetd[27061]: Could not request certificate: 
undefin
ed method `closed?'' for nil:NilClass

Not being initiated in the ways of Ruby, I''m not very well equipped to 
debug this :)

Any suggestions?

</edg>

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

On Oct 21, 2010, at 8:48 AM, Ed Greenberg wrote:
> OK, so I upgraded the puppetmaster server to lucid, which got me the
puppetmaster 0.25.4.
> 
> I am still having issues signing up a new lucid client, and I''ve
foudn this in the client''s log:
> Oct 21 15:32:53 edglucid1 puppetd[27061]: Could not request certificate:
undefin
> ed method `closed?'' for nil:NilClass
> 
> Not being initiated in the ways of Ruby, I''m not very well
equipped to debug this :)
> 
> Any suggestions?
The "undefined method `closed?'' for nil:NilClass" error is a
known and very confusing bug in 0.25.x, that is fixed in 0.25.5.  It replaces
most error messages with this "nil:NilClass" error.  Upgrade to fix
it, if you want to see the real error.

Bug report: (Most of the information isn''t applicable till you get near
the end)
http://projects.puppetlabs.com/issues/3101

If you can''t upgrade the whole package, you can find the fix at
http://projects.puppetlabs.com/projects/puppet/repository/revisions/ae0b0bf23e418e8c6665e9dc135148b78bdbd913
and manually use it.  In this case, "use" means:
1) Get the diff
2) Find that file on your client
3) Manually change that file

Someone really needs to make an FAQ entry and try to get that patch into Debian
and Lucid (Ubuntu).

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

On Thu, Oct 21, 2010 at 10:13 AM, Patrick <kc7zzv@gmail.com> wrote:
>
> On Oct 21, 2010, at 8:48 AM, Ed Greenberg wrote:
>
> OK, so I upgraded the puppetmaster server to lucid, which got me the
> puppetmaster 0.25.4.
>
> I am still having issues signing up a new lucid client, and I''ve
foudn this
> in the client''s log:
> Oct 21 15:32:53 edglucid1 puppetd[27061]: Could not request certificate:
> undefin
> ed method `closed?'' for nil:NilClass
>
> Not being initiated in the ways of Ruby, I''m not very well
equipped to
> debug this :)
>
> Any suggestions?
>
>
> The "undefined method `closed?'' for nil:NilClass" error
is a known and very
> confusing bug in 0.25.x, that is fixed in 0.25.5.  It replaces most error
> messages with this "nil:NilClass" error.  Upgrade to fix it, if
you want to
> see the real error.
>
> Bug report: (Most of the information isn''t applicable till you get
near the
> end)
> http://projects.puppetlabs.com/issues/3101
>
> If you can''t upgrade the whole package, you can find the fix at
>
http://projects.puppetlabs.com/projects/puppet/repository/revisions/ae0b0bf23e418e8c6665e9dc135148b78bdbd913
and
> manually use it.  In this case, "use" means:
> 1) Get the diff
> 2) Find that file on your client
> 3) Manually change that file
>
> Someone really needs to make an FAQ entry and try to get that patch into
> Debian and Lucid (Ubuntu).
>
If someone bug reports that to us on Debian, we can get a patch in for that
version.

We''re concentrating on 2.6.x now though due to the freeze.

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

> If someone bug reports that to us on Debian, we can get a patch in for 
> that version.
>
> We''re concentrating on 2.6.x now though due to the freeze.
>
I appreciate all the help I''ve received.

I really don''t know how to file a bug report on Debian, since I
don''t
even know what their release names mean.  I could file a bug against 
Ubuntu Lucid though, and will.

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

On Oct 21, 2010, at 2:20 PM, Nigel Kersten wrote:
> 
> 
> On Thu, Oct 21, 2010 at 10:13 AM, Patrick <kc7zzv@gmail.com> wrote:
> 
> On Oct 21, 2010, at 8:48 AM, Ed Greenberg wrote:
> 
>> OK, so I upgraded the puppetmaster server to lucid, which got me the
puppetmaster 0.25.4.
>> 
>> I am still having issues signing up a new lucid client, and
I''ve foudn this in the client''s log:
>> Oct 21 15:32:53 edglucid1 puppetd[27061]: Could not request
certificate: undefin
>> ed method `closed?'' for nil:NilClass
>> 
>> Not being initiated in the ways of Ruby, I''m not very well
equipped to debug this :)
>> 
>> Any suggestions?
> 
> The "undefined method `closed?'' for nil:NilClass" error
is a known and very confusing bug in 0.25.x, that is fixed in 0.25.5.  It
replaces most error messages with this "nil:NilClass" error.  Upgrade
to fix it, if you want to see the real error.
> 
> Bug report: (Most of the information isn''t applicable till you get
near the end)
> http://projects.puppetlabs.com/issues/3101
> 
> If you can''t upgrade the whole package, you can find the fix at
http://projects.puppetlabs.com/projects/puppet/repository/revisions/ae0b0bf23e418e8c6665e9dc135148b78bdbd913
and manually use it.  In this case, "use" means:
> 1) Get the diff
> 2) Find that file on your client
> 3) Manually change that file
> 
> Someone really needs to make an FAQ entry and try to get that patch into
Debian and Lucid (Ubuntu).
> 
> If someone bug reports that to us on Debian, we can get a patch in for that
version.
Are you talking about cherry picking that patch or switching from 0.25.4 to
0.25.5?  Either works, but I''ll defer to you for which I should file.
> We''re concentrating on 2.6.x now though due to the freeze.
-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Thu, Oct 21, 2010 at 2:27 PM, Patrick <kc7zzv@gmail.com> wrote:
>
> On Oct 21, 2010, at 2:20 PM, Nigel Kersten wrote:
>
>
>
> On Thu, Oct 21, 2010 at 10:13 AM, Patrick <kc7zzv@gmail.com> wrote:
>
>>
>> On Oct 21, 2010, at 8:48 AM, Ed Greenberg wrote:
>>
>> OK, so I upgraded the puppetmaster server to lucid, which got me the
>> puppetmaster 0.25.4.
>>
>> I am still having issues signing up a new lucid client, and
I''ve foudn
>> this in the client''s log:
>> Oct 21 15:32:53 edglucid1 puppetd[27061]: Could not request
certificate:
>> undefin
>> ed method `closed?'' for nil:NilClass
>>
>> Not being initiated in the ways of Ruby, I''m not very well
equipped to
>> debug this :)
>>
>> Any suggestions?
>>
>>
>> The "undefined method `closed?'' for nil:NilClass"
error is a known and
>> very confusing bug in 0.25.x, that is fixed in 0.25.5.  It replaces
most
>> error messages with this "nil:NilClass" error.  Upgrade to
fix it, if you
>> want to see the real error.
>>
>> Bug report: (Most of the information isn''t applicable till you
get near
>> the end)
>> http://projects.puppetlabs.com/issues/3101
>>
>> If you can''t upgrade the whole package, you can find the fix
at
>>
http://projects.puppetlabs.com/projects/puppet/repository/revisions/ae0b0bf23e418e8c6665e9dc135148b78bdbd913
and
>> manually use it.  In this case, "use" means:
>> 1) Get the diff
>> 2) Find that file on your client
>> 3) Manually change that file
>>
>> Someone really needs to make an FAQ entry and try to get that patch
into
>> Debian and Lucid (Ubuntu).
>>
>
> If someone bug reports that to us on Debian, we can get a patch in for that
> version.
>
>
> Are you talking about cherry picking that patch or switching from 0.25.4 to
> 0.25.5?  Either works, but I''ll defer to you for which I should
file.
>
At this stage cherry-picking would be best.

Bug reporting for Debian and Ubuntu is pretty simple to remember with:

http://bugs.debian.org/puppet
http://bugs.ubuntu.com/puppet



>
> We''re concentrating on 2.6.x now though due to the freeze.
>
>
>  --
> 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+unsubscribe@googlegroups.com<puppet-users%2Bunsubscribe@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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Oct 21, 2010, at 2:59 PM, Nigel Kersten wrote:
> 
> 
> On Thu, Oct 21, 2010 at 2:27 PM, Patrick <kc7zzv@gmail.com> wrote:
> 
> On Oct 21, 2010, at 2:20 PM, Nigel Kersten wrote:
> 
>> 
>> 
>> On Thu, Oct 21, 2010 at 10:13 AM, Patrick <kc7zzv@gmail.com>
wrote:
>> 
>> On Oct 21, 2010, at 8:48 AM, Ed Greenberg wrote:
>> 
>>> OK, so I upgraded the puppetmaster server to lucid, which got me
the puppetmaster 0.25.4.
>>> 
>>> I am still having issues signing up a new lucid client, and
I''ve foudn this in the client''s log:
>>> Oct 21 15:32:53 edglucid1 puppetd[27061]: Could not request
certificate: undefin
>>> ed method `closed?'' for nil:NilClass
>>> 
>>> Not being initiated in the ways of Ruby, I''m not very well
equipped to debug this :)
>>> 
>>> Any suggestions?
>> 
>> The "undefined method `closed?'' for nil:NilClass"
error is a known and very confusing bug in 0.25.x, that is fixed in 0.25.5.  It
replaces most error messages with this "nil:NilClass" error.  Upgrade
to fix it, if you want to see the real error.
>> 
>> Bug report: (Most of the information isn''t applicable till you
get near the end)
>> http://projects.puppetlabs.com/issues/3101
>> 
>> If you can''t upgrade the whole package, you can find the fix
at
http://projects.puppetlabs.com/projects/puppet/repository/revisions/ae0b0bf23e418e8c6665e9dc135148b78bdbd913
and manually use it.  In this case, "use" means:
>> 1) Get the diff
>> 2) Find that file on your client
>> 3) Manually change that file
>> 
>> Someone really needs to make an FAQ entry and try to get that patch
into Debian and Lucid (Ubuntu).
>> 
>> If someone bug reports that to us on Debian, we can get a patch in for
that version.
> 
> Are you talking about cherry picking that patch or switching from 0.25.4 to
0.25.5?  Either works, but I''ll defer to you for which I should file.
> 
> At this stage cherry-picking would be best.
> 
> Bug reporting for Debian and Ubuntu is pretty simple to remember with:
> 
> http://bugs.debian.org/puppet
> http://bugs.ubuntu.com/puppet
> 
I can''t figure out how you file a bug against lenny-backports. 
That''s the only notable version of Debian that''s affected now.
Stable, Testing, and Unstable are all either too old or too new.

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