Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Known Behavior

 

This section contains the known behavior and limitations for the specified Contrail Cloud Release.

Known Behaviors for Contrail Cloud Release 13.4

This section contains known behaviors and limitations in Contrail Cloud Release 13.4.

  • The following capabilities available in Contrail Networking Release 1912.L2 are not supported in Contrail Cloud 13.4:

  • Contrail Cloud 13.4 is released with a Red Hat content sync of 18 May 2020. Resolutions for the following security advisories are not yet available with Contrail Cloud 13.4:

  • CC-473 - Live migration of VMs is broken and is a known issue in OpenStack Queens. The error was reproduced in a lab environment and was tested with kernel compute to kernel compute, and DPDK compute to DPDK compute. The lab testing produced the error shown below:

    For more information, see: Red Hat Bugzilla - Bug 1196242, and Launchpad Nova Bug 1289064.

  • CC-509 - Open vSwitch (OvS) update on control host nodes causes the network connectivity to break. This issue happens during post-deployment activities of the manual yum update and reboot of the control host.

    A workaround for this issue is to temporarily switch the bridge used for the control plane/provisioning network to Linux bridge. See the procedure below for the workaround.

    On the Control Host node:

    1. Create a backup copy of the devices used in the Control/Provisioning communication: both bridge and bridge interface.

    2. Apply the following changes:

      1. For the bridged interface you will comment out DEVICETYPE, TYPE, and OVS_BRIDGE. Then you will add TYPE=Ethernet.

      2. For the bridge comment out DEVICETYPE and TYPE. Then you will add TYPE=Bridge.

    3. Use tmux, screen, or nohup to separate command execution from ssh connection status.

      The commands below will use nohup to remove OvS bridge and apply the new Linux bridge configuration that was completed in the previous step:

    4. Check interfaces status (interfaces should be visible as per Linux bridge configuration).

    5. Perform the yum update.

    6. Restore the backup that were prepared in the first step.

    7. Perform a reboot to reload the kernel and OvS configuration.

Known Behaviors for Contrail Cloud Release 13.3

This section contains known behaviors and limitations in Contrail Cloud Release 13.3.

  • The following capabilities available in Contrail Networking Release 1912.L1 are not supported in Contrail Cloud 13.3:

    • Contrail Fabric Management.

    • Public cloud deployment and connectivity.

    • Using Contrail Command for Contrail Cloud deployment.

      • Command UI is supported for Contrail Cloud 13.3 Release, but the deployment capability is not compatible with Contrail Cloud deployment.

    • TLS certificate management using IDM for Contrail Services.

  • Contrail Cloud 13.3 is released with a Red Hat content sync of 25 Feb 2020. Resolutions for the following security advisories are not yet available with Contrail Cloud 13.3:

  • CC-473 - Live migration of VMs is broken and is a known issue in OpenStack Queens. The error was reproduced in a lab environment and was tested with kernel compute to kernel compute, and DPDK compute to DPDK compute. The lab testing produced the error shown below:

    For more information, see: Red Hat Bugzilla - Bug 1196242, and Launchpad Nova Bug 1289064.

  • CC-509 - Open vSwitch (OvS) update on control host nodes causes the network connectivity to break. This issue happens during post-deployment activities of the manual yum update and reboot of the control host.

    A workaround for this issue is to temporarily switch the bridge used for the control plane/provisioning network to Linux bridge. See the procedure below for the workaround.

    On the Control Host node:

    1. Create a backup copy of the devices used in the Control/Provisioning communication: both bridge and bridge interface.

    2. Apply the following changes:

      1. For the bridged interface you will comment out DEVICETYPE, TYPE, and OVS_BRIDGE. Then you will add TYPE=Ethernet.

      2. For the bridge comment out DEVICETYPE and TYPE. Then you will add TYPE=Bridge.

    3. Use tmux, screen, or nohup to separate command execution from ssh connection status.

      The commands below will use nohup to remove OvS bridge and apply the new Linux bridge configuration that was completed in the previous step:

    4. Check interfaces status (interfaces should be visible as per Linux bridge configuration).

    5. Perform the yum update.

    6. Restore the backup that were prepared in the first step.

    7. Perform a reboot to reload the kernel and OvS configuration.

  • CC-514 - This issue is seen when updating a non-HA topology from CC13.2 or CC13.2.1 to CC13.3. Previous releases assumed fencing was enabled even when HA was not part of the topology. See below for an example of the error output:

    Use the CLI input below as a workaround for non-HA updates from CC13.2/CC13.2.1 to CC13.3:

Known Behaviors for Contrail Cloud Release 13.2

This section contains known behaviors and limitations in Contrail Cloud Release 13.2.

  • The following capabilities available in Contrail Networking Release 1910 are not supported in Contrail Cloud 13.2:

    • Contrail Fabric Management.

    • Public Cloud.

    • Contrail Command Deployment–only the UI is supported for Contrail Cloud 13.2 release.

    • TLS certificate management using IDM for Contrail Services.

  • Contrail Cloud 13.2 is released with a Red Hat content sync of 1 Oct 2019. Resolutions for the following security advisories are not yet available with Contrail Cloud 13.2:

  • The deployment of Contrail Command requires connectivity to an external package repository outside of the Contrail Cloud Satellite.

  • Setting Linux bridges with DHCP causes race conditions with the underlying bridge interfaces.

  • Ceph Pools PGs and replica sets are not updated. After Ceph changes (new OSDs or change in the replicas) TripleO will not make adjustments. These changes must be manually applied post-deployment.

  • ceph-osd fsid mismatch on redeployed environment due to use of legacy filestore.

    • Cleaning done by Ironic during openstack-deploy-cleanup does not bring osd disk to a usable state.

    • Legacy filestore should not be used. BlueStore with LVM is the recommended approach.

    • For more information, see: Ceph Issue #22354 and Red Hat Bugzilla #1590526.

  • Exception is raised when rabbitmq-client tries to delete a queue for which parameters have changed. The following might display when you run contrail-status on the Control nodes:

    • Identify the stuck queues by locating which one <queue_name> has a large number of messages. To generate the list:

      Purge each problematic queue by running:

      Verify the problem has been fixed by running contrail-status on the Control node.

      It might be necessary to restart the RabbitMQ container to fix the issue. To restart the RabbitMQ container:

Known Behaviors for Contrail Cloud Release 13.1

This section contains known behaviors and limitations in Contrail Cloud Release 13.1.

  • The following capabilities available in Contrail Networking Release 1908 are not supported in Contrail Cloud 13.1:

    • Contrail Fabric Management.

    • Public Cloud.

    • Contrail Command Deployment–only the UI is supported for Contrail Cloud 13.1 release.

    • TLS certificate management using IDM for Contrail Services.

  • Contrail Cloud 13.1 is released with a Red Hat content sync of 5-August-2019. The following security advisories were introduced after this date and not included in Contrail Cloud 13.1:

  • Linux bridges can only be configured with static IP.

  • ceph-osd fsid mismatch on redeployed environment.

    • Cleaning done by Ironic during openstack-deploy-cleanup does not bring osd disk to a usable state.

    • BlueStore with LVM is the preferred approach.

    • For more information, see: Ceph Issue #22354 and Red Hat Bugzilla #1590526.

  • Ceph Pools PGs and replica sets are not updated. After Ceph changes (new OSDs or change in the replicas) TripleO will not make adjustments. These changes must be manually applied post-deployment.

  • Running the overcloud-validation.sh script will create objects that are not subsequently cleaned up after the test completes. You must manually remove any remaining objects after the overcloud-validation script completes.

Known Behaviors for Contrail Cloud Release 13.0.2

This section contains known behaviors and limitations in Contrail Cloud Release 13.0.2.

  • Only the first element of the global.ntp list in config/site.yml is used when setting up NTP synchronization in the infrastructure. This entry must be reachable and a fully functional NTP server. The full list is utilized in the overcloud.

  • The samples/site.yml incorrectly shows the overcloud.registry. This should be commented in the deployment config/site.yml.

Known Behaviors for Contrail Cloud Release 13.0

This section contains known behaviors and limitations in Contrail Cloud Release 13.0.

  • Object storage for Ceph—Rados Gateway is not functional when ceph.support is set to enabled.

  • Contrail Cloud Release 13 configures only endpoint TLS encryption but not internal Contrail TLS.