Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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
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