-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.8
-
None
-
None
-
Unspecified
-
If docs needed, set a value
Description of problem:
Deploying multiple SNOs via ACM/AI/Hive via ZTP process
Version-Release number of selected component (if applicable):
HUB OCP cluster 4.8.0-fc.8
SNO OCP cluster 4.8.0-fc.8
ACM 2.3.0-DOWNSTREAM-2021-06-07-19-53-02
How reproducible:
Some clusters show a start timestamp that is newer than the installed timestamp, but not all.
Steps to Reproduce:
1.
2.
3.
Actual results:
[root@f16-h11-000-1029p ~]# oc describe cd -A | egrep "Namespace:|Install.*Timestamp:"
Namespace: sno00001
Install Started Timestamp: 2021-06-09T22:34:07Z
Installed Timestamp: 2021-06-09T23:49:05Z
Namespace: sno00002
Install Started Timestamp: 2021-06-09T22:35:19Z
Installed Timestamp: 2021-06-09T22:30:20Z
Namespace: sno00003
Install Started Timestamp: 2021-06-09T22:35:19Z
Installed Timestamp: 2021-06-09T23:34:05Z
Namespace: sno00004
Install Started Timestamp: 2021-06-09T22:33:43Z
Installed Timestamp: 2021-06-09T22:30:40Z
Namespace: sno00005
Install Started Timestamp: 2021-06-09T22:33:52Z
Installed Timestamp: 2021-06-09T22:30:50Z
Namespace: sno00006
Install Started Timestamp: 2021-06-09T22:35:13Z
Installed Timestamp: 2021-06-09T22:31:00Z
...
Note how sno00002, sno00004, sno00005 and sno00006 all show installed timestamps that occur before their started timestamps.
Expected results:
installed timestamp should never be before the start of the install.
Additional info: