Description of problem (please be detailed as possible and provide log snippests): When creating a bucket using NooBaa's S3 API, the bucket is created with a tiering policy that uses the internal storage and not the default backing store. Version of all relevant components (if applicable): ocs: 4.5.0-485 ocp: 4.5.0-0.nightly-2020-07-11-040723 mcg: 5.5.0-3dba413 Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? Yes, since the space on the internal storage is very limited. Is there any workaround available to the best of your knowledge? Yes - it's possible to enter the NB UI and add the default backingstore to the bucket's tiering policy Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? 1 Can 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 issue does not happen in OCS 4.4 Steps to Reproduce: 1. Create a new NB bucket by using the S3 API 2. Enter the NB UI, find the created bucket, check it's status and tiering policy 3. The bucket is in a warning state about its usage of the internal storage, and no backingstore is assigned in the tiering policy Actual results: Bucket is in warning state and uses the internal storage Expected results: Bucket is in a healthy state and uses the default backing store
*** This bug has been marked as a duplicate of bug 1838621 ***
Nimrod - why did you mark this bug as a duplicate of BZ1838621? The bucket is created successfully, and all operations performed on it are successful, too. We did not receive any InternalErrors while testing this BZ.
Symptoms are different, but this is the cause for 1838621. Since that one has all the logs and discussions on it, I marked this one as dup.