Bug 1199827 – RHEL-OSP-Installer should disable all repos before activating the right ones

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1199827 - RHEL-OSP-Installer should disable all repos before activating the right ones

Summary:	RHEL-OSP-Installer should disable all repos before activating the right ones

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat OpenStack
Classification:	Red Hat
Component:	rhel-osp-installer (Show other bugs)
Sub Component:
Version:	6.0 (Juno)
Hardware:	Unspecified Unspecified

Priority	medium Severity medium
Target Milestone:	z2
Target Release:	Installer
Assigned To:	Mike Burns
QA Contact:	Omri Hochman
Docs Contact:

URL:
Whiteboard:
Keywords:	ZStream

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2015-03-08 15:01 EDT by Alessandro Vozza
Modified:	2016-11-07 23:08 EST (History)
CC List:	10 users (show)

See Also:
Fixed In Version:	rhel-osp-installer-0.5.7-1.el7ost
Doc Type:	Enhancement
Doc Text:	This enhancement disable all repositories by default during the subscription management stage of the provisioning process. This is due to some invalid or incorrect repositories becoming enabled and resulting in untested package combinations. Now all the repositories are disabled in the kickstart prior to enabling the required repositories listed in the installer.
Story Points:	---
Clone Of:
Environment:
Last Closed:	2015-04-07 11:08:52 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2015:0791	normal	SHIPPED_LIVE	Important: Red Hat Enterprise Linux OpenStack Platform Installer update	2015-04-07 15:07:29 EDT

Groups: None (edit)

Description Alessandro Vozza 2015-03-08 15:01:35 EDT

Description of problem:

By default, the installer subscribes each machine and enables the repos specified during the wizard installation. However, this can leave unnecessary repos enabled on systems that may not need them

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


How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Creating patches for https://github.com/theforeman/foreman-installer-staypuft as I'm entering this BZ

Comment 5 Alessandro Vozza 2015-03-08 15:18:27 EDT

https://github.com/theforeman/foreman-installer-staypuft/pull/140

and 

https://github.com/theforeman/foreman-installer-staypuft/pull/139

I added also reference to rhel-ha-for-rhel-7-server-rpms as per BZ1196310

Comment 6 Arthur Berezin 2015-03-11 14:22:18 EDT

Can users turn this off in case that want to keep the existing repos?

Comment 7 Mike Burns 2015-03-11 14:25:13 EDT

It's not something configurable (as far as no disabling), but the user can specify additional repos if needed.  The idea here is to prevent some repos that we don't want getting enabled by default.  For most people, this should be a mostly invisible change.

Comment 9 Omri Hochman 2015-03-16 17:00:21 EDT

Verified with : rhel-osp-installer-0.5.7-1.el7ost.noarch


The 'disable repo part' could found on the redhat_register snippet after choosing to use subscription-manager during running rhel-osp-installer. : 
 
# workaround for RHEL 6.4 bug https://bugzilla.redhat.com/show_bug.cgi?id=1008016
    subscription-manager repos --list > /dev/null
    subscription-manager repos --disable=*

Comment 11 errata-xmlrpc 2015-04-07 11:08:52 EDT

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2015-0791.html

Note You need to log in before you can comment on or make changes to this bug.