Creating a custom target e.g. rhel-3es-athlon on a system does not allow rpm's within the Athlon channel to be seen.
Since YUM Repostructure is not a standard , the YUM mirror subscription in ZLM, cannot handle all the compatible archs packages for a given OS target platform.
For example ,mapping(i386,i586,i686,noarch) arch packages to 32 bit target platform is not supported in zlm. As a result of this, existing YUM implementation of ZLM cannot identify athlon arch as any of the existing target platforms. The athlon arch packages needs to be mirrored only as custom target platform (rhel-3es-athlon) into the bundle . The other 32 bit target compatible packages can be mirrored into the same bundle and later athlon package needs to be converted to32 bit target platform of the registered device.
The steps to achieve this is as follows :
1)Mirror the 32 bitcompatible packages (i386,i586,i686,noarch) with target rhel-4es-i386 into a givenbundle
2)Mirror the athlon arch packages for target rhel-4es-athlon into same or another bundle
3) Convert the athlon packages in the bundle from rhel-3es-athlon target to rhel-3es-i386 target in the bundle as follows :
zlman bap --freshen=truebundle_name rhel-3es-i386/var/opt/novell/zenworks/pkg-repo/bundles/first_two_letters_of_the_bundle_GUID/bundle_GUID/bundle_version/rhel-3es-athlon/*.rpm