Bug 1596233 - Webconsole secret is not created after being removed
Summary: Webconsole secret is not created after being removed
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Master
Version: 3.9.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.9.z
Assignee: Michal Fojtik
QA Contact: Xingxing Xia
URL:
Whiteboard:
Depends On:
Blocks: 1592303 1596557 1623987 1667981
TreeView+ depends on / blocked
 
Reported: 2018-06-28 12:48 UTC by Vadim Rutkovsky
Modified: 2019-11-20 19:09 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-20 19:09:46 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Controllers log (169.13 KB, application/x-xz)
2018-06-28 12:48 UTC, Vadim Rutkovsky 		no flags Details
View All

Description Vadim Rutkovsky 2018-06-28 12:48:16 UTC 
Created attachment 1455309 [details]
Controllers log

Description of problem:
Webconsole secret 'webconsole-serving-cert' in 'openshift-web-console' is not being recreated

Version-Release number of selected component (if applicable):
origin-3.9.0-1.el7.git.0.ba7faec.x86_64

openshift v3.9.0+ba7faec-1
kubernetes v1.9.1+a0ce1bc657

How reproducible:
Always

Steps to Reproduce:
1. Setup a cluster with webconsole
2. Run 'playbooks/redeploy-certificates.yml' playbook from openshift-ansible from release-3.9 branch
3. Check pod status

Actual results:
Pod stuck in ContainerCreating, as webconsole-serving-cert secret is not created

Expected results:
A new secret is generated, the pod comes up

Additional info:
Comment 3 Stephen Cuppett 2019-11-20 19:09:46 UTC 
OCP 3.6-3.10 is no longer on full support [1]. Marking CLOSED DEFERRED. If you have a customer case with a support exception or have reproduced on 3.11+, please reopen and include those details. When reopening, please set the Target Release to the appropriate version where needed.

[1]: https://access.redhat.com/support/policy/updates/openshift
Note You need to log in before you can comment on or make changes to this bug.