Description of problem: A node's host file can end up with an oc error message written to /etc/hosts: [root@master-2 ~]# cat /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 ;; image-registry.openshift-image-registry.svc image-registry.openshift-image-registry.svc.cluster.local # openshift-generated-node-resolver Connection image-registry.openshift-image-registry.svc image-registry.openshift-image-registry.svc.cluster.local # openshift-generated-node-resolver to image-registry.openshift-image-registry.svc image-registry.openshift-image-registry.svc.cluster.local # openshift-generated-node-resolver 198.223.0.10#53(198.223.0.10) image-registry.openshift-image-registry.svc image-registry.openshift-image-registry.svc.cluster.local # openshift-generated-node-resolver for image-registry.openshift-image-registry.svc image-registry.openshift-image-registry.svc.cluster.local # openshift-generated-node-resolver image-registry.openshift-image-registry.svc.cluster.local image-registry.openshift-image-registry.svc image-registry.openshift-image-registry.svc.cluster.local # openshift-generated-node-resolver failed: image-registry.openshift-image-registry.svc image-registry.openshift-image-registry.svc.cluster.local # openshift-generated-node-resolver timed image-registry.openshift-image-registry.svc image-registry.openshift-image-registry.svc.cluster.local # openshift-generated-node-resolver out. image-registry.openshift-image-registry.svc image-registry.openshift-image-registry.svc.cluster.local # openshift-generated-node-resolver Version-Release number of selected component (if applicable): How reproducible: Only rarely seen. This needs networking to be in a messed up state to prevent oc from being able to talk to the apiserver. Steps to Reproduce: 1. Not sure 2. 3. Actual results: See above for erroneous file. Expected results: The correct registry service name and ip address written to /etc/hosts Additional info:
This looks to be a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1882485. *** This bug has been marked as a duplicate of bug 1882485 ***
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days