Bug 1916100 - [oVirt] Consume 23-10 ovirt sdk - csi operator
Summary: [oVirt] Consume 23-10 ovirt sdk - csi operator
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Storage
Version: 4.6
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.6.z
Assignee: Gal Zaidman
QA Contact: Gal Zaidman
Depends On: 1917146
TreeView+ depends on / blocked
Reported: 2021-01-14 08:13 UTC by Gal Zaidman
Modified: 2021-02-08 13:51 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1916096
: 1917146 (view as bug list)
Last Closed: 2021-02-08 13:51:20 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift ovirt-csi-driver-operator pull 38 0 None closed Bug 1916100: [release-4.6] bump go-ovirt to 2020-10-23 2021-02-05 18:34:15 UTC
Red Hat Product Errata RHSA-2021:0308 0 None None None 2021-02-08 13:51:37 UTC

Description Gal Zaidman 2021-01-14 08:13:55 UTC
Description of problem:
This is a bug for PR https://github.com/openshift/ovirt-csi-driver-operator/pull/38 cheery pick.

FollowLink function issues an additional HTTP call which may fail if ovirt-engine suddenly becomes unavailable.

When this will merge an error will be returned which will be caught by logic added in https://github.com/openshift/ovirt-csi-driver-operator/pull/37.

Steps to Reproduce:
1. Make the engine suddenly unavailable
2. Watch the CSI logs for a "Failed to follow disk: {disk name}" error

** I recommend verifying this and https://bugzilla.redhat.com/show_bug.cgi?id=1916096 together because BZ1916096 added the code to handle the error, and this BZ added the code that throws it

Comment 6 errata-xmlrpc 2021-02-08 13:51:20 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 (Important: OpenShift Container Platform 4.6.16 security and bug fix 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.


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