-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.20
-
None
-
False
-
-
None
-
Important
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
In OpenShift 4.20.1, attempting to use the "Edit Secret" form on a Secret that contains mixed data (binary files and text literals) results in a JavaScript error in the UI. Instead of loading the form or allowing edits, the Console displays a "Something wrong happened" crash screen.
Version-Release number of selected component (if applicable):
OpenShift Container Platform 4.20.1
How reproducible:
Always (100%)
Steps to Reproduce:
1. Generate a binary keystore file (JCEKS) and pack it into a JAR: keytool -genseckey -alias encryption-key-alias -keyalg AES -keysize 256 -keystore jgroups.jceks -storetype JCEKS -storepass abcd1234 -keypass abcd1234 jar cf jgroups-encryption.jar jgroups.jceks 2. Create a Secret containing this JAR and a separate password field: oc create secret generic test-ocp-secret --from-file=JGROUPS_ENCRYPTION=jgroups-encryption.jar --from-literal=JGROUPS_KEYSTORE_PASSWORD=abcd1234 3. Log in to the OpenShift Web Console (v4.20.1). 4. Navigate to Workloads -> Secrets, find test-ocp-secret. 5. Click Actions -> Edit Secret.
Actual results:
The Edit form fails to load or crashes immediately. Error Message: Something wrong happened: Cannot set properties of null (setting 'JGROUPS_KEYSTORE_PASSWORD')
Expected results:
The "Edit Secret" form should load successfully.
Additional info:
Workaround: Editing the Secret via the YAML tab works correctly.