November 2023 - openstack-discuss

[publiccloud-sig] Reminder - next meeting November 22nd - 0800 UTC
by Felix Kronlage-Dammers 20 Nov '23

20 Nov '23

Hi everyone, this Wednesday the next meeting of the public cloud sig is going to happen. Since we do every other meeting as a videosession, we’ll be meeting at 0800 UTC here: https://conf.scs.koeln:8443/OIF-public-cloud-sig In parallel we will be on irc on #openstack-operators as well of course. Am very much looking forward to wednesday morning! :) felix -- Felix Kronlage-Dammers Product Owner IaaS & Operations Sovereign Cloud Stack Sovereign Cloud Stack — standardized, built and … [View More]

1 0

RE: openstack-discuss -Nova Compute - Error | Urgent
by Asma Naz Shariq 20 Nov '23

20 Nov '23

Hi Openstack Community, I am deploying Openstack zed release Multinode cluster with 1x Controller and 1x compute and 1x storage. At the time of deployment, I encountered a below error for failed to register the compute service: TASK [nova-cell: Fail if nova-compute service failed to register] *********************************** fatal: [X.X.X.X]: FAILED! => {"changed": false, "msg": "The Nova compute service failed to register itself on the following hosts: computenode-virtual-machine"} … [View More]fatal: [X.X.X.X]: FAILED! => {"changed": false, "msg": "The Nova compute service failed to register itself on the following hosts: computenode-virtual-machine"} The logs in nova-compute.log at compute node state the ERROR: 2023-11-20 11:54:32.008 7 ERROR oslo. messaging._drivers.impl_rabbit [None req-f8176572-75bf-4c27-a9be-e096cb43e2e3 - - - - - -] Connection failed: [Errno 113] EHOSTUNREACH (retrying in 31.0 seconds): OSError: [Errno 113] EHOSTUNREACH. Can anyone guide me how to resolve this issue? Thanks -----Original Message----- From: openstack-discuss-request(a)lists.openstack.org <openstack-discuss-request(a)lists.openstack.org> Sent: Monday, November 20, 2023 10:16 AM To: openstack-discuss(a)lists.openstack.org Subject: openstack-discuss Digest, Vol 61, Issue 70 Send openstack-discuss mailing list submissions to openstack-discuss(a)lists.openstack.org To subscribe or unsubscribe via email, send a message with subject or body 'help' to openstack-discuss-request(a)lists.openstack.org You can reach the person managing the list at openstack-discuss-owner(a)lists.openstack.org When replying, please edit your Subject line so it is more specific than "Re: Contents of openstack-discuss digest..." Today's Topics: 1. Re: about magnum capi for production (Nguyễn Hữu Khôi) ---------------------------------------------------------------------- Message: 1 Date: Mon, 20 Nov 2023 12:16:11 +0700 From: Nguyễn Hữu Khôi <nguyenhuukhoinw(a)gmail.com> Subject: Re: about magnum capi for production To: Satish Patel <satish.txt(a)gmail.com> Cc: OpenStack Discuss <openstack-discuss(a)lists.openstack.org> Message-ID: <CABAODRfcEA38QRLCpr_DtC5Dbxmr2x=G9nD8hENptAdh0Z0QXg(a)mail.gmail.com> Content-Type: multipart/alternative; boundary="000000000000068859060a8e96ec" Hello guys. This is a doc which is about how to make Magnum CAPI to work with Openstack deployed by Kolla Ansible.. https://github.com/ngyenhuukhoi/openstack-note/blob/main/Magnum%20Cluster%2… Feel free to ask. If I can help, I will. Nguyen Huu Khoi On Mon, Nov 20, 2023 at 12:09 PM Nguyễn Hữu Khôi <nguyenhuukhoinw(a)gmail.com> wrote: > Hello. > It uses prebuild Ubuntu to provision k8s cluster, > > On Mon, Nov 20, 2023 at 11:47 AM Satish Patel <satish.txt(a)gmail.com> > wrote: > >> Hi Folks, >> >> Tell me if I am wrong. CAPI is just kubernetes images to build k8s >> clusters instead using coreOS and install a bunch of stuff via heat. >> In documentation all I can see are imported images. Reference doc: >> https://vexxhost.github.io/magnum-cluster-api/user/getting-started/ >> >> Do I need to install anything else to make it work? >> >> On Fri, Nov 17, 2023 at 11:30 AM Mohammed Naser <mnaser(a)vexxhost.com> >> wrote: >> >>> Thanks! Happy to see that it is working smoothly 😊 >>> >>> >>> >>> Appreciate any docs, comments or issues. >>> >>> >>> >>> *From: *Nguyễn Hữu Khôi <nguyenhuukhoinw(a)gmail.com> >>> *Date: *Friday, November 17, 2023 at 8:57 AM >>> *To: *Mohammed Naser <mnaser(a)vexxhost.com> >>> *Cc: *OpenStack Discuss <openstack-discuss(a)lists.openstack.org> >>> *Subject: *Re: about magnum capi for production >>> >>> Hello guys. >>> >>> >>> >>> I have successfully implemented Magnum CAPI on my openstack system. >>> My deployment tool for Openstack is Kolla-Ansible. It worked >>> greatly, I am testing with create, delete and resize k8s cluster. It >>> is smooth when compared with Heat Driver. I will make some docs for new users to use it. >>> >>> >>> >>> Thank you vexxhost.com and contributors for very nice production. >>> >>> >>> >>> I will keep testing and reporting to help it be much better in the >>> future. >>> >>> >>> Nguyen Huu Khoi >>> >>> >>> >>> >>> >>> On Tue, Nov 14, 2023 at 5:50 AM Nguyễn Hữu Khôi < >>> nguyenhuukhoinw(a)gmail.com> wrote: >>> >>> Hello. >>> >>> I get it now; >>> >>> Thank you very much. >>> >>> Nguyen Huu Khoi >>> >>> >>> >>> >>> >>> On Mon, Nov 13, 2023 at 11:20 PM Mohammed Naser >>> <mnaser(a)vexxhost.com> >>> wrote: >>> >>> Hi there, >>> >>> >>> Nope – it is simply a different driver, so if you try to create >>> Fedora CoreOS clusters – it’ll use the old heat driver. Otherwise, >>> it will use the Cluster API if the image is marked as Ubuntu >>> >>> >>> >>> Thanks! >>> >>> Mohammed >>> >>> >>> >>> *From: *Nguyễn Hữu Khôi <nguyenhuukhoinw(a)gmail.com> >>> *Date: *Monday, November 13, 2023 at 1:58 AM >>> *To: *Mohammed Naser <mnaser(a)vexxhost.com> >>> *Cc: *OpenStack Discuss <openstack-discuss(a)lists.openstack.org> >>> *Subject: *Re: about magnum capi for production >>> >>> Hello Mohammed, >>> >>> >>> >>> I found that >>> >>> >>> >>> >>> https://vexxhost.github.io/magnum-cluster-api/user/getting-started/# >>> creating >>> >>> >>> >>> I would like to know that if we use cluster api, does it overwrite >>> heat when deploying new k8s cluster from horizon? >>> >>> >>> Nguyen Huu Khoi >>> >>> >>> >>> >>> >>> On Mon, Oct 30, 2023 at 7:49 PM Nguyễn Hữu Khôi < >>> nguyenhuukhoinw(a)gmail.com> wrote: >>> >>> Awesome, thank you so much! >>> >>> Nguyen Huu Khoi >>> >>> >>> >>> >>> >>> On Mon, Oct 30, 2023 at 7:31 PM Mohammed Naser <mnaser(a)vexxhost.com> >>> wrote: >>> >>> Sounds good, thank you. >>> >>> >>> >>> We also have a channel on the Kubernetes Slack that is relatively >>> active if you need help — it’s in the README :) >>> >>> >>> >>> Thanks! >>> >>> Mohammed >>> >>> >>> >>> Get Outlook for iOS <https://aka.ms/o0ukef> >>> ------------------------------ >>> >>> *From:* Nguyễn Hữu Khôi <nguyenhuukhoinw(a)gmail.com> >>> *Sent:* Monday, October 30, 2023 8:23:07 AM >>> *To:* Mohammed Naser <mnaser(a)vexxhost.com> >>> *Cc:* OpenStack Discuss <openstack-discuss(a)lists.openstack.org> >>> *Subject:* Re: about magnum capi for production >>> >>> >>> >>> Hello. >>> >>> Thank you very much. I am planning to use Magnum CAPI for my system. >>> I will feedback later. >>> >>> Nguyen Huu Khoi >>> >>> >>> >>> >>> >>> On Mon, Oct 30, 2023 at 7:03 PM Mohammed Naser <mnaser(a)vexxhost.com> >>> wrote: >>> >>> Hi there! >>> >>> >>> >>> It works out of the box since the goal is to have an API that is >>> compatible so that all the ecosystem tools such as Terraform, >>> Ansible, CLI, Horizon all continue to work just fine! >>> >>> >>> >>> We’ve even made some quality of life improvements to the Magnum >>> plugin like letting you download KUBECONFIG from it. >>> >>> >>> >>> Thanks >>> >>> Mohammed >>> >>> >>> >>> Get Outlook for iOS <https://aka.ms/o0ukef> >>> ------------------------------ >>> >>> *From:* Nguyễn Hữu Khôi <nguyenhuukhoinw(a)gmail.com> >>> *Sent:* Monday, October 30, 2023 1:09:10 AM >>> *To:* Mohammed Naser <mnaser(a)vexxhost.com> >>> *Cc:* OpenStack Discuss <openstack-discuss(a)lists.openstack.org> >>> *Subject:* Re: about magnum capi for production >>> >>> >>> >>> Hello, >>> >>> >>> >>> Thank you for your sharing, Could you tell me how we use it with >>> Horizon or we need custom Horizon to use Magnum CAPI. >>> >>> >>> >>> Nguyen Huu Khoi >>> >>> >>> >>> >>> >>> On Mon, Oct 30, 2023 at 11:10 AM Mohammed Naser >>> <mnaser(a)vexxhost.com> >>> wrote: >>> >>> Hi there. >>> >>> >>> >>> We deploy this driver in production in our public cloud as well as >>> many private clouds and as part of Atmosphere and we’ve been fully >>> maintaining it on our side here. >>> >>> >>> >>> Let me know if you have any questions >>> >>> >>> >>> Thanks >>> >>> Mohammed >>> >>> >>> >>> Get Outlook for iOS <https://aka.ms/o0ukef> >>> ------------------------------ >>> >>> *From:* Nguyễn Hữu Khôi <nguyenhuukhoinw(a)gmail.com> >>> *Sent:* Sunday, October 29, 2023 10:22:22 PM >>> *To:* OpenStack Discuss <openstack-discuss(a)lists.openstack.org> >>> *Subject:* about magnum capi for production >>> >>> >>> >>> Hello guys. >>> >>> Could you share with me some experience about using Magnum CAPI in >>> production? >>> >>> >>> >>> https://github.com/vexxhost/magnum-cluster-api >>> >>> >>> >>> Thank you so much. >>> >>> >>> Nguyen Huu Khoi >>> >>> [View Less]

2 1

kolla-toolbox problem in multinode deploy
by Bursztynowski Dariusz 20 Nov '23

20 Nov '23

Hello, I'm facing a problem with kolla-toolbox while deploying zed-ubunu-jammy-aarch64 on a Raspberry Pi cluster using kolla-ansible. I 've built the images myself (on Raspbbery Pi) using kolla-build because images for Ubuntu-aarch64 were missing in standard repos (for Debian/aarch64, stuff installs from quay.io and works fine, but wanted to try out Ubuntu). The error can be seen at the very end of a fragment of the ansible log pasted below. As seen, images in my local repo are reachable … [View More](fluentd & kolla-toolbox restart succesfully). But in task "Initializing kolla-toolbox container" three hosts fail with the notification "Container xyz is restarting, wait until the container is running", while the fourth one gives "unable to upgrade to tcp, received 409". Interestingly, in a preceding task "Ensuring config directories have correct owner and permission" (the very first part of the log below), kolla-toolbox check is skipped. I can provide more data, create a bug report in appropriate place, etc. But please instruct me what and where. Best regards, Darek TASK [common : Ensuring config directories have correct owner and permission] ************************************************************************************************ ok: [ost64] => (item={'key': 'fluentd', 'value': {'container_name': 'fluentd', 'group': 'fluentd', 'enabled': True, 'image': '192.168.2.59:443/openstack.kolla/fluentd:zed-ubuntu-jammy-aarch64', 'environment': {'KOLLA_CONFIG_STRATEGY': 'COPY_ALWAYS'}, 'volumes': ['/etc/kolla/fluentd/:/var/lib/kolla/config_files/:ro', '/etc/localtime:/etc/localtime:ro', '/etc/timezone:/etc/timezone:ro', 'kolla_logs:/var/log/kolla/', 'fluentd_data:/var/lib/fluentd/data/'], 'dimensions': {}}}) ok: [ost61] => (item={'key': 'fluentd', 'value': {'container_name': 'fluentd', 'group': 'fluentd', 'enabled': True, 'image': '192.168.2.59:443/openstack.kolla/fluentd:zed-ubuntu-jammy-aarch64', 'environment': {'KOLLA_CONFIG_STRATEGY': 'COPY_ALWAYS'}, 'volumes': ['/etc/kolla/fluentd/:/var/lib/kolla/config_files/:ro', '/etc/localtime:/etc/localtime:ro', '/etc/timezone:/etc/timezone:ro', 'kolla_logs:/var/log/kolla/', 'fluentd_data:/var/lib/fluentd/data/'], 'dimensions': {}}}) skipping: [ost64] => (item={'key': 'kolla-toolbox', 'value': {'container_name': 'kolla_toolbox', 'group': 'kolla-toolbox', 'enabled': True, 'image': '192.168.2.59:443/openstack.kolla/kolla-toolbox:zed-ubuntu-jammy-aarch64', 'environment': {'ANSIBLE_NOCOLOR': '1', 'ANSIBLE_LIBRARY': '/usr/share/ansible'}, 'privileged': True, 'volumes': ['/etc/kolla/kolla-toolbox/:/var/lib/kolla/config_files/:ro', '/etc/localtime:/etc/localtime:ro', '/etc/timezone:/etc/timezone:ro', '/dev/:/dev/', '/run/:/run/:shared', 'kolla_logs:/var/log/kolla/'], 'dimensions': {}}}) skipping: [ost61] => (item={'key': 'kolla-toolbox', 'value': {'container_name': 'kolla_toolbox', 'group': 'kolla-toolbox', 'enabled': True, 'image': '192.168.2.59:443/openstack.kolla/kolla-toolbox:zed-ubuntu-jammy-aarch64', 'environment': {'ANSIBLE_NOCOLOR': '1', 'ANSIBLE_LIBRARY': '/usr/share/ansible'}, 'privileged': True, 'volumes': ['/etc/kolla/kolla-toolbox/:/var/lib/kolla/config_files/:ro', '/etc/localtime:/etc/localtime:ro', '/etc/timezone:/etc/timezone:ro', '/dev/:/dev/', '/run/:/run/:shared', 'kolla_logs:/var/log/kolla/'], 'dimensions': {}}}) ok: [ost62] => (item={'key': 'fluentd', 'value': {'container_name': 'fluentd', 'group': 'fluentd', 'enabled': True, 'image': '192.168.2.59:443/openstack.kolla/fluentd:zed-ubuntu-jammy-aarch64', 'environment': {'KOLLA_CONFIG_STRATEGY': 'COPY_ALWAYS'}, 'volumes': ['/etc/kolla/fluentd/:/var/lib/kolla/config_files/:ro', '/etc/localtime:/etc/localtime:ro', '/etc/timezone:/etc/timezone:ro', 'kolla_logs:/var/log/kolla/', 'fluentd_data:/var/lib/fluentd/data/'], 'dimensions': {}}}) skipping: [ost62] => (item={'key': 'kolla-toolbox', 'value': {'container_name': 'kolla_toolbox', 'group': 'kolla-toolbox', 'enabled': True, 'image': '192.168.2.59:443/openstack.kolla/kolla-toolbox:zed-ubuntu-jammy-aarch64', 'environment': {'ANSIBLE_NOCOLOR': '1', 'ANSIBLE_LIBRARY': '/usr/share/ansible'}, 'privileged': True, 'volumes': ['/etc/kolla/kolla-toolbox/:/var/lib/kolla/config_files/:ro', '/etc/localtime:/etc/localtime:ro', '/etc/timezone:/etc/timezone:ro', '/dev/:/dev/', '/run/:/run/:shared', 'kolla_logs:/var/log/kolla/'], 'dimensions': {}}}) ok: [ost63] => (item={'key': 'fluentd', 'value': {'container_name': 'fluentd', 'group': 'fluentd', 'enabled': True, 'image': '192.168.2.59:443/openstack.kolla/fluentd:zed-ubuntu-jammy-aarch64', 'environment': {'KOLLA_CONFIG_STRATEGY': 'COPY_ALWAYS'}, 'volumes': ['/etc/kolla/fluentd/:/var/lib/kolla/config_files/:ro', '/etc/localtime:/etc/localtime:ro', '/etc/timezone:/etc/timezone:ro', 'kolla_logs:/var/log/kolla/', 'fluentd_data:/var/lib/fluentd/data/'], 'dimensions': {}}}) skipping: [ost63] => (item={'key': 'kolla-toolbox', 'value': {'container_name': 'kolla_toolbox', 'group': 'kolla-toolbox', 'enabled': True, 'image': '192.168.2.59:443/openstack.kolla/kolla-toolbox:zed-ubuntu-jammy-aarch64', 'environment': {'ANSIBLE_NOCOLOR': '1', 'ANSIBLE_LIBRARY': '/usr/share/ansible'}, 'privileged': True, 'volumes': ['/etc/kolla/kolla-toolbox/:/var/lib/kolla/config_files/:ro', '/etc/localtime:/etc/localtime:ro', '/etc/timezone:/etc/timezone:ro', '/dev/:/dev/', '/run/:/run/:shared', 'kolla_logs:/var/log/kolla/'], 'dimensions': {}}}) ok: [ost64] => (item={'key': 'cron', 'value': {'container_name': 'cron', 'group': 'cron', 'enabled': True, 'image': '192.168.2.59:443/openstack.kolla/cron:zed-ubuntu-jammy-aarch64', 'environment': {'KOLLA_LOGROTATE_SCHEDULE': 'daily'}, 'volumes': ['/etc/kolla/cron/:/var/lib/kolla/config_files/:ro', '/etc/localtime:/etc/localtime:ro', '/etc/timezone:/etc/timezone:ro', 'kolla_logs:/var/log/kolla/'], 'dimensions': {}}}) ok: [ost61] => (item={'key': 'cron', 'value': {'container_name': 'cron', 'group': 'cron', 'enabled': True, 'image': '192.168.2.59:443/openstack.kolla/cron:zed-ubuntu-jammy-aarch64', 'environment': {'KOLLA_LOGROTATE_SCHEDULE': 'daily'}, 'volumes': ['/etc/kolla/cron/:/var/lib/kolla/config_files/:ro', '/etc/localtime:/etc/localtime:ro', '/etc/timezone:/etc/timezone:ro', 'kolla_logs:/var/log/kolla/'], 'dimensions': {}}}) ok: [ost62] => (item={'key': 'cron', 'value': {'container_name': 'cron', 'group': 'cron', 'enabled': True, 'image': '192.168.2.59:443/openstack.kolla/cron:zed-ubuntu-jammy-aarch64', 'environment': {'KOLLA_LOGROTATE_SCHEDULE': 'daily'}, 'volumes': ['/etc/kolla/cron/:/var/lib/kolla/config_files/:ro', '/etc/localtime:/etc/localtime:ro', '/etc/timezone:/etc/timezone:ro', 'kolla_logs:/var/log/kolla/'], 'dimensions': {}}}) ok: [ost63] => (item={'key': 'cron', 'value': {'container_name': 'cron', 'group': 'cron', 'enabled': True, 'image': '192.168.2.59:443/openstack.kolla/cron:zed-ubuntu-jammy-aarch64', 'environment': {'KOLLA_LOGROTATE_SCHEDULE': 'daily'}, 'volumes': ['/etc/kolla/cron/:/var/lib/kolla/config_files/:ro', '/etc/localtime:/etc/localtime:ro', '/etc/timezone:/etc/timezone:ro', 'kolla_logs:/var/log/kolla/'], 'dimensions': {}}}) TASK [common : Copy rabbitmq-env.conf to kolla toolbox] ********************************************************************************************************************** changed: [ost61] => (item=/home/ubuntu/labs/ostack/kolla-ansible-zed/share/kolla-ansible/ansible/roles/common/templates/rabbitmq-env.conf.j2) changed: [ost64] => (item=/home/ubuntu/labs/ostack/kolla-ansible-zed/share/kolla-ansible/ansible/roles/common/templates/rabbitmq-env.conf.j2) changed: [ost62] => (item=/home/ubuntu/labs/ostack/kolla-ansible-zed/share/kolla-ansible/ansible/roles/common/templates/rabbitmq-env.conf.j2) changed: [ost63] => (item=/home/ubuntu/labs/ostack/kolla-ansible-zed/share/kolla-ansible/ansible/roles/common/templates/rabbitmq-env.conf.j2) TASK [common : Copy rabbitmq erl_inetrc to kolla toolbox] ******************************************************************************************************************** changed: [ost64] => (item=/home/ubuntu/labs/ostack/kolla-ansible-zed/share/kolla-ansible/ansible/roles/common/templates/erl_inetrc.j2) changed: [ost61] => (item=/home/ubuntu/labs/ostack/kolla-ansible-zed/share/kolla-ansible/ansible/roles/common/templates/erl_inetrc.j2) changed: [ost62] => (item=/home/ubuntu/labs/ostack/kolla-ansible-zed/share/kolla-ansible/ansible/roles/common/templates/erl_inetrc.j2) changed: [ost63] => (item=/home/ubuntu/labs/ostack/kolla-ansible-zed/share/kolla-ansible/ansible/roles/common/templates/erl_inetrc.j2) TASK [common : Check common containers] ************************************************************************************************************************************** changed: [ost62] => (item={'key': 'fluentd', 'value': {'container_name': 'fluentd', 'group': 'fluentd', 'enabled': True, 'image': '192.168.2.59:443/openstack.kolla/fluentd:zed-ubuntu-jammy-aarch64', 'environment': {'KOLLA_CONFIG_STRATEGY': 'COPY_ALWAYS'}, 'volumes': ['/etc/kolla/fluentd/:/var/lib/kolla/config_files/:ro', '/etc/localtime:/etc/localtime:ro', '/etc/timezone:/etc/timezone:ro', 'kolla_logs:/var/log/kolla/', 'fluentd_data:/var/lib/fluentd/data/'], 'dimensions': {}}}) changed: [ost61] => (item={'key': 'fluentd', 'value': {'container_name': 'fluentd', 'group': 'fluentd', 'enabled': True, 'image': '192.168.2.59:443/openstack.kolla/fluentd:zed-ubuntu-jammy-aarch64', 'environment': {'KOLLA_CONFIG_STRATEGY': 'COPY_ALWAYS'}, 'volumes': ['/etc/kolla/fluentd/:/var/lib/kolla/config_files/:ro', '/etc/localtime:/etc/localtime:ro', '/etc/timezone:/etc/timezone:ro', 'kolla_logs:/var/log/kolla/', 'fluentd_data:/var/lib/fluentd/data/'], 'dimensions': {}}}) changed: [ost64] => (item={'key': 'fluentd', 'value': {'container_name': 'fluentd', 'group': 'fluentd', 'enabled': True, 'image': '192.168.2.59:443/openstack.kolla/fluentd:zed-ubuntu-jammy-aarch64', 'environment': {'KOLLA_CONFIG_STRATEGY': 'COPY_ALWAYS'}, 'volumes': ['/etc/kolla/fluentd/:/var/lib/kolla/config_files/:ro', '/etc/localtime:/etc/localtime:ro', '/etc/timezone:/etc/timezone:ro', 'kolla_logs:/var/log/kolla/', 'fluentd_data:/var/lib/fluentd/data/'], 'dimensions': {}}}) changed: [ost63] => (item={'key': 'fluentd', 'value': {'container_name': 'fluentd', 'group': 'fluentd', 'enabled': True, 'image': '192.168.2.59:443/openstack.kolla/fluentd:zed-ubuntu-jammy-aarch64', 'environment': {'KOLLA_CONFIG_STRATEGY': 'COPY_ALWAYS'}, 'volumes': ['/etc/kolla/fluentd/:/var/lib/kolla/config_files/:ro', '/etc/localtime:/etc/localtime:ro', '/etc/timezone:/etc/timezone:ro', 'kolla_logs:/var/log/kolla/', 'fluentd_data:/var/lib/fluentd/data/'], 'dimensions': {}}}) changed: [ost64] => (item={'key': 'kolla-toolbox', 'value': {'container_name': 'kolla_toolbox', 'group': 'kolla-toolbox', 'enabled': True, 'image': '192.168.2.59:443/openstack.kolla/kolla-toolbox:zed-ubuntu-jammy-aarch64', 'environment': {'ANSIBLE_NOCOLOR': '1', 'ANSIBLE_LIBRARY': '/usr/share/ansible'}, 'privileged': True, 'volumes': ['/etc/kolla/kolla-toolbox/:/var/lib/kolla/config_files/:ro', '/etc/localtime:/etc/localtime:ro', '/etc/timezone:/etc/timezone:ro', '/dev/:/dev/', '/run/:/run/:shared', 'kolla_logs:/var/log/kolla/'], 'dimensions': {}}}) changed: [ost61] => (item={'key': 'kolla-toolbox', 'value': {'container_name': 'kolla_toolbox', 'group': 'kolla-toolbox', 'enabled': True, 'image': '192.168.2.59:443/openstack.kolla/kolla-toolbox:zed-ubuntu-jammy-aarch64', 'environment': {'ANSIBLE_NOCOLOR': '1', 'ANSIBLE_LIBRARY': '/usr/share/ansible'}, 'privileged': True, 'volumes': ['/etc/kolla/kolla-toolbox/:/var/lib/kolla/config_files/:ro', '/etc/localtime:/etc/localtime:ro', '/etc/timezone:/etc/timezone:ro', '/dev/:/dev/', '/run/:/run/:shared', 'kolla_logs:/var/log/kolla/'], 'dimensions': {}}}) changed: [ost62] => (item={'key': 'kolla-toolbox', 'value': {'container_name': 'kolla_toolbox', 'group': 'kolla-toolbox', 'enabled': True, 'image': '192.168.2.59:443/openstack.kolla/kolla-toolbox:zed-ubuntu-jammy-aarch64', 'environment': {'ANSIBLE_NOCOLOR': '1', 'ANSIBLE_LIBRARY': '/usr/share/ansible'}, 'privileged': True, 'volumes': ['/etc/kolla/kolla-toolbox/:/var/lib/kolla/config_files/:ro', '/etc/localtime:/etc/localtime:ro', '/etc/timezone:/etc/timezone:ro', '/dev/:/dev/', '/run/:/run/:shared', 'kolla_logs:/var/log/kolla/'], 'dimensions': {}}}) changed: [ost63] => (item={'key': 'kolla-toolbox', 'value': {'container_name': 'kolla_toolbox', 'group': 'kolla-toolbox', 'enabled': True, 'image': '192.168.2.59:443/openstack.kolla/kolla-toolbox:zed-ubuntu-jammy-aarch64', 'environment': {'ANSIBLE_NOCOLOR': '1', 'ANSIBLE_LIBRARY': '/usr/share/ansible'}, 'privileged': True, 'volumes': ['/etc/kolla/kolla-toolbox/:/var/lib/kolla/config_files/:ro', '/etc/localtime:/etc/localtime:ro', '/etc/timezone:/etc/timezone:ro', '/dev/:/dev/', '/run/:/run/:shared', 'kolla_logs:/var/log/kolla/'], 'dimensions': {}}}) changed: [ost61] => (item={'key': 'cron', 'value': {'container_name': 'cron', 'group': 'cron', 'enabled': True, 'image': '192.168.2.59:443/openstack.kolla/cron:zed-ubuntu-jammy-aarch64', 'environment': {'KOLLA_LOGROTATE_SCHEDULE': 'daily'}, 'volumes': ['/etc/kolla/cron/:/var/lib/kolla/config_files/:ro', '/etc/localtime:/etc/localtime:ro', '/etc/timezone:/etc/timezone:ro', 'kolla_logs:/var/log/kolla/'], 'dimensions': {}}}) changed: [ost62] => (item={'key': 'cron', 'value': {'container_name': 'cron', 'group': 'cron', 'enabled': True, 'image': '192.168.2.59:443/openstack.kolla/cron:zed-ubuntu-jammy-aarch64', 'environment': {'KOLLA_LOGROTATE_SCHEDULE': 'daily'}, 'volumes': ['/etc/kolla/cron/:/var/lib/kolla/config_files/:ro', '/etc/localtime:/etc/localtime:ro', '/etc/timezone:/etc/timezone:ro', 'kolla_logs:/var/log/kolla/'], 'dimensions': {}}}) changed: [ost64] => (item={'key': 'cron', 'value': {'container_name': 'cron', 'group': 'cron', 'enabled': True, 'image': '192.168.2.59:443/openstack.kolla/cron:zed-ubuntu-jammy-aarch64', 'environment': {'KOLLA_LOGROTATE_SCHEDULE': 'daily'}, 'volumes': ['/etc/kolla/cron/:/var/lib/kolla/config_files/:ro', '/etc/localtime:/etc/localtime:ro', '/etc/timezone:/etc/timezone:ro', 'kolla_logs:/var/log/kolla/'], 'dimensions': {}}}) changed: [ost63] => (item={'key': 'cron', 'value': {'container_name': 'cron', 'group': 'cron', 'enabled': True, 'image': '192.168.2.59:443/openstack.kolla/cron:zed-ubuntu-jammy-aarch64', 'environment': {'KOLLA_LOGROTATE_SCHEDULE': 'daily'}, 'volumes': ['/etc/kolla/cron/:/var/lib/kolla/config_files/:ro', '/etc/localtime:/etc/localtime:ro', '/etc/timezone:/etc/timezone:ro', 'kolla_logs:/var/log/kolla/'], 'dimensions': {}}}) TASK [common : Creating log volume] ****************************************************************************************************************************************** ok: [ost64] ok: [ost61] ok: [ost62] ok: [ost63] TASK [common : Link kolla_logs volume to /var/log/kolla] ********************************************************************************************************************* changed: [ost64] changed: [ost61] changed: [ost62] changed: [ost63] TASK [common : Flush handlers] *********************************************************************************************************************************************** RUNNING HANDLER [common : Restart fluentd container] ************************************************************************************************************************* changed: [ost63] changed: [ost64] changed: [ost62] changed: [ost61] RUNNING HANDLER [common : Restart kolla-toolbox container] ******************************************************************************************************************* changed: [ost62] changed: [ost61] changed: [ost63] changed: [ost64] RUNNING HANDLER [common : Initializing toolbox container using normal user] ************************************************************************************************** fatal: [ost62]: FAILED! => {"changed": false, "cmd": ["docker", "exec", "-t", "kolla_toolbox", "ansible", "--version"], "delta": "0:00:00.064846", "end": "2023-11-19 21:46:19.187519", "msg": "non-zero return code", "rc": 1, "start": "2023-11-19 21:46:19.122673", "stderr": "Error response from daemon: Container 34d4dcc029d807cb70061bcab3f21e1980ec2541b6e116764dab22917d1ba602 is restarting, wait until the container is running", "stderr_lines": ["Error response from daemon: Container 34d4dcc029d807cb70061bcab3f21e1980ec2541b6e116764dab22917d1ba602 is restarting, wait until the container is running"], "stdout": "", "stdout_lines": []} fatal: [ost61]: FAILED! => {"changed": false, "cmd": ["docker", "exec", "-t", "kolla_toolbox", "ansible", "--version"], "delta": "0:00:00.170840", "end": "2023-11-19 21:46:19.383867", "msg": "non-zero return code", "rc": 1, "start": "2023-11-19 21:46:19.213027", "stderr": "Error response from daemon: Container fbe3a84809b7b5e23dbc84e896735bcc8c72fbd300b53637061bd305a6bd45eb is restarting, wait until the container is running", "stderr_lines": ["Error response from daemon: Container fbe3a84809b7b5e23dbc84e896735bcc8c72fbd300b53637061bd305a6bd45eb is restarting, wait until the container is running"], "stdout": "", "stdout_lines": []} fatal: [ost63]: FAILED! => {"changed": false, "cmd": ["docker", "exec", "-t", "kolla_toolbox", "ansible", "--version"], "delta": "0:00:00.422087", "end": "2023-11-19 21:46:19.579842", "msg": "non-zero return code", "rc": 1, "start": "2023-11-19 21:46:19.157755", "stderr": "Error response from daemon: Container 2b8c1c77cd75d8780ad358407178d0e8d431e22885fc0f58ae1e08e746928d9d is restarting, wait until the container is running", "stderr_lines": ["Error response from daemon: Container 2b8c1c77cd75d8780ad358407178d0e8d431e22885fc0f58ae1e08e746928d9d is restarting, wait until the container is running"], "stdout": "", "stdout_lines": []} fatal: [ost64]: FAILED! => {"changed": false, "cmd": ["docker", "exec", "-t", "kolla_toolbox", "ansible", "--version"], "delta": "0:00:00.693630", "end": "2023-11-19 21:46:19.859925", "msg": "non-zero return code", "rc": 1, "start": "2023-11-19 21:46:19.166295", "stderr": "unable to upgrade to tcp, received 409", "stderr_lines": ["unable to upgrade to tcp, received 409"], "stdout": "", "stdout_lines": []} [View Less]

1 1

[release] Release countdown for week R-19, Nov 20-24
by Herve Beraud 17 Nov '23

17 Nov '23

Development Focus ----------------- We are now past the Caracal-1 milestone. Teams should now be focused on feature development. General Information ------------------- Our next milestone in this development cycle will be Caracal-2, on January 11, 2024. This milestone is when we freeze the list of deliverables that will be included in the 2024.1 Caracal final release, so if you plan to introduce new deliverables in this release, please propose a change to add an empty deliverable file in the … [View More]

1 0

[kolla-ansible][cinder]Backend problems
by Franck VEDEL 17 Nov '23

17 Nov '23

Hi, I come back to a point that caused me a big problem, because I would like to understand something that I did not do correctly. I have a lab with an Openstack (2023.1, kolla-ansible, ubuntu 22-04, 2 nodes) and to show that it works, I start with an LVM backend. Everything is working. I'm adding a Ceph (Pacific) cluster and want to switch from LVM backend to CEPH. If we edit the globals.yml file and make the changes, then the "deploy" command, the LVM backend is still in the list of backends.… [View More]

2 2

[kolla][masakari] Deprecating Masakari Support in Kolla-Ansible
by Michał Nasiadka 17 Nov '23

17 Nov '23

Hello, Since the Kolla-Ansible CI jobs for Masakari using 2023.2 have been failing [1] due to some time - we are deprecating Masakari support in Kolla/Kolla-Ansible. As I can see - even the OpenStack bot patches have not been merged in 2023.2 branch [2]. If there is anybody willing to go the extra mile of reviving Masakari stable/2023.2 branch - please reach out - ideally by commenting on the deprecation patch in Gerrit [3]. [1]: https://zuul.opendev.org/t/openstack/builds?job_name=kolla-… [View More]

1 0

[neutron] Drivers meeting cancelled next two weeks
by Brian Haley 17 Nov '23

17 Nov '23

Hello Neutrinos: Due to the lack of agenda, Friday's drivers meeting is cancelled. Have a nice weekend! Also canceling next week's since with the US Thanksgiving holiday we will likely not have quorum. -Brian

1 0

openstack: how can you remove volumen from postgres database on openstack controller?
by kjme001＠gmail.com 17 Nov '23

17 Nov '23

Hello, I have a problem with the volume, I can't delete it, it's still in the deleting state how can you remove volumen from postgres database on openstack controller? Thank you for your help

1 0

[neutron] How to divide a provider network into address segments for different projects to use
by 韩光宇 16 Nov '23

16 Nov '23

Hi, I have a victoria cluster. And all node have two nic. Same to neutron doc[1], one nic is management interface, other is provider interface. Assuming provider network is same as the example in the Neutron deployment doc, which is the 203.0.113.0/24 with gateway 203.0.113.1. I hope use different address segment for different project. For example: project_A: 203.0.113.11,203.0.113.30 project_B: 203.0.113.31,203.0.113.60 project_C: 203.0.113.61,203.0.113.90 I am currently considering … [View More]

1 0

[Glance] Cancelling Weekly Meeting - 16th Nov
by Mridula Joshi 16 Nov '23

16 Nov '23

Hello All, Cancelling today's weekly meeting as most of the team members are not around for the meeting. See you next week ! Thanks, Mridula Joshi

1 0