Bug 2008591 - [Clone for 4.7 backport] [Azure] NooBaa insecure StorageAccount does not allow for TLS 1.2
Summary: [Clone for 4.7 backport] [Azure] NooBaa insecure StorageAccount does not allo...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenShift Container Storage
Classification: Red Hat Storage
Component: Multi-Cloud Object Gateway
Version: 4.7
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: OCS 4.7.10
Assignee: Nimrod Becker
QA Contact: Ben Eli
URL:
Whiteboard:
Depends On: 1970123 2029749
Blocks: 2008590
TreeView+ depends on / blocked
 
Reported: 2021-09-28 15:48 UTC by Bipin Kunal
Modified: 2022-04-26 09:32 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previously, when the Microsoft Azure resource group was configured with a policy to enforce secure transfer for storage accounts, the installation of Multicloud Object Gateway (MCG) was stuck on the creation of the default backing store. This was because the MCG failed to create a storage account for the default backing store. With this update, a flag is added to allow HTTPS traffic only when you create a storage account. Now, you can install the MCG only in an environment that enforces secure transfer.
Clone Of: 1970123
Environment:
Last Closed: 2022-04-26 09:32:41 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github noobaa noobaa-operator pull 842 0 None Merged set EnableHTTPSTrafficOnly on create storage account 2022-01-27 15:24:39 UTC
Github noobaa noobaa-operator pull 884 0 None Merged [backport to 5.7] create azure StorageAccount with minTLS 1.2 2022-03-22 12:15:07 UTC
Red Hat Product Errata RHBA-2022:1534 0 None None None 2022-04-26 09:32:47 UTC

Comment 26 errata-xmlrpc 2022-04-26 09:32:41 UTC 
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 (Red Hat OpenShift Container Storage 4.7.10 bug fix update), 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-2022:1534
Note You need to log in before you can comment on or make changes to this bug.