Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
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 1RHEL 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.
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.