Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira ( If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1107327 - Cannot provision systems via capsule content
Summary: Cannot provision systems via capsule content
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Foreman Proxy
Version: 6.0.3
Hardware: Unspecified
OS: Unspecified
Target Milestone: Unspecified
QA Contact: Corey Welton
Depends On:
Blocks: 1030584
TreeView+ depends on / blocked
Reported: 2014-06-09 22:41 UTC by Corey Welton
Modified: 2019-09-25 20:47 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2014-07-02 14:06:55 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 6145 0 None None None 2016-04-22 15:37:59 UTC

Description Corey Welton 2014-06-09 22:41:36 UTC
Description of problem:
When users configure capsules as their puppet master/puppet ca, content is still pulled from main sat to populate new VMs.  This is because the content source on the sat itself is, for the most part, hardcoded to the path on the sat.  There is no way to point this to capsule.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.  Create and sync content to a capsule
2.  Create a hostgroup, etc., pointing to your capsule for puppet master/ca
3.  Try to create a new libvirt host using the hostgroup above

Actual results:
Notification in main sat logs:
D, [2014-06-09T21:38:46.592955 #23661] DEBUG -- : Starting task (total: 0): /usr/bin/wget --timeout=10 --tries=3 --no-check-certificate -nv -c -O "/var/lib/tftpboot//boot/RedHat-6.5-x86_64-vmlinuz"
D, [2014-06-09T21:38:46.660651 #23661] DEBUG -- : Starting task (total: 0): /usr/bin/wget --timeout=10 --tries=3 --no-check-certificate -nv -c -O "/var/lib/tftpboot//boot/RedHat-6.5-x86_64-initrd.img"

Expected results:
Content being pulled from capsule instead of main sat.

This is due to the fact that the content sources (As created when publishing/promoting a content view and thus getting installation media) are hard-coded to the satellite itself:

ACME_Corporation/dev/6ServerAndSatTake2 RedHat Server 6.5 x86_64

There is no way to point to capsule content as a source for kickstarts. In theory it might be possible to manually do so, but that is ugly -- not to mention if a user has a dozen capsules with a bunch of content sources, it will quickly become unwieldy.

Additional info:

Comment 2 Brad Buckingham 2014-06-13 20:14:00 UTC
Assigning to Joseph as his work to associate capsule to host and hostgroup (for pulp feature) should address this.

Comment 3 Justin Sherrill 2014-06-18 14:47:24 UTC
Connecting redmine issue from this bug

Comment 4 Bryan Kearney 2014-06-20 14:04:33 UTC
Moving to POST since upstream bug has been closed

Comment 7 Corey Welton 2014-06-27 13:44:49 UTC
Verified in Satellite-6.0.3-RHEL-6-20140626.1.  Woohoo!

Comment 8 Bryan Kearney 2014-07-02 14:06:55 UTC
This was delivered with 6.0.3, which is the Satellite 6 Beta.

Note You need to log in before you can comment on or make changes to this bug.