The following sections describe issues that might be encountered during installation.

The following sections describe issues that might be encountered when upgrading from Oracle Linux 6 (_latest) to Oracle Linux 7 Update 3.

This section describes known package conflicts for packages distributed by Oracle for Oracle Linux 7 via ULN or Oracle Linux yum server.

The following are issues that related to file systems:

The automated reporting daemons and features provided by the Red Hat Automatic Bug Reporting Tool (ABRT) are not supported with Oracle Linux

ABRT packages and associated files, such as libreport, are included in the distribution to satisfy package dependencies and can be used to generate local bug reports but the features to automatically upload these reports are not supported. For technical assistance, contact Oracle Support by using the My Oracle Support portal or by telephone.

Pressing the Tab key to complete commands automatically in the bash shell works for some commands such as ls but not for other commands such as export. You can use the following workaround to enable auto completion for all commands:

1. Remove the bash-completion package:

   sudo yum remove bash-completion

2. Run the complete -r command in the shell. To make this command persistent, you could put it in $HOME/.bashrc.

(Bug ID 19248362)

If you enable the crashkernel=auto kernel parameter for UEK R3 to simplify Kdump configuration, both dmesg output and /proc/cmdline show crashkernel=NNNM@0M. This is the expected behavior for the implementation, where @0M implies the auto setting. The crashkernel=auto parameter is not supported for Xen.

(Bug ID 17616874)

The following error message indicates that IPv6 NAT is not currently supported by firewalld with UEK R3.

ERROR: ipv6 table 'nat' does not exist (or not enough permission to check)

(Bug ID 18504545)

If grubby is used to remove a kernel menu entry from the GRUB 2 configuration, the value of the default entry in /etc/grub2/grub.cfg is incorrect. The workaround is to set the value of GRUB_DEFAULT in /etc/default/grub to the correct entry and use grub2-mkconfig to recreate /etc/grub2/grub.cfg, or use yum or rpm to remove the kernel packages. (Bug ID 19192278)

If /boot is hosted on a btrfs subvolume, GRUB 2 is unable to correctly process the initramfs and vmlinuz pathnames. This problem occurs when you update or install a new kernel and grubby attempts to update the GRUB 2 configuration. In the case where you are running a fresh installation of Oracle Linux 7 update 3 and you upgrade the RHCK or UEK kernel, the following error is displayed:

grubby fatal error: unable to find a suitable template

When the system is rebooted, after the kernel update, the system boots to the old kernel.

Similarly, when upgrading from Oracle Linux 7 update 2 to Oracle Linux 7 update 3, if the /boot directory is hosted on a btrfs subvolume, the system boots to the old Oracle Linux 7 update 2 kernel after the upgrade is complete.

The workaround to this problem is to use grub2-mkconfig to recreate /etc/grub2/grub.cfg immediately after the kernel has been installed or upgraded. For example:

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

Obtain a listing of the kernel menu entries in the generated configuration:

grep -P "submenu|^menuentry" /boot/grub2/grub.cfg | cut -d "'" -f2

From the listing, select the kernel entry that you wish to run as the default kernel and set this entry as the default using the following command, substituting menu entry title with the title of the kernel entry that you identified in the listing:

grub2-set-default "menu entry title"

You can use the grub2-editenv list command to check that the saved_entry has been updated with the selected kernel menu title.

Reboot and use uname -a to check that the correct kernel is running when the system is rebooted.

(Bug ID 22750169)

Installing the tex-fonts-hebrew package fails unless you first install all texlive* packages. (Bug ID 19059949)

The following sections describe issues that might be encountered when using InfiniBand devices.

The UEK R3 does not support the QAT driver that allows cryptographic capabilities to be offloaded to QuickAssist hardware.

If RemoveIPC=yes is configured for systemd, interprocess communication (IPC) is terminated for a non-system user's processes when that user logs out. This setting, which is intended for laptops, can cause software problems on server systems. For example, if the user is a database software owner such as oracle for Oracle Database, this configuration can cause database installation to fail or database services to crash.

By default, Oracle Linux 7 Update 3 configures RemoveIPC=no in /etc/systemd/logind.conf to prevent systemd from terminating IPC. However, if you have touched this file before updating your system to Oracle Linux 7 Update 3, the update installs the new version of the file as /etc/systemd/logind.conf.rpmnew and does not set RemoveIPC=no in /etc/systemd/logind.conf. To avoid database crashes, set RemoveIPC=no in /etc/systemd/logind.conf and run systemctl reboot to reboot the system. (Bug ID 22224874)

If you want to install MariaDB, you must deselect the MySQL repository. Otherwise, MySQL is installed even if you select only the MariaDB group. (Bug ID 22238684)

The /etc/init.d/oracleasm script fails if SELinux is in Enforcing mode. This interface is deprecated. Instead, use the global oracleasm userspace tool installed in /usr/sbin/oracleasm to run any oracleasm operations while SELinux is enabled.

(Bug ID 18513404)

Running the multipath -ll command under UEK R3 produces messages such as the following:

zram0: No fc_host device for 'host'
zram0: No fc_host device for 'host'
zram0: No fc_remote_port device for 'rport--1:-1-0'

You can ignore these message as there is no effect on multipath functionality. You can prevent the messages from occurring by blocklisting the zram device in /etc/multipath.conf.

Note that this issue is fixed for RHCK and UEK R4 u2 as zram support is compiled into separate kernel modules that can be loaded as needed. The warning messages reappear if the zram kernel module is loaded for either of these kernels.

(Bug ID 20300644)

The creation of Oracle Linux 7 containers fail when the root file system (/container) is hosted on an NFS share. RPM fails to set capabilities while attempting to install some packages. For instance, when attempting to create an Oracle Linux 7 update 2 container, the installation fails while installing the iputils package:

Error unpacking rpm package iputils-20121221-7.el7.x86_64
error: unpacking of archive failed on file /usr/bin/ping: cpio: cap_set_file
error: iputils-20121221-7.el7.x86_64: install failed

Similar issues are seen when attempting to install the initscripts and systemd packages while creating an Oracle Linux 7 update 1 container.

This issue occurs on both NFSv3 and NFSv4.

Oracle Linux 6 containers are unaffected.

(Bug ID 25024258)

Oracle Linux 7 guests are supported for both hardware virtualization (HVM) and hardware virtualization with paravirtual drivers (PVHVM) on Oracle VM 3. Oracle Linux 7 guests in a paravirtualized domain (PVM) on Oracle VM or other Xen-based hypervisors are not supported.

Oracle Linux 7 guests of any type are not supported on Oracle VM 2.

For an Oracle Linux 7 update 3 guest with UEK R4 kernel running on Windows Hyper-V Server, the hypervkvpd and hypervvssd services fail to start if the Hyper-V packages are at version 0-0.29.20160216git.el7.

The workaround is to downgrade the package version to 0-0.26.20150402git.el7 for the following packages:

• hyperv-daemons

• hyperv-daemons-license

• hypervfcopyd

• hypervkvpd

• hypervvssd

These userspace packages are available in both the ol7_latest yum repository and in the ol7_x86_64_UEKR4 ULN channel.

Use the yum utility to downgrade the packages. For example:

1. Stop any running Hyper-V services:

   sudo systemctl stop hypervfcopyd.service
   sudo systemctl stop hypervkvpd.service
   sudo systemctl stop hypervvssd.service

2. Downgrade the packages:

   sudo yum downgrade hyperv*

3. Restart the Hyper-V services:

   sudo systemctl restart hypervfcopyd.service
   sudo systemctl restart hypervkvpd.service
   sudo systemctl restart hypervvssd.service

4. Modify your Yum configuration to exclude the Hyper-V packages from future updates. For example:

   echo "exclude = hyperv*" >> /etc/yum.conf

   Remember that you may want to remove this exclude at a later date when this issue is resolved.

(Bug ID 24745861)

Per-CPU allocation fails when the kvm_intel module is loaded with UEK R3. Messages such as the following are logged:

kvm_intel: Could not allocate 48 bytes percpu data 
PERCPU: limit reached, disable warning 

There is no current workaround for UEK R3. (Bug ID 18459498)

At boot time, systemd fails to load the autofs4 and ipv6 modules and errors such as the following are logged:

systemd[1]: Failed to insert module 'autofs4'
systemd[1]: Failed to insert module 'ipv6'

There is no current workaround for UEK R3. (Bug ID 18470449)

The ip and iproute commands included with Oracle Linux 7 Update 3 include support for MACsec network devices. The module for this driver is included with the RHCK but is not included in either UEK R3 or UEK R4. The commands to set or view MACsec features are only functional when used with the RHCK. (Bug ID 24614549).

The ip and iproute commands included with Oracle Linux 7 Update 3 include support for Geneve-capable devices. The module for this driver is included with the RHCK but is not included in either UEK R3 or UEK R4. The commands to set, add or view Geneve devices are only functional when used with the RHCK. (Bug ID 24652835) .

Where VxLANs are configured for both IPv4 and IPv6 on the same host, there may be issues on UEK R4u2, due to the inability to bind the VxLAN tunnel on the same port and due to the way in which IPv6 sockets lists for IPv4 traffic as well. A patch has been applied in the RHCK, but the patch is not available in UEK R4u2.

To allow both versions of VxLAN to co-exist on the same system running Oracle Linux 7 update 3 when using UEK R4, enable the bindv6only system-wide socket option before bringing up the IPv6 VxLAN interface. You can disable the bindv6only system-wide socket option once the interface is online:

1. Enable the bindv6only system-wide socket option:

   sudo sysctl -w net.ipv6.bindv6only=1

2. Bring up the IPv6 interface, for example:

   sudo ip link set vlt2 up

3. Disable the bindv6only system-wide socket option once you are certain that the IPv6 interface is up:

   sudo sysctl -w net.ipv6.bindv6only=0

(Bug ID 24579830)

The Network Priority cgroup subsystem (net_prio) is not currently supported for use with UEK R3. Attempting to use the module with UEK R3 results in error messages such as the following:

modprobe: FATAL: Module netprio_cgroup not found
mount: special device cgroup does not exist.

(Bug ID 18966564)

After upgrading from Oracle Linux 7 update 2 to Oracle Linux update 3, or when running UEK R3 on Oracle Linux 7 update 3, network interfaces configured for IPv6 may not be brought up by Network Manager and errors appear in the system log, similar to the following:

<error> platform-linux: do-add-ip6-address[2: fe80::210:e0ff:fe5f:920c]:
        failure 22 (Invalid argument)
<error> platform-linux: do-add-ip6-address[5: fd00:1:1:24::456]:
        failure 22 (Invalid argument)

It is possible to manually add the IPv6 address to the interface using the ip addr add command.

This issue is apparent regardless of whether IPv6 is configured statically, assigned dynamically via DHCP, or configured via Stateless Address Autoconfiguration (SLAAC).

The workaround for this issue is to disable Network Manager for interfaces where IPv6 must be configured for an interface. To disable Network Manager for an interface, edit the network script for the interface in /etc/sysconfig/network-scripts/ifcfg-dev and add the parameter NM_CONTROLLED=no. For example:

echo "NM_CONTROLLED=no" >> /etc/sysconfig/network-scripts/ifcfg-eno4

(Bug ID 24848072)

The network connection icon might report an active network interface as being disconnected. This behavior is seen for the root user but not for other users. Command-line utilities such as ip link and ifconfig report the correct state. (Bug ID 19060089)

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

In previous Oracle Linux versions, the hardware power button initiated a system shutdown. To make Oracle Linux 7 do the same, create a file named /etc/dconf/db/local.d/01-shutdown-button with the following content:

[org/gnome/settings-daemon/plugins/power]
button-power='shutdown'

Then run the following command:

sudo dconf update

You must log out of the desktop environment and log back in for the new setting to take effect. (Bug ID 25597898)