can not create a volume
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MicroStack |
Invalid
|
Undecided
|
Unassigned |
Bug Description
in openstack page ,I create a volume ,but it failed.it returned
"schedule allocate volume:Could not find any available weighted backend."
my server is ubuntu 20.04
my microstack version is 233
in a single noe
df -h shows below:
udev 7.7G 0 7.7G 0% /dev
tmpfs 1.6G 1.5M 1.6G 1% /run
/dev/mapper/
tmpfs 7.7G 0 7.7G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 7.7G 0 7.7G 0% /sys/fs/cgroup
/dev/sda2 976M 199M 710M 22% /boot
/dev/sda1 511M 7.8M 504M 2% /boot/efi
/dev/loop1 387M 387M 0 100% /snap/microstac
/dev/loop2 62M 62M 0 100% /snap/core20/x1
/dev/loop0 33M 33M 0 100% /snap/snapd/x1
tmpfs 1.6G 0 1.6G 0% /run/user/1000
microstack.
+------
| ID | Name | Type |
+------
| 123d61ae87bb42a
| 1440bac4a2bf43d
| 1a9f1c68c24142e
| 4350ef5bd3ab45b
| 9d434dc4913d40f
| aed08482ea1e4d0
| e34d5368d02e4a4
+------
sudo microstack.
Binary Host Zone Status State Updated At RPC Version Object Version Cluster
cinder-scheduler tsingyun nova enabled :-) 2021-05-18 10:53:38 3.12 1.38
the attachment is the log after I click create volume button.I got it from /var/log/syslog
I really do not konw what's going wrong...
When you initialized microstack, did you enable the experimental volume backend? The cinder volume lvm configuration is not setup with the standard `sudo microstack init --auto --control`, but can be initialized from scratch using `sudo microstack init --auto --control --setup- loop-based- cinder- lvm-backend` which will setup a 32 GB loopback device for cinder volume storage. You can further expand the command to include `--loop- device- file-size <size_in_ GB_integer> ` to influence the size of the loopback device, i.e.:
sudo microstack init --auto --control --setup- loop-based- cinder- lvm-backend --loop- device- file-size 50
would initialize a control + compute node with a 50 GB loop device for storing cinder volumes.
I think that the microstack installation could do a bit better of a job of disabling cinder capabilities when its not fully configured to use the experimental volume backend, b/c otherwise it seems that the volume services are available when they really aren't.
With experimental volume support enabled, you'd see a microstack. cinder- scheduler and a microstack. cinder- volume service enabled and active in the output of `snap services microstack`. For future reference, the log files should be available in /var/snap/ microstack/ common/ log which should help debug the specific service.