Known Behavior

This section lists known limitations with this release. Bug numbers are listed and can be researched in Launchpad.net at https://bugs.launchpad.net/juniperopenstack .

  • 1628326 DPDK-based compute node may not handle ARP packets correctly if only one CPU core is assigned to the vRouter in the test bed file.

  • 1694343 In DPDK vRouter use cases such as SNAT and LBaaS that require netns, you cannot set jumbo MTU size. Maximum MTU allowed: <=1500 . There is no workaround at present.

  • 1714063 Analytics services does not support Keystone V3.

  • 1716308 When the vRouter receives the head fragment of an ICMPv6 packet, the head fragment is immediately enqueued to the assembler. The flow is created as hold flow and then trapped to the agent. If fragments corresponding to this head fragment are already in the assembler or if new fragments arrive immediately after the head fragment, the assembler releases them to flow module. Fragments get enqueued in the hold queue if agent does not write flow action by the time the assembler releases fragments to the flow module. A maximum of three fragments are enqueued in the hold queue at a time. The remaining fragments are dropped from the assembler to the flow module.

As a workaround, the head fragment is enqueued to assembler only after flow action is written by agent. If the flow is already present in non-hold state, it is immediately enqueued to assembler.

  • 1730021 In Tungsten Fabric Security, non-admin users cannot access global scope objects when global_access is set to 0.

As a workaround, for non-admin users to access global scope objects, set global_access to 5.

  • 1733027 In a multi-node analytics cluster, when one of analytics nodes shuts down or is rebooted, the contrail-status on the other analytics nodes displays the status of contrail-analytics-api and contrail-alarm-gen as initializing with the error message: Redis-UVE:<ip-address of analytics node that was shutdown/rebooted>:6381[None] connection down. This does not impact the functioning of the analytics cluster.

  • 1735057 When bringing up Tungsten Fabric cluster on Red Hat container, manually install docker-py on all the target nodes.

    • To install Pip, use the following command:

      wget https://bootstrap.pypa.io/get-pip.py python get-pip.py

    • To install docker-py, use the following command:

      pip install docker-py

  • 1749614 In a Helm-based provisioned cluster, VM launch fails if MariaDB replication is set to >1.

  • 1754742 When you receive an error message during Kolla provisioning, rerunning the code will not work. In order for the provisioning to work, restart provisioning from scratch.

  • 1755997 Kubernetes IP fabric feature is supported only on the pods and not the services.

  • 1759428 Cannot provision an external MX series router by running the provision_mx.pyscript that contains the list of external routers.

  • 1759576 Metadata SSL works only in HA deployment mode.

  • 1759695 After deleting a vRouter chart with DPDK, the NICS do not rebind to the host in Helm.

  • 1761137 High Availability provisioning of Kubernetes master is not supported.

  • 1764610 Ansible-deployer: DPDK PPS is low.

  • 1764739 Docker restart hangs indefinitely and Docker daemon stops running post the hang.

  • 1765281 On a DPDK compute vif list –ratecore-dumps with traffic.

  • 1766035 On a Kubernetes cluster, a controller node reboot fails to re-establish the BGP XMPP connection with compute nodes. As a workaround, flush the iptables on the Kubernetes master.

  • 1766315 After provisioning Tungsten Fabric by using a Helm-based provisioned cluster, restart nova-compute container.

  • 1767472 SR-IOV with DPDK co-existence deployment is not supported using contrail-helm-deployer.

  • 1781305 OpenShift deployer code does not have the option to choose different interface names for different physical nodes.

  • 1784085 OpenShift deployments do not install NTP on the nodes. After provisioning, you must install and start the ntpd on all Openshift nodes manually.

  • 1784750 Tungsten Fabric RBAC (API and analytics) policies are not part of Tungsten Fabric Helm charts unlike in OpenStack components. You cannot override global/domain/project RBAC policies while deploying Helm charts.

  • 1786487 Dynamic mirroring without Juniper header does not work for VxLAN encapsulation.

  • 1786511 rabbitmq cluster formation fails during Helm sanity job. As a workaround, update the rabbitmq section of the contrail-analytics/values.yaml and contrail-controller/values.yaml files, to include the IP addresses of the controller nodes. For example, change endpoints.rabbitmq.hosts.default: rabbitmq to endpoints.rabbitmq.hosts.default: "controller_node1_IP,controller_node2_IP,controller_node3_IP" .

  • 1786527 In Helm-based provisioning when the vRouter gets provisioned, the vRouter gets disconnected from other vRouters residing on different subnets. As a workaround, move the host routes used to reach different subnets to vhost0 interface and restart the system.

  • 1786560 In Kubernetes single yaml file-based provisioning, when the vRouter gets provisioned, the vRouter gets disconnected from other vRouters residing on different subnets. As a workaround, move the host routes used to reach different subnets to vhost0 interface and restart the system.

  • 1787303 Tungsten Fabric Release 5.0.1 uses DPDK version 17.11.03, DPDK vRouter using uio driver as vfio-pci, typically for Intel Fortville NICs, and needs firmware upgrade to the following version or later (if it is certified by users).

    driver: i40e

    version: 2.1.14-k

    firmware-version: 6.01 0x80003493 255.65535.255

  • 1789768 Instances.yml in the contrail_command container is populated with the default password instead of the one provided by the user.