NEXUS-28166 (but not same) sometimes rebuilding yum metadata generates unexpectedly smaller filelists.xml.gz file, which doesn't contain expected RPM files so that yum install fails on the client PCs.
NOTE: the metadata of the repository "yum-releases-prd" was rebuilt hourly.
The request.log shows good sizes until around 09:30, then after rebuilding the metadata by the thread ID: event-20-thread-130817, the file size became almost half, then fixed automatically from around 17:44:
When the rebuild ran, it knew the rpmCount is 621:
But counting 'Adding RPM' shows much less number than other threads' counts:
Can't reproduce internally. Also it does not seem to happen frequently on customer's environment, but can last for hours. However certain features are in use where this was occurring:
- customer has scheduled regular ( every 60 minutes) tasks to manually rebuild the yum metadata for the affected repo - one of these tasks truncated the filelists file
- staging/move operations are being used while running 3.32.0 instance (
NEXUS-28166still in play )
- The rebuilding yum metadata task should be more robust (shouldn't generate significantly different size files)
- At least it should provide more logging information when it didn't add the expected number.