Back to bug 2005801
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Mudit Agarwal | 2021-09-20 08:30:09 UTC | CC | muagarwa | |
| Assignee | hchiramm | rar | ||
| Mudit Agarwal | 2021-09-20 10:36:06 UTC | Status | NEW | ASSIGNED |
| Red Hat Bugzilla | 2021-09-20 10:36:06 UTC | Doc Type | If docs needed, set a value | No Doc Update |
| Rejy M Cyriac | 2021-09-26 17:38:53 UTC | Component | csi-driver | csi-driver |
| Product | Red Hat OpenShift Container Storage | Red Hat OpenShift Data Foundation | ||
| Niels de Vos | 2021-09-28 13:58:38 UTC | Flags | needinfo?(rgeorge) | |
| CC | ndevos | |||
| Rachael | 2021-09-29 04:37:28 UTC | Flags | needinfo?(rgeorge) | |
| Mudit Agarwal | 2021-10-06 12:43:42 UTC | Flags | needinfo?(ndevos) | |
| Mudit Agarwal | 2021-10-11 10:26:16 UTC | Blocks | 2011326 | |
| Mudit Agarwal | 2021-10-11 10:28:09 UTC | Assignee | rar | nthomas |
| Doc Type | No Doc Update | Known Issue | ||
| Component | csi-driver | management-console | ||
| CC | jefbrown | |||
| Niels de Vos | 2021-10-11 12:27:21 UTC | Flags | needinfo?(ndevos) | |
| Niels de Vos | 2021-10-11 12:35:01 UTC | Doc Text | Cause: KMS provider options set in a Tenants namespace can be more advanced than the key/value settings that the OCS UI supports. Consequence: Configuration options for KMS providers set in the Tenants namespace need to be formatted as camelCase, instead of UPPER_CASE. This might be confusing for users that have access to the KMS provider configuration in the openshift-storage namespace, and the configuration in a Tenants namespace. Options in the openshift-storage namespace will be in UPPER_CASE, whereas the options in the Tenants namespace will be in camelCase. Workaround (if any): Use camelCase formatting of the KMS provider options. Result: Ceph-CSI is capable of taking the UPPER_CASE configuration options from the openshift-storage namespace, and combine the camelCase configuration options from the Tenants namespace. When a Tenant overrides configuration options from the openshift-namespace, the Tenant needs to use the camelCase format. |
|
| Sanjal Katiyar | 2021-10-12 19:50:19 UTC | CC | afrahman, gshanmug | |
| Flags | needinfo?(gshanmug) | |||
| CC | skatiyar | |||
| Rachael | 2021-10-13 11:49:41 UTC | CC | nberry | |
| Flags | needinfo?(nberry) | |||
| Neha Berry | 2021-10-14 07:29:49 UTC | Flags | needinfo?(nberry) | |
| gowtham | 2021-10-14 08:11:27 UTC | Flags | needinfo?(gshanmug) | |
| Nishanth Thomas | 2021-10-19 09:20:56 UTC | Assignee | nthomas | gshanmug |
| Nishanth Thomas | 2021-10-19 09:21:04 UTC | CC | nthomas | |
| gowtham | 2021-10-25 08:28:48 UTC | Flags | needinfo?(ndevos) needinfo?(shan) | |
| CC | shan | |||
| Sébastien Han | 2021-10-25 09:32:28 UTC | Flags | needinfo?(shan) | |
| gowtham | 2021-10-28 09:42:19 UTC | Flags | needinfo?(ndevos) | |
| Niels de Vos | 2021-10-28 11:58:00 UTC | Flags | needinfo?(ndevos) needinfo?(ndevos) | |
| Kusuma | 2021-12-09 03:30:01 UTC | Target Release | --- | ODF 4.10.0 |
| CC | kbg | |||
| Doc Text | Cause: KMS provider options set in a Tenants namespace can be more advanced than the key/value settings that the OCS UI supports. Consequence: Configuration options for KMS providers set in the Tenants namespace need to be formatted as camelCase, instead of UPPER_CASE. This might be confusing for users that have access to the KMS provider configuration in the openshift-storage namespace, and the configuration in a Tenants namespace. Options in the openshift-storage namespace will be in UPPER_CASE, whereas the options in the Tenants namespace will be in camelCase. Workaround (if any): Use camelCase formatting of the KMS provider options. Result: Ceph-CSI is capable of taking the UPPER_CASE configuration options from the openshift-storage namespace, and combine the camelCase configuration options from the Tenants namespace. When a Tenant overrides configuration options from the openshift-namespace, the Tenant needs to use the camelCase format. | .Tenant config does not override backendpath if the key is specified in upper case Key Management Service (KMS) provider options set in a Tenants namespace is more advanced than the key/value settings that the OpenShift Container Storage user interface supports. As a result, the configuration options for KMS providers set in the Tenants namespace need to be formatted as camel case, instead of upper case. It might be confusing for the users that have access to the KMS provider configuration in the `openshift-storage` namespace, and the configuration in a Tenants namespace as options in the `openshift-storage` namespace are in upper case, whereas the options in the Tenants namespace are in camel case. Workaround: Use camel case formatting for the KMS provider options. |
||
| Kusuma | 2021-12-09 03:31:56 UTC | Flags | needinfo?(ndevos) | |
| gowtham | 2022-01-24 12:33:02 UTC | Flags | needinfo?(rgeorge) | |
| RHEL Program Management | 2022-01-28 17:58:21 UTC | Target Release | ODF 4.10.0 | --- |
| Mudit Agarwal | 2022-01-31 15:43:19 UTC | Doc Text | .Tenant config does not override backendpath if the key is specified in upper case Key Management Service (KMS) provider options set in a Tenants namespace is more advanced than the key/value settings that the OpenShift Container Storage user interface supports. As a result, the configuration options for KMS providers set in the Tenants namespace need to be formatted as camel case, instead of upper case. It might be confusing for the users that have access to the KMS provider configuration in the `openshift-storage` namespace, and the configuration in a Tenants namespace as options in the `openshift-storage` namespace are in upper case, whereas the options in the Tenants namespace are in camel case. Workaround: Use camel case formatting for the KMS provider options. | |
| Doc Type | Known Issue | Bug Fix | ||
| Status | ASSIGNED | ON_QA | ||
| Neha Berry | 2022-01-31 16:17:03 UTC | QA Contact | ebenahar | rgeorge |
| RHEL Program Management | 2022-01-31 16:17:13 UTC | Target Release | --- | ODF 4.10.0 |
| Rachael | 2022-02-22 09:54:16 UTC | Flags | needinfo?(rgeorge) | needinfo?(gshanmug) |
| gowtham | 2022-02-22 10:16:55 UTC | Flags | needinfo?(gshanmug) | |
| Rachael | 2022-02-22 11:00:10 UTC | Status | ON_QA | VERIFIED |
| Mudit Agarwal | 2022-03-04 12:13:30 UTC | Blocks | 2056571 | |
| Mudit Agarwal | 2022-03-31 15:00:07 UTC | Flags | needinfo?(gshanmug) | |
| gowtham | 2022-03-31 16:26:22 UTC | Flags | needinfo?(gshanmug) | |
| Mudit Agarwal | 2022-03-31 16:33:57 UTC | Flags | needinfo?(gshanmug) | |
| gowtham | 2022-03-31 16:50:20 UTC | Doc Text | Cause: Upto 4.9, UI uses UPPER case to store all vault kms realted configs in csi-kms-connection-details configmap. But CSI uses camel case for mos of the places. Consequence: Same KMS config map is mixed with UPPER Case and lower, which leads the user in confusion. Fix: Now UI is moved to camel case and UPPER case for backward compatible. (Basically, we are using same keys what exactly CSI is using). Result: Now user can follow the CSI doc easily to any modification on this KMS config map file. | |
| Flags | needinfo?(gshanmug) | |||
| gowtham | 2022-03-31 17:04:39 UTC | Doc Text | Cause: Upto 4.9, UI uses UPPER case to store all vault kms realted configs in csi-kms-connection-details configmap. But CSI uses camel case for mos of the places. Consequence: Same KMS config map is mixed with UPPER Case and lower, which leads the user in confusion. Fix: Now UI is moved to camel case and UPPER case for backward compatible. (Basically, we are using same keys what exactly CSI is using). Result: Now user can follow the CSI doc easily to any modification on this KMS config map file. | Cause: Upto 4.9, UI uses an UPPER case to store the vault KMS configs in csi-kms-connection-details config map. But CSI supports upper case for UI in very limited places. and they recommed to use camel case for most of the places. Consequence: csi-kms-connection-detailsconfig map is mixed with both UPPER case and lower, which leads the user in confusion. Fix: With this fix, UI is moving to camel case and still supporting upper case for backward compatible. (UI using same keys which CSI is mentioned in their doc). Result: Now user can follow the CSI doc to do any modification on the csi-kms-connection-details config map. |
| Shilpi Sharma | 2022-04-04 19:29:03 UTC | CC | shilpsha | |
| Flags | needinfo?(gshanmug) | |||
| gowtham | 2022-04-05 10:14:17 UTC | Flags | needinfo?(gshanmug) | |
| Shilpi Sharma | 2022-04-05 10:16:25 UTC | Doc Text | Cause: Upto 4.9, UI uses an UPPER case to store the vault KMS configs in csi-kms-connection-details config map. But CSI supports upper case for UI in very limited places. and they recommed to use camel case for most of the places. Consequence: csi-kms-connection-detailsconfig map is mixed with both UPPER case and lower, which leads the user in confusion. Fix: With this fix, UI is moving to camel case and still supporting upper case for backward compatible. (UI using same keys which CSI is mentioned in their doc). Result: Now user can follow the CSI doc to do any modification on the csi-kms-connection-details config map. | OpenShift Data Foundation user interface available in camel case Previously, OpenShift Data Foundation user interface used upper case to store the vault Key Management System (KMS) configs in the csi-kms-connection-details config map. However, Ceph Container Storage Interface (CSI) supports the upper case for a user interface at limited places. Ceph CSI recommends using camel cases in most places. As a result, the csi-kms-connection-details config map is mixed with both upper and lower cases which caused confusion. With this update, the user interface is moving to the camel case while supporting the upper case for backward compatibility. |
| Shilpi Sharma | 2022-04-05 16:17:56 UTC | Doc Text | OpenShift Data Foundation user interface available in camel case Previously, OpenShift Data Foundation user interface used upper case to store the vault Key Management System (KMS) configs in the csi-kms-connection-details config map. However, Ceph Container Storage Interface (CSI) supports the upper case for a user interface at limited places. Ceph CSI recommends using camel cases in most places. As a result, the csi-kms-connection-details config map is mixed with both upper and lower cases which caused confusion. With this update, the user interface is moving to the camel case while supporting the upper case for backward compatibility. | .OpenShift Data Foundation user interface available in camel case Previously, OpenShift Data Foundation user interface used upper case to store the vault Key Management System (KMS) configs in the csi-kms-connection-details config map. However, Ceph Container Storage Interface (CSI) supports the upper case for a user interface at limited places. Ceph CSI recommends using camel cases in most places. As a result, the csi-kms-connection-details config map is mixed with both upper and lower cases which caused confusion. With this update, the user interface is moving to the camel case while supporting the upper case for backward compatibility. |
| errata-xmlrpc | 2022-04-13 15:07:35 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2022-04-13 18:49:43 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2022-04-13 18:49:43 UTC | |||
| errata-xmlrpc | 2022-04-13 18:50:26 UTC | Link ID | Red Hat Product Errata RHSA-2022:1372 | |
| Niels de Vos | 2022-09-28 15:46:13 UTC | Flags | needinfo?(ndevos) | |
| Elad | 2023-08-09 16:46:41 UTC | CC | odf-bz-bot |
Back to bug 2005801