Bug 873421 - Oddities in sync progress after task group move
Summary: Oddities in sync progress after task group move
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Pulp
Classification: Retired
Component: user-experience
Version: 2.0.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: Sprint 42
Assignee: Michael Hrivnak
QA Contact: Preethi Thomas
URL:
Whiteboard:
Depends On: 857998
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-05 19:54 UTC by Jay Dobies
Modified: 2013-09-09 16:32 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 857998
Environment:
Last Closed: 2013-01-09 17:09:20 UTC
Embargoed:


Attachments (Terms of Use)

Description Jay Dobies 2012-11-05 19:54:03 UTC
+++ This bug was initially created as a clone of Bug #857998 +++

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

Comment 1 Michael Hrivnak 2012-11-20 17:10:42 UTC
Consulting with jdob, we decided to just make the message more reasonable by changing it to "Waiting to begin next step".

https://github.com/pulp/pulp/pull/150

Comment 2 Jeff Ortel 2012-11-20 22:19:56 UTC
build: 2.0.6-0.3.beta

Comment 3 Preethi Thomas 2012-11-27 02:22:34 UTC
verified

[root@preethi-el6-pulp ~]# rpm -q pulp-server
pulp-server-2.0.6-0.9.beta.noarch
[root@preethi-el6-pulp ~]# 
[root@preethi-el6-pulp ~]# pulp-admin rpm repo sync run --repo-id scientific
+----------------------------------------------------------------------+
                 Synchronizing Repository [scientific]
+----------------------------------------------------------------------+

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:       562/562 items
Delta RPMs: 0/0 items
Tree Files: 0/0 items
Files:      0/0 items
... completed

Importing errata...
[/]
... completed

Importing package groups/categories...
[-]
... completed

Publishing packages...
[==================================================] 100%
Packages: 0/0 items
... completed

Publishing distributions...
[==================================================] 100%
Distributions: 0/0 items
... completed

Generating metadata
[|]
... completed

Publishing repository over HTTPS
[-]
... completed

Publishing repository over HTTP
[-]
... skipped

[root@preethi-el6-pulp ~]#

Comment 4 Preethi Thomas 2013-01-09 17:09:20 UTC
Pulp v2.0 released


Note You need to log in before you can comment on or make changes to this bug.