Project

General

Profile

Actions

Bug #6008

closed

Capsule: Puppet content doesn't appear to be published to /etc/puppet/environments on capsule

Added by Ivan Necas almost 10 years ago. Updated almost 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
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=1103277
Description of problem:

When content is synced from Satellite 6 to Capsule, it doesn't appear that the puppet content from the Satellite is making its way to the Capsule (i.e. /etc/puppet/environments)

Version-Release number of selected component (if applicable):
katello-1.5.0-25.el6sat.noarch

How reproducible:
always

Steps to Reproduce:
1. install/configure sat6
2. install/configure capsule (in my case, it is on a separate machine from the sat6)

on the sat6 server:
3. sync some rhel content (e.g. 6Server)
4. create a custom repo and import some puppet modules
5. create a content view
6. add the content from 3 & 4 to the content view
7. publish a content view version

8. associate the capsule (from 2) with the Library using the cli, e.g.
capsule content add-lifecycle-environment --id 4 --environment-id 1
9. sync the content to the capsule, e.g.
capsule content synchronize --id 4

Actual results:

Satellite 6: /etc/puppet/environments has content (e.g. KT_ACME_Corporation_Library_WordPress__Application_3)
Capsule: /etc/puppet/environments is empty

Expected results:

Capsule: /etc/puppet/environments should have the same environments that were in

Additional info:

Actions

Also available in: Atom PDF