Bug 1970123
| Summary: | [GSS] [Azure] NooBaa insecure StorageAccount does not allow for TLS 1.2 | |||
|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat OpenShift Data Foundation | Reporter: | Tom Manor <tmanor> | |
| Component: | Multi-Cloud Object Gateway | Assignee: | Danny <dzaken> | |
| Status: | CLOSED ERRATA | QA Contact: | Ben Eli <belimele> | |
| Severity: | urgent | Docs Contact: | ||
| Priority: | urgent | |||
| Version: | 4.6 | CC: | assingh, dzaken, ebenahar, etamir, kelwhite, lsantann, madam, muagarwa, nbecker, ocs-bugs, odf-bz-bot, shilpsha, tdesala | |
| Target Milestone: | --- | |||
| Target Release: | ODF 4.10.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | 4.10.0-201 | Doc Type: | Bug Fix | |
| Doc Text: |
.Install the Multicloud Object Gateway with a secure transfer
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.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 2008590 2008591 2029749 (view as bug list) | Environment: | ||
| Last Closed: | 2022-04-13 18:49:40 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: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 2008590, 2008591, 2011326, 2029749, 2056571 | |||
|
Comment 21
Yaniv Kaul
2021-10-11 06:05:31 UTC
Pending on a setup from QE to test Trying again here: https://ocs4-jenkins-csb-ocsqe.apps.ocp4.prod.psi.redhat.com/job/qe-trigger-azure-ipi-3az-rhcos-3m-3w-deployment/2/ Previous deployment job failed on OCP deployment cause of lack of resources in Azure. Ok as the deployment blocker got just fixed in latest ODF build I am rebuilding once more here: https://ocs4-jenkins-csb-ocsqe.apps.ocp4.prod.psi.redhat.com/job/qe-deploy-ocs-cluster-prod/2296/ 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 (Important: Red Hat OpenShift Data Foundation 4.10.0 enhancement, security & 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/RHSA-2022:1372 |