Add unique constraint on rhnPackageNEVRA for name_id, evr_id, package_arch_id. This will resolve a few customer issues that have come up (bz #151797).
unique constraint added to satellite schema and hosted. No testplan.
how can this be tested?
Registering a system to a satellite would make use of the table where this constraint has been added. There isn't really a good way to test this, we opened this bug b/c we saw a customer come up with an issue where this constraint would have prevented the issue, but we never could reproduce the customer's problem.
will qa this.
I registered a few systems successfully using the latest ISO against a sat. This is prod_ready then :-)