Puppet users - Nov 2009 - Passenger versions with Puppet 0.25.1 puppetmasterd

So I''ve been playing around with this a bit lately, and I''m
not
entirely clear on the supported versions of Passenger with Puppet
0.25.1 puppetmasterd.

2.2.1 works fine so long as you''re only serving 0.24.8 clients. It
does not work with 0.25.1 clients.

I''ve lost track of the situation with Passenger 2.2.5, I see some
reports saying it works happily, others that it doesn''t.

experiences?

-- 
nigel

--~--~---------~--~----~------------~-------~--~----~
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 06/11/09 19:06, Nigel Kersten wrote:
>
> So I''ve been playing around with this a bit lately, and
I''m not
> entirely clear on the supported versions of Passenger with Puppet
> 0.25.1 puppetmasterd.
>
> 2.2.1 works fine so long as you''re only serving 0.24.8 clients. It
> does not work with 0.25.1 clients.
>
> I''ve lost track of the situation with Passenger 2.2.5, I see some
> reports saying it works happily, others that it doesn''t.
>
> experiences?
I think the following matrix will give you more information. Note, I 
gathered this from #puppet and the various bugs.
I''m not running passenger myself so this might not be accurate.
At least, I think it depicts what people are seeing.
As Volcane usually says: I''ll switch to passenger when
there''ll be less
than 5 reports of issue per day :-)

Puppet  Passenger Status
Master
0.24.8  2.2.2     OK
0.24.8  2.2.3     NO
0.24.8  2.2.4     NO
0.24.8  2.2.5     OK

0.25.1  2.2.2     OK
0.25.1  2.2.3     NO
0.25.1  2.2.4     NO
0.25.1  2.2.5     NO*



[*]: this one should be fixed with Christian revert of c702f7, see 
puppet-dev message-id: <1257416944-2114-1-git-send-email-ch+git@zeha.at>
Note, Christian asked for report on this patch, so if you''re in a 
position to test this revert, please report to puppet-dev.
-- 
Brice Figureau
My Blog: http://www.masterzen.fr/


--~--~---------~--~----~------------~-------~--~----~
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 06/11/09 19:22, Brice Figureau wrote:
>
> On 06/11/09 19:06, Nigel Kersten wrote:
>>
>> So I''ve been playing around with this a bit lately, and
I''m not
>> entirely clear on the supported versions of Passenger with Puppet
>> 0.25.1 puppetmasterd.
>>
>> 2.2.1 works fine so long as you''re only serving 0.24.8
clients. It
>> does not work with 0.25.1 clients.
>>
>> I''ve lost track of the situation with Passenger 2.2.5, I see
some
>> reports saying it works happily, others that it doesn''t.
>>
>> experiences?
>
> I think the following matrix will give you more information. Note, I
> gathered this from #puppet and the various bugs.
> I''m not running passenger myself so this might not be accurate.
> At least, I think it depicts what people are seeing.
> As Volcane usually says: I''ll switch to passenger when
there''ll be less
> than 5 reports of issue per day :-)
>
> Puppet  Passenger Status
> Master
> 0.24.8  2.2.2     OK
> 0.24.8  2.2.3     NO
> 0.24.8  2.2.4     NO
> 0.24.8  2.2.5     OK
I stand corrected, 2.2.3, 2.2.4 do work with a 0.24.8 master, as that 
has been confirmed by Nigel.
-- 
Brice Figureau
My Blog: http://www.masterzen.fr/


--~--~---------~--~----~------------~-------~--~----~
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 Fri, Nov 6, 2009 at 10:50 AM, Brice Figureau
<brice-puppet@daysofwonder.com> wrote:
>
> On 06/11/09 19:22, Brice Figureau wrote:
>>
>> On 06/11/09 19:06, Nigel Kersten wrote:
>>>
>>> So I''ve been playing around with this a bit lately, and
I''m not
>>> entirely clear on the supported versions of Passenger with Puppet
>>> 0.25.1 puppetmasterd.
>>>
>>> 2.2.1 works fine so long as you''re only serving 0.24.8
clients. It
>>> does not work with 0.25.1 clients.
>>>
>>> I''ve lost track of the situation with Passenger 2.2.5, I
see some
>>> reports saying it works happily, others that it doesn''t.
>>>
>>> experiences?
>>
>> I think the following matrix will give you more information. Note, I
>> gathered this from #puppet and the various bugs.
>> I''m not running passenger myself so this might not be
accurate.
>> At least, I think it depicts what people are seeing.
>> As Volcane usually says: I''ll switch to passenger when
there''ll be less
>> than 5 reports of issue per day :-)
>>
>> Puppet  Passenger Status
>> Master
>> 0.24.8  2.2.2     OK
>> 0.24.8  2.2.3     NO
>> 0.24.8  2.2.4     NO
>> 0.24.8  2.2.5     OK
>
> I stand corrected, 2.2.3, 2.2.4 do work with a 0.24.8 master, as that
> has been confirmed by Nigel.
> --
> Brice Figureau
> My Blog: http://www.masterzen.fr/

I''m in the middle of testing 2.2.5 now, and hit this problem.

http://groups.google.com/group/phusion-passenger/browse_thread/thread/21f258f01ebc4126

Once that fix was applied, 0.24.8 and 0.25.1 clients are working
happily for me with an install of the current git 0.25.x branch.

This is on ubuntu hardy btw. I had to build my own
libapache2-passenger, but that''s about it.

--~--~---------~--~----~------------~-------~--~----~
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 Nov 6, 11:32 pm, Nigel Kersten <nig...@google.com>
wrote:
> [..]
> I''m in the middle of testing 2.2.5 now, and hit this problem.
>
> http://groups.google.com/group/phusion-passenger/browse_thread/thread...
>
> Once that fix was applied, 0.24.8 and 0.25.1 clients are working
> happily for me with an install of the current git 0.25.x branch.
So, you''re saying, 2.2.5 works fine with current 0.25.x git, with a
passenger fix applied but not my puppet patch?

If so, then this "passenger is not working" problem puzzles me
completely. Could qualify for a heisenbug.
May I ask what versions of Ruby and Apache you''re using?

Thanks,
Christian
--~--~---------~--~----~------------~-------~--~----~
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 Sat, Nov 7, 2009 at 3:14 AM, Christian Hofstaedtler <ch+git@zeha.at>
wrote:
>
> On Nov 6, 11:32 pm, Nigel Kersten <nig...@google.com> wrote:
>> [..]
>> I''m in the middle of testing 2.2.5 now, and hit this problem.
>>
>>
http://groups.google.com/group/phusion-passenger/browse_thread/thread...
>>
>> Once that fix was applied, 0.24.8 and 0.25.1 clients are working
>> happily for me with an install of the current git 0.25.x branch.
>
> So, you''re saying, 2.2.5 works fine with current 0.25.x git, with
a
> passenger fix applied but not my puppet patch?
Yes.
>
> If so, then this "passenger is not working" problem puzzles me
> completely. Could qualify for a heisenbug.
> May I ask what versions of Ruby and Apache you''re using?
Vanilla versions that come with Ubuntu Hardy of absolutely everything
other than libapache2-passenger, which I built from the git repo at:

http://github.com/FooBarWidget/passenger/

I''ll get exact versions to this thread later as I want to replicate it
with a pure upstream install that doesn''t look at our internal repos
at all.



>
> Thanks,
> Christian
> >
>


-- 
nigel

--~--~---------~--~----~------------~-------~--~----~
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 Sat, Nov 7, 2009 at 8:12 AM, Nigel Kersten <nigelk@google.com>
wrote:
> On Sat, Nov 7, 2009 at 3:14 AM, Christian Hofstaedtler
<ch+git@zeha.at> wrote:
>>
>> On Nov 6, 11:32 pm, Nigel Kersten <nig...@google.com> wrote:
>>> [..]
>>> I''m in the middle of testing 2.2.5 now, and hit this
problem.
>>>
>>>
http://groups.google.com/group/phusion-passenger/browse_thread/thread...
>>>
>>> Once that fix was applied, 0.24.8 and 0.25.1 clients are working
>>> happily for me with an install of the current git 0.25.x branch.
>>
>> So, you''re saying, 2.2.5 works fine with current 0.25.x git,
with a
>> passenger fix applied but not my puppet patch?
>
> Yes.
>
>>
>> If so, then this "passenger is not working" problem puzzles
me
>> completely. Could qualify for a heisenbug.
I just realized I have this in place...

ssl_client_header=HTTP_X_SSL_SUBJECT

could that possibly be changing behavior?

I also have separate virtual hosts for CA and non-CA servers on
different ports. I haven''t fully tested running a 0.25.1 CA under the
above configuration.





>> May I ask what versions of Ruby and Apache you''re using?
>
> Vanilla versions that come with Ubuntu Hardy of absolutely everything
> other than libapache2-passenger, which I built from the git repo at:
>
> http://github.com/FooBarWidget/passenger/
>
> I''ll get exact versions to this thread later as I want to
replicate it
> with a pure upstream install that doesn''t look at our internal
repos
> at all.
>
>
>
>
>>
>> Thanks,
>> Christian
>> >>
>>
>
>
>
> --
> nigel
>


-- 
nigel

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

* Nigel Kersten <nigelk@google.com> [091109
22:22]:
> 
> On Sat, Nov 7, 2009 at 8:12 AM, Nigel Kersten <nigelk@google.com>
wrote:
> > On Sat, Nov 7, 2009 at 3:14 AM, Christian Hofstaedtler
<ch+git@zeha.at> wrote:
> >>
> >> On Nov 6, 11:32 pm, Nigel Kersten <nig...@google.com> wrote:
> >>> [..]
> >>> I''m in the middle of testing 2.2.5 now, and hit this
problem.
> >>>
> >>>
http://groups.google.com/group/phusion-passenger/browse_thread/thread...
> >>>
> >>> Once that fix was applied, 0.24.8 and 0.25.1 clients are
working
> >>> happily for me with an install of the current git 0.25.x
branch.
> >>
> >> So, you''re saying, 2.2.5 works fine with current 0.25.x
git, with a
> >> passenger fix applied but not my puppet patch?
> >
> > Yes.
> >
> >>
> >> If so, then this "passenger is not working" problem
puzzles me
> >> completely. Could qualify for a heisenbug.
> 
> I just realized I have this in place...
> 
> ssl_client_header=HTTP_X_SSL_SUBJECT
> 
> could that possibly be changing behavior?
> 
> I also have separate virtual hosts for CA and non-CA servers on
> different ports. I haven''t fully tested running a 0.25.1 CA under
the
> above configuration.
It''s interesting that it even works. It''s supposed to only
work with
ssl_client_header = SSL_CLIENT_S_DN. Having this configured /wrong/
would lead to clients not getting authorized at all; if your clients
work, then it can''t be actually "wrong".

Are you using an SSL proxy or something else which might change SSL
behaviour?

Thanks,
Christian

-- 
christian hofstaedtler

--~--~---------~--~----~------------~-------~--~----~
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 Mon, Nov 9, 2009 at 1:58 PM, Christian Hofstaedtler <ch+git@zeha.at>
wrote:
>
> * Nigel Kersten <nigelk@google.com> [091109 22:22]:
>>
>> On Sat, Nov 7, 2009 at 8:12 AM, Nigel Kersten <nigelk@google.com>
wrote:
>> > On Sat, Nov 7, 2009 at 3:14 AM, Christian Hofstaedtler
<ch+git@zeha.at> wrote:
>> >>
>> >> On Nov 6, 11:32 pm, Nigel Kersten <nig...@google.com>
wrote:
>> >>> [..]
>> >>> I''m in the middle of testing 2.2.5 now, and hit
this problem.
>> >>>
>> >>>
http://groups.google.com/group/phusion-passenger/browse_thread/thread...
>> >>>
>> >>> Once that fix was applied, 0.24.8 and 0.25.1 clients are
working
>> >>> happily for me with an install of the current git 0.25.x
branch.
>> >>
>> >> So, you''re saying, 2.2.5 works fine with current
0.25.x git, with a
>> >> passenger fix applied but not my puppet patch?
>> >
>> > Yes.
>> >
>> >>
>> >> If so, then this "passenger is not working" problem
puzzles me
>> >> completely. Could qualify for a heisenbug.
>>
>> I just realized I have this in place...
>>
>> ssl_client_header=HTTP_X_SSL_SUBJECT
>>
>> could that possibly be changing behavior?
>>
>> I also have separate virtual hosts for CA and non-CA servers on
>> different ports. I haven''t fully tested running a 0.25.1 CA
under the
>> above configuration.
>
> It''s interesting that it even works. It''s supposed to
only work with
> ssl_client_header = SSL_CLIENT_S_DN. Having this configured /wrong/
> would lead to clients not getting authorized at all; if your clients
> work, then it can''t be actually "wrong".
>
> Are you using an SSL proxy or something else which might change SSL
> behaviour?
Nope. Very vanilla Apache setup.


>
> Thanks,
> Christian
>
> --
> christian hofstaedtler
>
> >
>


-- 
nigel

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

I''ve been testing puppet 0.25.x in a two system test environment for a
while now, just waiting for the day that I could deploy into
production (currently 0.24.8).  Yesterday I applied your patch to
0.25.1 and finally had things working!  Here is my setup:

System A:
  Centos 5.4
  httpd-2.2.3-31.el5.centos
  Ruby enterprise edition 1.8.6-20090610
  passenger 2.2.5
  puppetmaster 0.25.1 + revert patch
  puppet client 0.25.1

System B:
  Centos 5.4
  puppet client 0.24.8

If this patch can make it into 0.25.2, I believe I can finally start
work on upgrading production.

On Sat, Nov 7, 2009 at 4:14 AM, Christian Hofstaedtler <ch+git@zeha.at>
wrote:
> So, you''re saying, 2.2.5 works fine with current 0.25.x git, with
a
> passenger fix applied but not my puppet patch?
>
> If so, then this "passenger is not working" problem puzzles me
> completely. Could qualify for a heisenbug.
> May I ask what versions of Ruby and Apache you''re using?
>
> Thanks,
> Christian
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---