When the backing store of a volume wasn't accessible while updating the
volume definition the call would fail alltogether. In cases where we
currently (incorrectly) treat remote backing stores as local one this
might lead to strange errors.
Ignore the opening errors until we figure out how to track proper volume
metadata.
---
src/storage/storage_backend.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/src/storage/storage_backend.c b/src/storage/storage_backend.c
index f5bfdee..fdcaada 100644
--- a/src/storage/storage_backend.c
+++ b/src/storage/storage_backend.c
@@ -1465,7 +1465,8 @@ virStorageBackendUpdateVolInfo(virStorageVolDefPtr vol,
(ret = virStorageBackendUpdateVolTargetInfo(vol->target.backingStore,
updateCapacity,
withBlockVolFormat,
-
VIR_STORAGE_VOL_OPEN_DEFAULT)) < 0)
+
VIR_STORAGE_VOL_OPEN_DEFAULT |
+
VIR_STORAGE_VOL_OPEN_NOERROR) < 0))
return ret;
return 0;
--
2.0.0
--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
