Known Issues
The following issues exist in this release of TIBCO Control Plane and capabilities.
TIBCO Control Plane
Key | Summary and Workaround |
---|---|
PCP-10935 |
Summary: Some app statuses are not getting displayed in TIBCO Control Plane Home page Global Assets list. Workaround: Restart the apps. After restart, the statuses get displayed. |
PCP-10221 |
Summary: When upgrading a control tower data plane, if you click the Upgrade button on UI, an error message is displayed: Workaround: Refresh the page few times so that upgrade commands get displayed on UI. |
PCP-9489 |
Summary: After upgrading from an earlier TIBCO Control Plane version to the latest version, if you are already signed in to TIBCO Control Plane, upgrading infrastructure components fails. Workaround: Sign out and sign in again to TIBCO Control Plane. |
PCP-9484 |
Summary: Consider the following scenario:
Workaround: None |
PCP-9344 |
Summary: After upgrading to TIBCO Control Plane from an earlier version, if only infrastructure components are upgraded and capabilities are not upgraded, the following compatibility issues occur for existing apps:
Workaround: After upgrading infrastructure components, upgrade the capabilities to version 1.5.0. |
PCP-8083 |
Summary: When provisioning a subscription, if you have selected the Configure Corporate IdP option and not yet configured a Corporate IdP for that subscription, the owner gets an email with only the sign-in link. There is no account activation link. Hence the newly added user is unable to activate the account and sign in with the default IdP. Workaround: The TIBCO Platform Console Admin must configure Corporate IdP for the subscription to enable newly added users to sign in. |
PCP-7415 |
Summary: After upgrading TIBCO BusinessWorks Container Edition capability and enabling BWCE monitoring service, BWCE monitoring service is not displayed on the monitoring details page. Workaround: None |
PCP-7204 |
Summary: After upgrading to TIBCO Control Plane, if observability components are not yet upgraded, Global configuration page does not show linked data planes which uses global configuration resource. Workaround: Navigate to the Observability tab of the Data Plane configuration and return back to the Observability dashboard. |
PCP-7182 |
Summary: Delete button is not enabled for connected domains in Control Tower data plane. Workaround: None |
PCP-7178 |
Summary: After upgrading to TIBCO Control Plane, if observability components are not yet upgraded, Observability dashboard display message as "No results found". Workaround: Navigate to the Observability tab of the Data Plane configuration and return back to the Observability dashboard. |
PCP-6861 |
Summary: Observability services of TIBCO Control Plane do not support outbound proxy to communicate with the backend servers such as ElasticSearch and Prometheus that are configured with the outbound proxy. Workaround: None |
PCP-4211 |
Summary: When upgrading infrastructure components, if Workaround: None |
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-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-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-8566 |
Summary: An incorrect TIBCO Business Studio for BusinessWork version is shown on authorization window during devhub-studio integration. Workaround: None. |
BWCE-8561 |
Summary: An Application fails to start on platform if we use 'Custom Profile' which does not include system properties. Workaround: None. |
BWCE-8521 |
Summary: If the TIBCO BusinessWorks Container Edition capability is not upgraded to the latest version with the Infra, then TIBCO BusinessWorks Container Edition capability runs into some issues. Workaround: Ensure TIBCO BusinessWorks Container Edition capability is upgraded to the latest version after infra is upgraded to latest version. |
BWCE-8354 |
Summary: TIBCO Business Studio for BusinessWorks does not support control plane or data plane with custom certificates. Workaround: To connect TIBCO Business Studio for BusinessWorks with Developer Hub from environments having custom certificate, perform the below steps to register the custom or self signed certificate in TIBCO Business Studio for BusinessWorks:
|
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
Key |
Summary and Workaround |
---|---|
FLOGO-14869 |
Summary: App deployment fails for applications created with connectors that require supplements when the app build .zip file is exported using the Maven plug-in. Workaround: None. |
FLOGO-14448 |
Summary: If a custom Swagger endpoint is set for a Flogo REST trigger app in the Engine variables on the TIBCO Platform, the default Swagger endpoint is not working. Workaround: To access the Swagger endpoint for an app with a custom Swagger endpoint, manually update the endpoint URL in the Swagger editor with the custom endpoint value. For example: If the default Swagger endpoint URL is: |
FLOGO-13960 | Summary: Only the latest version of the TIBCO Flogo® Extension for Visual Studio Code is available for download in the TIBCO® Control Plane's Download section. Previous versions of the extension are not provided. Workaround: Contact TIBCO Support if you need access to previous versions of the TIBCO Flogo® Extension for Visual Studio Code. |
FLOGO-13296 |
Summary: On deploying an app in non default namespace, it shows status as Not Found for the first time Workaround: The Not Found status goes away after a few seconds. |
FLOGO-13250 |
Summary: Getting a custom extension provision related error immediately after provisioning a Flogo capability. Workaround: Watch for all Data Plane pods. Once all are in a running state then proceed with opening flogo capability. |
FLOGO-13233 |
Summary: Unable to provision more than two 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-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-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. |
TIBCO ActiveMatrix BusinessWorks™ 6
Key |
Description |
---|---|
AMBW-52027 | Summary: On the Application level 2 page, in the Execution History section, the 'Select filter' for the specified time range fails to function correctly. Workaround: None. |
TIBCO Enterprise Message Service Capability
Key |
Summary and Workaround |
---|---|
MSGDP-1041 |
Summary: When registering an EMS server with explicit monitor MTLS enabled, metrics are not collected. Workaround: In the |
MSGDP-1013 |
Summary: During bulk registration of large numbers of servers health goes to red temporarily on UI. Workaround: None. |
MSGDP-1000 |
Summary: Enabling Workaround: None. |
MSGDP-976 |
Summary: Currently in a BMDP registration, a user can successfully register a server group without supplying all the required hostports, causing issues in GEMS dashboard. Workaround: Delete the server, and reregister with the full list of ClientURLs and MonitorURLs. |
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. |
Bare-Metal Data Plane
Key |
Summary and Workaround |
---|---|
HKCT-190 |
Summary: The Domains registered from the Control Plane UI should match the already created domains using Domain Utility to view the connected product specific applications. Workaround: None. |
TIBCO BusinessEvents® Enterprise Edition
Key |
Description |
---|---|
BE-33480 |
Summary: The application with the same name deployed in the same domain but in different clusters are still visible on UI after it is been removed from Admin. Workaround: None. |
TIBCO® Messaging Quasar - Powered by Apache Pulsar™ Capability
Key |
Description |
---|---|
MSGDP-667 |
Summary: The Admin CLI is a new feature in Control Plane 1.3.0, attempting to use it with a pre-upgrade 1.2.0 capability instance results in a cryptic error message. Workaround: Upgrade the capability to Control Plane 1.3.0 version before attempting to use this feature. |
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. |
TIBCO Developer Hub
Key |
Summary and Workaround |
---|---|
PLTDX-1459 | Summary: When the Control Plane and Data Plane are deployed using the same Kubernetes cluster and using traefik as ingress controller and the host-name used for the control plane and TIBCO Developer Hub are same, you get a 404 response code from the Control plane while accessing TIBCO Developer Hub. Workaround: In this case, the ingress configured for the Control Plane namespace is taking priority over the TIBCO Developer Hub ingress. Use different hostnames for Control Plane and TIBCO Developer Hub. FQDN of the Control Plane and the TIBCO Developer Hub should not overlap. For example, it should not have |
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 Use the following steps:
|
PLTDX-967 |
Summary: User is getting the following error - "could not find 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. |