Bug 1991527
Summary: | Many Postgres ERRORs (duplicate key) especailly on RedHat repo sync | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Brad Buckingham <bbuckingham> |
Component: | Documentation | Assignee: | Nobody <nobody> |
Documentation sub component: | default | QA Contact: | |
Status: | CLOSED WONTFIX | Docs Contact: | |
Severity: | medium | ||
Priority: | unspecified | CC: | dkliban, ggainey, peter.vreman, ttereshc |
Version: | 6.9.0 | ||
Target Milestone: | Unspecified | ||
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2023-06-13 00:18:35 UTC | Type: | Bug |
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: | 1957813 |
Description
Brad Buckingham
2021-08-09 11:04:54 UTC
Bug 1989182 was also created for a duplicate constraint on rpm_variant_variant_id_ . The duplicate keys are seen in different database (base on ttable names) and might be good to be split in a pulp3 BZ and katello BZ E.g. the following is katello code: ~~~ 3990 postgresql-Thu.log:2021-07-01 03: ERROR: duplicate key value violates unique constraint "katello_erratum_bz_eid_bid_href" 18171 postgresql-Thu.log:2021-07-01 03: ERROR: duplicate key value violates unique constraint "katello_erratum_packages_eid_nvrea_n_f" ~~~ Input for a Reproducer, i sync the following RHEL7 repos, simaliar setup repos also for RHEL8. - RHEL 7.6 E4S Server Optional Sat6.8-Tools Sat6.9-Tools - RHEL 7.7 EUS Server Optional Sat6.8-Tools Sat6.9-Tools - RHEL 7.7 E4S Server Optional Sat6.8-Tools Sat6.9-Tools - RHEL 7.9 Server Optional Sat6.8-Tools Sat6.9-Tools - RHEL 7Server Server Optional Sat6.8-Tools Sat6.9-Tools - RHSCL There are several upstream tickets like https://pulp.plan.io/issues/8967 and https://pulp.plan.io/issues/9029 that are talking about syncing repos with same content. That kind of matches my setup where 7Server=7.9 have and also 7.7-EUS=7.7-E4S share same content. And with RHEL8 you even have 3 repos RHEL8.4=RHEL8.4-EUS=RHEL-8.4-E4S with same content Hope this input helps for engineering to build reproducers I as user of the end-to-end Satellite Repo+CV+CVV functionality did not notice any functional restricts from the errors The ContentView and CompositeContentView creates were working without issues and on the client (1x RHEL7.9, 1x RHEL8.4, 1x 7Server (the Sat6 and Capsule itself)) i did not see any abnormal behaviour that content was missing The major issue i noticed is the filling of the postgres filesystem huge postgres logs that are unreadable due to excesive (up to 1500000 chars) long lines Thanks Peter! I've created bug 1991557 to track the katello errors. I have also downgraded the severity since the error itself is not resulting in failure of the sync/publish. If there are no sync/publish failures, the current BZ is unrelated to the Bug 1989182, https://pulp.plan.io/issues/8967 or https://pulp.plan.io/issues/9029. In all those, task will fail. I suspect that it's more of implementation approach to solve race conditions. We'll see what we can do. In order to solve potential race conditions during sync/upload/cleanup operations, various db records might be attempted to be created when they are already there. Also for performance reasons, bulk operations are used and in some cases, can cause `duplicate key...` records in the postgres logs. For the sake of data consistency, currently there are no plans to adjust anything in this area. This comment is relevant for the Pulp related records (do not have word `katello` or `dynflow` in them). I propose to close this BZ. If it is on purpose that ERRORs in log files are expected it shall at least be documented and explained why they are harmless. That i have opened a BZ for it is a sign that at least some users care about clean logs. Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team. Thank you. Thank you for your interest in Red Hat Satellite. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this feel free to contact your Red Hat Account Team. Thank you. |