6 Known Issues
This chapter contains information about known issues and limitations in this release.
Disabled virt module on Oracle Linux 8
After deploying the Kubernetes module on Oracle Linux 8, the virt
module is
disabled in the OS. We recommend that you don't enable this module again unless requested to
do so in this documentation or by Oracle Support.
Errors using overlay networking
A Kubernetes cluster that uses overlay networking, might result in an issue with the VxLAN
configuration for the cluster. Nodes that are affected by the issue contain errors similar to
the following in the dmesg
output:
[ 610.495450] bnxt_en 0000:00:03.0 ens3: hwrm req_type 0xa1 seq id 0x67 error 0xf [ 610.498246] bnxt_en 0000:00:03.0 ens3: hwrm_tunnel_dst_port_alloc failed. rc:15
This issue is commonly caused when the tx
offload
feature is enabled in the
bnxt_en
driver module. You can resolve this
issue by disabling the tx offload
feature using
the ethtool
command. For example:
sudo ethtool --offload $(ip -o -4 route show to default | awk '{print $5}') tx off
Listing environments
The Platform CLI doesn't yet have a method to display a list of the environments created.
Validating a module reports network ports aren't open
If you open network ports on nodes using the range option, the olcnectl module
validate
command can't validate the ports are open. This is because of an issue in
the firewall-cmd
command. For example, if you use a command such as the
following which opens ports using a port range:
sudo firewall-cmd --add-port=2379-2380/tcp sudo firewall-cmd --add-port=2379-2380/tcp --permanent
The olcnectl module validate
command reports that ports 2379 and 2380
aren't open.
Workaround: Open network ports individually, without specifying a port range. For example:
sudo firewall-cmd --add-port=2379/tcp sudo firewall-cmd --add-port=2379/tcp --permanent sudo firewall-cmd --add-port=2380/tcp sudo firewall-cmd --add-port=2380/tcp --permanent