Time Zone Difference in OpenShift PODS & Pega Logs Issue

General
, , , , , ,
1

We observed that, Openshift Cluster and PostgreSQL servers are configured with UTC+3 (Saudi Arabia / AST / Asia-Riyadh) time zone but Openshift PODS are running with UTC time zone.

Below approaches tried to fix the issue but no use. Looking for a solution to fix it.

  1. Tried Passing the JVM Argument: -Duser.timezone=“Asia/Riyadh”
  2. Created a configmap in the web deployment with below parameter
    kind: ConfigMap
    apiVersion: v1
    metadata:
    name: timezone
    namespace: pegadev
    data:
    TZ: Asia/Riyadh
  3. Updated the _pega-deployment.tpl with below setting
    containers:
    • name: pega-web-tomcat
      image: {{ .root.Values.global.docker.pega.image }}
      env:
    • name: TZ
      value: “Asia/Riyadh”
  4. used the oc command: oc set env deployments/dc_name TZ=Asia/Riyadh
  5. used the oc command: oc set env deploymentconfig/dc_name TZ=Asia/Riyadh
  6. Tried all other instructions mentioned: https://access.redhat.com/solutions/2567961
  7. Created Environment Variable: TZ=Asia/Riyadh in Openshift Deployment

References: Pega image date settings in openshift is not working properly · Issue #280 · pegasystems/pega-helm-charts · GitHub

Note: The same issue reported in Timezone Difference issue · Issue #710

2

@Kishore Sanagapalli

Solution: In prlog4j2.xml file, added: {DEFAULT}{Asia/Riyadh} across all the logging level in Tab.

Result: All the logs started producing in UTC+3 Time zone.

Above solution fixed the Time Zone issue in Pega RULES Logs.

Solution will be added further once the issue is fixed.