3 Known Issues
WARNING:
Oracle Linux 7 is now in Extended Support. See Oracle Linux Extended Support and Oracle Open Source Support Policies for more information.
Migrate applications and data to Oracle Linux 8 or Oracle Linux 9 as soon as possible.
This chapter describes the known issues for Oracle Linux 7 Update 2.
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.
Autocompletion 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 autocompletion 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)
Ceph Block Devices
Mounting and formatting Ceph block devices is available as a technical preview with UEK R3. See the Oracle Linux: Ceph Release Notes at Oracle Linux 7 documentation. (Bug ID 20304006)
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)
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 2 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 2, 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)
Docker Fails to Start if SELinux Is Enabled
Docker 1.8.3 can fail to start if SELinux is enabled. A workaround is to disable SELinux. To
fix the issue without disabling SELinux, upgrade to
docker-engine-1.8.3-1.0.2
, which automatically pulls in
docker-engine-selinux-1.8.3-1.0.2
as a dependency. (Bug ID 22258930)
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)
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 interfaceib0
: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. It is also not possible to change the mode
of an InfiniBand interface while it is enabled.
-
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
(Bug ID 17479833)
Disabling a Switch Port Generates Warnings
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)
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 Oracle Server X5-2 System with iSCSI Storage
When installing on an Oracle Server X5-2 system with iSCSI storage, the RHCK puts the 10 Gigabit PCI Express network interface in low-power mode. Following the warm installation reboot, networking is broken, and the UEFI BIOS cannot access the boot loader on the iSCSI target. The workaround is to completely power off the system and then power it on again instead of letting it perform a warm reboot. (Bug ID 22262810)
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)
Intel QuickAssist Acceleration Technology
The UEK R3 does not support the QAT driver that allows cryptographic capabilities to be offloaded to QuickAssist hardware.
iSCSI Boot Firmware Table Incorrectly Initialized under UEK R3 on Oracle Server X5-2 Systems
For an Oracle Server X5-2 system booted using UEK R3 from iSCSI storage, the iSCSI Boot Firmware Table is not initialized with the iSCSI initiator IP address that has been configured in the UEFI BIOS. (Bug ID 22265721)
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)
multipath Messages Relating to zram
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
.
(Bug ID 20300644)
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 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)
NFS Issues
The following sections describe issues that might be encountered when using NFS.
Using NFS v4 with an lxc-oracle Container Fails
Attempting to create an lxc-oracle
container on a remote file system mounted using NFS v4 fails.
In addition, attempting to mount a remote file system using
NFS v4 from within an lxc-oracle
container
also fails. The workaround is to use NFS v3 instead. (Bug ID
16316266)
Oracle ASM Fails to Initialize with SELinux in Enforcing Mode
The oracleasm script fails if SELinux is in
Enforcing
mode. The suggested workaround is
to disable the SELInux policy module for Oracle ASM before
running oracleasm:
sudo semodule -d oracleasm sudo semodule -l | grep oracleasm
oracleasm 1.0.0 Disabled
(Bug ID 18513404)
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.
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)
systemctl Does Not Support Some Service Actions
The systemctl command supports the
disable, enable,
restart, start,
status, and stop actions
for services such as o2cb
and
oracleasm
. To perform actions such as
configure, invoke the
/etc/init.d
script for the service directly.
(Bug IDs 18527520 and 18528039)
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)
Update Fails Unless i686 Kerberos Packages Are Removed
krb5-server
and krb5-server-ldap
packages on a system.
Remove these packages before updating the system, for example:
sudo yum remove krb5-server.i686 krb5-server-ldap.i686(Bug ID 20671170)
Upgrade Issues
The following sections describe issues that might be encountered
when upgrading from Oracle Linux 6 (_latest
)
to Oracle Linux 7 Update 2.
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)
Rebooting Fails if preupg Is Not Run
If you do not run the preupgrade assistant utility
preupg, an upgraded system hangs while
rebooting with the message starting wait for plymouth
boot screen to quit
. (Bug ID 18815298)
Red Hat Compatible Kernel Is Not Removed
The old RHCK is not removed during the upgrade. (Bug ID 18767222)
Upgrade Tool Does Not Exit if UEK R3 Is Not Installed
The redhat-upgrade-tool-cli utility does not exit if UEK R3 is not installed. (Bug ID 18900135)
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)
xfs_copy Fails for Sector Size Larger than 512 Bytes
xfs_copy fails to copy a file system under UEK R3 if the device sector size is greater than 512 bytes. (Bug ID 19267663)
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)