Description of problem: When I create a new bucket and want to use it for the registry instead of the bucket that was provided by the registry operator, the operator starts to manage. Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. create a new bucket 2. update config.imageregistry spec.storage.s3.bucket, use the new bucket Actual results: The operator starts to use the new bucket, but status.storageManaged stays true. Expected results: storageManaged should become false. Additional info:
It's too risky to fix this in 4.5.0, moving to 4.6
*** Bug 1814709 has been marked as a duplicate of this bug. ***
I still can see status.storageManaged==true when I use self-created bucket on 4.6.0-0.nightly-2020-09-03-191144: storage: managementState: Managed s3: bucket: wzheng-test-3 encrypt: true region: us-east-1 virtualHostedStyle: false storageManaged: true
This is by design, we bootstrap as Managed and only move to Unmanaged (or storageManaged = false) if the user asks for it. The idea here is, if the user wants to manage the storage by herself she must first change the Spec.Storage.ManagementState to Unmanaged, from this point on the operator won't touch the storage anymore.
Thanks for the reply, Ricardo! Then this bug can be verified.
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 (OpenShift Container Platform 4.6 GA Images), 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:4196