Hey! I can guess that there's some config issue we have with the default ISCSI driver for cinder-volume that results in a failure you see. I can recall patching something simmilar a while back, but maybe it was not enough... I guess, I would actually try to add `ceph` to the SCENARIO (in case you're considering to use ceph later on) to spawn a ceph cluster as a backing storage for cinder - the flavor you've picked should be enough to handle that. Regarding logs - we try to write all logs to journald. So one way to get logs for cinder-volume could be like this: lxc-attach -n $(lxc-ls -1 | grep cinder_volume) -- journalctl -u cinder-volume Or you can just do lxc-attach -n $(lxc-ls -1 | grep cinder_volume) and inspect the container once attached. LXC on the contrary to Docker are system containers, not application ones. Journal logs are passed to host under /var/log/journal/ - each container has it's own directory based on the container machine-id, however I can't recall right away on how to map these folders to the specific container except do smth like: CINDER_MACHINE=$(lxc-attach -n $(lxc-ls -1 | grep cinder_volume) -- cat /etc/machine-id) journalctl --directory /var/log/journal/$CINDER_MACHINE -f Hope this helps. пт, 22 мар. 2024 г. в 12:45, <tatsuro.makita.bp@nttdata.com>:
Hi OpenStack Users Group,
I am building a single instance of AWS EC2 using OpenStack Ansible AIO (Bobcat). We are trying to build an all-in-one environment and check the functions of Bobcat. Construction Steps: https://docs.openstack.org/openstack-ansible/latest/user/aio/quickstart.html * I could use VLAN on EC2 only one instance. it doesn't multi-instance.
Anssible has been successful, and I can access and log in to the Horizon console with a browser. I have been able to register the image, but I get an error when I create a volume from the image. * Even if you create an empty volume, the same error will occur.
Wording displayed in the volume creation message: Message Level: ERROR Event Id: VOLUME_VOLUME_001_003 User Message: "all schedulelocate volume:Could not find any available weighted backend."
When I tried to refer to the lxc log to debug the environment, Under /var/log/lxc, there is only the log from the first startup, and there are no debug statements that are running during the actual inspection. The lxc-* command does not have a command like "Docker logs", so I am having trouble analyzing logs such as Cinder.
When building with Ansible, it is built with "debug:True" defined in /etc/openstacl_deploy/user_variables.yml. Is there any other configuration that outputs Debug logs for each component? Any advice on things to look at when analyzing each component built with lxc would be fine.
Furthermore, my environment is as follows. *Instance type: m5a.2xlarge *vCPU8, 32GiB, EBS storage 100GB(root) and 50GB(seccond) *OS:Ubuntu-jammy-22.04 *OpenStack Ansible: 28.0.1 (Bobcat)
Thanks regards.