[Oraclevm-errata] OVMBA-2019-0051 Oracle VM 3.4 ovs-agent bug fix update

[Errata Announcements for Oracle VM]

Oracle VM Bug Fix Advisory OVMBA-2019-0051

The following updated rpms for Oracle VM 3.4 have been uploaded to the 
Unbreakable Linux Network:

x86_64:
ovs-agent-3.4.6-27.el6.x86_64.rpm


SRPMS:
http://oss.oracle.com/oraclevm/server/3.4/SRPMS-updates/ovs-agent-3.4.6-27.el6.src.rpm



Description of changes:

[3.4.6-27]
- Added a new optional configurable parameter tls1_1 in file
/etc/ovs-agent/agent.ini
Default code behavior is to enable TLSv1.1 for backward compatibility with
older Managers. It can be disabled by adding line "tls1_1=disable" as shown
below if customer wishes.
[security]
;enable ssl support in xmlrpc transport?(enable/disable)
ssl=enable
tls1_1=disable
Signed-off-by: Srinivasa Naravaram <srini.naravaram at oracle.com>
Reviewed-by: Sergei Garbuzov <sergei.garbuzov at oracle.com> [bug 30057269] 
[bug -] [bug Disabling] [bug TLSv1.1] [bug on] [bug ovs-agent] [bug 
port] [bug 8899] [bug for] [bug Oracle] [bug VM] [bug Server]

[3.4.6-26]
- Do not write the HWADDR to the ifcfg file when configuring a static IP 
on a
VLAN if the underlying device is a VXLAN
Signed-off-by: Adnan Misherfi <adnan.misherfi at oracle.com>
Reviewed-by: Sergei Garbuzov <sergei.garbuzov at oracle.com> [bug 29688921]

[3.4.6-25]
- Fixed a a conditinal that cause a unary operator error.
Signed-off-by: Adnan Misherfi <adnan.misherfi at oracle.com>
Reviewed-by: Sergei Garbuzov <sergei.garbuzov at oracle.com> [bug 29726269]

[3.4.6-24]
- Change network discovery to accommodate the VXLAN pre-fix interface 
name from vxlan to vx
Signed-off-by: Adnan Misherfi <adnan.misherfi at oracle.com>
Reviewed-by: Sergei Garbuzov <sergei.garbuzov at oracle.com> [bug 29726269]

[3.4.6-23]
- Change pre-fix of VXLAN interface name from vxlan to vx to shorten the
name especially when you have a vlan over vxlan + alias configuration.
Write DEVICETYPE directive to the vxlan config file so that the correct
ifup is called.
Bring down the interface before removing it.
Signed-off-by: Adnan Misherfi <adnan.misherfi at oracle.com>
Reviewed-by: Sergei Garbuzov <sergei.garbuzov at oracle.com> [bug 29726269]

[3.4.6-22]
- Do not write the HWADDR to the interface config file when add it to a 
bridge,
if the interface or the underlying interface is a vxlan. (e.g vlan over 
a vxlan)
Signed-off-by: Adnan Misherfi <adnan.misherfi at oracle.com>
Reviewed-by: Firas Azar <firas.azar at oracle.com> [bug 29688921]

[3.4.6-21]
- Detect CX5 cards when calculating dom0_mem. If a CX5 card is present, 
add 7GB.
Signed-off-by: Firas Azar <firas.azar at oracle.com>
Reviewed-by: Adnan Misherfi <adnan.misherfi at oracle.com>
Reviewed-by: Ke-chiang Chen <ke-chiang.chen at oracle.com> [bug 29460705]

[3.4.6-20]
- When adding an IP address to a VXLAN interface do not write the HWADDR to
the config file because the HWADDR changes every time you remove and add
the VXALN. (ifdown/ifup)
write the PHYSICAL device directive when creating a VLAN for PCA.
Preserver the PHYSICAL device directive on ip config, and bridge config.
Signed-off-by: Adnan Misherfi <adnan.misherfi at oracle.com>
Reviewed-by: Sergei Garbuzov <sergei.garbuzov at oracle.com> [bug 29541286]

[3.4.6-19]
- Get information for a VLAN device from the kernel space,
device name itself is not a right source for this kind of
information.
Signed-off-by: Sergei Garbuzov <sergei.garbuzov at oracle.com>
Reviewed-by: Adnan Misherfi <adnan.misherfi at oracle.com> [bug 29540528]

[3.4.6-18]
- The VXLAN MTU is set automatically by the system at the time of the 
VXLAN creation.
It value is equal to the MTU of the underlying interface - 50. (e.g 1500 
--> 1450, 9000-->1850).
In the case of a VLAN over a VXLAN there is a 4 bytes VLAN header that 
the kernel is not counting for,
which is causing packets fragmentation. This fragmentation is causing 
performance degradation.
TO work around this we just reduce the VXLAN MTU by four bytes.
Signed-off-by: Adnan Misherfi <adnan.misherfi at oracle.com>
Reviewed-by: Sergei Garbuzov <sergei.garbuzov at oracle.com> [bug 29443986]

[3.4.6-17]
- Keep the VXLAN directives in the interface configuration files when 
add IP to
a VXLAN interface or adding the interface to a bridge
Signed-off-by: Adnan Misherfi <adnan.misherfi at oracle.com>
Reviewed-by: Firas Azar <firas.azar at oracle.com> [bug 29444043]

[3.4.6-16]
- Allocate at least 16 GB in dom0 to accomodate CX-5 card memory 
requirements.
Signed-off-by: Firas Azar <firas.azar at oracle.com>
Reviewed-by: Ke-Chiang Chen <ke-chiang.chen at oracle.com>
Reviewed-by: Adnan Misherfi <adnan.misherfi at oracle.com> [bug 29460705]

[3.4.6-15]
- Remove mtu configuration from vxlan config script, it is not needed at 
this point.
Signed-off-by: Adnan Misherfi <adnan.misherfi at oracle.com>
Reviewed-by: Firas Azar <firas.azar at oracle.com> [bug 29357301]

[3.4.6-14]
- Do not allow the removal of a bond or a vlan if they have upper interfaces
configured on them.
Signed-off-by: Adnan Misherfi <adnan.misherfi at oracle.com>
Reviewed-by: Sergei Garbuzov <sergei.garbuzov at oracle.com> [bug 29343890]

[3.4.6-13]
- Get VID information for a VLAN device from the kernel space.
VID as a suffix for the name of VLAN device is not a must rule.
Signed-off-by: Sergei Garbuzov <sergei.garbuzov at oracle.com>
Reviewed-by: Adnan Misherfi <adnan.misherfi at oracle.com> [bug 29325411]

[3.4.6-12]
- Added XMLRPC command (ovs_pcavlan_config) that add/removes a VLAN with 
a given name and mtu size
Fixed ovs-ip-config to preserve VID, MTU and name when assigning IP 
address to this type of VLAN.
Signed-off-by: Adnan Misherfi <adnan.misherfi at oracle.com>
Reviewed-by: Sergei Garbuzov (sergei.garbuzov at oracle.com) [bug 29261184]

[3.4.6-11]
- Added a parameter to ovs_vxlan_config to pass a ttl value (0-255), 
this parameter is
optional, if you do not pass it, 32 will be use as a default. ttl is also
preserved across reboots and network restart.
Signed-off-by: Adnan Misherfi <adnan.misherfi at oracle.com>
Reviewed-by: Zhigang Wang <zhigang.x.wang at oracle.com> [bug 29274033]