Bug 1190665

Summary: New package for Discovery 2.0: discovery_proxy_plugin
Product: Red Hat Satellite Reporter: Lukas Zapletal <lzap>
Component: PackagingAssignee: Jason Montleon <jmontleo>
Status: CLOSED ERRATA QA Contact: Sachin Ghai <sghai>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.1.0CC: bkearney, sthirugn
Target Milestone: UnspecifiedKeywords: Rebase
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-08-12 05:24:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1181461, 1193977    

Description Lukas Zapletal 2015-02-09 11:36:53 UTC
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.

Comment 1 Lukas Zapletal 2015-02-09 11:37:44 UTC
Or ASSIGNED is better.

Comment 3 Lukas Zapletal 2015-02-09 12:25:44 UTC
FYI the SPEC is in the foreman-packaging repo.

Comment 6 Lukas Zapletal 2015-02-17 10:46:44 UTC
Please disregard the comment 5. Wrong BZ.

Comment 8 Sachin Ghai 2015-03-04 12:19:50 UTC
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

Comment 9 Bryan Kearney 2015-08-11 13:37:23 UTC
This bug is slated to be released with Satellite 6.1.

Comment 10 errata-xmlrpc 2015-08-12 05:24:07 UTC
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