Description of problem: When syncing a custom repository (product), if there are some packages that fail to download we now receive the error: PLP0000: Importer indicated a failed response. The rest of the sync information is still there indicating successfully downloaded packages (if any) and how many failed. For my example, I synced EPEL 5 and received: New packages: 4941 (3.68 GB). Failed to download 3296 packages. PLP0000: Importer indicated a failed response. When we goto the EPEL product and check this EPEL 5 repo now, it shows 0 packages and 0 errata available. How reproducible: So far, 100%. Steps to Reproduce: 1. Add custom product (Like EPEL). 2. Sync EPEL (typically, it will fail to download /all/ packages on the first sync, and you will see the results I have above. 3. Check product page under repo tab and view that it shows 0 packages in repo even though there were some successfully downloaded per the task data. Actual results: Packages are not indexed after encountering a partial sync completion and do not show up under the product repo. Expected results: Packages that were successfully synced should show up under the product. Additional info: I was able to get some of the package count to show up after I ran a re-index following recieving this error during a sync of EPEL 5, although the number that appears under the product is smaller than the number the task reported to download successfully.
This bug may relate to these two fixes that were implemented into Satellite 6: https://github.com/Katello/katello/pull/5680 https://github.com/Katello/katello/pull/5567
Moving 6.2 bugs out to sat-backlog.
Brad, I think the component for this should not be Pulp. Perhaps you can find a better one for it?
I'm changing the component since the issue appears to be with how and when katello queries pulp. Let me know if there's anything to be done on the pulp side for this.
Justin, with the changes that have gone in to Satellite 6.2, would the described behavior still exist?
I believe this behavior still exists. What works now on (some time before 6.2.6) is that re-syncing will properly re-index the content even if nothing changed on the 2nd sync. We might have to think about this a bit, lets say I sync a repo and it syncs some of the rpms, but not all. Does the metadata for that repo get generated? Should it? If it doesn't get generated (and thus the client will not see the new rpms), should we index them?
(In reply to Justin Sherrill from comment #6) > We might have to think about this a bit, lets say I sync a repo and it syncs > some of the rpms, but not all. Does the metadata for that repo get > generated? Should it? Yes it gets generated. Download errors are so common for yum repos that we just note the error in the task status, but the overall task succeeds, and a publish task gets queued as normal. You can know for sure if new metadata gets generated based on whether a publish task gets queued and succeeds.
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.