Bug 1307117

Summary:	getting started guide should warn about yum repos that may be enabled outside of subscription-manager scope
Product:	OpenShift Container Platform	Reporter:	Dave Sullivan <dsulliva>
Component:	Documentation	Assignee:	Zac Dover <zdover>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Vikram Goyal <vigoyal>
Severity:	low	Docs Contact:	Vikram Goyal <vigoyal>
Priority:	low
Version:	3.1.0	CC:	aos-bugs, dsulliva, jokerman, mmccomas
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-05-16 04:00:30 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:

Description Dave Sullivan 2016-02-12 18:20:40 UTC

Document URL: 

https://access.redhat.com/documentation/en/red-hat-atomic-enterprise-platform/version-3.1/getting-started-guide/

Section Number and Name: 

Chapter 2 step 3 

subscription-manager repos --disable="*"

Describe the issue: 

In most situations this is good, however it's possible that customers have additional yum repos enabled.  And outside of /etc/yum.repos.d/redhat.repo the command above doesn't cover.  Because any additional repos outside of redhat.repo/subscription-manager scope could cause unknown conflicts we should make a note to watch.

Suggestions for improvement: 

Add an additional check after step 3

[root@aepmaster001 yum.repos.d]# yum repolist
Loaded plugins: langpacks, product-id, subscription-manager
repolist: 0

If it is not 0 then you have other yum repos outside of subscription-manager's scope and these could cause unknown conflicts, recommend that they be disabled before proceeding or recommend that the admin validate that they do not conflict with the redhat.repo provided repositories.


Additional information:

Comment 1 Dave Sullivan 2016-02-12 18:44:17 UTC

Also after step 3 after yum repolist it would probably be good to train customers to do a check with repoclosure that's actually how they would know whether any additional yum repos that they may want impact this environment

As you can see we have dep issues with only our supplied repos, which sort of also tells me we must be missing this step in QA

http://pastebin.test.redhat.com/348529

Comment 4 Vikram Goyal 2016-05-16 04:00:30 UTC

The note to remind readers about external repos can be verified here [1].

Moving this to CLOSED-->CURRENTRELEASE.

[1] https://access.redhat.com/documentation/en/red-hat-atomic-enterprise-platform/version-3.2/getting-started-guide/#aep_getting_started_procedure