fix(vd,vmbda): write occurred data volume errors to condition #286
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Some StorageClasses cause errors in the data volume, the CDI importer pod, and the PVC.
The error might be found either in the conditions or the events. CDI does not have a unified approach for storing errors.
As part of this task, I have propagated the errors from the conditions of the CDI importer pod to the conditions of the virtual disk.
Added a check to ensure the disk unplug operation is feasible before proceeding.
Improved the identification of conflicting VMBDA instances: now, a VMBDA instance is considered to be in conflict if it attempts to attach a disk that is already in use by another VMBDA instance, irrespective of whether the virtual machines match.
Checklist