How puppet install another version of the same package.

[shlo....@gmail.com]

Hi 

I want to install same package with a 2 different version like:

libstdc++-4.4.7-3.el6.i686

libstdc++-4.4.7-3.el6.x86_64

I put it in puppet init file and when I run puppet I get:

err: /Package[libstdc++]/ensure: change from 4.4.7-3.el6 to 4.4.7-4.el6.i686 failed: Could not update: Execution of '/usr/bin/yum -d 0 -e 0 -y install libstdc++-4.4.7-4.el6.i686' returned 1: Error:  Multilib version problems found. This often means that the root cause is something else and multilib version checking is just pointing out that there is a problem.

I have libstdc++-4.4.7-3.el6.x86_64 installed already. 

When I run yum from the command like it run okay and install both version.

What I can do to make puppet install it too.

Thanks.

[Flamarion Jorge]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi,

I have same "problem" and my workaround, until discovery solution,has
been to use a "exec" function and run yum command.

This works for me.

Flamarion Jorge

Em 05/03/14 03:42, shlo....@gmail.com escreveu:

> -- You received this message because you are subscribed to the
> Google Groups "Puppet Users" group. To unsubscribe from this group
> and stop receiving emails from it, send an email to
> puppet-users...@googlegroups.com
> <mailto:puppet-users...@googlegroups.com>. To view this
> discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/c2318c1f-25a9-442d-867e-336ebd5aeceb%40googlegroups.com
>
>
<https://groups.google.com/d/msgid/puppet-users/c2318c1f-25a9-442d-867e-336ebd5aeceb%40googlegroups.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/groups/opt_out.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJTFvzXAAoJEJhPZF0zwv0zn2sP/iaoowsgzbewTQfF3Wlt0kj1
6TxXGgmGo8Gy6AaLC2pmPj484WYUEbSgJkbA3Rbj5caqdLNiJzZ2EdtF5PAWY+tt
7OGwMaANETL52mgopJ+ApEIPw2pBY04NV4yfKSwhz8aN3jG2W2AnyCYvn9D+4feT
lvDcycZQ9wW0UbRzq8UQ1nEWwwJcaDzbnBpE2C4yMRwiNr1tpjTCmP4T5M9YRY3h
ptrlCcCEWahF3RscbQqHG5M+vFS5JKZmfSiqBNNRE/s4EWKDN1i2kKCz3bLmoRt+
Dy/Sf0eD7mBeU4LqU1BDO6cvxXQJKMDHBe7RsqtNJYdV42ibzNupuA8ZB0X418PH
73aLWVzeiWJ46+utfFOSL//wntNDbCWfaH3w6sKulWoXjfHdk7hO1JLIwk84kKaU
RuWx2PAaLo1Jn9aWshfpWybgYRdFASMqWdf4/ZeG9FaBv4RuHN3P6IOJB1Bks+zf
fbHR3TnpTTjjRTWRnq04eOVkNe0EJSfYtJ2OwCGU4pWUARDi3CVKGZuPin85k/i5
7hQ5ESJMH6MERbcnHFP1T7jYgBG7d7g/sLaqLt+S5xq6YYefak6ZSa+Qt5EX81iI
1QIhNgX+FfRnLSyAJwiezGpbTDSzESNtjWvAG2vjGZNVYDiNHjs/Yj35JkhiXeKl
y8inW+s7zvhWyW0GVA6I
=OVro
-----END PGP SIGNATURE-----

[Felix Frank]

Interesting use case. Sounds like we may be lacking a feature here.

Shlo, is the yum command working when you paste it just the way puppet
issues it, or are you skipping all the fancy parameters of puppet's?

Cheers,
Felix

[shlo....@gmail.com]

Hi,

I did not understand what you mean, I can tell what I did:

I run on one computer the command:

    puppet resource package

I took the output and put it in puppet. Run puppet  on another computer and I got this error.

Thanks.

[Felix Frank]

On 04/23/2014 08:25 AM, shlo....@gmail.com wrote:
>
> Hi,
> I did not understand what you mean, I can tell what I did:
> I run on one computer the command:
> puppet resource package
> I took the output and put it in puppet. Run puppet on another computer
> and I got this error.
> Thanks.

That's interesting new information. What is that output of `puppet
resource package`?

Thanks,
Felix

[shlo....@gmail.com]

The output contain :

....

warning: Package libstdc++ found in both yum and yum; skipping the yum version

.....

package { 'libstdc++':

  ensure => '4.4.7-4.el6',

}

.... other packages ...

[Felix Frank]

Hmm, okay.

On 04/23/2014 12:44 PM, shlo....@gmail.com wrote:
> The output contain :
>
> ....
> warning: Package libstdc++ found in both yum and yum; skipping the
> yum version

I can reproduce the effect. I suspect this happens when yum presents
several different versions of a package for the same architecture.

> .....
> package { 'libstdc++':
> ensure => '4.4.7-4.el6',
> }
> .... other packages ...

And this piece of manifest yields that error message? Humm.

What is the difference between the output of `yum info libstdc++` on the
box where you run `puppet resource` vs. the box where you want to apply
the manifest?