Released hotfixes for WorkZone 2024.4

264100 - Timeouts in database connections

This hotfix solves an issue with timeouts on Network Address Translation (NAT) environments. Timeouts ocurred between AKS and Oracle after 2 minutes due to a NAT in between, which cut the connection between pods and the database due to timeouts on inactive connections.

With this container release, we introduce the "ENABLE=BROKEN" parameter, which ensures that NATs do not cause timeouts in the database connections.

Changes required to fix the issue

1. Verify that the connection string for WORKZONE-DB-ARCHIVE and WORKZONE-DB-ODPNET secrets in the Key Vault includes “… (DESCRIPTION=(ENABLE=broken)…”
2. Upgrade the containers for WorkZone Content Server to version 2024.4.1 (not to be confused with 2.24.4.1).

Installation steps

1. Change WORKZONE-DB-ARCHIVE and WORKZONE-DB-ODPNET to include “… (DESCRIPTION=(ENABLE=broken)…”.
2. Upgrade the container versions of WorkZone Content Server to 2024.4.1.

Install from a standard Pipeline Azure DevOps

1. Ensure that the the global image tag of the deployment pipeline is set to "24.4.1".
2. Verify that the following WorkZone Content Server containers have the correct tag.

   Repository	Tag
   workzone/wzcs/agentadw	24.4.1
   workzone/wzcs/agentfix	24.4.1
   workzone/wzcs/agentocr	24.4.1
   workzone/wzcs/agentsub	24.4.1
   workzone/wzcs/dbupgrade	24.4.1
   workzone/wzcs/explorer	24.4.1
   workzone/wzcs/landingpage	24.4.1
   workzone/wzcs/notifications	24.4.1
   workzone/wzcs/oauth2	24.4.1
   workzone/wzcs/odata	24.4.1
   workzone/wzcs/odata4	24.4.1
   workzone/wzcs/office	24.4.1
   workzone/wzcs/scim	24.4.1
   workzone/wzcs/sourceimport	24.4.1
   workzone/wzcs/wopi	24.4.1
   workzone/wzcs/wopiclient	24.4.1

Install with helm

Connect to the cluster and ensure that the cluster has access to pull the new images. Once you have connected to the cluster, you can deploy the helm charts for the WorkZone Content Server products.

In the pipeline, use the following command note that segments that marked with "<>" indicate that you must insert your actual value that is specified.

helm upgrade --namespace workzone --install --wait --create-namespace --timeout 180m --values <path-to-top-value-file>/values.yaml --values <path-to-env-value-file>/prepaks.yaml --set secretProvider.keyVaultName=<key-vault-name> --set secretProvider.tenantId=<tenant-id> --set secretProvider.userAssignedIdentityID=<userAssignedIdentityID>  <release-name>  <chart-path>

Repeat this step for all WorkZone Content Server containers. See the table above for a full list.