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.

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)

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)

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)

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)

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)

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

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)

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)

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)

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)

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)

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)

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)

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)

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)

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)

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)

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)

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)

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)

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)

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)

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)

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)

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)

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)

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)

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)

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)

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

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.

(Bug ID 17479833)