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

Bug 1742002

Summary:	upgrade failed due to [openshift_control_plane : Wait for /apis/servicecatalog.k8s.io/v1beta1 when registered]
Product:	OpenShift Container Platform	Reporter:	Russell Teague <rteague>
Component:	Installer	Assignee:	Russell Teague <rteague>
Installer sub component:	openshift-ansible	QA Contact:	liujia <jiajliu>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	urgent
Priority:	urgent	CC:	aos-bugs, dmoessne, jesusr, jiajliu, jokerman, mfojtik, mmccomas, mtraylor, palonsor, rteague, syangsao, tmanor, wmeng
Version:	3.11.0
Target Milestone:	---
Target Release:	3.11.z
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: ServiceCatalog API endpoint not responding before timeout Consequence: Control Plane upgrade fails Fix: Increase timeout for checking API endpoints Result: Successful control plane upgrade	Story Points:	---
Clone Of:	1692735	Environment:
Last Closed:	2019-09-03 15:56:03 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Comment 2 liujia 2019-08-28 09:08:25 UTC

Version: openshift-ansible-3.11.141-1.git.0.a7e91cd.el7

Checked pr11821 merged.

# cat /usr/share/ansible/openshift-ansible/roles/openshift_control_plane/tasks/check_master_api_is_ready.yml|grep retries
  retries: 60
  retries: 60
  retries: 60
  retries: 60
  retries: 60

Steps:
1. Install ocp v3.10
2. Enable v3.11.141 repo on all hosts
3. Do upgrade against above cluster

Upgrade succeed, verify the bug.

Comment 4 errata-xmlrpc 2019-09-03 15:56:03 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:2580