July 2024 - openstack-discuss - lists.openstack.org

when deleting an instance, its volume is not deleted
by kjme001＠gmail.com 08 Jul '24

08 Jul '24

I have the following problem, when deleting an instance, its volume is not deleted along with it, the volume remains and I then have to execute the command to detach the volume from the non-existent instance and then delete it. I don't know what could be causing this, the volume should probably be deleted together with the instance being deleted Thank you for your help

4 3

[neutron] Bug deputy July 01 - July 07
by Lajos Katona 08 Jul '24

08 Jul '24

Hi Neutrinos, This is the bug report from the first week of July: *High*: * https://bugs.launchpad.net/neutron/+bug/2071818 ("over 4096 resubmit actions" error occurs when there are ~250 neutron routers on a provider network) ** In progress: https://review.opendev.org/c/openstack/neutron/+/923391 * https://bugs.launchpad.net/neutron/+bug/2072154 (Port status goes BUILD when migrating non-sriov instance in sriov setting. ) ** In Progress: https://review.opendev.org/c/openstack/neutron/+/923467 * https://bugs.launchpad.net/neutron/+bug/2072466 (FWaaS does not apply rules to routers under DVR agents) ** In Progress: https://review.opendev.org/c/openstack/neutron-fwaas/+/922963 *Medium*: * https://bugs.launchpad.net/neutron/+bug/2071920 (The periodic workers service should run only ``PeriodicWorker`` instances) ** In Progress: https://review.opendev.org/c/openstack/neutron/+/923500 *Invalid*: * https://bugs.launchpad.net/neutron/+bug/2071721 ([OVN] unshelve not working when referenced by allowed address ) Best Wishes Lajos Katona (lajoskatona)

1 0

attach both virtio-scsi and virtio-blk to an instance
by Jiatong Shen 08 Jul '24

08 Jul '24

Hello, I am searching whether it is possible to use both virtio-scsi and virtio-blk at the same time for one instance. I knew it was possible to use each of them separately. I have this requirement because virtio-blk is not possible to support as many as devices like virtio-scsi, but we still want to keep virtio-blk for performance reasons and for legacy instances. Thank you for help. -- Best Regards, Jiatong Shen

2 2

Kolla-Ansible Issues
by Alexandra Rong 06 Jul '24

06 Jul '24

Hello OpenStack-Ansible team, We are students in Germany studying Business Informatics. Currently, we have a project where we need to build an OpenStack environment using Kolla-Ansible. Our goal is to use Gnocchi and CloudKitty to gather metrics on the usage of the VMs in OpenStack. We tried following the official Kolla-Ansible deployment guide but encountered issues starting Kolla-Ansible, as shown in the attached screenshots. Could you possibly help us? Best regards, Felix and Alexandra Ansible.cfg: Error: All-in-one:

5 4

[openstack-helm] SQLAlchemy 2.0 support
by Mohammed Naser 06 Jul '24

06 Jul '24

Hi everyone! It seems like our db-init jobs are broken with the latest version of OpenStack because it doesn’t work with SQLAlchemy 2.0 2024-05-31 03:21:34,290 - OpenStack-Helm DB Init - INFO - Got DB root connection 2024-05-31 03:21:34,290 - OpenStack-Helm DB Init - INFO - Using /etc/keystone/keystone.conf as db config source 2024-05-31 03:21:34,292 - OpenStack-Helm DB Init - INFO - Trying to load db config from database:connection 2024-05-31 03:21:34,292 - OpenStack-Helm DB Init - INFO - Got config from /etc/keystone/keystone.conf 2024-05-31 03:21:34,331 - OpenStack-Helm DB Init - INFO - Tested connection to DB @ percona-xtradb-haproxy.openstack.svc.cluster.local:3306 as root 2024-05-31 03:21:34,332 - OpenStack-Helm DB Init - INFO - Got user db config 2024-05-31 03:21:34,332 - OpenStack-Helm DB Init - CRITICAL - Could not create database keystone Traceback (most recent call last): File "/tmp/db-init.py", line 112, in <module> root_engine.execute("CREATE DATABASE IF NOT EXISTS {0}".format(database)) AttributeError: 'Engine' object has no attribute 'execute' I was wondering if it makes sense to fix this, or if this is something that we should just take the time to simply replace with some sort of simple operator that creates manages/watches database CRs (if one doesn’t exist?) Thanks Mohammed

2 2

[ironic] the fate of ironic-hardware-inventory-recorder-image
by Dmitry Tantsur 05 Jul '24

05 Jul '24

Hi folks! The project in question (https://github.com/metal3-io/ironic-hardware-inventory-recorder-image) was created as part of our effort to allow updating introspection data in ironic-inspector from inside of already running ("active" in the ironic terminology) instances. It is a container image that packages ironic-python-agent in a way that limits its activity to finding ironic-inspector and posting data to it. The initial plans did not happen, ironic-inspector is pending deprecation in favor of ironic's built-in inspection, and the project is unused by anyone in the Metal3 ecosystem. We want to archive and eventually remove it, but we've heard that some members of the ironic community (CERN? CC'ing Arne) are using it. If you do have an interest in this approach, please reach out to me to organize a take-over of the project. Dmitry

4 5

[release] Release countdown for week R-12, Jul 08-12
by Elõd Illés 05 Jul '24

05 Jul '24

Development Focus ----------------- We are now past the Dalmatian-2 milestone, and entering the last development phase of the cycle. Teams should be focused on implementing planned work for the cycle. Now is a good time to review those plans and reprioritize anything if needed based on the what progress has been made and what looks realistic to complete in the next few weeks. General Information ------------------- Looking ahead to the end of the release cycle, please be aware of the feature freeze dates. Those vary depending on deliverable type: * General libraries (except client libraries) need to have their last feature release before Non-client library freeze (August 22nd, 2024). Their stable branches are cut early. * Client libraries (think python-*client libraries) need to have their last feature release before Client library freeze (August 29th, 2024) * Deliverables following a cycle-with-rc model (that would be most services) observe a Feature freeze on that same date, August 29th, 2024. Any feature addition beyond that date should be discussed on the mailing-list and get PTL approval. After feature freeze, cycle-with-rc deliverables need to produce a first release candidate (and a stable branch) before RC1 deadline (September 12th, 2024) * Deliverables following cycle-with-intermediary model can release as necessary, but in all cases before Final RC deadline (September 25th, 2024) Upcoming Deadlines & Dates -------------------------- Non-client library freeze: August 22nd, 2024 (R-6 week) Client library freeze: August 29th, 2024 (R-5 week) Dalmatian-3 milestone: August 29th, 2024 (R-5 week) Előd Illés irc: elodilles @ #openstack-release

1 0

[neutron] Neutron drivers meeting cancelled
by Rodolfo Alonso Hernandez 05 Jul '24

05 Jul '24

Hello Neutrinos: Due to the lack of quorum, today's Neutron drivers meeting will be cancelled. Have a nice weekend.

1 0

[horizon][python-openstackclient] Hypervisor listed in dashboard but not in CLI
by Francesco Di Nucci 05 Jul '24

05 Jul '24

Hello, I am having a strange "error" with an hypervisor. It works and it is shown in Horizon under /Admin/System/System Information/Compute Services/, but it is not listed through the CLI with /openstack hypervisor list/ Any suggestion on how to prevent this? Thanks in advance -- Francesco Di Nucci System Administrator Compute & Networking Service, INFN Naples Email:francesco.dinucci@na.infn.it

1 0

Magnum Caracal: how to use the K8s cluster API instead of Heat driver
by Michel Jouvin 05 Jul '24

05 Jul '24

Hi, In our testing of Caracal Magnum, we saw that the cluster upgrade feature is now disabled for clusters using the Heat driver. There are many good reasons for this explained at [1] and [2] in particular. But I don't see any Magnum documentation of this new approach to K8s cluster provisionning. Is https://vexxhost.github.io/magnum-cluster-api/ the authoritative place? I had a quick look to the URL above but I am not sure I understood what configures Magnum to use Cluster API rather than Heat driver. Is Magnum configured to use one or the other for all clusters it manages? Is it a per cluster choice? How it works to transition from Heat driver to Cluster API, ie how it works if you have existing clusters configured with Heat drivers and if you are creating new ones with Cluster API? Best regards, Michel [1] https://opendev.org/openstack/magnum/commit/2fd3059f3885ff4a14f7f0141016196… (see comments in the code, at line 313) [2] https://vexxhost.com/blog/cluster-api-driver-openstack-magnum/

1 0