Bug 1664750
| Summary: | [RFE] Possibility to not include or/and disable repo by id (name) in kickstart | ||
|---|---|---|---|
| Product: | [Retired] Beaker | Reporter: | Martin Styk <mastyk> |
| Component: | general | Assignee: | Martin Styk <mastyk> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | tools-bugs <tools-bugs> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 26 | CC: | bnater, bpeck, breilly, cbeer, rjoost |
| Target Milestone: | 26.3 | Keywords: | Patch |
| 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: | 2019-01-11 09:40:15 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1665019 | ||
|
Description
Martin Styk
2019-01-09 15:15:24 UTC
While I am sure you have thought of this already, I just want to add a brief comment here to make sure that the solution allow multiple repos IDs (names) to be selected for removal/disabling. Yes, it will be working in the same ways as no_<type>_repos worked. So, if you want to remove/disable multiple IDs (names) you have to list them one by one. support will be added for following options in ks meta: no_repo_<repo_id> - repo_id(name) is not part of kickstart not yum.repos.d (equivalent for no_<type>_repos) disable_<type>_repos - All repos of given type are not part of kickstart, however, they are created in yum.repos.d, but enabled flag is set to 0. disable_repo_<repo_id> - Same as disable_<type>_repos but for individual repo defined by repo_id. The patch has been merged. I will test it tomorrow in devel environment. Beaker 26.3 has been released. *** Bug 1574803 has been marked as a duplicate of this bug. *** |