Bug #17524
closedRepository synchronization tries to create all the missing repositories on a remote capsule
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1398438
Description of problem:
If library is synchronized into a capsule, the repository
synchornization also tries to get the content into this capsule.
However, as part of this effort, it checks for all repositories that
were not synchronized into a capsule, and tries to create them there.
This can have a big impact on performance, if there are a lot of
repositories in library, and a new capsule is added to the system to
be synchronized with the library.
How reproducible:
When library is synchonized to capsules
Steps to Reproduce:
1. have a large number of repositories in library
2. add new capsule to the system and add library as an environment to be synchronized
3. synchronize the repository
Actual results:
The synchronization of repository takes much longer, than it should,
the sync task in dynflow sits in "Actions::Katello::Repository::Sync" action,
a lot of trafic between sat and capsule due to checking for status.
Expected results: The sync task is not much slower than without a
capsule present. Only the specific repo is being created when missing on the capsule.
Updated by Brad Buckingham about 8 years ago
- Subject changed from Repository synchronization tries to create all the missing repositories on a remote capsule to Repository synchronization tries to create all the missing repositories on a remote capsule
- Target version set to 147
- Translation missing: en.field_release set to 197
Updated by The Foreman Bot about 8 years ago
- Status changed from New to Ready For Testing
- Assignee set to Brad Buckingham
- Pull request https://github.com/Katello/katello/pull/6475 added
Updated by Brad Buckingham about 8 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset katello|8fbcd7f112e13773a3a2cc18ffc82f72417636e7.