Thanks for your reply John. I read about your first solution which you 
posted earlier but I'm trying the second one. 

yum repo: (This was updated)

Available Packages
libstdc++.i686                                                             
                  4.4.7-4.el6                                               
                           
libstdc++.x86_64                                                           
                4.4.7-4.el6

Current package on agent:

libstdc++-4.4.7-3.el6.i686
libstdc++-4.4.7-3.el6.x86_64

Puppet Master:

In hiera

packages::aa_app_req:
  - libtiff
  - libpng
  - libstdc++.x86_64
  - libtiff.i686
  - libpng.i686
  - libstdc++.i686

In manifest

  $aa_app_req_array = hiera_array('packages::aa_app_req')
  package { $aa_app_req_array:
#    ensure => installed,
    ensure => latest,
  }

Now as the repository has been updated recently and the agent already has 
previous version of both arch installed, the next puppet run fails with the 
multilib error. If you could help me understand whether I'm implementing 
the 2nd solution correctly?

Error: Could not update: Execution of '/usr/bin/yum -d 0 -e 0 -y install 
libstdc++.x86_64' returned 1: Error: Protected multilib versions: 
libstdc++-4.4.7-4.el6.x86_64 != libstdc++-4.4.7-3.el6.i686
 You could try using --skip-broken to work around the problem


thanks,
amogh

On Thursday, 3 April 2014 09:26:57 UTC-5, jcbollinger wrote:
>
>
>
> On Wednesday, April 2, 2014 10:18:59 AM UTC-5, amogh patel wrote:
>>
>> Hi Puppet Users,
>>
>> I'm facing below error after the repo updates:
>>
>> Error: Execution of '/usr/bin/yum -d 0 -e 0 -y install libstdc++.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.
>>
>> rotected multilib versions: libstdc++-4.4.7-4.el6.i686 != 
>> libstdc++-4.4.7-3.el6.x86_64
>>  You could try using --skip-broken to work around the problem
>>
>> same with libtiff.
>>
>> Googled and found a work around using exec but how can we address 
>> application package upgrade which requires both architecture.
>>
>>
>
> Package names and multilib are a bit of a sore spot for Puppet at the 
> moment, but there are at least two approaches you could try:
>
>    1. Manage yum.conf to ensure that the 'multilib_policy' is set to 
>    'all'.
>    2. Manage arch-specific packages, e.g. "libstdc++.i686" and 
>    "libstdc++.x86_64".  This may also depend on having matching versions in 
>    your repository
>
> Both approaches require that your package repositories contain matching 
> package versions for each architecture where there are packages for 
> multiple architectures at all.
>
>
> John
>
>

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/0adc97af-7e6d-4615-888f-b34583621980%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to