Bug 516573

Summary:	last sync time for yum repo (in channel) shows start-time instead of end-time
Product:	[Community] Spacewalk	Reporter:	Sandro Mathys <sandro>
Component:	WebUI	Assignee:	Tomas Lestach <tlestach>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	medium	Docs Contact:
Priority:	low
Version:	0.6	CC:	jpazdziora, tlestach
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-07-21 14:43:36 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	695242

Description Sandro Mathys 2009-08-10 14:09:36 UTC

Description of problem:
'last sync time' of an 'associated yum repository' of a software channel shows the time of the last time the sync started. this should either:
- show the end time or
- show the start time _after_ the sync completed

Right now, it looks like the sync finished, because the sync start-time is shown as soon as the sync started. For example with F11 (where os+updates = 17+k pkgs), there's a big difference between start and end time.

Version-Release number of selected component (if applicable):
# rpm -qa | grep spacewalk
spacewalk-backend-0.6.30-1.el5
spacewalk-html-0.6.19-1.el5
spacewalk-backend-server-0.6.30-1.el5
spacewalk-backend-app-0.6.30-1.el5
spacewalk-backend-package-push-server-0.6.30-1.el5
spacewalk-base-minimal-0.6.19-1.el5
spacewalk-monitoring-selinux-0.6.12-1.el5
spacewalk-setup-0.6.21-1.el5
spacewalk-0.6.4-1.el5
spacewalk-backend-xml-export-libs-0.6.30-1.el5
spacewalk-backend-config-files-tool-0.6.30-1.el5
spacewalk-backend-iss-0.6.30-1.el5
spacewalk-java-0.6.42-1.el5
spacewalk-pxt-0.6.19-1.el5
spacewalk-moon-0.6.19-1.el5
spacewalk-monitoring-0.6.7-1.el5
spacewalk-selinux-0.6.13-1.el5
spacewalk-repo-0.6-1.el5
spacewalk-java-config-0.6.42-1.el5
spacewalk-doc-indexes-0.6.1-1.el5
spacewalk-backend-config-files-common-0.6.30-1.el5
spacewalk-backend-config-files-0.6.30-1.el5
spacewalk-backend-applet-0.6.30-1.el5
spacewalk-taskomatic-0.6.42-1.el5
spacewalk-base-0.6.19-1.el5
spacewalk-grail-0.6.19-1.el5
spacewalk-sniglets-0.6.19-1.el5
spacewalk-admin-0.6.3-1.el5
spacewalk-schema-0.6.22-1.el5
spacewalk-certs-tools-0.6.3-1.el5
spacewalk-config-0.6.13-1.el5
spacewalk-java-lib-0.6.42-1.el5
spacewalk-branding-0.6.8-1.el5
spacewalk-backend-sql-0.6.30-1.el5
spacewalk-backend-xmlrpc-0.6.30-1.el5
spacewalk-backend-iss-export-0.6.30-1.el5
spacewalk-backend-xp-0.6.30-1.el5
spacewalk-search-0.6.11-1.el5
spacewalk-cypress-0.6.19-1.el5
spacewalk-backend-tools-0.6.30-1.el5


How reproducible:
Always

Steps to Reproduce:
1. start new sync of a big yum repo
2. check the 'last sync time'
  
Actual results:
immediately shows sync start-time

Expected results:
doesn't show a new time before the sync has finished

Comment 1 Jan Pazdziora (Red Hat) 2010-11-19 16:05:40 UTC

Mass-moving to space13.

Comment 2 Tomas Lestach 2011-01-28 13:13:44 UTC

Hello Sandro,

I triggered a reposync of a large channel.

I see on WebUI:

* Last Modified:	2011-01-28 14:09:28 CET
* Last Repo Build:	2011-01-25 10:45:13 CET
* Last Sync Time:	2011-01-25 10:47:28 CET

So, the reposync is running ... 

# ps aux | grep spacewalk-repo-sync
root     18395  6.0  2.1 512680 181224 ?       S    06:11   7:15 /usr/bin/python -u /usr/bin/spacewalk-repo-sync --channel fedora14 --type yum
root     20503  0.0  0.0  61148   752 pts/4    S+   08:10   0:00 grep spacewalk-repo-sync

Actual time:
# date
Fri Jan 28 08:11:22 EST 2011
(what shall be aprox. the same as (Last Modified), just different TZ)

But "Last Sync Time" is definitely 3 days older than the current time, when repo-sync is running.

Does it look good to you?

Comment 3 Miroslav Suchý 2011-04-11 07:34:15 UTC

We did not have time for this one during Spacewalk 1.4 time frame. Mass moving to Spacewalk 1.5.

Comment 4 Miroslav Suchý 2011-04-11 07:37:28 UTC

We did not have time for this one during Spacewalk 1.4 time frame. Mass moving to Spacewalk 1.5.

Comment 5 Jan Pazdziora (Red Hat) 2011-05-10 12:11:28 UTC

I confirm that the date/time gets updated only once the spacewalk-repo-sync has finished -- tested on Satellite 5.4, so roughly Spacewalk 1.2.

Comment 6 Jan Pazdziora (Red Hat) 2011-07-21 14:43:36 UTC

Spacewalk 1.5 was released.