On Mar 8, 3:54 pm, Mike <[email protected]> wrote: > Why does puppet return an error when a package is already installed?
It doesn't. > I use ensure => installed to make sure that a package is installed, and > then have a file that is dependent on that package. When the manifest is > applied and the package is already installed, it reports an error and then > doesn't do anything with the file. Isn't this a bug? The package type is > just supposed to ensure that the package is installed. If it sees that it > is already installed, that should be a good thing, not an error. Puppet checks whether the package is already installed before attempting to install it. If no change is needed then Puppet doesn't do anything. Based on the other thread in which you are asking about this, I conclude that you are lying to Puppet about the name of the package. The RPM file you designate in your Package resource contains a package named differently than the package name you specified. It will work correctly if you give Puppet the correct package name, as Nan described. It's much better, though, to set up a local yum repository to serve packages to your clients, even for only a handful of packages. John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
