Bug 1369208

Summary:	Spacewalk-repo-sync --sync-kickstart does not work with Fedora x86-64
Product:	[Community] Spacewalk	Reporter:	Luzemario <luzemario>
Component:	Server	Assignee:	Jan Dobes <jdobes>
Status:	CLOSED EOL	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	2.5	CC:	jdobes
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-03-13 13:30:06 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 Luzemario 2016-08-22 16:27:57 UTC

Description of problem:
Spacewalk-repo-sync with --sync-kickstart does not sync kickstart files from fedora repos. Distro is always invalid asking for images/pxeboot/vmlinuz and images/pxeboot/initrd.img files if these files are copied manually, Anaconda stops asking for squashfs,img file, and installation can't continue. If you supply this file too, installation aborts by Anaconda claiming for @core packages.

Version-Release number of selected component (if applicable):


How reproducible:

From a working Spacewalk, use spacewalk-repo-sync --sync kickstart to add any of Fedora 22 or 23 x86_64 repos. After a long sync time, distro-trees are created for these distros but are invalid.

Steps to Reproduce:
1. Use "spacewalk-repo-sync --sync-kickstart -c fedora22-x86_64" (or -c fedora23-x86_64
2. Spacewalk-repo-sync synchronizes the repo, but not the kickstartable tree
3. You end with a broken kickstartable tree. Adding the missing files does not resolve the problem.

Actual results:
The kickstartable tree don't have the needed files to boot. Installation cannot continue.

Expected results:
The kickstartable tree must contain all files for Fedora 22/23 to boot. The files for installation must provide the @core group, to allow a complete Fedora install.

Additional info:
All systems tested can deploy CentOS/Redhat kickstarts with no issues.

Comment 1 Jan Dobes 2016-08-31 16:42:48 UTC

Which Fedora repository do you have assigned to channel?

Comment 2 Luzemario 2016-08-31 19:07:50 UTC

As main repo, the Fedora23-x86-64 (Netinstall). As child, I synced and checked the client from yum.spacewalkproject.org for Fedora23-x86_64. Anaconda/DNF repo logs show all child repos added, but not the main repo, despite it being chosen and the key being configured correctly.

Comment 3 Michael Mráka 2020-03-13 13:30:06 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.