1. Release Notes for Oracle Linux 8.10
  2. Known Issues
  3. Installation and Upgrade Issues

Installation and Upgrade Issues

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

Messages Referring to tmpfiles.d Files Appear During Upgrade

During an upgrade from Oracle Linux 8.5 to Oracle Linux 8.6, and with the appropriate Oracle Linux 8 repositories enabled, the dnf upgrade command displays messages similar to the following: 

Running scriptlet: systemd-239-44.0.1.el8.x86_64                    
4550/4550
[/usr/lib/tmpfiles.d/dnssec-trigger.conf:1] Line references path below legacy
directory /var/run/, updating /var/run/dnssec-trigger → /run/dnssec-trigger;
please update the tmpfiles.d/ drop-in file accordingly.
[/usr/lib/tmpfiles.d/krb5-krb5kdc.conf:1] Line references path below legacy
directory /var/run/, updating /var/run/krb5kdc → /run/krb5kdc; please update
the tmpfiles.d/ drop-in file accordingly.
[/usr/lib/tmpfiles.d/nss-pam-ldapd.conf:2] Line references path below legacy
directory /var/run/, updating /var/run/nslcd → /run/nslcd; please update the
tmpfiles.d/ drop-in file accordingly.
[/usr/lib/tmpfiles.d/pesign.conf:1] Line references path below legacy
directory /var/run/, updating /var/run/pesign → /run/pesign; please update
the tmpfiles.d/ drop-in file accordingly.
[/usr/lib/tmpfiles.d/portreserve.conf:1] Line references path below legacy
directory /var/run/, updating /var/run/portreserve → /run/portreserve; please
update the tmpfiles.d/ drop-in file accordingly.
.
.
.

These messages can be safely ignored, as the upgrade or package installation completes successfully.

As an alternative workaround, update the configuration by following the instructions in the message. Change the legacy var/run/<...> directory path to /run/<...>.

(Bug ID 32852433)

Installer Automatically Enables Ethernet Over USB Network Interface During a PXE Installation

During a Preboot Execution Environment (PXE) installation of Oracle Linux 8, the installer automatically enables the Ethernet over USB network interface with the bootproto=dhcp and ONBOOT=yes parameters. These default settings 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 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 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, then after the installation, change the network configuration setting for the Ethernet over USB network interface to ONBOOT=no. Then reboot the system.

(Bug ID 31888490)

Interactive Text-Based Installation Wizard Unable to Complete When An Alternate Language Is Selected

If you selected an alternate language while using the text-based installer to install the OS, you cannot proceed with the installation. The installation is blocked with [!] flags for Software Selection and Installation Destination regardless of what you have set for these two options.

However, this issue does not occur if you are performing an installation by using the default English language selection or by using the graphical installation program.

(Bug IDs 30535416, 29648703)

Graphical Installation Program Fails to Produce Error When an Unacceptable Kdump Value Is Entered

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, 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)

Graphical Installation Program Does Not Display the Reserved Memory That's Manually Set For Kdump

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.

Note:

The default setting auto for Kdump memory reservation is adequate as the kernel determines what size to use when it boots

(Bug IDs 31133287 and 31182699)

Scriptlet-Related Error for microcode_ctl Might Be Displayed During Upgrade

A scriplet-related error message might be displayed during an upgrade of an Oracle Linux 8 release to its next version. When you run the dnf update command, an output similar to the following might appear: 

  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

This error message is displayed if you use the Server with GUI environment to install Oracle Linux 8 and then you reboot the server by using RHCK. This installation method installs the kernel dependent, kmod-kvdo package or module, which is a different version in the previous Oracle Linux 8 release.

However, you can safely ignore the message because the kmod-kvdo package is successfully installed during the upgrade process.

Note:

This error does not occur if you install the Minimal Install base environment or if you boot the server with UEK R6 or UEK R7.

(Bug ID 31292199)

rhnreg_ks Register Command Might Fail If python3-rhn-virtualization-host Package Is Installed

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)

Package Conflict Between usbguard-1.0.0-2.el8.i686 And usbguard-1.0.0-8.el8.x86_64 on Oracle Linux 8 Upgrades

Beginning with Oracle Linux 8.5, when you upgrade Oracle Linux 8 with both the ol8_baseos_latest and ol8_appstream yum repositories enabled, a conflict between the usbguard-1.0.0-2.el8.i686 and usbguard-1.0.0-8.el8.x86_64 packages occurs.

The following error is produced: 

Problem: package usbguard-1.0.0-8.el8.x86_64 conflicts with usbguard
provided by usbguard-1.0.0-2.el8.i686
  - cannot install the best candidate for the job
  - problem with installed package usbguard-1.0.0-2.el8.i686
(try to add '--allowerasing' to command line to replace conflicting packages
or '--skip-broken' to skip uninstallable packages or '--nobest' to use not
only best candidate packages)

This conflict occurs because in Oracle Linux 8.6 and later releases, the usbguard-1.0.0-2.el8.i686 and the usbguard-1.0.0-8.el8.x86_64 packages conflict with each other and could no longer be installed together, unlike in previous Oracle Linux 8 releases.

To work around this issue, remove the usbguard-1.0.0-2.el8.i686 package from your Oracle Linux 8 system prior to upgrading to the current release.

(Bug ID 34097708)

Presence of beignet Package Could Result in Dependency Issue During An Upgrade

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)

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 options to register with ULN and to use Oracle Ksplice isn't 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)

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

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)

aarch64 Only: Installer Displays Error: 'Failed to set new efi boot target' on Systems With a Multipath-Enabled NVMe Controller

The Oracle Linux 8.7 installer displays the following error on aarch64 systems that have a multipath-enabled NVMe controller: 

Failed to set new efi boot target . This is most likely a kernel or firmware bug.

To work around this issue, disable native multipath support for the installation at boot time by adding the nvme_core.multipath=N command-line argument on the target system.

(Bug IDs 34233800, 34215333, 31758304)

Mellanox NIC interface name subject to change after upgrading from RHCK or UEK R6 to UEK R7

During a kernel upgrade of x86_64 systems from RHCK or UEK R6 to UEK R7, the mlx5_core device name is subject to change, from ens2f0 (RHCK or UEK R6) to ens2f0np0 (UEK R7).

You might encounter this issue if you selected Server With GUI as the installation profile and under the following circumstances:

  • When upgrading an Oracle Linux 8 system that's running RHCK or UEKR6 to UEK R7.

  • When upgrading an Oracle Linux 8 system that's running RHCK or UEK R6 to Oracle Linux 9, which ships with UEK R7 by default.

  • When upgrading an Oracle Linux 8 system that's already running UEK R7 to Oracle Linux 9.

    Note:

    In the case where an Oracle Linux 8 system is already running UEK R7, if you previously configured the system to use backward-compatible device names (ens2f0), you might need to apply the workaround that follows to the GRUB configuration after the upgrade to Oracle Linux 9 has completed.

Note that fresh installations of UEK R7 on Oracle Linux 8 and Oracle Linux 9 use the default naming convention for UEK R7 (enp2s0f0np0) by default.

To retain backward-compatible (RHCK) device names for the mlx5_core driver-based network interface card (NIC), perform the following workaround after upgrading to UEK R7, prior to rebooting the system. We recommended that you back up the existing grub.cfg file before making this change.

  1. Edit the /etc/default/grub file and append the end of the line in the GRUB_CMDLINE_LINUX= module as follows: 

    GRUB_CMDLINE_LINUX="console=xxxx mlx5_core.expose_pf_phys_port_name=0"

  2. After editing the file, locate the grub.cfg file on the system, then run the command to update GRUB configuration, as appropriate:

    • On BIOS-based systems, the grub.cfg output/target file is typically located at /boot/grub2/grub.cfg and you would run the following command: 

      sudo grub2-mkconfig -o /boot/grub2/grub.cfg

    • On UEFI-based systems, the grub.cfg output/target file could be located at /etc/grub2-efi.cfg or /boot/efi/EFI/redhat/grub.cfg. Depending on the location of the file, you would run one of the following commands: 

      sudo grub2-mkconfig -o /etc/grub2-efi.cfg
      sudo grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg

  3. Reboot the system for the changes to take effect.

(Bug IDs 34103369, 34145887, 35270018)