Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation  Back up to About Overview 

No index entries found.

Known Issues

This section lists known limitations with this release. Bug numbers are listed and can be researched in at​ .

Contrail Networking:

  • 1462990 When a TOR agent switchover occurs on the Contrail controller, the OVS controller address changes to the TSN. In this scenario, there is a delay of up to two minutes between the OVS being updated in the QFX Series switch and the first multicast packet reaching the TSN node.
  • 1404846 In Juno, VPC VM launch is failing VPC API is not supported with Juno. Its planned to be supported in subsequent release.
  • 1464606 Vtep-ctl is only able to list 7 MAC addresses. The TOR agent is learning fewer MAC addresses than are actually present.
  • 1465744 Contrail/MX interop when a VM is using SNAT to reach a bare metal server floating IP address. This happens only in cases where a SNAT instance and destination Floating IP address are on the same compute node.
  • 1466777 There is a need to improve api-server and schema initialization times in a scaled setup. On highly scaled setups it takes up to 40 minutes for an API server and schema transformer to converge.
  • 1466731 A QFX Series switch does not handle transient duplicate VxLAN IDs for two different VNs. If a VN is deleted and added quickly the TOR switch may go in to a bad state.
  • 1468685 Centos6.5 icehouse - single node setup config processes are killed after a node reboot. A single node Centos installation runs into an API server exception.
  • 1469366 In a Device Manager setup which has an MX Series router configured for a virtual network, if the MX Series router is down and then comes back up, the latest configuration is not pushed.
  • 1475028 One Contrail controller can get stuck initializing for about 5 minutes. When this happens, another controller is initialized and the first one moves to a backup role.
  • 1477371 If a VMI contains an underscore '_' in its name, you receive an error when you select Monitor >Infrastructure >Virtual Routers.
  • 1484600 When a device is moved from one QFX Series switch to another Series switch, the MAC address is not learned on the switch for a period up to 12 minutes.
  • 1486387 If you configure compute and config services in the same node, you must use the fab setup_nova_aggregate command after the node is rebooted. If the command is not used, setup_nova_aggregate will never get executed.
  • 1491202 The TSN stops replicating broadcast packets after broadcast packets with a payload of 1400 bytes are sent.
  • 1491791 When the mcast_controller gets switched as part of a control node switchover there is 6 seconds of multicast traffic loss.
  • 1451701 If you try to create a port using the Neutron API on a subnet with a specified IP address that is outside the subnet allocation pools, the API call fails.
  • 1493861 When clearing the setup used for inter-VN communication, the compute node might crash.
  • 1414850 Interfaces created for logical routers and other constructs that are not on vRouters, do not get accounted for in the dashboard.
  • 1403348 If you attach and then detach a security group, the transparent firewall service interface does not have an internal security group.
  • 1447401 On multiple VMs in a Docker cluster, they invariably end up on one compute only.
  • 1454813 Setup of a vCenter fails if the same dv_port or dv_switch name is part of multiple data centers.
  • 1455944 When creating nova instances in Docker containers, the user-data script is not executed.
  • 1457854 If you try to create an analyzer VM with contrail_flavor_small configured, the VM is not created but multiple instances are respawned and all are in an error state.
  • 1458794 DNS configuration in Docker container is wrong. A Docker instance does not learn the DNS address provided by the vVrouter.
  • 1459505 An xmpp peer is not deleted until the replicated routes are gone.
  • 1460241 If you create twelve virtual routers attached to a single logical router and then clear the router, Neutron experiences an error.
  • 1461791 When servers in a cluster are reimaged with an ESX ISO image, only one server is successfully reimaged, all other servers in that cluster will be re-imaging in a loop.
  • 1463622 If you create multiple compute nodes and multiple virtual machines, return traffic from server to client converges on a single label. Eventually, all the flows converge on one VM on each compute node.
  • 1463786 If you create thousands of logical interfaces and thousands of virtual machine interfaces, deleting all the interfaces using the Web user interface might result in the Too many pending updates to RabbitMQ: 4096 error.
  • 1465372 If a bare metal server and a SNAT instance are attached to a public network and a packet is sent from the network namespace (netns) instance to the bare metal server, it gets Layer 3 lookups rather than a bridge table lookup.
  • 1467028 In a three-node Vcenter setup, restarting the plugin service might take up to two minutes for the other node to detect and establish mastership.
  • 1467031 A TSN drops ARP packets coming from a backup LBaaS network namespace with the invalid multicast source error. As a result, the backup LBaaS network namespace instance continuously sends ARP requests for each of the bare metal server IP addresses that have been configured as members of the load-balance pool.
  • 1468420 If you create thousands of virtual machine interfaces and logical interfaces with a thousand virtual networks, and then push the configuration using the device manager, the configuration might get repeatedly added and deleted on the MX Series router.
  • 1468474 TOR Agent Switchover: BUM/ARP traffic loss. Currently a control node does not implement the graceful restart feature, so MAC routes are immediately withdrawn on the TOR agent during switchover leading to traffic loss.
  • 1468886 Sometimes it takes more than half an hour for cmon to bring up mysql during node failure scenarios.
  • 1469296 When an MX Series router is providing NAT service for a bare metal server using floating IP addresses and the bare metal server belongs to overlapping subnets, their respective NAT configurations will collide in the NAT pool section of the config and get rejected.
  • 1469312 When HAProxy is stopped on a virtual IP node, one out of three glance requests fail.
  • 1399812 The OpenStack high availability control node reboot hangs if the Network File System mount point is unavailable during boot.
  • 1441810 After rebooting a compute node, sometimes the nova-compute is started before the virtualization API (libvirt) is initialized. Therefore it fails to come up.
  • 1480050 If you assign the same FIP address to two virtual machines, only the VM with an active VRRP address should get the FIP traffic.
  • 1489610 If two DNS servers are configured and one is down, the DNS request should only be sent to the server that is up.
  • 1490788 When a ToR-Agent’s status is busy, it can not reply to HAProxy keepalive messages.
  • 1492979 Broadcast routes are always programmed with the EVPN as the next hop. So even if there is no MX Series router to flood the traffic, it is still programmed in the composite next hop.

    The Vrouter replicates the traffic for the EVPN next hop and eventually the traffic is discarded. This causes the drop statistics count to increase.

  • 1469341 The Vcenter setup does not use the svc-monitor. The contrail-svc-monitor status needs to be removed from the contrail-status command output.
  • 1493687 Fragment packets with partial TCP headers get dropped but the flow still gets created and the next fragment gets forwarded to the receiver.

    When a packet fragment has a full TCP header and the next fragments offset is 1, then the Vrouter forwards this fragment.

    When a fragment packet head is received after 3 or more fragments, it sometime leads to fragment loss.

Modified: 2015-09-15