Project

Profile

Help

Story #2978

As a user, applicability task is visible in the task list

Added by jsherril@redhat.com about 2 years ago. Updated 6 months ago.

Status:
NEW
Priority:
Normal
Assignee:
-
Category:
API
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Platform Release:
Blocks Release:
Backwards Incompatible:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:

Description

Right now task group tasks (such as those for applicability generation) are completely invisible to pulp-admin

This makes it more difficult to tell what pulp is doing and generally causes confusion. Things that should be simple to answer become very difficult, such as:

  • what are my pulp workers doing?
  • why isn't my sync running?
  • what is currently running on this worker?

This would greatly help to debug issues.

History

#1 Updated by jsherril@redhat.com about 2 years ago

  • Subject changed from Make task group tasks visible to Make task-group tasks visible

#2 Updated by mhrivnak about 2 years ago

FWIW the fact that these tasks are related to a task group is a coincidence and not related to whether or not they appear as a "user-facing" task.

#3 Updated by ttereshc about 2 years ago

  • Tracker changed from Issue to Story
  • Subject changed from Make task-group tasks visible to As a user, applicability task is visible in the task list
  • % Done set to 0

#5 Updated by ttereshc over 1 year ago

Easy workaround is to look into DB directly:

Number of all tasks which are running or waiting to be picked up:
$ mongo pulp_database --eval 'db.task_status.find({"state": {"$in": ["waiting","running"]}}).count()'

List of all those tasks (write to a file if there are many tasks):
$ mongo pulp_database --eval 'db.task_status.find({"state": {"$in": ["waiting","running"]}}).forEach(printjson)' > tasks_list.log

#6 Updated by bmbouter 6 months ago

  • Tags Pulp 2 added

Please register to edit this issue

Also available in: Atom PDF