Hello, Andrew & Joke:

I have the same problem.

If I enable

show_image_direct_url = True
show_multiple_locations = True

on /etc/glance/glance-api.conf

When I create an instance from image, I get:

 [Error: Build of instance 5855874c-860c-4ab8-8b3f-08970e220806 aborted: Volume 0367557b-4efc-40ab-8fda-932ce0a9f542 did not finish being created even after we waited 3 seconds or 2 attempts. And its status is error.].


Thanks!


El 16/3/22 a las 10:33, Erno Kuvaja escribió:
On Thu, Feb 24, 2022 at 2:37 PM west, andrew <andrew.west-contractor@cgg.com> wrote:

Hello experts

 

Currently using openstack Xena and Ceph backend (Pacific 16.2.7)

 

It seems there is a bug (since Wallaby?) where the efficient use of a CEPH Pacific RBD backend (i.e with copy-on-write-cloning) is not working .

Show_image_direct_url needs to be False to create volumes (or ephemeral volumes for nova)

 

This can of course be tremendously slow (Nova  , ephemeral root disk) without copy-on-write cloning feature of Ceph.

 

As Ceph RBD is THE most favourite  backend for block storage in openstack I am wondering how others are coping (or workarounds found ?)

Which combinations of Openstack and Ceph  are known to work well with copy-on-write-cloning?

 

How is the noted GRAVE Security RISK  of enabling Show_image_direct_url mitigated  ?  (i.e I think , for CEPH RBD, it needs to  be True to get cloning to work efficiently)

 

 

See another report of this issue here:

Re: Ceph Pacifif and Openstack Wallaby - ERROR cinder.scheduler.flows.create_volume — CEPH Filesystem Users (spinics.net)

 

Thanks for any help or pointers,

 

Andrew West

Openstack consulting

CGG France

 

 

“This e-mail and any accompanying attachments are confidential. The information is intended solely for the use of the individual to whom it is addressed. Any review, disclosure, copying, distribution, or use of the email by others is strictly prohibited. If you are not the intended recipient, you must not review, disclose, copy, distribute or use this e-mail; please delete it from your system and notify the sender immediately.”