Chapter 4 Known Issues

Table of Contents

This chapter describes known issues in the Oracle Linux 8.3 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.3.

4.1.1 Installer automatically enables Ethernet over USB network interface during a PXE installation

During a Preboot Execution Environment (PXE) installation of Oracle Linux 8.3, the installer automatically enables the Ethernet over USB network interface with the bootproto=dhcp and ONBOOT=yes parameters. This issue causes the NetworkManager service to fail to start.

To prevent this issue from occurring or to resolve the issue if you have already encountered it, use one of the following workarounds:

  • Prior to the installation, disable the ONBOOT parameter for the Ethernet over USB network interface in the kickstart file, as follows:

    network --bootproto=dhcp --device=enp0s20f0u8u3c2 --onboot=off --ipv6=auto
  • During the installation, on the Network & Host Name screen, do not select the Connect automatically with priority check box to connect automatically on every reboot for the Ethernet over USB network interface.

  • If you have already encountered this issue, you can resolve the issue after the installation by changing the network configuration setting for the Ethernet over USB network interface to ONBOOT=no, and then rebooting the system.

(Bug ID 31888490)

4.1.2 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 IDs 30535416, 29648703)

4.1.3 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.4 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 then 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 if 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.5 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.6 Scriptlet-related error for microcode_ctl may be encountered during an upgrade from Oracle Linux 8.2 to Oracle Linux 8.3

A scriplet-related error similar to the following may be encountered when upgrading from Oracle Linux 8.2 to Oracle Linux 8.3 by using the yum update command:

  Running scriptlet: tuned-2.13.0-6.0.2.el8.noarch                            
             1089/1089
  Running scriptlet: microcode_ctl-4:20191115-4.el8.x86_64                    
             1089/1089
realpath: weak-updates/kmod-kvdo/vdo/kvdo.ko: No such file or directory
realpath: weak-updates/kmod-kvdo/uds/uds.ko: No such file or directory
dracut: installkernel failed in module kernel-modules-extra
warning: %posttrans(microcode_ctl-4:20191115-4.el8.x86_64) scriptlet failed,
exit status 1

Error in POSTTRANS scriptlet in rpm package microcode_ctl
  Running scriptlet: libgcc-8.3.1-4.5.0.7.el8.x86_64                          
             1089/1089
  Running scriptlet: glibc-common-2.28-101.0.1.el8.x86_64                    
             1089/1089
  Running scriptlet: info-6.5-6.el8.x86_64                                    
             1089/1089

The error is encountered if you perform a Server with GUI installation and boot the server by using RHCK because this installation method installs the kernel-dependent, kmod-kvdo package/module, which is a different version in Oracle Linux 8.2 than the version that is in Oracle Linux 8.3. Note that the error does not occur when performing a Minimal Install or if you boot the server by using UEK R6.

The error can be safely ignored and is of no consequence, as the kmod-kvdo package is successfully installed during the upgrade process.

(Bug ID 31292199)

4.1.7 Version of libpcap packages in BaseOS channel does not support RDMA

The libpcap packages that are in the BaseOS channel do not support dumping RDMA sniffer information. After installing or upgrading to Oracle Linux 8.3, if you require RDMA functionality, you should run the dnf downgrade command to downgrade your libpcap version so that you can use the libpcap packages that are published to the ol8_UEKR6_RDMA repository, for example:

# dnf downgrade libpcap

(Bug ID 32049290)

4.1.8 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.3 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.9 Missing beignet package results in dependency issue during upgrade from Oracle Linux 8.2 to Oracle Linux 8.3

When upgrading from Oracle Linux 8.2 to Oracle Linux 8.3, 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.3.

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

(Bug ID 31213935)

4.1.10 ULN registration wizard not displayed on first boot after an 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.11 Graphics controller requirements for an installation on an Oracle VM VirtualBox guest

To successfully install Oracle Linux 8.3 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 VM in Oracle VM VirtualBox 6.0, or later.

(Bug ID 30004543)

4.2 Running dnf update glusterfs-* fails to upgrade previously installed packages to Oracle Linux 8.3

The glusterfs-*.i686 packages are not included in either the Oracle Linux 8.2 or Oracle Linux 8.3 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 dnf update glusterfs* command fails to upgrade the packages to Oracle Linux 8.3.

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

(Bug ID 30279840)

4.3 Updating libss package might fail if libss-devel package is installed

Installing the libss package might fail to update if the libss-devel package is installed on the system.

The workaround for this issue is to first remove the libss-devel package from the system and then install the corresponding version of this package from the Oracle Linux 8 Distro Builder developer repository. Note that because the ol8_distro_builder repository is an unsupported developer repository, it is recommended that you only enable the repository for this particular installation action, rather than enabling it globally. For example, you can run the following command:

$ sudo dnf --enablerepo=ol8_distro_builder install libss-devel

(Bug ID 32005190)

4.4 Options for configuring disk cache characteristics during VM creation unavailable in web console

Some options for configuring disk cache characteristics in the web console are currently not available when you are creating a new VM or before the installation starts. For disks that are already added to a VM or when adding a new disk to an already running system, these configuration options are available in the web console.

As an alternative solution, you can use the virt-manager command-line interface (CLI) or a similar CLI to configure disk cache characteristics for a newly added disk before the installation begins, as well for disks that already exist in the VM.

Per Oracle recommendation, you should use Oracle Linux Virtualization Manager for more complex virtualization requirements. For more information, see https://docs.oracle.com/en/virtualization/oracle-linux-virtualization-manager/.

(Bug ID 30301271)

4.5 ACPI error messages displayed on Dell EMC PowerEdge Server during boot

When booting an Intel-based Dell EMC PowerEdge Server, error messages similar to the following might be displayed if the Dell Active Power Controller (DAPC) setting is enabled in the BIOS:

kernel: ACPI Error: No handler for Region [SYSI] (0000000061df8ef3) [IPMI] (20190816/evregion-132)
kernel: ACPI Error: Region IPMI (ID=7) has no handler (20190816/exfldio-265)
kernel: ACPI Error: Aborting method \_SB.PMI0._GHL due to previous error (AE_NOT_EXIST) (20190816/psparse-531)
kernel: ACPI Error: Aborting method \_SB.PMI0._PMC due to previous error (AE_NOT_EXIST) (20190816/psparse-531)
kernel: ACPI Error: AE_NOT_EXIST, Evaluating _PMC (20190816/power_meter-743)

Note that this issue is encountered on both RHCK and UEK kernels.

The workaround for this issue is to disable the apci_power_meter kernel module as follows:

#  echo "blacklist acpi_power_meter" >> /etc/modprobe.d/hwmon.conf

After disabling the apci_power_meter kernel module, reboot the system for the change to take effect.

For environments that do not require the DAPC feature, as an alternative workaround, you can disable the DAPC BIOS setting.

(Bug ID 32105233)

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

The Oracle Linux 8.3 installer does not recognize some Serial Attached SCSI (SAS) controllers that are found in 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. Examples of these 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.7 File System Issues

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

4.7.1 Btrfs file system not supported on RHCK

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.

Note

Support for the Btrfs file system is enabled in UEK R6. Starting with Oracle Linux 8.3, during an installation, you now 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, see the following documentation:

4.7.2 OCFS2 file system not supported on RHCK

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 R6. For more information about other enhancements that have been made to OCFS2 in UEK R6, see Unbreakable Enterprise Kernel: Release Notes for Unbreakable Enterprise Kernel Release 6.

4.7.3 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 because it is difficult to replicate it. The issue exists in the upstream code and proposed patches are currently under review.

(Bug ID 27547113)

4.8 Kernel Issues

The following are known kernel issues in Oracle Linux 8.3.

4.8.1 Default kernel for KVM guest snapshots might not be interchangeable

Creating KVM guest snapshots when using one kernel and then attempting to revert the snapshot to use another kernel might fail with errors similar to the following:

[root@host ~]# virsh snapshot-create-as myGuest mySnapshot1
-- Reboot into another kernel --
[root@host ~]# virsh start myGuest
[root@host ~]# virsh snapshot-revert myGuest mySnapshot1
error: revert requires force: Target CPU feature count 20 does not match source 18

-- Even forced revert fails --
[root@host ~]# virsh snapshot-revert myGuest mySnapshot1 --force
error: operation failed: guest CPU doesn't match specification: missing features: ibpb,amd-ssbd

For example, if you create a KVM guest snapshot while running RHCK, and you then attempt to revert that guest snapshot by using UEK R6, you could encounter this issue. Note that the same issue applies irrespective of which default kernel you are running.

Note

This issue only occurs in situations where you are attempting to interchange an RHCK kernel for a UEK kernel or a UEK kernel for an RHCK kernel. The issue is not encountered if you are interchanging kernel versions from the same vendor.

To avoid encountering this issue, make sure to use guest snapshots that use the same kernel on which they were initially created.

(Bug ID 30561489)

4.8.2 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 64-bit AMD hosts:

[   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.3 hosts that are running RHCK only and is not encountered on UEK R6 hosts.

(Bug ID 29853602)

4.8.3 Output of modinfo command does not show Retpoline support

A bug in the Oracle Linux 8.3 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.

To confirm whether the CONFIG_RETPOLINE flag is enabled, search the configuration file, for example:

# cat /boot/config-5.4.17-2011.7.4.el8uek.x86_64 | grep RETPOLINE
CONFIG_RETPOLINE=y

(Bug ID 29894295)

4.8.4 Kdump might fail on some AMD hardware

Kdump might fail on some AMD hardware that is running Oracle Linux 8.3 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 and 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.3.

(Bug ID 31274238)

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

4.9 tracepath6 command does not correctly parse destination IPv6 address

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, you can use a tool with similar capabilities to the tracepath6 command.

(Bug ID 29540588)

4.10 Running nohup prevents ssh command from executing

If you run the nohup command on an Oracle Linux 8.3 system, and then attempt to remotely connect to that system by using the ssh command, the ssh command hangs, for example:

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

To work around for this issue, modify the nohup command as follows:

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

(Bug ID 30287091)

4.11 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.12 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. This error should be downgraded to a warning.

(Bug ID 29501190)

4.13 Power button defaults to ACPI Suspend mode

By default, the Oracle Linux 8 graphical user interface (GUI) console mode treats the hardware power button as the equivalent of the ACPI "Sleep" button, which puts the system into low-power sleep mode. This behavior is specific to the GNOME desktop environment.

In previous Oracle Linux releases, the hardware power button initiated a system shutdown. To ensure that Oracle Linux 8 behaves the same way, do the following:

  1. Create a file named /etc/dconf/db/local.d/01-shutdown-button-action with following content:

    # cat /etc/dconf/db/local.d/01-power
    [org/gnome/settings-daemon/plugins/power]
    power-button-action='interactive'
    #
  2. Create a file named /etc/dconf/db/local.d/locks/01-power with the following content:

    # cat /etc/dconf/db/local.d/locks/01-power
    /org/gnome/settings-daemon/plugins/power/power-button-action
    #
  3. Run the following command:

    # dconf update
  4. Log out of the desktop environment and then log back in for the new settings to take effect.

(Bug ID 25597898)

4.14 Podman Issues

For more information about the Podman container management tool, including any known issues, see the Oracle® Linux: Podman User's Guide.

4.15 TLS 1.3 not supported for NSS in FIPS Mode

TLS 1.3 is enabled by default in Oracle Linux 8.3. 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.

4.16 SAN boot may fail when using an Emulex 32GB FC Adapter

Booting from a multipath attached LUN when using the Emulex 32GB FC Adapter may fail. Note that booting from single path attached LUNs are not affected by this issue. To work around the issue, add the rd.multipath=1 rd.driver.pre=lpfc boot parameter.

For systems with multiple boot disks, such as a local boot disk and a SAN boot disk, the rd.driver.pre=lpfc option does not guarantee that the SAN attached storage is discovered first. To avoid booting from devices other than the SAN, such as from a local disk, additional module_blacklist=disk_driver boot options are required; for example, rd.driver.blacklist=megaraid_sas module_blacklist=megaraid_sas.

(Bug ID 31898488)