image pull error when installed from operator hub

[openshift]

image pull error when installed from operator hub

[arunabhabanerjee]

I just installed this operator from operato hub and I'm getting this error:

Failed to pull image "openshift/ose-node-problem-detector:v4.0": rpc error: code = Unknown desc = Error reading manifest v4.0 in docker.io/openshift/ose-node-problem-detector: errors: denied: requested access to the resource is denied unauthorized: authentication required

on the daemon set image.

Are you able to solve this issue? I am facing the same problem.

Failed to pull image "openshift/ose-node-problem-detector:v4.0": rpc error: code = Unknown desc = Error reading manifest v4.0 in docker.io/openshift/ose-node-problem-detector: errors: denied: requested access to the resource is denied unauthorized: authentication required

[mohit-sheth]

@raffaelespazzoli @arunabhabanerjee
did anyone of you find a solution?

[east4ming]

I have the same problem.

[east4ming]

Should be "registry.svc.ci.openshift.org/openshift/ose-node-problem-detector:v4.0" ?

[arunabhabanerjee]

Still I am facing the same issue.

Failed to pull image "registry.svc.ci.openshift.org/openshift/origin-v4.0:node-problem-detector-operator": rpc error: code = Unknown desc = Error reading manifest node-problem-detector-operator in registry.svc.ci.openshift.org/openshift/origin-v4.0: received unexpected HTTP status: 500 Internal Server Error

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci-robot]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.