Bug 1396030

Summary:	Missing files for given errata/packages
Product:	[Community] Spacewalk	Reporter:	Thomas Schweikle <tschweikle>
Component:	Server	Assignee:	Michael Mráka <mmraka>
Status:	CLOSED EOL	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	2.4
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:	2019-10-21 13:12:08 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 Thomas Schweikle 2016-11-17 09:58:00 UTC

Description of problem:
After spacewalk synced via spacewalk-repo-sync started internally or on commandline, I am noticed via WebUI about systems outdated. Trying to install updated packages to these systems They report:

<system>	17.11.16 10:37:07 MEZ	Failed: Packages failed to install properly: Package nss-tools-0:3.21.3-2.0.1.el7_3.x86_64 is not available for installation Package nss-sysinit-0:3.21.3-2.0.1.el7_3.x86_64 is not available for installation Package policycoreutils-0:2.5-9.0.1.el7.x86_64 is not available for installation Package nss-util-0:3.21.3-1.1.el7_3.x86_64 is not available for installation Package nss-0:3.21.3-2.0.1.el7_3.x86_64 is not available for installation

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


How reproducible:
Always. Some packages are not available since days from spacewalk, without any error messages anywhere: policycoreutils-0:2.5-9.0.1.el7.x86_64.

Steps to Reproduce:
1. Install spacewalk 2.4, create repos to sync, create channels, register systems, then force syncing all channels
2. Start upgrading packages, as soon as systems are announced outdated
3. Watch the packages missing from spacewalk.

Actual results:
Packages are not installed, because they are "not available"
But: using pure "yum upgrade" with the very same repositories, the spacewalk server shall sync installation will succeed!
 
Expected results:
Spacewalk holding the "missing" packages and installing them seeamlessly

Additional info:
Pacakges are announced outdated for systems, installing them will fail with "not available for installation". Activating the repository locally, then using "yum upgrade" will install this very same package instantly. Thus: the package was recognized by spacewalk, but not downloaded to the local repository.

I could not find any error message for such behaviour. Such errors seem to be silent any only noticeable by not upgradeable packages.

Comment 1 Thomas Schweikle 2016-11-17 11:36:38 UTC

These "missing" files are downloaded. The downloaded files pass checksums and gpg-check. Length and size are OK too. But they are not delivered to the clients: these report "Package <XYZ> is not available for installation". Trying to resync this repository again does not help: same as before. Logs do only state the file. No information on download, checksum, gpg-check.

Comment 2 Michael Mráka 2019-10-21 13:12:08 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.