Bug 1011934

Summary:	taskomatic: repodata is not being regenerated for cloned channel
Product:	[Community] Spacewalk	Reporter:	daniel.schunack <daniel.schunack>
Component:	Server	Assignee:	Michael Mráka <mmraka>
Status:	CLOSED EOL	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	2.0
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-10-21 11:39:21 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description daniel.schunack@computacenter.com 2013-09-25 12:19:21 UTC

Description of problem:
We lost all repodata files under /var/cache/rhn/repodata. Taskomatic create new repodata files for the original Base Channels, but not for our Cloned Channels. 
We test it in Spacewalk 1.8 and taskomatic create the repodata files for all channel. As workaround we change the Repository Checksum Type and taskomatic create new repodata files.
All packages up2date.


Version-Release number of selected component (if applicable):
spacewalk-backend-server-2.0.3-1.el6.noarch
spacewalk-taskomatic-2.0.5-1.el6.noarch

RedHat 6.3; 2.6.32-279.22.1.el6.x86_64

Steps to Reproduce:
Delete Cloned Channel repodata under /var/cache/rhn/repodata and restart taskomatic.

Comment 1 daniel.schunack@computacenter.com 2013-11-28 14:45:42 UTC

Any news?

Comment 2 Michael Mráka 2013-11-28 15:20:10 UTC

Repodata generation is triggered either when there's a change made to the channel, e.g. new package synced or repository checksum changed, or a client requests repodata from the channel and they aren't available.

So for cloned channels either cloning new package to it or access from a client should trigger repodata re-generation.

Comment 3 daniel.schunack@computacenter.com 2013-11-29 14:54:28 UTC

Yes, if the folder not exist the repodate will re-generated.
Sorry, I forgot the say if the files in the folder zero or corrupted nothing happens.

Comment 4 daniel.schunack@computacenter.com 2013-12-17 12:17:49 UTC

Any news?

Comment 5 daniel.schunack@computacenter.com 2014-01-15 15:44:11 UTC

Any news?

Comment 7 Michael Mráka 2019-10-21 11:39:21 UTC

Spacewalk 2.8 (and older) has already reached it's End Of Life.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before end of life. If you would still like
to see this bug fixed and are able to reproduce it against current version
of Spacewalk 2.9, you are encouraged change the 'version' and re-open it.