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.

Jason,

for Discovery 2.0 we have introduced new *Capusule* only foreman-proxy plugin. We need to get it in.

https://github.com/theforeman/smart_proxy_discovery

Thanks.

Or ASSIGNED is better.

FYI the SPEC is in the foreman-packaging repo.

Please disregard the comment 5. Wrong BZ.

Yeah.. following packages are available in sat6.1 beta composes for discovery_proxy_plugin:

rubygem-smart_proxy_discovery-1.0.2.1-1.el7sat.noarch
rubygem-smart_proxy_discovery-1.0.2.1-1.el6_6sat.noarch


And discovery via proxy works with sat61 beta on both rhel7 and rhel66. 

Verified wit build:

sat6.1 beta snap4 compose2
Satellite-6.1.0-RHEL-7-20150225.0
Satellite-6.1.0-RHEL-6-20150225.0

This bug is slated to be released with Satellite 6.1.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2015:1592