Description of problem: During 4.6.4 -> 4.6.6 upgrade registry, backed with oVirt CSI drivers, failed to rollout as backing volume could not be mounted.
Same Issue, here is my must-gather file https://drive.google.com/file/d/1JoYZ1-VBC_E93xe4QCXiL7mELg5tTY9G/view?usp=sharing
Another must-gather with similar issue during OKD 4.5 -> 4.6 upgrade from https://github.com/openshift/okd/issues/406 - https://1drv.ms/u/s!AhsStU0_yWDegUXpTfbwE7Bq67IV
(In reply to Michael Silich from comment #2) > Same Issue, > > here is my must-gather file > > https://drive.google.com/file/d/1JoYZ1-VBC_E93xe4QCXiL7mELg5tTY9G/ > view?usp=sharing I see a lot of: 2020-12-04T10:22:48.787550045Z E1204 10:22:48.787247 1 server.go:125] /csi.v1.Controller/ControllerPublishVolume returned with error: Fault reason is "Operation Failed". Fault detail is "[Cannot attach Virtual Disk. The disk is already attached to VM.]". HTTP response code is "409". HTTP response message is "409 Conflict". 2020-12-04T10:22:48.820303504Z I1204 10:22:48.820230 1 controller.go:133] Attaching Disk 38c79a7d-42ee-48db-8692-eb452726d03f to VM 4089c540-80a7-4aca-bf44-b3dd0eabeeb8 Looks like it tries to move the PV to another node, can you share some information on the layout of nodes? Where this disk is currently attached?
steps: 1) install ocp 4.5 2) upgrade ocp to 4.6 3) Look on .install-config.log actual: there are no errors in .install-config.log I tried to reproduce this bug before the fix and couldn't reproduce it
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.7.0 security, bug fix, and enhancement 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-2020:5633
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days