We currently get errors like :
Oct 17 18:41:52.205 E clusteroperator/machine-api changed Degraded to True: SyncingFailed: Failed when progressing towards operator: 4.3.0-0.ci-2019-10-17-173803 because timed out waiting for the condition
But "timed out waiting for the condition" is not as useful as whatever it was that made us decide the last poll wasn't good enough. We should put that reason in the message instead.
Unable to get the deployment stuck during upgrade, but the comments in this PR shows it puts useful message now.
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.