Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1190656 - Rebase Foreman Discovery to 2.0
Rebase Foreman Discovery to 2.0
Status: CLOSED ERRATA
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Packaging (Show other bugs)
6.1.0
Unspecified Unspecified
unspecified Severity high (vote)
: Unspecified
: Unused
Assigned To: Jason Montleon
Sachin Ghai
:
Depends On:
Blocks: 1193977
  Show dependency treegraph
 
Reported: 2015-02-09 06:03 EST by Lukas Zapletal
Modified: 2017-02-23 15:34 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-08-12 01:24:03 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:1592 normal SHIPPED_LIVE Important: Red Hat Satellite 6.1.1 on RHEL 6 2015-08-12 05:04:35 EDT

  None (edit)
Description Lukas Zapletal 2015-02-09 06:03:23 EST
Hello,

we are releasing Foreman Discovery plugin 2.0 today. Please rebase Satellite 6.1 package to 2.0-stable branch. Thank you.
Comment 3 Sachin Ghai 2015-03-09 02:04:53 EDT
Not sure what QE needs to verify here, But I think sat6.1 beta compose ( snap5 compose1), is on discovery 2.0. I've installed the packages and performed the discovery via proxy and it works.

rpm installed:

foreman-discovery-image-2.1.0-9.el7sat.noarch
rubygem-hammer_cli_foreman_discovery-0.0.1.2-1.el7sat.noarch
ruby193-rubygem-foreman_discovery-2.0.0.5-1.el7sat.noarch
rubygem-smart_proxy_discovery-1.0.2.1-1.el7sat.noarch

verified with build: Satellite-6.1.0-RHEL-7-20150303.0
Comment 4 Bryan Kearney 2015-08-11 09:30:06 EDT
This bug is slated to be released with Satellite 6.1.
Comment 5 errata-xmlrpc 2015-08-12 01:24:03 EDT
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

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