August 2023 - openstack-discuss - lists.openstack.org

[ptls][tc] OpenStack User Survey Updates
by Allison Price 29 Aug '23

29 Aug '23

Hi Everyone, Like Helena mentioned last week, we are closing the 2023 OpenStack User Survey in a few weeks and will then open the 2024 OpenStack User Survey. At this time, we want to offer the project teams and TC the opportunity to update your project specific questions that appear at the end of the survey. As a reminder, for the project-specific questions, these appear if a survey taker selects your project in their deployment and TC questions appear to all survey takers. If you and your team would like to update the question, please let me know by Friday, August 18. I know that this is a holiday time for many, so if any team needs some extra time, just let me know. I am also able to share the existing questions with any team that needs a refresher on what is currently in the survey. In the meantime, please continue to promote openstack.org/usersurvey to anyone (and everyone!) you know who is running OpenStack or planning to in the future. We want to get as much feedback as we possibly can. Cheers, Allison

7 24

[all][elections][ptl][tc] Combined PTL/TC 2024.1 cycle Election Nominations Last Days
by Tony Breeds 29 Aug '23

29 Aug '23

A quick reminder that we are in the last hours for declaring PTL and TC candidacies. Nominations are open until Aug 30, 2023 23:45 UTC. If you want to stand for election, don't delay, follow the instructions at[1] to make sure the community knows your intentions. Make sure your nomination has been submitted to the openstack/election repository and approved by election officials. All members of the community are encouraged to confirm their email address and opt in to the CIVS election as described at: https://governance.openstack.org/election/#electorate Election statistics[2]: Nominations started @ 2023-08-16 23:45:00 UTC Nominations end @ 2023-08-30 23:45:00 UTC Nominations duration : 14 days, 0:00:00 Nominations remaining : 1 day, 22:20:09 Nominations progress : 86.21% --------------------------------------------------- Projects[1] : 48 Projects with candidates : 18 ( 37.50%) Projects with election : 0 ( 0.00%) --------------------------------------------------- Need election : 0 () Need appointment : 30 (Adjutant Barbican Blazar Cinder Cloudkitty Cyborg Ec2_Api Glance Heat Horizon Keystone Kuryr Manila Mistral Monasca Octavia OpenStack_Helm Openstack_Chef Puppet_OpenStack Rally Sahara Senlin Skyline Storlets Sunbeam Swift Tacker Telemetry Trove Venus) --------------------------------------------------- TC Candidates : 4 (4 Required) =================================================== Stats gathered @ 2023-08-29 01:24:51 UTC This means that with approximately 2 days left, 30 projects will be deemed leaderless. In this case the TC will oversee PTL selection as described by [3]. Thank you, [1] https://governance.openstack.org/election/#how-to-submit-a-candidacy [2] Any open reviews at https://review.opendev.org/q/project:openstack/election+is:open+file:candid… have not been factored into these stats. [3] https://governance.openstack.org/resolutions/20141128-elections-process-for… Yours Tony.

1 0

[nova][election] Self-nomination for 2024.1 Nova PTL
by Sylvain Bauza 28 Aug '23

28 Aug '23

Hey Nova and Placement folks, Yet again, I'm asking you to put myself on the Nova and Placement PTL seat. For the exact same reasons than last time (see my previous nomination e-mail), I was convinced to run again for this position, which hopefully will be the last one (despite having already said it once). Challenges are still upfront. Our gate is still coughing every single day and despite the excellent work that a very few awesome people did on stabilizing and which helped improving the situation (kudos to those who will recognize themselves), we are still urging to fix the most common patterns. As a PTL, I'll ensure to keep the energy to chase those issues and identify them so as a team we can fight them. Another concern to me is the reviewing pace. While we're continuing to deliver solid reviews on feature proposals and patches, our team isn't much evolving and we need fresh blood. In order to be able to deliver things, we need to ensure that we properly recognize those who dedicate a portion of their daytime to help others by providing valuable feedback (and I stress on the fact that this feedback *has to* be valuable in order to by worthy). As a PTL, I'll continue to encourage people to express their thoughts and concerns into Gerrit comments so that we are able to count on. The last challenge I have to mention here is the release cadence. Now that more people are getting noticed of the SLURP cadence, we'll be awaited on delivering our next SLURP release, which will be 2024.1 (Caracal). I'll take special attention to that, ensuring that our skip-level-upgrade process we have in Nova will conveniently work with Caracal and that our release notes correctly include the upgrade steps for those who skip 2023.2 (Bobcat). I'll just finish on a last word. While I really appreciated acting as a PTL for the last 4 cycles, I'd be more than happy if someone would like to step up and compete for the seat. I personnally prefer expansion over attrition and one of my favourite tasks is mentoring. Thanks, -Sylvain

1 0

Red Hat Open stack external IP pool change
by Adivya Singh 28 Aug '23

28 Aug '23

Hi Team, Does any body have seen this issue, I am running RHOSP 16 2023-08-28 13:24:29Z [overcloud-Networks-xtd6lzqc6hhx-ExternalNetwork-ssk732o4rze6.ExternalSubnet]: UPDATE_FAILED NotSupported: resources.ExternalSubnet: Update to properties cidr of ExternalSubnet (OS::Neutron::Subnet) is not supported. 2023-08-28 13:24:29Z [overcloud-Networks-xtd6lzqc6hhx-ExternalNetwork-ssk732o4rze6]: UPDATE_FAILED Resource UPDATE failed: NotSupported: resources.ExternalSubnet: Update to properties cidr of ExternalSubnet (OS::Neutron::Subnet) is not supported. 2023-08-28 13:24:30Z [overcloud-Networks-xtd6lzqc6hhx.ExternalNetwork]: UPDATE_FAILED NotSupported: resources.ExternalNetwork.resources.ExternalSubnet: Update to properties cidr of ExternalSubnet (OS: : Neutron: : Subnet) is not supported. 2023-08-28 13:24:30Z [overcloud-Networks-xtd6lzqc6hhx]: UPDATE_FAILED Resource UPDATE failed: NotSupported: resources.ExternalNetwork.resources.ExternalSubnet: Update to properties cidr of ExternalSubnet (OS: : Neutron: : Subnet) is not supported. 2023-08-28 13:24:30Z [Networks]: UPDATE_FAILED NotSupported: resources.Networks.resources.ExternalNetwork.resources.ExternalSubnet: Update to properties cidr of ExternalSubnet (OS: : Neutron: : Subnet) is not supported. 2023-08-28 13:24:30Z [overcloud]: UPDATE_FAILED Resource UPDATE failed: NotSupported: resources.Networks.resources.ExternalNetwork.resources.ExternalSubnet: Update to properties cidr of ExternalSubnet (OS: : Neutron: : Subnet) is not supported. I delete the interface from OVS bridge and restart the OVS services and re push the templates Or I change the File manually, Configure any floating ip range , Add the route manually , and restart the Network services Any thought on this Regards Adivya Singh

1 0

[neutron] Bug Deputy Report August 21 - 27
by Nurmatov Mamatisa 28 Aug '23

28 Aug '23

Hi, Below is the week summary of bug deputy report for last week. Undecided bugs needs further triage. Details: High ---- - https://bugs.launchpad.net/neutron/+bug/2032738 - [os-ken] [CI] Jobs setting up os-ken from pypi instead of patch in review - Fixed: https://review.opendev.org/c/openstack/os-ken/+/892452 - Assigned to Yatin Karel - https://bugs.launchpad.net/neutron/+bug/2032817 - OVN: Distributed FIP packet drops when provider network MTU exceeds tenant network MTU - Confirmed - Unassigned - https://bugs.launchpad.net/neutron/+bug/2033090 - Able to change vnic type on a bound port - In progress: https://review.opendev.org/c/openstack/neutron/+/892815 - Assigned to Jakub Libosvar Medium ------ - https://bugs.launchpad.net/neutron/+bug/2032169 - OVN synchronized too many segments - In progress: https://review.opendev.org/c/openstack/neutron/+/891930 - Assigned to Zhou Heng - https://bugs.launchpad.net/neutron/+bug/2032183 - [CI] UT py311 job failing, "libmysqlclient-dev" missing - Fixed: https://review.opendev.org/c/openstack/neutron/+/892142 - Assigned to Rodolfo Alonso - https://bugs.launchpad.net/neutron/+bug/2032765 - [L3][DVR]disable ARP response for vlan networks on compute node - Confirmed - Unassigned Low --- - https://bugs.launchpad.net/neutron/+bug/2032770 - [OVN] port creation with --enable-uplink-status-propagation does not work with OVN mechanism driver - Confirmed - Unassigned - https://bugs.launchpad.net/neutron/+bug/2032929 - OVN security group logging burst limit has an unexpected value for stateless security groups - In progress: https://review.opendev.org/c/openstack/neutron/+/892648 - Assigned to Elvira García Ruiz - https://bugs.launchpad.net/neutron/+bug/2033203 - Quality of Service (QoS) in Neutron - Confirmed - Unassigned Undecided --------- - https://bugs.launchpad.net/neutron/+bug/2032973 - Neutron is not creating DNS records when recreating an instance with the same floating IP - https://bugs.launchpad.net/neutron/+bug/2033179 - Using .local as TLD in dns testing is breaking some scenarios Invalid ------ - https://bugs.launchpad.net/neutron/+bug/2033083 - [OVN] The router GW is "restoring" the NAT rule that disables SNAT - Ironic bug Best regards, Mamatisa Nurmatov Advanced Software Technology Lab / Cloud Technologies Research

1 0

TripleO deployment over IPV6
by Kushagr Gupta 26 Aug '23

26 Aug '23

Hi Team, We were trying to perform IPV6-based deployment of TripleO. We are following the link: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16… As per our environment, we set the "ipv6_address_mode" to "dhcpv6-stateful" and tried undercloud deployment. It was successful. But when we try node introspection, openstack is not providing an IP that will be used for PXE booting the system. We have enabled PXE booting on the IPV6 network. On Dell machines, we get the following error: "PXE-E16: No offer received." For your reference, the undercloud file which we used is attached. We also tried to find the communication happening on the br-ctlplane interface when the machine tries to boot over IPV6 PXE boot. I am attaching those tcpdump records as well. We are unable to find the MAC address of our machines. *Questions:* 1. Is it even possible to perform tripleO deployment with IPV6? 2. Do we need to do some extra settings, so that our baremetal machines can be PXE booted? Thanks and Regards

3 9

Live migration between centos and ubuntu compute nodes
by Jim Kilborn 25 Aug '23

25 Aug '23

Openstack peers: I am migrating our production openstack environment from centos7 to ubuntu. I am on the train release currently, so I can have that release on both centos7 and ubuntu 18 The issue is that I need to live migrate the vms if it's possible. When I try, I get an error on the source compute node (centos 7). Live Migration failure: Cannot check QEMU binary /usr/libexec/qemu-kvm: No such file or directory: libvirtError: Cannot check QEMU binary /usr/libexec/qemu-kvm: No such file or directory Any ideas how to get around this until I get my vms migrated? Maybe create a link on the ubuntu 18 host? I'm sure I am not the first to leave centos 7 for ubuntu Thanks for any help on this.

2 1

[keystone] outstanding reviews for federation fix
by Mohammed Naser 25 Aug '23

25 Aug '23

Hi there, Can I please get eyes on https://review.opendev.org/q/I665b7e0234650ba07e0d030a2d442d6599d0888a ? We’ve been carrying this down for too long and it’s a very simple fix. Thanks, Mohammed

2 1

[neutron] Neutron drivers meeting cancelled
by Rodolfo Alonso Hernandez 25 Aug '23

25 Aug '23

Hello Neutrinos: Due to the lack of agenda [1], today's meeting is cancelled. Have a nice weekend. [1]https://wiki.openstack.org/wiki/Meetings/NeutronDrivers

1 0

[release] Release countdown for week R-5, Aug 28 - Sep 01
by Thierry Carrez 25 Aug '23

25 Aug '23

Development Focus ----------------- We are getting close to the end of the 2023.2 Bobcat cycle! Next week on August 31st is the bobcat-3 milestone, also known as feature freeze. It's time to wrap up feature work in the services and their client libraries, and defer features that won't make it to the 2024.1 Caracal cycle. General Information ------------------- This coming week is the deadline for client libraries: their last feature release needs to happen before "Client library freeze" on August 31st. Only bugfix releases will be allowed beyond this point. When requesting those library releases, you can also include the stable/2023.2 branching request with the review. As an example, see the "branches" section here: https://opendev.org/openstack/releases/src/branch/master/deliverables/pike/… August 31st is also the deadline for feature work in all OpenStack deliverables following the cycle-with-rc model. To help those projects produce a first release candidate in time, only bugfixes should be allowed in the master branch beyond this point. Any feature work past that deadline has to be raised as a Feature Freeze Exception (FFE) and approved by the team PTL. Finally, feature freeze is also the deadline for submitting a first version of your cycle-highlights. Cycle highlights are the raw data that helps shape what is communicated in press releases and other release activity at the end of the cycle, avoiding direct contacts from marketing folks. See https://docs.openstack.org/project-team-guide/release-management.html#cycle… for more details. Upcoming Deadlines & Dates -------------------------- Bobcat-3 milestone (feature freeze): August 31st (R-5 week) RC1 deadline: September 14th (R-3 week) Final RC deadline: September 28th (R-1 week) Final 2023.2 Bobcat release: October 4th, 2023 -- Thierry Carrez (ttx)

1 0