On Apr 25, 4:59 am, Juan José Presa Rodal <[email protected]> wrote: > Ok, but then this response is unconsistent: > > # puppet resource package linux-headers-server > > package { 'linux-headers-server': > ensure => '2.6.32.41.48', > > } > > I thought that if ensure property wasn't "absent", package provider make > nothing...
Much depends on the package versioning. Given that declaration, the agent will do nothing in the event that version 2.6.32.41.48 of a package named 'linux-headers-server' is installed. If no package with that name is installed, then Puppet will attempt to install the specified version of it. If a different version is installed, then Puppet will attempt to up/downgrade to the specified version. I'm not very clear on Ubuntu package naming and versioning involved here, but I'm suspicious that you may be mixing the two. Is 'linux- headers-server' actually the *name* of the package you want, or is it perhaps the name and version? (That is, could it refer to version "server" of the "linux-headers" package?) The latter would constitute an error in your manifest, but Puppet is not necessarily able to recognize that. You could consider running the agent in debug mode toget the actual commands Puppet is issuing recorded in the client-side log. Look not only at the package installation command, but also at the preceding package query command. You would want also to refer to the appropriate repository metadata for the package(s) you're looking at. 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.
