Project

General

Profile

Actions

Bug #14512

closed

Empty puppet repo results in failed capsule sync

Added by John Mitsch almost 8 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
API
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1322098
Description of problem:

When creating a puppet repo within sat6 we do not actually publish the empty repo. The result of that is that when the capsule syncs, that puppet repo will fail to sync and throw an error

Version-Release number of selected component (if applicable):
Sat 6.2 snap 4

How reproducible:
Always

Steps to Reproduce:
1. Create a puppet repo, do not upload or sync any modules
2. Sync a capsule that is attached to the library environment

Actual results:
Capsule sync Task will error and be left in 'warning state'

Expected results:
Capsule sync task is successful

Additional info:

For yum repos we 'publish' the metadata for them at creation time. We should do the same for puppet repos

Actions #1

Updated by The Foreman Bot almost 8 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to John Mitsch
  • Pull request https://github.com/Katello/katello/pull/5944 added
Actions #2

Updated by John Mitsch almost 8 years ago

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

Updated by Eric Helms almost 8 years ago

  • translation missing: en.field_release set to 86
Actions

Also available in: Atom PDF