Bug 1708204
| Summary: | Do not create /etc/yum.repos.d on redhat-release installation | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Marek Blaha <mblaha> |
| Component: | redhat-release | Assignee: | Djordje Todorovic <dtodorov> |
| Status: | CLOSED WONTFIX | QA Contact: | Release Test Team <release-test-team-automation> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 8.0 | CC: | csnyder, dtodorov, pkotvan, tmlcoch |
| Target Milestone: | rc | Flags: | pm-rhel:
mirror+
|
| Target Release: | 8.1 | ||
| 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-02-01 07:40:44 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: | 1653484 | ||
|
Description
Marek Blaha
2019-05-09 11:15:19 UTC
Chris, I wonder if this change won't break subscription-manager? Chris, can you answer the question above? In subscription-manager's current form, users will still be able to register, attach / remove subscriptions and so on. However, subscription-manager does not create this directory if it does not exist resulting in no access to any content provided in the form of a repo that comes from an entitlement. As soon as this directory is created (and rhsmcertd runs, or any subman command that reconciles entitlements) the correct redhat.repo file will be generated. Could dnf be modified to handle the special case of an empty /installroot/etc/yum.repos.d/ directory? It could treat an empty /installroot/etc/yum.repos.d directory as it does with a nonexistant /installroot/etc/yum.repos.d folder, rely on the host /etc/yum.repos.d directory. 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. |