Hide Forgot
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.
Moving 6.2 bugs out to sat-backlog.
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.