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.
Description of problem:
When goferd starts a task, it logs something like:
Dec 19 10:47:43 content-host goferd: [INFO][worker-0] gofer.rmi.dispatcher:600 - call: Content.install() sn=a985fe88-42f6-470d-bffd-59f072006770 data={'task_id': '097edece-e591-493a-8bb2-4dae29944b31', 'consumer_id': 'e40450f9-e1f4-45ca-836c-db8874c27142'}
Since the task might fail silently or take random time, it would be great to log also when the task was completed, with some correlation to the call log (i.e. via sn value).
Doing so will simplify troubleshooting goferd issues.
Version-Release number of selected component (if applicable):
python-gofer-2.6.8-1.el7sat.noarch
How reproducible:
100%
Steps to Reproduce:
1. Invoke some goferd task
2. Check in /var/log/messages when it started and was completed.
Actual results:
Just task started even is logged.
Task completion is not logged.
Expected results:
Also log task completion.
Additional info:
FIWI, goferd does log completion with a message like:
goferd: [INFO][worker-0] gofer.agent.rmi:144 - Request: a985fe88-42f6-470d-bffd-59f072006770 processed in: 22 (ms)
But, you need to match the 'sn=a985fe88-42f6-470d-bffd-59f072006770' and 'Request: a985fe88-42f6-470d-bffd-59f072006770'. Agreed, this could be much more user friendly.
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.
Description of problem: When goferd starts a task, it logs something like: Dec 19 10:47:43 content-host goferd: [INFO][worker-0] gofer.rmi.dispatcher:600 - call: Content.install() sn=a985fe88-42f6-470d-bffd-59f072006770 data={'task_id': '097edece-e591-493a-8bb2-4dae29944b31', 'consumer_id': 'e40450f9-e1f4-45ca-836c-db8874c27142'} Since the task might fail silently or take random time, it would be great to log also when the task was completed, with some correlation to the call log (i.e. via sn value). Doing so will simplify troubleshooting goferd issues. Version-Release number of selected component (if applicable): python-gofer-2.6.8-1.el7sat.noarch How reproducible: 100% Steps to Reproduce: 1. Invoke some goferd task 2. Check in /var/log/messages when it started and was completed. Actual results: Just task started even is logged. Task completion is not logged. Expected results: Also log task completion. Additional info: