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 1194441 - Packages to add for both RHEL6 and RHEL7
Summary: Packages to add for both RHEL6 and RHEL7
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: releng
Version: 6.0.8
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Mathieu Bridon
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-02-19 19:54 UTC by Bryan Kearney
Modified: 2017-02-23 20:28 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-05-11 20:38:06 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:1592 0 normal SHIPPED_LIVE Important: Red Hat Satellite 6.1.1 on RHEL 6 2015-08-12 09:04:35 UTC

Description Bryan Kearney 2015-02-19 19:54:49 UTC 
Please add these packages to both the RHEL6 and RHEL7 variants of Satellite 6.1

Add to Server
=============
ruby193-rubygem-gridster-rails
ruby193-rubygem-rack-jsonp
puppetlabs-stdlib
qpid-dispatch
ruby193-rubygem-jquery_pwstrength_bootstrap
puppet-foreman_scap_client
rubygem-foreman_scap_client
rubygem-hammer_cli_foreman_discovery

Add to Capsule
===============
rubygem-smart_proxy_discovery
qpid-dispatch

Add to RHCommon
===============
rubygem-foreman_scap_client
rubygem-hammer_cli_foreman_discovery
Comment 2 Bryan Kearney 2015-02-20 15:01:11 UTC 
Moving back to ASSIGNED. I missed one package

qpid-tests

and one package was not added:

qpid-dipatch

this would need to be added to both RHEL6 and RHEL7. Both Packages should go to both the server and the capsule.
Comment 4 jaudet 2015-03-10 13:02:54 UTC 
Tested against systems running Satellite-6.1.0-RHEL-6-20150303.0 and Satellite-6.1.0-RHEL-7-20150303.0. Identical output was received on both systems:

    $ packages=(ruby193-rubygem-gridster-rails ruby193-rubygem-rack-jsonp puppetlabs-stdlib qpid-dispatch ruby193-rubygem-jquery_pwstrength_bootstrap puppet-foreman_scap_client rubygem-foreman_scap_client rubygem-hammer_cli_foreman_discovery)
    $ for package in ${packages[@]}; do echo -n $(rpm -qa | grep "^${package}" | wc -l) && echo "  ${package}"; done0  ruby193-rubygem-gridster-rails
    0  ruby193-rubygem-rack-jsonp
    0  puppetlabs-stdlib
    1  qpid-dispatch
    0  ruby193-rubygem-jquery_pwstrength_bootstrap
    0  puppet-foreman_scap_client
    0  rubygem-foreman_scap_client
    1  rubygem-hammer_cli_foreman_discovery
    $ yum search rubygem-gridster
    Loaded plugins: product-id, security
    Warning: No matches found for: rubygem-gridster
    No Matches found
Comment 5 Bryan Kearney 2015-05-11 20:38:06 UTC 
I am closing this bug out. This was a tracker bug, and can be verified based on successful installs and upgrades. This bug is not needed.
Note You need to log in before you can comment on or make changes to this bug.