Bug 2173718
| Summary: | pulpcore core_progressreport table gets out of sync with core_task table with no easy/recommended way to clean it up | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Paul Dudley <pdudley> |
| Component: | Pulp | Assignee: | satellite6-bugs <satellite6-bugs> |
| Status: | CLOSED MIGRATED | QA Contact: | Satellite QE Team <sat-qe-bz-list> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.12.1 | CC: | dalley, dkliban, ggainey, rchan |
| Target Milestone: | Unspecified | Keywords: | MigratedToJIRA, Triaged |
| 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: | 2024-06-06 16:09:21 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: | |||
test bz update - disregard This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. |
Through various cases and environments now I've noticed that often the core_task and core_progressreport table can get out of sync with one another. For example; ─────────────────────────────────────────────────────────────────────── [root@satellite ~]# echo "select pulp_id, name, state, worker_id from core_task where state = 'running';" | su - postgres -c "psql pulpcore" pulp_id | name | state | worker_id ---------+------+-------+----------- (0 rows) [root@satellite ~]# echo "select pulp_id, pulp_created, pulp_last_updated, message, total, done, state from core_progressreport where state in ('running');" | sudo -u pulp PULP_SETTINGS='/etc/pulp/settings.py' pulpcore-manager dbshell | wc 47 675 10093 ─────────────────────────────────────────────────────────────────────── The discrepancy has no impact on the Satellite or Pulp as far as I can tell. Really my only concern is the reliability of the progressreport table - seeing running tasks there and believing there are running tasks without checking the tasks table first. It would be good to have some process of cleaning the progressreport table if it doesn't already exist. Perhaps a process to reference core_task and remove entries in progressreport if the pulp_ids no longer exist, or correct the state if the state of the ID doesn't match between the tables. Ultimately, however, I'm not familiar enough with the progressreport table and it's significance to know if these questions make sense to address so please correct me there if needed, as well. Thanks