-
Bug
-
Resolution: Done-Errata
-
Critical
-
CNV v4.15.0
Description of problem:
In Overview -> Settings -> User -> Manage SSH keys, when adding an existing key in the namespace whose key you are configuring, the UI indicates that a new key is saved with a randomly generated suffix; however, the key isn't actually created. If you navigate away and back again "Not configured" is displayed.
Version-Release number of selected component (if applicable):
How reproducible:
100%
Steps to Reproduce:
1. Add an existing key in the namespace whose key you are configuring 2. After clicking save the UI will display a new key with a random suffix 3. Navigate away and back
Actual results:
The UI displays "Not configured" instead of the secret name that was displayed previously. The key whose name was displayed was never created.
Expected results:
The existing key is configured instead of creating a new key with a random suffix.
Additional info:
It seems the bug caused by the design of adding key from another projects, some random strings are added to the key, this behavior should only happen while selecting key from another project. If it's the current project, it should use the same key name.
- clones
-
CNV-37629 Configure public SSH key from existing key not work
- Closed
- relates to
-
CNV-39316 test plans in polarion for bug 39108
- Closed
-
CNV-39317 automated tests for bug 39108
- Closed
- links to
-
RHEA-2024:128638 OpenShift Virtualization 4.15.1 Images
- mentioned on
(1 mentioned on)