Bug 1814709

Summary: Setting s3 storage parameters in config.imageregistry.operator.openshift.io gets reverted
Product: OpenShift Container Platform Reporter: Jaspreet Kaur <jkaur>
Component: Image RegistryAssignee: Ricardo Maraschini <rmarasch>
Status: CLOSED DUPLICATE QA Contact: Wenjing Zheng <wzheng>
Severity: high Docs Contact:
Priority: high    
Version: 4.2.0CC: adam.kaplan, aos-bugs, florin-alexandru.peter, mouimet, rekhan
Target Milestone: ---   
Target Release: 4.6.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: 2020-09-01 08:21:06 UTC 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 Jaspreet Kaur 2020-03-18 14:41:15 UTC
Description of problem: We are using an S3 compatible storage backend and we want to use this for the image-registry as well.
Setting this in config.imageregistry.operator.openshift.io -
spec:
   storage:
    s3:
      bucket: xyz-registry
      region: eu-de
      regionEndpoint: xyz.com

gets overwritten by this - 
spec:
   storage:
    s3:
      bucket: xyz-registry
      encrypt: true
      keyID: ''
      region: eu-de
      regionEndpoint: xyz.com

This causes builds to fail because the registry uses encryption but the backend does not support it. Setting explicitly "encrypt: false" is overwritten to "encrypt: true", we can also see that the "generation" of the resource is incremented by 2.



Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results: Not able to use S3 storage as backend doesnt support encrypt true

Expected results: Should be able to modify


Additional info:

Comment 8 Oleg Bulatov 2020-05-18 22:34:25 UTC
Fixing the bug 1833109 should mitigate this problem.

Comment 13 Ricardo Maraschini 2020-09-01 08:21:06 UTC
This has been addressed by https://bugzilla.redhat.com/show_bug.cgi?id=1833109, closing this one.

*** This bug has been marked as a duplicate of bug 1833109 ***

Comment 14 Oleg Bulatov 2020-10-19 11:28:15 UTC
*** Bug 1888936 has been marked as a duplicate of this bug. ***