- openstack-discuss - lists.openstack.org

[horizon] Cancelling next weekly meeting on 7th June
by vishal manchanda 04 Jun '23

04 Jun '23

Hello Team, As agreed, during the last weekly meeting, we are canceling our next weekly meeting on 7th June. I am on vacation for next complete week with limited or no access to internet. Please reach out to horizon core team if need any help. Thanks & regards, Vishal Manchanda

1 0

[charms] OpenStack Charms 2023.1 (Antelope) release is now available
by Peter Matulis 02 Jun '23

02 Jun '23

The 2023.1 (Antelope) release of the OpenStack Charms is now available. Please see the release notes for full details: https://docs.openstack.org/charm-guide/latest/release-notes/2023.1-antelope… == Highlights == * OpenStack Antelope OpenStack Antelope is now supported on Ubuntu 22.04 LTS (via UCA) and Ubuntu 23.04 natively. * New charm: ironic-dashboard This new charm integrates the Ironic Dashboard into the OpenStack Dashboard. * Service user password rotation The keystone, mysql-innodb-cluster, and rabbitmq-server charms have gained actions to assist with rotating the passwords of OpenStack service users. Two actions are provided for each of these charms (to list usernames and rotate their passwords). * New features for the ironic-conductor charm The ironic-conductor charm has acquired a few new abilities. It can now enable hardware specific options in the Ironic Conductor service. It also now supports custom timeouts for when requests are made to download install images. * Documentation updates Regular improvements and bug fixes. A new page on Network spaces was landed. == OpenStack Charms team == The OpenStack Charms team can be contacted via real time chat: https://chat.charmhub.io/charmhub/channels/openstack-charms The Juju user forum is also popular for diagnosing technical issues: https://discourse.charmhub.io/c/juju/ == Thank you == Lots of thanks to the 24 contributors below who squashed bugs, enabled new features, and improved the documentation! Alex Kavanagh Arif Ali Bas de Bruijne Billy Olsen Chris MacNaughton Corey Bryant Dmitrii Shcherbakov Edward Hope-Morley Felipe Reyes Frode Nordahl Gabriel Cocenza Guillaume Boutry Hemanth Nakkina James Page Jorge Merlino Liam Young Marcus Boden Martin Kalcok Neil Campbell Olivier Dufour-Cuvillier Peter Matulis Simon Dodsley Tiago Pasqualini Trent Lloyd -- OpenStack Charms Team

1 0

[nova] hw:numa_nodes question
by hai wu 02 Jun '23

02 Jun '23

Is there any concern to enable 'hw:numa_nodes=1' on all flavors, as long as that flavor can fit into one numa node?

4 18

RDO Ice Cream Social at OpenInfra Summit
by Amy Marrich 02 Jun '23

02 Jun '23

Join members of the community for ice cream after the Marketplace Mixer on Wednesday at Soft Peaks in Gastown! Soft Peaks is known for using organic milk and their unique topics! For those with dairy related dietary needs who register we will have an alternative for you so don't feel left out! https://eventyay.com/events/231a963f

1 1

[neutron] Neutron drivers meeting
by Rodolfo Alonso Hernandez 02 Jun '23

02 Jun '23

Hello Neutrinos: Please remember we have the Neutron drivers meeting today at 14:00 UTC. The agenda [1] has one topic: * https://bugs.launchpad.net/neutron/+bug/2020823: [RFE] Add flavor/service provider support to routers in the L3 OVN plugin See you later. [1]https://wiki.openstack.org/wiki/Meetings/NeutronDrivers

1 0

[Nova] How to (live-) migrate instances in a server-group with affinity to another host?
by Christian Rohmann 01 Jun '23

01 Jun '23

Hello OpenStack-Discuss, I was wondering how I as an admin can (live-)migrate instances for which the user applied a server-group with affinity. Looking at the API ([1]), there is no (obvious) way to migrate multiple instances or a server-group "en bloc". But migrating a single instance out of a group does result in: > [...] > 2023-06-01 12:20:00.489 6910 INFO nova.scheduler.host_manager > [req-01d9 83eb5 9c8353142098 - default default] Host filter ignoring > hosts: > 2023-06-01 12:20:00.490 6910 INFO nova.filters [req-01d9 83eb5 > 9c8353142098 - default default] Filter ServerGroupAffinityFilter > returned 0 hosts > 2023-06-01 12:20:00.491 6910 INFO nova.filters [req-01d9 83eb5 > 9c8353142098 - default default] Filtering removed all hosts for the > request with instance ID '2476cfdd-9315-4bff-ba3e-d3be5874593f'. > Filter results: ['AvailabilityZoneFilter: (start: 10, end: 10)', > 'ComputeFilter: (start: 10, end: 10)', 'ComputeCapabilitiesFilter: > (start: 10, end: 9)', 'ImagePropertiesFilter: (start: 9, end: 9)', > 'ServerGroupAntiAffinityFilter: (start: 9, end: 9)', > 'ServerGroupAffinityFilter: (start: 9, end: 0)'] > [...] Am I missing something here? Or am I just holding this wrong? Regards Christian [1] https://docs.openstack.org/api-ref/compute/?expanded=force-migration-comple…

4 4

openstack/devstack issue
by syed 01 Jun '23

01 Jun '23

Hi, I was building a system i.e. an orchestrator that includes resources like an ubuntu virtual machine, firecracker micro virtual machine, unikraft unikernel and a storage. It seems that openstack/devstack is capable of orchestration of such a heterogeneous system and could be customized according to the specific needs. I, however, am experiencing a lot of issues when including the resources e.g. when i try to create an ubuntu image and launch it, it results in errors that are quite complex to resolve and so i intend to reach out to the experts so as to resolve these issues at hand. Regards

2 1

[ironic][stable] Proposing EOL of ironic project branches older than Wallaby
by Jay Faulkner 01 Jun '23

01 Jun '23

Hi all, Ironic has a large amount of stable branches still in EM. We need to take action to ensure those branches are either retired or have CI repaired to the point of being usable. Specifically, I'm looking at these branches across all Ironic projects: - stable/queens - stable/rocky - stable/stein - stable/train - stable/ussuri - stable/victoria In lieu of any volunteers to maintain the CI, my recommendation for all the branches listed above is that they be marked EOL. If someone wants to volunteer to maintain CI for those branches, they can propose one of the below paths be taken instead: 1 - Someone volunteers to maintain these branches, and also report the status of CI of these older branches periodically on the Ironic whiteboard and in Ironic meetings. If you feel strongly that one of these branches needs to continue to be in service; volunteering in this way is how to save them. 2 - We seriously reduce CI. Basically removing all tempest tests to ensure that CI remains reliable and able to merge emergency or security fixes when needed. In some cases; this still requires CI fixes as some older inspector branches are failing *installing packages* in unit tests. I would still like, in this case, that someone volunteers to ensure the minimalist CI remains happy. My intention is to let this message serve as notice and a waiting period; and if I've not heard any response here or in Monday's Ironic meeting (in 6 days), I will begin taking action on retiring these branches. This is simply a start; other branches (including bugfix branches) are also in bad shape in CI, but getting these retired will significantly reduce the surface area of projects and branches to evaluate. I know it's painful to drop support for these branches; but we've provided good EM support for these branches for a long time and by pruning them away, we'll be able to save time to dedicate to other items. Thanks, Jay Faulkner

3 5

Add netapp storage in edge site | Wallaby | DCN
by Swogat Pradhan 01 Jun '23

01 Jun '23

Hi, I have a DCN setup and there is a requirement to use a netapp storage device in one of the edge sites. Can someone please confirm if it is possible? And if so then should i add the parameters in the edge deployment script or the central deployment script. Any suggestions? With regards, Swogat Pradhan

2 10

[blazar] Meeting cancelled today
by Pierre Riteau 01 Jun '23

01 Jun '23

Hello, I am unable to run the IRC meeting today, let's cancel. Best wishes, Pierre Riteau (priteau)

1 0

problem with zun not available console in horizon
by МАКАРОВ МАКС 01 Jun '23

01 Jun '23

1 0

CRITICAL! RabbitMQ PackageCloud repos will be not more available from today - affected Openstack-ansible
by Maroš Varchola 01 Jun '23

01 Jun '23

From today, the PackageCloud repos will be not more available from today. Official information: https://github.com/rabbitmq/rabbitmq-server/discussions/8386 BUG on launchpad: https://bugs.launchpad.net/openstack-ansible/+bug/2021410 -- S pozdravom/Yours Sincerely, Maroš Varchola +421 950 401 060 Astrová 6116/2, 071 01 Michalovce, Slovakia marosvarchola(a)sunray.sk ---- Táto správa bola digitálne podpísaná PGP certifikátom/ This message was digitally signed by PGP certificate

5 7

[neutron] New Yoga, Zed and 2023.1 releases
by Rodolfo Alonso Hernandez 01 Jun '23

01 Jun '23

Hello Neutrinos: Please check the new releases proposals for Yoga, Zed and 2023.1: * https://review.opendev.org/c/openstack/releases/+/885030 * https://review.opendev.org/c/openstack/releases/+/885031 * https://review.opendev.org/c/openstack/releases/+/885033 If you find something wrong please comment on the patch. Regards.

1 0

[horizon][stable] [release] Proposal to make stable/stein as EOL
by vishal manchanda 01 Jun '23

01 Jun '23

Hi all, As discussed in yesterday's Horizon weekly meeting[1] on 2023-05-31, I want to announce that the Horizon team decided to move the stable/stein branch as EOL. Consider this mail as an official announcement of that. The gate for horizon stable/stein is failing for the last few months [2]. I would like to know if anyone still wants to keep this branch to be open otherwise, I will propose an EOL patch for this branch. Thanks & Regards, Vishal Manchanda [1] https://meetings.opendev.org/irclogs/%23openstack-horizon/%23openstack-hori… [2] https://review.opendev.org/q/project:openstack%252Fhorizon+branch:stable%25…

1 0

Question About BGP Dynamic Routing, Floating IP, and SNAT
by Alex 31 May '23

31 May '23

Hi Everyone, Hope you are all doing well. I'm a beginner to Openstack and Neutron and now run into an issue about SNAT and shared floating IP. I've already deployed a neutron network which use BGP to announce floating IP to PE (Provider Edge router), and everything works as expected when I assigned the public floating IP (e.g., 123.0.0.10/24) to VMs. But when I tried to use floating IP port-forwarding function with floating IP 123.0.0.20/24 and rule (internal_ip 10.10.10.10, internal_port 5555, external_port 64000), and assign a private IP (10.10.10.10/24) to a VM. The floating IP 123.0.0.20 won't be advertised through BGP. May I have some suggestions about how could I get this fixed, or the neutron just won't work this way? FYI, 1. Per my understanding, the port_forwardings rule will make the port acts like a SNAT role and forward any packets that reached to it with destination 123.0.0.20:64000 to the private IP 10.10.10.10/24. 2. The IP address could be reached in the neutron network. 3. PE IP address, CE IP address, and floating IP gateway are using the same subnet A and subnet pool (192.168.123.0/24), while floating IP belongs to subnet B and subnet pool (123.0.0.0/24), both subnets belong to provider network. 4. Only floating IP that assigned to the specific VM will be advertised to PE through BGP 5. Floating IP that assigned to port of a router in the neutron network won't be advertised, even the IP is activated and is reachable internally. Sincerely, Alex

1 0

[ironic] retirement of old bugfix branches
by Riccardo Pittau 31 May '23

31 May '23

Hello everyone! We're going to remove old bugfix branches in the next few weeks, all bugfix branches that are older than 6 months are officially EoL. This includes: - for ironic bugfix/18.0 bugfix/18.1 bugfix/19.0 bugfix/20.2 bugfix/21.0 bugfix/21.2 - for ironic-inspector bugfix/10.7 bugfix/10.9 bugfix/10.12 bugfix/11.0 bugfix/11.2 -for ironic-python-agent bugfix/8.0 bugfix/8.1 bugfix/8.3 bugfix/8.6 bugfix/9.0 bugfix/9.2 Thanks! Ciao Riccardo

1 0

openstack backup volume - error with rootwrap
by garcetto 31 May '23

31 May '23

goodmorning, using kolla-openstack zed cluster, cinder backend is nfs, cinder-backup is another nfs too. when i try to do backup: #openstack volume backup create 43e97a6d-c965-4127-8334-df5b5e8e8a05 (on cinder-backup container) (/var/log/cinder-backup.log) " ERROR oslo_messaging.rpc.server Command: sudo cinder-rootwrap /etc/cinder/rootwrap.conf chown 42407 /var/lib/cinder/mnt/6c827b655049ba4f069fd5f103620555/volume-20f3c72c-0b57-4500-b552-5056d12fd9c7 2023-05-31 12:37:37.551 7 ERROR oslo_messaging.rpc.server Exit code: 1 2023-05-31 12:37:37.551 7 ERROR oslo_messaging.rpc.server Stdout: '' 2023-05-31 12:37:37.551 7 ERROR oslo_messaging.rpc.server Stderr: "/bin/chown: changing ownership of '/var/lib/cinder/mnt/6c827b655049ba4f069fd5f103620555/volume-20f3c72c-0b57-4500-b552-5056d12fd9c7': Invalid argument\n" 2023-05-31 12:37:37.551 7 ERROR oslo_messaging.rpc.server " could anyone give me advice how to proceed? thank you for your time.

3 3

[kolla-ansible][zed] nfs as backend for nova
by garcetto 31 May '23

31 May '23

good afternoon, it is a clear doc or tutorial on how to configure an nfs share as backend storage for nova root vm volumes? (find for ceph but not for nfs) thank you

1 0

Affinity Group in Open Stack
by Adivya Singh 31 May '23

31 May '23

Hi Guys, Anything i can check on this , more from the server logs and the switch logs Packet drops when using trex traffic generator when device under test and traffic generator are not in same compute node But if we launch the instance using affinity and traffic generator and client on the same node , it works fine Regards Adivya Singh

1 0

[openstack-helm] Storyboard cleanup
by Vladimir Kozhukalov 31 May '23

31 May '23

Dear Openstack-helmers, Minor announcement about OSH Storyboard. During May/2023 I have been putting some effort into cleaning up the Storyboard. More than 50 stories have been reviewed, verified and updated as merged or invalid. Now we still have 44 active stories in the OSH project group and I am going to clean them up even more. Also the infra team helped us to unlink 3 retired OSH projects from the OSH Storyboard project group. So now only active projects openstack-helm, openstack-helm-infra and openstack-helm-images are in the project group. -- Best regards, Kozhukalov Vladimir

1 0

Cinder Bug Report 2023-05-31
by Sofia Enriquez 31 May '23

31 May '23

Hello Argonauts, Cinder Bug Meeting Etherpad <https://etherpad.opendev.org/p/cinder-bug-squad-meeting> *Medium* - Creating a snapshot failed by schema validation when its description contains a new line control character <https://bugs.launchpad.net/cinder/+bug/2021909>. - *Status:* Unassigned. I'm kind of lost on this one if any Argonaut would like to give it a look. - Cached images duplicated per host. <https://bugs.launchpad.net/cinder/+bug/2020733> - *Status:* Unassigned. - HPE 3par: Unable to create clones of replicated vol. <https://bugs.launchpad.net/cinder/+bug/2021941> - *Status*: Fix proposed to master. <https://review.opendev.org/c/openstack/cinder/+/884594> - NetApp ONTAP enhanced instance creation using file copy API should allow use of DNS name for NFS share <https://bugs.launchpad.net/cinder/+bug/2021741>. - *Status*: Unassigned. Is this related to https://bugs.launchpad.net/cinder/+bug/2020733? - NetApp ONTAP driver does not include snapshot-<uuid> files for capacity calculations of provisioned_capacity_gb <https://bugs.launchpad.net/cinder/+bug/2021746>. - *Status*: Unassigned. - *Low* - Using NetApp ONTAP file copy for copy offload needs volume provider_location set. <https://bugs.launchpad.net/cinder/+bug/2021739> - *Status:* Unassigned. Cheers -- Sofía Enriquez she/her Software Engineer Red Hat PnT <https://www.redhat.com> IRC: @enriquetaso @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com>

1 0

[cinder] Midcycle-1 Status (31st May)
by Rajat Dhasmana 31 May '23

31 May '23

Hello Argonauts, As you know we had planned our first midcycle of 2023.2 Bobcat cycle on 31st May, 2023. I created an etherpad[1] around a month ago and have been providing constant reminders in every cinder meeting about adding topics. At this point, no topic has been added which makes me believe that we don't require a midcycle discussion. I will wait till today EOD to see if any new topics are added, and if not, we will continue with our usual video+IRC (end of the month) meeting[2]. [1] https://etherpad.opendev.org/p/cinder-bobcat-midcycles [2] https://etherpad.opendev.org/p/cinder-bobcat-meetings Thanks Rajat Dhasmana

1 1

[Cinder][LVM backend] LVM vg backed by a shared LUN
by wodel youchi 31 May '23

31 May '23

Hi, The examples I could find on the internet using LVM as backend for Cinder, they expose a local disk using lvm via Cinder. I did this configuration and I am wondering if it's correct, especially from a "simultaneous access" point of view. I have an iSCSI target backed by targetcli that exposes a LUN to my compute nodes. I did configure the iscsi connexion manually on each one of them and they all see the LUN, then on one of them I created the cinder-volumes VG (the other nodes can see the modifications), then I configured Cinder with lvm backend using this VG and it worked. I created some volumes on it without issues using my account. But what about when there are multiple tenants that try to create multiple volumes on it, is this configuration safe? Regards.

3 2

[largescale-sig] Next meeting: May 31, 8utc
by Thierry Carrez 31 May '23

31 May '23

Hi everyone, The Large Scale SIG will be meeting this Wednesday in #openstack-operators on OFTC IRC, at 8UTC, our APAC+EU-friendly time. I will be chairing. You can doublecheck how that UTC time translates locally at: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230531T08 Feel free to add topics to the agenda: https://etherpad.opendev.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez

1 1

[kolla][cinder] cinder containers api, volume, backup unhealthy
by Oliver Weinmann 30 May '23

30 May '23

Hi, after replacing my control nodes with new nodes (all bare-metal) somehow the cinder containers are no longer starting. I checked the logs on one of the control nodes and I see this in the api-eror.log: 2023-05-30 21:31:36.350636 Timeout when reading response headers from daemon process 'cinder-api': /var/www/cgi-bin/cinder/cinder-wsgi 2023-05-30 21:31:37.827101 mod_wsgi (pid=22): Failed to exec Python script file '/var/www/cgi-bin/cinder/cinder-wsgi'. 2023-05-30 21:31:37.827168 mod_wsgi (pid=22): Exception occurred processing WSGI script '/var/www/cgi-bin/cinder/cinder-wsgi'. 2023-05-30 21:31:37.828005 Traceback (most recent call last): 2023-05-30 21:31:37.828046 File "/var/www/cgi-bin/cinder/cinder-wsgi", line 52, in <module> 2023-05-30 21:31:37.828053 application = initialize_application() 2023-05-30 21:31:37.828058 File "/var/lib/kolla/venv/lib/python3.6/site-packages/cinder/wsgi/wsgi.py", line 44, in initialize_application 2023-05-30 21:31:37.828063 coordination.COORDINATOR.start() 2023-05-30 21:31:37.828068 File "/var/lib/kolla/venv/lib/python3.6/site-packages/cinder/coordination.py", line 86, in start 2023-05-30 21:31:37.828071 self.coordinator.start(start_heart=True) 2023-05-30 21:31:37.828075 File "/var/lib/kolla/venv/lib/python3.6/site-packages/tooz/coordination.py", line 689, in start 2023-05-30 21:31:37.828078 super(CoordinationDriverWithExecutor, self).start(start_heart) 2023-05-30 21:31:37.828083 File "/var/lib/kolla/venv/lib/python3.6/site-packages/tooz/coordination.py", line 426, in start 2023-05-30 21:31:37.828086 self._start() 2023-05-30 21:31:37.828090 File "/var/lib/kolla/venv/lib/python3.6/site-packages/tooz/drivers/etcd3gw.py", line 224, in _start 2023-05-30 21:31:37.828093 self._membership_lease = self.client.lease(self.membership_timeout) 2023-05-30 21:31:37.828098 File "/var/lib/kolla/venv/lib/python3.6/site-packages/etcd3gw/client.py", line 122, in lease 2023-05-30 21:31:37.828111 json={"TTL": ttl, "ID": 0}) 2023-05-30 21:31:37.828116 File "/var/lib/kolla/venv/lib/python3.6/site-packages/etcd3gw/client.py", line 88, in post 2023-05-30 21:31:37.828123 resp.reason 2023-05-30 21:31:37.828154 etcd3gw.exceptions.ConnectionTimeoutError: Gateway Time-out All other containers are working just fine. Even the cinder_scheduler container works fine. So far I have tried the following: remove the cinder containers including its volume from one control node mariadb_recovery Reboot all control nodes. kolla-ansible reconfigure --tags cinder,nova Any help is highly appreciated. Cheers, Oliver

2 1