Description of problem -

If the timezone is set to UTC, Lifecycle worker is not running.
Local time is in CEST (UTC +2) and in config.json , NC_LIFECYCLE_TZ is set as UTC.
Thus the Lifecycle worker is failing to run

The OCP platform infrastructure and deployment type (AWS, Bare Metal, VMware, etc. Please clarify if it is platform agnostic deployment), (IPI/UPI):
noobaa-core-5.18.4-20250527.el9.x86_64
Scale : 5.2.3.1

 

 

The version of all relevant components (OCP, ODF, RHCS, ACM whichever is applicable):
N/A

 

 

Does this issue impact your ability to continue to work with the product?

No

 

Is there any workaround available to the best of your knowledge?

No workaround as of now

 

Can this issue be reproduced? If so, please provide the hit rate

Reproduced

 

If this is a regression, please provide more details to justify this:

No

Steps to Reproduce:

1. Create a scale cluster with BLC configured.

2. Change the time zone to UTC

3. Trigger the lifecycle worker

 

Note that NTP is synced to UTC time 

[root@bright-31 lifecycle]# chronyc tracking
Reference ID    : D8EF230C (time4.google.com)
Stratum         : 2
Ref time (UTC)  : Fri Jun 06 09:51:56 2025
System time     : 0.000007782 seconds fast of NTP time
Last offset     : +0.000018254 seconds
RMS offset      : 0.000018254 seconds
Frequency       : 5.601 ppm fast
Residual freq   : +23.845 ppm
Skew            : 0.046 ppm
Root delay      : 0.014672107 seconds
Root dispersion : 0.000451321 seconds
Update interval : 2.0 seconds
Leap status     : Normal

 

[root@bright-31 lifecycle]# date
Fri Jun  6 11:54:00 AM CEST 2025. --> Local time UTC +2

[root@bright-31 lifecycle]# jq . /mnt/cesSharedRoot/ces/s3-config/config.json | grep TZ
  "NC_LIFECYCLE_TZ": "UTC",

[root@bright-31 lifecycle]# /usr/local/bin/noobaa-cli lifecycle 2>/dev/null
{
  "response":

{     "code": "LifecycleWorkerNotRunning",     "message": "Lifecycle worker must run at 09:54 with delay of 10 minutes in timezone UTC"   }

}
[root@bright-31 lifecycle]# 

 

Now BLC is not running on Local time as well as UTC time

Expected results:
BLC should run on UTC time zone.