Known Issues
The following issues exist in this release of TIBCO Control Plane and capabilities.
TIBCO Control Plane
| Key | Summary and Workaround |
|---|---|
| PCP-12292 |
Summary: After upgrading to version 1.7.0, for data planes with version 1.5.1, TIBCO BusinessWorks Container Edition and TIBCO Flogo app list does not get displayed. Workaround: Upgrade data plane and capability to the latest version. |
| PCP-11787 |
Summary: After upgrading to version 1.7.0, for Observability cards from TIBCO Control Plane 1.6.0 and earlier versions, if you select a time range that do not have data, still the main card returns data. Workaround: None |
| PCP-10859 |
Summary: On TIBCO Operated Control Plane, after deleting data plane level observability resource and then deleting corresponding query service or exporter, the following error is displayed on UI:
Workaround: None |
| 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-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-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 the latest version. |
| 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, the 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-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 Platform CLI
| Key | Summary and Workaround |
|---|---|
| PLTDX-1957 |
Summary: When you uninstall CLI, client folder files are not deleted. You cannot delete then manually also. Workaround: Restart the system. After system restart, you can delete those files manually. |
TIBCO BusinessWorks Container Edition Capability
|
Key |
Description |
|---|---|
| BWCE-9715 |
Summary: To export the supplement we have to double-click on the Kebab Menu instead of a single click. Workaround: None. |
| BWCE-9714 |
Summary: On clicking the delete option in the supplement action, all the delete windows for other uploaded supplement open as well. Workaround: None. |
| BWCE-9712 |
Summary: For the capability 1.9.0, export supplement option should not be visible on the UI because the backend API is not available in the BWCE capability 1.9.0. Workaround: The supplement option should work on upgrading the capability to 1.9.0. |
| BWCE-9694 |
Summary: Error message should be correct on passing invalid connector id in export supplement API. Workaround: None. |
| PCP-12552 |
Summary: Monitor agent should not auto discover Simple K8 deployment apps. Workaround: None. |
| PCP-12255 |
Summary: When an auto-discovered app is scaled from 0 to 1 instance, app status is seen as a failure on UI instead of Scaling. Workaround: None. |
| PCP-12276 |
Summary: When a platform app is deployed in namespace which is registered or used for auto-discovery, app status is seen as "App not present in DP". Workaround: Deploy the platform app in any other namespace which is not used for auto-discovery. |
| BWCE-9413 |
Summary:Commands requiring arguments do not work in the interactive mode. Workaround:Use the non-interactive mode for running commands that require arguments. |
| BWCE-8566 |
Summary: An incorrect TIBCO Business Studio for BusinessWork version is shown on authorization window during devhub-studio integration. 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 ActiveMatrix BusinessWorks™ 5 and TIBCO ActiveMatrix® Adapters
|
Key |
Description |
|---|---|
| BW-20928 |
Summary: If the user selects the filter for "State" of service instances in an application; and later on refreshes the page an error is thrown and user is redirected to Configuration page. Workaround: None. |
| BW-20926 |
Summary: User is able to start/stop service instances from Services screen of applications deployed in a domain which belongs to versions TRA 5.12.4/5.13.0/5.13.0 HF1. This is not an expected behavior and will be corrected in future releases. Workaround: None. |
| BW-20867 |
Summary: When an application has multiple service instances and user makes a configuration update on one of them; a redeploy attempt will show all the services need redeployment which is false. Workaround: None. |
| BW-20818 |
Summary: When user tries to undeploy an application; the undeploy window "Deployability" column is seen as empty and "Remote task to perform" shows "Deploy Engine on Client" instead of "Undeploy". Workaround: None. |
| BW-20817 |
Summary: Deployment Status filter option under Applications page does not allow the user to change a selected value. Workaround: Refresh the page so that the selection reverts and the page shows all the applications without any filter for deployment status. |
| BW-20763 |
Summary: Uptime for TIBCO Administrator service instance is not updated under Services view. Workaround: None. |
| BW-20868 |
Summary: Filter for domain name does not work properly. Workaround: None. |
| BW-20878 |
Summary: Engine control values are not applied appropriately when service instance is stopped from CP. Also, UI values are not appropriately retained. Workaround: None. |
| BW-20897 |
Summary: Once user makes a change in the Server settings tab on service instance level and redeploys the app; it still shows the status as "Deployable,containers require deployment". Workaround: None. |
| BW-20894 |
Summary: Not able to see the monitoring data for the adapter services for LDAP adapter from Control Plane UI. Workaround: None. |
| BW-20866 |
Summary: On the Application Process Archive page, clicking the breadcrumb application name redirects to the Configuration tab instead of the Services tab. Workaround: None. |
| BW-20838 |
Summary: Users cannot sort their service instances based on application name in "Services" page which lists all service instances. Workaround: None. |
| BW-20765 |
Summary: Pagination for service instances screen is not following a set number of entries per page. Workaround: None. |
| BW-20693 |
Summary: Users cannot deploy/undeploy multiple applications at a time. Workaround: None. |
| BW-20923 |
Summary: On CP, BE applications are also shown under BW5 product card in Control Tower Data Plane. Workaround: None. |
TIBCO Flogo Capability
|
Key |
Summary and Workaround |
|---|---|
| FLOGO-15877 |
Summary: A version mismatch appears for custom image apps when you use an older Flogo binary to build the Docker image. The Flogo version shown in runtime logs, application information, YAML editor, and Workaround: None. |
| FLOGO-15407 |
Summary: App deployment fails if the application name contains only digits. Workaround: Rename the app so that it does not start with a digit and follows the application name validation rules. |
| 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-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-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-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. |
TIBCO Enterprise Message Service Capability
|
Key |
Summary and Workaround |
|---|---|
| MSGDP-1381 |
Summary: The previous versions of the EMS Capability User Interface incorrectly tag the file for browser caching purposes. If you do not see new features or encounter an application error, you might be using an old version. Workaround: Clear your browser cache and refresh the current page. Alternatively, you can use a private browsing mode. |
| MSGDP-1163 |
Summary: When connectivity to the activation license server is lost and the server pod is restarted, the EMS server fails to obtain a license from the local cache. Workaround: Restore connectivity to the activation server. The EMS server keeps retrying, and service resumes when connectivity is restored. |
| 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. |
Control Tower 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 Developer Hub
|
Key |
Summary and Workaround |
|---|---|
| PLTDX-1694 |
Summary: User information is not populated in template by using the correct syntax, for example: Workaround: None |
| 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. |