fsp not having correct time (future time) causes terraform install to fail

[robgjertsen1]

If the fsp time is not correct and in the future, then the install will fail with ignition certifiate request continually retrying until install timeout occurs.

Seeing this message in regard to master nodes with ignition about the current time and certificate timestamp in the future:
[ 467.737679] ignition[1066]: GET error: Get "https://api-int.merlin1-30ee.9.5.36.141.nip.io:22623/config/master": x509: certificate has expired or is not yet valid: current time 2023-03-29T10:23:36Z is before 2023-03-29T15:53:38Z
[ 472.738315] ignition[1066]: GET https://api-int.merlin1-30ee.9.5.36.141.nip.io:22623/config/master: attempt #97

You have to get onto the HMC and the Advanced System Managment (ASM) window and change the frame fsp time in order to resolve the issue.
Ideally the install does a sanity check on the fsp time given that this is being referenced for the certificate.
The TOD on the bastion and bootstrap nodes were OK as I recall. If not an easy way to detect, then documenting
this problem in a README or elsewhere would be helpful because this isn't an obvious issue to resolve.