Bug 2001958

Summary:	Cluster becomes degraded if it can't talk to Manila
Product:	OpenShift Container Platform	Reporter:	OpenShift BugZilla Robot <openshift-bugzilla-robot>
Component:	Storage	Assignee:	Martin André <m.andre>
Storage sub component:	OpenStack CSI Drivers	QA Contact:	Jon Uriarte <juriarte>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	urgent
Priority:	urgent	CC:	aos-bugs
Version:	4.6	Keywords:	FastFix, Triaged
Target Milestone:	---
Target Release:	4.9.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: error handling when communicating with Manila didn't account for all possible failures. Consequence: unexpected errors when talking to Manila would degrade the operator and thus the cluster. Fix: treat all failures to reach the Manila endpoint as a non fatal error Result: the Manila operator gets disabled instead of making the cluster degraded.	Story Points:	---
Clone Of:
Clones:	2002554 (view as bug list)		Environment:
Last Closed:	2021-10-18 17:51:23 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:	2001620
Bug Blocks:	2002554

Description OpenShift BugZilla Robot 2021-09-07 14:25:22 UTC

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

Description of problem: It's possible that for one reason or another we're unable to reach the Manila endpoint. In the past we've tried to be smart and handled errors differently, if it's a 404, a 403, or other types of errors. The problem with this approach is that it's very easy to forget valid failure cases. We've had a recent example with proxy setting not correctly propagated to the Manila pod and degrading the cluster.

We should instead treat all failures to reach the Manila endpoint as a non fatal error and disable the Manila operator instead of making the cluster degraded.

Comment 7 errata-xmlrpc 2021-10-18 17:51:23 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 (Moderate: OpenShift Container Platform 4.9.0 bug fix and security update), 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/RHSA-2021:3759