Created attachment 1853003 [details] Switching authentication method Description of problem (please be detailed as possible and provide log snippets): During storagesystem creation, on the security and network page, when encryption is enabled using KMS, if the authentication method is switched from kubernetes to token or vice-versa, the data in the fields such as Connection name, Address, Port, Token/Role including all the fields in the advanced settings do not get cleared and retain the values that was previously set for the other authentication method. For example, if the authentication method is switched from token to kubernetes, the value in the token field is now the value in the Role field for the kubernetes auth method, which is not correct. Version of all relevant components (if applicable): --------------------------------------------------- OCP: 4.10.0-0.nightly-2022-01-22-102609 ODF: odf-operator.v4.10.0 full_version=4.10.0-113 Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? No Is there any workaround available to the best of your knowledge? n/a Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? 1 Can this issue reproducible? Yes Can this issue reproduce from the UI? Yes If this is a regression, please provide more details to justify this: No Steps to Reproduce: ------------------- 1. Install the ODF Operator 2. Create a storagesystem 3. On the Security and network page, enable cluster-wide encryption and select "Connect to an external key management service" 4. Set the authentication method as Kubernetes and fill out the details in other fields 5. Change the authentication method to Token Actual results: --------------- The data written for Kubernetes auth method is retained after switching to the token auth method and vice-versa. Expected results: ----------------- When the authentication method is switched, all the previously entered data should be cleared.
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: OpenShift Container Platform 4.11.0 bug fix and security 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:5069