Back to bug 1970123
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Eran Tamir | 2021-06-10 05:40:28 UTC | Priority | unspecified | high |
| CC | etamir, nbecker | |||
| Flags | needinfo?(nbecker) | |||
| Severity | unspecified | urgent | ||
| Eran Tamir | 2021-06-10 05:45:30 UTC | Component | installation | Multi-Cloud Object Gateway |
| Mudit Agarwal | 2021-06-10 06:42:28 UTC | CC | muagarwa | |
| Assignee | muagarwa | nbecker | ||
| Elad | 2021-06-14 16:54:15 UTC | CC | ebenahar | |
| RHEL Program Management | 2021-06-14 16:54:24 UTC | Target Release | --- | OCS 4.8.0 |
| Nimrod Becker | 2021-06-15 15:13:47 UTC | Status | NEW | ASSIGNED |
| Assignee | nbecker | dzaken | ||
| Mudit Agarwal | 2021-06-29 13:42:56 UTC | Doc Type | If docs needed, set a value | Bug Fix |
| Nimrod Becker | 2021-07-05 14:43:10 UTC | Flags | needinfo?(nbecker) | |
| Mudit Agarwal | 2021-08-09 08:20:19 UTC | Summary | [Azure] NooBaa insecure StorageAccount does not allow for TLS 1.2 | [GSS] [Azure] NooBaa insecure StorageAccount does not allow for TLS 1.2 |
| Target Release | OCS 4.8.0 | --- | ||
| RHEL Program Management | 2021-08-09 08:20:27 UTC | Target Release | --- | OCS 4.9.0 |
| Red Hat One Jira (issues.redhat.com) | 2021-08-17 17:49:07 UTC | Link ID | Red Hat Issue Tracker OCSQECL-86 | |
| Red Hat One Jira (issues.redhat.com) | 2021-08-17 17:50:50 UTC | Link ID | Red Hat Issue Tracker OCSQECL-86 | |
| Elad | 2021-08-25 09:25:02 UTC | Keywords | AutomationBackLog | |
| Tom Manor | 2021-08-26 13:33:32 UTC | CC | dzaken | |
| Flags | needinfo?(dzaken) | |||
| Nimrod Becker | 2021-08-29 07:34:35 UTC | Flags | needinfo?(dzaken) | |
| Levy Sant'Anna | 2021-09-24 17:56:34 UTC | CC | lsantann | |
| Flags | needinfo?(dzaken) | |||
| Levy Sant'Anna | 2021-09-24 17:57:03 UTC | Priority | high | urgent |
| Rejy M Cyriac | 2021-09-26 21:06:25 UTC | Target Release | OCS 4.9.0 | --- |
| Rejy M Cyriac | 2021-09-26 21:11:49 UTC | Component | Multi-Cloud Object Gateway | Multi-Cloud Object Gateway |
| Product | Red Hat OpenShift Container Storage | Red Hat OpenShift Data Foundation | ||
| RHEL Program Management | 2021-09-26 21:15:29 UTC | Target Release | --- | ODF 4.9.0 |
| Bipin Kunal | 2021-09-28 15:47:07 UTC | Blocks | 2008590 | |
| Bipin Kunal | 2021-09-28 15:48:27 UTC | Blocks | 2008591 | |
| Yaniv Kaul | 2021-10-11 06:05:31 UTC | Flags | needinfo?(dzaken) | |
| Mudit Agarwal | 2021-11-03 04:17:34 UTC | Blocks | 2011326 | |
| Ashish Singh | 2021-11-12 12:30:37 UTC | CC | assingh | |
| Mudit Agarwal | 2021-11-16 13:58:14 UTC | Doc Type | Bug Fix | Known Issue |
| Nimrod Becker | 2021-11-16 13:59:42 UTC | Doc Text | Cause: MCG does not support an Azure StorageAcvcount configured with TLS 1.2 Consequence: Cannot create the default BS or any new BS on a SA which is with 1.2 only policy Workaround (if any): Result: |
|
| RHEL Program Management | 2021-11-18 02:36:06 UTC | Target Release | ODF 4.9.0 | ODF 4.10.0 |
| Danny | 2021-11-25 10:58:11 UTC | Link ID | Github noobaa/noobaa-operator/pull/805 | |
| Status | ASSIGNED | POST | ||
| Nimrod Becker | 2021-11-30 12:59:22 UTC | Status | POST | MODIFIED |
| Kusuma | 2021-12-06 17:04:42 UTC | Doc Text | Cause: MCG does not support an Azure StorageAcvcount configured with TLS 1.2 Consequence: Cannot create the default BS or any new BS on a SA which is with 1.2 only policy Workaround (if any): Result: | .Multicloud Object Gateway insecure storage account does not support TLS 1.2 Multicloud Object Gateway (MCG) does not support Microsoft Azure storage account configured with Transport Layer Security (TLS) 1.2. As a result, you cannot create the default backing store or any new backing store on a storage account which is with 1.2 only policy. |
| Flags | needinfo?(nbecker) | |||
| CC | kbg | |||
| Nimrod Becker | 2021-12-07 07:54:31 UTC | Flags | needinfo?(nbecker) | |
| Mudit Agarwal | 2021-12-07 08:35:09 UTC | Blocks | 2029749 | |
| Nimrod Becker | 2021-12-21 06:59:53 UTC | Status | MODIFIED | ON_QA |
| Fixed In Version | 4.10.0-50 | |||
| Mudit Agarwal | 2021-12-21 12:50:30 UTC | Doc Text | .Multicloud Object Gateway insecure storage account does not support TLS 1.2 Multicloud Object Gateway (MCG) does not support Microsoft Azure storage account configured with Transport Layer Security (TLS) 1.2. As a result, you cannot create the default backing store or any new backing store on a storage account which is with 1.2 only policy. | |
| Doc Type | Known Issue | Bug Fix | ||
| Danny | 2022-01-05 08:42:21 UTC | Flags | needinfo?(dzaken) needinfo?(dzaken) | |
| Eran Tamir | 2022-01-09 15:07:26 UTC | CC | kelwhite | |
| Flags | needinfo?(etamir) | |||
| Flags | needinfo?(etamir) | needinfo?(kelwhite) | ||
| Eran Tamir | 2022-01-16 08:24:00 UTC | Flags | needinfo?(kelwhite) | |
| Flags | needinfo?(etamir) | |||
| Flags | needinfo?(etamir) | needinfo?(kelwhite) | ||
| Kusuma | 2022-01-17 08:13:53 UTC | CC | kbg | |
| Elad | 2022-02-15 16:07:18 UTC | Flags | needinfo?(kelwhite) | |
| Flags | needinfo?(kelwhite) | |||
| Flags | needinfo?(kelwhite) | |||
| QA Contact | pbalogh | belimele | ||
| Ben Eli | 2022-02-23 13:10:41 UTC | Status | ON_QA | ASSIGNED |
| Mudit Agarwal | 2022-03-04 12:13:30 UTC | Blocks | 2056571 | |
| Danny | 2022-03-13 18:36:07 UTC | Link ID | Github noobaa/noobaa-operator/pull/878 | |
| Status | ASSIGNED | POST | ||
| Danny | 2022-03-16 14:09:35 UTC | Status | POST | MODIFIED |
| Danny | 2022-03-16 14:43:53 UTC | Status | MODIFIED | POST |
| Danny | 2022-03-16 14:47:00 UTC | Link ID | Github noobaa/noobaa-operator/pull/881 | |
| Nimrod Becker | 2022-03-21 06:49:06 UTC | Link ID | Github noobaa/noobaa-operator/pull/885 | |
| Nimrod Becker | 2022-03-21 07:03:08 UTC | Status | POST | MODIFIED |
| Nimrod Becker | 2022-03-22 06:56:47 UTC | Status | MODIFIED | ON_QA |
| Fixed In Version | 4.10.0-50 | 4.10.0-201 | ||
| Ben Eli | 2022-03-23 12:03:17 UTC | Status | ON_QA | VERIFIED |
| Nimrod Becker | 2022-03-29 13:26:27 UTC | 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. |
|
| Shilpi Sharma | 2022-04-05 09:53:10 UTC | 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. | 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. |
| CC | shilpsha | |||
| Shilpi Sharma | 2022-04-06 11:41:03 UTC | 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. | .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. |
| errata-xmlrpc | 2022-04-13 15:06:05 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2022-04-13 18:49:40 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2022-04-13 18:49:40 UTC | |||
| errata-xmlrpc | 2022-04-13 18:50:11 UTC | Link ID | Red Hat Product Errata RHSA-2022:1372 | |
| Prasad Desala | 2022-06-30 06:43:28 UTC | Keywords | AutomationBackLog | |
| CC | tdesala | |||
| Link ID | Github red-hat-storage/ocs-ci/pull/6060/ | |||
| Elad | 2023-08-09 16:49:53 UTC | CC | odf-bz-bot |
Back to bug 1970123