The amd64 VM and the arm64 VM have different timezones

[matthewei]

for amd64

sh-5.1$ lscpu | grep Architecture
Architecture:                       x86_64
sh-5.1$ date 
Tue Dec  2 09:54:14 UTC 2025
sh-5.1$ 

for arm64

sh-5.2$ lscpu | grep Architecture 
Architecture:                       aarch64
sh-5.2$ date
Tue Dec  2 04:55:25 EST 2025
sh-5.2$ 

[metal3-io-bot]

This issue is currently awaiting triage.
If Metal3.io contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[elfosardo]

@matthewei can you please provide some more info?

[matthewei]

Hi @elfosardo , Many thanks,
cluster 1: I deploy ironic-deployment and login this pod , I execute the command "date", I get "Tue Dec 2 09:54:14 UTC 2025" in "x86"
cluster2: I deploy ironic-deployment and login this pod ,I execute the command "date", I get "Tue Dec 2 04:55:25 EST 2025" in "ARM"

[tuminoid]

I'm guessting the base image has different tz by default and we don't explicitly set it anywhere ?

[matthewei]

yes, So I think we should keep them consistent. By the way, the IPA's time-zone is also different.
if the ironic-pod if different from IPA, we would get the following errors.

 Normal  ProvisioningError   3m27s  metal3-baremetal-controller  Cleaning failed: Node failed to start the first cleaning step: Connection to agent failed: Failed to connect to the agent running on node 2358ac2a-a4f4-4c27-8821-a4a0c455e971 for invoking command clean.get_clean_steps. Error: HTTPSConnectionPool(host='10.22.171.142', port=9999): Max retries exceeded with url: /v1/commands/?wait=true&agent_token=K6EE1gCfxjf9-dv-kd_3adR5-mhlLe_-1pt61QL95Y4 (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate is not yet valid (_ssl.c:1147)')))

[elfosardo]

@matthewei are you sure this is due to the images and not to the timezone set on the servers you're using?
this is actually a known issue

[metal3-io-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues will close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle stale