August 2022 - openstack-discuss - lists.openstack.org

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

[Octavia] Monitor through Listener Prometheus Protocol
by Vu Tuan Dat 15 Aug '22

15 Aug '22

HI, I installed Prometheus on controller nodes. However, My prometheus instance cannot connect to Listener Prometheus endpoint because it's binded to VIP only in network namespace. Anyone can help? Thanks in advanced, Dat

2 1

[Ansible] [Yoga] Set rsyslog not to containerise
by Father Vlasie 15 Aug '22

15 Aug '22

Hello everyone! I am trying to deploy Openstack Ansible with Rocky Linux 8.6. I have a rsyslog host that is somewhat underpowered (RAM and CPU) and I thought it might help to run rsyslog without containerisation. I have searched but I have not been able to find an example of this.My guess is that I need to create a file in /etc/openstack_deploy/env.d What syntax and commands do I need? I have searched but I could not find any examples... Thank you very much! Father Vlasie

2 1

[ironic] Proposing Jacob Anders to sushy-core
by Iury Gregory 15 Aug '22

15 Aug '22

Hello ironic-cores and sushy-cores, I would like to propose Jacob Anders (janders irc) for sushy-core. He made great contributions to improve sushy to cover corner cases from different HW in the last releases, you can find some of his contributions in [1], please vote with +1/-1. [1] https://review.opendev.org/q/owner:janders%2540redhat.com+project:openstack… -- *Att[]'s* *Iury Gregory Melo Ferreira * *MSc in Computer Science at UFCG* *Ironic PTL * *Senior Software Engineer at Red Hat Brazil* *Social*: https://www.linkedin.com/in/iurygregory *E-mail: iurygregory(a)gmail.com <iurygregory(a)gmail.com>*

3 2

[Ansible] [Yoga] Not recognising Rocky Linux as supported
by Father Vlasie 13 Aug '22

13 Aug '22

Hello everyone! I am trying to deploy Openstack Ansible with Rocky Linux 8.6 on my target hosts. The documentation here (https://docs.openstack.org/project-deploy-guide/openstack-ansible/latest/ta…) says " • Centos 8 Stream 64-bit * Derivitives: Rocky Linux” under the list of supported operation systems. Ansible does not seem to check for the existence of RHEL 8 systems. :( But when I run “openstack-ansible setup-hosts.yml” I get the error: TASK [Check for a supported Operating System] ***************************************************************************************** fatal: [infra1]: FAILED! => { "assertion": "(ansible_facts['distribution'] == 'Debian' and ansible_facts['distribution_release'] == 'bullseye') or (ansible_facts['distribution'] == 'Ubuntu' and ansible_facts['distribution_release'] == 'focal') or (ansible_facts['distribution'] == 'Ubuntu' and ansible_facts['distribution_release'] == 'jammy') or (ansible_facts['os_family'] == 'RedHat' and ansible_facts['distribution_major_version'] == '9')", "changed": false, "evaluated_to": false, "msg": "The only supported platforms for this release are Debian 11 (Bullseye), Ubuntu 20.04 LTS (Focal), Ubuntu 22.04 (Jammy) and CentOS 9 Stream.\n” What should I do? Thank you!

3 2

[all][tc] What's happening in Technical Committee: summary 2022 Aug 12: Reading: 5 min
by Ghanshyam Mann 13 Aug '22

13 Aug '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Aug 11. Most of the meeting discussions are summarized in this email. Meeting full logs are available @https://meetings.opendev.org/meetings/tc/2022/tc.2022-08-11-15.00.log.html * Next TC weekly meeting will be on Aug 18 Thursday at 15:00 UTC, feel free to add the topic on the agenda[1] by Aug 17. 2. What we completed this week: ========================= * None in this week. 3. Activities In progress: ================== TC Tracker for Zed cycle ------------------------------ * Zed tracker etherpad includes the TC working items[3], Two are completed and others items are in-progress. Open Reviews ----------------- * Two open reviews for ongoing activities[4]. OpenStack TC + Board member meeting ------------------------------------------------ As you might know, OpenStack TC and Board member had a informal meeting on Aug 10[5][6], I am summarizing the discussion here. The Openstack TC has presented the 'OpenStack Updates' to Board meeting in berlin. One of the key part of the updates were 'OpenStack community Challenges' and we could not finish the discussion or brainstorm on these in berlin meeting. We decided to continue the discussion on those (Slide#21)[7]. In this call, we can only cover the first challenge only 'Less Interaction with Operators & Users'. There is no doubt that we are facing this issue at noticeable level (RBAC is good example where we lacked the operator/user feedback). A lot of things including ML, events are discussed on why it is happening and how to improve it. Having ops meetup as a separate event is something many members raised concern about and it will be good to merge these events into other community events like Summit, PTG etc. To try the first step towards that we can invite or welcome operators in Oct virtual PTG and give them a feeling on merging the events with developers event can be beneficial to both the group. On that, Dan suggested the idea of scheduling the 'Operatos Hours' per project in PTG and there we will keep the discussion on operator-centric and the format they want. We continued the discussion on this in TC weekly meeting where we had mixed suggestions on the 'Operator Hours' schedule, either to ask each project to schedule it in their room and operator join or other way around. Before deciding any format, we will be asking operators about their preference. We will continue the discussion on 'OpenStack community Challenges' in the next call which is schedule on 20:00 UTC on Wednesday, November 16[8]. If anyone is interested, feel free to join it. 2023.1 cycle Technical Election (TC + PTL) planning ------------------------------------------------------------- Not much update on this but we will be seeing the election schedule proposed soon. 2023.1 cycle TC PTG planning ------------------------------------ We discussed about how to best encourage/invite operators into the PTG (I wrote in the above section) and based on the operators feedback we will proceed next. We will continue the discussion in the next meeting also. 2021 User Survey TC Question Analysis ----------------------------------------------- No update on this. The survey summary is up for review[9]. Feel free to check and provide feedback. Zed cycle Leaderless projects ---------------------------------- Dale Smith volunteer to be PTL for Adjutant project [10] Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[11]12]. Project updates ------------------- * Retire openstack-helm-addons[13] 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[14]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [15] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://review.opendev.org/c/openstack/governance/+/849997 [3] https://etherpad.opendev.org/p/tc-zed-tracker [4] https://review.opendev.org/q/projects:openstack/governance+status:open [5] https://lists.openstack.org/pipermail/openstack-discuss/2022-August/029886.… [6] https://etherpad.opendev.org/p/2022-08-board-openstack-sync [7] https://docs.google.com/presentation/d/1yCiZy_9A6hURXD0BRdr33OlK7Ugch5EgSvF… [8] https://lists.openstack.org/pipermail/openstack-discuss/2022-August/029968.… [9] https://review.opendev.org/c/openstack/governance/+/836888 [10] https://review.opendev.org/c/openstack/governance/+/849606 [11] https://etherpad.opendev.org/p/zuul-config-error-openstack [12] http://lists.openstack.org/pipermail/openstack-discuss/2022-May/028603.html [13] https://review.opendev.org/c/openstack/governance/+/849997 [14] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [15] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

Re: [Ansible] [Yoga] Not recognising Rocky Linux as supported
by Father Vlasie 13 Aug '22

13 Aug '22

> On Aug 12, 2022, at 3:13 PM, openstack-discuss-request(a)lists.openstack.org wrote: > > Comparing https://opendev.org/openstack/openstack-ansible/src/branch/stable/yoga/play… <https://opendev.org/openstack/openstack-ansible/src/branch/stable/yoga/play…> to https://opendev.org/openstack/openstack-ansible/src/branch/master/playbooks… <https://opendev.org/openstack/openstack-ansible/src/branch/master/playbooks…> it appears that OpenStack Ansible has removed CentOS Stream/RHEL/Rocky 8 support on master, but the assertion allows it under Yoga. Based on the failure above you must be running master OSA? I would try running the Yoga branch instead. > > The master branch documentation likely needs to be updated as well. That worked perfectly, thank you! :)

1 0

[tc] November 2022 OpenInfra Board Sync
by Jeremy Stanley 12 Aug '22

12 Aug '22

The Open Infrastructure Foundation Board of Directors is endeavoring to engage in regular check-ins with official OpenInfra projects. The goal is for a loosely structured discussion one-hour in length, involving members of the board and the OpenStack TC, along with other interested community members. This is not intended to be a formal presentation, and no materials need to be prepared in advance. I've started an Etherpad where participants can brainstorm potential topics of conversation, time-permitting: https://etherpad.opendev.org/p/2022-11-board-openstack-sync At the conclusion of the August 10 discussion, we agreed to tentatively schedule the next call for 20:00 UTC on Wednesday, November 16, so I've attached a calendar file which can serve as a convenient schedule hold for this, in case anyone needs it. -- Jeremy Stanley

1 0

OpenStack User Survey
by Jimmy McArthur 12 Aug '22

12 Aug '22

Hi Everyone - Just a quick reminder to please take the OpenStack User Survey [1] This vitally important survey provides direct, anonymized feedback to our Project Teams to help them build better software. If you run a deployment, no matter the size, please take 30 min out of your day to take this survey! Thank you, Jimmy [1] https://openstack.org/user-survey/

1 0

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

12 Aug '22

Development Focus ----------------- We are entering the last weeks of the Zed development cycle. From now until the final release, we'll send a countdown email like this every week. It's probably a good time for teams to take stock of their library and client work that needs to be completed yet. The non-client library freeze is coming up, followed closely by the client lib freeze. Please plan accordingly to avoid any last minute rushes to get key functionality in. General Information ------------------- Next week is the Extra-ATC freeze, in preparation for elections. All contributions to OpenStack are valuable, but some are not expressed as Gerrit code changes. Please list active contributors to your project team who do not have a code contribution this cycle, and therefore won't automatically be considered an Active Technical Contributor and allowed to vote. This is done by adding extra-atcs to https://opendev.org/openstack/governance/src/branch/master/reference/projec… before the Extra-ATC freeze on August 18th, 2022. A quick reminder of the upcoming freeze dates. Those vary depending on deliverable type: * General libraries (except client libraries) need to have their last feature release before Non-client library freeze (August 25th, 2022). Their stable branches are cut early. * Client libraries (think python-*client libraries) 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) 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. After feature freeze, cycle-with-rc deliverables need to produce a first release candidate (and a stable branch) before RC1 deadline (September 15th, 2022) * Deliverables following cycle-with-intermediary model can release as necessary, but in all cases before Final RC deadline (September 29th, 2022) Finally, now is also a good time to start planning what highlights you want for your deliverables in the cycle highlights. The deadline to submit an initial version for those is set to Feature freeze (September 1st, 2022). Background on cycle-highlights: http://lists.openstack.org/pipermail/openstack-dev/2017-December/125613.html Project Team Guide, Cycle-Highlights: https://docs.openstack.org/project-team-guide/release-management.html#cycle… knelson [at] openstack.org/diablo_rojo on IRC is available if you need help selecting or writing your highlights Upcoming Deadlines & Dates -------------------------- Extra-ATC freeze: August 18th, 2022 (R-7 week) 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) Next PTG: October 17-21, 2022 (virtual PTG!!!) Előd Illés irc: elodilles

1 0

[tripleo] gate blocker tripleo-ci-centos-9-undercloud-upgrade
by Marios Andreou 12 Aug '22

12 Aug '22

o/ tripleo please hold rechecks on master tripleo branch - we have a gate blocker for tripleo-ci-centos-9-undercloud-upgrade https://bugs.launchpad.net/tripleo/+bug/1984175 package/conflict/mirror issue not clear yet - grateful for pointers if you have them

5 10

About the meaning of compute nodes
by 정재철 11 Aug '22

11 Aug '22

If there are many nodes, is it possible to create a high-performance VM? (e.g. Can 2 1 core cpu nodes create 1 2 core cpu VM)

5 5

[tc] August 2022 OpenInfra Board Sync
by Jeremy Stanley 11 Aug '22

11 Aug '22

The Open Infrastructure Foundation Board of Directors is endeavoring to engage in regular check-ins with official OpenInfra projects. The goal is for a loosely structured discussion one-hour in length, involving members of the board and the OpenStack TC, along with other interested community members. This is not intended to be a formal presentation, and no materials need to be prepared in advance. I've started an Etherpad where participants can brainstorm potential topics of conversation, time-permitting: https://etherpad.opendev.org/p/2022-08-board-openstack-sync I've also created a Framadate poll has in order to identify a few preferred dates and times. Responses must be submitted by Friday, 2022-07-15, in order to provide the board members with time to pick from the available options. The poll can be found here: https://framadate.org/atdFRM8YeUtauSgC Feel free to reply here on the mailing list, or you can reach out to me directly by E-mail or as fungi in the #openstack-tc IRC channel, with any questions you may have. -- Jeremy Stanley

1 3

[kolla] Best way to restart controllers
by Yves Gd 11 Aug '22

11 Aug '22

Hi all, We are looking for the best way to process system upgrades on our controller nodes and especially the best way to restart them (we have 3 controllers nodes with routers ha). If we just restart them one by one (waiting long time between each), we have already seen rabbitmq cluster errors (needing a complete restart of rabbitmq). With a kolla stop, a restart and a kolla deploy, some docker containers are restarted on others nodes. The administration guides describes how to add or remove a node but not this simple case. How do you proceed securely? Thanks for all, Yves

1 0

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

11 Aug '22

Hello Everyone, The technical Committee's next weekly meeting is scheduled for 2022 Aug 11, at 1500 UTC. If you would like to add topics for discussion, please add them to the below wiki page by Wednesday, Aug 10 at 2100 UTC. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting -gmann

1 1

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

10 Aug '22

This is a bug report from 08-03-2022 to 08-10-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Low - https://bugs.launchpad.net/cinder/+bug/1984169 "RBD pool stats are reported inaccurately." Fix proposed to master. - https://bugs.launchpad.net/cinder/+bug/1984000 "Infinidat Cinder driver consistency groups feature is broken." 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

[neutron][ovn] ovn-bgp-agent EVPN mode question
by Satish Patel 10 Aug '22

10 Aug '22

Folks, I am trying to set up the following lab and so far everything looks good and working but I have some doubts or questions to make sure it's really working as expected. Lab Ref: https://ltomasbo.wordpress.com/2021/06/25/openstack-networking-with-evpn/ 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

1 0

Openstack Graphical processors virtualisation
by KK CHN 10 Aug '22

10 Aug '22

1. Does Openstack support GPU virtualization ? We are running a cloud using ussuri with KVM hypervisors. Is creation of vGPUs possible? Does KVM support GPU virtualization or any limitations? 2. What are the supported GPU types? (GRID GPU or GPUs attached to physical blades ) 3. If it supports GPU attached to physical blades, will live migration of the VM be supported. Will OpenStack be able to identify the next host which has an attached GPU and perform live migration, in case of the Failure of One Blade with attached GPU with resident VM. 4. What are the virtualization options if vGPU options are not supported by a particular GPU model? Thanks in advance, Krish

4 4

[PTG] [ironic] Antelope PTG new Etherpad
by Iury Gregory 10 Aug '22

10 Aug '22

Hello everyone, We changed the etherpad link to track the topics we will discuss at the PTG, instead of https://etherpad.opendev.org/p/ironic-ptg-planing-Columbus-OH we will be using https://etherpad.opendev.org/p/ironic-antelope-ptg Feel free to add any topics =) -- *Att[]'s* *Iury Gregory Melo Ferreira * *MSc in Computer Science at UFCG* *Ironic PTL * *Senior Software Engineer at Red Hat Brazil* *Social*: https://www.linkedin.com/in/iurygregory *E-mail: iurygregory(a)gmail.com <iurygregory(a)gmail.com>*

1 0

Need help on rabbitmq
by AJ_ sunny 10 Aug '22

10 Aug '22

Hi team I am using kolla-ansible based openstack infra and getting below error in logs seems frequent rabbitmq disconnections <0.5023.16> closing AMQP connection <0.5023.16> (10.80.0.13:40356 -> 10.80.0.13:5672 - mod_wsgi:19:d3196668-57e5-46dc-8b69-78d73b5873a0): missed heartbeats from client, timeout: 60s AMQP server on 10.80.0.13:5672 is unreachable: [Errno 104] Connection reset by peer. Trying again in 1 seconds.: ConnectionResetError: [Errno 104] Connection reset by peer Is this bug or any resolution for fixing this issue? Thanks Arihant Jain

4 4

[tacker] IRC meeting on Aug 16 cancelled
by Yasufumi Ogawa 10 Aug '22

10 Aug '22

Hi team, Since many of us are going to have a vacation next week, I'll cancel the meeting on Aug 16th. Thanks, Yasufumi

1 0

Correct way to add firewall rules in tripleo | Wallaby
by Swogat Pradhan 10 Aug '22

10 Aug '22

Hi, I am trying to add a rule for zabbix in my tripleo wallaby setup on top of centos 8 stream. i followed https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/feature… but got the error message: [ERROR]: Failed, module return: {'msg': 'value of action must be one of: append, insert, got: accept', 'failed': True, 'invocation': {'module_args': {'state': 'present', 'action': 'accept', 'jump': 'ACCEPT', 'chain': 'INPUT', 'protocol': 'tcp', 'source': '172.25.161.50', 'ctstate': ['NEW'], 'ip_version': 'ipv4', 'comment': '301 allow zabbix ipv4', 'destination_port': '10050', 'table': 'filter', 'match': [], 'syn': 'ignore', 'flush': False}}, 'warnings': ["The value 10050 (type int) in a string field was converted to '10050' (type string). If this does not look like what you expect, quote the entire value to ensure it does not change."], '_ansible_parsed': True} [ERROR]: Failed, return data: {'stdout': None, 'stderr': None, 'msg': 'value of action must be one of: append, insert, got: accept', 'cmd': None, 'rc': 0, 'failed': True} 2022-07-21 01:27:33.335477 | 48d539a1-1679-1e80-25fd-000000005aa1 | TASK | Manage firewall rules 2022-07-21 01:27:33.351515 | 48d539a1-1679-1e80-25fd-000000005542 | FATAL | Manage firewall rules | overcloud-controller-0 | error={"changed": false, "cmd": null, "msg": "value of action must be one of: append, insert, got: accept", "rc": 0, "stderr": null, "stdout": null} When i tried the following link: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/15… <https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/15…> my script is running fine but rules are not updated in iptables for zabbix. Can you please suggest a correct approach to open port 10050 in tripleo? With regards, Swogat Pradhan

2 1

Security vulnerabilities in Horizon dashboard | Openstack Wallaby | Tripleo | Openstack Horizon
by Swogat Pradhan 09 Aug '22

09 Aug '22

Hi, I am setting up an openstack wallaby cloud for a client using tripleo. After setting everything up the client ran a WEB scan and found some vulnerabilities (attached snapshot for reference). Can you please guide me on how to fix these vulnerabilities in the dashboard service? With regards, Swogat pradhan

2 3

[openstack-ansible] Meeting on August 16 is cancelled
by Dmitriy Rabotyagov 09 Aug '22

09 Aug '22

Hi everyone, Since several core participants won't be able to present at the meeting it was decided to cancel the Team meeting on 16th of August 2022.

1 0

[nova] Review guide for PCI tracking for Placement patches
by Balazs Gibizer 09 Aug '22

09 Aug '22

Hi Nova, The first batch of patches are up for review for the PCI tracking for Placement feature. These mostly covers two aspects of the spec[1]: 1) renaming [pci]passthrough_whitelist to [pci]device_spec 2) pci inventory reporting to placement, excluding existing PCI allocation healing in placement This covers the first 4 sub chapters of Proposed Change chapter of the spec[1] up until "PCI alias configuration". I noted intentional deviations from the spec in the spec review [2] and I will push a follow up to the spec at some point fixing those. I tried to do it in small steps hence the long list of commits[3]: #2) pci inventory reporting to placement, excluding existing PCI allocation healing in placement 5827d56310 Stop if tracking is disable after it was enabled before a4b5788858 Support [pci]device_spec reconfiguration 10642c787a Reject devname based device_spec config b0ad05fb69 Ignore PCI devs with physical_network tag f5a34ee441 Reject mixed VF rc and trait config c60b26014f Reject PCI dependent device config 5cf7325221 Extend device_spec with resource_class and traits eff0df6a98 Basics for PCI Placement reporting #1) renaming [pci]passthrough_whitelist to [pci]device_spec adfe34080a Rename whitelist in tests ea955a0c15 Rename exception.PciConfigInvalidWhitelist to PciConfigInvalidSpec 55770e4c14 Rename [pci]passthrough_whitelist to device_spec There is a side track branching out from "adfe34080a Rename whitelist in tests" to clean up the device spec handling[4]: 514500b5a4 Move __str__ to the PciAddressSpec base class 3a6198c8fb Fix type annotation of pci.Whitelist class f70adbb613 Remove unused PF checking from get_function_by_ifname b7eef53b1d Clean up mapping input to address spec types 93bbd67101 Poison /sys access via various calls in test 467ef91a86 Remove dead code from PhysicalPciAddress 233212d30f Fix PciAddressSpec descendants to call super.__init__ ad5bd46f46 Unparent PciDeviceSpec from PciAddressSpec cef0d2de4c Extra tests for remote managed dev spec 2fa2825afb Add more test coverage for devname base dev spec adfe34080a Rename whitelist in tests This is not a mandatory part of the feature but I think they improve the code in hand and even fixing some small bugs. I will continue with adding allocation healing for existing PCI allocations. Any feedback is highly appreciated. Cheers, gibi [1] https://specs.openstack.org/openstack/nova-specs/specs/zed/approved/pci-dev… [2] https://review.opendev.org/c/openstack/nova-specs/+/791047 [3] https://review.opendev.org/q/topic:bp/pci-device-tracking-in-placement [4] https://review.opendev.org/q/topic:bp/pci-device-spec-cleanup

1 2

[publiccloud-sig] A new start for Public Cloud SIG
by Tobias Rydberg 09 Aug '22

09 Aug '22

Hi everyone, In Berlin it became clear that there is a big interest in restarting the Public Cloud SIG. Thank you all for your contributions in that forum session [0] and the interest in participating in the work of this SIG. A lot of good ideas of what we should focus on was identified, with a clear focus of interoperability and standardization, to make the experience of using OpenStack as an end-user even better. Standardization of images and flavors - naming, metadata etc - being one of them, working closely with InterOp WG regarding the checks and governance of the OpenStack Powered Program another. The ultimate goal could be to reach a state where it is possible to start to federate between the public clouds, but for that to be possible on a more global scale we need to start with aligning the simple things. To kick this off, we will start with bi-weekly IRC meetings again, shape the goals kick of some work towards identified goals. Since we have an IRC channel (#openstck-publiccloud) my suggestion is that we will start there. Let's decide on suggestions for day and time for our bi-weekly meetings during the kick off meeting. Kick off meeting =========== When: Wednesday 10th of August at 1400 UTC Where: IRC in channel #openstack-publiccloud I created an etherpad for our first meeting [1], feel free to add items to the agenda or other suggestions on goals etc that you might have prior to the meeting. Hope to see at IRC in August! [0] https://etherpad.opendev.org/p/berlin-summit-future-public-cloud-sig [1] https://etherpad.opendev.org/p/publiccloud-sig-kickoff BR, Tobias Rydberg

2 2

[announcement] [debian] Debian Buster with OpenStack Rocky will receive LTS support
by Thomas Goirand 08 Aug '22

08 Aug '22

Hi! After some discussion with the folks taking care of the Debian LTS project, we decided that we will attempt to support OpenStack Rocky, running on Debian 10 (aka: Buster), for another 2 years, together with the rest of the distribution. In the past, we decided that we wouldn't do it, and that OpenStack would be part of the list of unsupported packages, because it was too difficult to maintain. However, it is my opinion that this has changed, because: - The codebase is evolving slower - I do have all the tooling to re-do a Rocky deployment if needed - There's a lot less CVE per year than it used to be (10 years ago, it was 1 every 2 weeks on average, now we have like 2 grave issue per year...). - I'm confident that if there's a grave issue, I'll be able to find help from the this wonderful community (it happened in the past...). Also, some sponsors of the Debian LTS project are actually running OpenStack Rocky on Debian. So it makes sense to help them. It is to be noted that I will not be the person doing the actual security backports, but I'll be there in case the person doing it needs help from me (for example, to do a deployment and manual regression testing). Hoping this will help OpenStack users running on Debian, Cheers, Thomas Goirand (zigo)

1 0

[all] Automatic update of Python jobs in Zuul project configuration
by Pierre Riteau 08 Aug '22

08 Aug '22

Hello, A patch submitted to python-blazarclient by yoctozepto [1] made me realise the automatic change of Python jobs from yoga to zed missed various repositories [2], mostly python clients. Is there a reason for this? Also, one can easily find projects which are using even older job templates (xena or earlier). Thanks, Pierre Riteau (priteau) [1] https://review.opendev.org/c/openstack/python-blazarclient/+/851903 [2] https://codesearch.openstack.org/?q=openstack-python3-yoga-jobs&i=nope&lite…

3 6

[kolla-ansible] why does not the bootstrap create the docker bridge?
by wodel youchi 08 Aug '22

08 Aug '22

Hi, The bootstrap installs docker but it does not create the docker bridge, why? Regards.

2 1

[Oslo] IRC meeting.
by Daniel Mats Niklas Bengtsson 08 Aug '22

08 Aug '22

Hi there, I'm sorry, I was on vacation and then I had personal problems. We are still in the summer period and I think there are still people on vacation, I suggest resuming meetings in September. What do you think?

1 0

[neutron] Bug Deputy Report August 01 - 07
by Elvira Garcia Ruiz 08 Aug '22

08 Aug '22

Hi, I was the bug deputy last week. Find the summary below: High: ------- - [ovn]router_interface port probability cannot be up https://bugs.launchpad.net/neutron/+bug/1983530 Fix: https://review.opendev.org/c/openstack/neutron/+/851997 - l2_pop does unnecessary db fetches for incompatible network types https://bugs.launchpad.net/neutron/+bug/1983558 Fix: https://review.opendev.org/c/openstack/neutron/+/852089 Medium: ----------- - [OVN] Old DNS servers are served by DHCP after dns_servers option is updated https://bugs.launchpad.net/neutron/+bug/1983270 Assigned to me Low: ------- - Neutron should clean up ACLs in OVN NB DB when a remote security group is deleted https://bugs.launchpad.net/neutron/+bug/1983600 Unassigned Kind regards! Elvira

1 0

[Cinder][NFS][Openstack-Ansible]
by Dave Hall 08 Aug '22

08 Aug '22

Hello, I seem to have gotten myself in a bit of a mess trying to set up Cinder with an NFS back-end. After working with Glance and NFS, I started on Cinder. I noticed immediately that there weren't any NFS mounts in the Cinder-API containers like there were in the Glance-API containers. Also that there were no NFS packages in the Cinder-API containers. In reading some Cinder documentation, I also got the impression that each Cinder host/container needs to have its own NFS store. Pawing through the playbooks and documentation I saw that unlike Glance, Cinder is split into two pieces - Cinder-API and Cinder-Volume. I found cinder-volume.yml.example in env.d, activated it, and created Cinder-Volume containers on my 3 infra hosts. I also created 3 separate NFS shares and changed the storage-hosts section of my openstack_user_config.yml accordingly. After this I found that while I was able to create volumes, the prep_volume part of launching an instance was failing. Digging in, I found: # openstack volume service list +------------------+-------------------------------------------------------+------+---------+-------+----------------------------+ | Binary | Host | Zone | Status | State | Updated At | +------------------+-------------------------------------------------------+------+---------+-------+----------------------------+ | cinder-volume | C6220-9@nfs_volume | nova | enabled | down | 2022-07-23T02:46:13.000000 | | cinder-volume | C6220-10@nfs_volume | nova | enabled | down | 2022-07-23T02:46:14.000000 | | cinder-volume | C6220-11@nfs_volume | nova | enabled | down | 2022-07-23T02:46:14.000000 | | cinder-scheduler | infra36-cinder-api-container-da8e100f | nova | enabled | up | 2022-08-06T13:29:10.000000 | | cinder-scheduler | infra38-cinder-api-container-27219f93 | nova | enabled | up | 2022-08-06T13:29:10.000000 | | cinder-scheduler | infra37-cinder-api-container-ea7f847b | nova | enabled | up | 2022-08-06T13:29:10.000000 | | cinder-volume | C6220-9@nfs_volume1 | nova | enabled | up | 2022-08-06T13:29:10.000000 | | cinder-volume | infra37-cinder-volumes-container-5b9635ad@nfs_volume | nova | enabled | down | 2022-08-04T18:32:53.000000 | | cinder-volume | infra36-cinder-volumes-container-77190057@nfs_volume1 | nova | enabled | down | 2022-08-06T13:03:03.000000 | | cinder-volume | infra38-cinder-volumes-container-a7bcfc9b@nfs_volume | nova | enabled | down | 2022-08-04T18:32:53.000000 | | cinder-volume | infra37-cinder-volumes-container-5b9635ad@nfs_volume2 | nova | enabled | down | 2022-08-06T13:03:05.000000 | | cinder-volume | C6220-10@nfs_volume2 | nova | enabled | up | 2022-08-06T13:29:10.000000 | | cinder-volume | C6220-11@nfs_volume3 | nova | enabled | up | 2022-08-06T13:29:10.000000 | | cinder-volume | infra38-cinder-volumes-container-a7bcfc9b@nfs_volume3 | nova | enabled | down | 2022-08-06T13:03:03.000000 | +------------------+-------------------------------------------------------+------+---------+-------+----------------------------+ Thinking I could save this, I used containers-lxc-destroy.yml to destroy my cinder-volumes containers and deactivated cinder-volume.yml.example. Then I ran setup-hosts.yml, which has restored the cinder-volumes containers even though is_metal: false has been removed. Clearly a stronger intervention will be required. I would like to fully get rid of the cinder-volumes containers and go back to an is_metal: true scenario. I also need to get rid of the unnumbered nfs_volume referenes, which I assume are in some cinder config file somewhere. Below is a clip from my openstack_user_config.yml: storage_hosts: infra36: ip: 172.29.236.36 container_vars: cinder_backends: nfs_volume1: volume_backend_name: NFS_VOLUME1 volume_driver: cinder.volume.drivers.nfs.NfsDriver nfs_mount_options: "rsize=65535,wsize=65535,timeo=1200,actimeo=120" nfs_shares_config: /etc/cinder/nfs_shares_volume1 shares: - { ip: "172.29.244.27", share: "/NFS_VOLUME1" } infra37: ip: 172.29.236.37 container_vars: cinder_backends: nfs_volume2: volume_backend_name: NFS_VOLUME2 volume_driver: cinder.volume.drivers.nfs.NfsDriver nfs_mount_options: "rsize=65535,wsize=65535,timeo=1200,actimeo=120" nfs_shares_config: /etc/cinder/nfs_shares_volume2 shares: - { ip: "172.29.244.27", share: "/NFS_VOLUME2" } infra38: ip: 172.29.236.38 container_vars: cinder_backends: nfs_volume3: volume_backend_name: NFS_VOLUME3 volume_driver: cinder.volume.drivers.nfs.NfsDriver nfs_mount_options: "rsize=65535,wsize=65535,timeo=1200,actimeo=120" nfs_shares_config: /etc/cinder/nfs_shares_volume3 shares: - { ip: "172.29.244.27", share: "/NFS_VOLUME3" } Any advice would be greatly appreciated. Thanks. -Dave -- Dave Hall Binghamton University kdhall(a)binghamton.edu

4 8

Guide for Openstack installation with HA, OVN ?
by 박경원 07 Aug '22

07 Aug '22

3 2

[release] Release countdown for week R-8, Aug 08 - 12
by Előd Illés 06 Aug '22

06 Aug '22

General Information ------------------- The following cycle-with-intermediary deliverables have not done any intermediary release yet during this cycle: Ironic: * bifrost * ironic-prometheus-exporter * ironic-python-agent-builder * ironic-ui * networking-baremetal * networking-generic-switch OpenStackSDK: * python-openstackclient Swift: * swift Since these deliverables are traditionally released after our warning, we did not propose to change the release model to cycle-with-rc for them this time. Please let us know if any of the above project is considering the release model change anyway and we propose those patches. Otherwise immediately release an intermediary release, or acknowledge that a release needs to be done before RC1! We also published a proposed release schedule for the upcoming Antelope cycle. Please check out the separate thread: https://lists.openstack.org/pipermail/openstack-discuss/2022-July/029767.ht… Upcoming Deadlines & Dates -------------------------- Non-client library freeze: August 26th, 2022 (R-6 week) Client library freeze: September 1st, 2022 (R-5 week) Zed-3 milestone: September 1st, 2022 (R-5 week) Előd Illés irc: elodilles

1 0

[charms] General release of charmhub OpenStack xena/stable, ceph pacific/stable, OVN 21.09/stable tracks for Ubuntu 20.04 (focal) LTS
by Alex Kavanagh 06 Aug '22

06 Aug '22

Hi All The title may seem a bit odd because surely yoga is the current release, and zed is the current cycle? This is true, so a little explanation is in order. As the charm-guide [1] explains, in the previous cycle, the OpenStack, and supporting, charms moved from a single stable charm (for each component) that supported multiple releases, to a charm+track that targets a specific release [2]. The current release for the OpenStack charms is 'yoga' and thus there is a yoga/stable track. For a full explanation, please see [1]. Today, as part of our ongoing charmhub stable migration work this cycle, we have (re)released the 21.10 charms (that supported queens -> xena) as "xena" charms for OpenStack, "pacific" charms for Ceph, and "21.09" charms for OVN. The xena, pacific and 21.09-OVN channel charms have the same features as the existing 21.10 charms, include bug-fixes and relevant backports since the 21.10 charms were released, and have been re-tested and verified as a set prior to being released to the xena/stable channel. The full list of charms for a "Xena" OpenStack system, including ceph, OVN, mysql8, hacluster, rabbitmq-server, vault and others can be seen in the docs at [3]. The xena/pacific/21.09 charms have been designed to be upgradable from the 21.10 charms if you are running a xena OpenStack, but please consult the docs [4] about how to go about upgrading charms. The charms also are able to perform the OpenStack upgrade from wallaby -> xena, and again please consult the docs [5] for upgrading OpenStack. Our next stable maintenance release will be wallaby/pacific/20.12 (ovn), so please keep an eye out on the mailing lists. Thanks! [1] https://docs.openstack.org/charm-guide/latest/project/charm-delivery.html [2] https://juju.is/docs/olm/deploy-a-charm-from-charmhub#heading--specify-a-ch… [3] https://docs.openstack.org/charm-guide/latest/project/charm-delivery.html#c… [4] https://docs.openstack.org/project-deploy-guide/charm-deployment-guide/late… [5] https://docs.openstack.org/project-deploy-guide/charm-deployment-guide/late… -- Alex Kavanagh - Software Engineer OpenStack Engineering - Data Centre Development - Canonical Ltd

1 0

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

05 Aug '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Aug 4. Most of the topics I am summarizing in this email. This was a video call and recordings are available @https://www.youtube.com/watch?v=2CFrDKJsnEY * Next TC weekly meeting will be on Aug 11 Thursday at 15:00 UTC, feel free to add the topic on the agenda[1] by Aug 10. 2. What we completed this week: ========================= * Added charmed k8s operators to OpenStack Charms[2] 3. Activities In progress: ================== TC Tracker for Zed cycle ------------------------------ * Zed tracker etherpad includes the TC working items[3], Two are completed and others items are in-progress. Open Reviews ----------------- * Three open reviews for ongoing activities[4]. 2023.1 cycle Technical Election (TC + PTL) planning ------------------------------------------------------------- As we are in the R-9 week, its time to plan for the 2023.1 cycle election. As first step, we have volunteer to help executing this election. In TC meeting, Amy, Knikolla, and Slaweq volunteer to help and Ian might be available any ways. If you would like to get involved in the elections help, please let us know in #openstack-tc IRC channel. 2023.1 cycle TC PTG planning ------------------------------------ In TC meeting, we were gathering the data on who all will be traveling to in-person PTG or we should consider virtual PTG. But as you might have seen the announcement today, coming PTG will be 100% virtual[5]. 2021 User Survey TC Question Analysis ----------------------------------------------- No update on this. The survey summary is up for review[6]. Feel free to check and provide feedback. Zed cycle Leaderless projects ---------------------------------- Dale Smith volunteer to be PTL for Adjutant project [7] Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[8][9]. Project updates ------------------- * Retire openstack-helm-addons[10] 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[11]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [12] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://review.opendev.org/c/openstack/governance/+/849997 [3] https://etherpad.opendev.org/p/tc-zed-tracker [4] https://review.opendev.org/q/projects:openstack/governance+status:open [5] https://lists.openstack.org/pipermail/openstack-discuss/2022-August/029879.… [6] https://review.opendev.org/c/openstack/governance/+/836888 [7] https://review.opendev.org/c/openstack/governance/+/849606 [8] https://etherpad.opendev.org/p/zuul-config-error-openstack [9] http://lists.openstack.org/pipermail/openstack-discuss/2022-May/028603.html [10] https://review.opendev.org/c/openstack/governance/+/849997 [11] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [12] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

Fwd: October PTG Update
by Kendall Nelson 05 Aug '22

05 Aug '22

Hello Everyone, I wanted to provide an update on the October Project Teams Gathering (PTG). After discussing with community members and prospective sponsors, we have made the decision to pivot the event to 100% virtual to be as inclusive as possible. I know that this is not the ideal outcome and there are a lot of factors contributing to this decision, but we think it’s the best decision for the global community at this time. We are continuing to receive feedback on the value and importance of in-person PTGs; we just need to wait for other factors to be less of an obstacle If you have already registered, you should have been contacted for a full refund. We are going to use the same week for a virtual PTG and it will be free to attend, just like the previous ones. The registration is already live [1]. If you have any questions or feedback on this decision, please let us know. We will continue to monitor feedback as we make plans for a 2023 PTG. Thank you, Kendall (diablo_rojo) [1] https://openinfra-ptg.eventbrite.com

1 0

[manila] Feature Proposal Freeze in effect
by Carlos Silva 05 Aug '22

05 Aug '22

Greetings, Zorillas and interested stackers! As we defined in the release schedule, this week is the Manila Feature Proposal Freeze [1]. It means that all featureful changes should be already proposed and substantially completed with unit, functional and integration tests by EOW. If you have not managed to submit your featureful changes to gerrit yet, and would like to request an exception, please let me know by responding to this email thread. In case your exception is granted, we can get you some extra time. [1] https://releases.openstack.org/zed/schedule.html#z-manila-fpfreeze Thank you! carloss

1 0

[openstack] how to speed up live migration?
by Ignazio Cassano 05 Aug '22

05 Aug '22

Hello All, I am looking for a solution to speed up live migration. Instances where ram is used heavily like java application servers, live migration take a long time (more than 20 minutes for 8GB ram instance) and converge mode is already set to True in nova.conf. I also tried with post_copy but it does not change. After the first live migration (very solow) if I try to migrate again it is very fast. I presume the first migration is slow because memory fragmentation when an instance is running on the same compute node for a long time. I am looking for a solution considering the on my computing node I can have a little ram overcommit. Any case I am increasing the number of compute nodes to reduce it. Thanks Ignazio

6 21

[tripleo] gate blocker - tripleo-ci-centos-9-content-provider-wallaby
by Ananya Banerjee 05 Aug '22

05 Aug '22

Hi, We have a failure in tripleo-ci-centos-9-content-provider-wallaby which is blocking the gate. We are reverting [1] to clear the gate. Related Bug : https://bugs.launchpad.net/tripleo/+bug/1983585 [1] https://opendev.org/zuul/zuul-jobs/src/branch/master/roles/multi-node-bridg… Thanks, Ananya -- Ananya Banerjee, RHCSA, RHCE-OSP Software Engineer Red Hat EMEA <https://www.redhat.com/> anbanerj(a)redhat.com M: +491784949931 IM: frenzy_friday @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/>

2 1

Large files multipart upload fails - OpenStack Object Storage (swift)
by Komarov, Aleksandr 05 Aug '22

05 Aug '22

Hi to all! Please suggest how to fix the situation. When uploading files larger than 100GB, at the stage of multipart-manifest validation, we get 404 error for some segments that were previously uploaded successfully. As a result, the client receives a 400 response. Uploading a large file is not possible. Logs: Aug 1 13:18:30 swift01-object01 object-server: IP - - [01/Aug/2022:13:18:30 +0000] "PUT /mpathc/12130/AUTH_5affc785b3454cddb2d1f69ce62b4441/bucket/.file-segments/150.file/000 00032" 201 - "PUT http://domain-name/v1/AUTH_5affc785b3454cddb2d1f69ce62b4441/bucket/.file-se…" "tx30e82374b98845bab6883-0062e7d225" "proxy-server 8367" 128.7641 "-" 21577 0 Aug 1 13:18:30 swift01-object01 container-server: IP - - [01/Aug/2022:13:18:30 +0000] "PUT /mpathb/952/AUTH_5affc785b3454cddb2d1f69ce62b4441/bucket/.file-segments/150.file/00 000032" 201 - "PUT http://domain-name/mpathe/12130/AUTH_5affc785b3454cddb2d1f69ce62b4441/bucke…" "tx30e82374b98845bab6883-0062 e7d225" "object-server 24710" 0.0005 "-" 13211 0 Aug 1 14:01:46 swift01-object01 object-server: IP - - [01/Aug/2022:14:01:46 +0000] "HEAD /mpathc/12130/AUTH_5affc785b3454cddb2d1f69ce62b4441/bucket/.file-segments/150.file/00000032" 404 - "HEAD http://domain-name/v1/AUTH_5affc785b3454cddb2d1f69ce62b4441/bucket/.file-se…" "txf09676de38964ca299b77-0062e7dcc8" "proxy-server 8367" 0.0003 "-" 21579 0 At the same time, some segments successfully found. With files less than 50GB everything is fine.

2 2

[neutron] CI meeting on Aug 9 cancelled
by Slawek Kaplonski 05 Aug '22

05 Aug '22

Hi, I will be on PTO next week and on last CI meeting we decided to cancel CI meeting on Tuesday 9th of August. Have a great week and see You on the meeting on August 16th. -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

How do I deploy OpenStack open source cloud software on Red Hat Enterprise Linux 9.0?
by Turritopsis Dohrnii Teo En Ming 05 Aug '22

05 Aug '22

Subject: How do I deploy OpenStack open source cloud software on Red Hat Enterprise Linux 9.0? Good day from Singapore, How do I deploy OpenStack open source cloud software on Red Hat Enterprise Linux 9.0? I have just downloaded RHEL 9.0 ISO using RHEL Free Developer Subscription and installed it as a virtual machine inside Oracle VM VirtualBox. Windows 10 on my laptop is the host. Alternatively, can I deploy Red Hat OpenStack Platform in a Virtual Private Server (VPS)? I can make another order for a VPS just for this purpose. I already have 2 VPS servers just for deploying Virtualmin/Webmin web hosting control panel. If you can give me links to excellent and well-written guides and tutorials, it would be most useful. I want to try out open source software developed by NASA. Also, I have deployed Nextcloud previously. Now I want to try out OpenStack. Thank you. Regards, Mr. Turritopsis Dohrnii Teo En Ming Targeted Individual in Singapore 5 Aug 2022 Friday Blogs: https://tdtemcerts.blogspot.com https://tdtemcerts.wordpress.com

2 2

[glance] Error in store configuration. Adding images to store is disabled.
by Dave Hall 05 Aug '22

05 Aug '22

Hello, (Any help on this would be greatly appreciated. I've been chasing this for 2 weeks now...) I posted the other day that I had solved this issue, but now it's back. The primary glance-api error message is: Error in store configuration. Adding images to store is disabled. So why is my store disabled? Is there some command or config line that controls this? Shouldn't the store be enabled by default? The relevant stanza in my openstack-user-config.yml is image_hosts: # infra38: # ip: 172.29.236.38 # container_vars: # limit_container_types: glance # glance_remote_client: # - what: "172.29.244.27:/images" # where: "/var/lib/glance/images" # type: "nfs" # options: "_netdev,vers=3,proto=tcp,sec=sys" infra38: ip: 172.29.236.38 container_vars: glance_default_store: file glance_nfs_local_directory: "images" glance_nfs_client: - server: "172.29.244.27" remote_path: "/images" local_path: "/var/lib/glance/images" type: "nfs" options: "_netdev,vers=3,proto=tcp,sec=sys,noauto,user" config_overrides: "{}" The stanza that's commented out produced the same result. My user_variables.yaml does not have any lines pertaining to glance. Also, I've removed the stanzas for the other 2 infra hosts. The glance-api.conf file from the container is: [DEFAULT] # Disable stderr logging use_stderr = False debug = False use_journal = True fatal_deprecations = False bind_host = 172.29.238.205 bind_port = 9292 http_keepalive = True digest_algorithm = sha256 backlog = 4096 workers = 16 cinder_catalog_info = volumev3:cinderv3:internalURL enable_v2_api = True transport_url = rabbit:// glance:9e7f205ef620983a542b4f915420e50d33f774@172.29.238.84:5671, glance:9e7f205ef620983a542b4f915420e50d33f774@172.29.238.174:5671, glance:9e7f205ef620983a542b4f915420e50d33f774@172.29.239.33:5671//glance?ssl=1&ssl_version=TLSv1_2&ssl_ca_file= scrub_time = 43200 image_cache_dir = /var/lib/glance/cache/ image_cache_stall_time = 86400 image_cache_max_size = 10737418240 # defaults to true if RBD is used as default store show_image_direct_url = False show_multiple_locations = True enabled_backends = file:file,http:http,cinder:cinder [task] task_executor = taskflow [database] connection = mysql+pymysql:// glance:e6dd6f2ca946c9e6f72bb864387a@172.29.236.36/glance?charset=utf8&ssl_verify_cert=true max_overflow = 50 max_pool_size = 5 pool_timeout = 30 connection_recycle_time = 600 [keystone_authtoken] insecure = False auth_type = password auth_url = http://172.29.236.36:5000/v3 www_authenticate_uri = http://172.29.236.36:5000 project_domain_id = default user_domain_id = default project_name = service username = glance password = c96a36e76208ee26851c78670d34dcaff1c870 region_name = RegionOne service_token_roles_required = False service_token_roles = service service_type = image memcached_servers = 172.29.239.168:11211,172.29.239.242:11211, 172.29.236.80:11211 token_cache_time = 300 # if your memcached server is shared, use these settings to avoid cache poisoning memcache_security_strategy = ENCRYPT memcache_secret_key = 0b65b4b99155a6430e923fc9c24d9674 [oslo_policy] policy_file = policy.yaml policy_default_rule = default policy_dirs = policy.d [oslo_messaging_notifications] topics = notifications driver = messagingv2 transport_url = rabbit:// glance:9e7f205ef620983a542b4f915420e50d33f774@172.29.238.84:5671, glance:9e7f205ef620983a542b4f915420e50d33f774@172.29.238.174:5671, glance:9e7f205ef620983a542b4f915420e50d33f774@172.29.239.33:5671//glance?ssl=1&ssl_version=TLSv1_2&ssl_ca_file= [paste_deploy] flavor = keystone+cachemanagement [glance_store] default_backend = file [file] filesystem_store_datadir = /var/lib/glance/images/ [profiler] enabled = False [oslo_middleware] enable_proxy_headers_parsing = True [cors] allow_headers = origin,content-md5,x-image-meta-checksum,x-storage-token,accept-encoding,x-auth-token,x-identity-status,x-roles,x-service-catalog,x-user-id,x-tenant-id,x-openstack-request-id allow_methods = GET,POST,PUT,PATCH,DELETE allowed_origin = https://osa-portal.cs.binghamton.edu I'd be glad to run glance-api in the foreground with debug (in the container, or course), but it's not obvious from the .service file how to do that. I'd be glad to read source code, but a pointer or two would be handy. If NFS (or Hao's GPFS) just aren't supported anymore please tell me. Thanks. -Dave -- Dave Hall Binghamton University kdhall(a)binghamton.edu

2 2

[all] Dynamic Zuul results table in Gerrit 3
by Radosław Piliszek 04 Aug '22

04 Aug '22

Hello Fellow OpenStack and OpenDev Folks! TL;DR click on [3] and enjoy. I am starting this thread to not hijack the discussion happening on [1]. First of all, I would like to thank gibi (Balazs Gibizer) for hacking a way to get the place to render the table in the first place (pun intended). I have been a long-time-now user of [2]. I have improved and customised it for myself but never really got to share back the changes I made. The new Gerrit obviously broke the whole script so it was of no use to share at that particular state. However, inspired by gibi's work, I decided to finally sit down and fix it to work with Gerrit 3 and here it comes: [3]. Works well on Chrome with Tampermonkey. Not tested others. I hope you will enjoy this little helper (I do). I know the script looks super fugly but it generally boils down to a mix of styles of 3 people and Gerrit having funky UI rendering. Finally, I'd also like to thank hrw (Marcin Juszkiewicz) for linking me to the original Michel's script in 2019. [1] http://lists.openstack.org/pipermail/openstack-discuss/2020-November/019051… [2] https://opendev.org/x/coats/src/commit/444c95738677593dcfed0cfd9667d4c4f0d5… [3] https://gist.github.com/yoctozepto/7ea1271c299d143388b7c1b1802ee75e Kind regards, -yoctozepto

5 7

[Glance] Weekly Meeting Cancelled
by Pranali Deore 04 Aug '22

04 Aug '22

Hello, Since most of the team members will not be around today, so cancelling today's glance weekly meeting. Thanks & Regards, Pranali

1 0

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

04 Aug '22

Hello Everyone, Below is the agenda for Today TC meeting schedule at 1500 UTC. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting == Agenda for Today's TC 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 * 2023.1 cycle Technical Election planning * RBAC feedback in ops meetup ** https://etherpad.opendev.org/p/rbac-zed-ptg#L171 ** https://review.opendev.org/c/openstack/governance/+/847418 * Open Reviews ** https://review.opendev.org/q/projects:openstack/governance+is:open -gmann

1 0

resize or migrate problem
by fereshteh loghmani 03 Aug '22

03 Aug '22

hello I use OpenStack and I create some VMs in different compute in one region. when I resize the VM. if the compute doesn't have enough space, automatically the vm will be migrated to another compute. but my problem is here that when it migrated, the _base file doesn't migrate and remains in the first compute that it doesn't have enough space. because of this, the VM appears with an error status in OpenStack. if I move the _base from first compute to final compute and reboot the server this problem has been solved. so i need to not transfer _base manually and if it migrated to another compute the disk and _base transfer with each other. could you please help me to solve this problem? thanks in advance

2 3

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

03 Aug '22

This is a bug report from 07-27-2022 to 08-03-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Low - https://bugs.launchpad.net/cinder/+bug/1983237 "Cannot retype volume of lvm to volume of fujitsu." Unassigned. - https://bugs.launchpad.net/cinder/+bug/1983287 "Infinidat Cinder driver fails to backup attached volume." 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

[security-sig] Any interest in getting together at the PTG?
by Jeremy Stanley 03 Aug '22

03 Aug '22

I was going to bring this up during the monthly meeting, but since I'll be unavailable the next best solution is to raise it here... Are any of the Security SIG participants planning or at least hoping to be in Columbus for the PTG this October? And if so, is there any interest in carving out some spacetime in the schedule for security discussions? We still have another week to decide, but I'm happy to put in a request for us if anyone wants that. -- Jeremy Stanley

2 1

Reminder! PTG October 2022 Team Signup Deadline
by Kendall Nelson 03 Aug '22

03 Aug '22

Hello Everyone, Don't forget to sign your team up for the next Project Teams Gathering (PTG), which will be held in Columbus, OH from Monday, October 17 to Thursday, October 20th, 2022! If you haven't already done so and your team is interested in participating, please complete the survey[1] by August 12th, 2022 at 7:00 UTC. Then make sure to register[2] for the PTG before prices go up on August 15th! Also, please book in the official hotel block for a discounted rate[3]. Booking in the PTG hotel block helps us keep costs low for all attendees, so please encourage your teams to book here. Thanks! -Kendall (diablo_rojo) [1] Team Survey: https://openinfrafoundation.formstack.com/forms/oct2022_ptg_team_signup [2] PTG Registration: https://openinfra-ptg.eventbrite.com [3] Hotel Block: https://www.hyatt.com/en-US/group-booking/CMHRC/G-L0RT

1 0

[kolla][ops] Anyone using the collectd and/or telegraf?
by Radosław Piliszek 02 Aug '22

02 Aug '22

Hi Kolla-flavoured OpenStackers, Any of you using the collectd and/or telegraf with Kolla Ansible? The core team is looking to deprecate their support as it's not tested and collectd is now gone from Ubuntu Jammy. Please reply to this mail. Cheers, Radek -yoctozepto

2 2

[ceilometer][gnocchi][tacker] Internal Server Error in devstack for Zuul gate job
by ueha.ayumu＠fujitsu.com 02 Aug '22

02 Aug '22

Hi telemetry team, I’m Ueha from Tacker team, The Zuul gate job of Tacker failed with the following error. Do you know the solution? The gate job has failed, so we would appreciate it if you could deal it with high priority. Thanks! for reference, the same error occurring in the ceilometer patch. (https://review.opendev.org/c/openstack/ceilometer/+/851338 ‘s telemetry-dsvm-integration-centos-9s job) ------------------ ++ /opt/stack/ceilometer/devstack/plugin.sh:start_ceilometer:322 : /usr/local/bin/ceilometer-upgrade 2022-07-29 05:20:42.125 61523 DEBUG ceilometer.cmd.storage [-] Upgrading Gnocchi resource types upgrade /opt/stack/ceilometer/ceilometer/cmd/storage.py:42 2022-07-29 05:20:42.228 61523 CRITICAL ceilometer [-] Unhandled error: gnocchiclient.exceptions.ClientException: Internal Server Error (HTTP 500) 2022-07-29 05:20:42.228 61523 ERROR ceilometer Traceback (most recent call last): 2022-07-29 05:20:42.228 61523 ERROR ceilometer File "/usr/local/bin/ceilometer-upgrade", line 10, in <module> 2022-07-29 05:20:42.228 61523 ERROR ceilometer sys.exit(upgrade()) 2022-07-29 05:20:42.228 61523 ERROR ceilometer File "/opt/stack/ceilometer/ceilometer/cmd/storage.py", line 49, in upgrade 2022-07-29 05:20:42.228 61523 ERROR ceilometer tenacity.Retrying( ......... omit ......... 2022-07-29 05:20:42.228 61523 ERROR ceilometer File "/usr/local/lib/python3.8/dist-packages/gnocchiclient/client.py", line 52, in request 2022-07-29 05:20:42.228 61523 ERROR ceilometer raise exceptions.from_response(resp, method) 2022-07-29 05:20:42.228 61523 ERROR ceilometer gnocchiclient.exceptions.ClientException: Internal Server Error (HTTP 500) 2022-07-29 05:20:42.228 61523 ERROR ceilometer ------------------ Full log: https://zuul.opendev.org/t/openstack/build/71262e66ecf34827a8a3435657aa9b3f Best Regards, Ueha

4 4

[horizon][security-sig][tc] XStatic and JS dependencies
by Jeremy Stanley 02 Aug '22

02 Aug '22

We discussed this at the PTG, and sending out a recap has been on my to do list for a few months. Sorry about the delay! The tl;dr here is that OpenStack is effectively serving as the upstream distributor for (often vulnerable versions of) JavaScript software we didn't make, and downstream consumers like GNU/Linux distributions are then directly repackaging our copies of these things, and assuming we've taken care of any security vulnerabilities for them. In the early days, we needed a way to make it possible for Horizon to consume JavaScript libraries installed on systems, typically supplied by Linux distros via system level package management. XStatic was and still is a good framework for this, providing a means of bundling up metadata which can be adjusted in deployments to tie in local copies of JS libs so that Horizon can find them, and also allowing us to conveniently use the same sorts of mappings for upstream testing as well. The original idea was that we were shipping XStatic metadata packages, and distributions would take care of supplying the actual JS bits since that's not our specialty as a community. To make our own testing easier, we embedded copies of the actual JS within our XStatic packages, which is where all of this started going horribly wrong. The rationale at the time was that distro package maintainers would know to devendor (unbundle and replace) the JS inside our XStatic packages, substituting standard ones from their distribution. What has happened instead, likely due to a confluence of convenience and lack of clear communication on our part, is that the distros took the entirety of these XStatic packages and redistributed them, JS and all. Why is that bad? Well, our approach to Python dependencies is that we freeze the versions we use at the time of our coordinated release, on the assumption that distros backport any relevant security fixes for them. That's generally okay because we're not shipping those dependencies ourselves, someone else does and takes care of fixing and communicating vulnerabilities in them. For many of the XStatic packages Horizon relies on, however, distros are treating us as the upstream supplier of that software, including the JS bundled inside it. We don't (and really can't reliably) track security vulnerabilities in our dependencies, and JS is no exception in this regard. Unfortunately, when it comes to the outdated versions of JS libs we're redistributing inside those packages, many distros assume we are doing exactly that. Worse, it's not just the Linux distros, but even our own deployment projects following the same pattern. How can we address this? The first and fastest thing we should do is to start clearly communicating that we make no effort to track or fix vulnerabilities for JS inside our XStatic packages. Readme files in all of them should get a big disclaimer added, as visible as possible, that the included "convenience" copies of JS libs in them are not for production use and should be considered insecure, to be replaced at deployment time with actual upstream copies instead (this will be noticed not just when browsing our source code, but for any subsequent releases on PyPI too). Also update any places in our documentation where XStatic packages are mentioned to point this situation out. Ideally, we should reach out to distros and deployment projects we know are installing our copies of the embedded JS libs to make sure they're aware of this problem too. In the long term, we really need to gut the JS content from the source trees of our XStatic packages and make our test jobs use something like NPM or Yarn to fetch the relevant versions at deployment time, installing them into the expected locations pointed to by the XStatic metadata. This will make it more obvious that we're not taking responsibility for the security of those libraries, since we're no longer directly supplying them. I've only got the loosest understanding of how XStatic integration works, and not much familiarity with Horizon or its testing, so am relying on Horizon's contributors to weigh in on whether this course of action is sensible and, more importantly, achievable. -- Jeremy Stanley

1 1

[TripleO], Undercloud deployment is failing with with the NTP error
by Veronika Fisarova 02 Aug '22

02 Aug '22

Good day everyone, I was trying to deploy TripleO via tripleo-quickstart following this guide <https://docs.openstack.org/tripleo-quickstart/latest/getting-started.html#>. Working environment has satisfactory requirements following specifications in the guide. Python 3.6.8. is installed. The following deployment script was used: bash quickstart.sh --tags all -R wallaby -X --teardown all -v $VIRTHOST and the deployment is failing with the following error: 2022-08-02 13:05:13,693 p=21797 u=root n=ansible | 2022-08-02 13:05:13.692871 | 008acbda-7e58-575b-6e97-00000000078a | TASK | Ensure system is NTP time synced 2022-08-02 13:10:04,147 p=21797 u=root n=ansible | 2022-08-02 13:10:04.146932 | 008acbda-7e58-575b-6e97-00000000078a | FATAL | Ensure system is NTP time synced | undercloud | error={"changed": true, "cmd": ["chronyc", "waitsync", "30"], "delta": "0:04:50.254002", "end": "2022-08-02 13:10:04.121815", "msg": "non-zero return code", "rc": 1, "start": "2022-08-02 13:05:13.867813", "stderr": "", "stderr_lines": [], "stdout": "try: 1, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 2, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 3, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 4, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 5, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 6, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 7, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 8, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 9, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 10, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 11, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 12, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 13, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 14, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 15, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 16, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 17, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 18, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 19, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 20, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 21, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 22, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 23, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 24, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 25, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 26, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 27, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 28, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 29, refid: 00000000, correction: 0.000000000, skew: 0.000\ntry: 30, refid: 00000000, correction: 0.000000000, skew: 0.000", "stdout_lines": ["try: 1, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 2, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 3, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 4, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 5, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 6, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 7, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 8, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 9, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 10, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 11, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 12, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 13, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 14, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 15, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 16, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 17, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 18, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 19, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 20, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 21, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 22, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 23, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 24, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 25, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 26, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 27, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 28, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 29, refid: 00000000, correction: 0.000000000, skew: 0.000", "try: 30, refid: 00000000, correction: 0.000000000, skew: 0.000"]} 2022-08-02 13:10:04,178 p=21797 u=root n=ansible | PLAY RECAP ********************************************************************* 2022-08-02 13:10:04,178 p=21797 u=root n=ansible | localhost : ok=1 changed=0 unreachable=0 failed=0 skipped=2 rescued=0 ignored=0 2022-08-02 13:10:04,179 p=21797 u=root n=ansible | undercloud : ok=209 changed=110 unreachable=0 failed=1 skipped=50 rescued=0 ignored=2 For more information, please see the copy of the partially deployed undercloud here <https://paste.opendev.org/show/bxKvk87Y8ZH1RdboQaa3/> and here <https://paste.opendev.org/show/banD6k2R1gReYvBjN8bx/>. As far as I know, I can SSH to the deployed undercloud, but I cannot ensure if the undercloud is working properly and how many functions are missing. If you would need any additional information, please email me or use the IRC nick: deydra Any help or suggestions appreciated. -- *Veronika Fisarova* Openstack Validation Framework - Intern Red Hat <http://www.redhat.com>

1 0

[security-sig] Cancelling our August meeting
by Jeremy Stanley 02 Aug '22

02 Aug '22

Apologies for the late notice, but I have travel for an appointment conflicting with our meeting and will be unable to chair it this month. If someone else wants to run the meeting please feel free, though we don't have any pressing agenda items so it's probably fine to skip. I'm also open to holding the meeting next week instead, if anybody is interested in rescheduling. Barring any ad hoc meetings in the interim, our next scheduled meeting is 15:00 UTC on Thursday, September 1. In the meantime, Security SIG folks can be found in the #openstack-security channel on OFTC or by prepending subjects to this ML with [security-sig] of course! -- Jeremy Stanley

1 0

Horizon dashboard query
by KK CHN 02 Aug '22

02 Aug '22

Hi everyone! I need a guide or advice or anything. I am administering a private cloud in openstack. As I am using the Horizon dashboard for the VM provisioning and administering activities. But the users are sending requests in mail and creating the VMs for them. can we make workflow automation for the request and approval and provisioning automatically in the Horizon dashboard on approval? Has anyone already done /have idea on these kinds of solutions for your openstack cloud ??. Is there some kind of documentation that could help me?. Any guidance much appreciated, where to start, what to refer and which tool/programming language best if I need to code from scratch. thanks in advance. Krish

5 6

[neutron] CI meeting agenda for 2.08.2022
by Slawek Kaplonski 02 Aug '22

02 Aug '22

Hi, It's just a reminder that today at 1500 UTC we will have our CI meeting. It will be on video this time [1]. Agenda is on etherpad [2]. [1] https://meetpad.opendev.org/neutron-ci-meetings [2] https://etherpad.opendev.org/p/neutron-ci-meetings -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0