I am working on some initial testing of puppet and noticed that when
using the package type, I see this in my client logs (from different runs):
warning: Found multiple default providers for package: up2date, yum;
using up2date
warning: Found multiple default providers for package: yum, up2date;
using yum
This is on a CentOS 4.4 client with puppet-0.22.0-1.el4 (from dlutter
repo). After reviewing the type noted on package, it sounded like
forcing the provider should not be needed, but puppet seems to be a bit
nondeterministic here, so what is the correct way to force a global
default? I''m guessing it is something like (from the wiki):
case $operatingsystem {
centos: {
Package { type => yum }
}
}
Assuming that works, I''m good, just curious why this should be
necessary
given the statement in the type docs, and more importantly, why does the
decision change from run to run?
Thanks,
Mark
--
Mark D. Nagel, CCIE #3177 <mnagel@willingminds.com>
Principal Consultant, Willing Minds LLC (http://www.willingminds.com)
cell: 949-279-5817, desk: 714-630-4772, fax: 949-623-9854
On Sun, 2007-02-04 at 11:15 -0800, Mark D. Nagel wrote:> I am working on some initial testing of puppet and noticed that when > using the package type, I see this in my client logs (from different runs): > > warning: Found multiple default providers for package: up2date, yum; > using up2date > warning: Found multiple default providers for package: yum, up2date; > using yumSounds like a bug ... can you file that in trac and attach the output of facter to the ticket ? David
On Feb 5, 2007, at 8:12 AM, David Lutterkort wrote:> On Sun, 2007-02-04 at 11:15 -0800, Mark D. Nagel wrote: >> I am working on some initial testing of puppet and noticed that when >> using the package type, I see this in my client logs (from >> different runs): >> >> warning: Found multiple default providers for package: up2date, yum; >> using up2date >> warning: Found multiple default providers for package: yum, up2date; >> using yum > > Sounds like a bug ... can you file that in trac and attach the > output of > facter to the ticket ?There''s basically no way for Puppet to get consistent ordering of these, barring sorting by name or something. I use a hash to store the providers, and hashes will return different sort orders all the time. I can''t even use load-order, because then you''re relying on the order in which the filesystem returns the file names, which isn''t any more consistent across clients. The truth is that you have two perfectly valid package managers here and you do have to pick one. We should probably have ''yum'' marked as the default for any platform that has it installed, but I don''t use any Red Hat platforms, so I''m not in a position to recommend for or against that. -- It''s impossible to foresee the consequences of being clever. -- Christopher Strachey --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com
On Mon, 2007-02-05 at 11:13 -0600, Luke Kanies wrote:> The truth is that you have two perfectly valid package managers here > and you do have to pick one.Yes, that''s the fix that''s needed.> We should probably have ''yum'' marked as > the default for any platform that has it installed, but I don''t use > any Red Hat platforms, so I''m not in a position to recommend for or > against that.On RHEL4 or earlier, that would be wrong; it''s actually pretty messy there, since there are legitimate reasons for users to have both, and use up2date. The rules need to go sth like: for FC, CentOS and RHEL >= 5, use yum if it''s installed, for RHEL <= 4 use up2date. I''ll try and have a look at it soonish. Assign the bug to me. David
On Feb 5, 2007, at 3:27 PM, David Lutterkort wrote:> On Mon, 2007-02-05 at 11:13 -0600, Luke Kanies wrote: >> The truth is that you have two perfectly valid package managers here >> and you do have to pick one. > > Yes, that''s the fix that''s needed. > >> We should probably have ''yum'' marked as >> the default for any platform that has it installed, but I don''t use >> any Red Hat platforms, so I''m not in a position to recommend for or >> against that. > > On RHEL4 or earlier, that would be wrong; it''s actually pretty messy > there, since there are legitimate reasons for users to have both, and > use up2date. > > The rules need to go sth like: for FC, CentOS and RHEL >= 5, use > yum if > it''s installed, for RHEL <= 4 use up2date. I''ll try and have a look at > it soonish. Assign the bug to me.Is there actually an open bug? I couldn''t find it. -- I worry that the person who thought up Muzak may be thinking up something else. --Lily Tomlin --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com