Hi,

The error you're seeing could be due to a number of reasons. I will mention some places where you can check:

* check if the c-volume process is active and running: There could be some ERROR in the c-vol service logs due to LVM related issues to PV, VG etc

* given the scheduler logs, it looks like the backend couldn't pass filters and weighers, Check if there is available space in backend. If you're using a different volume type then does the backend pass the availability zone and capabilities filter of the volume type.

* Also I would recommend going through the scheduler logs (before the one you pasted) to see which filters your backend passes and which it doesn't to get an idea where it filters out your desired backend.

Hope that helps.

Thanks

Rajat Dhasmana

On Mon, Jan 16, 2023 at 4:06 AM A Monster <amonster369@gmail.com> wrote:

I deployed openstack yoga using kolla ansible, and used LVM as a backend for cinder storage service, after the deployment everything was working fine, but after a month, I could no longer create a volume as I get an error message
schedule allocate volume:Could not find any available weighted backend.
and the cinder_scheduler log shows the following error message
ERROR cinder.scheduler.flows.create_volume [req-2290223d-8f96-48d7-8680-959c5932d5be 3b4bd66ca3b04ab587a9a64a9e6966bc ec29bdcd73064dfb8186f413537327eb - - -] Failed to run task cinder.scheduler.flows.create_volume.ScheduleCreateVolumeTask;volume:create: No valid backend was found. No weighed backends available: cinder.exception.NoValidBackend: No valid backend was found. No weighed backends available

the storage server doesn't show any apparent errors,
any ideas of how can I fix this?