Feature #34225
closed
synchronization - instead of stopping at first error, try to complete
Added by Brad Van Orden about 3 years ago.
Updated about 3 years ago.
Description
Instead of the synchronization process stopping at the first error encountered, can it just note the error and continue? That way, it will synchronize as completely as possible and just report that it was not complete because of these issues?
- Status changed from New to Rejected
- Target version changed from Katello 4.4.0 to Katello Recycle Bin
- Triaged changed from No to Yes
Hi Brad,
Pulp handles the syncing and this would be better suited as an issue on their redmine. I am closing this out as there is not much we can do on our side since we just get the info back from Pulp.
Also available in: Atom
PDF