Bug 1668825

Summary:	serviceaccounttoken/service-ca.crt is missing
Product:	OpenShift Container Platform	Reporter:	David Eads <deads>
Component:	apiserver-auth	Assignee:	Erica von Buelow <evb>
Status:	CLOSED ERRATA	QA Contact:	Chuan Yu <chuyu>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.1.0	CC:	aos-bugs, eparis, mkhan, mrogers, nagrawal, yinzhou
Target Milestone:	---
Target Release:	4.1.0
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-04 10:42:08 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:

Description David Eads 2019-01-23 16:24:08 UTC

Workloads in 3.x relied upon the service-ca.crt being present to validate serving certificates. That file isn't present in 4.0 clusters and the new mechanism of configmap injection cannot be used on 3.x.  In order to run 3.x workloads on the 4.0 cluster, the serviceaccounttoken/service-ca.crt needs to be present.

Comment 1 Eric Paris 2019-01-23 16:25:27 UTC

I believe this must be fixed to ship 4.0

Comment 4 Chuan Yu 2019-03-14 03:55:48 UTC

Verified.

$ oc get secret -n default default-token-7gwqs -o json | jq '.data'
....
 "service-ca.crt": "LS0tLS1CRUdJTiBD.......
....

$ oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.0.0-0.nightly-2019-03-13-233958   True        False         35m     Cluster version is 4.0.0-0.nightly-2019-03-13-233958

Comment 5 Matt Rogers 2019-03-28 20:34:02 UTC

*** Bug 1659331 has been marked as a duplicate of this bug. ***

Comment 7 errata-xmlrpc 2019-06-04 10:42:08 UTC

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, 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/RHBA-2019:0758