Known Issues

The following issues exist in this release of TIBCO Control Plane and capabilities.

TIBCO Control Plane

Key Summary and Workaround
PCP-5813

Summary: After upgrading from TIBCO Control Plane version 1.1.0 to version 1.2.0, Fluentbit container is missing in some pods.

Workaround: None
PCP-5708

Summary: In TIBCO Platform Console, when you try to provision a subscription and it fails in between, the cleaning up of the subscription does not happen. Although the subscription provisioning has failed, you can see the new subscription card added on UI.

Workaround: None
PCP-5657

Summary: The Observability services count on the Monitoring details page does not match with the count of essential Observability services. It counts optional services also.

Workaround: None
PCP-4315

Summary: For upgrading infrastructure components, you must have Manage Capability permission for "All current and future capabilities" in a data plane.

Workaround: None
PCP-4211

Summary: When upgrading infrastructure components, if provisioner-agent fails to upgrade, roll back to the previous helm chart version fails.

Workaround: None
PCP-3074

Summary: There is no edit option for the observability resource configured at the data plane level.

Workaround: Delete the observability resource at the data plane level and configure a new resource.
PCP-2681

Summary: If you click Apply tags next time the application is restarted, apps that need to restart to apply tags do not have any flag on the UI.

Workaround: None. You must be aware of which apps need to be restarted.
PCP-1505

Summary: When you are using the User Management or Capability provisioning wizard, and if you click a menu on the left navigation, you lose your entered data in the wizard.

Workaround: None.
PDP-2728

Summary: After upgrading from TIBCO Control Plane 1.1.0 to TIBCO Control Plane 1.2.0, traces for TIBCO BusinessWorks Container Edition and TIBCO Flogo apps deployed on a data plane registered in version 1.1.0, are not displayed.

Workaround: Perform the following steps:

  1. Unlink the Global observability resource or delete data plane level observability resource.

  2. Delete the existing observability resource and add a new observability resource.

  3. Link the new observability resource.
PDP-2464

Summary: When app is deployed in a different namespace than the namespace registered for the data plane and when cluster-scope permissions for a data plane are disabled, the app metrics are not collected.

Workaround: None
PDP-1900

Summary: Request duration card does not display data for data plane having multiple namespaces and apps are deployed in a namespace in which TIBCO services are not deployed.

Workaround: None.
PDP-1411

Summary: On the Observability page, the Global Observability Data Planes dropdown is selected by default. It shows data only from the data planes that belong to a cluster where the observability backend is configured.

Workaround: To let the data planes point to the same global observability resource across clusters, expose the Elastic search and Prometheus as an Internet or public endpoint.

TIBCO BusinessWorks Container Edition Capability

Key

Description
BWCE-7490

Summary: The existing running or stopped application fail to scale (if started or restarted or scaled or pushed updates) after upgrading the Infra and TIBCO BusinessWorks Container Edition capabilities to 1.2.0

Workaround: None.

BWCE-7436

Summary: The plug-in applications are failing for eclipse temurin base image with version 2.9.0 of TIBCO BusinessWorks Container Edition.

Workaround: Use the Debian or Amazon Linux 2 as base image for 2.9.0 with security context enabled for apps with plug-ins and supplements.

TIBCO Flogo Capability Known Issues

Key

Description

FLOGO-13296

Summary: On deploying an app in non default namesapce, it shows status as Not Found for the first time

Workaround: Not found status goes away after a few seconds.

FLOGO-13250

Summary: Getting custom extension provision related error immediately after provisioning a flogo capability.

Workaround: Watch for all Data Plane pods. Once all are in running state then proceed with opening flogo capability.

FLOGO-13233

Summary: Unable to provision more than 2 flogo versions on the platform.

Workaround: Change the Flogo build version to a different version,/select the version option, and re-select the build type to enable the next button.

FLOGO-12832

Summary: MAC & Windows executable building is not working on TIBCO® Control Plane.

Workaround: None.

FLOGO-11702

Summary: The Apps details page does not open on a single click on the UI.

Workaround: Click twice on an application name on the app list page.

FLOGO-11669

Summary: Swagger-related buttons are not hidden for non-REST API endpoints.

Workaround: None.

FLOGO-11625

Summary: If there are more than two triggers, the service name and trigger name are not present in the URL.

Workaround: None.

FLOGO-11621

Summary: For an app with multiple triggers, a basepath does not have correct trigger names.

Workaround: None

FLOGO-11514

Summary: An application that has the protobufToJSON activity does not work at runtime.

Workaround: None

FLOGO-11451

Summary: A Flogo app description is not displayed on the UI.

Workaround: None
FLOGO-11876

Summary: The JSON type response is displayed as separate lines as it is stored in separate lines in Kibana.

Workaround: None

FLOGO-11776

Summary: You cannot run an EMS SSL case with the EMS instance details on the platform after EMS provisioning as there is no option to download SSL certificates.

Workaround: None

FLOGO-11846 Summary: You can navigate into the capability pages even when the Flogo Provisioner has not started.
Workaround: None
FLOGO-11602 Summary: When opening the Flogo capability, a "503 service unavailable" error is displayed.
Workaround: None
FLOGO-11578

Summary: On deleting app builds, the app build number is not automatically updated.

Workaround: Refresh the page.

FLOGO-11524

Summary: You cannot edit an app name and description from the App details page.

Workaround: None

TIBCO Enterprise Message Service Capability

Key

Summary and Workaround

MSGDP-199

Summary: On many Amazon Elastic Kubernetes Service (EKS) clusters, the default storage class gp2 does not support the shared logs option when provisioning EMS.

If you provide a storage class, which is backed by Amazon Elastic Block Store (EBS) volumes or other single-pod storage volumes, the chart is deployed but the pods are stuck in the Pending state.

Workaround: Delete and provision the capability again without enabling log sharing.

TIBCO Developer Hub

Key

Summary and Workaround
PLTDX-1106 Summary: Login issue with GitHub on CI/CD tab on component details page and Authorization tab on settings page.

Workaround: None.
PLTDX-911 Summary: TIBCO Developer Hub provisioning is failing with - "Error while provisioning Capability: Failed to provision chart(s): [oauth2-proxy-cml558asvbptpnp3pmeg]".

Workaround: The issue is caused by the presence of the oauth2proxy chart in your data plane for the old instance of TIBCO Developer Hub capability. You need to manually uninstall this chart to proceed.

Use the following steps: 

  1. Go to your DP Cluster.

  2. Run helm ls -n <dp-namespace>.

  3. Identify the oauth-proxy chart for your TIBCO Developer Hub capability. If you have BusinessWorks Container Edition or Flogo capability installed, you have more than one oauth2proxy chart installed. Kindly ensure that you identify the right oauth2proxy chart that corresponds to your TIBCO Developer Hub instance ID.

  4. To delete the chart, run - `helm uninstall <oauth2proxy-release-name> -n <dp-namespace>`.
PLTDX-967

Summary: User is getting the following error - "could not find oauth2proxy chart details, kindly delete this instance, and create a new instance to fix this issue".

Delete the current instance and provision again using the same custom configuration file. While creating an instance, you might face the PLTDX-911 error, kindly follow its workaround to proceed.

Workaround: None.

PLTDX-690

Summary: If you try to sign out of the developer hub, you get the "403 Forbidden" error.

Workaround: None.

TIBCO Control Tower

Key

Summary and Workaround

HKCT-190

Summary: The hawk domains that you configure in Control Tower need to have different names

Workaround: None.

TIBCO® Messaging Quasar - Powered by Apache Pulsar™ Capability

Key

Description

MSGDP-531

Summary: There is a race condition between Kubernetes node scheduling and EBS CSI StorageClass volume creation when multiple pods start at the same time, the node can be overbooked resulting in one or more pods getting stuck in the Pending state with the following error:

Could not attach volume "<ID>" to node <node ID>

This issue is most commonly hit by charts such as Apache Pulsar which contain multiple StatefulSets using the parallel start method.

Workaround: For each pod stuck in the Pending state, delete the pod and wait for it to reach the Running state before restarting the next pod.

Note: In some cases, you might need to cordon the node to force the pod to restart to schedule to a new node because StatefulSet pods are node sticky.
MSGDP-532 Summary: When provisioning TIBCO Messaging Quasar capability and selecting the Log storage is shared checkbox, the StorageClass supplied volumes must support multipod and multinode volume mounting. If you provide a StorageClass name backed by AWS EBS volumes or other single pod storage volumes, the chart is deployed, but pods are stuck in the Pending state. On many AWS-EKS Kubernetes clusters, StorageClass gp2 is created as a default and it does not support the shared logs option.

Workaround: Delete the capability and re-provision it without selecting the Log storage is shared checkbox, or by supplying a multipod StorageClass such as NFS or EFS.