Bug 1946922
| Summary: | Ingress details page doesn't show referenced secret name and link | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Yadan Pei <yapei> |
| Component: | Management Console | Assignee: | Joe Caiani <jcaiani> |
| Status: | CLOSED ERRATA | QA Contact: | Yadan Pei <yapei> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.8 | CC: | aos-bugs, jokerman, spadgett, yapei |
| Target Milestone: | --- | ||
| Target Release: | 4.8.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-07-27 22:57:54 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: | 1948958 | ||
Moving back to ASSIGNED based on comments in PR https://github.com/openshift/console/pull/8623#pullrequestreview-634111913 https://github.com/openshift/console/pull/8623#issuecomment-818378548 Moving back to ON_QA. The intent of the existing code was to show the secret name as plain text, and it wasn't showing up due to a bug. We can open a separate issue to make it a link, which is a more involved fix. based on discussion https://github.com/openshift/console/pull/8645#issuecomment-821192481, this bug is only used to track the plain text is shown which is already fix. Multiple secrets should be rendered with link is tracked in another bug Verified on 4.8.0-0.nightly-2021-04-18-101412 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.8.2 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-2021:2438 |
Description of problem: On Ingress details page, `TLS certificate` shows 'Not configured' even a secret is referred Version-Release number of selected component (if applicable): 4.8.0-0.nightly-2021-04-05-174735 How reproducible: Always Steps to Reproduce: 1. create an ingress by specifying a Secret that contains a TLS private key and certificate $ cat > tls-example-ingress.yaml << EOF apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: tls-example-ingress spec: tls: - hosts: - https-example.foo.com secretName: testsecret-tls rules: - host: https-example.foo.com http: paths: - path: / pathType: Prefix backend: service: name: service1 port: number: 80 EOF $ oc create -f tls-example-ingress.yaml $ oc get ingress tls-example-ingress -o json | jq .spec.tls [ { "hosts": [ "https-example.foo.com" ], "secretName": "testsecret-tls" } ] 2. check Ingress details from Networking -> Ingresses -> tls-example-ingress Actual results: 2. on Ingress details page, `TLS certificate` field shows a value 'Not configured' Expected results: 2. we should render a resource icon and link to the referred secret `testsecret-tls` Additional info: