Description of problem (please be detailed as possible and provide log snippests): When creating an objectbucketclaim for NooBaa the operator gets stuck atttempting to update the status and never proceeds: "E0227 16:55:55.508374 1 controller.go:190] error syncing 'openshift-storage/migstorage': error updating OBC status:%!(EXTRA *errors.StatusError=ObjectBucketClaim.objectbucket.io "migstorage" is invalid: status.phase: Unsupported value: "Pending": supported values: "pending", "bound", "released", "failed"), requeuing" Version of all relevant components (if applicable): OCS 4.2.1 lib-bucket-provisioner 1.0.0 Does this issue impact your ability to continue to work with the product Yes. It's impossible to set up an OBC and get it Bound. Is there any workaround available to the best of your knowledge? Not that I am aware of. Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? 2 Is this issue reproducible? Yes Can this issue reproduce from the UI? No If this is a regression, please provide more details to justify this: Yes. This worked when the aws-s3-provisioner operator was filling the dependency. Steps to Reproduce: 1. Install OCS 2. Create a BackingStore, BucketClass, and ObjectBucketClaim to set up a PV Pool backed Noobaa bucket Actual results: Error Expected results: OBC becomes bound. Additional info: I believe I saw this once prior manually installing lib-bucket-provisioner to fill the dependency instead of the aws-s3-provisioner operator. I never saw it with the aws-s3-provisioner operator filling the dependency.
Compare https://github.com/operator-framework/community-operators/blob/master/community-operators/lib-bucket-provisioner/1.0.0/objectbucketclaims.objectbucket.io.crd.yaml#L82-L86 https://github.com/operator-framework/community-operators/blob/0692f8912a9c69f45dd6191f1fe39d64c6f196e5/community-operators/awss3-operator-registry/1.0.0/objectbucketclaims.objectbucket.io.crd.yaml There was no validation, now there is, and the operator is trying to write an unsupported value.
I've hit this issue past 3 attempts this morning of getting ocs-operator (stable-4.2 channel) installed on new installs of OCP 4.3.
Moving this to MCG Since this appears to be a bug with NooBaa.
The problem is that the CRDs on lib-bucket-provisioner contain an outdated validation. This was never even used before because OLM always pulled those CRDs from awss3-operator, and now that this was “fixed” and lib-bucket-provisioner CRDs are installed, we fail. We will push a PR to community operators and ask OLM team to push it ASAP but it might only be propagated to clusters tomorrow…
Not sure how this can be fixed in 4.2 z stream which does not exist. @Nimrod, can you clarify?
ocp: 4.3.0-0.nightly-2020-03-20-053743 ocs: 4.3.0-377 created a pv backingstore, bucketclass and obc using ocs, created successfully and the obc became bound.
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-2020:1437