Bug 1366528 – saml-auth pod error because of readiness probe failure for 3.3

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1366528 - saml-auth pod error because of readiness probe failure for 3.3

Summary:	saml-auth pod error because of readiness probe failure for 3.3

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	Installer (Show other bugs)
Sub Component:
Version:	3.3.0
Hardware:	Unspecified Unspecified

Priority	high Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	Brenton Leanhardt
QA Contact:	Johnny Liu
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2016-08-12 04:58 EDT by Johnny Liu
Modified:	2016-09-19 07:49 EDT (History)
CC List:	6 users (show)

See Also:
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2016-09-19 07:49:57 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
ose32 saml pod log (38.55 KB, text/plain) 2016-08-12 04:59 EDT, Johnny Liu	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2016:1933	normal	SHIPPED_LIVE	Red Hat OpenShift Container Platform 3.3 Release Advisory	2016-09-27 09:24:36 EDT

Groups: None (edit)

Comment 1 Johnny Liu 2016-08-12 04:59 EDT

Created attachment 1190306 [details]
ose32 saml pod log

Comment 3 Brenton Leanhardt 2016-08-12 14:43:14 EDT

Hi Jianlin, I tried a few different solutions but in the end I choose this workaround:

https://github.com/openshift/request-header-saml-service-provider/pull/5

Can you let me know if this works for you?  You'll just need to update the template and redeploy.

Comment 4 Johnny Liu 2016-08-14 22:37:40 EDT

Verified this bug with the PR#5, it is working well. 

I will merge the PR by myself so that QE could run full-functional testing today, hope not bring trouble for that.

Comment 6 Brenton Leanhardt 2016-09-19 07:49:57 EDT

Closing this bug because it's not currently customer facing and thus not needed for an advisory.

Note You need to log in before you can comment on or make changes to this bug.