Puppet users - Jul 2008 - chicken/egg problem with custom types

Hi

while usings DavidS mysql module with its custom mysql types I hit some
kind of a chicken/egg problem:

While deploying mysql, I also like to define some mysql munin user, to
enable munin monitoring for mysql things. I choosed to use the
mysql_user type from DavidS and it works perfectly. However I start
using the custom types on a host where mysql have already been installed.

Now I should bootstrap a new mysql server and puppet is failing, with
the error, that no handler for the type mysql_user can be found. This is
obviously because no mysql is yet installed and therefor no mysqlbinary
is installed which is used by the custom types. So a typical chicken/egg
problem: mysql should be installed, but the manifests are failing
because mysql isn''t yet installed.

I tried to add require => Package[''mysql''] to the
mysql_user type,
however this doesn''t work, as this is only for ordering in the
execution
graph, but the fail already happens in the evaluation/compiling part of
the manifests.

so how would you solve that problem? my current solution is to have a
custom fact, which is set to true if the mysql binary is present and
wrap the inital mysql-types with this fact. but in my opinion this is
just a current workaround and not a solution.

any ideas?

greets pete

--~--~---------~--~----~------------~-------~--~----~
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 Jul 1, 2008, at 8:54 AM, Peter Meier wrote:
> Now I should bootstrap a new mysql server and puppet is failing, with
> the error, that no handler for the type mysql_user can be found.  
> This is
> obviously because no mysql is yet installed and therefor no  
> mysqlbinary
> is installed which is used by the custom types. So a typical chicken/ 
> egg
> problem: mysql should be installed, but the manifests are failing
> because mysql isn''t yet installed.

This shouldn''t be happening with 0.24.4 -- the provider should only  
check at evaluation time whether the provider is valid.

It could be that I actually made this fix in the current 0.24.x  
branch, though; would you be willing to test it, if you''re already  
running 0.24.4?

This is something I''ve been working on, and I think I''ve
finally
quashed all of the early provider validation bugs.

-- 
Basic research is what I am doing when I don''t know what I am doing.
     --Wernher von Braun
---------------------------------------------------------------------
Luke Kanies | http://reductivelabs.com | http://madstop.com


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

Hi
>> Now I should bootstrap a new mysql server and puppet is failing, with
>> the error, that no handler for the type mysql_user can be found.  
>> This is
>> obviously because no mysql is yet installed and therefor no  
>> mysqlbinary
>> is installed which is used by the custom types. So a typical chicken/ 
>> egg
>> problem: mysql should be installed, but the manifests are failing
>> because mysql isn''t yet installed.
> 
> 
> This shouldn''t be happening with 0.24.4 -- the provider should
only
> check at evaluation time whether the provider is valid.
> 
> It could be that I actually made this fix in the current 0.24.x  
> branch, though; would you be willing to test it, if you''re already
> running 0.24.4?
> 
> This is something I''ve been working on, and I think I''ve
finally
> quashed all of the early provider validation bugs.

I''m using 0.24.4 and the new server is now bootstrapped, but I can test
one tomorrow and can test it with 0.24.X. If I''ll still encounter this
problem, I''ll file a ticket.

greets pete


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

Hi
>>> Now I should bootstrap a new mysql server and puppet is failing,
with
>>> the error, that no handler for the type mysql_user can be found.  
>>> This is
>>> obviously because no mysql is yet installed and therefor no  
>>> mysqlbinary
>>> is installed which is used by the custom types. So a typical
chicken/
>>> egg
>>> problem: mysql should be installed, but the manifests are failing
>>> because mysql isn''t yet installed.
>>
>> This shouldn''t be happening with 0.24.4 -- the provider should
only
>> check at evaluation time whether the provider is valid.
>>
>> It could be that I actually made this fix in the current 0.24.x  
>> branch, though; would you be willing to test it, if you''re
already
>> running 0.24.4?
>>
>> This is something I''ve been working on, and I think
I''ve finally
>> quashed all of the early provider validation bugs.
> 
> 
> I''m using 0.24.4 and the new server is now bootstrapped, but I can
test
> one tomorrow and can test it with 0.24.X. If I''ll still encounter
this
> problem, I''ll file a ticket.

unfortunately it took me some time to test it and I can confirm that
with today''s checked out git-version I still have the problem.

Luke: should I file a bug?

greets pete

--~--~---------~--~----~------------~-------~--~----~
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 Jul 13, 2008, at 9:48 AM, Peter Meier wrote:
>
> Hi
>
>>>> Now I should bootstrap a new mysql server and puppet is
failing,
>>>> with
>>>> the error, that no handler for the type mysql_user can be
found.
>>>> This is
>>>> obviously because no mysql is yet installed and therefor no
>>>> mysqlbinary
>>>> is installed which is used by the custom types. So a typical  
>>>> chicken/
>>>> egg
>>>> problem: mysql should be installed, but the manifests are
failing
>>>> because mysql isn''t yet installed.
>>>
>>> This shouldn''t be happening with 0.24.4 -- the provider
should only
>>> check at evaluation time whether the provider is valid.
>>>
>>> It could be that I actually made this fix in the current 0.24.x
>>> branch, though; would you be willing to test it, if you''re
already
>>> running 0.24.4?
>>>
>>> This is something I''ve been working on, and I think
I''ve finally
>>> quashed all of the early provider validation bugs.
>>
>>
>> I''m using 0.24.4 and the new server is now bootstrapped, but I
can
>> test
>> one tomorrow and can test it with 0.24.X. If I''ll still
encounter
>> this
>> problem, I''ll file a ticket.
>
>
> unfortunately it took me some time to test it and I can confirm that
> with today''s checked out git-version I still have the problem.
>
> Luke: should I file a bug?
Yes, please, and provide as much information as you can, of course.

-- 
Neonle will continue to be rude, and will nretend that you had a small
stroke which makes you unable to say or see the letter "n". Stunid
nractical joke, if you ask me. Bunch of noon-heads, huh?
     -- Fred Barling, Humorscope
---------------------------------------------------------------------
Luke Kanies | http://reductivelabs.com | http://madstop.com


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

Hi
>>>>> Now I should bootstrap a new mysql server and puppet is
failing,
>>>>> with
>>>>> the error, that no handler for the type mysql_user can be
found.
>>>>> This is
>>>>> obviously because no mysql is yet installed and therefor no
>>>>> mysqlbinary
>>>>> is installed which is used by the custom types. So a
typical
>>>>> chicken/
>>>>> egg
>>>>> problem: mysql should be installed, but the manifests are
failing
>>>>> because mysql isn''t yet installed.
>>>> This shouldn''t be happening with 0.24.4 -- the
provider should only
>>>> check at evaluation time whether the provider is valid.
>>>>
>>>> It could be that I actually made this fix in the current 0.24.x
>>>> branch, though; would you be willing to test it, if
you''re already
>>>> running 0.24.4?
>>>>
>>>> This is something I''ve been working on, and I think
I''ve finally
>>>> quashed all of the early provider validation bugs.
>>>
>>> I''m using 0.24.4 and the new server is now bootstrapped,
but I can
>>> test
>>> one tomorrow and can test it with 0.24.X. If I''ll still
encounter
>>> this
>>> problem, I''ll file a ticket.
>>
>> unfortunately it took me some time to test it and I can confirm that
>> with today''s checked out git-version I still have the problem.
>>
>> Luke: should I file a bug?
> 
> Yes, please, and provide as much information as you can, of course.
I''m sorry. I couldn''t preproduce the problem on 2 dbservers
which had to
be staged. so it looks like it really have been fixed. cool :-)

greets pete



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