If an alternate language is selected during an interactive installation by using the text-based installer, you cannot progress through all of the steps in the installation wizard. The installation is blocked with [!] bullets for Software Selection and Installation Destination, irrespective of what is selected for these two options.

Note that this issue does not occur when performing an installation by using the default language selection of English or if you are using the graphical installer.

(Bug ID 30535416)

If the installer is booted with the inst.repo option set, changing the installation source to use a CD or DVD device within the installer results in an error that prevents you from continuing the installation, unless you set the source back to the original source that was set at boot.

If you set the inst.repo option to point to a hard disk and then attempt to change the installation source inside the installer, the installer displays an error; but, you can still proceed with the installation.

To avoid these issues, do not set the inst.repo option at boot if you do not intend to use the installation source that is provided. Or, use the inst.repo source that is defined at boot without attempting to change installation source inside the installer.

(Bug ID 30316179)

A minor upstream usability error affects the graphical installation program during the configuration of Kdump.

If you specify an unacceptable value when manually configuring the Kdump memory reservation, you can click Done to return to the Installation Summary screen. The installer does not generate a warning or error message. Instead, the installer automatically resets the value either to the last known acceptable value or the default value of 512 MB, which enables the installation to succeed. However, because this corrected setting is not displayed on the screen, you might not become aware that your specified value was ignored.

This issue does not occur with the text-based installer, which correctly returns an error if you enter an unacceptable value and prevents you from continuing.

(Bug IDs 31133351, 31182708)

A minor usability error affects the graphical installation program during the configuration of Kdump. If you manually change the default memory size that is reserved for Kdump, the new setting is not displayed when the screen is refreshed. Instead, only the values for the total system memory and usable system memory are displayed. Consequently, the limits for the parameter "Memory to be reserved (Mb)" become unknown for future Kdump configuration.

(Bug IDs 31133287 and 31182699)

Beginning with Oracle Linux 8.1, using the rhnreg_ks command to register a system with the Unbreakable Linux Network (ULN)might fail if the python3-rhn-virtualization-hosts package is installed on the system. This issue has been observed when the libvirtd service is not running.

To work around this issue, ensure that the libvirtd packages are installed on your system and that the service is enabled and running prior to issuing the rhnreg_ks command.

(Bug ID 30366521)

While upgrading a system to the current Oracle Linux 8 release, you might encounter a dependency issue if the beignet package exists on the system to be upgraded.

This issue exists specifically in cases where you upgrade systems running Oracle Linux 8.2 or earlier releases to the current Oracle Linux version. In these earlier releases, the beginet package requires earlier versions of the clang-libs package.

However, the beignet package is currently not available for Oracle Linux 8.4 and later Oracle Linux 8 releases. Therefore, the issue does not exist for these cases.

To work around this issue, remove the beignet package from the system prior to upgrading to the current Oracle Linux 8 release.

(Bug ID 31213935)

On new installations of Oracle Linux 8, the ULN registration wizard that presents the options to register with ULN and to use Oracle Ksplice is not displayed on first boot.

As an alternative, you can register with ULN after the installation completes. For instructions, see https://linux.oracle.com/.

(Bug ID 29933974)

During an Oracle Linux 8 installation, the following message can be observed in the /var/log/messages:systemd log:

1]: Failed to insert module 'ip_tables': Operation not permitted

This error can be safely ignored, as the ip_tables kernel module subsequently and can be verified by running the following command:

grep IPTABLES /boot/config*

The following output indicates the module loaded successfully:

CONFIG_IP_NF_IPTABLES=m
CONFIG_IP6_NF_IPTABLES=m

You can also check that the module loaded successfully by running the following command:

modinfo ip_tables

The output of the previous command indicates the module loaded successfully:

filename:      
/lib/modules/4.18.0-32.el8.x86_64/kernel/net/ipv4/netfilter/ip_tables.ko.xz
alias:          ipt_icmp
description:    IPv4 packet filter
author:         Netfilter Core Team <coreteam@netfilter.org>
license:        GPL
rhelversion:    8.0
srcversion:     3967C875058C2EE2475C9C2
depends:        
retpoline:      Y
intree:         Y
name:           ip_tables
vermagic:       4.18.0-32.el8.x86_64 SMP mod_unload modversions
sig_id:         PKCS#7
signer:        
sig_key:        
sig_hashalgo:   md4
signature:      30:82:02:59:06:09:2A:86:48:86:F7:0D:01:07:02:A0:82:02:4A:30:
82:02:46:02:01:01:31:0D:30:0B:06:09:60:86:48:01:65:03:04:02:
01:30:0B:06:09:2A:86:48:86:F7:0D:01:07:01:31:82:02:23:30:82:
02:1F:02:01:01:30:7A:30:62:31:22:30:20:06:03:55:04:0A:0C:19:
4F:72:61:63:6C:65:20:41:6D:65:72:69:63:61:2C:20:49:6E:63:2E:
2C:63:3D:55:53:31:19:30:17:06:03:55:04:03:0C:10:4F:72:61:63:
.
.
.

(Bug ID 29500599)

To successfully install Oracle Linux 8 on an Oracle VM VirtualBox guest, where the graphical installation program is used and the default Server with GUI environment is selected, you must set the guest to use the VMSVGA graphics controller and configure the guest with at least 64MB of memory. Otherwise, the graphical display is unable to start correctly.

Beginning with Oracle VM VirtualBox 6.0, the VMSVGA graphics controller is the default controller for guests running Linux operating systems. This issue is more likely to appear if install Oracle Linux 8 on an existing guest that was created on an earlier Oracle VM VirtualBox release. To configure Oracle Linux 8 guests, Oracle recommends that you use Oracle VM VirtualBox 6.0 or later.

(Bug ID 30004543)

After installing Oracle Linux 8 on a KVM guest by using iPXE and iSCSI boot, the SCSI Qualified Name (IQN) in the /etc/iscsi/initiatorname.iscsi file is not correct.

Note that this incorrect configuration could impact kdump functionality.

The workaround for this issue is to manually modify the /etc/iscsi/initiatorname.iscsi file with the correct IQN after the installation completes.

(Bug ID 29536715)

Attempts to boot the Oracle Linux 8 (aarch64) installer by using the ISO might fail. If USB Attached SCSI devices are present, the boot process may drop to a shell prompt. Examples of such devices include a virtual hard disk drive (HDD), a virtual CD-ROM, and a memory stick.

You also might encounter an issue during an installation of Oracle Linux 8 (aarch64), where USB ports are not recognized by the system right after the kernel takes control of the system, as well as by the installed system. When this problem occurs, any USB devices that are plugged into the system, such as keyboards and so on, do not work. In addition, booting images from certain USB-connected drives, such as virtual devices that are handled by a service processor, for example, MegaRAC SP firmware, does not work.

A workaround is to install an earlier Oracle Linux 8 (aarch64) release by using the ISO image, and then use the dnf update command to update to the current Oracle Linux 8 (aarch64) release.

Also, this issue does not affect a PXE boot, so as an alternative solution, you can perform a network-based installation of Oracle Linux 8 (aarch64). See Oracle Linux 8: Installing Oracle Linux for instructions on performing an installation from the network.

(Bug IDs 31626109, 31678684)

For both GUI-based and text-based installations of Oracle Linux 8 on the Arm platform, the following error is produced at the start of the installation:

** (anaconda:2843): CRITICAL **: 09:49:18.542: The function
'bd_btrfs_list_subvolumes' called, but not implemented!

This error prevents you from proceeding with the installation.

To work around this issue, before the installation, remove or format all of the Btrfs partitions from all of the disks on the host where you are planning to install Oracle Linux 8.

(Bug ID 31160993)

The Btrfs file system is removed from RHCK in Oracle Linux 8, which means you cannot create or mount this file system when using this kernel. Also, any Btrfs user space packages that are provided are not supported with RHCK.

Support for the Btrfs file system is enabled in UEK R7 and UEK R6. Starting with Oracle Linux 8.3, during an installation, you have the option to create a Btrfs root file system, as well as select Btrfs as the file system type when formatting devices.

For further details about these changes, see the following documentation:

• For information about creating a Btrfs root file system during an installation, see Oracle Linux 8: Installing Oracle Linux.

• For information about managing the Btrfs file system, see Oracle Linux 8: Managing Local File Systems.

• For the latest information about other enhancements that have been made to Btrfs in UEK R6, see Unbreakable Enterprise Kernel: Release Notes for Unbreakable Enterprise Kernel Release 6 Update 3 (5.4.17-2136).

  For information about UEK R7, see Unbreakable Enterprise Kernel: Release Notes for Unbreakable Enterprise Kernel Release 7 (5.15.0-0.30).

The OCFS2 file system is removed from RHCK in Oracle Linux 8, which means you cannot create or mount this file system when using this kernel. Also, OCFS2 user space packages that are provided are not supported with RHCK.

Note that support for OCFS2 file systems is enabled in UEK R7 and UEK R6. For the latest information and other enhancements that have been made to OCFS2 in UEK R6, see Unbreakable Enterprise Kernel: Release Notes for Unbreakable Enterprise Kernel Release 6 Update 3 (5.4.17-2136). See also Unbreakable Enterprise Kernel: Release Notes for Unbreakable Enterprise Kernel Release 7 (5.15.0-0.30).

If a system that is using the ext4 file system is repeatedly or frequently shut down, the file system might become corrupted. This issue is difficult to replicate and is therefore considered to be a corner-case issue. The issue exists in the upstream code and proposed patches are currently under review.

(Bug ID 27547113)

The following errors might be displayed repeatedly when KVM guests are booting on 64-bit AMD hosts:

[   12.474069] amd64_edac_mod: Unknown symbol amd_register_ecc_decoder (err [ 120)
[   12.474083] amd64_edac_mod: Unknown symbol amd_report_gart_errors (err 0)
[   12.852250] amd64_edac_mod: Unknown symbol amd_unregister_ecc_decoder (err 0)
[   12.852297] amd64_edac_mod: Unknown symbol amd_register_ecc_decoder (err 0)
.
.
.

These errors occur because the module code for the kernel erroneously returns -EEXIST for modules that failed to load and are in the process of being removed from the module list. The amd64_edac_mod module will not be loaded in a VM. These errors can be ignored, as they do not impact functionality in any way.

This issue occurs on Oracle Linux 8 hosts that are running RHCK only and is not encountered on UEK R6 hosts.

(Bug ID 29853602)

A bug in the Oracle Linux 8 code causes Retropline support to not be displayed in the output of the modinfo -F retpoline command, even though the CONFIG_RETPOLINE flag is set to Y, for example:

sudo modinfo -F retpoline
/usr/lib/modules/4.18.0-80.el8.x86_64/kernel/sound/usb/usx2y/snd-usb-us122l.ko
.xz

The CONFIG_RETPOLINE=Y flag is still required to add and display Retpoline support. If the parameter is enabled, the kernel builds with a retpoline capable compiler.

To confirm that the CONFIG_RETPOLINE flag is enabled, search for the parameter in the kernel's config-kernel configuration file, for example:

cat /boot/config-5.4.17-2011.7.4.el8uek.x86_64 | grep RETPOLINE.

CONFIG_RETPOLINE=y

(Bug ID 29894295)

Kdump might fail on some AMD hardware that is running the current Oracle Linux release. Impacted hardware includes the AMD EPYC CPU servers.

To work around this issue, modify the /etc/sysconfig/kdump configuration file and remove the iommu=off command-line option from the KDUMP_COMMANDLINE_APPEND variable. Restart the kdump service for the changes to take effect.

(Bug ID 31274238, 34034614, 34211826)

An issue in Oracle Linux 8 causes Kdump to run out of memory if you attempt to mount /sysroot on a Fibre Channel (FC) disk that uses LVM. This issue is due to a lack of memory when the crashkernel loads.

To resolve the issue, you can do one of the following:

• Override the crashkernel=auto boot option so that more memory is reserved for Kdump. For example, set the kernel boot parameter to crashkernel=512M.

• Set the Kdump destination to a network location (NFS or SSH).

(Bug ID 29840266)

The new LVM dm-writecache caching method has certain limitations that do not exist with the dm-cache method, including the following:

• Cannot attach or detach dm-writecache when a logical volume is active.

• Cannot take a snapshot of a logical volume when the logical volume is using dm-writecache.

• Must use a dm-writecache block size that matches the existing file system block size when attaching dm-writecache to an inactive logical volume.

• Cannot resize a logical volume when dm-writecache is attached to the volume.

• Cannot use pvmove commands on devices that are used with dm-writecache.

• Cannot use logical volumes with dm-writecache when using thin pools or the virtual data optimizer (VDO).

For more information about the dm-writecache caching method, see the File Systems and Storage features section of Oracle Linux 8: Release Notes for Oracle Linux 8.2. See also the lvmcache(7) manual page.

System hangs might occur during a crash kernel boot on ThunderX2 and X-Gene 3 platforms that are running Oracle Linux 8 (aarch64). This issue has been observed at different stages of the boot process. Consequently, Kdump might not work as expected on this hardware.

(Bug IDs 30339519, 30339571)

An attempt to subsequently register a cache set after removing it fails with the following error:

echo "CACHE_DEV" > /sys/fs/bcache/register
        echo: write error: Invalid argument

The following error message is displayed in the dmesg output:

bcache: register_bcache() error /dev/CACHE_DEV: Not a bcache superblock

This issue is related to 64KB page size (CONFIG_ARM64_64K_PAGES=y), which bcache currently does not support.

Because the superblock for the cache device becomes corrupted during this process, it is not possible to re-register the device.

To work around this issue, reinstall the bcache-tools package and then create a new bcache configuration.

As an alternative, avoid using a bcache configuration on Oracle Linux 8 (aarch64) systems.

(Bug ID 30210051)

Running the tracepath6 command fails to parse the destination IPv6 address correctly. Consequently, the tool traces a route to the wrong host.

To work around this issue, use a tool with similar capabilities to the tracepath6 command.

(Bug ID 29540588)

The ip_tables module fails to insert with an 'Operation not permitted' error. This issue, which is currently under investigation, can occur if SELinux is in enforcing mode.

A workaround for this issue is to set SELinux to permissive mode, which you can do temporarily by running the setenforce 0 command. Or, you can set SELinux to permissive mode permanently by editing the /etc/selinux/config file and then rebooting the system.

(Bug ID 29517166)