OSM CN : Timestamp Mismatch In console logs when running create/upgrade instance scripts (Doc ID 3049788.1)

Last updated on SEPTEMBER 30, 2024

Applies to:

Symptoms

On : 7.5.0.0.0 version, Cloud Native Toolkit

ACTUAL BEHAVIOR
---------------
Timestamp mismatch in Logs

We have observed different timestamp in the Putty commands and the file created using same command.

Sample given below:

LAST DEPLOYED: Fri Aug 2 10:06:28 2024
NAMESPACE: <namespace>
STATUS: deployed
REVISION: 11
TEST SUITE: None
@@ [2024-08-02T04:36:29][seconds=0] Info: Waiting up to 4400 seconds for exactly '2' WebLogic Server pods to reach the following criteria:
@@ [2024-08-02T04:36:29][seconds=0] Info: ready='true'
@@ [2024-08-02T04:36:29][seconds=0] Info: image='localhost/osm-cn-base:7.5.0'
@@ [2024-08-02T04:36:29][seconds=0] Info: domainRestartVersion='xx-xx-xx-xxxxx'
@@ [2024-08-02T04:36:29][seconds=0] Info: introspectVersion='xx-xx-xx-xxxxx'
@@ [2024-08-02T04:36:29][seconds=0] Info: namespace='namespace'
@@ [2024-08-02T04:36:29][seconds=0] Info: domainUID='namespace-instance'
@@ [2024-08-02T04:36:29][seconds=0] Info: Current pods that match the above criteria = 0
@@ [2024-08-02T04:37:22][seconds=53] Info: Current pods that match the above criteria = 1
@@ [2024-08-02T04:37:23][seconds=54] Info: Current pods that match the above criteria = 2
@@ [2024-08-02T04:37:23][seconds=54] Info: Success!

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.