Known Issues

Installation Issues

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

Configuring Encryption and /boot During Installation

During installation, if you select Encrypt my data on the Installation Destination screen and then perform manual partitioning, the Encrypt check box is not shown as selected on the Manual Partitioning screen. This check box refers to encryption that you can configure on a file system type that supports encryption or on an LVM logical volume that contains the file system. If you click Modify, the Encrypt check box on the Configure Volume screen is shown as selected for the volume, meaning that the encryption will be applied at the level of the underlying block device.

For LVM, selecting Encrypt my data encrypts the LVM physical volume and all the logical volumes that it contains. If you do not select Encrypt my data, you can encrypt the logical volume by selecting the Encrypt check box on the Manual Partitioning screen or encrypt the physical volume by selecting the Encrypt check box on the Configure Volume screen.

For btrfs, encryption can only be applied to the block device that contains the file system, including its subvolumes. For example, enabling encryption for the /home subvolume of a btrfs root file system implicitly enables encryption for the root file system itself. You can only select the Encrypt check box on the Configure Volume screen. As btrfs does not support encryption at the file-system level, you cannot select the Encrypt check box on the Manual Partitioning screen for a btrfs file system.

Do not select the Encrypt check box or a BTRFS, LVM, or LVM Thin Provisioning device type for /boot. The /boot file system must be configured on a standard partition and should be of type ext4 or XFS.

When entering a password in the Disk Encryption Passphrase dialog, press Tab to move between the entry fields. You cannot use the mouse to select the fields.

Network Installation

Attempting to perform a network installation without configuring a network interface to use DHCP to obtain its IP settings or with static IP settings results in the error Error in Installation Source.

For example, if you use a feature such as a remote console or Lights-out management to access a boot ISO, the network configuration of the embedded server manager might not be available when you select the installation location. The workaround is to use the graphical installer to configure the network settings manually before configuring the installation location. (Bug ID 19047736)

Installation on an iSCSI Disk

When installing on an iSCSI disk, add either ip=ibft or rd.iscsi.ibft=1 to the boot command line and specify at least one MBR or GPT-formatted disk as an installation target. Otherwise, the installation fails with the error message No valid boot loader target device found. (Bug ID 22076589)

Installation on an HP 3PAR TPVV

If you have not applied a Thin Persistence license to an HP 3PAR storage array, installation fails to create a file system on a thin provisioned virtual volume (TPVV). This license is required to support the low-level SCSI UNMAP command for storage reclamation. If you do not have a suitable license, the workaround is to use a fully provisioned virtual volume (FPVV) instead of a TPVV. (Bug ID 22140852)

Oracle Linux 7 update 3 systems running UEK R3 are unable to boot if the `/root` partition is formatted using btrfs

Updates to the btrfs file system utilities that include new features, such as the skinny-metadata feature, are incompatible with UEK R3. If the /root partition is formatted using btrfs, a system running UEK R3 is unable to boot as it cannot mount the /root file system. The system is able to boot using UEK R4 or RHCK kernel types.

This problem is particularly important during installation, as it is possible to manually configure partitioning and the file systems from within the installer. When the file system is formatted within the installer, using btrfs, all of the newer features are enabled. If you select to downgrade the kernel to UEK R3 after installation, the system is unable to boot.

Systems that are already using btrfs with UEK R3 are unaffected when they are upgraded, as the file system would have been formatted with the new features disabled. (Bug ID 24840489)

Upgrade Issues

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

cgconfig and cgred Packages Must Be Restored Separately

The libcgroup package in Oracle Linux 7 does not include the cgconfig and cgred control group services. To restore these services on an upgraded system, install the libcgroup-tools package. (Bug ID 19177606)

Postupgrade Fails if Web Proxy Is Required

The postupgrade scripts fail if a proxy is required to access Oracle Linux yum server. (Bug ID 19169163)

Using an Old Version of yum Causes Dependency Errors

The redhat-upgrade-tool-cli utility requires that you install version 3.2.29-43.0.1 or later of the yum package on the Oracle Linux 6 system that you want to upgrade. If you use an earlier version of the yum package, the upgrade tool fails with dependency errors. (Bug ID 18648783)

Package Conflicts

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

dovecot-devel.i686 and dovecot-devel.x86_64

The dovecot-devel.i686 and dovecot-devel.x86_64 packages in the ol7_x86_64_optional_latest ULN channel conflict. Attempting to install both packages results in a transaction check error:

Transaction check error:
  file /usr/include/dovecot/config.h conflicts between attempted installs of
dovecot-devel-1:2.2.10-7.el7.i686 and dovecot-devel-1:2.2.10-7.el7.x86_64

There are bitsize differences between the identified file. You may only install one of these packages on the same system at once. (Bug ID 25057633)

ipa-server-dns.x86_64 and freeipa-server-dns

There is a conflict between the ipa-server-dns.x86_64 package and the freeipa-server-dns package in the ol7_x86_64_latest ULN channel. The .x86_64 version of the ipa-server-dns package has been superseded by a .noarch package for Oracle Linux 7 update 3.

To avoid the conflict you should exclude the ipa-server-dns.*.x86_64 package in your Yum configuration. See Oracle Linux 7: Administrator's Guide for more information on how to exclude packages. (Bug ID 25054687)

ipa-admintools.x86_64 and freeipa-admintools

There is a conflict between the ipa-admintools.x86_64 package and the freeipa-admintools package in the ol7_x86_64_latest ULN channel. The .x86_64 version of the ipa-admintools package has been superseded by a .noarch package for Oracle Linux 7 update 3.

To avoid the conflict you should exclude the ipa-admintools.*.x86_64 package in your Yum configuration. See Oracle Linux 7: Administrator's Guide for more information on how to exclude packages. (Bug ID 25054687)

rear.x86_64 and rear.noarch

The .noarch version of the rear package in the ol7_x86_64_latest ULN channel has been superseded by a .x86_64 package for Oracle Linux 7 update 3.

To avoid the conflict you should exclude the rear.*.noarch package in your Yum configuration. See Oracle Linux 7: Administrator's Guide for more information on how to exclude packages. (Bug ID 25054687)

PackageKit.i686 and PackageKit.x86_64

The PackageKit.i686 package from the ol7_x86_64_optional_latest ULN channel conflicts with the PackageKit.x86_64 package in the ol7_x86_64_u3_base channel. Attempting to install both packages results in a transaction check error:

Transaction check error:
  file /usr/lib/python2.7/site-packages/packagekit/__init__.pyc from install
of PackageKit-1.0.7-6.0.1.el7.i686 conflicts with file from package
PackageKit-1.0.7-6.0.1.el7.x86_64
  file /usr/lib/python2.7/site-packages/packagekit/__init__.pyo from install
of PackageKit-1.0.7-6.0.1.el7.i686 conflicts with file from package
PackageKit-1.0.7-6.0.1.el7.x86_64
  file /usr/lib/python2.7/site-packages/packagekit/backend.pyc from install
of PackageKit-1.0.7-6.0.1.el7.i686 conflicts with file from package
PackageKit-1.0.7-6.0.1.el7.x86_64
  file /usr/lib/python2.7/site-packages/packagekit/backend.pyo from install
of PackageKit-1.0.7-6.0.1.el7.i686 conflicts with file from package
PackageKit-1.0.7-6.0.1.el7.x86_64
  file /usr/lib/python2.7/site-packages/packagekit/enums.pyc from install of
PackageKit-1.0.7-6.0.1.el7.i686 conflicts with file from package
PackageKit-1.0.7-6.0.1.el7.x86_64
  file /usr/lib/python2.7/site-packages/packagekit/enums.pyo from install of
PackageKit-1.0.7-6.0.1.el7.i686 conflicts with file from package
PackageKit-1.0.7-6.0.1.el7.x86_64
  file /usr/lib/python2.7/site-packages/packagekit/filter.pyc from install of
PackageKit-1.0.7-6.0.1.el7.i686 conflicts with file from package
PackageKit-1.0.7-6.0.1.el7.x86_64
  file /usr/lib/python2.7/site-packages/packagekit/filter.pyo from install of
PackageKit-1.0.7-6.0.1.el7.i686 conflicts with file from package
PackageKit-1.0.7-6.0.1.el7.x86_64
  file /usr/lib/python2.7/site-packages/packagekit/misc.pyc from install of
PackageKit-1.0.7-6.0.1.el7.i686 conflicts with file from package
PackageKit-1.0.7-6.0.1.el7.x86_64
  file /usr/lib/python2.7/site-packages/packagekit/misc.pyo from install of
PackageKit-1.0.7-6.0.1.el7.i686 conflicts with file from package
PackageKit-1.0.7-6.0.1.el7.x86_64
  file /usr/lib/python2.7/site-packages/packagekit/package.pyc from install
of PackageKit-1.0.7-6.0.1.el7.i686 conflicts with file from package
PackageKit-1.0.7-6.0.1.el7.x86_64
  file /usr/lib/python2.7/site-packages/packagekit/package.pyo from install
of PackageKit-1.0.7-6.0.1.el7.i686 conflicts with file from package
PackageKit-1.0.7-6.0.1.el7.x86_64
  file /usr/lib/python2.7/site-packages/packagekit/progress.pyc from install
of PackageKit-1.0.7-6.0.1.el7.i686 conflicts with file from package
PackageKit-1.0.7-6.0.1.el7.x86_64
  file /usr/lib/python2.7/site-packages/packagekit/progress.pyo from install
of PackageKit-1.0.7-6.0.1.el7.i686 conflicts with file from package
PackageKit-1.0.7-6.0.1.el7.x86_64

You may only install one of these packages on the same system at once. You should exclude the PackageKit.i686 package in your Yum configuration. See Oracle Linux 7: Administrator's Guide for information on how to exclude packages. (Bug ID 24963661)

sssd-common.i686 and sssd-common.x86_64

The sssd-common.i686 package conflicts with the sssd-common.x86_64 package in the ol7_x86_64_optional_base ULN channel. Attempting to install both packages results in a transaction check error:

Transaction check error:
  file /usr/share/systemtap/tapset/sssd.stp conflicts between attempted
installs of sssd-common-1.14.0-14.el7.i686 and
sssd-common-1.14.0-14.el7.x86_64

You may only install one of these packages on the same system at once. You should exclude the sssd-common.i686 package in your Yum configuration. See Oracle Linux 7: Administrator's Guide for more information on how to exclude packages. (Bug ID 24963661)

File System Related Bugs

The following are issues that related to file systems:

xfs: Kernel panic in the multi-block buffer logging code

A bug exists in the multi-block buffer logging code, for XFS, that causes a kernel panic at log push time due to invalid regions being set in the buffer log format bitmap. (Bug ID 24400444)

btrfs: Kernel warning after snapshot is created with incorrect qgroup

If qgroups are enabled, creating a snapshot that inherits from an invalid qgroup can cause the file system to crash and a warning to appear for the kernel in the system log. For example, the following operation causes the transaction to abort:

# btrfs subvolume snapshot -i 1/10 /mnt/scratch/ /mnt/scratch/snapshot

(Bug ID 24716895)

btrfs: Unable to replay log after snapshot delete and parent directory fsync

If a snapshot is deleted and the parent directory is fsynced the log cannot be replayed during the next mount operation, preventing the file system from mounting. This is solvable by wiping the log trees using the btrfs-zero-log tool but is very inconvenient as it results in the loss of any data and metadata fsynced before the parent directory was fsynced. (Bug ID 24424719)

btrfs: Empty symbolic link after fsync of parent directory

If a symbolic link is created and the parent directory is fsynced, a system crash or power outage results in an empty symbolic link when the file system is remounted. (Bug ID 23748445)

btrfs: Incorrect directory entries after fsync log replay

If a directory or file is moved to a new parent directory and the file system logs the new parent but does not explicitly log the old parent, when the log is replayed entries for the moved directory of file can appear in both the old and new parent directories. (Bug ID 23748405)

btrfs: File loss on log replay after renaming a file and fsync

If a file is renamed and fsynced and a system crash or power outage occurs, when the log is replayed, the file is deleted because the last_unlink_trans value is not captured in the log of the inode leaving the log without enough information to later replay the rename operation. (Bug ID 23725060)

btrfs: qgroup Reserved space leaks

Several bugs surrounding the way in which quota groups (qgroups) reserve space result in leaks. This includes an issue where leaks are caused by rewriting to dirty ranges, resulting in a "pwrite64: Disk quota exceeded" error. (Bug ID 22483655)

btrfs: Incorrect exclusive reference count after cloning file between subvolumes

The count for exclusive references is incorrect after cloning a file between two subvolumes. This issue is related to quota groups and the way in which some code is implemented. (Bug ID 22456419)

btrfs: Kernel oops when unmounting during a quota rescan or disable

Operations that trigger a quota rescan or to disable the quota on a mounted file system cause a kernel oops message when attempting to unmount the file system. This can cause the system to hang. (Bug ID 22377928)

btrfs: Kernel oops when removing shared extents using qgroup accounting

The removal of shared extents where quota group (qgroup) accounting is used can result in a kernel oops message. This relates to an issue where inaccurate results are obtained during a back reference walk due to missing records when adding delayed references. (Bug ID 21554517)

ext4: System hang when processing corrupted orphaned inode list

If the orphaned inode list is corrupted the inode may be processed repeatedly resulting in a system hang. For example, if the orphaned inode list contains a reference to the bootloader inode, ext4_iget() returns a bad inode resulting in the processing loop that can hang the system. (Bug ID 24433290)

xfs, ext4: IO error during DIO/AIO write results in disk content corruption

Disk content is corrupted when a Direct IO (DIO) or Asynchronous IO (AIO) write to an unwritten extent fails due to an IO error. (Bug ID 24393811)

Automatic Bug Reporting Tool

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.

Auto-completion of Commands in the bash Shell

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:

Remove the bash-completion package:
```
sudo yum remove bash-completion
```
Run the complete -r command in the shell. To make this command persistent, you could put it in $HOME/.bashrc.

(Bug ID 19248362)

Crash Kernel auto Setting

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)

firewalld Does Not Currently Support IPv6 NAT Under UEK R3

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)

grubby Sets Incorrect Saved Entry

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)

grubby Fatal Error Upgrading Kernel When `/boot` Is On a btrfs Subvolume

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)

Hebrew LaTeX Fonts

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

InfiniBand Issues

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

Configuring Internet Protocol over InfiniBand (IPoIB)

To configure Internet Protocol over InfiniBand (IPoIB):

Edit the /etc/sysconfig/network-scripts/ifcfg-ibN configuration file, where N is the number of the interface. The following example shows the configuration for the interface ib0:
```
DEVICE=ib0
TYPE=InfiniBand
ONBOOT=yes 
DHCP_HOSTNAME="myhost.mydom.com"
BOOTPROTO=static
IPADDR=192.168.100.1
NETMASK=255.255.255.0
IPV4_FAILURE_FATAL=yes
IPV6INIT=no 
CONNECTED_MODE=no
NAME=ib0 
```
Stop the NetworkManager service:
```
sudo systemctl stop NetworkManager
```
Start the RDMA service:
```
sudo systemctl start rdma
```
Bring up the interface:
```
sudo ifup ibN
```
(Bug ID 19150870)

Changing the IPoIB mode of an InfiniBand Interface

The IPoIB driver supports the use of either connected mode or datagram mode with an interface, where datagram mode is the default mode. Changing the mode of an InfiniBand interface by echoing either connected or datagram to /sys/class/net/ibN/mode is not supported for UEK R3. It is also not possible to change the mode of an InfiniBand interface while it is enabled if you are running UEK R3.

To change the IPoIB mode of an InfiniBand interface on a UEK R3 system:

Edit the /etc/sysconfig/network-scripts/ifcfg-ibN configuration file, where N is the number of the interface:
- To configure connected mode, specify CONNECTED_MODE=yes in the file.
- To configure datagram mode, either specify CONNECTED_MODE=no in the file or do not specify this setting at all (datagram mode is enabled by default).
Note:

Before saving your changes, make sure that you have not specified more than one setting for CONNECTED_MODE in the file.
To enable the specified mode on the interface, use the following commands to take down the interface and bring it back up:
```
sudo ifdown ibN
sudo ifup ibN
```

Note:

This issue is resolved in UEK R4.

(Bug ID 17479833)

Disabling an InfiniBand CA Port Generates Warnings

You might see the following warning messages if you use the ibportstate disable command to disable an InfiniBand CA or router port:

ibwarn: [2696] _do_madrpc: recv failed: Connection timed out
ibwarn: [2696] mad_rpc: _do_madrpc failed; dport (Lid 38)
ibportstate: iberror: failed: smp set portinfo failed

You can safely ignore these warnings. (Bug ID 16248314)

Intel QuickAssist Acceleration Technology

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

Database Installation and Operation Fails if RemoveIPC=yes Is Configured for systemd

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)

MariaDB Installation

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)

Oracle ASM Fails to Initialize with SELinux in Enforcing Mode

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)

multipath Messages Relating to zram on UEK R3

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)

Unable to create Oracle Linux 7 LXC containers on NFS

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 on Oracle VM and Xen

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.

Hyper-V related services fail to start on Oracle Linux 7 update 3 guest with UEK R4 kernel under Windows Hyper-V Server

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:

Stop any running Hyper-V services:

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

Downgrade the packages:
```
sudo yum downgrade hyperv*
```

Restart the Hyper-V services:

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

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 Loading kvm_intel Module with UEK R3

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)

systemd Fails to Load the autofs4 and ipv6 Modules with UEK R3

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)

MACsec/IEEE 802.1AE network driver support not available in UEK

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

Geneve network driver support not available in UEK

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

Co-existing IPv4 and IPv6 VxLAN Workaround for UEK R4u2

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:

Enable the bindv6only system-wide socket option:
```
sudo sysctl -w net.ipv6.bindv6only=1
```
Bring up the IPv6 interface, for example:
```
sudo ip link set vlt2 up
```
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)

net_prio Control Group

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)

Network Manager is Unable to Add IPv6 Addresses to Interfaces on UEK R3

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)

Network Connection Icon Reports Incorrect State for Interfaces

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)

Power Button Defaults to ACPI Suspend

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)