On Feb 26, 5:19 am, christian <[email protected]> wrote:
> I did some testing with your plugin on OpenSuse 11.1 and I’d like to
> offer some suggestions:
>
> 1. You should consider adding the zypper option "--force-resolution"
> to line 25 like:
> output = zypper "--quiet", :install, "-l", "-y", "--force-
> resolution" , wanted
>
> Otherwise i ran into some problems during the installation of some
> packages, e.g. replacing postifx with sendmail gave me:
>
> Problem: postfix-2.5.5-6.8.x86_64 conflicts with sendmail provided by
> sendmail-8.14.3-50.9.i586
> Solution 1: deinstallation of
> postfix-2.5.5-6.8.x86_64
> Solution 2: do not ask to install a solvable providing
> sendmail
>
> Choose from above solutions by number or cancel [1/2/C]: c
>
> As you can see zypper chose to cancel the installation, but I actually
> wanted to install that package so I added the „--force-resolution“
> option to your code and zypper chose solution 1.
Interesting -- perhaps the better solution would be to do a
package { "postfix": ensure => absent, before => Package["sendmail"] }
package { "sendmail": ensure => present }
At least then you know what puppet will do. I have no issue adding --
force-resolution, I just don't know if it would cause any issues with
uninstalling packages that may conflict -- for instance:
package { ["postfix", "sendmail"]: ensure =>latest }
Would cause issues with --force-resolution and I'm not sure how puppet
*should* handle that. I think someone on the core team should provide
input.
> 2. I don’t know if it’s a general puppet problem, false configuration
> or caused by your plugin…If a client receives the plugin for the first
> time, everything works just fine. But if I change anything in my
> manifests and a puppet-client runs again I always get this error:
> „err: Could not run Puppet configuration client: Invalid package
> provider 'zypper' at /etc/puppet/modules/webserver/manifests/
> webserver.pp:8“
I don't see this behavior. What I am doing is putting it in modules/
plugins/lib/puppet/provider/package/zypper.rb and having pluginsync =
true in my client's puppetd.conf and making sure modulepath is set
properly.
> In order to get the client working again, I have to add some random
> characters to the zypper.rb, so the puppet-master thinks that there
> were some changes to the plugin and updates the file on the client.
Yeah that's definitely strange to me. Can you try installing a
package with specific version? (I.e. ensure => "2.1.0") or
something... ) I've seen an issue where it will say package not found,
however if you cut and paste the exact line, it somehow finds it. Can
you reproduce it?
Thanks,
Andrew
> Christian
>
> On 4 Feb., 22:16, Andrew Forgue <[email protected]> wrote:
>
>
>
> > On Feb 4, 2:45 am, Peter <[email protected]> wrote:
>
> > > is there a possibility to integrate the function to install package-
> > > groups (Patterns) ?
>
> > > zypper install -t pattern <package-group-name>
>
> > > How sure is the integration of zypper in version 0.25.5 ?
>
> > Interesting, I'm not sure how that would work. You can install a
> > pattern simply by adding the '-t pattern', but when you try to remove
> > it, it says 'Uninstallation of a pattern is currently not defined and
> > implemented.' (SLES11) And when trying to upgrade it, even when you
> > supply the -t pattern, it tries to upgrade the package (appears to be
> > yet-another-zypper-bug). Novell seems to be rife with those.
>
> > In any case, it's simple to implement for installation, but I don't
> > have confidence that upgrading or removing a pattern would work at
> > all.
>
> > Zypper in 0.25.x is non-existent until this patch (Bug #1223) is
> > applied, but you can take my lib/puppet/provider/package/zypper.rb
> > file from my branch (mentioned in a previous post) and use it as a
> > plugin in your environment and it should work fine with provider =>
> > zypper in your manifests.
>
> > Andrew
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" 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-dev?hl=en.
