*** Bug 1804886 has been marked as a duplicate of this bug. ***
Verified a few days ago that we can deploy NFD successfully from operator hub in custom namespace on OCP 4.3.0-0.nightly-2020-03-03-052929 after manually pushing to local registry nfd-operator v4.3.6 images and node-feature-discovery operand v4.3.6 images:
oc get pods -n test-nfd436
NAME READY STATUS RESTARTS AGE
nfd-master-gfjrb 1/1 Running 0 6d9h
nfd-master-k8vqj 1/1 Running 0 6d9h
nfd-master-nn5s9 1/1 Running 0 6d9h
nfd-operator-696464458f-6xk9c 1/1 Running 0 6d9h
nfd-worker-5vh2z 1/1 Running 8 6d9h
nfd-worker-m68fv 1/1 Running 15 6d9h
nfd-worker-rsjtc 1/1 Running 12 6d9h
However on OCP 4.3.5 the latest nfd-operator and node-feature-discovery images v.4.3.7, I am not able to deploy NFD in custom namespace on OCP 4.3.5.
The nfd-opertaor pod is in ErrImagePull. This is with redhat-operators as the openshift-marketplace operatorsource:
Failed to pull image "image-registry.openshift-image-registry.svc:5000/openshift/ose-cluster-nfd-operator:v4.3.7": rpc error: code = Unknown desc = Error reading manifest v4.3.7 in image-registry.openshift-image-registry.svc:5000/openshift/ose-cluster-nfd-operator: name unknown
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.