-
Bug
-
Resolution: Won't Do
-
Major
-
None
-
4.13, 4.12
Description of problem:
The documentation to install with an agent-based setup in a disconnected environment does not mentioned NTP as a requirement in the nodes network configuration.
~~~
time="21-06-2023 13:17:26" level=info msg="Sending step <ntp-synchronizer-130882bc> reply output <{\"ntp_sources\":[{\"source_name\":\"ext.e-zu.co.uk\",\"source_state\":\"unreachable\"},{\"source_name\":\"time3.panq.nl\",\"source_state\":\"unreachable\"},{\"source_name\":\"time1.panq.nl\",\"source_state\":\"unreachable\"},{\"source_name\":\"ntp1.trans-ix.nl\",\"source_state\":\"unreachable\"},{\"source_name\":\"time.chrony.nl\",\"source_state\":\"unreachable\"},{\"source_name\":\"ntp.dicode.nl\",\"source_state\":\"unreachable\"}]}> error <> exit-code <0>" file="step_processor.go:74" request_id=64526871-b820-4fc9-938b-89bbb64ae0ce
~~~
A customer failed installation was fixed by adding the parameter "additionalNTPSources" to the agent config.
Version-Release number of selected component (if applicable):
4.12 4.13
How reproducible:
Untested. I guess with metal servers with un-synchronized clocks.
Actual results:
Nodes fail to become "Ready" during initial installation phase.
Expected results:
Nodes ready to install.