f35aace69f
The loopback handling in the Linux kernel limits the filenames of files associated to loopback devices, see also linux/loop.h. This is reflected also on userspace, as kpartx will silently do nothing (exiting with 0) when requesting to remove a filename longer than 64 characters, as that name will obviously not match the truncated filename. The result of this is that, when extracting qcow2 images for the first time, if the qcow2 filename is long enough then the loopback device will not be removed, remaining as stale in the host. As a workaround, use a temporary file name when convering a qcow2 image to raw, instead of using the base name of the qcow2 file. While this still will not fix the issue when manually using a long temporary directory (e.g. TMP_DIR=/very/long/etc...), at least should avoid it in other cases. Change-Id: Ibf46cd313a9d89412c0e1068fa0993be6c5a29db |
||
|---|---|---|
| .. | ||
| bin | ||
| finalise.d | ||
| pre-install.d | ||
| element-deps | ||
| package-installs.yaml | ||
| README.rst | ||
============= redhat-common ============= Image installation steps common to RHEL and Fedora. Overrides: * To use a non-default URL for downloading base cloud images, use the environment variable DIB_CLOUD_IMAGES * To download a non-default release of cloud images, use the environment variable DIB_RELEASE * Alternatively, set DIB_LOCAL_IMAGE to the local path of a qcow2 cloud image. This is useful in that you can use a customized or previously built cloud image from diskimage-builder as input. The cloud image does not have to have been built by diskimage-builder. It should be a full disk image, not just a filesystem image.