Hi Patrick,

On 02/11/2011 07:40 PM, Patrick wrote:

[...]

> 1) So, just some random advice.  If you're using the same server to
> serve files and catalogs, you can skip listing the server and just
> use 3 slashes like this: 
> puppet:///files/rpm-sles11sp1/ruby-shadow-$myrshadowversion.x86_64.rpm

I see but I've just added this during the debugging procedure of our
nameservers, anyhow your advice is welcome :)

>  2) You sure it's not easier to just create a repository right now
> instead?

Of course and I would really like to but for the moment we're facing
some serious issues which won't fix in time. Thats the major reason for
me searching a temporary solution.

> 3) What if you try using "ensure => installed" in the package?  Does
> that work?

This won't work because puppet (as of version 0.24.x) is already
installed on all nodes. That's the reason why I want puppet to upgrade
the package _only_ if a newer version is available. When using "ensure
=> installed" the package won't be upgraded because "some version" is
already installed.

However, I haven't checked it by myself but I think that the same error
message will be thrown if using "ensure => latest" on other packages,
right? If yes, would you say that its a bug or a feature? ;)

I want to get rid of that error message to keep the log files clean
maybe to let them be checked on errors by our monitoring agent at a
later time. The rest of the manifest seems to work just fine also with
this error message coming up.

> 4) I assume you're getting one of those errors for every package.  Is
> that true?

Yes, that's correct.

Jan

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

Reply via email to