When Pulp checks for remote files, reword the log message to sound non-fatal
When downloading an rpm, pulp checks for treeinfo files and logs ominous messages that users are complaining about:
==> /var/log/messages <== Oct 12 11:32:44 zoo pulp: nectar.downloaders.threaded:INFO: Download failed: Download of https://cdn.redhat.com/content/dist/rhel/server/7/7Server/x86_64/sat-tools/6.3/os/.treeinfo failed with code 404: Not Found Oct 12 11:32:45 cloud-qe-17 pulp: requests.packages.urllib3.connectionpool:INFO: Starting new HTTPS connection (1): cdn.redhat.com Oct 12 11:32:46 cloud-qe-17 pulp: nectar.downloaders.threaded:INFO: Download failed: Download of https://cdn.redhat.com/content/dist/rhel/server/7/7Server/x86_64/sat-tools/6.3/os/treeinfo failed with code 404: Not Found Oct 12 11:32:46 cloud-qe-17 pulp: pulp_rpm.plugins.importers.yum.sync:INFO: [f5963541] Sync complete.
Either don't log these messages, log them at a different level (e.g. DEBUG), or reword it to hide "404" and "Download failed".
#2 Updated by daviddavis about 1 year ago
- Project changed from RPM Support to Pulp
- Description updated (diff)
So this issue is not limited to the RPM plugin. Puppet also does something similar where it checks for a PULP_MANIFEST file and then logs:
Oct 12 16:51:36 pulp2.dev pulp: nectar.downloaders.threaded:INFO: Download failed: Download of http://forge.puppetlabs.com/PULP_MANIFEST failed with code 404: Not Found
#6 Updated by firstname.lastname@example.org 12 months ago
I think it makes sense to keep this at the INFO level, but change the wording to not sound fatal. The reason behind INFO is that it seems reasonable that the user should know that things didn't download. If we move to DEBUG, the task will succeed and the user would have no reason to check DEBUG.
Please register to edit this issue