Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Known Behavior

 

This section lists known limitations with this release.

  • CEM-7054 In Contrail Fabric deployments, it was observed that in rare scenarios the node profile for devices cannot be accessed. If this happens, restarting the Config API container will recover from the issue.

  • CEM-6379 Restarting Schema Transformer service can cause traffic disruption in BMS connected to Fabric Leafs.

  • CEM-5441 On a freshly provisioned Contrail + Appformix cluster, to enable the live data streaming the web sockets between Contrail UI and Appformix server need to be established. In release 1907 this needs to be triggered once by login to the Appformix UI.

  • CEM-5402 Though the APIs allow 4 byte ASN, the backend code only support 2 byte ASN. Do not use 4 byte ASN in API integrations.

  • CEM-5334 The multi cloud gateway on the cloud will allow traffic from only a vRouter or Controller nodes to reach to the On-Prem cluster. So in case of deployment where the On-Prem open stack cluster need to be extended to the K8s cluster on the cloud, the k8s master must be defined in one of the vRouters on the cloud.

  • CEM-5287 Multicloud Provision may fail in add_tunnel routes, if the initial subcluster extension is rerun .If the initial subcluster extension fails user need to delete the subcluster and extend it again.

  • CEM-5284 Cloud Compute/vrouter nodes will not be listed in the cluster-nodes/compute node page, all nodes/computes will be listed in the servers page

  • CEM-5283 For all-in-one cluster, where vrouter and openstack roles exist on the same node, "enable_haproxy" must not be enabled (set to 'yes') in the ansible yaml file. This is because of multicast traffic restrictions when vrouter is running.

  • CEM-5141 For deleting compute nodes, the UI workflow will not work. Instead, update the instances.yaml with “ENABLE_DESTROY: True” and “roles:” (leave it empty) and run the following playbooks.

    For example:

  • CEM-5290 While adding AWS cloud to an already existing public cloud with Azure, the AWS credentials need to be manually added in Contrail-Command container. Perform the following steps to add AWS credentials manually.

    1. Log in to the contrail_command container.
      docker exec -it contrail_command bash
      export CONTRAIL_CONFIG=/etc/contrail/contrail.yml
    2. Get the public cloud UUID.
      contrailcli list cloud
    3. Use the following command to get the cloud_user_refs for the <public_cloud_uuid> public cloud UUID.
      contrailcli show cloud <public_cloud_uuid> | grep -A 4 cloud_user_refs
    4. Replace the UUID in the cloud_user.yaml with the <cloud_user_ref> UUID of your cluster.
      cat <<EOF > cloud_user.yaml
    5. Use the following command to sync the cloud_user.yaml file.
      contrailcli sync cloud_user.yaml
    6. Verify that the credentials are updated.
      contrailcli show cloud_user <cloud_user_ref>
    Note

    The instance name or the hostname must be in lowercase so that it is consistent across all components.

  • CEM-5282 When Azure cloud is extended to On-Prem cluster running on RHEL hosts, contrail-status shows vRouters running on Azure as initializing, though the services are up. This is due to the Red Hat issue https://access.redhat.com/solutions/2766251.

  • CEM-5043 VNI update on a LR doesnt update the RouteTable. Workaround is to delete the LogicalRouter and create a new LogicalRouter with the new VNI.

  • CEM-5042 Adding new subnet on an already provisioned VPC is not supported. If all the subnets are added during initial bringup of VPC, nodes can be added incrementally to the subnets anytime.

  • CEM-5041 Provisioning of Region or VPC objects only on the cloud without any nodes is not supported. Add atleast one node while provisioning Region/VPC.

  • CEM-5024 Current multi cloud provisioning does not enable the On-prem TOR to exchange public cloud subnets with the On-Prem controllers. The user need to add static routes on the controllers to all the public cloud subnets.

  • CEM-4943 After deleting and reprovisioning public cloud infra, though the nodes get deleted from the cloud, the API server and Kubernetes will have stale entries for the deleted objects. To clean up the stale entries, run the following housekeeping scripts:

    1. Log in to the command container.
    2. Navigate to the contrail-multi-cloud folder.
      cd /usr/share/contrail/contrail-multi-cloud/
    3. Run the following script.
      TF_STATE=/root/contrail-multi-cloud/terraform.tfstate INVENTORY=inventories/inventory.yml TOPOLOGY=/root/contrail-multi-cloud/topology.yml ./housekeeper.sh
      Note

      If you run the script after provisioning, ensure that TF_STATE is the backup file. For example:

      TF_STATE=/root/contrail-multi-cloud/terraform.tfstate.backup INVENTORY=inventories/inventory.yml TOPOLOGY=/root/contrail-multi-cloud/topology.yml ./housekeeper.sh
  • CEM-4941 The multicloud gateway on the public cloud cannot be shared across different subnets. Each subnet must have its own gateway.

  • CEM-4865 Provisioning of Contrail Controllers on public cloud is not supported. Controllers need to be provisioned On-prem.

  • CEM-4381 Contrail Fabric device manager tasks can fail if one or more Contrail API servers is down. Contrail-status on the Contrail config nodes can be used to determine if this situation occur.

  • CEM-4370 After creating a PNF Service Instance, the fields like PNF eBGP ASN*, RP IP Address, PNF Left BGP Peer ASN*, Left Service VLAN*, PNF Right BGP Peer ASN* ,Right Service VLAN* cannot be modified. If there is a need to modify these values, delete and re-create the Service Instance with intended values.

  • CEM-4190 IPtables rules are not updated on MC-GW nodes. As a workaround, you must configure IPtables on the on-premise MC-GW nodes with INPUT and FORWARD and default ACCEPT policy.

  • CEM-3959 BMS movement across TORs is not supported. To move BMS across TORs the whole VPG need to be moved. That means if there are more than one BMS associated to one VPG, and one of the BMS need to be moved, the whole VPG need to be deleted and re-configured as per the new association.

  • CEM-3324 Users cannot provision Contrail Cluster entirely in Public cloud. Contrail Cluster need to be On-Prem and vRouters can be extended to public cloud.

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

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

  • JCB-190956 While creating ironic-provision, service address in the subnet must be pointing to openstack ironic node ip/kolla internal vip.

  • JCB-187320 On a DPDK compute vif list –rate core-dumps with traffic.

  • JCB-187287 High Availability provisioning of Kubernetes master is not supported.

  • JCB-186493 When a snapshot of an active VM fails, shutdown the VM before generating the snapshot.

  • JCB-184837 After provisioning Contrail by using a Helm-based provisioned cluster, restart nova-compute container.

  • JCB-184776 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.

  • JCB-177787 In DPDK vRouter use cases such as SNAT and LBaaS that require netns, jumbo MTU cannot be set. Maximum MTU allowed: <=1500.

  • JCB-177541 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.

  • JCB-171466 Metadata SSL works only in HA deployment mode.

  • JCB-163773 A false alarm for config service is generated when config and configdb services are installed on different nodes. Ignore the false alarm.

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