Chapter 4 Known Issues

Table of Contents

This chapter describes known issues that have been encountered in the Oracle Linux 8.1 release.

4.1 Installation and Upgrade Issues

The following are known installation and upgrade issues that have been encountered in Oracle Linux 8.1.

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

If an alternate language is selected for installation when using the text-based installer, it is not possible to progress through all of the steps in the installation wizard. The installation is blocked with [!] bullets for Software selection and Installation Destination, regardless of what is selected for these two options.

This issue does not occur when performing an installation by using the default language selection of English or when using the graphical installer.

(Bug ID 30535416)

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

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.

You can avoid these issues by not setting 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 rhnreg_ks register command may fail if python3-rhn-virtualization-host package is installed

Attempting to register with ULN in Oracle Linux 8.1 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.4 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 provides you with 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.

An alternative option is to register with ULN after the installation completes. For instructions, visit

(Bug ID 29933974)

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

During an Oracle Linux 8.1 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*
# modinfo ip_tables
alias:          ipt_icmp
description:    IPv4 packet filter
author:         Netfilter Core Team <>
license:        GPL
rhelversion:    8.0
srcversion:     3967C875058C2EE2475C9C2
retpoline:      Y
intree:         Y
name:           ip_tables
vermagic:       4.18.0-32.el8.x86_64 SMP mod_unload modversions
sig_id:         PKCS#7
sig_hashalgo:   md4
signature:      30:82:02:59:06:09:2A:86:48:86:F7:0D:01:07:02:A0:82:02:4A:30:

(Bug ID 29500599)

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

A successful installation of Oracle Linux 8.1 on an Oracle VM VirtualBox guest, where the graphical installer is used and where 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.


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 in Oracle VM VirtualBox 6.0, or later.

(Bug ID 30004543)

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

After installing Oracle Linux 8.1 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 Oracle Linux 8 packages to Oracle Linux 8.1

The glusterfs-*.i686 packages are not included in Oracle Linux 8.1. As a result, running the yum update glusterfs* command to upgrade the Oracle Linux 8 packages to Oracle Linux 8.1 fails if both glusterfs-*.i686 and glusterfs-*.x86_64 packages are installed..

The workaround for this issue is to first remove the glusterfs-*.i686 packages from the system 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 Cockpit web console's Services page has been updated in Oracle Linux 8.1 to enable you to search services by name, description, and state. This new functionality works as expected for filtering services by Name and Description, but if you attempt to filter services by State, an error is produced indicating there are no matching results.

(Bug ID 30286168)

4.4 libstorage package conflict causes dnf groupinstall command to fail

Running the dnf groupinstall command can cause an installation to fail. This issue is due to a conflict with a core dependency package (libstoragemgmt), where a conflict exists between i686 and x86_64 packages.

As a workaround, specify the --nobest option when running the dnf groupinstall command, which allows you to install packages for either build architecture and thus avoid this conflict, for example:

# dnf groupinstall "Server with GUI" --nobest
# dnf group update "Server with GUI"

(Bug ID 30882591)

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

The Oracle Linux 8.1 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 have been 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 have been 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.6 File System Issues

The following are known file systems issues that have been encountered in Oracle Linux 8.1.

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

If a system that is using ext4 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.7 Kernel Issues

The following are known kernel issues that have been encountered in Oracle Linux 8.1.

4.7.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
[   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
[   12.852297] amd64_edac_mod: Unknown symbol amd_register_ecc_decoder (err

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.

(Bug ID 29853602)

4.7.2 Output of modinfo does not show Retpoline support

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

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

(Bug ID 29894295)

4.7.3 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.1 causes Kdump to run out of memory if you attempt to mount /sysroot on a Fibre Channel (FC) disk that uses the Logical Volume Manager (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.8 Networking Issues

The following are networking issues that might be encountered in Oracle Linux 8.1.

4.8.1 tracepath6 does not parse destination IPv6 address correctly

When running the tracepath6 command in Oracle Linux 8.1, the command fails to parse the destination IPv6 address correctly. 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.8.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 can be done either temporarily by running setenforce 0. 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.9 Running nohup prevents ssh command from executing

If you run the nohup command (as shown in the following example) on an Oracle Linux 8.1 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.10 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.11 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 appear 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 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.12 Podman Issues

The following are known issues for the Podman container management tool in Oracle Linux 8.1.

4.12.1 Executing podman attach --latest causes panic if no containers are available

If you execute podman attach --latest and no containers exist in your environment, a runtime error occurs:

# podman  attach --latest
panic: runtime error: index out of range

Note that this error no longer occurs as soon as there are containers in the environment. Running the command when there are no containers is meaningless.

(Bug ID 29882537)

4.12.2 Requirements for using the default podman detach key sequence

The default key sequence that you use to detach a container (CTRL+P, CTRL+Q) requires a console that can handle detachment (pseudo-tty), as well as an input channel for passing control signals (stdin). Otherwise, you cannot create a container, attach it with the podman attach -l command, and then quit or detach the container by using the default key sequence, as documented in the podman-attach(1) manual page.

To ensure that you can use the default CTRL+P, CTRL+Q key sequence to detach a container, use either of the following methods to create a container:

  • Create a container in the background:

    # podman run --rm -t -d top -b

    You can then use the podman attach -l command to attach the container and the CTRL+P, CTRL+Q key sequence to detach the container.

  • Create a container interactively:

    # podman run --rm -t -i top -b

    The interactive method creates the container and automatically attaches it. You can then use the CTRL+P, CTRL+Q key sequence to detach the container.

    For more information, see the podman(1) and podman-attach(1) manual pages.

(Bug ID 29882852)

4.12.3 Authentication error displayed when attempting to pull an image and not specifying its correct name

If you attempt to pull an image by running the podman pull image-name command, but you do not specify the correct or full name of the image, an authentication error occurs.

For example, the following error is displayed because oracle:latest was specified as the name of the image instead of oraclelinux:latest, which is the correct name for the image:

$ podman pull oracle:latest
Trying to pull
Trying to pull
Trying to pull
error pulling image "oracle:latest": unable to pull oracle:latest: 3 errors

* Error determining manifest MIME type for
docker:// unable to retrieve auth token:
invalid username/password
* Error determining manifest MIME type for docker://
Error reading manifest latest in error parsing HTTP 404
response body: invalid character '<' looking for beginning of value:
"<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 3.2 Final//EN\">\n<title>404 Not
Found</title>\n<h1>Not Found</h1>\n<p>The requested URL was not found on the
server.  If you entered the URL manually please check your spelling and try
* Error determining manifest MIME type for docker://oracle:latest: Error
reading manifest latest in errors:
denied: requested access to the resource is denied
unauthorized: authentication required

To prevent this error from occurring, always specify the correct image name with the podman pull command.

(Bug ID 29894231)

4.12.4 Oracle Container Registry unable to service requests to search catalog

Attempts to search for an image in the Oracle Container Registry by using the podman search command fail with an authorization error, even if you are logged into the registry:

# podman search oraclelinux
ERRO[0001] error getting search results from v2 endpoint
"", status code 401 (Unauthorized)

The issue is related to how Oracle Container Registry handles token requests for access to "/v2/_catalog". The podman search command only requests a token for ping-level access and not for catalog access.

There is currently no workaround for this issue.

(Bug ID 29942671)