Project

General

Profile

Actions

Bug #8770

closed

Repository syncs should initiate capsule sync asynchronously

Added by Justin Sherrill over 9 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Normal
Category:
Foreman Proxy Content
Target version:
Difficulty:
Triaged:
Yes
Fixed in Releases:
Found in Releases:

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:

Actions #1

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 ()
Actions #2

Updated by Justin Sherrill over 9 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions #3

Updated by Eric Helms over 9 years ago

  • Translation missing: en.field_release set to 14
Actions #4

Updated by Eric Helms over 9 years ago

  • Triaged changed from No to Yes
Actions

Also available in: Atom PDF