8f5ca795b4
- The coreos-gpt-setup.service triggers sgdisk on firstboot to regenerate the GPT disk GUID. This causes a transient partition table re-read that momentarily removes the /dev/disk/by-label/boot symlink. ignition-ostree-uuid-boot.service (tune2fs) does the same. - Because coreos-rescue-misplaced-network.service depends on ConditionPathExists=/dev/disk/by-label/boot, it can accidentally be skipped if the condition evaluates exactly while the symlink is missing. - Fix this by explicitly ordering the rescue service Before=coreos-gpt-setup.service, so the condition is evaluated while the symlink is still stable. Since coreos-gpt-setup already orders before ignition-ostree-uuid-boot, so it covers both. - Also add Before=coreos-boot-edit.service to guarantee the network config is copied before boot-edit removes /boot/coreos-firstboot-network. Fixes: OCPBUGS-132171 Signed-off-by: Renata Ravanelli <rravanel@redhat.com> |
||
|---|---|---|
| .. | ||
| 05core | ||
| 08nouveau/etc/modprobe.d | ||
| 09misc/etc/sysconfig | ||
| 10aarch64/usr/lib/dracut/dracut.conf.d | ||
| 10disk-images/usr/lib | ||
| 11legacy-copy-network/usr | ||
| 15fcos | ||
| 16fcos-sshd-workaround/usr/lib/systemd/system-generators | ||
| 17fcos-container-signing | ||
| 20platform-chrony/usr | ||
| 30lvmdevices | ||
| 35container-signing-migration/usr | ||
| 40import-virtiofs-systemd-credentials/usr/lib/dracut/modules.d/40import-virtiofs-systemd-credentials | ||
| README.md | ||
These overlay directories are automatically committed to the build OSTree repo
by coreos-assembler. They are then explicitly included in our various manifest
files via ostree-layers (this used to be done automatically, but that's no
longer the case).
05core
This overlay matches fedora-coreos-base.yaml; core Ignition+ostree bits.
This overlay is shared with RHCOS/SCOS 9.
08nouveau
Blacklist the nouveau driver because it causes issues with some NVidia GPUs in EC2, and we don't have a use case for FCOS with nouveau.
"Cannot boot an p3.2xlarge instance with RHCOS (g3.4xlarge is working)" https://bugzilla.redhat.com/show_bug.cgi?id=1700056
09misc
Warning about /etc/sysconfig.
10disk-images
Configuration files for bootc and image-builder. These are used when building our disk images.
15fcos
Things that are more closely "Fedora CoreOS":
- disable password logins by default over SSH
- enable SSH keys written by Ignition and Afterburn
- branding (MOTD)
- enable FCOS-specific services by default
- display warnings on the console if no ignition config was provided or no ssh key found.
- display warnings if mount points are not set up properly
17fcos-container-signing
Configuration for container signature verification for our fedora-coreos containers pulled from quay.io. Initially adding here in a separate overlay to make it easy to include on specific streams for the time being. Eventually can probably put this in 15fcos.
20platform-chrony
Add static chrony configuration for NTP servers provided on platforms
such as azure, aws, gcp. The chrony config for these NTP servers
should override other chrony configuration (e.g. DHCP-provided)
configuration.
30lvmdevices
Populate an lvmdevices(8) file to limit LVM from autoactivating all devices it sees in a system. By default systems will get a "blank" configuration file with a comment in it explaining what it is used for. There is also a one-time "populate" service that will run and add any devices it sees into the devices file. This will serve to import existing devices on upgrading systems or new systems with pre-existing LVM devices attached. See the tracker issue [1] for more information.
[1] https://github.com/coreos/fedora-coreos-tracker/issues/1517
35container-signing-migration
This overlay will be used to perform a migration such that upgrading systems will start using container signatures for verification as opposed to OSTree commit signatures.
This is a necessary step for F43 as part of the build-via-container change [1]. See [2].
[1] https://github.com/coreos/fedora-coreos-tracker/issues/1969 [2] https://github.com/coreos/fedora-coreos-tracker/issues/2029
40import-virtiofs-systemd-credentials
Support exposing systemd-credentials via virtiofs. This is a cross-architecture alternative way to get settings into an instance when Ignition isn't an option (i.e. non-coreos bootable container) or when we want to explicity test behavior when no Ignition is provided to an instance.