Dieser Inhalt ist in der von Ihnen ausgewählten Sprache nicht verfügbar.
Chapter 11. Updating the boot loader on RHCOS nodes using bootupd
To update the boot loader on RHCOS nodes using
bootupd
bootupctl update
systemd
Unlike
grubby
bootupd
You can use
bootupd
11.1. Updating the boot loader manually Link kopierenLink in die Zwischenablage kopiert!
You can manually inspect the status of the system and update the boot loader by using the
bootupctl
Inspect the system status:
# bootupctl statusExample output for
x86_64Component EFI Installed: grub2-efi-x64-1:2.04-31.el8_4.1.x86_64,shim-x64-15-8.el8_1.x86_64 Update: At latest versionExample output for
aarch64Component EFI Installed: grub2-efi-aa64-1:2.02-99.el8_4.1.aarch64,shim-aa64-15.4-2.el8_1.aarch64 Update: At latest version
OpenShift Container Platform clusters initially installed on version 4.4 and older require an explicit adoption phase.
If the system status is
, perform the adoption:Adoptable# bootupctl adopt-and-updateExample output
Updated: grub2-efi-x64-1:2.04-31.el8_4.1.x86_64,shim-x64-15-8.el8_1.x86_64If an update is available, apply the update so that the changes take effect on the next reboot:
# bootupctl updateExample output
Updated: grub2-efi-x64-1:2.04-31.el8_4.1.x86_64,shim-x64-15-8.el8_1.x86_64
11.2. Updating the bootloader automatically via a machine config Link kopierenLink in die Zwischenablage kopiert!
Another way to automatically update the boot loader with
bootupd
bootupctl update
This configuration is not enabled by default as unexpected interruptions of the update operation may lead to unbootable nodes. If you enable this configuration, make sure to avoid interrupting nodes during the boot process while the bootloader update is in progress. The boot loader update operation generally completes quickly thus the risk is low.
Create a Butane config file,
, including the contents of the99-worker-bootupctl-update.busystemd unit.bootupctl-update.serviceNoteThe Butane version you specify in the config file should match the OpenShift Container Platform version and always ends in
. For example,0. See "Creating machine configs with Butane" for information about Butane.4.12.0Example output
variant: openshift version: 4.12.0 metadata: name: 99-worker-chrony1 labels: machineconfiguration.openshift.io/role: worker2 systemd: units: - name: bootupctl-update.service enabled: true contents: | [Unit] Description=Bootupd automatic update [Service] ExecStart=/usr/bin/bootupctl update RemainAfterExit=yes [Install] WantedBy=multi-user.targetUse Butane to generate a
object file,MachineConfig, containing the configuration to be delivered to the nodes:99-worker-bootupctl-update.yaml$ butane 99-worker-bootupctl-update.bu -o 99-worker-bootupctl-update.yamlApply the configurations in one of two ways:
-
If the cluster is not running yet, after you generate manifest files, add the object file to the
MachineConfigdirectory, and then continue to create the cluster.<installation_directory>/openshift If the cluster is already running, apply the file:
$ oc apply -f ./99-worker-bootupctl-update.yaml
-
If the cluster is not running yet, after you generate manifest files, add the