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

Bug 1820545

Summary:	4.1 UPI Vmware test runs fail with invalid internal LB hostname in certificates
Product:	OpenShift Container Platform	Reporter:	Stefan Schimanski <sttts>
Component:	kube-apiserver	Assignee:	Stefan Schimanski <sttts>
Status:	CLOSED WONTFIX	QA Contact:	Xingxing Xia <xxia>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.4	CC:	aos-bugs, kewang, mfojtik, xxia
Target Milestone:	---	Keywords:	Reopened
Target Release:	4.1.z	Flags:	mfojtik: needinfo?
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	LifecycleStale
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1820543	Environment:
Last Closed:	2021-02-10 15:11:05 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:
Bug Depends On:	1820543
Bug Blocks:

Description Stefan Schimanski 2020-04-03 10:20:17 UTC

+++ This bug was initially created as a clone of Bug #1820543 +++

+++ This bug was initially created as a clone of Bug #1820542 +++

+++ This bug was initially created as a clone of Bug #1820145 +++

Description of problem:

UPI Vmware test runs fail with invalid internal LB hostname in certificates

Version-Release number of selected component (if applicable):

4.4, 4.5

Actual results:

https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-vsphere-upi-4.4/1357

Comment 1 Michal Fojtik 2020-05-12 10:45:22 UTC

This bug hasn't had any activity in the last 30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

As such, we're marking this bug as "LifecycleStale" and decreasing the severity. 

If you have further information on the current state of the bug, please update it, otherwise this bug will be automatically closed in 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

Comment 2 Stefan Schimanski 2020-05-12 13:35:59 UTC

Won't merge anymore into 4.1.

Comment 3 Michal Fojtik 2020-12-08 12:49:16 UTC

This bug hasn't had any activity in the last 30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're marking this bug as "LifecycleStale" and decreasing the severity/priority. If you have further information on the current state of the bug, please update it, otherwise this bug can be closed in about 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. Additionally, you can add LifecycleFrozen into Keywords if you think this bug should never be marked as stale. Please consult with bug assignee before you do that.