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.

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)

Unable to boot after installation on systems using the Broadcom MegaRAID 9460 controller

Some systems having Intel® Xeon® E3 v5, Intel® Xeon® Platinum 8100, Intel® Xeon® Gold 6100, Intel® Xeon® Gold 5100, Intel® Xeon® Silver 4100 and Intel® Xeon® Bronze 3100 families of processors (formerly known as Skylake) may use the updated Broadcom MegaRAID 9460 RAID controller that depends on the MegaRAID_SAS v7.x. driver. This driver is not available on the installation media for this release. If Oracle Linux 7 is installed on a RAID volume attached to this controller the system is not able to boot.

To install the correct driver modules for this hardware, you must download and prepare a Driver Update Disk. This Driver update disk contains the following updated driver modules:

megaraid_sas 07.701.17.00-rc1
mpt3sas 15.100.00.00
smartpqi 1.0.4-100

Updated modules are provided for both UEK and RHCK as required.

You can download the Driver Update Disk from the Oracle Software Delivery Cloud at https://edelivery.oracle.com/. Search for 'Oracle Linux 7.4' and select the software to add it to your basket. Click on the 'Selected Software' basket and click Continue. Accept the Oracle Standard Terms and Restrictions and click Continue. You can select the Driver Update Disk files that are part of this media pack to download:

V952636-01.zip Readme for Driver Update Disk
V952635-01.iso Driver Update Disk for Oracle Linux 7 x86_64

Instructions for preparation and installation are covered in Oracle Linux 7: Installation Guide at:

https://docs.oracle.com/en/operating-systems/oracle-linux/7/install/ol7-install-dud.html

(Bug ID 26426929)

Upgrade Issues

You might encounter the following issues when upgrading from Oracle Linux 6 (_latest) to Oracle Linux 7 Update 4.

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

The following are known package conflicts for packages distributed by Oracle for Oracle Linux 7 through ULN or the Oracle Linux yum server.

rdma-core and infiniband-diags when installing oracle-ofed-release

There is a conflict between the rdma-core and infiniband-diags packages.

The conflict occurs when installing the oracle-ofed-release package, as RPM detects the conflict and attempts to install rdma-core-* packages instead of RDMA, which results in additional errors related to dependencies.

To avoid the conflict, use the ‐‐exclude=rdma-core* yum option when performing an install or upgrade of the OFED packages and install the yum-plugin-priorities package from the ol7_optional_latest yum repository on the Oracle Linux yum server. See Oracle-Supported OFED Packages for more information. (Bug ID 26309256)

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 more 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 file systems issues are related to Oracle Linux 7 Update 4.

AutoFS: AMD map `browsable_dirs` option does not work unless it is set in the `[amd]` section of `autofs.conf`

The autofs package, used to automatically mount file systems as they are required, includes some support for the browsable_dirs option when using an AMD format mount map, however this option only works if you manually set it in the [ amd ] section of the autofs.conf configuration file. See autofs.conf(5) and /usr/share/doc/autofs-5.0.7/README.amd-maps for more information. (Bug ID 26363401)

btrfs: Send operation causes soft lockup on large deduped file

Using btrfs send on a large deduped file results in a soft lockup or out-of-memory issue. This problem occurs because the btrfs send operation cannot handle a large deduped file containing file extents that are all pointing to one extent, as these types of file structures create tremendous pressure for the btrfs send operation.

To prevent this issue from occurring, do not use btrfs send on systems with less than 4 GB of memory. (Bug ID 25306023)

btrfs, ext4 and xfs: Kernel panic when freeze and unfreeze operations are performed in multiple threads

Freeze and unfreeze operations performed across multiple threads on any supported file system can cause the system to hang and the kernel to panic. This issue is the result of a race condition that occurs when the unfreeze operation is triggered before it is actually frozen. The resulting unlock operation attempts a write operation on a non-existent lock resulting in the kernel panic. (Bug ID 25321899)

btrfs: qgroup reserve 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 hangs on unmount after an append to a file with negative i_size

While it is invalid for a file system to load an inode with a negative i_size, it is possible to create a file like with a negative i_size and append to it. However, doing so causes an integer overflow in the routines underlying writeback, which results in the kernel locking up. (Bug ID 25565527)

ext4: hang occurs during dynamic expansion of inode size

A hang occurs with the ext4 file system during the dynamic expansion of inode size when using the inode's i_extra_size field. (Bug ID 25718971)

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: Oracle Linux 7 Update 4 is incompatible with UEK R3 where file systems are formatted using XFS with `d_type` enabled

All xfs file systems that are created with the Oracle Linux 7 Update 4 installer have d_type support enabled automatically and are formatted with the ftype=1 option. The UEK R3 kernel is incompatible with this option and does not boot on systems installed with the Oracle Linux 7 Update 4 installer, where default file system formatting is selected because the UEK R3 kernel cannot mount any xfs file system that is created using ftype=1.

Upgrades are unaffected, as previous updates of Oracle Linux 7 formatted disks use the ftype=0 option. However, when using UEK R3 on Oracle Linux 7 Update 4 and later, be aware that you must explicitly set the ftype=0 option when formatting the disk with XFS.

When performing a kickstart installation, if you intend to use UEK R3 on the system, you can manually specify alternate file system options for formatting. If you want to continue to use XFS with UEK R3, you must explicitly set the formatting option to ftype=0 in your kickstart configuration. (Bug ID 26176688)

xfs: Directory readahead completions can hang the system after unmount

Directory readahead can hang the system if the file system is unmounted suddenly after a mount. If a directory readahead is delayed for long enough, buffer I/O completion might occur after the unmount has completed. The asynchronous nature of directory readahead I/O means that when the readahead I/O completion occurs, core data structures could have been freed, causing the completion to run into invalid memory accesses., which can result in a kernel panic and system hang. (Bug ID 25550712)

xfs: System hangs on unmount after a buffered append to a file with negative i_size

While it is invalid for a file system to load an inode with a negative i_size, it is possible to create a file like this. In the case where a buffer appends to the file, an integer overflow in the routines underlying writeback result in the kernel locking up. Note that a direct append does not cause this behavior. (Bug ID 25565490)

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)

Ceph: SSL certificate verification error when accessing the Ceph Object Gateway in SSL mode

If you configured your Ceph Object Gateway service to enable SSL and you opted to use a self-signed certificate, you may encounter SSL certificate verification errors when you attempt to access the service in SSL mode.

The example Python scripts provided in the Ceph Storage for Oracle Linux Release 2.0 Release Notes and used to test the Ceph Object Gateway service, require Python libraries that have been updated in Oracle Linux 7 update 4. Libraries such as urllib2, a dependency for python-boto, have been updated to include much stricter SSL validation and verification, and may return an SSL certificate verification error when connecting over HTTPS to a service that uses a self-signed certificate.

If you choose to use a self-signed certificate, you can copy the CA certificate to the client system's certificate bundle. For example:

cat custom.crt >> /etc/pki/tls/certs/ca-bundle.crt

Alternately, use the program's environment to specify the path to additional trusted CA certificates in PEM format. The environment variables SSL_CERT_FILE and SSL_CERT_DIR can be used to specify additional trusted CA certificates. For example:

SSL_CERT_FILE=/root/ceph/custom.pem python script.py

(Bug ID 26451186)

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)

crashkernel=auto setting on UEK R3

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)

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 for this issue is to set the value of GRUB_DEFAULT in/etc/default/grub to the correct entry and then use grub2-mkconfig to regenerate the /etc/grub2/grub.cfg file. Or, use the yum command 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 4 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 3 to Oracle Linux 7 Update 4, if the /boot directory is hosted on a btrfs subvolume, the system boots to the old Oracle Linux 7 Update 3 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, as shown in this example:

sudo 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:

sudo 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 are issues that you might encounter when using InfiniBand devices.

ifup-ib: line 357: /sys/class/net/ib0/acl_enabled: Permission denied error

Running ifup ib-interface or service network restart on an Oracle Linux 7 Update 4 system reports the following error:

/etc/sysconfig/network-scripts/ifup-ib: line 357: /sys/class/net/ib0/acl_enabled: Permission denied

This error is reported, even though the InfiniBand interface is brought up successfully.

The workaround for this issue is to change from using the older configuration method, where you manipulate sysfs files to the newer ibacl tools that are provided. (Bug ID 26197105)

Kdump might fail due to an incorrect InfiniBand Adapter M3 Firmware version

Kdump might fail on Oracle Linux 7 Update 4 if the Oracle Dual Port QDR InfiniBand Adapter M3 Firmware version 2.31.5350 is installed.

To prevent this issue from occurring, update the Oracle Dual Port QDR InfiniBand Adapter M3 Firmware version to at least 2.31.5350. (Bug ID 26351183)

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

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

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 related 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 an later, 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 4 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 3 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. (Bug IDs 18712168, 18667813, 18266964)

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

If you are running UEK R4 or an earlier release on Oracle Linux 7, the hypervkvpd and hypervvssd services fail to start if the Hyper-V packages are at version 0-0.29.20160216git.el7 or later.

To avoid this issue, upgrade to UEK R4U5 or later.

(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 this issue. (Bug ID 18459498)

OpenSSH does not update login records with ssh client's host name

By default, after installing or upgrading to Oracle Linux 7 Update 4, OpenSSH does not update login records such as /var/run/utmp and other files with the ssh client's host name. This behavior is expected.

If you want to revert to the previous behavior, where login records are updated with the ssh client's host name, edit the /etc/ssh/sshd_config file and uncomment the "UseDNS yes" line. See the sshd_config(5) man page for more information. (Bug ID 26286750)

Geneve network driver support not available in UEK releases

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

net_prio control group not supported on UEK R3

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)

`NetworkManager` fails to set the default gateway and route for interfaces configured with DHCP on UEK R3

When running UEK R3 on Oracle Linux 7 update 4, NetworkManager fails to set the default gateway and route for network interfaces that are configured with DHCP. This can result in network interfaces not behaving correctly.

The workaround for this issue is to disable NetworkManager control over interfaces that are configured for DHCP.

To disable NetworkManager for an interface, edit the network script for the interface in /etc/sysconfig/network-scripts/ifcfg-dev and add the parameter NM_CONTROLLED=no, as shown in the following example:

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

(Bug ID 26268996)

`NetworkManager` unable to add IPv6 addresses to interfaces on UEK R3

After upgrading to Oracle Linux update 4, or when running UEK R3 on Oracle Linux 7 update 4, network interfaces that are configured for IPv6 might not be brought up by Network Manager.

Errors similar to the following appear in the system log:

<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, as shown in the following 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)

Cockpit web interface fails to display subscription status

The Cockpit web interface may fail to display subscription status when you click on the Subscriptions menu option. An error is returned:

Couldn't get system subscription status. Please ensure subscription-manager
is installed.

There is no subscription-manager package available. (Bug ID 26581257)

32-bit RDMA packages are installed when upgrading a system with `rdma-core` installed

When upgrading from a system where the rdma-core.noarch package is installed, 32-bit versions of the packages and many dependencies are also installed, unnecessarily. This is because the original version of the package is obsoleted and during upgrade the package is replaced with both the rdma-core.i686 and rdma-core.x86_64 versions of the package, along with those packages' dependencies.

To work around the issue, run the yum update command with the --exclude=\*.i686 option:

sudo yum update --exclude=\*.i686

(Bug ID 28217831)