Bug 1332672

Summary:	ruby193-rubygem-foreman-redhat_access module not available in rhel-7-server-satellite-6.1-rpms repo
Product:	Red Hat Satellite	Reporter:	David Bensimon <dbensimo>
Component:	RH Cloud - Insights	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED DUPLICATE	QA Contact:	Katello QA List <katello-qa-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.1.8	CC:	cmuraya, dbensimo, lphiri, nobody
Target Milestone:	Unspecified
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-05-04 19:15:23 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:

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 ***