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 1332672 - ruby193-rubygem-foreman-redhat_access module not available in rhel-7-server-satellite-6.1-rpms repo
Summary: ruby193-rubygem-foreman-redhat_access module not available in rhel-7-server-s...
Keywords:
Status: CLOSED DUPLICATE of bug 1315820
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: RH Cloud - Insights
Version: 6.1.8
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-03 18:01 UTC by David Bensimon
Modified: 2016-10-14 14:22 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-04 19:15:23 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description David Bensimon 2016-05-03 18:01:01 UTC 
Description of problem:
ruby193-rubygem-foreman-redhat_access_0.2.5-1 needs to be in the capsule repository. Currently only in satellite server repo. Docs say to only capsule repo, but module is not available in the capsule repo.

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

How reproducible:
100%

Steps to Reproduce:
1. subscription-manager repos --enable=rhel-7-server-satellite-capsule-6.1-rpms
2. yum install -y ruby193-rubygem-foreman-redhat_access
3. RESULT: No package ruby193-rubygem-foreman-redhat_access available. Error: Nothing to do


Actual results:
ruby193-rubygem-foreman-redhat_access_0.2.5-1 is available in rhel-7-server-satellite-6.1-rpms

Expected results:
Expected ruby193-rubygem-foreman-redhat_access_0.2.5-1 to be in rhel-7-server-satellite-capsule-6.1-rpms as per the Installation Guide (link below)

Workaround: scp'd the rpm to the capsule server, did not want to attach to rhel-7-server-satellite-6.1-rpms in fear of potentially breaking a machine in production.

Additional info:
Documentation (Chapter 7.3, Procedure 7.1) is incorrect: https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.1/html-single/Installation_Guide/#sect-Red_Hat_Satellite-Installation_Guide-Obtaining_the_Required_Packages_for_the_Capsule_Server
Comment 1 David Bensimon 2016-05-03 18:03:06 UTC 
CORRECTION

Workaround: scp'd the module to the capsule server, did not want to attach to rhel-7-server-satellite-6.1-rpms in fear of potentially breaking a machine in production.
Comment 2 Lindani Phiri 2016-05-04 17:29:12 UTC 
The ruby193-rubygem-foreman-redhat_access package is not required on the Satellite capsule server - what is the reason its being installed there?
Comment 3 David Bensimon 2016-05-04 17:56:42 UTC 
The ruby193-rubygem-foreman-redhat_access is required because puppet produced a 400 error, the module was not available on the Capsule server. Satellite does not sync the module since it is not part of a content view.
Comment 4 Lindani Phiri 2016-05-04 19:15:23 UTC 
Hi David,


Installing the access plugin on the capsule is not ideal. It solves the puppet module issue "accidentally" because we bundle the module in the rpm, but will also install software on the capsule that should not be there.
There is work in progress to fix this the right way. Please refer to :

https://bugzilla.redhat.com/show_bug.cgi?id=1315820 (for 6.1) 
and 
https://bugzilla.redhat.com/show_bug.cgi?id=1315844 (for 6.2).


Lindani

*** This bug has been marked as a duplicate of bug 1315820 ***
Note You need to log in before you can comment on or make changes to this bug.