Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Timezone Difference issue #710

Open
BUHPS2261R opened this issue Feb 20, 2024 · 2 comments
Open

Timezone Difference issue #710

BUHPS2261R opened this issue Feb 20, 2024 · 2 comments

Comments

@BUHPS2261R
Copy link

Describe the bug
There is a time-zone difference between OpenShift PODS and PostgreSQL DB, OpenShift Cluster. We set the env to use TZ=Asia/Riyadh and it is still showing UTC time in the OpenShift PODs. But Both OpenShift Cluster and PostgreSQL server set to UTC+3 (Asia/Riyadh).

To Reproduce
connect to OpenShift terminal of the pega container.

Expected behaviour
Date and Time should display the UTC+3 time zone.

Chart version
Version: 1.2.0, Overall Helm charts package 3.6.3

Server (if applicable, please complete the following information):

  • OS: Linux amd64 4.18.0-372.87.1.el8_6x86_64
  • Environment: OpenShift (Client Version: 4.12.0, Kustomize version:4.5.7, Kubernetes Version: 1.25.16+5c97f5b)
  • Database: PostgreSQL 12.17

Additional context
Findings & Approaches followed to fix the issue and none of them were successful

  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
@kishorv10
Copy link
Contributor

@BUHPS2261R Are you facing any functional issues in the platform due to this difference? Are the rules create/update timestamps correctly reflected in the database & retrieved in the application?

connect to OpenShift terminal of the pega container.

Do you mean the pod OS time stamp is not honouring the timezone?

I wanted to understand the problems you are facing due to the mismatch.

@BUHPS2261R
Copy link
Author

Differneces facing: POD Shell Time zone and Pega Application Logs are different timezones. By default, UTC time zone being noted for application. But we want everything to be in KSA Time Zone.

Yes, The POD & logs stamps are not honouring the time zone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants