This section provides the list of the OpenContrail issues resolutions that are automatically applied to your MCP cluster after you perform the steps described in Apply maintenance updates.
var/crashes
directory
to the OpenContrail analytics container
for the contrail-analytics-nodemgr
service to properly handle
logging of the OpenContrail monitoring, alarm, and web UI services.insecure = true
for connection
to Keystone through SSL.ifmap-server
package for OpenContrail 4.x instead of the internal
implementation of ifmap
.contrail-config-nodemgr
spawning
NodeTool.Repair
for non-existing keyspaces by removing
the keyspace repairing of the DISCOVERY_SERVER
service, which is not used
by OpenContrail starting version 4.0.contrail-api
by setting the wait_for_connect
parameter
to False
in the OpenContrail Salt formula.confluent-kafka
service that often fails
on slow environments during the OpenContrail deployment
because of connection timeouts.
The fix changes the restart
option in the confluent-kafka
service file.contrail-charts.css
from dashboard.tmpl
since it is also included
to contrail.thirdparty.unified.css
.schema-transformer
objects reinit in OpenContrail 4.1 to avoid downtime
during the contrail-schema
failover.
This fixes the issue of route targets being temporarily removed from an SNAT
routing instance during the reinit procedure.contrail-webui
service failing
to start after updating OpenContrail version 4.x
due to the missing quotation mark in /etc/contrail/config.global.js
.contrail-vrouter-agent
crashing during the
VrfEntry::DeleteTimeout()
assertion.L2 or L3
(default) and L3 only
. The
issue appeared when a VM tried to reach the floating IP of another VM through
SNAT to an external network hosting the floating IP.