Hey Sarah, i ve seen situations where file or directory permissions cause this kind of error and check the directories where LXC containers are supposed to be created - u need to make sure the Ansible user has the necessary rights to create and manage containers there for sure.. another thing is given that you can create containers manually, it really feels like something's going awry when OpenStack-Ansible tries to automate the process and digging into the OpenStack-Ansible logs might give you a more detailed error message that points to the exact issue.. By the way %60-70, it's likely an issue with how OpenStack-Ansible is trying to create and manage the containers so pls checking the OpenStack-Ansible logs in more detail might provide further clues for you and all of us. Have fun and good luck mate! Sevgiler, Best, Kerem ÇELİKER On Wed, Mar 12, 2025 at 23:49 Sarah Thompson <plodger@gmail.com> wrote:
Hi all,
I've been experimenting with openstack through a devstack instance, but I need to start looking at a more realistic deployment architecture. I have a 5 node Proxmox cluster available, so I've created 6 VMs, one to serve as a deployment host for Ansible etc, one as a controller node, and four compute nodes. These are all currently set up with Ubuntu 22 LTS and configured with 128GB of disk, 20GB of RAM and 12 cores. I've verified that Ansible works, LXC works correctly, etc.
I'm getting a failure when I'm running
openstack-ansible openstack.osa.setup_infrastructure
Specifically I get errors like:
PLAY [Gather repo facts] *******************************************************************************************************
TASK [Gathering Facts] ********************************************************************************************************* [WARNING]: Unhandled error in Python interpreter discovery for host openstack-controller-repo-container-e44299d5: unexpected output from Python interpreter discovery fatal: [openstack-controller-repo-container-e44299d5]: FAILED! => ansible_facts: {} changed: false failed_modules: ansible.legacy.setup: ansible_facts: discovered_interpreter_python: /usr/bin/python3 failed: true module_stderr: |- lxc-attach: openstack-controller-repo-container-e44299d5: attach.c: get_attach_context: 405 Connection refused - Failed to get init pid lxc-attach: openstack-controller-repo-container-e44299d5: attach.c: lxc_attach: 1469 Connection refused - Failed to get attach context module_stdout: '' msg: |- MODULE FAILURE See stdout/stderr for the exact error rc: 1 warnings: - Platform unknown on host openstack-controller-repo-container-e44299d5 is using the discovered Python interpreter at /usr/bin/python3, but future installation of another Python interpreter could change the meaning of that path. See https://docs.ansible.com/ansible-core/2.17/reference_appendices/interpreter_... for more information. msg: |- The following modules failed to execute: ansible.legacy.setup
Inspecting the openstack-controller node manually with lxc-ls, there are no containers present. (I have manually created one and tested it successfully, so it's definitely not something weird with not being able to create/run containers).
Thank you in advance for your insights. :-)
Sarah PS: When I have this working, next step is to put this on bare metal in a colo, assuming I can get it working.