Back to bug 1984334
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Mudit Agarwal | 2021-07-21 09:32:50 UTC | Target Release | OCS 4.7.4 | --- |
| Mudit Agarwal | 2021-07-21 09:33:15 UTC | Status | NEW | ASSIGNED |
| Assignee | hchiramm | ndevos | ||
| Niels de Vos | 2021-07-21 09:47:00 UTC | Status | ASSIGNED | POST |
| Link ID | Github ceph/ceph-csi/pull/2307 | |||
| Blocks | 1983931 | |||
| Depends On | 1983931 | |||
| Doc Text | Cause: a failure in parsing the connection parameters for a Hashicorp Vault KMS Consequence: initializing a Hashicorp Vault KMS as store for PV encryption passphrases fails. Volumes that want to use Hashicorp Vault to store/retrieve PV encryption passphrases can not be created, existing volumes can not be used. Fix: correct the parsing of the Vault connection parameters Result: By correctly parsing the Vault connection parameters, intializing the connection to the KMS works again and PV encryption passphrases can be stored/retrieved from Hashicorp Vault. |
|||
| Niels de Vos | 2021-07-21 09:47:48 UTC | Blocks | 1979604 | |
| Niels de Vos | 2021-07-21 09:50:33 UTC | Blocks | 1979604 | 1984333 |
| Niels de Vos | 2021-07-21 09:54:05 UTC | Doc Text | Cause: a failure in parsing the connection parameters for a Hashicorp Vault KMS Consequence: initializing a Hashicorp Vault KMS as store for PV encryption passphrases fails. Volumes that want to use Hashicorp Vault to store/retrieve PV encryption passphrases can not be created, existing volumes can not be used. Fix: correct the parsing of the Vault connection parameters Result: By correctly parsing the Vault connection parameters, intializing the connection to the KMS works again and PV encryption passphrases can be stored/retrieved from Hashicorp Vault. | Feature: Allow configuring `VAULT_BACKEND` parameter for selecting the type of backend used by Hashicorp Vault Reason: The autodetection of the backend used by Hashicorp Vault is not always working correctly. In case a non-common configuration is used, the automatically detected configuration parameter might be set incorrectly. Result: By allowing users to configure the `VAULT_BACKEND` (or `vaultBackend`) parameter, non-common configurations can be forced to use a particular type of backend. |
| Niels de Vos | 2021-07-21 11:50:01 UTC | Target Release | --- | OCS 4.9.0 |
| Mudit Agarwal | 2021-07-29 05:03:34 UTC | Status | POST | MODIFIED |
| Neha Berry | 2021-08-16 14:46:31 UTC | CC | nberry | |
| Elad | 2021-08-25 09:25:03 UTC | Keywords | AutomationBackLog | |
| Mudit Agarwal | 2021-09-24 15:52:51 UTC | Fixed In Version | v4.9.0-158.ci | |
| Status | MODIFIED | ON_QA | ||
| Rejy M Cyriac | 2021-09-26 16:57:11 UTC | CC | rcyriac | |
| Rejy M Cyriac | 2021-09-26 20:45:44 UTC | Target Release | OCS 4.9.0 | --- |
| Rejy M Cyriac | 2021-09-26 20:47:29 UTC | Component | csi-driver | csi-driver |
| Product | Red Hat OpenShift Container Storage | Red Hat OpenShift Data Foundation | ||
| RHEL Program Management | 2021-09-26 20:54:11 UTC | Target Release | --- | ODF 4.9.0 |
| Elad | 2021-10-05 12:46:09 UTC | QA Contact | ebenahar | rgeorge |
| Rachael | 2021-10-26 13:01:17 UTC | Status | ON_QA | VERIFIED |
| Mudit Agarwal | 2021-11-03 04:17:34 UTC | Blocks | 2011326 | |
| Kusuma | 2021-12-09 15:32:39 UTC | Doc Text | Feature: Allow configuring `VAULT_BACKEND` parameter for selecting the type of backend used by Hashicorp Vault Reason: The autodetection of the backend used by Hashicorp Vault is not always working correctly. In case a non-common configuration is used, the automatically detected configuration parameter might be set incorrectly. Result: By allowing users to configure the `VAULT_BACKEND` (or `vaultBackend`) parameter, non-common configurations can be forced to use a particular type of backend. | .Configuring `VAULT_BACKEND` parameter for selecting the type of backend used by Hashicorp Vault is now allowed With this update, you can configure the `VAULT_BACKEND` parameter for selecting the type of backend used by Hashicorp Vault. The autodetection of the backend used by Hashcorp Vault does not always work correctly. In case of a non-common configuration, the automatically detected configuration parameter might be set incorrectly. By allowing you to configure the `VAULT_BACKEND` parameter, non-common configurations can be forced to use a particular type of backend. |
| CC | kbg | |||
| Kusuma | 2021-12-09 15:36:33 UTC | Doc Text | .Configuring `VAULT_BACKEND` parameter for selecting the type of backend used by Hashicorp Vault is now allowed With this update, you can configure the `VAULT_BACKEND` parameter for selecting the type of backend used by Hashicorp Vault. The autodetection of the backend used by Hashcorp Vault does not always work correctly. In case of a non-common configuration, the automatically detected configuration parameter might be set incorrectly. By allowing you to configure the `VAULT_BACKEND` parameter, non-common configurations can be forced to use a particular type of backend. | .Configuring `VAULT_BACKEND` parameter for Hashicorp Vault is now allowed With this update, you can configure the `VAULT_BACKEND` parameter for selecting the type of backend used by Hashicorp Vault. The autodetection of the backend used by Hashcorp Vault does not always work correctly. In case of a non-common configuration, the automatically detected configuration parameter might be set incorrectly. By allowing you to configure the `VAULT_BACKEND` parameter, non-common configurations can be forced to use a particular type of backend. |
| Erin Donnelly | 2021-12-09 19:36:10 UTC | CC | edonnell | |
| Doc Text | .Configuring `VAULT_BACKEND` parameter for Hashicorp Vault is now allowed With this update, you can configure the `VAULT_BACKEND` parameter for selecting the type of backend used by Hashicorp Vault. The autodetection of the backend used by Hashcorp Vault does not always work correctly. In case of a non-common configuration, the automatically detected configuration parameter might be set incorrectly. By allowing you to configure the `VAULT_BACKEND` parameter, non-common configurations can be forced to use a particular type of backend. | .Configuring `VAULT_BACKEND` parameter for Hashicorp Vault is now allowed With this update, you can configure the `VAULT_BACKEND` parameter for selecting the type of backend used by Hashicorp Vault. The autodetection of the backend used by Hashicorp Vault does not always work correctly. In case of a non-common configuration, the automatically detected configuration parameter might be set incorrectly. By allowing you to configure the `VAULT_BACKEND` parameter, non-common configurations can be forced to use a particular type of backend. |
||
| Erin Donnelly | 2021-12-09 19:46:32 UTC | Doc Text | .Configuring `VAULT_BACKEND` parameter for Hashicorp Vault is now allowed With this update, you can configure the `VAULT_BACKEND` parameter for selecting the type of backend used by Hashicorp Vault. The autodetection of the backend used by Hashicorp Vault does not always work correctly. In case of a non-common configuration, the automatically detected configuration parameter might be set incorrectly. By allowing you to configure the `VAULT_BACKEND` parameter, non-common configurations can be forced to use a particular type of backend. | .Configuring `VAULT_BACKEND` parameter for HashiCorp Vault is now allowed With this update, you can configure the `VAULT_BACKEND` parameter for selecting the type of backend used by HashiCorp Vault. The autodetection of the backend used by HashiCorp Vault does not always work correctly. In case of a non-common configuration, the automatically detected configuration parameter might be set incorrectly. By allowing you to configure the `VAULT_BACKEND` parameter, non-common configurations can be forced to use a particular type of backend. |
| errata-xmlrpc | 2021-12-13 15:16:34 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2021-12-13 17:44:54 UTC | Resolution | --- | ERRATA |
| Status | RELEASE_PENDING | CLOSED | ||
| Last Closed | 2021-12-13 17:44:54 UTC | |||
| errata-xmlrpc | 2021-12-13 17:45:17 UTC | Link ID | Red Hat Product Errata RHSA-2021:5086 | |
| Elad | 2023-08-09 16:37:41 UTC | CC | odf-bz-bot |
Back to bug 1984334