Hi, Walid, this is a clone of original bug 1755469, could you verify it? Thanks in advance. One interesting thing is 4.2.2 was shown running well in bug 1755469#c42 while above PR is recent.
Verified that all nodes are still Ready after 25+ hours on both AWS and Azure IPI installed clusters: Azure: # oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.2.10 True False 25h Cluster version is 4.2.10 # oc get nodes NAME STATUS ROLES AGE VERSION walid4210zb-dxzqw-master-0 Ready master 26h v1.14.6+888f9c630 walid4210zb-dxzqw-master-1 Ready master 26h v1.14.6+888f9c630 walid4210zb-dxzqw-master-2 Ready master 26h v1.14.6+888f9c630 walid4210zb-dxzqw-worker-centralus1-kfxzw Ready worker 26h v1.14.6+888f9c630 walid4210zb-dxzqw-worker-centralus2-wrml6 Ready worker 26h v1.14.6+888f9c630 walid4210zb-dxzqw-worker-centralus3-csvpq Ready worker 26h v1.14.6+888f9c630 AWS: # oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.2.10 True False 25h Cluster version is 4.2.10 # oc get nodes NAME STATUS ROLES AGE VERSION ip-10-0-132-101.us-west-2.compute.internal Ready master 26h v1.14.6+888f9c630 ip-10-0-142-51.us-west-2.compute.internal Ready worker 26h v1.14.6+888f9c630 ip-10-0-157-108.us-west-2.compute.internal Ready master 26h v1.14.6+888f9c630 ip-10-0-157-125.us-west-2.compute.internal Ready worker 26h v1.14.6+888f9c630 ip-10-0-163-205.us-west-2.compute.internal Ready master 26h v1.14.6+888f9c630 ip-10-0-164-109.us-west-2.compute.internal Ready worker 26h v1.14.6+888f9c630
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-2019:4181