Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). 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 rh-issues@redhat.com 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 "https://issues.redhat.com/browse/SAT-XXXX", 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 1150905 - Clients provisioned via a capsule still need significant access to the main satellite
Summary: Clients provisioned via a capsule still need significant access to the main s...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Foreman Proxy
Version: 6.0.4
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: Unspecified
Assignee: Mike McCune
QA Contact: jaudet
URL:
Whiteboard:
Depends On: sat6-capsule-isolation
Blocks: 1122832
TreeView+ depends on / blocked
 
Reported: 2014-10-09 07:20 UTC by Ade Bradshaw
Modified: 2019-09-12 08:01 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-12 13:56:17 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Ade Bradshaw 2014-10-09 07:20:09 UTC 
Description of problem:
Unable to manage clients on a DMZ, using a capsule in the DMZ. Clients still need significant access to the main satellite server for
1) Kickstart itself
2) Candlepin RPM
3) the entire post section pulls RPMs from the Satellite, via port 443

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

How reproducible:
100%

Steps to Reproduce:
1. Install Sat and add a capsule server
2. Create a new host, setting the capsule as the Content Source, Puppet CA and Puppet Master
3. TCPdump on the satellite 

Actual results:
Once the provisioning is finished and you enter the post section of the kickstart, over 3000 https packets arrive from the host vm, on the satellite server. 

Expected results:
Very few/no packets from the capsule provisioned host should arrive at the satellite server

Additional info:
Capsule server setup with the following command 
capsule-installer --parent-fqdn          "satellite6.example.com"  
--register-in-foreman  "true"     \
 --foreman-oauth-key    "jBcvCpQJsSUb2mjCpX5UGoaXk6hoEzi5"
--foreman-oauth-secret "8sZkTWjQp29Ne6Y5Gr5WmASGXSbduwW9"  \
 --pulp-oauth-secret    "jHzb9Gr6uXqzY79rMTc58jpuFXF65VwB" --certs-tar 
"~/capsule.tar"  --puppet  "true"   \
 --puppetca "true"   --pulp "true"  --tftp  "true"  --dhcp "true" 
--dhcp-interface       "eth0"  \
 --dhcp-gateway 10.40.0.1
Comment 1 RHEL Program Management 2014-10-09 07:33:18 UTC 
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Comment 3 Mike McCune 2015-01-26 22:08:34 UTC 
This is being included as a top level feature in Satellite 6.1
Comment 7 jaudet 2015-04-07 18:33:34 UTC 
Verified with the following combinations of systems:

* RHEL 7.1 Satellite, RHEL 7.1 Capsule, RHEL 7.1 Client
* RHEL 7.1 Satellite, RHEL 7.1 Capsule, RHEL 6.6 Client
* RHEL 7.1 Satellite, RHEL 6.6 Capsule, RHEL 7.1 Client
* RHEL 7.1 Satellite, RHEL 6.6 Capsule, RHEL 6.6 Client

The Satellite was running Satellite-6.1.0-RHEL-7-20150406.0. In each of the four test cases, the client followed steps like this:

    rpm -Uvh http://capsule.exaomple.com/pub/katello-ca-consumer-latest.noarch.rpm
    subscription-manager register --org="Default_Organization" --environment="Library"
    subscription-manager list --available --all | grep -i 'subscription name\|pool id'
    subscription-manager attach --pool …
    yum install some_package
    subscription-manager remove --all
    subscription-manager unregister

The Satellite monitored for traffic while this was happening:

    ip -family inet addr
    tcpdump -i enp7s0 -w client71-capsule71.pcap

And the traffic dump was later inspected with the filter `ip.addr == client_ip_address`. No frames were listed.
Comment 9 Bryan Kearney 2015-08-11 13:20:07 UTC 
This bug is slated to be released with Satellite 6.1.
Comment 10 Bryan Kearney 2015-08-12 13:56:17 UTC 
This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015.
Note You need to log in before you can comment on or make changes to this bug.