Bug 152426
Summary: | Add unique constraint on rhnPackageNEVRA for name_id, evr_id, package_arch_id | ||
---|---|---|---|
Product: | Red Hat Satellite 5 | Reporter: | James Slagle <jslagle> |
Component: | Other | Assignee: | James Slagle <jslagle> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike McCune <mmccune> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | unspecified | CC: | rhn-bugs |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | RHN 4.0.0 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-09-01 02:53:05 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 147875 |
Description
James Slagle
2005-03-29 14:05:18 UTC
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 :-) |