Project

General

Profile

Actions
Copy link

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.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Katello Recycle Bin
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

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?

Actions
Copy link
 #1

Updated by Chris Roberts about 3 years ago

  • 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.

Actions
Copy link

Also available in: Atom PDF