Bug 1419952

Summary:	RFE: a way to disable repo in Kickstart
Product:	Red Hat Enterprise Linux 7	Reporter:	Jaroslav Škarvada <jskarvad>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED WONTFIX	QA Contact:	Release Test Team <release-test-team-automation>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.4	Keywords:	FutureFeature
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-01-15 07:31:29 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 Jaroslav Škarvada 2017-02-07 13:43:35 UTC

Description of problem:
It seems there is no way how to disable repository defined in Kickstart. E.g. in Beaker jobs the Kickstart is generated and we are using ks_append. But if there is repository added by 'repo', it seems there is no way how to override/disable it in ks_append.

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

How reproducible:
Always

Steps to Reproduce:
1. Add e.g. repo --name=beaker-Server-NFV --cost=100 --baseurl=URL

Actual results:
No way how to disable the repo through ks_append

Expected results:
A way how to disable the repo, e.g. something like:
repo --name=beaker-Server-NFV --disable
would be useful

Additional info:
It would help with temporal workarounds in Beaker jobs.

Comment 3 RHEL Program Management 2021-01-15 07:31:29 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.