My guess is that the code loops over each task and does the same thing. That handling has the potential to sit at "Waiting to begin" if it's encountered while the task being rendered is at the waiting state. This can cause an oddity if the sync completes and the publish has yet to begin. See the example below. We should either prefix each section to make it clear that it's the publish portion that's waiting to begin or only display that "Waiting to begin" message on the first task in the group. pulp-admin repo sync run --repo-id pulp +----------------------------------------------------------------------+ Synchronizing Repository [pulp] +----------------------------------------------------------------------+ This command may be exited by pressing ctrl+c without affecting the actual operation on the server. Downloading metadata... [\] ... completed Downloading repository content... [==================================================] 100% RPMs: 35/35 items Delta RPMs: 0/0 items Tree Files: 0/0 items Files: 0/0 items ... completed Importing errata... [-] ... completed Importing package groups/categories... [-] ... completed [-] Waiting to begin Publishing packages... [==================================================] 100% Packages: 0/0 items ... completed Publishing distributions... [==================================================] 100% Distributions: 0/0 items ... completed Generating metadata [\] ... completed Publishing repository over HTTP [-] ... skipped Publishing repository over HTTPS [-] ... completed Successfully synchronized repository