Checkinstall and HealthReport do not detect Timezone mismatch with DB on PostgreSQL

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

When upgrading PostgreSQL to 16.3.0, it looks like check-timezones.xml does not properly match App with DB timezones and the result is always an INFO message in which the DB Server Timezone is just set to the same value as App Server Timezone incorrectly

In the application, HealthReport will also show matching timezones and Host App Server time

STEPS TO REPRODUCE

1. Set a Windows upgrade from 16.2.3.1 to 16.3.0
2. Check PostgreSQL Database OS timezone (for this test it’s set to PST -8)
3. Set Clarity Windows app server OS timezone to -5 or anything else different from the above DB Timezone
4. Restart Clarity services after the changes
5. Now go to Administration – Health Report – Data Warehouse
6. Note the Application and Database Timezone Match is green and shows App Server time
7. Run the upgrade checkinstall

Expected Results: Checkinstall to fail with error

Actual Results: Checkinstall does not fail and detects DB Server Timezone wrongly as the same as Host Timezone. If you switch the Host Timezone 1 hour, again it will detect both as the same as the Host.

Environment

Clarity 16.3.0, 16.3.1

Cause

DE158160 

Resolution

• Due to PostgreSQL limitation
• Will Not Fix, please ignore the check status in checkinstall