Building a test cluster with openstack ansible
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.
Hey! Sorry, can you please provide a little bit more output? As it's not even clear on what playbook/stage failure occurs. As the error you have pasted can be a result of some prior failed task as well. You can use https://paste.openstack.org/ to attach longer stdout On Wed, 12 Mar 2025, 21: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.
Hi Dmitriy, Many thanks -- I've captured the complete output here: https://paste.openstack.org/show/827099/ Sarah On Wed, Mar 12, 2025 at 8:59 PM Dmitriy Rabotyagov <noonedeadpunk@gmail.com> wrote:
Hey!
Sorry, can you please provide a little bit more output? As it's not even clear on what playbook/stage failure occurs.
As the error you have pasted can be a result of some prior failed task as well.
You can use https://paste.openstack.org/ to attach longer stdout
On Wed, 12 Mar 2025, 21: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.
-- [s]
++in addition, do u mind if you provide osp variable files on it to checking deep-dive about issue Sevgiler, Best, Kerem ÇELİKER On Thu, Mar 13, 2025 at 00:07 Sarah Thompson <plodger@gmail.com> wrote:
Hi Dmitriy,
Many thanks -- I've captured the complete output here:
https://paste.openstack.org/show/827099/
Sarah
On Wed, Mar 12, 2025 at 8:59 PM Dmitriy Rabotyagov < noonedeadpunk@gmail.com> wrote:
Hey!
Sorry, can you please provide a little bit more output? As it's not even clear on what playbook/stage failure occurs.
As the error you have pasted can be a result of some prior failed task as well.
You can use https://paste.openstack.org/ to attach longer stdout
On Wed, 12 Mar 2025, 21: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.
-- [s]
The only thing I have in the variables config is the default: --- # This file contains an example of the global variable overrides # which may need to be set for a production environment. ## OpenStack public endpoint protocol openstack_service_publicuri_proto: http ~ Am investigating the LXC issues, not found anything yet, but I've only looked on the Ansible host so far. On Wed, Mar 12, 2025 at 9:11 PM Kerem Celiker <kmceliker@gmail.com> wrote:
++in addition, do u mind if you provide osp variable files on it to checking deep-dive about issue
Sevgiler, Best, Kerem ÇELİKER
On Thu, Mar 13, 2025 at 00:07 Sarah Thompson <plodger@gmail.com> wrote:
Hi Dmitriy,
Many thanks -- I've captured the complete output here:
https://paste.openstack.org/show/827099/
Sarah
On Wed, Mar 12, 2025 at 8:59 PM Dmitriy Rabotyagov < noonedeadpunk@gmail.com> wrote:
Hey!
Sorry, can you please provide a little bit more output? As it's not even clear on what playbook/stage failure occurs.
As the error you have pasted can be a result of some prior failed task as well.
You can use https://paste.openstack.org/ to attach longer stdout
On Wed, 12 Mar 2025, 21: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.
-- [s]
-- [s]
Quick question: When LXC containers are created as part of the install process, what's the mechanism? Are they built from scratch? Are they downloaded? Are they cached on the ansible host or elsewhere and then moved to the target nodes for deployment? Or are they downloaded directly by the nodes? I'm pretty sure the problem is somewhere here -- if the download fails silently, I could imagine the ansible scripts getting confused and thinking they have installed LXC images when they haven't, so the errors only show up when something tries to attach to the (nonexistent) container. If I run setup_openstack I get a similar failure, just on a different nonexistent LXC. It's getting late here, I'm going to have another go at this tomorrow. Good night all! On Wed, Mar 12, 2025 at 9:19 PM Sarah Thompson <plodger@gmail.com> wrote:
The only thing I have in the variables config is the default:
--- # This file contains an example of the global variable overrides # which may need to be set for a production environment.
## OpenStack public endpoint protocol openstack_service_publicuri_proto: http ~
Am investigating the LXC issues, not found anything yet, but I've only looked on the Ansible host so far.
On Wed, Mar 12, 2025 at 9:11 PM Kerem Celiker <kmceliker@gmail.com> wrote:
++in addition, do u mind if you provide osp variable files on it to checking deep-dive about issue
Sevgiler, Best, Kerem ÇELİKER
On Thu, Mar 13, 2025 at 00:07 Sarah Thompson <plodger@gmail.com> wrote:
Hi Dmitriy,
Many thanks -- I've captured the complete output here:
https://paste.openstack.org/show/827099/
Sarah
On Wed, Mar 12, 2025 at 8:59 PM Dmitriy Rabotyagov < noonedeadpunk@gmail.com> wrote:
Hey!
Sorry, can you please provide a little bit more output? As it's not even clear on what playbook/stage failure occurs.
As the error you have pasted can be a result of some prior failed task as well.
You can use https://paste.openstack.org/ to attach longer stdout
On Wed, 12 Mar 2025, 21: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.
-- [s]
-- [s]
-- [s]
So images for LXC containers are build on the host directly with help of deboostrap/rpm as part of the prior openstack.osa.setup_hosts playbook. So now having a little bit more context I wonder if openstack.osa.setup_hosts was launched and what was the result there. Can you please re-run openstack-ansible openstack.osa.containers_lxc_create ? This playbook is included from setup_host and specifically oriented on creation of lxc containers. But the image and general preparation of the host for lxc is made with openstack.osa.containers_lxc_host playbook. But eventually, it is expected that setup_hosts is completed without errors before proceeding next to setup_infrastructure. On Wed, 12 Mar 2025, 23:05 Sarah Thompson, <plodger@gmail.com> wrote:
Quick question:
When LXC containers are created as part of the install process, what's the mechanism? Are they built from scratch? Are they downloaded? Are they cached on the ansible host or elsewhere and then moved to the target nodes for deployment? Or are they downloaded directly by the nodes?
I'm pretty sure the problem is somewhere here -- if the download fails silently, I could imagine the ansible scripts getting confused and thinking they have installed LXC images when they haven't, so the errors only show up when something tries to attach to the (nonexistent) container. If I run setup_openstack I get a similar failure, just on a different nonexistent LXC.
It's getting late here, I'm going to have another go at this tomorrow. Good night all!
On Wed, Mar 12, 2025 at 9:19 PM Sarah Thompson <plodger@gmail.com> wrote:
The only thing I have in the variables config is the default:
--- # This file contains an example of the global variable overrides # which may need to be set for a production environment.
## OpenStack public endpoint protocol openstack_service_publicuri_proto: http ~
Am investigating the LXC issues, not found anything yet, but I've only looked on the Ansible host so far.
On Wed, Mar 12, 2025 at 9:11 PM Kerem Celiker <kmceliker@gmail.com> wrote:
++in addition, do u mind if you provide osp variable files on it to checking deep-dive about issue
Sevgiler, Best, Kerem ÇELİKER
On Thu, Mar 13, 2025 at 00:07 Sarah Thompson <plodger@gmail.com> wrote:
Hi Dmitriy,
Many thanks -- I've captured the complete output here:
https://paste.openstack.org/show/827099/
Sarah
On Wed, Mar 12, 2025 at 8:59 PM Dmitriy Rabotyagov < noonedeadpunk@gmail.com> wrote:
Hey!
Sorry, can you please provide a little bit more output? As it's not even clear on what playbook/stage failure occurs.
As the error you have pasted can be a result of some prior failed task as well.
You can use https://paste.openstack.org/ to attach longer stdout
On Wed, 12 Mar 2025, 21: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.
-- [s]
-- [s]
-- [s]
Yeah, that one unlocked things for me. I had two problems -- one was the node configuration was messed up somehow, possibly by my attempt to verify LXC was working and ending up with defaults that didn't work for Openstack. After I rolled it back and started clean it installed the containers OK. The containers won't start, but this seems to be network config stuff but tbh I was expecting that because I was just using one of the examples without having done detailed configuration work. So my current work is really just getting the VMs' networking configured properly and verified before having another try via Ansible. Thanks for your help all! On Thu, Mar 13, 2025 at 6:02 AM Dmitriy Rabotyagov <noonedeadpunk@gmail.com> wrote:
So images for LXC containers are build on the host directly with help of deboostrap/rpm as part of the prior openstack.osa.setup_hosts playbook.
So now having a little bit more context I wonder if openstack.osa.setup_hosts was launched and what was the result there.
Can you please re-run openstack-ansible openstack.osa.containers_lxc_create ?
This playbook is included from setup_host and specifically oriented on creation of lxc containers.
But the image and general preparation of the host for lxc is made with openstack.osa.containers_lxc_host playbook.
But eventually, it is expected that setup_hosts is completed without errors before proceeding next to setup_infrastructure.
On Wed, 12 Mar 2025, 23:05 Sarah Thompson, <plodger@gmail.com> wrote:
Quick question:
When LXC containers are created as part of the install process, what's the mechanism? Are they built from scratch? Are they downloaded? Are they cached on the ansible host or elsewhere and then moved to the target nodes for deployment? Or are they downloaded directly by the nodes?
I'm pretty sure the problem is somewhere here -- if the download fails silently, I could imagine the ansible scripts getting confused and thinking they have installed LXC images when they haven't, so the errors only show up when something tries to attach to the (nonexistent) container. If I run setup_openstack I get a similar failure, just on a different nonexistent LXC.
It's getting late here, I'm going to have another go at this tomorrow. Good night all!
On Wed, Mar 12, 2025 at 9:19 PM Sarah Thompson <plodger@gmail.com> wrote:
The only thing I have in the variables config is the default:
--- # This file contains an example of the global variable overrides # which may need to be set for a production environment.
## OpenStack public endpoint protocol openstack_service_publicuri_proto: http ~
Am investigating the LXC issues, not found anything yet, but I've only looked on the Ansible host so far.
On Wed, Mar 12, 2025 at 9:11 PM Kerem Celiker <kmceliker@gmail.com> wrote:
++in addition, do u mind if you provide osp variable files on it to checking deep-dive about issue
Sevgiler, Best, Kerem ÇELİKER
On Thu, Mar 13, 2025 at 00:07 Sarah Thompson <plodger@gmail.com> wrote:
Hi Dmitriy,
Many thanks -- I've captured the complete output here:
https://paste.openstack.org/show/827099/
Sarah
On Wed, Mar 12, 2025 at 8:59 PM Dmitriy Rabotyagov < noonedeadpunk@gmail.com> wrote:
Hey!
Sorry, can you please provide a little bit more output? As it's not even clear on what playbook/stage failure occurs.
As the error you have pasted can be a result of some prior failed task as well.
You can use https://paste.openstack.org/ to attach longer stdout
On Wed, 12 Mar 2025, 21: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. >
-- [s]
-- [s]
-- [s]
-- [s]
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.
participants (3)
-
Dmitriy Rabotyagov
-
Kerem Celiker
-
Sarah Thompson