Bug 2184151
| Summary: | katello:clean_backend_objects false alarms on systems with >1500 clients when PUTing customer facts | |||
|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Pavel Moravec <pmoravec> | |
| Component: | Hosts - Content | Assignee: | satellite6-bugs <satellite6-bugs> | |
| Status: | CLOSED ERRATA | QA Contact: | Cole Higgins <chiggins> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | medium | |||
| Version: | 6.12.2 | CC: | ahumbe, bkearney, chiggins, jlenz, jpasqual, jsenkyri, myoder, nmoumoul, rlavi, visawant, wderick, wpinheir, zhunting | |
| Target Milestone: | 6.15.0 | Keywords: | Triaged, WorkAround | |
| Target Release: | Unused | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | rubygem-katello-4.11.0.9-1.el8sat | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 2272113 (view as bug list) | Environment: | ||
| Last Closed: | 2024-04-23 17:14:02 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: | ||||
|
Description
Pavel Moravec
2023-04-03 18:33:58 UTC
Hi Michael and Jeremy, rather double-check confirmation: The code fix in ':sort_by => "uuid"' will help also when virt-who is updating it mapping between the paginated "get me consumers" requests, am I right? (we had a very unlucky customer where 6.12->6.13 upgrade run automatic clean_backend_objects script with COMMIT=true, and at exactly that "bad" time, virt-who sent its mapping - this ended up in 600 Hosts unregistered during the upgrade) Also, when considering impacts of the sorting; shall not it be rather per `created` timestamp (ascending ordering)? What if a new Host is registered just during the clean_backend_objects execution - its new uuid can break the linearity/ordering of "get me consumers per pages" responses.. > shall not it be rather per `created` timestamp (ascending ordering)? What if a new Host is registered just during the clean_backend_objects execution - its new uuid can break the linearity/ordering of "get me consumers per pages" responses..
Hey Pavel
I thought about this as well. If we still have problems we can change it again to sort by created, but the reason we didn't do this from the start is that the "all_uuids" method we altered is currently restricted to only the "uuid" field and does not include the "created" field in the response.
This change should help when more consumers are added during the rake task, no matter if they're added by virt-who mapping or another method.
Hi Pavel/Jeremy, The issue I discovered was because candlepin was duplicating ids, instead of getting a unique list. It happened with an organization with 6,065 host ids. Candlepin was returning 6,065 host uuids, but they were not all unique, it was getting duplicate hosts in its output. So really candlepin had roughly 5,000 unique ids, while katello had 6,065 unique ids. Which means they had a different count, so hosts got removed. I don't think there is any linearity/ordering issue. The issue was just about a unique list of hosts ids. So if one is added, and is out of order, shouldn't matter (unless katello doesn't have that id in its list). I could have missed something, but that was my understanding of the code. Kind regards, Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: Satellite 6.15.0 release), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2024:2010 |