Chapter 4 Known Issues

Table of Contents

This chapter describes known issues in the Oracle Linux 8.2 release on the x86_64 platform, unless otherwise noted. For issues that apply specifically the Arm (aarch64) platform, see Section 6.5, “Known Issues (aarch64)”.

4.1 Installation and Upgrade Issues

The following are known installation and upgrade issues for Oracle Linux 8.2.

4.1.1 Interactive text-based installation wizard unable to complete when an alternate language is selected

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)

4.1.2 Changing installation source results in errors if alternative installation repository is set at boot

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)

4.1.3 Graphical installer fails to produce error when unacceptable Kdump value is entered

There is a minor upstream usability error that applies to the graphical installer when configuring Kdump settings. In the situation where you attempt to configure a manual kdump memory reservation, and you then set the memory reservation value to an unacceptable value, the installer allows you to click Done and return to the Installation Summary screen without producing a warning or error message.

When you select an unacceptable value, the installer resets the value to the last-known acceptable value that was entered; or, the installer sets the default minimum value of 512 MB. Note that this information is not displayed in the Installation Summary screen. Because an incorrect value cannot be stored for this parameter, the installation succeeds even when incorrect information is entered.

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

(Bug IDs 31133351, 31182708)

4.1.4 Graphical installer does not display the reserved memory that is manually set for Kdump

A minor usability error applies to the graphical installer when configuring Kdump settings. 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.

Note

The default settings for Kdump memory reservation of auto is adequate as the kernel will determine what size to use when it boots

(Bug IDs 31133287 and 31182699)

4.1.5 rhnreg_ks register command may fail if python3-rhn-virtualization-host package is installed

Attempting to register with the Unbreakable Linux Network (ULN) in Oracle Linux 8.2 by running the rhnreg_ks command may 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 registering with ULN by using the rhnreg_ks command.

(Bug ID 30366521)

4.1.6 Missing beignet package causes dependency issue during upgrade

When upgrading from Oracle Linux 8.1 to Oracle Linux 8.2, a dependency issue is encountered if the beignet package is installed, as this package requires an earlier version of the clang-libs package.

Currently, a newer version of the beignet package is not available in Oracle Linux 8.2.

To work around the issue, remove the beignet package from the Oracle Linux 8.1 system to be installed prior to upgrading to Oracle Linux 8.2.

(Bug ID 31213935)

4.1.7 ULN registration wizard not displayed on first boot after an Oracle Linux 8 installation

On new installations of Oracle Linux 8, the ULN registration wizard that presents the option to register with ULN and use Oracle Ksplice is not displayed on first boot. This behavior differs from previous Oracle Linux releases, where you were presented with these options on the first boot after completing the installation.

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

(Bug ID 29933974)

4.1.8 Syslog Error: Failed to insert module 'ip_tables': Operation not permitted

During an Oracle Linux 8.2 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 loads successfully, as shown in the output of the following command:

# grep IPTABLES /boot/config*
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP6_NF_IPTABLES=m
#
# modinfo ip_tables
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)

4.1.9 Graphics controller requirements for an installation on an Oracle VM VirtualBox guest

To successfully install Oracle Linux 8.2 on an Oracle VM VirtualBox guest, where the graphical installer is used and the default install of the Server with GUI environment is set, requires that the Oracle VM VirtualBox guest use the VMSVGA graphics controller and that it is configured with at least 64MB of memory.

Warning

Failure to set the graphics controller correctly can result in an installation where the graphical display is unable to start correctly.

The VMSVGA graphics controller is the default controller when you create a new guest by using Oracle VM VirtualBox 6.0, or later, for Linux guest operating systems. This issue is more likely to appear if you attempt to install over an existing guest that was created on an earlier Oracle VM VirtualBox release. Oracle recommends that you only attempt to install Oracle Linux 8 on a newly created virtual machine (VM) in Oracle VM VirtualBox 6.0, or later.

(Bug ID 30004543)

4.1.10 Installation on a KVM guest by using iPXE and iSCSI boot results in incorrect IQN name

After installing Oracle Linux 8.2 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)

4.2 Running yum update glusterfs-* fails to upgrade previously installed packages to Oracle Linux 8.2

The glusterfs-*.i686 packages are not included in either the Oracle Linux 8.1 or Oracle Linux 8.2 release. However, if you installed the glusterfs-*.i686 and glusterfs-*.x86_64 packages on the system to be upgraded in an earlier release, running the yum update glusterfs* command fails to upgrade the packages to Oracle Linux 8.2.

The workaround for this issue is to first remove the glusterfs-*.i686 packages from the system to be upgraded, and then run the yum update glusterfs* command.

(Bug ID 30279840)

4.3 Cockpit web console Services page unable to search services by state

The Services page for the Cockpit web console has been updated to enable you to search services by name, description, and state. This new functionality works as expected for filtering services by Name and Description; however, if you attempt to filter services by State, an error indicating there are no matching results is produced.

(Bug ID 30286168)

4.4 Oracle Linux 8 does not recognize SAS controllers on older Oracle Sun hardware

The Oracle Linux 8.2 installer does not recognize some Serial Attached SCSI (SAS) controllers that are found on older Oracle Sun server models. If you attempt to install Oracle Linux 8 on these server models, the installer does not recognize the local disk and the installation fails. Some examples of these older server models include, but are not limited to, the following: Oracle Sun Fire X4170 M2 Server, Oracle Sun Fire X4170 M3 Server, Oracle Sun OVCA X3-2 Server, and the Oracle Sun X4-2 Server.

The following SAS controllers are removed from the mpt2sas driver in RHCK:

  • SAS2004, PCI ID 0x1000:0x0070

  • SAS2008, PCI ID 0x1000:0x0072

  • SAS2108_1, PCI ID 0x1000:0x0074

  • SAS2108_2, PCI ID 0x1000:0x0076

  • SAS2108_3, PCI ID 0x1000:0x0077

  • SAS2116_1, PCI ID 0x1000:0x0064

  • SAS2116_2, PCI ID 0x1000:0x0065

  • SSS6200, PCI ID 0x1000:0x007E

The following SAS controllers are removed from the megaraid_sas driver in RHCK:

  • Dell PERC5, PCI ID 0x1028:0x15

  • SAS1078R, PCI ID 0x1000:0x60

  • SAS1078DE, PCI ID 0x1000:0x7C

  • SAS1064R, PCI ID 0x1000:0x411

  • VERDE_ZCR, PCI ID 0x1000:0x413

  • SAS1078GEN2, PCI ID 0x1000:0x78

  • SAS0079GEN2, PCI ID 0x1000:0x79

  • SAS0073SKINNY, PCI ID 0x1000:0x73

  • SAS0071SKINNY, PCI ID 0x1000:0x71

(Bug ID 29120478)

4.5 File System Issues

The following are known file systems issues in Oracle Linux 8.2.

4.5.1 Btrfs and OCFS2 file systems not supported on RHCK

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

Note that support for the Btrfs and OCFS2 file systems is enabled in UEK R6. For more information about enhancements that have been made to Btrfs and OCFS2 in UEK R6, see Unbreakable Enterprise Kernel: Release Notes for Unbreakable Enterprise Kernel Release 6.

4.5.2 ext4: Frequent or repeated system shutdowns can cause file system corruption

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

(Bug ID 27547113)

4.6 Kernel Issues

The following are known kernel issues in Oracle Linux 8.2.

4.6.1 KVM guests boot with "amd64_edac_mod: Unknown symbol" errors on AMD 64-bit platforms

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

[   12.474069] amd64_edac_mod: Unknown symbol amd_register_ecc_decoder (err
0)
[   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.

Note

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

(Bug ID 29853602)

4.6.2 Output of modinfo command does not show Retpoline support

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

# 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.

(Bug ID 29894295)

4.6.3 Kdump might fail on some AMD hardware

Kdump might fail on some AMD hardware that is running Oracle Linux 8.2 with the default RHCK kernel. Impacted hardware includes the AMD EPYC CPU (codename Naples and Rome) servers.

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

Note that this issue does not occur on this particular hardware if you are running UEK R6 with Oracle Linux 8.2.

(Bug ID 31274238)

4.6.4 Kdump runs out of memory when attempting to mount /sysroot on FC disks that use the Logical Volume Manager

An issue in Oracle Linux 8.2 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)

4.6.5 Limitations of the LVM dm-writecache caching method

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 the Section 3.6, “File Systems and Storage” features section of these release notes. See also the lvmcache(7) manual page.

4.7 Networking Issues

The following are networking issues in Oracle Linux 8.2.

4.7.1 tracepath6 does not parse destination IPv6 address correctly

When running the tracepath6 command in Oracle Linux 8.2, the command fails to correctly parse the destination IPv6 address. As a result, the tool traces a route to the wrong host.

The workaround for this issue is to use another tool with similar capability to tracepath6.

(Bug ID 29540588)

4.7.2 Failure to insert ip_tables module

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)

4.8 Running nohup prevents ssh command from executing

If you run the nohup command as shown in the following example on an Oracle Linux 8.2 system, and then attempt to remotely connect to that system by using the ssh command, the ssh command hangs:

# /usr/bin/nohup ./myscript > nohup.out &

The workaround for this issue is to modify the nohup command as follows:

# /usr/bin/nohup ./myscript > nohup.out 2>&1 &

(Bug ID 30287091)

4.9 Restarting firewalld service results in SSH connection timeout

Restarting the firewalld service leads to an SSH connection timeout on the terminal from which the service was started. Note that other SSH terminals remain connected.

(Bug ID 29478124)

4.10 Error: "mcelog service does not support this processor"

An error indicating that the mcelog service does not support the processor can appear in the system log on systems with AMD processors, such as some Oracle Server hardware. The message might be displayed as follows:

mcelog: ERROR: AMD Processor family
23: mcelog does not support this processor.  Please use the edac_mce_amd
module instead.

The mcelog daemon is a service that is used on x86_64 platforms to log and handle hardware error messaging, but it is not required on AMD systems where the edac_mce_amd kernel module handles machine exception logging. The error should be downgraded to a warning. (Bug ID 29501190)

4.11 Podman Issues

For information about known issues with the Podman container management tool in Oracle Linux 8.2, refer to Known Issues chapter of the Oracle® Linux: Podman User's Guide.

4.12 TLS 1.3 Not Supported for NSS in FIPS Mode

TLS 1.3 is enabled by default in Oracle Linux 8.2. Applications that are built with NSS do not support connections that require TLS 1.3 in FIPS mode. To make such connections work, disable FIPS mode or use TLS 1.2.