Chapter 5 Known Issues
- 5.1 Installation and Upgrade Issues
-
5.2 Package Conflicts
-
5.2.1
rdma-core
andinfiniband-diags
when installingoracle-ofed-release
package -
5.2.2
dovecot-devel.i686
anddovecot-devel.x86_64
-
5.2.3
ipa-server-dns.x86_64
andfreeipa-server-dns
-
5.2.4
ipa-admintools.x86_64
andfreeipa-admintools
-
5.2.5
rear.x86_64
andrear.noarch
-
5.2.6
PackageKit.i686
andPackageKit.x86_64
-
5.2.7
sssd-common.i686
andsssd-common.x86_64
-
5.2.1
-
5.3 File System Bugs
-
5.3.1
btrfs
: Send operation causes soft lockup on large deduped file -
5.3.2
btrfs
,ext4
andxfs
: Kernel panic when freeze and unfreeze operations are performed in multiple threads -
5.3.3
btrfs
:qgroup
reserve space leaks -
5.3.4
btrfs
: Incorrect exclusive reference count after cloning file between subvolumes -
5.3.5
btrfs
: Kernel oops when unmounting during a quota rescan or disable -
5.3.6
btrfs
: Kernel oops when removing shared extents usingqgroup
accounting -
5.3.7
ext4
: System hangs on unmount after an append to a file with negativei_size
-
5.3.8
ext4
: hang occurs during dynamic expansion of inode size -
5.3.9
ext4
: System hang when processing corrupted orphaned inode list -
5.3.10
xfs
: Oracle Linux 7.4 and later incompatible with UEK R3 for file systems formatted using XFS withd_type
enabled -
5.3.11
xfs
: System hangs on unmount after a buffered append to a file with negativei_size
-
5.3.12
xfs
: System hangs duringxfs_fsr
on two-extent files with speculative preallocation
-
5.3.1
- 5.4 Automatic Bug Reporting Tool
- 5.5 The libvirtd process displays a warning on startup
- 5.6 Snapshots of KVM guests using UEFI fail and are unsupported
- 5.7 KVM guests with LSI MegaRAID SAS ISCSI controller limited to 7 virtual disks
-
5.8
crashkernel=auto
setting on UEK R3 -
5.9 Running sosreport on UEFI systems results in
grub2-plugin-errors.txt
-
5.10 grubby fatal error during kernel upgrade when
/boot
is on abtrfs
subvolume - 5.11 Hebrew LaTeX fonts
- 5.12 InfiniBand Issues
- 5.13 Intel QuickAssist Acceleration Technology
-
5.14 Database installation and operation fails if
RemoveIPC=yes
is configured forsystemd
- 5.15 Unable to create Oracle Linux 7 LXC containers on NFS
- 5.16 Support for Oracle Linux 7 guests on Oracle VM and Xen
-
5.17 Kdump to
ssh
target failed with Oracle Linux 7 PVHVM guest - 5.18 Hyper-V related services fail to start on Oracle Linux 7 guest with UEK R4 kernel under Windows Hyper-V Server
- 5.19 Geneve network driver support not available in UEK releases
-
5.20
net_prio
control group not supported on UEK R3 -
5.21
NetworkManager
fails to set the default gateway and route for interfaces configured with DHCP on UEK R3 -
5.22
NetworkManager
fails to respond to IPv6 addresses on low priority networks with DHCP on UEK R4 -
5.23
NetworkManager
unable to add IPv6 addresses to interfaces on UEK R3 - 5.24 Network connection icon reports incorrect state for interfaces
- 5.25 Power button defaults to ACPI Suspend
- 5.26 Cockpit web interface fails to display subscription status
-
5.27 32-bit RDMA packages are installed when upgrading a system with
rdma-core
installed -
5.28 Uninstalling
libpcap
can result in the removal of a large number of libvirt packages
This chapter describes the known issues for Oracle Linux 7.5.
Note that additional issues specific to the kernel that you are using might also be present. If you are using the default UEK R4U6 please see Unbreakable Enterprise Kernel: Release Notes for Unbreakable Enterprise Kernel Release 4 Update 6. If you are using an alternate UEK release or update, please refer to the appropriate release notes for this kernel version, at Unbreakable Enterprise Kernel Documentation
5.1 Installation and Upgrade Issues
The following issues that might be encountered during installation.
5.1.1 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)
5.1.2 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)
5.1.3 Installation on an Aura7 NVMe device
Installation fails if the target device is an Aura7 NVMe add in card with 2 block devices. Although the card has two independent NVMe controllers and devices, they are assigned identical WWIDs. The multipath device mapper maps the two block devices to the same WWID, resulting in a bogus multipath configuration that prevents installation.
To work around the issue, disable multipath at boot for the
installation by using the installer boot argument
nompath
. After installation, blocklist the
NVMe block devices for multipath configuration on the system
by editing /etc/multipath.conf
, or disable
device mapper multipath altogether. See Oracle® Linux 7: Administrator's Guide for
more information on configuring multipath. (Bug ID 27638939)
5.2 Package Conflicts
-
5.2.1
rdma-core
andinfiniband-diags
when installingoracle-ofed-release
package -
5.2.2
dovecot-devel.i686
anddovecot-devel.x86_64
-
5.2.3
ipa-server-dns.x86_64
andfreeipa-server-dns
-
5.2.4
ipa-admintools.x86_64
andfreeipa-admintools
-
5.2.5
rear.x86_64
andrear.noarch
-
5.2.6
PackageKit.i686
andPackageKit.x86_64
-
5.2.7
sssd-common.i686
andsssd-common.x86_64
The following are known package conflicts for packages distributed by Oracle for Oracle Linux 7 through ULN or the Oracle Linux yum server.
5.2.1 rdma-core
and infiniband-diags
when installing oracle-ofed-release
package
In this release, a conflict between the
rdma-core
and
infiniband-diags
packages exists.
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 Section 6.2, “Oracle-Supported OFED Packages” for
more information. (Bug ID 26309256)
5.2.2 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)
5.2.3 ipa-server-dns.x86_64
and
freeipa-server-dns
A conflict between the
ipa-server-dns.x86_64
package and the
freeipa-server-dns
package in the
ol7_x86_64_latest
ULN channel exists in
this release. The .x86_64
version of the
ipa-server-dns
package has been superseded
by a .noarch
package, starting with
Oracle Linux 7.3.
To avoid the conflict, exclude the
ipa-server-dns.*.x86_64
package in your yum
configuration. See Oracle® Linux: Unbreakable Linux Network User's Guide for Oracle Linux 6 and Oracle Linux 7 more information about how to
exclude packages. (Bug ID 25054687)
5.2.4 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, starting with
Oracle Linux 7.3.
To avoid the conflict, you exclude the
ipa-admintools.*.x86_64
package in your yum
configuration. See Oracle® Linux: Unbreakable Linux Network User's Guide for Oracle Linux 6 and Oracle Linux 7 for more information about
how to exclude packages. (Bug ID 25054687)
5.2.5 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, starting
with Oracle Linux 7.3.
To avoid the conflict, exclude the
rear.*.noarch
package in your yum
configuration. See Oracle® Linux: Unbreakable Linux Network User's Guide for Oracle Linux 6 and Oracle Linux 7 for more information abut how
to exclude packages. (Bug ID 25054687)
5.2.6 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_u5_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-version
.el7.i686 conflicts with file from package PackageKit-version
.el7.x86_64 file /usr/lib/python2.7/site-packages/packagekit/__init__.pyo from install of PackageKit-version
.el7.i686 conflicts with file from package PackageKit-version
.el7.x86_64 file /usr/lib/python2.7/site-packages/packagekit/backend.pyc from install of PackageKit-version
.el7.i686 conflicts with file from package PackageKit-version
.el7.x86_64 file /usr/lib/python2.7/site-packages/packagekit/backend.pyo from install of PackageKit-version
.el7.i686 conflicts with file from package PackageKit-version
.el7.x86_64 file /usr/lib/python2.7/site-packages/packagekit/enums.pyc from install of PackageKit-version
.el7.i686 conflicts with file from package PackageKit-version
.el7.x86_64 file /usr/lib/python2.7/site-packages/packagekit/enums.pyo from install of PackageKit-version
.el7.i686 conflicts with file from package PackageKit-version
.el7.x86_64 file /usr/lib/python2.7/site-packages/packagekit/filter.pyc from install of PackageKit-version
.el7.i686 conflicts with file from package PackageKit-version
.el7.x86_64 file /usr/lib/python2.7/site-packages/packagekit/filter.pyo from install of PackageKit-version
.el7.i686 conflicts with file from package PackageKit-version
.el7.x86_64 file /usr/lib/python2.7/site-packages/packagekit/misc.pyc from install of PackageKit-version
.el7.i686 conflicts with file from package PackageKit-version
.el7.x86_64 file /usr/lib/python2.7/site-packages/packagekit/misc.pyo from install of PackageKit-version
.el7.i686 conflicts with file from package PackageKit-version
.el7.x86_64 file /usr/lib/python2.7/site-packages/packagekit/package.pyc from install of PackageKit-version
.el7.i686 conflicts with file from package PackageKit-version
.el7.x86_64 file /usr/lib/python2.7/site-packages/packagekit/package.pyo from install of PackageKit-version
.el7.i686 conflicts with file from package PackageKit-version
.el7.x86_64 file /usr/lib/python2.7/site-packages/packagekit/progress.pyc from install of PackageKit-version
.el7.i686 conflicts with file from package PackageKit-version
.el7.x86_64 file /usr/lib/python2.7/site-packages/packagekit/progress.pyo from install of PackageKit-version
.el7.i686 conflicts with file from package PackageKit-version
.el7.x86_64
You may only install one of these packages on the same system
at once. To avoid the conflict, exclude the
PackageKit.i686
package in your yum
configuration. For more information about how to exclude
packages, see Oracle® Linux: Unbreakable Linux Network User's Guide for Oracle Linux 6 and Oracle Linux 7.
(Bug ID 24963661)
5.2.7 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 similar to the following:
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 any given time. To avoid the conflict, exclude the
sssd-common.i686
package in your yum
configuration. See Oracle® Linux: Unbreakable Linux Network User's Guide for Oracle Linux 6 and Oracle Linux 7 for more information about
how to exclude packages. (Bug ID 24963661)
5.3 File System Bugs
-
5.3.1
btrfs
: Send operation causes soft lockup on large deduped file -
5.3.2
btrfs
,ext4
andxfs
: Kernel panic when freeze and unfreeze operations are performed in multiple threads -
5.3.3
btrfs
:qgroup
reserve space leaks -
5.3.4
btrfs
: Incorrect exclusive reference count after cloning file between subvolumes -
5.3.5
btrfs
: Kernel oops when unmounting during a quota rescan or disable -
5.3.6
btrfs
: Kernel oops when removing shared extents usingqgroup
accounting -
5.3.7
ext4
: System hangs on unmount after an append to a file with negativei_size
-
5.3.8
ext4
: hang occurs during dynamic expansion of inode size -
5.3.9
ext4
: System hang when processing corrupted orphaned inode list -
5.3.10
xfs
: Oracle Linux 7.4 and later incompatible with UEK R3 for file systems formatted using XFS withd_type
enabled -
5.3.11
xfs
: System hangs on unmount after a buffered append to a file with negativei_size
-
5.3.12
xfs
: System hangs duringxfs_fsr
on two-extent files with speculative preallocation
The following file systems related issues pertain to Oracle Linux 7.5.
5.3.1 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 all point 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)
5.3.2 btrfs
, ext4
and
xfs
: Kernel panic when freeze and unfreeze
operations are performed in multiple threads
Freeze and unfreeze operations that are 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, which results in a kernel panic. (Bug ID 25321899)
5.3.3 btrfs
: qgroup
reserve space leaks
The way in which quota groups (qgroups
)
reserve space can result in issues with leaks. Some of these
leaks are caused by rewriting to dirty ranges, resulting in a
"pwrite64: Disk quota exceeded" error. (Bug ID 22483655)
5.3.4 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)
5.3.5 btrfs
: Kernel oops when unmounting during a quota
rescan or disable
Operations that trigger a quota rescan or those that disable the quota on a mounted file system cause a kernel oops message when attempting to unmount the file system. This issue can cause the system to hang. (Bug ID 22377928)
5.3.6 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 issue occurs when inaccurate
results are obtained during a back reference walk, due to
missing records when adding delayed references. (Bug ID
21554517)
5.3.7 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 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)
5.3.8 ext4
: hang occurs during dynamic expansion of inode
size
A hang occurs with the ext4
file system
during the dynamic expansion of an inode's size when using the
inode's i_extra_size
field. (Bug ID
25718971)
5.3.9 ext4
: System hang when processing corrupted orphaned
inode list
If the orphaned inode list is corrupted, the inode might be
processed repeatedly, which results in a system hang. For
example, if the orphaned inode list contains a reference to
the bootloader inode, ext4_iget()
, returns
a bad inode, it results in a processing loop that can hang the
system. (Bug ID 24433290)
5.3.10 xfs
: Oracle Linux 7.4 and later incompatible with UEK R3 for
file systems formatted using XFS with
d_type
enabled
All xfs
file systems that are created by
using the Oracle Linux 7.4 and later Oracle Linux 7 installers have
d_type
support enabled automatically. These
files systems are formatted with the
ftype=1
option. The UEK R3 kernel is
incompatible with this option and therefore does not boot on
systems that have been installed with the Oracle Linux 7.4 or a later
version installer. This problem occurs when the default file
system formatting is selected because the UEK R3 kernel
cannot mount any xfs
file system that is
created by specifying ftype=1
.
Note that upgrades are unaffected because previous updates of
Oracle Linux 7 formatted disks use the ftype=0
option. However, when using UEK R3 on Oracle Linux 7.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)
5.3.11 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 in this manner. 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)
5.3.12 xfs
: System hangs during xfs_fsr
on two-extent files with speculative preallocation
During an xfs_fsr
process on extents that
are generated by speculative preallocation, the code that
determines whether all of the extents fit inline miscalculates
because the di_nextents
call that is used
does not account for these extents. This results in corruption
of the in-memory inode, and ultimately the code attempts to
move memory structures using incorrectly calculated ranges.
This causes a kernel panic. (Bug ID 25333211)
5.4 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.
5.5 The libvirtd process displays a warning on startup
After upgrading from Oracle Linux 7.4, the libvirtd
process displays a warning message during startup. The message
is similar to:
libvirtd ... warning : virQEMUCapsInit:1211 : Failed to get host CPU cache info libvirtd ... warning : virLXCDriverCapsInit:85 : Failed to get host CPU cache info
This warning does not occur with a fresh install. You can safely ignore this warning. (Bug ID 27700583)
5.6 Snapshots of KVM guests using UEFI fail and are unsupported
You cannot do snapshots of KVM guests if they use UEFI. In older versions of QEMU and libvirt, the tools may allow you to create the snapshot without an error or warning, but the snapshot could be corrupted. More recent versions of these tools prevent snapshot creation with an error. For example:
virsh # snapshot-create-as OL7-seboot error: Operation not supported: internal snapshots of a VM with pflash based firmware are not supported
(Bug ID 26826800)
5.7 KVM guests with LSI MegaRAID SAS ISCSI controller limited to 7 virtual disks
An Oracle Linux 7 KVM guest using the LSI MegaRAID SAS ISCSI controller is limited to 7 virtual disks. Although KVM guests can have up to 8 ISCSI virtual disks, the LSI MegaRAID SAS controller uses the first slot for the ISCSI Initiator, leaving the 7 remaining slots for virtual disks.
The workaround for this issue is to use the
megasas
controller instead of the
lsi
controller when creating ISCSI virtual
disks. For example, change -device lsi
to
-device megasas
, as shown in highlighted text
in the following example:
# /usr/bin/qemu-system-x86_64 -machine accel=kvm -m 8192 -smp 8 \
-drive file=/path/OracleLinux-7.5-x86_64.qcow2,format=qcow2,if=none,id=disk \
-device ide-hd,bus=ide.0,unit=0,drive=disk,bootindex=0 -device lsi,id=lsi0 \
-drive file=/path/disk1.img,format=raw,if=none,id=drive_image1 \
-device scsi-hd,id=image1,drive=drive_image1,bus=lsi0.0 \
...
# /usr/bin/qemu-system-x86_64 -machine accel=kvm -m 8192 -smp 8 \
-drive file=/path/OracleLinux-7.5-x86_64.qcow2,format=qcow2,if=none,id=disk \
-device ide-hd,bus=ide.0,unit=0,drive=disk,bootindex=0 -device megasas,id=lsi0 \
-drive file=/path/disk1.img,format=raw,if=none,id=drive_image1 \
-device scsi-hd,id=image1,drive=drive_image1,bus=lsi0.0 \
...
(Bug 27681238)
5.8 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=
.
This behavior is expected for the implementation, where
NNN
M@0M@0M
implies the auto
setting. The crashkernel=auto
parameter is
not supported for Xen. (Bug ID 17616874)
5.9 Running sosreport on UEFI systems results in
grub2-plugin-errors.txt
Running the sosreport command on UEFI systems
produces a grub2-plugin-errors.txt
file with
errors. This problem occurs because the
sosreport command cannot locate the
grub.cfg
file, as UEFI systems do not use the
same GRUB plug-in as BIOS systems.
This issue also happens on UEFI systems running the UEK release. (Bug ID 26586473)
5.10 grubby fatal error during kernel upgrade 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.5, 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.4 to Oracle Linux 7.5, if
/boot
is hosted on a btrfs
subvolume, the system boots to the old Oracle Linux 7.4 kernel after the
upgrade is complete.
The workaround for this problem is to use
grub2-mkconfig to regenerate the
/etc/grub2/grub.cfg
file 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 as follows:
# grep -P "submenu|^menuentry" /boot/grub2/grub.cfg | cut -d "'" -f2
From the listing, select the kernel entry that you want 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 now running.
(Bug ID 22750169)
5.11 Hebrew LaTeX fonts
Installing the tex-fonts-hebrew
package fails
unless you first install all texlive*
packages. (Bug ID 19059949)
5.12 InfiniBand Issues
The following are issues that you might encounter when using InfiniBand devices.
5.12.1 Kdump might fail due to an incorrect InfiniBand Adapter M3 Firmware version
Kdump might fail on Oracle Linux 7.5 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)
5.12.2 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)
5.13 Intel QuickAssist Acceleration Technology
UEK R3 does not support the QAT driver that allows cryptographic capabilities to be offloaded to QuickAssist hardware.
5.14 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.5 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.5,
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)
5.15 Unable to create Oracle Linux 7 LXC containers on NFS
The creation of Oracle Linux 7 containers fails when the
root
file system
(/container
) is hosted on an NFS share. The
problem occurs because the iputils
package in
Oracle Linux 7 releases, (Updates 4 and 5) is built to use the Linux file
extended attributes [xattr(7)] security
capabilities(7)
. The NFS protocol does not support
these file capabilities, so the iputils
package might not be installed into an NFS files system. For
example, when attempting to create an Oracle Linux 7.4 container, the
installation fails while installing the
iputils
package, producing the following
error:
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.3 container.
This issue occurs on both NFSv3 and NFSv4.
Oracle Linux 6 containers are not affected. (Bug ID 25024258)
5.16 Support for 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 Release 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 Release 2. (Bug IDs 18712168, 18667813, 18266964)
5.17 Kdump to ssh
target failed with Oracle Linux 7 PVHVM guest
If Kdump is set to an ssh
target on an
Oracle Linux 7.5 PVHVM guest, running on Oracle VM Release 3.4.4, Kdump
fails to connect to the guest operating system. This issue is
caused by the kdump
service failing to start
on the Oracle Linux 7.5 guest operating system.
To workaround this issue, on the guest virtual machine, manually
start the kdump
service after the operating
system boots up using:
# kdumpctl start
(Bug ID 27654392)
5.18 Hyper-V related services fail to start on Oracle Linux 7 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)
5.19 Geneve network driver support not available in UEK releases
The ip and iproute commands included with Oracle Linux 7.5 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) .
5.20 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)
5.21 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.4 and later,
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-
and add the parameter dev
NM_CONTROLLED=no
, as
shown in the following example:
# echo "NM_CONTROLLED=no" >> /etc/sysconfig/network-scripts/ifcfg-eno4
(Bug ID 26268996)
5.22 NetworkManager
fails to respond to IPv6 addresses on
low priority networks with DHCP on UEK R4
When running UEK R4 on Oracle Linux 7.5, NetworkManager fails to send a
response to low priority networks with DHCP on UEK R4. Networks
with higher priority (link-local, IPv6
fe80:/64
routes) take priority over the low
priority networks. This behavior might result in the DHCPv6
server failing to send a response to a DHCP client on a lower
priority network, even if the network has another output device.
(Bug ID 27714775)
5.23 NetworkManager
unable to add IPv6 addresses to
interfaces on UEK R3
After upgrading to Oracle Linux 7.5, or when running UEK R3 on Oracle Linux 7.4
and later releases, network interfaces that are configured for
IPv6 might not be brought up by
NetworkManager
.
Messages similar to the following appear in the system log:
<warn> platform-linux: do-add-ip6-address[2: fe80::210:e0ff:fe5f:920c]: failure 22 (Invalid argument) <warn> 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 by using the ip addr add command.
This issue is apparent, irrespective of whether IPv6 is configured statically, assigned dynamically through DHCP, or configured by using Stateless Address Autoconfiguration (SLAAC).
The workaround for this issue is to disable
NetworkManager
for interfaces where IPv6 must
be configured for an interface. To disable
NetworkManager
for an interface, edit the
network script for the interface in
/etc/sysconfig/network-scripts/ifcfg-
and add the parameter dev
NM_CONTROLLED=no
, as
shown in the following example:
# echo "NM_CONTROLLED=no" >> /etc/sysconfig/network-scripts/ifcfg-eno4
(Bug ID 24848072)
5.24 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)
5.25 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:
# dconf update
You must log out of the desktop environment and log back in for the new setting to take effect. (Bug ID 25597898)
5.26 Cockpit web interface fails to display subscription status
The Cockpit web interface might fail to display a subscription status when you click the Subscriptions menu option. An error similar to the following is returned:
Couldn't get system subscription status. Please ensure subscription-manager is installed.
There is no subscription-manager package available. (Bug ID 26581257)
5.27 32-bit RDMA packages are installed when upgrading a system with
rdma-core
installed
When upgrading from a system prior to Oracle Linux 7.4, 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:
# yum update --exclude=\*.i686
(Bug ID 28217831)
5.28 Uninstalling libpcap
can result in the removal of a
large number of libvirt packages
The libpcap
package is updated to enable
functionality for future technologies. If you install this
package and then attempt to uninstall it, a large number of
libvirt packages may also be uninstalled due to dependency
relationships. The libvirt
package has a
dependency on the
libvirt-daemon-driver-nwfiler
package and
this package has a dependency on libpcap
.
Removing libpcap
removes the entire libvirt
family of packages. (Bug ID 28582266)