Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FAQ: Where'd my /etc/yum.repos.d go? #438

Merged
merged 1 commit into from
Nov 12, 2020
Merged

FAQ: Where'd my /etc/yum.repos.d go? #438

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions docs/faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -139,6 +139,25 @@ is in place, as the cluster currently has [no mechanism for reporting](https://g
fashion. This kind of package replacement can also leave your nodes exposed to potential problems
that are fixed in newer versions of the package.

## Q: Why are there no yum (rpm-md) repositories in /etc/yum.repos.d?

First, a core part of the design is that the OS upgrades are controlled
by and integrated with the cluster. See [OSUpgrades.md](https://github.com/openshift/machine-config-operator/blob/master/docs/OSUpgrades.md).

A key part of the idea here with OpenShift 4 is that everything around
our continuous integration and delivery pipeline revolves around the release image.
The state of the installed system can be derived by that checksum; there
aren't other external inputs that need to be mirrored or managed.

Further, you only need a regular container pull secret to be able to
download and mirror OpenShift 4, including the operating system updates.
There is no `subscription-manager` step required.

Conceptually, RPMs are an implementation detail.

For these reasons, RHCOS does not include any rpm-md (yum) repository
configuration in `/etc/yum.repos.d`.

## Q: How do I build my own version of RHCOS for testing?

You need the RHCOS manifest configuration (currently hosted on an RHT internal [GitLab repo](https://url.corp.redhat.com/rhcos-repo)) and
Expand Down