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.

Bug 1198070

Summary: [RFE] Include foreman_default_hostgroup with Satellite
Product: Red Hat Satellite Reporter: Peter Vreman <peter.vreman>
Component: InstallationAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Katello QA List <katello-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.0.8CC: bbuckingham, bkearney, kshirsal, stbenjam
Target Milestone: UnspecifiedKeywords: FutureFeature
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-02 19:24:35 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: 1122832    

Description Peter Vreman 2015-03-03 10:56:13 UTC
Description of problem:
Enabling the foreman-plugin-default-hostgroup option in the installer:

katello-installer --verbose \
  "--enable-foreman-plugin-hooks" --enable-foreman-plugin-default-hostgroup --enable-foreman-plugin-discovery \

results in a fail installation:

[ INFO 2015-03-03 10:33:54 verbose] /usr/bin/puppet:8
[ERROR 2015-03-03 10:33:54 verbose]  /Stage[main]/Foreman::Plugin::Default_hostgroup/Foreman::Plugin[default_hostgroup]/Package[ruby193-rubygem-foreman_default_hostgroup]/ensure: change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0 -y list ruby193-rubygem-foreman_default_hostgroup' returned 1: Error: No matching Packages to list
[ INFO 2015-03-03 10:33:54 verbose]  Class[Foreman::Service]: Scheduling refresh of Exec[restart_foreman]
[ INFO 2015-03-03 10:33:54 verbose]  Class[Foreman::Service]: Scheduling refresh of Service[foreman]


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Run the katello-installer -=enable-foreman-plugin-default-hostgroup
2.
3.

Actual results:
Installation fails

Expected results:
Installation succeeds and installs the foreman plugin default_hostgroup

Additional info:
See also BZ1198065

Comment 1 Peter Vreman 2015-03-03 13:01:19 UTC
Having the default-hostgroup plugin and the dynamic hostgroup name support (requested in BZ1198065) solves also the request BZ1127164 (Foreman #6952)

Comment 2 RHEL Program Management 2015-03-03 20:19: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.

Comment 5 Bryan Kearney 2016-12-02 19:24:35 UTC

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