Bug 2176545

Summary: nooba bucket left bound after obc deleted
Product: [Red Hat Storage] Red Hat OpenShift Data Foundation Reporter: Daniel Osypenko <dosypenk>
Component: Multi-Cloud Object GatewayAssignee: nadav <nmizrahi>
Status: ASSIGNED --- QA Contact: krishnaram Karthick <kramdoss>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.12CC: nbecker, nberry, odf-bz-bot, shirshfe
Target Milestone: ---   
Target Release: ODF 4.14.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Daniel Osypenko 2023-03-08 16:10:16 UTC 
Description of problem (please be detailed as possible and provide log
snippests):

After Object Bucket Claims removal via web console one of the Buckets left on cluster in bound state. No events registered.

Version of all relevant components (if applicable):

OC version:
Client Version: 4.12.0-202208031327
Kustomize Version: v4.5.4
Server Version: 4.12.0-0.nightly-2023-03-03-043014
Kubernetes Version: v1.25.4+18eadca

OCS verison:
ocs-operator.v4.12.1              OpenShift Container Storage   4.12.1    ocs-operator.v4.12.0              Succeeded

Cluster version
NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.12.0-0.nightly-2023-03-03-043014   True        False         2d13h   Cluster version is 4.12.0-0.nightly-2023-03-03-043014

Rook version:
rook: v4.12.1-0.f4e99907f9b9f05a190303465f61d12d5d24cace
go: go1.18.9

Ceph version:
ceph version 16.2.10-138.el8cp (a63ae467c8e1f7503ea3855893f1e5ca189a71b9) pacific (stable)

  NooBaa Core Version:     5.12.0-d82be60
  NooBaa Operator Version: 5.12.0

must-gather logs and nooba description:
https://drive.google.com/drive/folders/1PmLgLT3KW0o8e6WgkIyX50HZoYUm_kjQ?usp=share_link

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
no

Is there any workaround available to the best of your knowledge?
remove OB

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?


Can this issue reproducible?
cannot reproduce

Can this issue reproduce from the UI?
yes

If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1. Create Object Bucket Claim nooba-default-bucket-class
2. Verify Object Bucket created
3. Delete Object Bucket Claim
4. Open Object Buckets, verify Object Bucket removed


Actual results:
Object Bucket stay in cluster

Expected results:
Object Bucket removed

Additional info:
The issue is not UI visible only. Object bucket exists. Reclaim policy: Delete

OB yaml:

01) danielosypenko@dosypenk-mac ocs-ci % oc get ob obc-default-bucket-claim-dosypenk-3 -o yaml
apiVersion: objectbucket.io/v1alpha1
kind: ObjectBucket
metadata:
  creationTimestamp: "2023-03-07T07:06:41Z"
  finalizers:
  - objectbucket.io/finalizer
  generation: 1
  labels:
    app: noobaa
    bucket-provisioner: openshift-storage.noobaa.io-obc
    noobaa-domain: openshift-storage.noobaa.io
  name: obc-default-bucket-claim-dosypenk-3
  resourceVersion: "1428614"
  uid: d445643f-304d-41f5-b126-9842e579216b
spec:
  additionalState:
    account: obc-account.bucket-claim-dosypenk-3-908094d0-af79-4d92-adfb-eb0cf494ced9.6406e281
    bucketclass: noobaa-default-bucket-class
    bucketclassgeneration: "1"
  claimRef: {}
  endpoint:
    additionalConfig:
      bucketclass: noobaa-default-bucket-class
    bucketHost: s3.openshift-storage.svc
    bucketName: bucket-claim-dosypenk-3-908094d0-af79-4d92-adfb-eb0cf494ced9
    bucketPort: 443
    region: ""
    subRegion: ""
  reclaimPolicy: Delete
  storageClassName: openshift-storage.noobaa.io
status:
  phase: Bound