Back to bug 2029749

Who When What Removed Added
Mudit Agarwal 2021-12-07 08:36:46 UTC Target Release ODF 4.10.0 ---
Assignee nbecker dzaken
Status NEW POST
Link ID Github noobaa/noobaa-operator/pull/805
Mudit Agarwal 2021-12-07 10:26:01 UTC Blocks 2011326
krishnaram Karthick 2021-12-14 14:03:46 UTC CC kramdoss
RHEL Program Management 2021-12-14 14:03:54 UTC Target Release --- ODF 4.9.1
Nimrod Becker 2021-12-14 14:04:51 UTC Status POST MODIFIED
Kusuma 2021-12-14 14:49:31 UTC CC kbg
errata-xmlrpc 2021-12-15 05:53:24 UTC Status MODIFIED ON_QA
Mudit Agarwal 2021-12-15 10:13:38 UTC Flags needinfo?(dzaken)
Doc Type If docs needed, set a value Bug Fix
Fixed In Version 4.9.1-252.ci
Danny 2021-12-15 13:37:59 UTC Doc Text Cause:
When the azure resource-group is configured with a policy to enforce secure transfer for storage accounts, NooBaa failed to create a storage account for the default backing store

Consequence:
NooBaa Installation failed and was stuck on the default backing store creation

Fix:
Added a flag to allow HTTPS traffic only when creating a storage account

Result:
NooBaa can be installed on environment that enforce secure transfer only.
Danny 2021-12-20 06:52:18 UTC Flags needinfo?(dzaken)
krishnaram Karthick 2021-12-21 06:43:08 UTC QA Contact ratamir belimele
Mudit Agarwal 2022-01-04 05:54:14 UTC Target Release ODF 4.9.1 ---
RHEL Program Management 2022-01-04 05:54:20 UTC Target Release --- ODF 4.9.2
Agil Antony 2022-01-12 14:06:54 UTC Doc Text Cause:
When the azure resource-group is configured with a policy to enforce secure transfer for storage accounts, NooBaa failed to create a storage account for the default backing store

Consequence:
NooBaa Installation failed and was stuck on the default backing store creation

Fix:
Added a flag to allow HTTPS traffic only when creating a storage account

Result:
NooBaa can be installed on environment that enforce secure transfer only.
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.
CC agantony
Ben Eli 2022-01-24 12:40:20 UTC QA Contact belimele asandler
Danny 2022-01-27 09:26:43 UTC Link ID Github noobaa/noobaa-operator/pull/813
Ben Eli 2022-01-27 17:51:11 UTC CC belimele
Nimrod Becker 2022-01-31 14:37:15 UTC Status ON_QA POST
RHEL Program Management 2022-01-31 14:37:23 UTC Target Release ODF 4.9.2 ---
Rejy M Cyriac 2022-01-31 15:09:59 UTC CC rcyriac
Fixed In Version 4.9.1-252.ci
Sunil Kumar Acharya 2022-02-21 14:37:17 UTC CC sheggodu
krishnaram Karthick 2022-03-03 02:13:34 UTC Status POST ASSIGNED
Danny 2022-03-16 14:51:26 UTC Status ASSIGNED POST
Link ID Github noobaa/noobaa-operator/pull/882
krishnaram Karthick 2022-03-21 08:10:28 UTC QA Contact asandler belimele
RHEL Program Management 2022-03-21 08:10:37 UTC Target Release --- ODF 4.9.5
Nimrod Becker 2022-03-21 15:50:49 UTC Status POST MODIFIED
errata-xmlrpc 2022-03-23 06:48:24 UTC Status MODIFIED ON_QA
Ben Eli 2022-03-24 13:30:08 UTC Status ON_QA VERIFIED
errata-xmlrpc 2022-04-05 12:22:48 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2022-04-05 18:59:28 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2022-04-05 18:59:28 UTC
errata-xmlrpc 2022-04-05 18:59:43 UTC Link ID Red Hat Product Errata RHBA-2022:1237
Elad 2023-08-09 16:49:53 UTC CC odf-bz-bot

Back to bug 2029749