I see that the job recognizes 3399 packages to download and those the number of RPMs that are failed to download.
If the analysis is not showing any patches as missing, it could be a case of the metadata not getting updated. I remember this happening once with one of the customers when they made changes in the filter of the existing catalog and re-ran the job.
Is it possible to try updating the catalog again and see what happens?
It is worth checking the appserver logs during the time of the error as well.
We definitely need to know the exact appserver build as Bill suggested.
Thanks. Build number is 8.5.01.96. I tried downloading the catalog multiple times. But same issue.
Can you let me know how did you manage to resolve the issue at the customer place
Are you seeing this behavior in other catalogs as well?
What happens when you create a new catalog? Is that failing with the same error too?
If the new catalog is successful, then we are sure that it’s something with this catalog. Most probably the metadata (repodata.tar.gz file on the repo server)
Yes. I tried creating a new catalog. Same issue. Infact we have one more entity wherein we have same version and same issue.
Any suggestions on this?
I have tried creating a new catalog again and the situation is same. However, I have noticed some errors in the appserver.log file when the patch download is trying to connect to the RHN site.
I suspect it has something to do with the proxy. My proxy does not require any username and password hence I have kept it blank in the patch global configuration and windows catalog download works fine. The error which I am talking about is pasted below. I have also attached the appserver.log files.
I have checked the URL's listed in the below error and I am able to download the packages from them on the application server.
Can anybody let me know why this is happening?
[28 Mar 2016 13:54:56,861] [PSU-Thread-24] [INFO] [BLAdmin:BLAdmins:] [Patch-Metadata-Updator] Using proxy: proxy type - SQUID, host name - 10.0.228.80
[28 Mar 2016 13:54:56,861] [PSU-Thread-24] [INFO] [BLAdmin:BLAdmins:] [Patch-Metadata-Updator] Setting the proxy credentials
[28 Mar 2016 13:54:56,908] [PSU-Thread-23] [DEBUG] [BLAdmin:BLAdmins:] [Patch-Metadata-Updator] received response  for url [https://rhn.redhat.com/rhn/software/packages/details/Overview.do?pid=655153]
[28 Mar 2016 13:54:56,908] [PSU-Thread-23] [DEBUG] [BLAdmin:BLAdmins:] [Patch-Metadata-Updator] Caught Exception: https://rhn.redhat.com/rhn/software/packages/details/Overview.do?pid=655153
com.bmc.sa.patchfeed.FeedException: Could not parse download Url from details page of package: https://rhn.redhat.com/rhn/software/packages/details/Overview.do?pid=655153
at com.bmc.sa.patchfeed.redhat.util.RhnWebService.getPackageDownloadUrl(Unknown Source)
at com.bmc.sa.patchfeed.redhat.util.RhnWebService.downloadPayload(Unknown Source)
at com.bmc.sa.patchfeed.redhat.util.RhnDownloadTask.run(Unknown Source)
at com.bmc.sa.patchfeed.util.net.DefaultThreadPool$1.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
appserver.log.zip 4.3 MB
there were some fixes in the 8.5.01 patches to account for redhat site changes - i would suggest upgrading to 8.5.01 patch5 or 8.6+ if you haven't already.