NooBaa PV-Pool Backingstore Frequently Flaps between "Rejected" and "Ready" Phase - OpenShift Data Foundation (ODF)

Solution Verified - Updated -

Issue

With insufficient resources on the pv-pool and sometimes noobaa-core-o, noobaa-endpoint, and noobaa-db-pg-0 are default/too low, the pods may breach the resource threshold, taking a resource(s) from the NooBaa stack offline and causing NooBaa to enter a temporary Rejected state. To overcome this, additional resources may need to be configured.

  • Objects fail to push to Object Bucket Claim
  • Unable to upload images to a Quay registry
  • pv-pool backingstore flaps between "Rejected" and "Ready" Phase
  • Error message: 'blob update invalid'
WARN[0077] Failed, retrying in 1s ... (1/3). Error: writing blob: uploading layer chunked: blob upload invalid

Environment

  • Red Hat OpenShift Container Platform (RCOCP) v4.x
  • Red Hat OpenShift Container Storage (OCS) v4.x
  • Red Hat OpenShift Data Foundations (ODF) v4.x
  • Red Hat Quay (RHQ) v3.x

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