Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1582295

Summary: After upgrade - build logs do not load
Product: OpenShift Container Platform Reporter: Vikas Laad <vlaad>
Component: MasterAssignee: Jordan Liggitt <jliggitt>
Status: CLOSED DUPLICATE QA Contact: Wang Haoran <haowang>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.10.0CC: aos-bugs, jokerman, mfojtik, mmccomas
Target Milestone: ---   
Target Release: 3.10.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: 2018-05-25 13:38:21 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:
Attachments:
Description Flags
oc get logs --loglevel=9 none

Description Vikas Laad 2018-05-24 18:43:36 UTC 
Description of problem:
I upgraded cluster from 3.9.27 to v3.10.0-0.51.0, after the upgrade I am not able to load the logs for builds

Error from server: Get https://ip-172-31-38-139.us-west-2.compute.internal:10250/containerLogs/svt-cakephp-0/cakephp-mysql-example-5-build/sti-build: remote error: tls: internal error

attaching logs with loglevel=9

Version-Release number of selected component (if applicable):
openshift v3.10.0-0.51.0

Steps to Reproduce:
1. create 3.9 ha cluster
2. upgrade cluster to 3.10
3. start a build and load logs for a quickstart app

Actual results:
"oc get logs" fails

Expected results:
oc get logs should return logs for build

Additional info:
Comment 1 Vikas Laad 2018-05-24 18:45:05 UTC 
Created attachment 1441207 [details]
oc get logs --loglevel=9
Comment 3 Jordan Liggitt 2018-05-25 13:38:21 UTC 
duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1571515

ansible is not correctly waiting for all the nodes to request a serving certificate

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