Bug 1893351
Summary: | TLS secrets are not able to edit on console. | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | V S Krishna <kvatteka> |
Component: | Management Console | Assignee: | Jakub Hadvig <jhadvig> |
Status: | CLOSED ERRATA | QA Contact: | Yadan Pei <yapei> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.5 | CC: | aos-bugs, jokerman, yapei |
Target Milestone: | --- | ||
Target Release: | 4.7.0 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause: Wrong Secret type determination upon the saving.
Consequence: TLS secrets are not able to edit in the console.
Fix: Use the secret's 'type' field when updating Secret.
Result: TLS secrets are able to be updated.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2021-02-24 15:29:18 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1896149 |
Description
V S Krishna
2020-10-30 19:34:13 UTC
1. Create a Key/Value secret from console, Add tls.crt and tls.key as secret key, save the changes and the secret type will be set to kubernetes.io/tls 2. Goes to secret details page and Actions -> Edit Secret, Add Key/Value and Save the changes, kubernetes.io/tls type secret can be edited Verified on 4.7.0-0.nightly-2020-11-09-235738 We have back ported to 4.6.z and I see no issues back port to 4.5.z from QE's point of view. Let me confirm with Devs bug 1900443 is opened to track the backport to 4.5.z 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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement 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-2020:5633 |