Bug 2078567

Summary:	Adding option that is not understood by legacy cloud provider to user-managed cloud.conf causes KCM to crashloop
Product:	OpenShift Container Platform	Reporter:	Martin André <m.andre>
Component:	Cloud Compute	Assignee:	ShiftStack Bugwatcher <shiftstack-bugwatcher>
Cloud Compute sub component:	OpenStack Provider	QA Contact:	Jon Uriarte <juriarte>
Status:	CLOSED DUPLICATE	Docs Contact:
Severity:	medium
Priority:	high	CC:	aos-bugs, m.andre, mfedosin, pprinett
Version:	4.11	Keywords:	Triaged
Target Milestone:	---
Target Release:	4.11.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:	2022-04-26 06:49:13 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 Martin André 2022-04-25 16:06:03 UTC

As the openstack platform is migrating to the external cloud provider, the user-managed cloud.conf in `openshift-config/cloud-provider-config` is now the source for both the in-tree cloud.conf (in `openshift-config-managed/kube-cloud-config`) and the CCM cloud.conf (in `openshift-cloud-controller-manager/cloud-conf`).

However, even after switching to CCM we need to keep initializing the in-tree cloud provider in order to be able to detach volumes created with legacy cloud provider.

Moreover, the legacy cloud provider errors out when it finds an option it does not understand, causing KCM to enters a crashloopback.

We can't legitimately ask customer to limit themselves to the intersection of in-tree and external cloud provider options. We should make the legacy cloud provider option parsing more tolerant and ignore unknown options.

Comment 1 Martin André 2022-04-26 06:49:13 UTC


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