September 2022 - openstack-discuss

OpenStack PTG, Neutron schedule
by Rodolfo Alonso Hernandez 21 Sep '22

21 Sep '22

Hello Neutrinos: This is the poll to vote for the Neutron schedule during the next OpenStack PTG. The goal is to have at least 3 hours per day, from Monday to Thursday. The second poll is to decide the operator hour for Neutron [2], according to [3]. I'll keep the polls open until next Monday 26 Sep. Then I'll reserve the room in [3]. Thank you for participating. [1]https://doodle.com/meeting/participate/id/dwmlAVra [2]https://doodle.com/meeting/participate/id/eZVRoxge [3]https://ptg.opendev.org/ptg.html

1 0

[cinder] Bug Report 09-21-2022
by Sofia Enriquez 21 Sep '22

21 Sep '22

This is a bug report from 09-14-2022 to 09-21-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Medium - https://bugs.launchpad.net/cinder/+bug/1989514 "NFS volume snapshot does not update volume attachment format to qcow2." Fix proposed to master. Low - https://bugs.launchpad.net/cinder/+bug/1989730 "Dell PowerMax - Optimized SL should be assigned when retyping a volume to a default volume type." Fixed proposed to master. - https://bugs.launchpad.net/cinder/+bug/1990136 " Dell PowerFlex: Failed to attach a volume when using self-signed Certificates." Fixed proposed to master. - https://bugs.launchpad.net/cinder/+bug/1990134 "Tatlin driver does not set project id for temp volumes." Fixed proposed to master. -- 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

[ironic] Looking for downstream users of bugfix/* branches
by Jay Faulkner 21 Sep '22

21 Sep '22

Hey all, Ironic releases intermediate bugfix releases during the cycle. These are consumed by some packagers and standalone users of Ironic. Today, using Ironic as an example, we have 4 active bugfix branches: - bugfix/21.0 and bugfix/20.2 are between yoga and zed - bugfix/19.0 is between xena and yoga - bugfix/18.1 is between wallaby and xena We are considering cleaning up some of the older bugfix branches, to reduce stable maintenance load -- but we would like to poll you all first: Is anyone consuming these releases downstream? If so, which ones and why? This will be useful input to whatever action we decide to take! Thanks, Jay Faulkner

2 1

[ironic] Proposing Harald Jensas to metalsmith-core
by Iury Gregory 21 Sep '22

21 Sep '22

Hello ironic-cores and metalsmith-cores, I would like to propose Harald Jensas for metalsmith-core. During the Zed Cycle he had a lot of reviews for the project [1], in yoga he contributed a lot to the project [2]. Looking at all the releases in stackalytics he is #6 in commits [3] and reviews [4]. Please vote with +1/-1 (till Sep 25) [1] https://www.stackalytics.io/?release=zed&module=opendev.org/openstack/metal… [2] https://www.stackalytics.io/?release=yoga&module=opendev.org/openstack/meta… [3] https://www.stackalytics.io/?release=all&module=opendev.org/openstack/metal… [4] https://www.stackalytics.io/?release=all&module=opendev.org/openstack/metal… -- *Att[]'s* *Iury Gregory Melo Ferreira * *MSc in Computer Science at UFCG* *Ironic PTL Yoga and Zed Cycle* *Senior Software Engineer at Red Hat Brazil* *Social*: https://www.linkedin.com/in/iurygregory *E-mail: iurygregory(a)gmail.com <iurygregory(a)gmail.com>*

5 4

[tacker][ptg] Virtual PTG Planning
by Yasufumi Ogawa 21 Sep '22

21 Sep '22

Hi Tacker team, I've updated the etherpad for our antelope PTG [1] as I mentioned in the previous IRC meeting. Please add your topics if you have any suggestions for the next release. [1] https://etherpad.opendev.org/p/tacker-antelope-ptg Cheers, Yasufumi

1 0

[keystone] Changing user password_hash directly in database
by 박경원 21 Sep '22

21 Sep '22

1 0

CFP Open - Ubuntu Summit 2022
by T. Nichole Williams 21 Sep '22

21 Sep '22

Greetings everyone, Your friendly neighborhood Kata Community Manager checking in to let you all know that the call for presentations[2] is now open for Ubuntu Summit 2022[1]. The event will be held from November 7-9, 2022 in Prague, Czech Republic. The Ubuntu Summit (FKA the Ubuntu Developer Summit) will include a series of talks, workshops, panels and Q&A covering a broad range of topics to appeal not only to developers, but anyone involved in open source. The event is organized into the following tracks: • Ubuntu Desktop • Community • Data Science & Data Platforms • Application Ecosystem • Infrastructure Though in-person attendance is preferred, there is a virtual option for those unable to travel. CFP will close September 30, 2002, so if you have a presentation (or workshop) on OpenStack ready to go, please send it in! Regards, T. Nichole Williams Technical Community Manager | Kata Containers Twitter: OGtrilliams GitHub: OGtrilliams IRC: PagliaccisCloud [1] https://events.canonical.com/event/2/ [2] https://events.canonical.com/event/2/abstracts/

1 0

[tripleo] Gate blocker NODE_FAILURES when running tripleo-ci-centos-9-scenario010-standalone
by Amol Kahat 20 Sep '22

20 Sep '22

Hello All, Description of problem: NODE_FAILURE when running tripleo-ci-centos-9-scenario010-standalone job. We have been seeing this failure[1] since 09/17. Logs are not present so it's hard to say what is the root cause of this issue. This job uses nodeset: single-centos-9-node-nested-virt - so assumption is that it's the nest-virt nodeset [1] https://zuul.openstack.org/builds?job_name=tripleo-ci-centos-9-scenario010-… Thanks, -- *Amol Kahat* Software Engineer *Red Hat India Pvt. Ltd. Pune, India.* akahat(a)redhat.com B764 E6F8 F4C1 A1AF 816C 6840 FDD3 BA6C 832D 7715

3 2

Query about networking-onos for newer OpenStack releases
by Aditya Sathish 20 Sep '22

20 Sep '22

Hello! I am trying to integrate an SDN controller with our lab's OpenStack network. Currently, we have already deployed a version of ONOS to serve our needs and I have been following the SONA project which uses the networking-onos ML2 plugin with OpenStack. However, it seems that the networking-onos project has been retired since the Train release. Is there any way I can get ONOS to work with OpenStack Yoga? If not, what is the go-to way to integrate an SDN controller with OpenFlow support with Neutron?? Any help will be much appreciated. Regards, Aditya.

2 1

[ironic] Check PTG topics
by Iury Gregory 20 Sep '22

20 Sep '22

Hello ironicers, The Antelope PTG is in a a few weeks, we had the idea to check the PTG topics (so we can group some before setting the final schedule) Please vote in the doodle [1] for a time where we can discuss a bit o/ Feel free to add topics to our etherpad! [2] Thanks! [1] https://doodle.com/meeting/participate/id/dBL8ZZXa [2] https://etherpad.opendev.org/p/ironic-antelope-ptg -- *Att[]'s* *Iury Gregory Melo Ferreira * *MSc in Computer Science at UFCG* *Ironic PTL * *Senior Software Engineer at Red Hat Brazil* *Social*: https://www.linkedin.com/in/iurygregory *E-mail: iurygregory(a)gmail.com <iurygregory(a)gmail.com>*

1 2

Re: RE : [neutron][nova][ipv6]instance on compute node not getting dhcpv6
by Neil Jerram 20 Sep '22

20 Sep '22

They may be outdated now, but I wonder if any of the steps described at https://projectcalico.docs.tigera.io/networking/openstack/ipv6 would help you? In particular, given that you have no route, perhaps you need the accept_ra config. Best wishes, Neil On Tue, Sep 20, 2022 at 9:12 AM Michael Hazan <mhazan(a)mandint.org> wrote: > Hello, > > The 3 nodes are running Ubuntu 20.04 and using libvirt. The instance are > Ubuntu or debian based. The openstack virtual network is configured with > both a v4 and a v6 dhcp pool. The instance should be getting both v4 and v6 > (on the same interface) but the instance that are hosted on the compute > node only get v4. If i run the dhclient -6 -r the instance actually get > it’s ipv6 but it’s wrongly configured with a /128 (instead of 64) and no > route. > > > > Michael > > > > *De : *Lajos Katona <katonalala(a)gmail.com> > *Envoyé le :*mardi, 20 septembre 2022 09:39 > *À : *mhazan(a)mandint.org > *Cc : *openstack-discuss(a)lists.openstack.org > *Objet :*Re: [neutron][nova][ipv6]instance on compute node not getting > dhcpv6 > > > > Hi, > > Do you have some more details of your environment, which backend you use? > OVS? > > Your VMs have both IPv4 and v6 addresses and you mean that they got IPv4 > as expected? > > > > Lajos > > > > <mhazan(a)mandint.org> ezt írta (időpont: 2022. szept. 19., H, 16:19): > > Hello all, > > i manage a small openstack cluster installed via Ubuntu package, it has > been upgraded since the day of Newton and currently running Victoria. it > started as a single node with the basic services installed, later a > dedicated storage node and compute node were added. after upgrading to > victoria, any instance that boot on the dedicated compute node start up > but fails to get it's global ipv6 via stateful dhcp6, only > linklocal(fe80) ip is shown by the instance. The ipv6 is created in > openstack, the dhcpv4 works and there are no issue if the instance boot > on the "old" all in one node. i can manually allocate (by editing the > instance network config file) the ipv6 config and it works. any pointer > as to what could cause this issue ? > > BR, Michael > > >

2 1

[kuryr] Antelope PTG topics
by Maysa De Macedo Souza 20 Sep '22

20 Sep '22

Hello, The Antelope PTG is a few weeks away and if you have any topics to discuss in the Kuryr session, feel free to include it in the etherpad[1]. Cheers, Maysa Macedo. [1] https://etherpad.opendev.org/p/kuryr-antelope-ptg

1 0

[neutron][nova][ipv6]instance on compute node not getting dhcpv6
by mhazan＠mandint.org 20 Sep '22

20 Sep '22

Hello all, i manage a small openstack cluster installed via Ubuntu package, it has been upgraded since the day of Newton and currently running Victoria. it started as a single node with the basic services installed, later a dedicated storage node and compute node were added. after upgrading to victoria, any instance that boot on the dedicated compute node start up but fails to get it's global ipv6 via stateful dhcp6, only linklocal(fe80) ip is shown by the instance. The ipv6 is created in openstack, the dhcpv4 works and there are no issue if the instance boot on the "old" all in one node. i can manually allocate (by editing the instance network config file) the ipv6 config and it works. any pointer as to what could cause this issue ? BR, Michael

3 2

[neutron] dhcp/dnsmasq issue after upgrade to queens
by Benedikt Trefzer 19 Sep '22

19 Sep '22

Hello out there I'm stuck with neutron not starting any dnsmasq processes after upgrading neutron to the queens release (yes I know this is an elderly version ;)) Details: I see errors from neutron-dhcp-agent (on the dhcp host and on the controller node for the neutron-rpc-server): ValueError: Unrecognized attribute(s) 'binding:host_id' But I'm pretty sure this is a followup of the directory /var/lib/neutron/dhcp ($state_path) beeing almost empty (only empty directories named by the networks beeing there, which are rebuild by the neutron-dhcp-agent if deleted). I'm further do not see any ports in the DB for dhcp. Which eventually explains why the state files for dnsmasq are missing. So now I'm stuck: - Which agent/daemon should create the ports for the dnsmasq process ? The installation should launch two dhcp processes on two router nodes (HA setup). Which is also correctly shown using neutron dhcp-agent-list-hosting-net which shows two dhcp-agents up and running ! Any hints how to solve are appreciated ! Greetings Benedikt

1 0

[CloudKitty] Virtual PTG October 2022
by Rafael Weingärtner 19 Sep '22

19 Sep '22

Hello everyone, As you probably heard our next PTG will be held virtually in October. We've marked October 17, at 14:00-16:00 UTC [1]. We already have a CloudKitty meeting organized for this day. Therefore, it seems the most practical choice. However, if you guys would like some other dates and/or time, just let me know. The room we selected is called "Essex". I've also created an etherpad [2] to collect ideas/topics for the PTG sessions. If you have anything to discuss, please don't hesitate to write it there. [1] https://ptg.opendev.org/ptg.html [2] https://etherpad.opendev.org/p/oct2022-ptg-cloudkitty -- Rafael Weingärtner

1 0

[neutron] bug deputy report September 12th to 18th
by Miguel Lavalle 19 Sep '22

19 Sep '22

Hi, Here's this week's bugs deputy report: Requires follow up ============== High ==== https://bugs.launchpad.net/neutron/+bug/1989480 [OVN] Neutron server floods logs with hash ring messages on startup. Assigned to Lucas Gomes. Proposed fix: https://review.opendev.org/c/openstack/neutron/+/857463 Medium ====== https://bugs.launchpad.net/neutron/+bug/1989460 [ovn-octavia-provider] HealthMonitor event received on port deleted. Assigned to Fernando Royo. Proposed fix: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/857365 https://bugs.launchpad.net/neutron/+bug/1989979 Unexpected number of DHCP interfaces for metadata proxy. Assigned to MIguel Lavalle (mlavalle) RFE === Incomplete ======== https://bugs.launchpad.net/neutron/+bug/1989986 changing dns_domain on the charm does not propagate to ovn

1 0

Container not appearing
by Lee, Vincent Z 17 Sep '22

17 Sep '22

Hi all, I am facing issues with making containers to appear on my gui. I have managed to run a container, however, it is not showing it on horizon dashboard. [cid:3761763c-eed0-4912-af5f-4a4e91d7da1f] When I tried to create a container, it will be successfully [cid:067852ef-34b3-40c5-a590-757a192eb556] [cid:56d30ba1-c65b-4dfa-ab91-41e872332e29] Best, Vincent

2 1

[all][tc] What's happening in Technical Committee: summary 2022 Sept 16: Reading: 5 min
by Ghanshyam Mann 16 Sep '22

16 Sep '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Sept 15. Most of the meeting discussions are summarized in this email. Most of the meeting discussions are summarized in this email. Meeting logs are available @ https://meetings.opendev.org/meetings/tc/2022/tc.2022-09-15-15.00.log.html * Next TC weekly meeting will be on Sept 22 Thursday at 15:00 UTC, feel free to add the topic on the agenda[1] by Sept 21. 2. What we completed this week: ========================= * Switched release management to distributed leadership [2] * Retired panko projects [3] * Add Keystone OpenID Connect charm to OpenStack charms [4] * 2023.1 cycle testing runtime: 2023.1 cycle testing runtime is defined and merged [5], As feedback by the Horizon team, I am updating Node.JS version also to 18.0[6]. As discussed in last cycle PTG, we are moving to the python version testing template to unversioned name[7] and will control/update the new stable branch and cycle changes in central place in openstack-zuul-jobs repo. With that we do not need to update the each project repo on every release by release bot patches. 3. Activities In progress: ================== TC Tracker for Zed cycle ------------------------------ * Zed tracker etherpad includes the TC working items[8], four are completed and others items are in-progress. Open Reviews ----------------- * Two open reviews for ongoing activities[9]. 2023.1 cycle Technical Election (TC + PTL) -------------------------------------------------- We will have election voting for TC and Ironic project. The voting is open until Sept 19. Please follow the election official emails for actions/things to do. We had 9 projects missed the PTL nomination but good news is that we found the leaders for all the 9 projects now[10]. As next step, TC will be discussing the PTL appointment. 2023.1 cycle TC PTG planning ------------------------------------ Updates on PTG planning: * "TC + Leader interaction" sessions is scheduled for Oct 17 Monday 15-17 UTC[10], * I have created the TC PTG etherpad to collect the topic[11]. * I sent email about the 'Operator Hours' slots in this PTG, please check and reserve the operator hour slot for your project[12] 2021 User Survey TC Question Analysis ----------------------------------------------- No update on this. The survey summary is up for review[13]. Feel free to check and provide feedback. Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[14]15]. Project updates ------------------- * None. 4. How to contact the TC: ==================== If you would like to discuss or give feedback to TC, you can reach out to us in multiple ways: 1. Email: you can send the email with tag [tc] on openstack-discuss ML[16]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [17] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://review.opendev.org/c/openstack/governance/+/855276 [3] https://review.opendev.org/c/openstack/governance/+/850005 [4] https://review.opendev.org/c/openstack/governance/+/857493 [5] https://review.opendev.org/c/openstack/governance/+/854375 [6] https://review.opendev.org/c/openstack/governance/+/856927 [7] https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/856903 [8] https://etherpad.opendev.org/p/tc-zed-tracker [9] https://review.opendev.org/q/projects:openstack/governance+status:open [10] https://etherpad.opendev.org/p/2023.1-leaderless [10] https://lists.openstack.org/pipermail/openstack-discuss/2022-September/0303… [11] https://etherpad.opendev.org/p/tc-2023-1-ptg [12] https://lists.openstack.org/pipermail/openstack-discuss/2022-September/0303… [13] https://review.opendev.org/c/openstack/governance/+/836888 [14] https://etherpad.opendev.org/p/zuul-config-error-openstack [15] http://lists.openstack.org/pipermail/openstack-discuss/2022-May/028603.html [16] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [17] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[release] Release countdown for week R-2, Sep 19 - 23
by Előd Illés 16 Sep '22

16 Sep '22

Development Focus ----------------- At this point we should have release candidates (RC1 or recent intermediary release) for all the Zed deliverables. Teams should be working on any release-critical bugs that would require another RC or intermediary release before the final release. Actions ------- Early in the week, the release team will be proposing stable/zed branch creation for all deliverables that have not branched yet, using the latest available Zed release as the branch point. If your team is ready to go for creating that branch, please let us know by leaving a +1 on these patches. If you would like to wait for another release before branching, you can -1 the patch and update it later in the week with the new release you would like to use. By the end of the week the release team will merge those patches though, unless an exception is granted. Once stable/zed branches are created, if a release-critical bug is detected, you will need to fix the issue in the master branch first, then backport the fix to the stable/zed branch before releasing out of the stable/zed branch. After all of the cycle-with-rc projects have branched we will branch devstack, grenade, and the requirements repos. This will effectively open them up for 2023.1 Antelope development, though the focus should still be on finishing up Zed until the final release. For projects with translations, watch for any translation patches coming through and merge them quickly. A new release should be produced so that translations are included in the final Zed release. Finally, now is a good time to finalize release notes. In particular, consider adding any relevant "prelude" content. Release notes are targeted for the downstream consumers of your project, so it would be great to include any useful information for those that are going to pick up and use or deploy the Zed version of your project. Upcoming Deadlines & Dates -------------------------- Final RC deadline: September 29th, 2022 (R-1 week) Final Zed release: October 5th, 2022 Virtual PTG: October 17-21, 2022 Előd Illés irc: elodilles

1 0

[all] Deprecated Zuul queue syntax
by Clark Boylan 16 Sep '22

16 Sep '22

Hello, Zuul deprecated declaring shared queues at a pipeline level with release 4.1.0 [0]. Zuul's current plan is to stop accepting this form of configuration with a future 7.0.0 release. More details on what needs to change can be found in Zuul's reminder notice on the Zuul mailing list [1]. I expect we have about a month before the v7 release which should give us plenty of time to fix this. If we don't fix this before the v7 release the expected fallout will be that these project branches will not have any pipelines defined, which means no Zuul jobs will run against that project branch until the configs are updated. I've marked this for everyone because 98 repositories are affected, and I'm not sure listing them all in the subject would be productive. Here is the list of affected repos: openstack/adjutant openstack/ansible-collection-kolla openstack/ansible-role-collect-logs openstack/ansible-role-tripleo-modify-image openstack/barbican openstack/barbican-tempest-plugin openstack/barbican-ui openstack/blazar openstack/blazar-tempest-plugin openstack/ceilometer openstack/cinderlib openstack/cloudkitty openstack/cloudkitty-tempest-plugin openstack/cyborg-tempest-plugin openstack/designate openstack/designate-dashboard openstack/designate-tempest-plugin openstack/devstack-gate openstack/ec2-api openstack/ec2api-tempest-plugin openstack/freezer openstack/freezer-tempest-plugin openstack/heat openstack/heat-dashboard openstack/heat-tempest-plugin openstack/horizon openstack/ironic openstack/ironic-inspector openstack/ironic-lib openstack/ironic-prometheus-exporter openstack/ironic-python-agent openstack/ironic-tempest-plugin openstack/kayobe openstack/kayobe-config openstack/kayobe-config-dev openstack/kolla openstack/kolla-ansible openstack/kuryr openstack/magnum openstack/magnum-tempest-plugin openstack/manila openstack/manila-tempest-plugin openstack/masakari openstack/masakari-monitors openstack/mistral openstack/mistral-tempest-plugin openstack/monasca-api openstack/monasca-common openstack/monasca-events-api openstack/monasca-log-api openstack/monasca-tempest-plugin openstack/murano openstack/murano-tempest-plugin openstack/networking-generic-switch openstack/octavia openstack/octavia-tempest-plugin openstack/openstack-chef openstack/os-net-config openstack/os-win openstack/oswin-tempest-plugin openstack/paunch openstack/project-config openstack/puppet-pacemaker openstack/puppet-tripleo openstack/python-designateclient openstack/python-ironicclient openstack/python-saharaclient openstack/python-tripleoclient openstack/python-troveclient openstack/sahara openstack/sahara-tests openstack/senlin openstack/senlin-tempest-plugin openstack/solum openstack/solum-tempest-plugin openstack/telemetry-tempest-plugin openstack/tenks openstack/tripleo-ci openstack/tripleo-ci-health-queries openstack/tripleo-common openstack/tripleo-heat-templates openstack/tripleo-quickstart openstack/tripleo-quickstart-extras openstack/tripleo-upgrade openstack/trove openstack/trove-tempest-plugin openstack/vitrage openstack/vitrage-tempest-plugin openstack/watcher openstack/watcher-tempest-plugin openstack/zaqar openstack/zaqar-tempest-plugin openstack/zun openstack/zun-tempest-plugin windmill/windmill windmill/windmill-backup x/neutron-classifier x/vmware-nsx I'll go ahead and push changes to windmill/* and x/* as those are leftovers from splitting things up into tenants and haven't ended up in their own tenants yet. But it would be great if OpenStack can work on cleaning up this deprecated syntax in the OpenStack repos. I've attached a file with a listing that includes more details for each repo (branches and specific config files) to make it easier for people to find where the old syntax is located so that it can be replaced with the new syntax. [0] https://zuul-ci.org/docs/zuul/latest/releasenotes.html#relnotes-4-1-0-depre… [1] https://lists.zuul-ci.org/pipermail/zuul-discuss/2022-May/001801.html

2 2

[kolla] [train] Horizon port security group management fails
by Albert Braden 16 Sep '22

16 Sep '22

We're running kolla train and we're seeing an apparent bug when we try to add or remove security groups on a port. We see error "Failed to update port <ID>". It works fine in CLI; we only see this in Horizon. Is this a known bug, or are we doing something wrong?

6 19

[requirements][adjutant][magnum][sahara][venus][relmgmt] Requirements Freeze Exception requests
by Előd Illés 15 Sep '22

15 Sep '22

Hi, I would like to ask for a Requirements Freeze Exception for the following deliverables (as their former releases were done from broken gates, thus needed some extra fix): python-adjutantclient 0.11.0 [1] python-magnumclient 4.0.0 [2] python-saharaclient 4.0.2 [3] python-venusclient 1.0.1 [4] [1] https://review.opendev.org/c/openstack/releases/+/857736 [2] https://review.opendev.org/c/openstack/releases/+/856853 [3] https://review.opendev.org/c/openstack/releases/+/856858 [4] https://review.opendev.org/c/openstack/releases/+/856381 Előd irc: elodilles

2 1

[neutron] Drivers meeting - Friday 15.09.2022 - cancelled
by Lajos Katona 15 Sep '22

15 Sep '22

Hi Neutron Drivers! Due to the lack of agenda, let's cancel tomorrow's drivers meeting. See You on the meeting next week. Lajos Katona (lajoskatona)

1 0

[all][ptl][release] Zed release critical issue with oslo.db 12.1.0
by Előd Illés 15 Sep '22

15 Sep '22

Hi, With the latest oslo.db 12.1.0 release it seems multiple repositories are broken (see the corresponding requirements patch [1] for details, and probably there are more, that are not tested within requirements repository). The patch that introduces the break [2] "is necessary for oslo.db and openstack applications in general to be able to run on SQLAlchemy 2.0" according to patch author. Since we are after the 3rd milestone of Zed, we have very limited time to figure out what to do. The 2 options are: 1) fix every broken repository to work with oslo.db 12.1.0 as far as we know this is quite impossible as for some repositories the already existing fixes took almost a cycle to be implemented and there are still undiscovered bugs around this. (we don't know if this is really true, or probably there are cases where it's easy to fix) 2) revert the breaking change [2] and do another release in oslo.db now without it (and add it back after Zed release & release oslo.db with it as soon as possible in Antelope cycle) as far as we understand this does not cause any issue for those who already adapted to oslo.db 12.1.0, so this should not be painful Based on the above Release team is opting toward the 2nd option. Please let us know your opinion! [1] https://review.opendev.org/c/openstack/requirements/+/855153/ [2] https://review.opendev.org/c/openstack/oslo.db/+/804775 Thanks, Előd

8 18

[all][elections][ptl][tc] Reminder to opt-in to CIVS polling
by Jay Bryant 15 Sep '22

15 Sep '22

All, Apologies for the additional e-mail in your in-box, but wanted to make sure that everyone saw the reminder to opt-in to voting with CIVS. ACTION IS REQUIRED to receive the voting ballot from CIVS: you must opt-in to receiving email communications from CIVS. More information and the form to do so can be found at https://civs1.civs.us/cgi-bin/opt_in.pl Polling will start TODAY and this operation needs to be completed before then. Happy Voting! - Jay Bryant (jungleboyj)

1 1