During a conversion process cinder can overfill a controller root file system
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Undecided
|
Ivan Kolodyazhny |
Bug Description
When I create a new volume from a very large QCOW image (virtual size) the root file system of a controller might be overfilled because the cinder downloads the full size image to the /var/lib/
Steps to reproduce:
Install one controller and two ceph/compute nodes. The controller has to have the minimal possible size of a root filesystem (20GB). Ceph size should be enough to keep about 30GB. Create a QCOW2 image with large virtual size and upload it to Glance:
root@node-
image: ubuntu_
file format: qcow2
virtual size: 20G (21474836480 bytes)
disk size: 835M
cluster_size: 65536
Format specific information:
compat: 1.1
lazy refcounts: false
refcount bits: 16
corrupt: false
Then try to create a new volume from this image:
root@node-1:~# cinder create --image-id 4a5c016b-
During the conversion Cinder will download the whole image to the /var/lib/
Expected results:
Root filesystem should not be overfilled
Workaround:
1. To keep images in Raw format in Ceph so that Cinder does not download them but perform snapshots in Ceph storage
2. To forcefully separate /var from the root file system
This bug also affect other cinder backends
Fix proposed to branch: master /review. openstack. org/415868
Review: https:/