-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Fully Compatible
-
ALL
-
v5.0, v4.4, v4.2, v4.0
-
Sharding 2021-06-28
-
12
disable_cluster_time_gossiping_in_unreadable_state.js asserts a read against a secondary from an external client to include cluster time metadata, but this is only true if the secondary has cached the cluster time signing keys, which isn't guaranteed immediately after startup. The test should account for this by wrapping the assertion with assert.soon().