When we have an image with size > 1 GB, we follow the following steps to accomodate the image: 1) Detach the volume 2) extend the volume 3) Attach the volume 4) Open the volume device as a file and resume writing the image Sometimes due to several reasons (mostly network related), the size of the device file could mismatch with the actual volume size (or the backend LUN size). This can happen if the extend was performed (i.e. the control path) but it takes the time to reflect that into the mapped device (i.e. the data path). This mismatch can cause the issue "IOError: [Errno 28] No space left on device". To avoid this scenario, we check if the device size is less than the volume size, we wait for the extended LUN to show up in mapped device and then continue the image writing operation. Closes-Bug: #1959913 Change-Id: I206580f6be615ebc5e15b546b9c23728d4116a5d (cherry picked from commitchanges/71/829771/1 wallaby-emf3433ed1a5
) (cherry picked from commitea5139be9a
)
parent
2bc17c0a9e
commit
5f1cee6fa9
@ -0,0 +1,7 @@
|
||||
---
|
||||
fixes:
|
||||
- |
|
||||
`Bug #1959913 <https://bugs.launchpad.net/glance-store/+bug/1959913>`_:
|
||||
Added wait between the volume being extended and
|
||||
the new size being detected while opening the
|
||||
volume device.
|
Loading…
Reference in new issue