+++ This bug was initially created as a clone of Bug #1843314 +++ Cluster version: 4.4.4 In our testbeds we occasionally see timeouts occuring during the phase when ironic is being brought up. time="2020-06-02T20:56:12Z" level=debug msg="module.masters.ironic_node_v1.openshift-master-host[2]: Still creating... [34m0s elapsed]" time="2020-06-02T20:56:12Z" level=debug msg="module.masters.ironic_node_v1.openshift-master-host[0]: Still creating... [34m0s elapsed]" time="2020-06-02T20:56:17Z" level=error time="2020-06-02T20:56:17Z" level=error msg="Error: could not contact API: timeout reached" When I check the bootstrap VM - I see that it works fine, just took it a bit longer than 30 minutes to boot with the ignition config and to get the rhcos image. Would it be possible to increase the timeout to say 1 hour. Thanks. --- Additional comment from sasha on 2020-06-04 20:52:50 UTC --- Just did some tests today on somewhat slow testbeds. Successfully deployed 4.4.5 today. As you can see from below it took a bit less than 27 mins: time="2020-06-04T07:14:52Z" level=debug msg="module.masters.ironic_node_v1.openshift-master-host[0]: Creation complete after 26m49s [id=4d8b98b2-ff8e-400d-bf07-ef8778e6183b]" time="2020-06-04T07:14:53Z" level=debug msg="module.masters.ironic_node_v1.openshift-master-host[2]: Creation complete after 26m50s [id=85acbf97-106e-4bee-83fa-4b855d69069c]" time="2020-06-04T07:14:53Z" level=debug msg="module.masters.ironic_node_v1.openshift-master-host[1]: Creation complete after 26m50s [id=7b522fe0-91a8-4234-898f-3a837ea5ccd9]" Then tried to install 4.5.0-0.nightly-2020-06-04-025914 it was timing out around 25 mins.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:2409