packages listed as incorrect until second bcfg2 client run - centos

[Aaron Levy]

This is because yum is installing both i386 and x86_64 packages and bcfg2 doesn't like it. On the second run bcfg2 resolves the conflict and reports all packages as properly managed.

This can be manually resolved by adding "exclude=*.i?86" to the yum.conf.

A full solution is to put the yum.conf under bcfg2 management. Steps this includes:
 - create a TGenshi template for yum.conf based on arch probe (i386 excludes x86_64 packages and vice versa)
 - Must start using bcfg2 1.1.0rc2 as it contains code to place a managed yum.conf/repo files before doing any package/bundle installations.
 - The above means that we will probably need to setup our own repo to store the 1.1.0rc2 rpms