Red Hat Bugzilla – Bug 644880
Possibility to assign 64 package into 32 channel by channel.software.addPackages
Last modified: 2011-03-17 10:12:37 EDT
Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. take 32b channel (I have clone of rhel-i386-server-5)
2. push 64b package to the satellite
3. client.channel.software.addPackages(key, chan, [pkgId])
package is assigned to the channel
64b package should not be allowed in 32b. channel.
This is not a regression against Sat530.
Note to QA: (nice to test)
After the reproducer from comment 0, when there is 64b package
in the 32. channel. Errata.create api call will fail with strange
<Fault -1: 'redstone.xmlrpc.XmlRpcFault: unhandled internal
exception: The server architecture (AMD64) is incompatible
with the channel architecture (IA-32)'>
when attempting to create new errata containing that package
in that channel.
Adding an arch compatibility check.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Not checking for arch compatibility, when adding a package to channel using channel.software.addPackages API
A package of non-compatible arch may land in a channel
Arch non-compatible packages won't be added into a channel when using channel.software.addPackages API
speeding up of the API call:
fix permission check to packages:
Not a good day ...
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.