Bug #8770
closed
Repository syncs should initiate capsule sync asynchronously
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1176157
Description of problem:
Currently in the sync dynflow action, after the repo sync in pulp is finished, we initiate a node metadata generation and sync as part of the sync task. this means that if the capsule is not running the sync task will hang until the capsule comes back online.
It should behave just like the content view publish/promote and initiate it as a 2nd entire action which is not dependent on the first.
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1. Install a capsule and associate it with library
2. Shut down the capsule
3. Attempt to sync a repo
Actual results:
Sync hangs around 69%
Expected results:
Sync completes successfully
Additional info:
Updated by The Foreman Bot over 9 years ago
- Status changed from New to Ready For Testing
- Target version set to 62
- Pull request https://github.com/Katello/katello/pull/4887 added
- Pull request deleted (
)
Updated by Justin Sherrill over 9 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset katello|82cd0a41d1374fedd00550debb5b05da671663ef.
Updated by Eric Helms over 9 years ago
- translation missing: en.field_release set to 14