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

[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

[manila] Bugsquash event: Jul 10th to 12th
by Carlos Silva 04 Jul '24

04 Jul '24

Hello, zorilla and interested stackers! We are going to have our first bugsquash of this cycle in the next week. For this event, we will be focusing on pursuing closure for bugs that are currently in progress. - It will start next Wednesday (July 10) and ends on Friday (July 12th). - We will have a kick-off meeting to go over the list of bugs as usual on Wednesday, 14 UTC, and work on assignments if needed. - We will use half of the next upstream weekly meeting to talk about the progress and discuss ongoing reviews. All of the details will be added to the bugsquash etherpad [1]. Looking forward to closing a lot of bugs with your help! [1] https://etherpad.opendev.org/p/manila-dalmatian-m2-bugsquash Regards, carloss

1 0

[CloudKitty] query regarding ElasticSearch usage
by Rafael Weingärtner 04 Jul '24

04 Jul '24

Hello OpenStack community and users of CloudKitty! There have been some discussions in our bi-weekly meetings and vPTG meetings regarding the deprecation and removal of ElasticSearch support as a storage backend. Therefore, this e-mail is to consult/query users regarding ElasticSearch users. If there are no people using it anymore with CloudKitty, we are considering the alternative of removing it and maintaining only the OpenSearch support. We would like to hear back from you guys. Let me know if you are using ElasticSearch, and if you intend to stick with it. Also, do you guys feel the need to improve something in its support in CloudKitty. Thanks in advance for your feedback! -- Rafael Weingärtner

5 5

Magnum issues http requests to other services when internal/admin endpoint is https
by Michel Jouvin 04 Jul '24

04 Jul '24

Hi, We have reconfigured our cloud with a Nginx sever handling TLS in front of every API service, as described in https://docs.openstack.org/security-guide/secure-communication/secure-refer…. Previously we used to have Magnum/Heat/Barbican endpoints using http rather than https (not good!). Since this change, we have seen problems in Magnum (starting in Antelope when we did the change but still present in Caracal) where some "internal" requests to Barbican and Heat are done in http rather than https. We worked around this defining a redirect to https on 497 status code, as documented in Nginx documentation but it is not really satisfying as it means all clients, not only Magnum service, could use http on the https port and get serviced. I remember seing an issue on Launchpad about this issue but forgot the issue number. We were wondering wether it would not be better, at least until the problem is fixed, to define the internal+admin endpoints with http rather than https. According to our tests, it fixes the problem, as expected. Thanks in advance for any thought or experience on this. Best regards, Michel

2 2

[nova] volume information was duplicated when Live Migration failed
by Junya Noguchi (Fujitsu) 04 Jul '24

04 Jul '24

To whom it may concern Hi. I encountered an issue with OpenStack where volume information was duplicated when Live Migration failed. Could you please provide a solution to this issue? [Issue] After a Live Migration failure, when I checked the volume where the error occurred using the 'openstack volume list' command, the following was displayed: +--------------------------------------+-----------------------------------+-----------+------+---------------------------------------------------------------------------------------------------------------------------------------------+ | ID | Name | Status | Size | Attached to | +--------------------------------------+-----------------------------------+-----------+------+---------------------------------------------------------------------------------------------------------------------------------------------+ | 9ba9734f-575e-41de-8bb4-60839388e0ad | | in-use | 10 | Attached to 73c4c6e8-fe34-4f87-9f26-e70b4cc593ba on /dev/vda Attached to 73c4c6e8-fe34-4f87-9f26-e70b4cc593ba on /dev/vda Attached to | | | | | | 73c4c6e8-fe34-4f87-9f26-e70b4cc593ba on /dev/vda Attached to 73c4c6e8-fe34-4f87-9f26-e70b4cc593ba on /dev/vda Attached to | | | | | | 73c4c6e8-fe34-4f87-9f26-e70b4cc593ba on /dev/vda Attached to 73c4c6e8-fe34-4f87-9f26-e70b4cc593ba on /dev/vda Attached to | | | | | | 73c4c6e8-fe34-4f87-9f26-e70b4cc593ba on /dev/vda Attached to 73c4c6e8-fe34-4f87-9f26-e70b4cc593ba on /dev/vda | I expect that the 'Attached to' display should only appear once as there is one volume connected, but it is duplicated for each failed attempt. The versions of OpenStack and nova are as follows: OpenStack Zed $ openstack --version openstack 6.0.0 $ nova --version nova CLI is deprecated and will be a removed in a future release 18.1.0 [Details] The volume display is duplicated under the following conditions: - When Live Migration of an instance fails If the communication between the ports required for Live Migration is closed, Live Migration will fail when executed. $ sudo netstat -tuln | grep 16509 $ The output of nova-compute.log at the time of Live Migration failure is as follows: --- 2024-02-28 17:04:32.119 2785 ERROR nova.virt.libvirt.driver [-] [instance: 521eb55f-535d-4fa7-a27e-447b0bbae9b4] Live Migration failure: unable to connect to server at 'XXXXX.com:16509': Connection refused: libvirt.libvirtError: unable to connect to server at 'XXXXX.com:16509': Connection refused 2024-02-28 17:04:32.119 2785 DEBUG nova.virt.libvirt.driver [-] [instance: 521eb55f-535d-4fa7-a27e-447b0bbae9b4] Migration operation thread notification thread_finished /usr/lib/python3.9/site-packages/nova/virt/libvirt/driver.py:10516 2024-02-28 17:04:32.607 2785 DEBUG nova.virt.libvirt.migration [-] [instance: 521eb55f-535d-4fa7-a27e-447b0bbae9b4] VM running on src, migration failed _log /usr/lib/python3.9/site-packages/nova/virt/libvirt/migration.py:432 2024-02-28 17:04:32.608 2785 DEBUG nova.virt.libvirt.driver [-] [instance: 521eb55f-535d-4fa7-a27e-447b0bbae9b4] Fixed incorrect job type to be 4 _live_migration_monitor /usr/lib/python3.9/site-packages/nova/virt/libvirt/driver.py:10330 2024-02-28 17:04:32.608 2785 ERROR nova.virt.libvirt.driver [-] [instance: 521eb55f-535d-4fa7-a27e-447b0bbae9b4] Migration operation has aborted --- After Live Migration, when I check the volume where the error occurred using the 'openstack volume list' command, the following is displayed: +--------------------------------------+-----------------------------------+-----------+------+---------------------------------------------------------------------------------------------------------------------------------------------+ | ID | Name | Status | Size | Attached to | +--------------------------------------+-----------------------------------+-----------+------+---------------------------------------------------------------------------------------------------------------------------------------------+ | 9ba9734f-575e-41de-8bb4-60839388e0ad | | in-use | 10 | Attached to 73c4c6e8-fe34-4f87-9f26-e70b4cc593ba on /dev/vda Attached to 73c4c6e8-fe34-4f87-9f26-e70b4cc593ba on /dev/vda Attached to | | | | | | 73c4c6e8-fe34-4f87-9f26-e70b4cc593ba on /dev/vda Attached to 73c4c6e8-fe34-4f87-9f26-e70b4cc593ba on /dev/vda Attached to | | | | | | 73c4c6e8-fe34-4f87-9f26-e70b4cc593ba on /dev/vda Attached to 73c4c6e8-fe34-4f87-9f26-e70b4cc593ba on /dev/vda Attached to | | | | | | 73c4c6e8-fe34-4f87-9f26-e70b4cc593ba on /dev/vda Attached to 73c4c6e8-fe34-4f87-9f26-e70b4cc593ba on /dev/vda | '73c4c6e8-fe34-4f87-9f26-e70b4cc593ba on /dev/vda' is displayed as many times as Live Migration failed. The duplicate display did not disappear even after Live Migration was successful. Thanks,

2 2

[kolla-ansible][letsencrypt] containers are running but not getting certificates.
by Jonathan Proulx 03 Jul '24

03 Jul '24

Hi All, I'm trying to do a test multinode deploy using 2023.2 I have letsencrypt_webserver and letsencrypt_lego contsainers running and I'm seeing random traffic in the /var/log/kolla/letsencrypt/letsencrypt-webserver-access.log so fairly confident they're plumbed through to the public internet properly, but I don't seem to be getting certificates. how can I trigger a renewal attempt so I can maybe see what I've screwed up? Thanks, -Jon -- Jonathan Proulx (he/him) Sr. Technical Architect The Infrastructure Group MIT CSAIL

3 6