Bug 1659331

Summary:	[4.0]Couldn't find the default service cert secret in the pod from the Next-gen env
Product:	OpenShift Container Platform	Reporter:	zhou ying <yinzhou>
Component:	apiserver-auth	Assignee:	Matt Rogers <mrogers>
Status:	CLOSED DUPLICATE	QA Contact:	Chuan Yu <chuyu>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.1.0	CC:	aos-bugs, evb, jokerman, mfojtik, mmccomas, mrogers, wsun
Target Milestone:	---
Target Release:	4.1.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:	2019-03-28 20:34:02 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 zhou ying 2018-12-14 05:52:08 UTC

Description of problem:
Create pod in the Next-gen env, check the default service cert, couldn't find the service-ca.crt in path: /var/run/secrets/kubernetes.io/serviceaccount/

Ansible-installed BRYO env doesn't have the issue.

Version-Release number of selected component (if applicable):
oc v4.0.0-0.82.0
kubernetes v1.11.0+6855010f70

How reproducible:
Always

Steps to Reproduce:
1. Login the Next-gen env, create project;
2. Create pod, check the service cert

Actual results:
2. Couldn't find the service-ca.crt in path: /var/run/secrets/kubernetes.io/serviceaccount/
Without this cert, `curl https://hello.xxia-proj.svc:443` cannot be accessed within pod securely.


Expected results:
2. Should contain 'service-ca.crt' in the path /var/run/secrets/kubernetes.io/serviceaccount/.

Additional info:

Comment 3 Matt Rogers 2019-03-28 17:30:34 UTC

This was fixed by https://jira.coreos.com/browse/AUTH-131 where we added service-ca.crt back.

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


*** This bug has been marked as a duplicate of bug 1668825 ***