- openstack-discuss - lists.openstack.org

[all][tc] Technical Committee next weekly meeting on 2022 Aug 25 at 1500 UTC
by Ghanshyam Mann 25 Aug '22

25 Aug '22

Hello Everyone, Below is the agenda for Tomorrow's TC meeting schedule at 1500 UTC. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting * Roll call * Follow up on past action items * Gate health check ** Bare 'recheck' state *** https://etherpad.opendev.org/p/recheck-weekly-summary * 2023.1 cycle PTG Planning ** Schedule 'operator hours' as a separate slot in PTG(avoiding conflicts among other projects 'operator hours') * 2023.1 cycle Technical Election * Open Reviews ** https://review.opendev.org/q/projects:openstack/governance+is:open -gmann

1 0

container and instances are not working on my dashboard
by Lee, Vincent Z 25 Aug '22

25 Aug '22

Hi all, I am quite new to Openstack and faced some issues with creating instances and displaying created containers on my Openstack dashboard. I am currently working on multinode Openstack. I am hoping to get some helps and feedbacks about this. I will briefly go through the problems I encountered. When I created an instances on my dashboard, it directly went into error state. I have attached a screenshot as shown below. [cid:c1615736-e4b3-4100-99c0-dfb970ff365f] This is my list of hosts. [cid:8d2f9138-27fd-4cf5-95ca-0cd9038f723c] When I created a container using both cli and dashboard, two containers were running. However, when I tried to look into my dashboard, those containers were not shown. These are the created containers. [cid:61d517f2-c60a-4892-bf88-1a9e0d763b7f] However, when i try to open my dashboard and look for them, they just don't appear on it. So I am not sure what is causing this. [cid:fb9d0f7e-1afa-48c1-bc92-9c8054382b55] Hope to hear from everyone soon. Best regards, Vincent

3 2

[all][elections][ptl][tc] Combined PTL/TC Antelope cycle Election Nominations Kickoff
by Amy Marrich 25 Aug '22

25 Aug '22

Apologies all for the lack of notice to the start of the PTL/TC election season. Unfortunately we are starting late and we are attempting to get back on schedule. We will make sure we send out a reminder notice (or two) for nominations closing. Remember we can't do this without your nominations and folks being willing to lead the projects and the community ======================================================================== Nominations for OpenStack PTLs (Project Team Leads) and TC (Technical Committee) positions (4 positions) are now open and will remain open until Aug 31, 2022 23:45 UTC. All nominations must be submitted as a text file to the openstack/election repository as explained at https://governance.openstack.org/election/#how-to-submit-a-candidacy Please make sure to follow the candidacy file naming convention: candidates/antelope/<Project_Name or "TC">/<email_address> (for example, "candidates/antelope/TC/stacker(a)example.org"). The name of the file should match an email address for your current OpenStack Foundation Individual Membership. Take this opportunity to ensure that your OSF member profile contains current information: https://www.openstack.org/profile/ Any OpenStack Foundation Individual Member can propose their candidacy for an available, directly-elected seat on the Technical Committee. In order to be an eligible candidate for PTL you must be an OpenStack Foundation Individual Member. PTL candidates must also have contributed to the corresponding team during the Zed to Antelope timeframe, Sep 17, 2021 00:00 UTC - Aug 31, 2022 00:00 UTC. Your Gerrit account must also have a verified email address matching the one used in your candidacy filename. Both PTL and TC elections will be held from Sep 07, 2022 23:45 UTC through to Sep 14, 2022 23:45 UTC. The electorate for the TC election are the OpenStack Foundation Individual Members who have a code contribution to one of the official teams over the Zed to Antelope timeframe, Sep 17, 2021 00:00 UTC - Aug 31, 2022 00:00 UTC, as well as any Extra ATCs who are acknowledged by the TC. The electorate for a PTL election are the OpenStack Foundation Individual Members who have a code contribution over the Zed to Antelope timeframe, Sep 17, 2021 00:00 UTC - Aug 31, 2022 00:00 UTC, in a deliverable repository maintained by the team which the PTL would lead, as well as the Extra ATCs who are acknowledged by the TC for that specific team. The list of project teams can be found at https://governance.openstack.org/tc/reference/projects/ and their individual team pages include lists of corresponding Extra ATCs. Please find below the timeline: PTL + TC nomination starts @ Aug 24, 2022 23:45 UTC PTL + TC nomination ends @ Aug 31, 2022 23:45 UTC TC campaigning starts @ Aug 31, 2022 23:45 UTC TC campaigning ends @ Sep 07, 2022 23:45 UTC PTL + TC elections start @ Sep 07, 2022 23:45 UTC PTL + TC elections end @ Sep 14, 2022 23:45 UTC Shortly after election officials approve candidates, they will be listed on the https://governance.openstack.org/election/ page. The electorate is requested to confirm their email addresses in Gerrit prior to 2022-08-31 00:00:00+00:00, so that the emailed ballots are sent to the correct email address. This email address should match one which was provided in your foundation member profile as well. Gerrit account information and OSF member profiles can be updated at https://review.openstack.org/#/settings/contact and https://www.openstack.org/profile/ accordingly. If you have any questions please be sure to either ask them on the mailing list or to the elections officials: https://governance.openstack.org/election/#election-officials

1 0

[TripleO] Derived Parameters going away
by John Fulton 25 Aug '22

25 Aug '22

It seems this feature was not widely adopted so the current maintainers would like to remove it. We have a proposed patch [1] to remove it from the main branch so it won't be in the TripleO release which accompanies Zed. It's presently in the release which accompanies Wallaby. Note that TripleO is using the independent release model [2]. What is the "Derived Parameters" feature? NFV and HCI overclouds require system tuning. There are formulas which output tuning parameters based on hardware. These parameters may then be provided as input to TripleO to deploy a tuned overcloud. There is an additional method of system tuning called “derived parameters” where TripleO uses inspected hardware data as input and automatically sets tuning parameters [3]. Removing this feature shouldn't block anyone since they can still deploy a tuned overcloud by providing standard parameters. There's also a docs patch [4] explaining how to migrate away from derived to standard parameters. John [1] https://review.opendev.org/q/topic:derive-parameters-cleanup [2] https://review.opendev.org/c/openstack/tripleo-specs/+/801512 [3] https://specs.openstack.org/openstack/tripleo-specs/specs/pike/tripleo-deri… [4] https://review.opendev.org/c/openstack/tripleo-docs/+/854443

1 0

OpenInfra Live - August 25 at 1400 UTC
by Allison Price 24 Aug '22

24 Aug '22

Hi everyone, This week’s OpenInfra Live episode is brought to you by members of the OpenStack community. Episode: Making VDI a first-class citizen in the OpenStack world Learn the importance of having a Virtual Desktop Infrastructure (VDI) with OpenStack. Get to know the VDI use cases. Discover which relevant features are already integrated and which are still missing. You’ll also have the opportunity to meet Bumblebee and enjoy the cute flying insect during a demo! Date and time: Thursday, August 25 at 1400 UTC (9am CT) You can watch us live on: YouTube: https://www.youtube.com/watch?v=juczRNlfg6c <https://www.youtube.com/watch?v=juczRNlfg6c> LinkedIn: https://www.linkedin.com/video/event/urn:li:ugcPost:6966050226767884289/ <https://www.linkedin.com/video/event/urn:li:ugcPost:6966050226767884289/> Facebook: https://www.facebook.com/104139126308032/posts/5359387687449790/ <https://www.facebook.com/104139126308032/posts/5359387687449790/> WeChat: recording will be posted on OpenStack WeChat after the live stream Speakers: Manuel Bentele Andy Botting Radosław Piliszek Have an idea for a future episode? Share it now at ideas.openinfra.live <https://openinfrafoundation.formstack.com/forms/openinfralive>. See you there! Allison

1 0

[neutron][ovn] Gauging community interest in supporting a masquerading forwarding DNS resolver for isolated tenant networks
by Miguel Lavalle 24 Aug '22

24 Aug '22

Hi, As described in this Launchpad bug https://bugs.launchpad.net/neutron/+bug/1902950, in contrast with ML2 / OVS, with ML2 / OVN there is not a masquerading forwarding DNS resolver available to instances on isolated tenant networks. The purpose of this message is to gather feedback from the community as to how much interest there is in providing this functionality under ML2 / OVN. If your organization has interest, please respond to this thread. Even better, register your interest on the topic in the etherpad for the upcoming Antelope PTG (https://etherpad.opendev.org/p/neutron-antelope-ptg) under the "Check of interest on closing ML2/OVN DNS gaps" topic. And of course, attend the conversation in October Best regards Miguel Lavalle

1 0

(no subject)
by ralonsoh＠redhat.com 24 Aug '22

24 Aug '22

The original message was received at Wed, 24 Aug 2022 22:48:10 +0900 from redhat.com [7.150.121.148] ----- The following addresses had permanent fatal errors ----- <openstack-discuss(a)lists.openstack.org>

1 0

High memory use with RabbitMQ on RHEL9 hosts
by Marcin Juszkiewicz 24 Aug '22

24 Aug '22

If you run RabbitMQ on RHEL9 family hosts (CentOS Stream 9, RockyLinux 9, AlmaLinux 9) and you see 1.6GB memory use then consider limiting amount of file descriptors: > EL9 (both CentOS Stream 9 and Rocky Linux 9) have 1073741816 while > CentOS Stream 8 has 1048576 - after lowering it's acceptable > memory usage. https://github.com/rabbitmq/erlang-rpm/discussions/104 for more

1 0

[cinder] Bug deputy report for week of 08-24-2022
by Sofia Enriquez 24 Aug '22

24 Aug '22

This is a bug report from 08-17-2022 to 08-24-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Low - https://bugs.launchpad.net/cinder/+bug/1982945 "[docs] Cannot start VM from disk with burst QoS." Unassigned. - https://bugs.launchpad.net/cinder/+bug/1900406 "RBD support extends for in-use volume." Unassigned. Cheers, Sofia -- 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

[octavia] Help with fix barbican client in octavia when use trust-scoped token
by Ришат Азизов 24 Aug '22

24 Aug '22

Hello! I have error with terminated https loadbalancer, it described here: https://storyboard.openstack.org/#!/story/2007619 Could you please help with fix for barbican client? Thank you.

3 3

Re: ovn-bgp-agent installation issue
by Satish Patel 24 Aug '22

24 Aug '22

Hi Luis, /cc - openstack discuss mailing list Thank you so much for clearing my doubts. I have a counter question. BGP Mode: - In bgp mode where i should run ovn-bgp-agent ? Network node or Compute node? EVPN Mode: - In evpn mode where i should run ovn-bgp-agent? - In my lab i am using your heck "How to use it without BGPVPN" to create vni mapping, do you think because of that i am not seeing vni pushed out to FRR automatically? https://ltomasbo.wordpress.com/2021/06/25/openstack-networking-with-evpn/ - In your demo link I can see you have bridge two different deployment clouds using the same VNI, In this scenario we need a router (or vrf) somewhere correct to bridge to different subnet IPs, correct? or is this L2 stretch? I am going to open a new thread to discuss issues related to expose_tenant_networks=True flag issue. On Tue, Aug 23, 2022 at 3:14 AM Luis Tomas Bolivar <ltomasbo(a)redhat.com> wrote: > Hi Satish! See inline > > On Mon, Aug 22, 2022 at 5:22 PM Satish Patel <satish.txt(a)gmail.com> wrote: > >> Hi Luis, >> >> Welcome back from your vacation, sorry i didn't know you are on vacation. >> Hope you had a wonderful time. >> >> How do i start conversion on opendev thread? is there a mailing list or >> are you saying open thread here - >> https://storyboard.openstack.org/#!/project/x/ovn-bgp-agent >> > > Actually, you did it right (sending it to openstack-discuss), but it seems > at some point we stop adding it on our replies... probably my fault due to > replying on the phone while on vacation. > > For the next issue we can open a different thread and I'll try not to drop > the openstack-discuss list! xD > > It would be great though if you can sent a follow up to the previous > thread with the final outcome (fixed by updating, or adding config X, ..), > so that community can see the project is alive, and other people facing > similar issues can try your solution/config. > >> I have an update for you, after upgrading the OVN/OVS version to the >> latest and that resolved lots of issues. As you mentioned earlier running >> the latest code is very important to get proper functionality. >> > > Awesome! Yeah, it is a new project, so functionality/fixes are being added > regularly, therefore using the latest version is the best approach. The > plan is to soon create a more stable version/release, once we have enough > testing coverage and main functionality covered > >> >> You are saying in BGP mode only FIP will get exposed but not the tenant >> VM ( What is this flag for expose_tenant_network=True ?) >> > > Main idea was: > - BGP mode for exposing VMs/LBs on provider networks, or with FIPs attached > - EVPN mode for tenant networks > > To give you some more context, we started with the BGP mode, and did the > expose_tenant_network to expose also tenant IPs. However, the BGP mode is > lacking an API to decide what to expose. So we moved to the EVPN mode (with > networking-bgpvpn as the API) to expose the tenant networks. > > That said, you are right, and the expose_tenant_network flag is intended > for the BGP mode, to expose all tenant networks (so you need to ensure no > overlapping CIDRs). And, if that is not working (it may be, as there is no > testing coverage for it), it is something we can definitely look at and > fix. So, feel free to open a new thread on openstack-discuss, or bug in > storyboard (whatever works for you better), and I'll try to fix asap. > > >> >> You are saying in EVPN mode only tenant VM ip will get exposed but not >> FIP but in this design what is the use of getting tenant VM exposed but you >> can't expose FIP then how does external people access VMs? ( I am totally >> confused in EVPN design and use case because your tenant VM is already >> talking to each other using geneve tunnel so why do we need EVPN/L2VPN to >> expose them?) >> > > EVPN mode is indeed only for tenant VMs (and loadbalancer). Idea for this > mode is to connect (N/S traffic, as you mention E/W is still using the > normal geneve path) tenant networks between different OpenStack clusters. > EVPN will create a vxlan tunnel connecting them. So, the vni/vxlan id > selected (with networking-bgpvpn) is the vxlan tunnel encap id being used > to connect both tenant networks. > > So, the idea behind the EVPN mode is not to make your VMs in a tenant > network publicly accessible, but being able to access them from a different > tenant network in a different cloud (it actually does not need to be an > OpenStack cloud, anything connected to the same vxlan id. Perhaps this is a > bit more clear in this demo: > https://ltomasbo.wordpress.com/2021/10/01/ovn-bgp-agent-interconnecting-kub… > > >> >> This is current status of my LAB >> >> ovn-bgp-agent in BGP Mode: >> I am successfully able to expose FIP and provider IPs (as you mentioned) >> but when i use expose_tenant_network=True in config then getting error and >> vm tenant ips not getting exposed to bgp so i am not sure what is the use >> case of that flag. >> > > Yep, most probably we broke something here due to lack of upstream testing > for this flag. I'll check asap and try to fix it > >> >> ovn-bgp-agent in EVPN Mode: >> In this mode everything is working and tenant vm also gets exposed but >> when I attach FIP to vm those FIP ip are not getting exposed in BGP (as you >> mentioned in your reply). >> > Yes, EVPN mode is not intended for FIPs or VMs on provider networks. Only > for tenants > > >> But i am seeing one bug here where vni config not getting inserted in FRR >> https://opendev.org/x/ovn-bgp-agent/src/branch/master/ovn_bgp_agent/drivers… >> >> >> Who will trigger that code and when will that code get triggered to >> configure FRR for vrf/vni ? >> > > This is being added by networking-bgpvpn. You can see some details about > the integration into my blogpost ( > https://ltomasbo.wordpress.com/2021/06/25/openstack-networking-with-evpn/) > or in the upstream documentation: > https://opendev.org/x/ovn-bgp-agent/src/branch/master/doc/source/contributo… > > Note though, to make networking-bgpvpn to work with this integration, this > patch is needed (which btw I should include into the documentation): > https://review.opendev.org/c/openstack/networking-bgpvpn/+/803161 > > Cheers, > Luis > > >> >> >> >> >> >> On Mon, Aug 22, 2022 at 5:44 AM Luis Tomas Bolivar <ltomasbo(a)redhat.com> >> wrote: >> >>> Hi Satish, >>> >>> Sorry I was on vacation. Trying to get through my inbox. >>> >>> I'm not sure what is the current status, note there is a difference >>> between EVPN and BGP mode. BGP mode is for FIPs and VMs/LBs on the provider >>> network or with FIPs, while EVPN is for VMs on the tenant networks, without >>> FIPs. Right now you cannot mix them and need to choose either EVPN or BGP >>> mode. I'm planning to give it a try to make it multidriver, but I haven't >>> even started yet. >>> >>> BTW, as you did with the initial email, perhaps it is worth to have >>> conversations on the opendev thread, so that anyone else facing the same >>> issues can get some hints (or even provide feedback), that was one of the >>> main ideas about moving it in there. To be able to have better support. >>> >>> As for the questions: >>> # # on rack-2-host-1 >>> # when i created vm1 which endup on rack-2-host-1 but it doesn't expose >>> the vm ip address. Is that normal behavior? >>> >>> This should be exposed in the node with cr-lrp port, i.e., rack1-host2, >>> and it should be as simple as adding the IP to the lo-2001 dummy device >>> >>> # When I attach a floating ip to vm2 then why does my floating ip >>> address not get exposed in BGP? >>> This is what I mentioned before, you cannot merge BGP and EVPN mode. >>> >>> On Mon, Aug 8, 2022 at 1:41 PM Satish Patel <satish.txt(a)gmail.com> >>> wrote: >>> >>>> Hi Luis, >>>> >>>> Sorry for bugging. I’m almost there now. Do you have any thought of >>>> following question >>>> >>>> Sent from my iPhone >>>> >>>> On Aug 5, 2022, at 1:16 AM, Satish Patel <satish.txt(a)gmail.com> wrote: >>>> >>>> >>>> Good morning Luis, >>>> >>>> Quick question, I have following deployment as per your lab >>>> >>>> rack-1-host-1 (controller) >>>> rack-1-host-2 (compute1 - This is hosting cr-lrp ports, inshort router) >>>> rack-2-host-1 (compute2) >>>> >>>> I have created two vms >>>> >>>> vagrant@rack-1-host-1:~$ nova list >>>> nova CLI is deprecated and will be a removed in a future release >>>> >>>> +--------------------------------------+------+--------+------------+-------------+--------------------------------------+ >>>> | ID | Name | Status | Task State | >>>> Power State | Networks | >>>> >>>> +--------------------------------------+------+--------+------------+-------------+--------------------------------------+ >>>> | aecb4f10-c46f-4551-b112-44e4dc007e88 | vm1 | ACTIVE | - | >>>> Running | private-test=10.0.0.105 | >>>> | ceae14b9-70c2-4dbc-8071-0d64d9a0ca84 | vm2 | ACTIVE | - | >>>> Running | private-test=10.0.0.86, 172.16.1.200 | >>>> >>>> +--------------------------------------+------+--------+------------+-------------+--------------------------------------+ >>>> >>>> # on rack-1-host-2 >>>> when i spun up vm2 which endup on rack-1-host-2 hence it created >>>> vrf-2001 on dummy lo-2001 interface and exposed vm2 ip address >>>> 10.0.0.86/32 >>>> >>>> 96: vrf-2001: <NOARP,MASTER,UP,LOWER_UP> mtu 65575 qdisc noqueue state >>>> UP group default qlen 1000 >>>> link/ether 22:cc:25:b3:7b:96 brd ff:ff:ff:ff:ff:ff >>>> 97: br-2001: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue >>>> master vrf-2001 state UP group default qlen 1000 >>>> link/ether 0a:c3:23:7a:8f:0c brd ff:ff:ff:ff:ff:ff >>>> inet6 fe80::851:67ff:fe64:b2c3/64 scope link >>>> valid_lft forever preferred_lft forever >>>> 98: vxlan-2001: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc >>>> noqueue master br-2001 state UNKNOWN group default qlen 1000 >>>> link/ether 0a:c3:23:7a:8f:0c brd ff:ff:ff:ff:ff:ff >>>> inet6 fe80::8c3:23ff:fe7a:8f0c/64 scope link >>>> valid_lft forever preferred_lft forever >>>> 99: lo-2001: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue >>>> master vrf-2001 state UNKNOWN group default qlen 1000 >>>> link/ether d6:60:da:91:2e:6d brd ff:ff:ff:ff:ff:ff >>>> inet 10.0.0.86/32 scope global lo-2001 >>>> valid_lft forever preferred_lft forever >>>> inet6 fe80::d460:daff:fe91:2e6d/64 scope link >>>> valid_lft forever preferred_lft forever >>>> >>>> >>>> # on rack-2-host-1 >>>> when i created vm1 which endup on rack-2-host-1 but it doesn't expose >>>> the vm ip address. Is that normal behavior? >>>> >>>> When I attach a floating ip to vm2 then why does my floating ip address >>>> not get exposed in BGP? >>>> >>>> Thank you in advance >>>> >>>> >>>> On Thu, Aug 4, 2022 at 2:30 PM Satish Patel <satish.txt(a)gmail.com> >>>> wrote: >>>> >>>>> Update: Good news, I found what was wrong. >>>>> >>>>> After adding AS it works. In your doc you only added VNI but look like >>>>> it is required to add BGP AS. Or may be your doc is little older and new >>>>> code required AS. >>>>> >>>>> vagrant@rack-1-host-1:~$ sudo ovn-nbctl set logical_switch_port >>>>> c32dcd90-7820-44bd-894f-416e44b36aa0 external_ids:"neutron_bgpvpn\:as"=64999 >>>>> vagrant@rack-1-host-1:~$ sudo ovn-nbctl set logical_switch_port >>>>> f55c1d1e-4b5b-4d8c-b922-3ad4a9700c81 external_ids:"neutron_bgpvpn\:as"=64999 >>>>> >>>>> Now i can see it created VRF and exposed VM tenant ip in lo-2001 >>>>> >>>>> 73: vrf-2001: <NOARP,MASTER,UP,LOWER_UP> mtu 65575 qdisc noqueue state >>>>> UP group default qlen 1000 >>>>> link/ether b2:29:65:3b:ac:db brd ff:ff:ff:ff:ff:ff >>>>> 74: br-2001: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue >>>>> master vrf-2001 state UP group default qlen 1000 >>>>> link/ether d6:0d:61:2d:b7:29 brd ff:ff:ff:ff:ff:ff >>>>> inet6 fe80::6830:47ff:febc:b10b/64 scope link >>>>> valid_lft forever preferred_lft forever >>>>> 75: vxlan-2001: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc >>>>> noqueue master br-2001 state UNKNOWN group default qlen 1000 >>>>> link/ether d6:0d:61:2d:b7:29 brd ff:ff:ff:ff:ff:ff >>>>> inet6 fe80::d40d:61ff:fe2d:b729/64 scope link >>>>> valid_lft forever preferred_lft forever >>>>> 76: lo-2001: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue >>>>> master vrf-2001 state UNKNOWN group default qlen 1000 >>>>> link/ether fe:a1:a0:87:76:7c brd ff:ff:ff:ff:ff:ff >>>>> inet 10.0.0.83/32 scope global lo-2001 >>>>> valid_lft forever preferred_lft forever >>>>> inet6 fe80::fca1:a0ff:fe87:767c/64 scope link >>>>> >>>>> >>>>> I am continuing doing testing and seeing if I hit any other bug.. >>>>> >>>>> On Thu, Aug 4, 2022 at 11:58 AM Satish Patel <satish.txt(a)gmail.com> >>>>> wrote: >>>>> >>>>>> Luis, >>>>>> >>>>>> I am following your doc, tell me if that doc is outdated or not >>>>>> https://ltomasbo.wordpress.com/2021/06/25/openstack-networking-with-evpn/ >>>>>> >>>>>> I have upgraded pyroute2 to 0.7.2 but still getting the same error, >>>>>> if you look at carefully following logs you will see an agent saying I >>>>>> can't find VNI but it's there, i can see in ovn-nbctl list >>>>>> logical_switch_port. >>>>>> >>>>>> pyroute2 0.7.2 >>>>>> pyroute2.core 0.6.13 >>>>>> pyroute2.ethtool 0.6.13 >>>>>> pyroute2.ipdb 0.6.13 >>>>>> pyroute2.ipset 0.6.13 >>>>>> pyroute2.ndb 0.6.13 >>>>>> pyroute2.nftables 0.6.13 >>>>>> pyroute2.nslink 0.6.13 >>>>>> >>>>>> >>>>>> ovn-bgp-agent logs >>>>>> >>>>>> 2022-08-04 15:52:52.898 396714 DEBUG >>>>>> ovn_bgp_agent.drivers.openstack.utils.ovn [-] Either "neutron_bgpvpn:vni" >>>>>> or "neutron_bgpvpn:as" were not found or have an invalid value in the port >>>>>> f55c1d1e-4b5b-4d8c-b922-3ad4a9700c81 external_ids {'neutron:cidrs': ' >>>>>> 172.16.1.132/24', 'neutron:device_id': >>>>>> '43b2c756-d92c-4fe5-b17b-32d5ab9b1f37', 'neutron:device_owner': >>>>>> 'network:router_gateway', 'neutron:network_name': >>>>>> 'neutron-0d82e6b0-bf9f-484d-85bd-0ba38aab508d', 'neutron:port_name': '', >>>>>> 'neutron:project_id': '', 'neutron:revision_number': '4', >>>>>> 'neutron:security_group_ids': '', 'neutron_bgpvpn:vni': '2001'} >>>>>> get_evpn_info >>>>>> /usr/local/lib/python3.8/dist-packages/ovn_bgp_agent/drivers/openstack/utils/ovn.py:251 >>>>>> >>>>>> 2022-08-04 15:52:52.899 396714 DEBUG >>>>>> ovn_bgp_agent.drivers.openstack.ovn_evpn_driver [-] No EVPN information for >>>>>> CR-LRP Port with IPs ['172.16.1.132/24']. Not exposing it. >>>>>> _expose_ip >>>>>> /usr/local/lib/python3.8/dist-packages/ovn_bgp_agent/drivers/openstack/ovn_evpn_driver.py:220 >>>>>> >>>>>> >>>>>> In OVN i can see vni number >>>>>> >>>>>> _uuid : 3473d0ce-1348-4423-a2dc-6d4df4c06f74 >>>>>> addresses : [router] >>>>>> dhcpv4_options : [] >>>>>> dhcpv6_options : [] >>>>>> dynamic_addresses : [] >>>>>> enabled : true >>>>>> external_ids : {"neutron:cidrs"="172.16.1.132/24", >>>>>> "neutron:device_id"="43b2c756-d92c-4fe5-b17b-32d5ab9b1f37", >>>>>> "neutron:device_owner"="network:router_gateway", >>>>>> "neutron:network_name"=neutron-0d82e6b0-bf9f-484d-85bd-0ba38aab508d, >>>>>> "neutron:port_name"="", "neutron:project_id"="", >>>>>> "neutron:revision_number"="4", "neutron:security_group_ids"="", >>>>>> "neutron_bgpvpn:vni"="2001"} >>>>>> ha_chassis_group : [] >>>>>> name : "f55c1d1e-4b5b-4d8c-b922-3ad4a9700c81" >>>>>> options : {exclude-lb-vips-from-garp="true", >>>>>> nat-addresses=router, router-port=lrp-f55c1d1e-4b5b-4d8c-b922-3ad4a9700c81} >>>>>> parent_name : [] >>>>>> port_security : [] >>>>>> tag : [] >>>>>> tag_request : [] >>>>>> type : router >>>>>> up : true >>>>>> >>>>>> >>>>>> On Thu, Aug 4, 2022 at 11:39 AM Satish Patel <satish.txt(a)gmail.com> >>>>>> wrote: >>>>>> >>>>>>> Hi Luis, >>>>>>> >>>>>>> This is what I have installed on the compute and controller nodes. >>>>>>> >>>>>>> pyroute2 0.6.13 >>>>>>> pyroute2.core 0.6.13 >>>>>>> pyroute2.ethtool 0.6.13 >>>>>>> pyroute2.ipdb 0.6.13 >>>>>>> pyroute2.ipset 0.6.13 >>>>>>> pyroute2.ndb 0.6.13 >>>>>>> pyroute2.nftables 0.6.13 >>>>>>> pyroute2.nslink 0.6.13 >>>>>>> >>>>>>> On Wed, Aug 3, 2022 at 10:10 AM Luis Tomas Bolivar < >>>>>>> ltomasbo(a)redhat.com> wrote: >>>>>>> >>>>>>>> What version of pyroute2 are you using? Maybe it is related to some >>>>>>>> bug in there in an old version (I hit quite a few). You can try to upgrade >>>>>>>> that. Also, as it is on the resync, you can also disable that by setting a >>>>>>>> very long time in there. >>>>>>>> >>>>>>>> >>>>>>>> On Wednesday, August 3, 2022, Satish Patel <satish.txt(a)gmail.com> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Any thoughts Luis. Thanks >>>>>>>>> >>>>>>>>> Sent from my iPhone >>>>>>>>> >>>>>>>>> On Jul 27, 2022, at 11:53 AM, Satish Patel <satish.txt(a)gmail.com> >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>> >>>>>>>>> Luis, >>>>>>>>> >>>>>>>>> If you look at this logs - >>>>>>>>> https://paste.opendev.org/show/buRbY415guvHFUtSapFK/ >>>>>>>>> >>>>>>>>> I am able to expose the tenant ip when I set "expose_tenant_networks=True" >>>>>>>>> in the ovn-bgp-agent.conf file. But interestingly it exposes ip for the >>>>>>>>> first time but when i delete vm and re-create new vm then its throws >>>>>>>>> following error which you can see full track in above link >>>>>>>>> >>>>>>>>> ERROR oslo_service.periodic_task [-] Error during BGPAgent.sync: KeyError: 'object does not exists' >>>>>>>>> >>>>>>>>> >>>>>>>>> I have just 1x controller and 1x compute machine at present. As >>>>>>>>> you said something is broken when setting up "expose_tenant_networks=True" >>>>>>>>> Let me know if you need more info or logs etc. i will continue to poke and >>>>>>>>> see if anything else I can find. >>>>>>>>> >>>>>>>>> >>>>>>>>> On Wed, Jul 27, 2022 at 10:35 AM Luis Tomas Bolivar < >>>>>>>>> ltomasbo(a)redhat.com> wrote: >>>>>>>>> >>>>>>>>>> Hi Satish,sorry for the delay in replies, I'm on vacations and >>>>>>>>>> have limited connectivity. >>>>>>>>>> >>>>>>>>>> See soon comments/replies inline >>>>>>>>>> >>>>>>>>>> On Wed, Jul 27, 2022 at 4:58 AM Satish Patel < >>>>>>>>>> satish.txt(a)gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> Luis, >>>>>>>>>>> >>>>>>>>>>> Just checking incase you missed my last email. If you are on >>>>>>>>>>> vacation then ignore it :) Thank you. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Sat, Jul 23, 2022 at 12:27 AM Satish Patel < >>>>>>>>>>> satish.txt(a)gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> Hi Luis, >>>>>>>>>>>> >>>>>>>>>>>> As you suggested, checkout 5 commits back to avoid the >>>>>>>>>>>> Load_Balancer issue that made good progress. >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> Great to hear! >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> But now i am seeing very odd behavior where floating IP can get >>>>>>>>>>>> exposed to BGP but when i am trying to expose VM Tenant IP then I get a >>>>>>>>>>>> strange error. Here is the full logs output; >>>>>>>>>>>> https://paste.opendev.org/show/buRbY415guvHFUtSapFK/ >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> I was using the evpn mode for the tenant networks, so it has been >>>>>>>>>> a while since I tested the vm tenant ip with plain bgp. Perhaps we broke it >>>>>>>>>> with some of the new features/reshapes. >>>>>>>>>> >>>>>>>>>> Regarding the error, two things: >>>>>>>>>> - Do you have several hosts or just one? The VM IP should be >>>>>>>>>> exposed in the host holding the ovn cr-lrp port (ovn router gateway port >>>>>>>>>> connecting the router to the provider network). >>>>>>>>>> - The error there seems to be related to the re-sync task. I've >>>>>>>>>> hit some issues with pyroute2 in the past, please be sure to use a recent >>>>>>>>>> enough version (minimum supported is 0.6.4) >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Fri, Jul 22, 2022 at 8:55 AM Satish Patel < >>>>>>>>>>>> satish.txt(a)gmail.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Hi Luis, >>>>>>>>>>>>> >>>>>>>>>>>>> Thank you for reply, >>>>>>>>>>>>> >>>>>>>>>>>>> Let me tell you that your blog is wonderful. I have used your >>>>>>>>>>>>> method to install frr without any docker container. >>>>>>>>>>>>> >>>>>>>>>>>>> What is the workaround here? Can I tell ovn-bgp-agent to not >>>>>>>>>>>>> look for container of frr? >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>> You just need to point where the frr socket is on the host. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>>> I have notice one more thing that it’s trying to run “copy >>>>>>>>>>>>> /tmp/blah running-config” but that command isn’t supported. >>>>>>>>>>>>> >>>>>>>>>>>>> I have tried to run copy command manually on vtysh shell to >>>>>>>>>>>>> see what options are available for copy command but there is only one >>>>>>>>>>>>> command available with copy which is “copy running-config startup-config” >>>>>>>>>>>>> do you think I have wrong version of frr running? I’m running 7.2. >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>> I think the minimum version I tried was either 7.4 or 7.5. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>>> Please let me know if any workaround here. Thank you >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>> No easy workaround for this, as it is relying on that way to >>>>>>>>>> reconfigure the frr.conf >>>>>>>>>> >>>>>>>>>> Cheers, >>>>>>>>>> Luis >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>>> Sent from my iPhone >>>>>>>>>>>>> >>>>>>>>>>>>> On Jul 22, 2022, at 2:41 AM, Luis Tomas Bolivar < >>>>>>>>>>>>> ltomasbo(a)redhat.com> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Hi Satish, >>>>>>>>>>>>> >>>>>>>>>>>>> The one to use should be https://opendev.org/x/ovn-bgp-agent. >>>>>>>>>>>>> The one on my personal github repo was the initial PoC for it. But the >>>>>>>>>>>>> opendev one is the upstream effort to develop it, and is the one being >>>>>>>>>>>>> maintained/updated. >>>>>>>>>>>>> >>>>>>>>>>>>> Looking at your second logs, it seems you are missing FRR (and >>>>>>>>>>>>> its shell, vtysh) in the node. >>>>>>>>>>>>> >>>>>>>>>>>>> Actually, thinking about this: >>>>>>>>>>>>> "Unexpected error while running command. >>>>>>>>>>>>> Command: /usr/bin/vtysh --vty_socket /run/frr/ -c copy >>>>>>>>>>>>> /tmp/tmpiz5s_wvs running-config" >>>>>>>>>>>>> >>>>>>>>>>>>> The ovn-bgp-agent has been developed with "deploying on >>>>>>>>>>>>> containers" in mind, meaning it is assuming there is a frr container >>>>>>>>>>>>> running, and the container running the agent is trying to connect to the >>>>>>>>>>>>> same socket so that it can run the vtysh commands. Perhaps in your case the >>>>>>>>>>>>> frr socket is in a different location than /run/frr/ >>>>>>>>>>>>> >>>>>>>>>>>>> On Fri, Jul 22, 2022 at 6:27 AM Satish Patel < >>>>>>>>>>>>> satish.txt(a)gmail.com> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Folks, >>>>>>>>>>>>>> >>>>>>>>>>>>>> I am trying to create lab of of ovn-bgp-agent using this blog >>>>>>>>>>>>>> https://ltomasbo.wordpress.com/2021/02/04/ovn-bgp-agent-testing-setup/ >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> So far everything went well but I'm stuck at the bgp-agent >>>>>>>>>>>>>> installation and I encounter following error when running bgp-agent. >>>>>>>>>>>>>> Any suggestions? >>>>>>>>>>>>>> >>>>>>>>>>>>>> root@rack-1-host-2:/home/vagrant/bgp-agent# bgp-agent >>>>>>>>>>>>>> 2022-07-22 04:02:39.123 111551 INFO bgp_agent.config [-] >>>>>>>>>>>>>> Logging enabled! >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 CRITICAL bgp-agent [-] >>>>>>>>>>>>>> Unhandled error: AssertionError >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent Traceback >>>>>>>>>>>>>> (most recent call last): >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent File >>>>>>>>>>>>>> "/usr/local/bin/bgp-agent", line 10, in <module> >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent >>>>>>>>>>>>>> sys.exit(start()) >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent File >>>>>>>>>>>>>> "/usr/local/lib/python3.8/dist-packages/bgp_agent/agent.py", line 76, in >>>>>>>>>>>>>> start >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent >>>>>>>>>>>>>> bgp_agent_launcher = service.launch(config.CONF, BGPAgent()) >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent File >>>>>>>>>>>>>> "/usr/local/lib/python3.8/dist-packages/bgp_agent/agent.py", line 44, in >>>>>>>>>>>>>> __init__ >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent >>>>>>>>>>>>>> self.agent_driver = driver_api.AgentDriverBase.get_instance( >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent File >>>>>>>>>>>>>> "/usr/local/lib/python3.8/dist-packages/bgp_agent/platform/driver_api.py", >>>>>>>>>>>>>> line 25, in get_instance >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent >>>>>>>>>>>>>> agent_driver = stevedore_driver.DriverManager( >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent File >>>>>>>>>>>>>> "/usr/local/lib/python3.8/dist-packages/stevedore/driver.py", line 54, in >>>>>>>>>>>>>> __init__ >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent >>>>>>>>>>>>>> super(DriverManager, self).__init__( >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent File >>>>>>>>>>>>>> "/usr/local/lib/python3.8/dist-packages/stevedore/named.py", line 78, in >>>>>>>>>>>>>> __init__ >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent extensions >>>>>>>>>>>>>> = self._load_plugins(invoke_on_load, >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent File >>>>>>>>>>>>>> "/usr/local/lib/python3.8/dist-packages/stevedore/extension.py", line 221, >>>>>>>>>>>>>> in _load_plugins >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent ext = >>>>>>>>>>>>>> self._load_one_plugin(ep, >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent File >>>>>>>>>>>>>> "/usr/local/lib/python3.8/dist-packages/stevedore/named.py", line 156, in >>>>>>>>>>>>>> _load_one_plugin >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent return >>>>>>>>>>>>>> super(NamedExtensionManager, self)._load_one_plugin( >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent File >>>>>>>>>>>>>> "/usr/local/lib/python3.8/dist-packages/stevedore/extension.py", line 257, >>>>>>>>>>>>>> in _load_one_plugin >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent obj = >>>>>>>>>>>>>> plugin(*invoke_args, **invoke_kwds) >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent File >>>>>>>>>>>>>> "/usr/local/lib/python3.8/dist-packages/bgp_agent/platform/osp/ovn_bgp_driver.py", >>>>>>>>>>>>>> line 64, in __init__ >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent >>>>>>>>>>>>>> self._sb_idl = ovn.OvnSbIdl( >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent File >>>>>>>>>>>>>> "/usr/local/lib/python3.8/dist-packages/bgp_agent/platform/osp/utils/ovn.py", >>>>>>>>>>>>>> line 62, in __init__ >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent >>>>>>>>>>>>>> super(OvnSbIdl, self).__init__( >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent File >>>>>>>>>>>>>> "/usr/local/lib/python3.8/dist-packages/bgp_agent/platform/osp/utils/ovn.py", >>>>>>>>>>>>>> line 31, in __init__ >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent >>>>>>>>>>>>>> super(OvnIdl, self).__init__(remote, schema) >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent File >>>>>>>>>>>>>> "/usr/local/lib/python3.8/dist-packages/ovs/db/idl.py", line 283, in >>>>>>>>>>>>>> __init__ >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent schema = >>>>>>>>>>>>>> schema_helper.get_idl_schema() >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent File >>>>>>>>>>>>>> "/usr/local/lib/python3.8/dist-packages/ovs/db/idl.py", line 2323, in >>>>>>>>>>>>>> get_idl_schema >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent >>>>>>>>>>>>>> self._keep_table_columns(schema, table, columns)) >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent File >>>>>>>>>>>>>> "/usr/local/lib/python3.8/dist-packages/ovs/db/idl.py", line 2330, in >>>>>>>>>>>>>> _keep_table_columns >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent assert >>>>>>>>>>>>>> table_name in schema.tables >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent AssertionError >>>>>>>>>>>>>> 2022-07-22 04:02:39.475 111551 ERROR bgp-agent >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> After googling I found one more agent at >>>>>>>>>>>>>> https://opendev.org/x/ovn-bgp-agent and its also throwing an >>>>>>>>>>>>>> error. Which agent should I be using? >>>>>>>>>>>>>> >>>>>>>>>>>>>> root@rack-1-host-2:~# ovn-bgp-agent >>>>>>>>>>>>>> 2022-07-22 04:04:36.780 111761 INFO ovn_bgp_agent.config [-] >>>>>>>>>>>>>> Logging enabled! >>>>>>>>>>>>>> 2022-07-22 04:04:37.247 111761 INFO ovn_bgp_agent.agent [-] >>>>>>>>>>>>>> Service 'BGPAgent' stopped >>>>>>>>>>>>>> 2022-07-22 04:04:37.248 111761 INFO ovn_bgp_agent.agent [-] >>>>>>>>>>>>>> Service 'BGPAgent' starting >>>>>>>>>>>>>> 2022-07-22 04:04:37.248 111761 INFO >>>>>>>>>>>>>> ovn_bgp_agent.drivers.openstack.utils.frr [-] Add VRF leak for VRF >>>>>>>>>>>>>> ovn-bgp-vrf on router bgp 64999 >>>>>>>>>>>>>> 2022-07-22 04:04:37.248 111761 INFO oslo.privsep.daemon [-] >>>>>>>>>>>>>> Running privsep helper: ['sudo', 'privsep-helper', '--privsep_context', >>>>>>>>>>>>>> 'ovn_bgp_agent.privileged.vtysh_cmd', '--privsep_sock_path', >>>>>>>>>>>>>> '/tmp/tmp4cie9eiz/privsep.sock'] >>>>>>>>>>>>>> 2022-07-22 04:04:37.687 111761 INFO oslo.privsep.daemon [-] >>>>>>>>>>>>>> Spawned new privsep daemon via rootwrap >>>>>>>>>>>>>> 2022-07-22 04:04:37.598 111769 INFO oslo.privsep.daemon [-] >>>>>>>>>>>>>> privsep daemon starting >>>>>>>>>>>>>> 2022-07-22 04:04:37.613 111769 INFO oslo.privsep.daemon [-] >>>>>>>>>>>>>> privsep process running with uid/gid: 0/0 >>>>>>>>>>>>>> 2022-07-22 04:04:37.617 111769 INFO oslo.privsep.daemon [-] >>>>>>>>>>>>>> privsep process running with capabilities (eff/prm/inh): >>>>>>>>>>>>>> CAP_NET_ADMIN|CAP_SYS_ADMIN/CAP_NET_ADMIN|CAP_SYS_ADMIN/none >>>>>>>>>>>>>> 2022-07-22 04:04:37.617 111769 INFO oslo.privsep.daemon [-] >>>>>>>>>>>>>> privsep daemon running as pid 111769 >>>>>>>>>>>>>> 2022-07-22 04:04:37.987 111769 ERROR >>>>>>>>>>>>>> ovn_bgp_agent.privileged.vtysh [-] Unable to execute vtysh with >>>>>>>>>>>>>> ['/usr/bin/vtysh', '--vty_socket', '/run/frr/', '-c', 'copy >>>>>>>>>>>>>> /tmp/tmpiz5s_wvs running-config']. Exception: Unexpected error while >>>>>>>>>>>>>> running command. >>>>>>>>>>>>>> Command: /usr/bin/vtysh --vty_socket /run/frr/ -c copy >>>>>>>>>>>>>> /tmp/tmpiz5s_wvs running-config >>>>>>>>>>>>>> Exit code: 1 >>>>>>>>>>>>>> Stdout: '% Unknown command: copy /tmp/tmpiz5s_wvs >>>>>>>>>>>>>> running-config\n' >>>>>>>>>>>>>> Stderr: '' >>>>>>>>>>>>>> Traceback (most recent call last): >>>>>>>>>>>>>> File >>>>>>>>>>>>>> "/usr/local/lib/python3.8/dist-packages/ovn_bgp_agent/privileged/vtysh.py", >>>>>>>>>>>>>> line 30, in run_vtysh_config >>>>>>>>>>>>>> return processutils.execute(*full_args) >>>>>>>>>>>>>> File >>>>>>>>>>>>>> "/usr/local/lib/python3.8/dist-packages/oslo_concurrency/processutils.py", >>>>>>>>>>>>>> line 438, in execute >>>>>>>>>>>>>> raise ProcessExecutionError(exit_code=_returncode, >>>>>>>>>>>>>> oslo_concurrency.processutils.ProcessExecutionError: >>>>>>>>>>>>>> Unexpected error while running command. >>>>>>>>>>>>>> Command: /usr/bin/vtysh --vty_socket /run/frr/ -c copy >>>>>>>>>>>>>> /tmp/tmpiz5s_wvs running-config >>>>>>>>>>>>>> Exit code: 1 >>>>>>>>>>>>>> Stdout: '% Unknown command: copy /tmp/tmpiz5s_wvs >>>>>>>>>>>>>> running-config\n' >>>>>>>>>>>>>> Stderr: '' >>>>>>>>>>>>>> 2022-07-22 04:04:37.990 111761 ERROR oslo_service.service [-] >>>>>>>>>>>>>> Error starting thread.: >>>>>>>>>>>>>> oslo_concurrency.processutils.ProcessExecutionError: Unexpected error while >>>>>>>>>>>>>> running command. >>>>>>>>>>>>>> Command: /usr/bin/vtysh --vty_socket /run/frr/ -c copy >>>>>>>>>>>>>> /tmp/tmpiz5s_wvs running-config >>>>>>>>>>>>>> Exit code: 1 >>>>>>>>>>>>>> Stdout: '% Unknown command: copy /tmp/tmpiz5s_wvs >>>>>>>>>>>>>> running-config\n' >>>>>>>>>>>>>> Stderr: '' >>>>>>>>>>>>>> 2022-07-22 04:04:37.990 111761 ERROR oslo_service.service >>>>>>>>>>>>>> Traceback (most recent call last): >>>>>>>>>>>>>> 2022-07-22 04:04:37.990 111761 ERROR oslo_service.service >>>>>>>>>>>>>> File "/usr/local/lib/python3.8/dist-packages/oslo_service/service.py", line >>>>>>>>>>>>>> 806, in run_service >>>>>>>>>>>>>> 2022-07-22 04:04:37.990 111761 ERROR oslo_service.service >>>>>>>>>>>>>> service.start() >>>>>>>>>>>>>> 2022-07-22 04:04:37.990 111761 ERROR oslo_service.service >>>>>>>>>>>>>> File "/usr/local/lib/python3.8/dist-packages/ovn_bgp_agent/agent.py", line >>>>>>>>>>>>>> 50, in start >>>>>>>>>>>>>> 2022-07-22 04:04:37.990 111761 ERROR oslo_service.service >>>>>>>>>>>>>> self.agent_driver.start() >>>>>>>>>>>>>> 2022-07-22 04:04:37.990 111761 ERROR oslo_service.service >>>>>>>>>>>>>> File >>>>>>>>>>>>>> "/usr/local/lib/python3.8/dist-packages/ovn_bgp_agent/drivers/openstack/ovn_bgp_driver.py", >>>>>>>>>>>>>> line 73, in start >>>>>>>>>>>>>> 2022-07-22 04:04:37.990 111761 ERROR oslo_service.service >>>>>>>>>>>>>> frr.vrf_leak(constants.OVN_BGP_VRF, CONF.bgp_AS, CONF.bgp_router_id) >>>>>>>>>>>>>> 2022-07-22 04:04:37.990 111761 ERROR oslo_service.service >>>>>>>>>>>>>> File >>>>>>>>>>>>>> "/usr/local/lib/python3.8/dist-packages/ovn_bgp_agent/drivers/openstack/utils/frr.py", >>>>>>>>>>>>>> line 110, in vrf_leak >>>>>>>>>>>>>> 2022-07-22 04:04:37.990 111761 ERROR oslo_service.service >>>>>>>>>>>>>> _run_vtysh_config_with_tempfile(vrf_config) >>>>>>>>>>>>>> 2022-07-22 04:04:37.990 111761 ERROR oslo_service.service >>>>>>>>>>>>>> File >>>>>>>>>>>>>> "/usr/local/lib/python3.8/dist-packages/ovn_bgp_agent/drivers/openstack/utils/frr.py", >>>>>>>>>>>>>> line 93, in _run_vtysh_config_with_tempfile >>>>>>>>>>>>>> 2022-07-22 04:04:37.990 111761 ERROR oslo_service.service >>>>>>>>>>>>>> ovn_bgp_agent.privileged.vtysh.run_vtysh_config(f.name) >>>>>>>>>>>>>> 2022-07-22 04:04:37.990 111761 ERROR oslo_service.service >>>>>>>>>>>>>> File "/usr/local/lib/python3.8/dist-packages/oslo_privsep/priv_context.py", >>>>>>>>>>>>>> line 271, in _wrap >>>>>>>>>>>>>> 2022-07-22 04:04:37.990 111761 ERROR oslo_service.service >>>>>>>>>>>>>> return self.channel.remote_call(name, args, kwargs, >>>>>>>>>>>>>> 2022-07-22 04:04:37.990 111761 ERROR oslo_service.service >>>>>>>>>>>>>> File "/usr/local/lib/python3.8/dist-packages/oslo_privsep/daemon.py", line >>>>>>>>>>>>>> 215, in remote_call >>>>>>>>>>>>>> 2022-07-22 04:04:37.990 111761 ERROR oslo_service.service >>>>>>>>>>>>>> raise exc_type(*result[2]) >>>>>>>>>>>>>> 2022-07-22 04:04:37.990 111761 ERROR oslo_service.service >>>>>>>>>>>>>> oslo_concurrency.processutils.ProcessExecutionError: Unexpected error while >>>>>>>>>>>>>> running command. >>>>>>>>>>>>>> 2022-07-22 04:04:37.990 111761 ERROR oslo_service.service >>>>>>>>>>>>>> Command: /usr/bin/vtysh --vty_socket /run/frr/ -c copy /tmp/tmpiz5s_wvs >>>>>>>>>>>>>> running-config >>>>>>>>>>>>>> 2022-07-22 04:04:37.990 111761 ERROR oslo_service.service >>>>>>>>>>>>>> Exit code: 1 >>>>>>>>>>>>>> 2022-07-22 04:04:37.990 111761 ERROR oslo_service.service >>>>>>>>>>>>>> Stdout: '% Unknown command: copy /tmp/tmpiz5s_wvs running-config\n' >>>>>>>>>>>>>> 2022-07-22 04:04:37.990 111761 ERROR oslo_service.service >>>>>>>>>>>>>> Stderr: '' >>>>>>>>>>>>>> 2022-07-22 04:04:37.990 111761 ERROR oslo_service.service >>>>>>>>>>>>>> 2022-07-22 04:04:37.993 111761 INFO ovn_bgp_agent.agent [-] >>>>>>>>>>>>>> Service 'BGPAgent' stopping >>>>>>>>>>>>>> 2022-07-22 04:04:37.994 111761 INFO ovn_bgp_agent.agent [-] >>>>>>>>>>>>>> Service 'BGPAgent' stopped >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> LUIS TOMÁS BOLÍVAR >>>>>>>>>>>>> Principal Software Engineer >>>>>>>>>>>>> Red Hat >>>>>>>>>>>>> Madrid, Spain >>>>>>>>>>>>> ltomasbo(a)redhat.com >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> LUIS TOMÁS BOLÍVAR >>>>>>>>>> Principal Software Engineer >>>>>>>>>> Red Hat >>>>>>>>>> Madrid, Spain >>>>>>>>>> ltomasbo(a)redhat.com >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> LUIS TOMÁS BOLÍVAR >>>>>>>> Principal Software Engineer >>>>>>>> Red Hat >>>>>>>> Madrid, Spain >>>>>>>> ltomasbo(a)redhat.com >>>>>>>> >>>>>>>> >>>>>>>> >>> >>> -- >>> LUIS TOMÁS BOLÍVAR >>> Principal Software Engineer >>> Red Hat >>> Madrid, Spain >>> ltomasbo(a)redhat.com >>> >>> >> > > -- > LUIS TOMÁS BOLÍVAR > Principal Software Engineer > Red Hat > Madrid, Spain > ltomasbo(a)redhat.com > >

2 1

[ironic][xena] problems updating redfish_password for existing node
by Wade Albright 24 Aug '22

24 Aug '22

Hi, I'm hitting a problem when trying to update the redfish_password for an existing node. I'm curious to know if anyone else has encountered this problem. I'm not sure if I'm just doing something wrong or if there is a bug. Or if the problem is unique to my setup. I have a node already added into ironic with all the driver details set, and things are working fine. I am able to run deployments. Now I need to change the redfish password on the host. So I update the password for redfish access on the host, then use an 'openstack baremetal node set <node> --driver-info redfish_password=<newpass>' command to set the new redfish_password. Once this has been done, deployment no longer works. I see redfish authentication errors in the logs and the operation fails. I waited a bit to see if there might just be a delay in updating the password, but after awhile it still didn't work. I restarted the conductor, and after that things work fine again. So it seems like the password is cached or something. Is there a way to force the password to update? I even tried removing the redfish credentials and re-adding them, but that didn't work either. Only a conductor restart seems to make the new password work. We are running Xena, using rpm installation on Oracle Linux 8.5. Thanks in advance for any help with this issue.

3 21

RE: [glance][cinder] Glance cinder backend or image cache ?
by Simon Dodsley 23 Aug '22

23 Aug '22

> Hello ! > > We're planning a new cluster without Ceph storage. > We will use an iSCSI pureStorage array for all storage except object > storage. > > PureStorage provide only a cinder driver. > So we will need to user boot on volume nova instances. > > My question is about glance. > PureStorage speak about Image Cache since Liberty: > https://support.purestorage.com/Solutions/OpenStack/z_Legacy_OpenStack_Refe… > > But I wonder if using the cinder backend of glance is a better, simpler, > transparent option ? The Image Cache you referenced is not specific to Pure. It is a common Cinder feature that many backend can leverage. You can use both the image cache and cinder as a glance store as well but they are redundant. It is best to pick one or the other. It depends on the images format you are using. For example if you are using QCOW2 as the format the glance cinder backend cannot optimize it, but the image cache can optimize. Simon

1 0

[TripleO] Adding Undercloud and overcloud container images to Foreman
by Ruslanas Gžibovskis 23 Aug '22

23 Aug '22

Hi all, Have anyone tried adding a container images registry from quay.io to the foreman installation? So far what I managed to achieve is - adding each image one by one, not a registry itself. I add it over Content > Products > (Added Product docker-registries) > Repositories > New Repository > Name > Type (select docker) > Upstream URL: quay.io > Upstream repository (tripleoussuri or tripleowallaby or any other) fails, it works only if I specify full image: tripleoussuri/centos-binary-heat-engine So my question, is there any way to copy whole repo using Foreman? Maybe I just go in incorrect place? Thanks. Regards -- Ruslanas Gžibovskis +370 6030 7030

1 0

[glance][cinder] Glance cinder backend or image cache ?
by Gilles Mocellin 23 Aug '22

23 Aug '22

Hello ! We're planning a new cluster without Ceph storage. We will use an iSCSI pureStorage array for all storage except object storage. PureStorage provide only a cinder driver. So we will need to user boot on volume nova instances. My question is about glance. PureStorage speak about Image Cache since Liberty: https://support.purestorage.com/Solutions/OpenStack/z_Legacy_OpenStack_Refe… But I wonder if using the cinder backend of glance is a better, simpler, transparent option ?

1 0

[openstack-helm] No Meeting Tomorrow
by Gage Hugo 23 Aug '22

23 Aug '22

Hey team, Since there is nothing on the agenda for tomorrow's meeting, it has been cancelled. We will plan on meeting next week at the usual time.

1 0

[edge] OpenStack updates for an Akraino presentation
by Ildiko Vancsa 23 Aug '22

23 Aug '22

Hi OpenStack community, I’m reaching out to you as I would like to ask for a little help and pointers for a presentation I’m building about OpenStack. I was recently asked by the Akraino community to give a presentation about recently added features and enhancements and further updates in OpenStack. Akraino is a project that is primarily focused on edge computing use cases and building blocks of end-to-end edge infrastructures. To make my presentation relevant and most informative for them, I would like to highlight any recent development or ongoing work item that is, or can be, relevant for edge use cases. If there are features in your project that you think would be good to highlight or if your project team is working on relevant work items in the current release cycle, I would really appreciate if you could share pointers to any information about them! Thanks and Best Regards, Ildikó ——— Ildikó Váncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation

1 0

[openstack-ansible] [yoga] utility_container failure
by Father Vlasie 23 Aug '22

23 Aug '22

Hello everyone, I have happily progressed to the second step of running the playbooks, namely "openstack-ansible setup-infrastructure.yml" Everything looks good except for just one error which is mystifying me: ---------------- TASK [Get list of repo packages] ********************************************************************************************************************************************************** fatal: [infra1_utility_container-5ec32cb5]: FAILED! => {"changed": false, "content": "", "elapsed": 30, "msg": "Status code was -1 and not [200]: Request failed: <urlopen error timed out>", "redirected": false, "status": -1, "url": "http://192.168.3.9:8181/constraints/upper_constraints_cached.txt"} ---------------- 192.168.3.9 is the IP listed in user_variables.yml under haproxy_keepalived_internal_vip_cidr Any help or pointers would be very much appreciated! Thank you, Father Vlasie

2 9

evacuate vm
by fereshteh loghmani 22 Aug '22

22 Aug '22

hello i use kolla ansiable with wallaby version. when i evacuate server some of my vm with centos OS have error about xfs and for solve this issue i change server to rescue mode and from rescue i use command xfs_repair -l and my server will be ok and boot successfully. could you help me about this issue that why some of my vm had xfs error ?

1 0

Kolla-ansible Xena installation Error
by KK CHN 22 Aug '22

22 Aug '22

I am following the documentation https://docs.openstack.org/project-deploy-guide/kolla-ansible/xena/quicksta… on VM with Debian 10 distro But I am getting the errors as follows . Here is my /etc/hosts whats wrong here ?? ############################################## (venv) cloud@Xena:~$ cat /etc/hosts 127.0.0.1 localhost #127.0.1.1 Xena #10.184.48.94 localhost Xena # The following lines are desirable for IPv6 capable hosts ::1 localhost ip6-localhost ip6-loopback ff02::1 ip6-allnodes ff02::2 ip6-allrouters # BEGIN ANSIBLE GENERATED HOSTS 10.184.48.94 Xena # END ANSIBLE GENERATED HOSTS (venv) cloud@Xena:~$ ################################################### ERROR fatal: [localhost]: FAILED! => {"changed": false, "module_stderr": "sudo: a password is required\n", "module_stdout": "", "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", "rc": 1} I am trying this installation on a Virtual Machine on Debian 10 OS. (venv) cloud@Xena:~$ kolla-ansible -i ./all-in-one bootstrap-servers Bootstrapping servers : ansible-playbook -e @/etc/kolla/globals.yml -e @/etc/kolla/passwords.yml -e CONFIG_DIR=/etc/kolla -e kolla_action=bootstrap-servers /home/cloud/venv/share/kolla-ansible/ansible/kolla-host.yml --inventory ./all-in-one [WARNING]: Invalid characters were found in group names but not replaced, use -vvvv to see details PLAY [Gather facts for all hosts] *************************************************************************************************************************************** TASK [Gather facts] ***************************************************************************************************************************************************** ok: [localhost] TASK [Group hosts to determine when using --limit] ********************************************************************************************************************** ok: [localhost] [WARNING]: Could not match supplied host pattern, ignoring: all_using_limit_True PLAY [Gather facts for all hosts (if using --limit)] ******************************************************************************************************************** skipping: no hosts matched PLAY [Apply role baremetal] ********************************************************************************************************************************************* TASK [baremetal : include_tasks] **************************************************************************************************************************************** included: /home/cloud/venv/share/kolla-ansible/ansible/roles/baremetal/tasks/bootstrap-servers.yml for localhost TASK [baremetal : Ensure localhost in /etc/hosts] *********************************************************************************************************************** fatal: [localhost]: FAILED! => {"changed": false, "module_stderr": "sudo: a password is required\n", "module_stdout": "", "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", "rc": 1} PLAY RECAP ************************************************************************************************************************************************************** localhost : ok=3 changed=0 unreachable=0 failed=1 skipped=0 rescued=0 ignored=0 Command failed ansible-playbook -e @/etc/kolla/globals.yml -e @/etc/kolla/passwords.yml -e CONFIG_DIR=/etc/kolla -e kolla_action=bootstrap-servers /home/cloud/venv/share/kolla-ansible/ansible/kolla-host.yml --inventory ./all-in-one (venv) cloud@Xena:~$ Any hints welcome. Thank you all krish

2 1

Floating IP
by Venkat Reddy 22 Aug '22

22 Aug '22

Hi All Goodmorning, Please help me ,I have the requirement to assign floating IP automatically while creating an instance. Can please help me. -- Thanks & Regards, Venkat Reddy.S

4 4

docker.repo file
by Faezeh Salali 22 Aug '22

22 Aug '22

Hi on Kolla ansible victoria version in bootstrap command this error is displayed: failed to fetch key at https://download.docker.com/linux/rocky/gpg , error was: HTTP Error 404: Not Found my compute os is rocky Linux 8 and it seems there is some problem with the docker repo on compute and /etc/yum.repos.d/docker.repo directory. Please send me the link of the baseurl and gpgkey. Thank you.

4 3

[neutron] Bug deputy report for week of August 15
by Lajos Katona 22 Aug '22

22 Aug '22

Hi Neutron Team I was the bug deputy in neutron last week, please check my summary. Needs attention ================= * OVN Metadata set up very slow (https://bugs.launchpad.net/neutron/+bug/1987060) * [stable/stein][stable/rocky}[stable/queens] CI jobs failing (https://bugs.launchpad.net/neutron/+bug/1986682 ) For stein I pushed 2 patches, not sure if with minimal effort it can be fixed: * https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/853794 * https://review.opendev.org/c/openstack/neutron/+/853608 In Progress ================= * [ovn-octavia-provider] HealthMonitor affecting several LBs (https://bugs.launchpad.net/neutron/+bug/1986977 ) In Progress ( https://review.opendev.org/c/openstack/ovn-octavia-provider/+/853681) * ovn: db sync fails if all ips are allocated in the subnet and metadata port is missing an ip (https://bugs.launchpad.net/neutron/+bug/1987135) In Progress: https://review.opendev.org/c/openstack/neutron/+/853840 Documentation bug ================= * Manually assign --device and --device-owner to a port does NOT binds the port immediately (https://bugs.launchpad.net/neutron/+bug/1986969 ) RFE proposals ================= * [rfe][fwaas]support standard_attrs for firewall_group (https://bugs.launchpad.net/neutron/+bug/1986906 ) we already discussed and approved this RFE on Drivers meeting * [RFE] Add a port extension to set/define the switchdev capabilities (https://bugs.launchpad.net/neutron/+bug/1987093 )

1 0

[OVS] Can't access instances on a compute and after restarted ovs-vswitchd it's back to normal
by ginton 4k 22 Aug '22

22 Aug '22

*Bug Description* We are using openstack ussuri with openvswitch version 2.13.3 and ovn version 20.03.2. We are using ubuntu 18.04.5 LTS with kernel 4.15.0-122-generic. My question is sometimes and consistently all instances in one compute can't access and when hard reboot instance we got an error message: Unable to add port tapxxx to OVS bridge br-int. After restart ovs-vswitchd service all instances can be accessed.

1 0

[openstack-ansible] Reset Target Host
by Father Vlasie 21 Aug '22

21 Aug '22

Hello everyone, Is there a way to reset a target host with OpenStack-Ansible? What I mean is to remove all the changes that have been applied, say, to infra1 so that the scripts can be deployed afresh. (It seems that the only way to get back to square one is to do a OS reinstall…is that right?) I am trying to avoid a reinstall because I am deploying from a remote location. Thank you, Father Vlasie

2 1

Re: [octavia] Help with fix barbican client in octavia when use trust-scoped token
by Ришат Азизов 21 Aug '22

21 Aug '22

Hello, Dmitry, Thanks for answer, I think this issue with Barbican client inside Octavia, and it can be fixed in the same way as the problem with the neutron client was fixed by Ligxian Kong https://review.opendev.org/c/openstack/octavia/+/726042/ Or not?

1 0

[all] Proposed Antelope cycle schedule
by Előd Illés 20 Aug '22

20 Aug '22

Hi, As we are beyond Zed milestone 2 for more than 2 weeks now, it's time to start planning the next, Antelope cycle and its release schedule: Antelope schedule: https://review.opendev.org/c/openstack/releases/+/850753 (or see its generated page [1]) Feel free to review it and comment on the patch if there is something that should be considered for the schedule. [1] https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/… Thanks, Előd Illés irc: elodilles

3 3

[swift] Terraform has deprecated the Swift backend
by Andrew Ruthven 20 Aug '22

20 Aug '22

Hey, It has come to our attention that Terraform has recently added deprecation messages to a number of backends, including Swift[0], warning that these backends will be removed in a future version of Terraform. Unfortunately we don't have the bandwidth within Catalyst Cloud to pick this up, but I was hopeful that there'd be others on this list who share our concern. It looks as though Terraform has had the Swift backend marked as unmaintained since at least March 2020[1]. If there is another backend, or another method of managing Swift that isn't the S3 API then I'd be keen to hear about it. Kind regards, Andrew [0] https://github.com/hashicorp/terraform/commit/7941b2fbdc33a42a68b9b32af51e0… [1] https://github.com/hashicorp/terraform/commit/c434db158e631b0bfddb92e1dd342… -- Andrew Ruthven, Wellington, New Zealand andrew(a)etc.gen.nz | Catalyst Cloud: | This space intentionally left blank https://catalystcloud.nz |

4 4

Fwd: Virtual PTG October 2022 Team Signup Reminder - Last Call
by Kendall Nelson 19 Aug '22

19 Aug '22

Hello Everyone, This is your last call to sign up your team up for the next virtual Project Teams Gathering (PTG), which will be held from Monday, October 17 to Friday, October 21st, 2022! NOTE: Since we are now hosting the PTG virtually, we will be holding the event all week (Monday - Friday) and will be using the ‘normal’ virtual schedule of 4 hour blocks of time covering hours for Americas/APAC, APAC/Europe+Africa, and Europe+Africa/Americas. If you haven't already done so and your team is interested in participating, please complete the survey[1] by August 26th, 2022 at 7:00 UTC. Then make sure to register[2] - it’s free :) Thanks! -Kendall (diablo_rojo) [1] Team Survey: https://openinfrafoundation.formstack.com/forms/oct2022_ptg_team_signup [2] PTG Registration: https://openinfra-ptg.eventbrite.com

1 0

[kolla-ansible] upgrade process when it involves OS and ceph major version
by wodel youchi 19 Aug '22

19 Aug '22

Hi, What are the steps of upgrading an openstack platform when the upgrade involves: - OS upgrade: how to perform the upgrade? What type of node to upgrade first? Controllers, network or compute? - Ceph storage when using HCI deployment? Just general steps. Regards

2 2

[release] Release countdown for week R-6, Aug 22 - 26
by Előd Illés 19 Aug '22

19 Aug '22

Development Focus ----------------- Work on libraries should be wrapping up, in preparation for the various library-related deadlines coming up. Now is a good time to make decisions on deferring feature work to the next development cycle in order to be able to focus on finishing already-started feature work. General Information ------------------- We are now getting close to the end of the cycle, and will be gradually freezing feature work on the various deliverables that make up the OpenStack release. This coming week is the deadline for general libraries (except client libraries): their last feature release needs to happen before "Non-client library freeze" on August 25th, 2022. Only bugfix releases will be allowed beyond this point. When requesting those library releases, you can also include the stable/zed branching request with the review (as an example, see the "branches" section here: https://opendev.org/openstack/releases/src/branch/master/deliverables/pike/… In the next weeks we will have deadlines for: * Client libraries (think python-*client libraries), which need to have their last feature release before "Client library freeze" (September 1st, 2022) * Deliverables following a cycle-with-rc model (that would be most services), which observe a Feature freeze on that same date, September 1st, 2022. Any feature addition beyond that date should be discussed on the mailing-list and get PTL approval. As we are getting to the point of creating stable/zed branches, this would be a good point for teams to review membership in their $project-stable-maint groups. Once the stable/zed branches are cut for a repo, the ability to approve any necessary backports into those branches for Zed will be limited to the members of that stable team. If there are any questions about stable policy or stable team membership, please reach out in the #openstack-stable channel. Upcoming Deadlines & Dates -------------------------- Non-client library freeze: August 25th, 2022 (R-6 week) Client library freeze: September 1st, 2022 (R-5 week) Zed-3 milestone: September 1st, 2022 (R-5 week) Cycle Highlights Due: September 1st, 2022 (R-5 week) Zed final release: October 5th, 2022 Előd Illés irc: elodilles

1 0

[cinder] Festival of XS reviews
by Rajat Dhasmana 19 Aug '22

19 Aug '22

Hello Argonauts, We will be having our monthly festival of XS reviews today i.e. 19th August (Friday) from 1400-1600 UTC. Following are some additional details: Date: 19th August, 2022 Time: 1400-1600 UTC Meeting link: https://bluejeans.com/556681290 etherpad: https://etherpad.opendev.org/p/cinder-festival-of-reviews Thanks and regards Rajat Dhasmana

1 0

[all][tc] What's happening in Technical Committee: summary 2022 Aug 19
by Slawek Kaplonski 19 Aug '22

19 Aug '22

Hi, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Aug 18. Most of the meeting discussions are summarized in this email. Meeting full logs are available at https://meetings.opendev.org/meetings/tc/2022/tc.2022-08-18-15.00.log.html * Next TC weekly meeting will be on 25 Aug Thursday at 15:00 UTC, feel free to add the topic on the agenda[1] by Aug 3. 2. What we completed this week: ========================= 3. Activities In progress: ================== TC Tracker for Zed cycle ------------------------------ * Zed tracker etherpad includes the TC working items[2], Two are completed and others items are in-progress. Open Reviews ----------------- * Four open reviews for ongoing activities[3]. 2021 User Survey TC Question Analysis ----------------------------------------------- No update on this. The survey summary is up for review[4]. Feel free to check and provide feedback. Zed cycle Leaderless projects ---------------------------------- Dale Smith volunteer to be PTL for Adjutant project [5] Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[6][7]. Project updates ------------------- * Retire openstack-help-addons [8] 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[9]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [10] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://etherpad.opendev.org/p/tc-zed-tracker [3] https://review.opendev.org/q/projects:openstack/governance+status:open [4] https://review.opendev.org/c/openstack/governance/+/836888 [5] https://review.opendev.org/c/openstack/governance/+/849606 [6] https://etherpad.opendev.org/p/zuul-config-error-openstack [7] http://lists.openstack.org/pipermail/openstack-discuss/2022-May/028603.html [8] https://review.opendev.org/c/openstack/governance/+/851859 [9] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [10] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[nova] Is the VMware NSX CI still being maintained?
by melanie witt 18 Aug '22

18 Aug '22

Hi all, I have noticed lately the VMware NSX CI does not seem to be running since March/April of this year based on casual gerrit search [1]. More recently, maybe starting in May, I have seen it post comments on reviews but they say: Build failed - ext-nova-zuul : NOT_REGISTERED Does anyone know whether this job is still being maintained and if it will be fixed? Thanks, -melwitt [1] https://review.opendev.org/q/reviewer:%2522VMware+NSX+CI%2522+project:opens…

1 0

Re: [all][tc] Technical Committee next weekly meeting on 2022 Aug 18 at 1500 UTC
by Ghanshyam Mann 18 Aug '22

18 Aug '22

Hello Everyone, Below is the agenda for Today's TC meeting schedule at 1500 UTC. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting * Roll call * Follow up on past action items * Gate health check ** Bare 'recheck' state *** https://etherpad.opendev.org/p/recheck-weekly-summary * 2023.1 cycle PTG Planning ** Encourage projects to schedule 'operator hours' as a separate slot in PTG(avoiding conflicts among other projects 'operator hours') * Open Reviews ** https://review.opendev.org/q/projects:openstack/governance+is:open -gmann

1 0

[neutron] Drivers meeting agenda - 19.08.2022.
by Lajos Katona 18 Aug '22

18 Aug '22

Hi Neutron Drivers, The agenda for tomorrow's drivers meeting is at [1]. We have the following RFEs to discuss tomorrow: [RFE] Add possibility to define default security group rules (#link https://bugs.launchpad.net/neutron/+bug/1983053 ) [rfe][fwaas]support standard_attrs for firewall_group (#link https://bugs.launchpad.net/neutron/+bug/1986906 ) [1] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers#Agenda See you at the meeting tomorrow. Lajos Katona (lajoskatona)

1 0

Weird behaviour on a provider net
by Derek O keeffe 18 Aug '22

18 Aug '22

Hi all, We have an Openstack Victoria cluster deployed and a provider network (IPv4) created that worked fine for months. Lately we've noticed that about 30-40% of the VM's that are spun up using this network are inaccessible over ssh, Permission denied (publickey). Also, if you add a customisation script to create a password for the Ubuntu user that fails too. Initially we thought it was confined to one/two compute nodes but further testing this week shows that it can be any of the 6 compute nodes we have and always the original two that we identified as being the problem. If we create the VM's from the cli and send them to specific hosts everything works fine including the original two hosts that had issues. We're finding it hard to nail down the cause of this because it's not consistent behaviour so any tips on where to investigate would be welcome, we have a second provider net (IPv4 & IPv6) that works fine and have went through all the configs to see if there's any difference and all are identical over the hosts. Thanks in advance for any info. Regards,Derek

2 1

Which deployment Method for a production cloud ?
by KK CHN 18 Aug '22

18 Aug '22

List, I want to install Openstack Xena version on a DELL ( R650 2 CPU and 40 cores . 2.4 TB) server machine. Operating System preference is Debian 10. I want to deploy this for production use with Ceph OSDs. There are four methods described in the URL : Confused which to select. https://docs.openstack.org/xena/deploy/ 1. Using Charms deployment 2. Deploy openstack using Ansible in Docker containers 3. Openstack - Ansible Deployment guide. 4. Triple O deployment guide Which method do I have to follow a full fledged production deployment ? why ? Going ahead with Ansible and Docker is a best option or not ? Your kind guidance requested.. Thanks in advance, Krish ps:- Once Completed this installation I have to extend this as a High available(HA) Multi Node cloud. (multi node production cloud with 3 Controllers, 6 compute Nodes and 3 Storage nodes with Ceph OSD pools) . Request to consider this future scalability requirement while answering my query.

2 1

[openstack-ansible][wallaby] lxc-containers-create.yml fails when specifying a container group
by Taltavull Jean-François 18 Aug '22

18 Aug '22

Hello everyone, Whatever the container group, lxc-containers-create playbook fails when specifying the group with -l option. For example : $ sudo openstack-ansible lxc-containers-create.yml -l repo_container Fails with: TASK [lxc_container_create : Gather variables for each operating system] ******************************************************************************************************************************************************************************************************fatal: [p3controller1a_repo_container-b54c9eba]: FAILED! => {"msg": "No file was found when using first_found. Use errors='ignore' to allow this task to be skipped if no files are found"} fatal: [p3controller1b_repo_container-1c7f8c1f]: FAILED! => {"msg": "No file was found when using first_found. Use errors='ignore' to allow this task to be skipped if no files are found"} fatal: [p3controller1c_repo_container-1e73e8a7]: FAILED! => {"msg": "No file was found when using first_found. Use errors='ignore' to allow this task to be skipped if no files are found"} Any similar experience ? Any idea ? Thank you, Jean-Francois

2 2

[Neutron][Octavia][ovn-octavia-provider] proposing Fernando Royo for ovn-octavia-provider core reviewer
by Lajos Katona 18 Aug '22

18 Aug '22

Hi I would like to propose Fernando Royo (froyo) as a core reviewer to the ovn-octavia-provider project. Fernando is very active in the project (see [1] and [2]). As ovn-octavia-provider is a link between Neutron and Octavia I ask both Neutron and Octavia cores to vote by answering to this thread, to have a final decision. Thanks for your consideration. [1]: https://review.opendev.org/q/owner:froyo%2540redhat.com [2]: https://www.stackalytics.io/report/contribution?module=neutron-group&projec… Cheers Lajos

6 6

[cinder] Bug deputy report for week of 08-17-2022
by Sofia Enriquez 17 Aug '22

17 Aug '22

This is a bug report from 08-10-2022 to 08-17-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Medium - https://bugs.launchpad.net/cinder/+bug/1985962 "Wrong volume_quota exception msg when extending volume_size." Fix proposed to master. Low - https://bugs.launchpad.net/cinder/+bug/1985065 "[Storwize] mkhost command failure". Fix proposed to master. - https://bugs.launchpad.net/cinder/+bug/1986658 "NetApp driver is hitting the QoS policy limit due soft deletion." Fix proposed to master. Cheers, Sofia -- 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

[oslo][stable] Backport of the default value of the config option change
by Slawek Kaplonski 17 Aug '22

17 Aug '22

Hi, Some time ago oslo.messaging changed default value of the "heartbeat_in_pthread" config option to "True" [1]. As was noticed some time ago, this don't works well with nova-compute - see bug [2] for details. Recently we noticed in our downstream Red Hat OpenStack, that it's not only nova-compute which don't works well with it and can hangs. We saw the same issue in various neutron agent processes. And it seems that it can be the same for any non-wsgi service which is using rabbitmq to send heartbeats. So giving all of that, I just proposed change of the default value of that config option to be "False" again [3]. And my question is - would it be possible and acceptable to backport such change up to stable/wallaby (if and when it will be approved for master of course). IMO this could be useful for users as using this option set as "True" be default don't makes any sense for the non-wsgi applications really and may cause more bad then good things really. What are You opinions about it? [1] https://review.opendev.org/c/openstack/oslo.messaging/+/747395 [2] https://bugs.launchpad.net/oslo.messaging/+bug/1934937 [3] https://review.opendev.org/c/openstack/oslo.messaging/+/852251/ -- Slawek Kaplonski Principal Software Engineer Red Hat

13 14

[glance] Antelope PTG Planning
by Abhishek Kekane 17 Aug '22

17 Aug '22

Hi everyone, Virtual PTG for the Antelope cycle will be held between 17th - 21st October [1]. 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://openinfra-ptg.eventbrite.com/ [2] https://etherpad.opendev.org/p/antelope-ptg-glance-planning Thanks, Abhishek Kekane

1 0

[kolla-ansible][octavia] need networking help
by Stuart Whitman 17 Aug '22

17 Aug '22

Hello, I enabled Octavia on a kolla-ansible installed Openstack cluster. When I try to launch a loadbalancer instance, the octavia-worker.log file reports: "WARNING octavia.amphorae.drivers.haproxy.rest_api_driver [-] Could not connect to instance." I researched enough to know that the problem has to do with networking between the controller and the lb-mgmt-net network. I initially overlooked this in the kolla-ansible Octavia documentation: "If using a VLAN provider network, ensure that the traffic is also bridged to Open vSwitch on the controllers." But, I don't know how to do it. Help to create the necessary bridge would be greatly appreciated. Thanks, -Stu _____________________________________ The information contained in this e-mail and any attachments from Group W may contain confidential and/or proprietary information and is intended only for the named recipient to whom it was originally addressed. If you are not the intended recipient, be aware that any disclosure, distribution, or copying of this e-mail or its attachments is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately of that fact by return e-mail and permanently delete the e-mail and any attachments to it.

4 6

[horizon][plugins] Horizon angular based plugins are broken after migrating to angularjs 1.8.2.2
by vishal manchanda 16 Aug '22

16 Aug '22

Hello everyone, Horizon team recently migrated XStatic-Angular 1.5.8.0->1.8.2.2 [1] and after that many horizon angular based plugins start failing [2]. We already fixed these issues in horizon [3]. So I guess we need to fix the similar thing in horizon plugins. Why did we migrated Angular 1.5.8.0->1.8.2.2? The angularjs version is updated 1.5.8.0->1.8.2.2 to include the CVE fixed in the latest version. Also, there is a security bug reported for the same [4]. I have also created an etherpad to track the progress for failed horizon plugins [5]. Action items for the horizon plugins team either fixed their plugins or review/merge the patch pushed by horizon team members on priority basis to fix the gate. The npm jobs are failing in below horizon plugins : • ironic-ui • octavia-dashboard • senlin-dashboard • designate-dashboard • vitrage-dashboard • murano-dashboard • zaqar-ui • zun-ui • magnum-ui In case of any queries, please feel free to reach out to Horizon channel #openstack-horizon. Thanks & Regards, Vishal Manchanda(irc: vishalmanchanda) [1] https://review.opendev.org/c/openstack/requirements/+/844099 [2] https://review.opendev.org/c/openstack/horizon/+/845733 [3] https://review.opendev.org/c/openstack/horizon/+/843346 [4] https://bugs.launchpad.net/horizon/+bug/1955556 [5] https://etherpad.opendev.org/p/Fix_Horizon_Plugins_With_Angularjs_v1.8.2.2

2 2

[neutron] CI meeting - agenda for 16.08.2022
by Slawek Kaplonski 16 Aug '22

16 Aug '22

Hi, Agenda for today's Neutron CI meeting is at [1]. This will be video meeting, which we will have on [2]. [1] https://etherpad.opendev.org/p/neutron-ci-meetings [2] https://meetpad.opendev.org/neutron-ci-meetings -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

Metering, billing software components for Openstack
by KK CHN 16 Aug '22

16 Aug '22

List, We are running our datacenter using the Ussuri version. Planning to upgrade to higher versions soon. 1. What are the metering, billing and metric solutions for ussuri and other latest openstack versions ? 2. The ceilometer and gnocchi is the way forward or ? People are using any latest tools for the best results pls share your thoughts. Any thoughts most welcome. Krish

3 3

[openstack-helm] No meeting tomorrow
by Gage Hugo 16 Aug '22

16 Aug '22

Hey team, Since there's nothing on the agenda for tomorrow's meeting, it has been cancelled. We will meet as scheduled next week. Thanks!

1 0

[neutron] Bug deputy report (week starting on Aug-8-2022)
by Bernard Cafarelli 16 Aug '22

16 Aug '22

Hello neutrinos, it is time again to start a new bug deputy rotation: https://wiki.openstack.org/wiki/Network/Meetings#Bug_deputy and my turn for last week's bugs A relatively quiet week (it is the holiday season in quite a few parts of the world!) with fixes already merged for most bugs. Two bugs to highlight though (and in need of some neutron eyes): a manila job failing with IPv6 VMs (1940324) and a live-migration issue (1986003) Critical * neutron-tempest-plugin failing on networking-bagpipe tests - https://bugs.launchpad.net/neutron/+bug/1986534 networking-bagpipe also needed update after neutron-lib constants rehoming, fix merged: https://review.opendev.org/c/openstack/networking-bagpipe/+/852867 High * [CI][Devstack] Failing to SSH to test VMs with IPv6 - https://bugs.launchpad.net/neutron/+bug/1940324 LVM job for manila fails on IPv6 hosts with socket.timeout: timed out, if CI/IPv6 gurus can take a look and help manila team Medium * neutron-dynamic-routing: Continuous warning because of missing context wrapper - https://bugs.launchpad.net/neutron/+bug/1984238 Previous fix missed one context wrapper, fix by tkajinam https://review.opendev.org/c/openstack/neutron-dynamic-routing/+/852775 Low * Replace "click" with "cliff" - https://bugs.launchpad.net/neutron/+bug/1985049 Several patches in progress to update tools using click, see LP for details Original started as bug to add click to requirements - https://bugs.launchpad.net/neutron/+bug/1984109 * [OVN] Remove "FIPAddDeleteEvent" event - https://bugs.launchpad.net/neutron/+bug/1985096 Unassigned cleanup bug, workaround is not needed since OVN v20.03.0 * DeprecationWarning: Using the 'user' argument is deprecated in version '2.18' and will be removed in version '3.0', please use the 'user_id' argument instead - https://bugs.launchpad.net/neutron/+bug/1986418 Fix merged https://review.opendev.org/c/openstack/neutron/+/853050 * DeprecationWarning: invalid escape sequence \u - https://bugs.launchpad.net/neutron/+bug/1986421 Fix merged https://review.opendev.org/c/openstack/neutron/+/853051 * PkgResourcesDeprecationWarning: <MagicMock name='execute().split().__getitem__().__getitem__()' id='140417024565696'> is an invalid version and will not be supported in a future release - https://bugs.launchpad.net/neutron/+bug/1986428 Fix also merged: https://review.opendev.org/c/openstack/neutron/+/853053 Thanks Takashi Natsume for this series of deprecation fixes Untriaged * Exception in concurrent port binding activation - https://bugs.launchpad.net/neutron/+bug/1986003 Live migration issue that I did not have time to dig into - any takers? Have a nice week! -- Bernard Cafarelli

1 0

[Ansible] [Yoga] Infra LXC Cache Failure
by Father Vlasie 16 Aug '22

16 Aug '22

Hello everyone! I am trying to deploy Openstack Ansible with Rocky Linux 8.6. I have 3 infra nodes all running the same software/hardware specifications but the 3rd one keeps giving me the following error. This occurs when running setup-hosts.yml ---------- TASK [lxc_hosts : Ensure that the LXC cache has been prepared] ******************************************************************************* FAILED - RETRYING: [infra3]: Ensure that the LXC cache has been prepared (120 retries left). FAILED - RETRYING: [infra3]: Ensure that the LXC cache has been prepared (119 retries left). fatal: [infra3]: FAILED! => {"ansible_job_id": "205392349782.93369", "attempts": 3, "changed": true, "cmd": "chroot /var/lib/machines/rocky-8-amd64 /opt/cache-prep-commands.sh > /var/log/lxc-cache-prep-commands.log 2>&1", "delta": "0:00:16.353232", "end": "2022-08-15 12:59:42.058169", "finished": 1, "msg": "non-zero return code", "rc": 1, "results_file": "/root/.ansible_async/205392349782.93369", "start": "2022-08-15 12:59:25.704937", "started": 1, "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []} ---------- Thank you very much for any help! Father Vlasie

1 1