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.

Document URL: 
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.6-beta/html-single/provisioning_guide/index#Provisioning_Bare_Metal_Hosts-Configuring_Red_Hat_Satellites_Discovery_Service

Section Number and Name: 

6.4. Configuring Red Hat Satellite’s Discovery Service

Describe the issue: 

# yum install foreman-discovery-image rubygem-smart_proxy_discovery will not work due to package version-lock in 6.6

Suggestions for improvement: 

# foreman-maintain packages unlock
# yum install foreman-discovery-image rubygem-smart_proxy_discovery
# foreman-maintain packages lock

Additional information: 

N/A

closing as a duplicate of 1738199

*** This bug has been marked as a duplicate of bug 1738199 ***