Description of problem: When installing node-problem-detector it fails as it tries to pull from registry.redhat.io and doesnt consider oreg_url Version-Release number of the following components: rpm -q openshift-ansible openshift-ansible-3.11.7-1.git.0.911481d.el7_5.noarch rpm -q ansible ansible-2.6.4-1.el7ae.noarch ansible --version How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: fails Expected results: Should succeed without any issue. Additional info: https://github.com/openshift/openshift-ansible/blob/release-3.11/roles/openshift_node_problem_detector/defaults/main.yaml#L13
Node problem detector needs to be updated to follow something like https://github.com/openshift/openshift-ansible/blob/master/roles/openshift_web_console/defaults/main.yml#L7
Node-problem-detector always fails (irrespective of disconnected environment). Specifying the registry url using oreg_url doesn't help and it always tries to get the images from registry.redhat.io Tried with "openshift_docker_additional_registries" as well which failed with the same error.
This worked for me after modifying the image parameters. Created a PR for this: https://github.com/openshift/openshift-ansible/pull/10260
Based on my comment https://github.com/openshift/openshift-ansible/pull/10260#issuecomment-425471968, I am moving it to 3.11.z, please let me know if you disagree. So far does not seem critical enough to hold 3.11.
If the customer tries to install Node Problem detector in 3.11 from Satellite or disconnected installations, the installations will fail. So, they either need to disable Node Problem detector or pull the images manually on the nodes. I think, since we can workaround this issue, we are good to wait till 3.11.z
3.11 PR - https://github.com/openshift/openshift-ansible/pull/10335
Fix is available in openshift-ansible-3.11.23-1
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:0024