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.

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)

Rebooting following installation fails if you format / and /boot as ext3 file systems. The system displays messages similar to the following before starting the emergency shell:

systemd[1]: Timed out waiting for device ...
systemd[1]: Dependency failed for /boot. 
systemd[1]: Dependency failed for Local file ...

systemd[1]: Dependency failed for Mark the need to relabel after reboot. 
systemd[1]: Dependency failed for Relabel all filesystems, if necessary. 
systemd[1]: Dependency failed for File System Check on ...

[DEPEND] Dependency failed for Local File Systems. 
[DEPEND] Dependency failed for Mark the need to relabel after reboot 
[DEPEND] Dependency failed for Relabel all filesystems, if necessary. 

The workaround is to disable SELinux during installation by specifying selinux=0 on the installation boot command line or by specifying selinux --disabled in the Kickstart file. (Bug ID 19171480)

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)

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)

The avahi-daemon fails to start with UEK R3 and messages such as the following are logged:

WARNING: No NSS support for mDNS detected, consider installing nss-mdns! 
Unit avahi-daemon.service entered failed state.

The workaround is to comment out the disallow-other-stacks entry in /etc/avahi/avahi-daemon.conf as shown here:

#disallow-other-stacks=yes

(Bug ID 18459758)

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. For Xen, crashkernel=auto is supported only for Domain 0.

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)

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)

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:

# semodule -d oracleasm
# semodule -l | grep oracleasm
oracleasm      1.0.0   Disabled

(Bug ID 18513404)

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)

The btrfs-convert command fails when invoked to convert an ext2, ext3, or ext4 file system to btrfs. This error occurs whether the system has been booted with UEK R3 or RHCK. There is currently no known workaround or fix available. (Bug ID 18534417)

The following issues may be encountered when upgrading:

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.

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

The sosreport -o selinux -a command reports many SELinux warnings for files that do not belong to RPMs. This is the expected behavior. You can safely ignore these warnings. (Bug ID 18913115)

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)

You cannot enable or disable the NFS service by using the systemctl command with nfs.service. Specify nfs-server.service instead, for example:

sudo systemctl enable nfs-server

(Bug ID 18437212)

Network teaming is not currently supported for use with UEK R3. The workaround is to use bonding instead. (Bug ID 19151770)

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)

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)

Attempting to add many attributes to a file in an XFS file system under UEK R3 can result in a kernel panic or a system reboot. (Bug ID 18504299)

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.

The following issues might be encountered with InfiniBand devices:

• You might see the following warning messages if you use the ibportstate disable command to disable a switch 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)

• To configure Internet Protocol over InfiniBand (IPoIB):

  1. Edit the /etc/sysconfig/network-scripts/ifcfg-ibN configuration file, where N is the number of the interface. The following example shows the configuration for the interface ib0:

     DEVICE=ib0
     TYPE=InfiniBand
     ONBOOT=yes 
     DHCP_HOSTNAME="myhost.mydom.com"
     BOOTPROTO=static
     IPADDR=192.168.100.1
     NETMASK=255.255.255.0
     IPV4_FAILURE_FATAL=yes
     IPV6INIT=no 
     CONNECTED_MODE=no
     NAME=ib0 

  2. Stop the NetworkManager service:

     sudo systemctl stop NetworkManager

  3. Start the RDMA service:

     sudo systemctl start rdma

  4. Bring up the interface:

     sudo ifup ibN

     (Bug ID 19150870)

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

  To change the IPoIB mode of an InfiniBand interface:

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

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

• When the rds_ib_srq parameter for the rds_rdma module is enabled and the module is in use (for example, when running the rds-stress tool), restarting the rdma service (which reloads the rds_rdma module) generates error messages visible in dmesg or /var/log/messages. (Bug ID 19010606)

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)