I believe volume creation is failing here because the scheduler is looking for the extra_specs/properties specified in the type, but no backend is reporting those extra_specs, so the scheduler filters out all backends and can't fulfill the request. (The scheduler debug logs should show this.)
Extra_specs fields added to the type need to correspond to something reported by the volume service.
Thanks, Eric
On Fri, Feb 2, 2024 at 9:12 AM Josephine Seifert < josephine.seifert@cloudandheat.com> wrote:
Hi,
I was experimenting with the extra_specs of volume types for a project. And while I was able to set and unset properties freely, the volumes created from volume types with random properties could not be created. They always went into Error state.
When I removed the properties from the volume type, volumes could be created again. Is it meant to behave like this? So in other words: Are custom properties not allowed for volume types? And if so, why am I allowed to set custom properties? I would expect an Error to happen in the volume type set --property ... process and not when creating a volume.
greetings. Josephine (Luzi)