Hi Grant, Not currently via the serialized task result from the API in Pulp2. The data model for Pulp3 already has a created field so this only affects Pulp2.
If you are interested in contributing this feature to Pulp2, the first step is to open a feature request and then we can outline what you would need to do. If you do please post a link to it. A workaround option would be to record the time you made the API request at which generated the task locally somehow (sqlite perhaps?). Waiting time should be start_time - creation_time. With Pulp2 approaching maintenance mode, it may be easier to do the workaround for now until Pulp3 is usable enough for you. More questions or feedback is welcome. All the best, Brian On Fri, May 25, 2018 at 12:13 AM, Grant Byers <[email protected]> wrote: > Hi, > > Is there any means to determine how long a task has been waiting since > (Pulp2)? For example, if I query the tasks endpoint, I get the following; > > > {u'_href': u'/pulp/api/v2/tasks/61d0eabc-5007-43e2-9646-0a1fd987efc3/', > u'_id': {u'$oid': u'5b078c09bebdfa187befb0ae'}, > u'_ns': u'task_status', > u'error': None, > u'exception': None, > u'finish_time': None, > u'id': u'5b078c09bebdfa187befb0ae', > u'progress_report': {}, > u'result': None, > u'spawned_tasks': [], > u'start_time': None, > u'state': u'waiting', > u'tags': [u'pulp:action:consumer_content_applicability_regeneration'], > u'task_id': u'61d0eabc-5007-43e2-9646-0a1fd987efc3', > u'task_type': u'pulp.server.managers.consumer.applicability. > regenerate_applicability_for_consumers', > u'traceback': None, > u'worker_name': None} > > > For monitoring purposes, I'd really like to know how long that task has > been waiting for. I see no way to get that info. > > > Thanks, > Grant > > _______________________________________________ > Pulp-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/pulp-list >
_______________________________________________ Pulp-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-list
