Noobaa-operator pod is stuck in init state when deploying OCS 4 in a proxy environment.

Solution Verified - Updated -

Issue

  • noobaa-operator pod is stuck in Initializing state when deploying OCS 4 in a proxy enabled environment.
  • noobaa-operator pod returns status code: 403 error while creating the default noobaa backing store in a UPI VMware environment
time="2020-01-23T09:46:38Z" level=info msg="creating bucket noobaa-backing-store-ed24f6c7-579c-49da-a8ed-b07a299a6b8e" sys=openshift-storage/noobaa
time="2020-01-23T09:23:36Z" level=error msg="got error when trying to create bucket noobaa-backing-store-62e0c28e-b598-413a-86e6-ee56bbf8141b. error: SerializationError: failed to unmarshal error message\n\tstatus code: 403, request id: , host id: \ncaused by: Unmarshal Error: failed to unmarshal error message\n\t00000000

Environment

  • Red Hat OpenShift Container Storage 4.2
  • VMware UPI

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content