Question
LTIMindtree
SA
Last activity: 4 Mar 2024 7:01 EST
Time Zone Difference in OpenShift PODS & Pega Logs Issue
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.
- Tried Passing the JVM Argument: -Duser.timezone="Asia/Riyadh"
- Created a configmap in the web deployment with below parameter kind: ConfigMap apiVersion: v1 metadata: name: timezone namespace: pegadev data: TZ: Asia/Riyadh
- 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"
- used the oc command: oc set env deployments/dc_name TZ=Asia/Riyadh
- used the oc command: oc set env deploymentconfig/dc_name TZ=Asia/Riyadh
- Tried all other instructions mentioned: https://access.redhat.com/solutions/2567961
- Created Environment Variable: TZ=Asia/Riyadh in Openshift Deployment
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.
- Tried Passing the JVM Argument: -Duser.timezone="Asia/Riyadh"
- Created a configmap in the web deployment with below parameter kind: ConfigMap apiVersion: v1 metadata: name: timezone namespace: pegadev data: TZ: Asia/Riyadh
- 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"
- used the oc command: oc set env deployments/dc_name TZ=Asia/Riyadh
- used the oc command: oc set env deploymentconfig/dc_name TZ=Asia/Riyadh
- Tried all other instructions mentioned: https://access.redhat.com/solutions/2567961
- Created Environment Variable: TZ=Asia/Riyadh in Openshift Deployment
Note: The same issue reported in Timezone Difference issue · Issue #710
***Edited by Moderator Rupashree to add Capability tags***
Accepted Solution
LTIMindtree
SA
Solution: In prlog4j2.xml file, added: {DEFAULT}{Asia/Riyadh} across all the logging level in <Pattern> 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.