Bug 1705297 - When the secret referred to by the IngressController defaultCertificate is updated (oc apply) some apps continue to serve with old cert
Summary: When the secret referred to by the IngressController defaultCertificate is up...
Keywords:
Status: CLOSED DUPLICATE of bug 1701410
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Dan Mace
QA Contact: Hongan Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-01 23:20 UTC by Justin Pierce
Modified: 2022-08-04 22:24 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-01 23:39:30 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Justin Pierce 2019-05-01 23:20:04 UTC 
Description of problem:
After installing a cluster and configuring an ingress default certificate, when that certificate is renewed, the openshift-console, for one, does not serve the new certificate.

Version-Release number of selected component (if applicable):
4.0.0-0.9

How reproducible:
Unknown

Steps to Reproduce:
1. Install a cluster
2. Create certificate ALPHA and populate it into TLS secret X
3. Configure IngressController resource with defaultCertificate set to secret X
4. Verify that https://openshift-authentication-openshift-authentication.apps.... is served with ALPHA
5. Login
6. Verify that https://console-openshift-console.apps... is served with ALPHA
7. Generate a new certificate BETA
8. oc apply the changes to the secret X
9. Allow clusteroperators to settle
10. Note that openshift-authentication-openshift-authentication.apps is served with BETA
11. Note that console-openshift-console.apps is served with ALPHA

Actual results:
Console is still serving with the old certificate.

Expected results:
All apps should be serving with certificate BETA.

Additional info:
See attachments and listing for details.
Comment 4 Dan Mace 2019-05-01 23:39:30 UTC 

*** This bug has been marked as a duplicate of bug 1701410 ***
Note You need to log in before you can comment on or make changes to this bug.