- openstack-discuss - lists.openstack.org

Migration from linuxbridge to ovs
by Luk 31 Mar '23

31 Mar '23

Hello, Can You share some thoughts/ideas or some clues regarding migration from linux bridge to ovs ? Does this migration is posible without interrupting traffic from VMs ? We have now linuxbridge with l3-ha, and we noticed that for example when doing live migration of VM from linuxbridge baked compute to openvswitch compute is created bridge... inside openvswitch, instead adding qvo device to br-int: Bridge brq91dc40ac-ea datapath_type: system Port qvo84e2bd98-e9 Interface qvo84e2bd98-e9 Port brq91dc40ac-ea Interface brq91dc40ac-ea type: internal After removing the brq91dc40ac-ea from ovs, and hard reboot, the qvo interface is added properly to br-int: Bridge br-int Controller "tcp:127.0.0.1:6633" is_connected: true fail_mode: secure datapath_type: system Port qvo84e2bd98-e9 tag: 1 Interface qvo84e2bd98-e9 Also, before hard reboot, there is no flow for br-int or any other openvswitch bridge regarding this VM/ip. Does anyone have same problems ? Have tried to migrate from lb to ovs ? Openstack version: ussuri OS: ubuntu 20 Regards Lukasz

3 3

[Octavia] moving back to Launchpad
by Gregory Thiemonge 31 Mar '23

31 Mar '23

Hi Folks, During the Antelope PTG, we discussed the move from Storyboard to Launchpad, and in the Bobcat PTG session, we decided to switch at the beginning of the B cycle (now). The Octavia Launchpad [0] is now re-enabled, we are marking all the old entries as Invalid. We don't plan to have an automated migration script, we will duplicate manually the most recent bugs reported in Storyboard (not started bugs). I'm also proposing patches to update the links to the bug tracker in the Octavia projects. Greg [0] https://launchpad.net/octavia

2 1

[kolla-ansible] deploy cinder and glance with multi-backend
by wodel youchi 30 Mar '23

30 Mar '23

Hi, I need to deploy cinder and glance with multi-backend. My experience for now is simple, my deployment is an HCI built on top of ceph storage, and I am using it to store both cinder volumes and glance images. I have some questions if you can help: - can multi-backend be deployed at first run with kolla-ansible, or do I need to do at least two runs? - reading the doc about multi-backend, I saw that the first backend is specified, do I need to remove the creation of the first backend from glabals.yml and put it in a configuration file cinder.conf and glance.conf? In other words, do I have to create all the backends from the config files, or can I still create the first one using globals.yml and the rest from the config files? I hope my question is clear. Regards.

1 0

[neutron][ptg] Today's agenda
by Rodolfo Alonso Hernandez 30 Mar '23

30 Mar '23

Hello Neutrinos: Same as yesterday, we have a packed agenda. Today we'll have the Nova-Neutron meetings, starting at 13UTC. Quick summary: * delete_on_termination for Neutron ports * Blueprint: "Add support for Napatech LinkVirt SmartNICs" * https://bugs.launchpad.net/neutron/+bug/1986003 * ovn-bgp-agent roadmap * neutron-dynamic-routing: Make static scheduler finally the default? See you in a few minutes. Regards.

1 0

[nova][ptg] Today's agenda (Thursday)
by Sylvain Bauza 30 Mar '23

30 Mar '23

Heya again, Yesterday was a very productive day. Thanks folks. Today, we'll have mostly cross-project discussions but we'll also try to discuss about 3 topics : - 13:00 - 14:30 UTC : Nova-Neutron cross-project sessions* in the neutron room (tbd)* - 14:30 - 14:45 UTC : Transition Xena to EM, any concerns ? - 14:45 - 15:00 UTC : break - 15:00 - 15:30 UTC : Glance/Cinder/Nova cross-project session about secure glance Direct URLs *in the glance room (newton)* - 15:30 - 16:30 UTC : Cinder/Nova cross-project session* in the nova room (diablo)* - 16:30 - 16:50 UTC : Discuss the next steps with compute hostname robustification - 16:50 - 16:00 UTC : (tentatively) Instance.name is not persisted and just sub'd by every service calling the object Thanks and enjoy this day. -Sylvain

1 1

Nova undefine secret | openstack | wallaby
by Swogat Pradhan 30 Mar '23

30 Mar '23

Hi, For some reason, i had to redeploy ceph for my hci nodes and then found that the deployment command is giving out the following error: 2023-03-28 01:49:46.709605 | | WARNING | ERROR: Can't run container nova_libvirt_init_secret stderr: error: Failed to set attributes from /etc/nova/secret.xml error: internal error: a secret with UUID bd136bb0-fd78-5429-ab80-80b8c571d821 already defined for use with client.openstack secret 2023-03-28 01:49:46.711176 | 48d539a1-1679-623b-0af7-000000004b45 | FATAL | Create containers managed by Podman for /var/lib/tripleo-config/container-startup-config/step_4 | dcn01-hci-0 | error={"changed": false, "msg": "Failed containers: nova_libvirt_init_secret"} Can you please tell me how I can undefine the existing secret? With regards, Swogat Pradhan

3 5

[oslo][heat][masakari][senlin][venus][all] oslo.db 13.0.0 will remove sqlalchemy-migrate support
by Stephen Finucane 30 Mar '23

30 Mar '23

tl;dr: Projects still relying on sqlalchemy-migrate for migrations need to start their switch to alembic immediately. Projects with "legacy" sqlalchemy-migrated based migrations need to drop them. A quick heads up that oslo.db 13.0.0 will be release in the next month or so and will remove sqlalchemy-migrate support and formally add support for sqlalchemy 2.x. The removal of sqlalchemy-migrate support should only affect projects using oslo.db's sqlalchemy-migrate wrappers, as opposed to using sqlalchemy-migrate directly. For any projects that rely on this functionality, a short-term fix is to vendor the removed code [1] in your project. However, I must emphasise that we're not removing sqlalchemy-migrate integration for the fun of it: it's not compatible with sqlalchemy 2.x and is no longer maintained. If your project uses sqlalchemy-migrate and you haven't migrated to alembic yet, you need to start doing so immediately. If you have migrated to alembic but still have sqlalchemy- migrate "legacy" migrations in-tree, you need to look at dropping these asap. Anything less will result in broken master when we bump upper-constraints to allow sqlalchemy 2.x in Bobcat. I've listed projects in $subject that appear to be using the removed modules. For more advice on migrating to sqlalchemy 2.x and alembic, please look at my previous post on the matter [2]. Cheers, Stephen [1] https://review.opendev.org/c/openstack/oslo.db/+/853025 [2] https://lists.openstack.org/pipermail/openstack-discuss/2021-August/024122.…

3 3

[neutron][ovn] stateless SG behavior for metadata / slaac / dhcpv6
by Ihar Hrachyshka 30 Mar '23

30 Mar '23

Hi all, (I've tagged the thread with [ovn] because this question was raised in the context of OVN, but it really is about the intent of neutron stateless SG API.) Neutron API supports 'stateless' field for security groups: https://docs.openstack.org/api-ref/network/v2/index.html#stateful-security-… The API reference doesn't explain the intent of the API, merely walking through the field mechanics, as in "The stateful security group extension (stateful-security-group) adds the stateful field to security groups, allowing users to configure stateful or stateless security groups for ports. The existing security groups will all be considered as stateful. Update of the stateful attribute is allowed when there is no port associated with the security group." The meaning of the API is left for users to deduce. It's customary understood as something like "allowing to bypass connection tracking in the firewall, potentially providing performance and simplicity benefits" (while imposing additional complexity onto rule definitions - the user now has to explicitly define rules for both directions of a duplex connection.) [This is not an official definition, nor it's quoted from a respected source, please don't criticize it. I don't think this is an important point here.] Either way, the definition doesn't explain what should happen with basic network services that a user of Neutron SG API is used to rely on. Specifically, what happens for a port related to a stateless SG when it trying to fetch metadata from 169.254.169.254 (or its IPv6 equivalent), or what happens when it attempts to use SLAAC / DHCPv6 procedure to configure its IPv6 stack. As part of our testing of stateless SG implementation for OVN backend, we've noticed that VMs fail to configure via metadata, or use SLAAC to configure IPv6. metadata: https://bugs.launchpad.net/neutron/+bug/2009053 slaac: https://bugs.launchpad.net/neutron/+bug/2006949 We've noticed that adding explicit SG rules to allow 'returning' communication for 169.254.169.254:80 and RA / NA fixes the problem. I figured that these services are "base" / "basic" and should be provided to ports regardless of the stateful-ness of SG. I proposed patches for this here: metadata series: https://review.opendev.org/q/topic:bug%252F2009053 RA / NA: https://review.opendev.org/c/openstack/neutron/+/877049 Discussion in the patch that adjusts the existing stateless SG test scenarios to not create explicit SG rules for metadata and ICMP replies suggests that it's not a given / common understanding that these "base" services should work by default for stateless SGs. See discussion in comments here: https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/876692 While this discussion is happening in the context of OVN, I think it should be resolved in a broader context. Specifically, a decision should be made about what Neutron API "means" by stateless SGs, and how "base" services are supposed to behave. Then backends can act accordingly. There's also an open question of how this should be implemented. Whether Neutron would like to create explicit SG rules visible in API that would allow for the returning traffic and that could be deleted as needed, or whether backends should do it implicitly. We already have "default" egress rules, so there's a precedent here. On the other hand, the egress rules are broad (allowing everything) and there's more rationale to delete them and replace them with tighter filters. In my OVN series, I implement ACLs directly in OVN database, without creating SG rules in Neutron API. So, questions for the community to clarify: - whether Neutron API should define behavior of stateless SGs in general, - if so, whether Neutron API should also define behavior of stateless SGs in terms of "base" services like metadata and DHCP, - if so, whether backends should implement the necessary filters themselves, or Neutron will create default SG rules itself. I hope I laid the problem out clearly, let me know if anything needs clarification or explanation. Yours, Ihar

3 6

[Magnum] vPTG
by Jake Yip 29 Mar '23

29 Mar '23

Dear all, Magnum vPTG will be held at Wed 0900 UTC in the Havana Room. Please see etherpad https://etherpad.opendev.org/p/march2023-ptg-magnum for updates Regards, Jake (sorry for duplicates)

1 1

OpenStack 2023.1 Antelope for Ubuntu 22.04 LTS
by Corey Bryant 29 Mar '23

29 Mar '23

The Ubuntu OpenStack team at Canonical is pleased to announce the general availability of OpenStack 2023.1 Antelope on Ubuntu 22.04 LTS (Jammy Jellyfish). Details of the Antelope release can be found at: https://www.openstack.org/software/antelope The Ubuntu Cloud Archive for OpenStack 2023.1 Antelope can be enabled on Ubuntu 22.04 by running the following command: sudo add-apt-repository cloud-archive:antelope The Ubuntu Cloud Archive for 2023.1 Antelope includes updates for: aodh, barbican, ceilometer, cinder, designate, designate-dashboard, dpdk (22.11.1), glance, gnocchi, heat, heat-dashboard, horizon, ironic, ironic-ui, keystone, magnum, magnum-ui, manila, manila-ui, masakari, mistral, murano, murano-dashboard, networking-arista, networking-bagpipe, networking-baremetal, networking-bgpvpn, networking-hyperv, networking-l2gw, networking-mlnx, networking-odl, networking-sfc, neutron, neutron-dynamic-routing, neutron-fwaas, neutron-taas, neutron-vpnaas, nova, octavia, octavia-dashboard, openstack-trove, openvswitch (3.1.0), ovn (23.03.0), ovn-octavia-provider, placement, sahara, sahara-dashboard, senlin, swift, trove-dashboard, vitrage, watcher, watcher-dashboard, zaqar, and zaqar-ui. For a full list of packages and versions, please refer to: https://openstack-ci-reports.ubuntu.com/reports/cloud-archive/antelope_vers… == Reporting bugs == If you have any issues please report bugs using the ‘ubuntu-bug’ tool to ensure that bugs get logged in the right place in Launchpad: sudo ubuntu-bug nova-conductor Thank you to everyone who contributed to OpenStack 2023.1 Antelope! Corey (on behalf of the Ubuntu OpenStack Engineering team)

1 0

(Openstack-Designate) rndc key not getting generated in /etc/designate
by Adivya Singh 29 Mar '23

29 Mar '23

Hi Team, My DNS Server located outside the Open Stack, and i am using below variables in my user_variables.yaml File. But When i ' m running os-desigante-install.yml Playbook, rndc key are not generating in /etc/designate Folder and the playbook fail at the below Task {"msg": "The task includes an option with an undefined variable. The error was: 'dict object' has no attribute 'file'\n\nThe error appears to be in '/etc/ansible/roles/os_designate/tasks/designate_post_install.yml': line 89, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- name: Create Designate rndc key file\n ^ here\n"} - name: Create Designate rndc key file template: src: rndc.key.j2 dest: "{{ item.file }}" owner: "{{ item.owner | default('root') }}" group: "{{ item.group | default('root') }}" mode: "{{ item.mode | default('0600') }}" with_items: "{{ designate_rndc_keys }}" when: designate_rndc_keys is defined and the post-install.yml File looks like this Any idea on this, Where i am missing ## rndc keys for authenticating with bind9 # define this to create as many key files as are required # designate_rndc_keys # - name: "rndc-key" # file: /etc/designate/rndc.key # algorithm: "hmac-md5" # secret: "<key>"

2 1

[ironic] bug tracking move to launchpad
by Julia Kreger 29 Mar '23

29 Mar '23

Greetings Ironic! During the PTG yesterday, we discussed the fact we had not moved back to Launchpad for bug tracking. Mainly because we are all very busy. The point was raised, why don't we just re-enable launchpad bug tracking, and move our primary usage back to that. Consensus on the call resulted with this proposal, and the consensus to send this email to the mailing list. As such, if nobody objects, I'm going to go turn the bug tracker for Ironic in launchpad back on next Monday. If you object, scream now and/or write a migration script and/or propose another solution. Thanks! -Julia

1 0

(Openstack-Nova)
by Adivya Singh 29 Mar '23

29 Mar '23

Hi Team I see these error in my syslog related to my nova compute service getting hung while communicating to rabbit-mq service "A recoverable connection/channel error occurred, trying to reconnect: [Errno 24] Too many open files" Is this a OS related error, or some thing i can change to get rid of this error Regards Adivya Singh

3 2

[neutron] BGP for self-service network
by Deniz AYDIN 29 Mar '23

29 Mar '23

Hi, I am looking for options for removing Layer-2 in the underlay as much as possible. The features explained in the document, BGP floating IPs over L2 segmented network <https://docs.openstack.org/neutron/zed/admin/config-bgp-floating-ip-over-l2…>, solve the problem for floating IPS where layer 2 is only needed between servers and rack switches. Is there any specific reason that this feature is limited to floating IPS? As long as we have unique BGP next-hops defined for every DVR, it can also be used for advertising self-service networks /32 routes. Thanks for the help Deniz

1 0

[nova] openstack-tox-pep8 job broken, hold your rechecks
by melanie witt 29 Mar '23

29 Mar '23

Hey all, Sending this to the ML to try to help others who may not have heard about it yet. I didn't know about myself until I saw the job fail on a random nova patch and I looked around to figure out why. It looks like openstack-tox-pep8 is failing 100% in nova due to a newer version of the mypy library being pulled in since a recent upper-constraints bump: https://review.opendev.org/c/openstack/requirements/+/872065 And the job isn't going to pass until the following fix merges: https://review.opendev.org/c/openstack/nova/+/878693 Finally, to help prevent a breakage for this in the future, a cross-nova-pep8 job has been approved: https://review.opendev.org/c/openstack/requirements/+/878748 and will be on its way to the gate once the aforementioned fix merges. I'll post a reply to this email when it's OK to do rechecks again. Cheers, -melwitt

2 3

[nova] Hold your rechecks
by Sylvain Bauza 29 Mar '23

29 Mar '23

Hey, Due to the recent merge of https://review.opendev.org/c/openstack/requirements/+/872065/10/upper-const… we now use mypy==1.1.1 which includes a breaking behavioural change against our code : https://07de6a0c9e6ec0c6835f-ccccbfab26b1456f69293167016566bc.ssl.cf2.rackc… Thanks to Eric (kudos to him, he was quickier than me), we have a fix https://review.opendev.org/c/openstack/nova/+/878693 Please accordingly hold your rechecks until that fix is merged. -Sylvain

1 1

[PTL][release][stable][EM] Extended Maintenance - Xena
by Elõd Illés 29 Mar '23

29 Mar '23

Hi teams, As 2023.1 Antelope was released last week and we are in a less busy period, now is the good time to call your attention to the following: In less than a month Xena is planned to transition to Extended Maintenance phase [1] (planned date: 2023-04-20). I have generated the list of the current *open* and *unreleased* changes in stable/xena for every repositories [2] (where there are such patches). These lists could help the teams who are planning to do a *final* release on Xena before moving stable/xena branches to Extended Maintenance. Feel free to edit and extend these lists to track your team's progress! Note that the *latest* Xena *release* tagging patches ('xena-em' tag) have been generated too in advance [3], please mark with a -1 if your team plans to do a final release, or +1 if the team is ready for the transition. The schedule from now on is as follows: * patches with +1 from PTL / release liaison will be merged, thus those repositories will transition to Extended Maintenance * at the planned deadline (April 20th) the Release Team will merge all of the transition patches (even the ones without any response!) * after the transition, stable/xena will be still open for bug fixes, but there won't be official releases anymore. *NOTE*: teams, please focus on wrapping up your libraries first if there is any concern about the changes, in order to avoid broken (final!!) releases! [1] https://releases.openstack.org/ [2] https://etherpad.opendev.org/p/xena-final-release-before-em [3] https://review.opendev.org/q/topic:xena-em Thanks, Előd irc: elodilles @ #openstack-release

1 0

[nova][ptg] Today's agenda
by Sylvain Bauza 29 Mar '23

29 Mar '23

(just shamelessly stealing the idea from Neutron's team) Hey foks, Yesterday was a packed day but we didn't really progressed on a lot of topics. Today I'm gonna propose a list of topics in order to improve our sessions's visibility and in order to provide some timeboxing. 13:00 UTC - 14:45 UTC : * How to make sure people can help to review ? * Should we ask for some implementation before accepting a spec ? * CI stability is a nightmare, let's fight over this * Bobcat is a non-SLURP release * Let's clean up our upgrade documentation * Nova community outreach * Clean-up our bug list by abandoning very old LP bug reports ? * Summit/PTG : what could we be doing for the physical PTG ? (Will be 4 weeks before milestone-2) 15:00 UTC - 15:45 UTC : * Nova/Manila cross-project session : Prevent share deletion while it's attached to an instance 16:00 UTC - 17:00 UTC : * When your instance is stuck due to hard affinity policies, what could we do ? * Users reported exhaustion of primary keys ('id') in some large tables like system_metadata. How could we achieve a data migration from sa.Integer to sa.BigInteger ? Details can be found in https://etherpad.opendev.org/p/nova-bobcat-ptg#L192 I assume the packed agenda, particularly the first two hours. As a reminder, people are welcome to add their IRC nicks in each of the courtesy ping list of the related topic. Hope this gives you a taste of joining the Nova PTG today. -Sylvain

1 0

[neutron][ptg] Today's agenda
by Rodolfo Alonso Hernandez 29 Mar '23

29 Mar '23

Hello all: This is a quick summary of the agenda for today's meeting (starting at 13UTC): * Status and questions about https://review.opendev.org/q/topic:port-hints * IPv6 Prefix Delegation in OVN * Neutron agents status (https://bugs.launchpad.net/neutron/+bug/2011422) * DHCP IPv6 issues with metadata service ( https://bugs.launchpad.net/neutron/+bug/1953165) * Operator hour Please check the full agenda, topics and past logs in https://etherpad.opendev.org/p/neutron-bobcat-ptg. Regards.

1 0

[Horizon][policies][keystone] allow _member_ role to add user
by James Leong 28 Mar '23

28 Mar '23

Hi all, I am using kolla-ansible for OpenStack deployment in the yoga version. Would it be possible to allow a user with a "_member_" role to add a user to the respective project? In OpenStack, an admin role allows users to add, delete, and edit a user profile. I would like to have the same privilege added to the "_member_" role. I have tried to modify the file "user.py" in the keystone container at "keystone/common/policies" and restarted the container. However, the button on my horizon dashboard did not appear. How could I integrate the code in order to allow the create button to appear on my dashboard with the "_member_" role? Is there a way to do that? THanks for your help James

1 0

[scientific-sig] PTG sessions for Scientific SIG
by Stig Telfer 28 Mar '23

28 Mar '23

Hi all - The Scientific SIG has two sessions on Wednesday (tomorrow) at the PTG, at 1400 UTC and 2100 UTC. Everyone is welcome. There is an etherpad for the sessions here: https://etherpad.opendev.org/p/march2023-ptg-scientific-sig <https://etherpad.opendev.org/p/march2023-ptg-scientific-sig>. We'll begin with an introduction to the SIG and some discussion of problems, challenges and new features specific to research computing use cases. We'd also like participants to contribute lightning talks about anything relevant that is of interest to them. Cheers, Stig

1 0

[Magnum] vPTG
by Jake Yip 28 Mar '23

28 Mar '23

Dear all, Magnum vPTG will be held at Wed 0900 UTC in the Havana Room. Please see etherpad https://etherpad.opendev.org/p/march2023-ptg-magnum for updates Regards, Jake -- Jake Yip DevOps Engineer, ARDC Nectar Research Cloud

2 1

[networking-mlnx] release job failure - missing openstackci as maintainer in pypi
by Elõd Illés 28 Mar '23

28 Mar '23

Hi networking-mlnx maintainers, latest networking-mlnx releases caused release job failures [1][2][3], with the following error: The user 'openstackci' isn't allowed to upload to project 'networking-mlnx'. (note, that networking-mlnx is not under openstack namespace (x/networking-mlnx)) [1] https://lists.openstack.org/pipermail/release-job-failures/2023-March/00165… [2] https://lists.openstack.org/pipermail/release-job-failures/2023-March/00165… [3] https://lists.openstack.org/pipermail/release-job-failures/2023-March/00165… Thanks, Előd irc: elodilles @ #openstack-release

1 0

[Freezer] Restore action report ERROR can't delete temporary Image
by Annie Liu(BJ-RD) 28 Mar '23

28 Mar '23

Hi All My Cinder Backend is Ceph, and so is Glance. For backup and restore, I choose Cinder for mode and local for storage . When I restore a Cinder volume with Freezer, an ERROR reported related to deleting temporary Image failure, which makes the whole restore flow can't be completed. 2023-03-23 16:53:50.555 361 ERROR freezer.main [-] HTTP 409 Conflict: Image 8af4be3f-2e7a-4965-8b34-74e610a89a3e could not be deleted because it is in use: The image cannot be deleted because it is in use through the backend store outside of Glance.: HTTPConflict: HTTP 409 Conflict: Image 8af4be3f-2e7a-4965-8b34-74e610a89a3e could not be deleted because it is in use: The image cannot be deleted because it is in use through the backend store outside of Glance. According to Cinder source code, the volume created from Image is a child of the Image, since it is made by clone which means it doesn't copy volume data at first. In other words, the Image is its parent holding the real data, and that's why deleting is failed. My question is, is this a general issue for other storage solution? Is there any opportunity to fix it? For example, do a flatten immediately after create volume from Image? Thanks. Beat Regards, Annie Liu ????? ????????????????????????????????????????????????????? CONFIDENTIAL NOTE: This email contains confidential or legally privileged information and is for the sole use of its intended recipient. Any unauthorized review, use, copying or forwarding of this email or the content of this email is strictly prohibited.

1 0

[neutron] Bug deputy report (week of Mar 20)
by Akihiro Motoki 28 Mar '23

28 Mar '23

Hi, Here is the bug deputy report last week. Hopefully, someone familiar with DNS integration can check the first bug. # Needs assignee * FQDN inside guest VM is not the same as dns_assignment on network port https://bugs.launchpad.net/neutron/+bug/2012391 It would be nice if someone familiar with DNS integration can look into it. * [CI] "neutron-ovs-grenade-multinode-skip-level" and "neutron-ovn-grenade-multinode-skip-level" failing always https://bugs.launchpad.net/neutron/+bug/2012731 # New but assigned * [OVN] Define the OVS port in the LSP to allow OVN to set the QoS rules https://bugs.launchpad.net/neutron/+bug/2012613 Assigned to ralonsoh # In Progress * [ovn] N/S traffic for VMs without FIPs not working https://bugs.launchpad.net/neutron/+bug/2012712 Assigned to ltomasbo [1] was proposed as a fix of bug 2012712 which is caused by [2]. In parallel, [3] was proposed to revert [2]. Reverting [2] first sounds reasonable to avoid the regression but it is better to clarify the priority and the relationship in the review comments. ltomasbo is involved in both, so I think there is no confusion though. [1] https://review.opendev.org/c/openstack/neutron/+/878450 [2] https://review.opendev.org/c/openstack/neutron/+/875644 [3] https://review.opendev.org/c/openstack/neutron/+/878441 * neutron-ovn-agent fails on do_commit aborted due to error: 'Chassis_Private' https://bugs.launchpad.net/neutron/+bug/2012385 * Intermittent failures of test_agent_metadata_port_ip_update_event https://bugs.launchpad.net/neutron/+bug/2012754 * [sqlalchemy-20] sqlalchemy.exc.InvalidRequestError: No 'on clause' argument may be passed when joining to a relationship path as a target https://bugs.launchpad.net/neutron/+bug/2012643 * [sqlalchemy-20] Strings are not accepted for attribute names in loader options https://bugs.launchpad.net/neutron/+bug/2012662 * [sqlalchemy-20] Unexpected keyword argument "when" in "sqlalchemy.case" method https://bugs.launchpad.net/neutron/+bug/2012705 # RFE * [rfe] Add one api support CRUD allowed_address_pairs https://bugs.launchpad.net/neutron/+bug/2012332 Thanks, Akihiro Motoki (amotoki)

1 0