February 2022 - openstack-discuss

[ironic][election][ptl] PTL Candidacy for Zed Cycle
by Iury Gregory 15 Feb '22

15 Feb '22

Hello, Ironicers and stackers! I would like to submit my candidacy to continue serving as Ironic PTL for the Zed cycle. In the Yoga cycle, we are adding features to facilitate the cloud operator's life (e.g., Ironic now can calculate the default value for any enabled interface based on the `enabled_hardware_type`, verify steps). We fixed bugs related to SW Raid, virtual media deployments, and many others! Let's continue working together so we can take over the world! =) Best regards, Iury Gregory Melo Ferreira IRC: iurygregory -- *Att[]'sIury Gregory Melo Ferreira * *MSc in Computer Science at UFCG* *Part of the ironic-core and puppet-manager-core team in OpenStack* *Software Engineer at Red Hat Czech* *Social*: https://www.linkedin.com/in/iurygregory *E-mail: iurygregory(a)gmail.com <iurygregory(a)gmail.com>*

1 0

[elections][ptl][masakari]
by Sam Su (苏正伟) 15 Feb '22

15 Feb '22

Hi all, I write to submit my candidacy for the Masakari PTL position during the Z cycle. I took over as Masakari PTL during the Yoga cycle, and would like to serve the community for another cycle. Right now the biggest challenge of the Masakari project is lack of activity. We have been using Masakari in our cloud environment for years, so I want to continue to make some little improvement as feedback. Best regards for you. -suzhengwei

1 0

[election][Sahara]PTL candidacy for Z
by Juntingqiu Qiujunting (邱军婷) 15 Feb '22

15 Feb '22

Hi all: I write to submit my candidacy for the Sahara PTL position during the Z cycle.I have been PTL for the Yoga cycle, and I would like to serve the community for another cycle. In yoga cycle, we have discuss about the plugins are CDH, MapR, Storm, Spark and Vanilla will be removed from Sahara. I will continue this work on Z cycle. And assist the community to resolve some inappropriate issues in Yoga about Sahara project. At present, the Sahara project is not very active, and welcome my dears to actively participate in the construction of the Sahara project in Z cycle. Finally, expect the Sahara project to develop healthily and stably. Best regards for you. Fossen Qiu (fossenqiu) --------------------------------- Fossen Qiu | 邱军婷 CBRD | 云计算与大数据研发部 T: 18249256272 E: qiujunting(a)inspur.com<mailto:qiujunting@inspur.com> 浪潮云海

1 0

[election][puppet] PTL Candidacy for the "Z" release
by Takashi Kajinami 15 Feb '22

15 Feb '22

Hello, I'd like to announce my candidacy for the PTL role in Puppet OpenStack, for the Z release cycle. I've been involved in the project for a few years. I joined the core reviewers of the project in 2020. My contribution started with adding a few parameters but nowdays I'm covering literally all modules to keep these modules consistent with the latest service implementation, as well as helping release management. I'll list up some important items for the upcoming Z-release, which I'd like to prioritize. - Keep our implementation up to date and clean up old items to keep codes as simple as possible. - Extend support for Secure RBAC. We are adding partial support to enforce Secure RBAC in Keystone during Yoga. - Stabilize support for CentOS 9 Stream, which we are adding for Yoga. - Add support for the new Ubuntu LTS. - Improve scenario/component coverage by CI. Finally, as we are currently a small team, we always welcome new contributors, reviewers or whoever interested in helping the project ! Thank you for your consideration. Thank you, Takashi

1 0

[election][storlets] PTL Candidacy for the "Z" release
by Takashi Kajinami 15 Feb '22

15 Feb '22

Hi All, I'd like to announce my candidacy for PTL of Storlets for the z release cycle, continuing the role from past several cycles. The biggest change we're expecting for this cycle is removal of Python 2 support, following the same in Swift, which was recently announced[1]. We don't expect any challenges at this moment as Storlets has been fully complatble with Python 3 for several cycles, but the remaining work to clean up items left to keep Python 2 support (Python 2 jobs, for example) is our priority. [1] http://lists.openstack.org/pipermail/openstack-discuss/2022-January/026925.… Thank you for your consideration. Thank you, Takashi

1 0

[all][tc] Relmgt team position on release cadence
by Thierry Carrez 14 Feb '22

14 Feb '22

Hi everyone, The (long) document below reflects the current position of the release management team on a popular question: should the OpenStack release cadence be changed? Please note that we only address the release management / stable branch management facet of the problem. There are other dimensions to take into account (governance, feature deprecation, supported distros...) to get a complete view of the debate. Introduction ------------ The subject of how often OpenStack should be released has been regularly debated in the OpenStack community. OpenStack started with a 3-month release cycle, then switched to 6-month release cycle starting with Diablo. It is often thought of a release management decision, but it is actually a much larger topic: a release cadence is a trade-off between pressure to release more often and pressure to release less often, coming in from a lot of different stakeholders. In OpenStack, it is ultimately a Technical Committee decision. But that decision is informed by the position of a number of stakeholders. This document gives historical context and describes the current release management team position. The current trade-off --------------------- The main pressure to release more often is to make features available to users faster. Developers get a faster feedback loop, hardware vendors ensure software is compatible with their latest products, and users get exciting new features. "Release early, release often" is a best practice in our industry -- we should generally aim at releasing as often as possible. But that is counterbalanced by pressure to release less often. From a development perspective, each release cycle comes with some process overhead. On the integrators side, a new release means packaging and validation work. On the users side, it means pressure to upgrade. To justify that cost, there needs to be enough user-visible benefit (like new features) in a given release. For the last 10 years for OpenStack, that balance has been around six months. Six months let us accumulate enough new development that it was worth upgrading to / integrating the new version, while giving enough time to actually do the work. It also aligned well with Foundation events cadence, allowing to synchronize in-person developer meetings date with start of cycles. What changed ------------ The major recent change affecting this trade-off is that the pace of new development in OpenStack slowed down. The rhythm of changes was divided by 3 between 2015 and 2021, reflecting that OpenStack is now a mature and stable solution, where accessing the latest features is no longer a major driver. That reduces some of the pressure for releasing more often. At the same time, we have more users every day, with larger and larger deployments, and keeping those clusters constantly up to date is an operational challenge. That increases the pressure to release less often. In essence, OpenStack is becoming much more like a LTS distribution than a web browser -- something users like moving slow. Over the past years, project teams also increasingly decoupled individual components from the "coordinated release". More and more components opted for an independent or intermediary-released model, where they can put out releases in the middle of a cycle, making new features available to their users. This increasingly opens up the possibility of a longer "coordinated release" which would still allow development teams to follow "release early, release often" best practices. All that recent evolution means it is (again) time to reconsider if the 6-month cadence is what serves our community best, and in particular if a longer release cadence would not suit us better. The release management team position on the debate -------------------------------------------------- While releasing less often would definitely reduce the load on the release management team, most of the team work being automated, we do not think it should be a major factor in motivating the decision. We should not adjust the cadence too often though, as there is a one-time cost in switching our processes. In terms of impact, we expect that a switch to a longer cycle will encourage more project teams to adopt a "with-intermediary" release model (rather than the traditional "with-rc" single release per cycle), which may lead to abandoning the latter, hence simplifying our processes. Longer cycles might also discourage people to commit to PTL or release liaison work. We'd probably need to manage expectations there, and encourage more frequent switches (or create alternate models). If the decision is made to switch to a longer cycle, the release management team recommends to switch to one year directly. That would avoid changing it again anytime soon, and synchronizing on a calendar year is much simpler to follow and communicate. We also recommend announcing the change well in advance. We currently have an opportunity of making the switch when we reach the end of the release naming alphabet, which would also greatly simplify the communications around the change. Finally, it is worth mentioning the impact on the stable branch work. Releasing less often would likely impact the number of stable branches that we keep on maintaining, so that we do not go too much in the past (and hit unmaintained distributions or long-gone dependencies). We currently maintain releases for 18 months before they switch to extended maintenance, which results in between 3 and 4 releases being maintained at the same time. We'd recommend switching to maintaining one-year releases for 24 months, which would result in between 2 and 3 releases being maintained at the same time. Such a change would lead to longer maintenance for our users while reducing backporting work for our developers. -- Thierry Carrez (ttx) On behalf of the OpenStack Release Management team

15 45

[election][tc] Candidacy for TC for Z
by Nikolla, Kristi 14 Feb '22

14 Feb '22

Hi all, I am announcing my candidacy for a position on the OpenStack Technical Committee. I'm a software engineer at the Mass Open Cloud[0], and the New England Research Cloud[1], two initiatives from major universities in the Boston area to create and operate public and open clouds that can federated and replicated. I've been involved with OpenStack for the past 7 years as a user, operator, and developer. This is not my first time running, I have previously served on the Technical Committee[2] and as Keystone PTL for 1 year during the Victoria and Wallaby cycles[3][4]. I am passionate about open source and governance and keeping the community healthy. My focus will be in facilitating the discussions that need to happen, whether they are internal to a team, between project teams, or between OpenStack and other projects. Please allow me once again the honor of representing you, and the opportunity to continue contributing to the community that I owe so much to and want to see flourish. I look forward to hopefully seeing you all very soon! Thank you for your time and consideration, Kristi Nikolla (he/him) [0]. https://massopen.cloud [1]. https://nerc.mghpcc.org [2]. https://opendev.org/openstack/election/raw/branch/master/candidates/victori… [3]. https://opendev.org/openstack/election/raw/branch/master/candidates/victori… [4]. https://opendev.org/openstack/election/raw/branch/master/candidates/wallaby…

1 0

[puppet][tc] Propose changing the release model to cycle-with-rc
by Takashi Kajinami 14 Feb '22

14 Feb '22

Hello, I already discussed this with a few cores last year but I'm raising this topic in ML to make an official decision. Currently Puppet OpenStack is following cycle-with-intermediary and creates a release every milestone. However our code is tightly related to the actual service implementations and having only puppet releases is not very useful. Considering the above point, and effort required to cut off releases per milestone, I'll propose changing our release model to cycle-with-rc , and creating a single release. Because we already created milestone releases for Yoga, I'm thinking of applying the change from next cycle(Z). Please let me know if you have any concerns. Thank you, Takashi

5 5

[blazar][election][ptl] PTL candidacy for Z
by Pierre Riteau 14 Feb '22

14 Feb '22

Hi, I would like to self-nominate for the role of PTL of Blazar for the Z release cycle. I have been PTL since the Stein cycle and I am willing to continue in this role. We have experienced an uptick in contributions during the Yoga cycle, merging some long-awaited features such as a calendar view in the dashboard or initial support for preemptible instances. I would like to keep this momentum going, improving Blazar for its existing users and plugging gaps preventing it from getting adopted by more deployments. Thank you for your support, Pierre Riteau (priteau)

1 0

[election][Designate][ptl] My candidacy for the "Z" release
by Michael Johnson 14 Feb '22

14 Feb '22

Hello OpenStack community, I would like to announce my candidacy for PTL of Designate for the "Z" cycle. I would like to continue to support the Designate team for the "Z" release. We have made good progress improving the Designate tempest tests and documentation, but we have more work to do. The team has also been focusing on cleaning up some of the accumulated technical debt, which I expect will continue into the "Z" cycle. Thank you for your support and your consideration for "Z", Michael Johnson (johnsom)

1 0

Outreachy OpenStack Coordinator change
by Mahati Chamarthy 14 Feb '22

14 Feb '22

Hello all, There has been a change in coordination responsibilities for Outreachy OpenStack <https://www.outreachy.org>. Samuel has decided to step down as a coordinator. I'd like to thank Samuel for his time and efforts to Outreachy. He has helped onboard many new contributors onto the Outreachy Openstack internship program. Thank you Samuel and hope our paths cross again! Good luck. I'd also like to welcome Dmitry Tantsur who kindly offered to coordinate along with me for Outreachy Openstack. Dmitry has been a long time OpenStack contributor and a core committer for the Ironic project. He has already been an Outreachy mentor for multiple rounds. For any queries regarding Outreachy, he can be reached at divius.inside(a)gmail.com (or) on IRC: dtantsur Welcome aboard Dmitry, thank you for stepping up! Best, Mahati

1 0

[neutron] lldpd Errors
by Ammad Syed 14 Feb '22

14 Feb '22

Hello, I am using ovn 21.09 with neutron 19.0. I am continuously seeing below lldpd errors in my journalctl and syslog of compute nodes. Is there anything to worry about? Feb 13 21:17:29 computehost02 lldpd[5025]: MSAP has changed for port tap30b18e08-00, sending a shutdown LLDPDU Feb 13 21:17:29 computehost02 lldpd[5025]: unable to send packet on real device for tap30b18e08-00: No such device or address Feb 13 21:17:29 computehost02 lldpd[5025]: unable to send packet on real device for tap48d8e15e-ee: No such device or address Feb 13 21:17:59 computehost02 lldpd[5025]: unable to send packet on real device for tap48d8e15e-ee: No such device or address Feb 13 21:17:59 computehost02 lldpd[5025]: MSAP has changed for port tap30b18e08-00, sending a shutdown LLDPDU Ammad

3 2

[election][Octavia][ptl] PTL candidacy for Z
by Gregory Thiemonge 14 Feb '22

14 Feb '22

Hi, I would like to nominate myself for Octavia PTL for the Z release cycle. I am the current PTL and I would like to continue to contribute to this role. For the Z release, my plan for Octavia is to enable persistence in taskflow in the amphorav2 driver, to start working on HTTP/3 support, to fix old known issues (handling multiple subnets on the VIP port, fixing multiple subnets issue on member ports). Thanks for your consideration, Gregory

1 0

Re: [kolla-ansible][nova] volume creation time
by Eugen Block 14 Feb '22

14 Feb '22

I haven't used iscsi as a backend yet, but for HDDs the speed looks relatable, on a system with HDD ceph backend the volume creation of a volume (image is 2 GB) takes about 40 seconds, as you yee the download is quite slow, the conversion is a little faster: Image download 541.00 MB at 28.14 MB/s Converted 2252.00 MB image at 172.08 MB/s With a factor of 10 (20 GB) I would probably end up with similar creation times. Just for comparison, this is almost the same image (also 2 GB) in a different ceph cluster where I mounted the cinder conversion path from cephfs, SSD pool: Image download 555.12 MB at 41.34 MB/s Converted 2252.00 MB image at 769.17 MB/s This volume was created within 20 seconds. You might also want to tweak these options: block_device_allocate_retries = 300 block_device_allocate_retries_interval = 10 These are the defaults: block_device_allocate_retries = 60 block_device_allocate_retries_interval = 3 This would fit your error message: > Volume be0f28eb-1045-4687-8bdb-5a6d385be6fa did not finish being > created even after we waited 187 seconds or 61 attempts. And its > status is downloading. It tried 60 times with a 3 second interval, apparently that's not enough. Can you see any bottlenecks in the network or disk utilization which would slow down the download? Zitat von Franck VEDEL <franck.vedel(a)univ-grenoble-alpes.fr>: > Hi Eugen, > thanks for your help > We have 3 servers (s1, s2 , s3) and an iscsi bay attached on s3. > Multinode: > [control] > s1 > s2 > > [compute] > s1 > s2 > s3 > > [storage] > s3 > > on s1: more /etc/kolla/globals.yml > ... > enable_cinder: "yes" > enable_cinder_backend_iscsi: "yes" > enable_cinder_backend_lvm: « yes" > enable_iscsid: « yes" > cinder_volume_group: "cinder-volumes » > ... > enable_glance_image_cache: "yes" > glance_cache_max_size: "21474836480" > glance_file_datadir_volume: « /images/« > ... > > on s3: /images is on the iscsi bay > mount |grep images > /dev/mapper/VG--IMAGES-LV--IMAGES on /images type xfs > (rw,relatime,seclabel,attr2,inode64,logbufs=8,logbsize=32k,sunit=1024,swidth=1024,noquota) > > lsblk > sdf > 8:80 0 500G 0 disk > └─mpathc > 253:3 0 500G 0 mpath > └─mpathc1 > 253:4 0 500G 0 part > └─VG--IMAGES-LV--IMAGES > 253:5 0 500G 0 lvm /images > > > ls -l /images: > drwxr-x---. 5 42415 42415 4096 6 févr. 18:40 image-cache > drwxr-x---. 2 42415 42415 4096 4 févr. 15:16 images > drwxr-x---. 2 42415 42415 6 22 nov. 12:03 staging > drwxr-x---. 2 42415 42415 6 22 nov. 12:03 tasks_work_dir > > ls -l /images/image-cache > total 71646760 > -rw-r-----. 1 42415 42415 360841216 2 déc. 11:52 > 3e3aada8-7610-4c55-b116-a12db68f8ea4 > -rw-r-----. 1 42415 42415 237436928 28 nov. 16:56 > 6419642b-fcbd-4e5d-9c77-46a48d2af93f > -rw-r-----. 1 42415 42415 10975379456 26 nov. 14:59 > 7490e914-8001-4d56-baea-fabf80f425e1 > -rw-r-----. 1 42415 42415 21474836480 22 nov. 16:46 > 7fc7f9a6-ab0e-45cf-9c29-7e59f6aa68a5 > -rw-r-----. 1 42415 42415 2694512640 15 déc. 18:07 > 890fd2e8-2fac-42c6-956b-6b10f2253a56 > -rw-r-----. 1 42415 42415 12048400384 1 déc. 17:04 > 9a235763-ff0c-40fd-9a8d-7cdca3d3e9ce > -rw-r-----. 1 42415 42415 5949227008 15 déc. 20:41 > 9cbba37b-1de1-482a-87f2-631d2143cd46 > -rw-r-----. 1 42415 42415 566994944 6 déc. 12:32 > b6e29dd9-a66d-4569-a222-6fc0bd9b1b11 > -rw-r-----. 1 42415 42415 578748416 2 déc. 11:24 > c40953ee-4b39-43a5-8f6c-b48a046c38e9 > -rw-r-----. 1 42415 42415 16300544 27 janv. 12:19 > c88630c7-a7c6-44ff-bfa0-e5af4b1720e3 > -rw-r-----. 1 42415 42415 12288 6 févr. 18:40 cache.db > -rw-r-----. 1 42415 42415 12324503552 1 déc. 07:50 > e0d4fddd-5aa7-4177-a1d6-e6b4c56f12e8 > -rw-r-----. 1 42415 42415 6139084800 22 nov. 15:05 > eda93204-9846-4216-a6e8-c29977fdcf2f > -rw-r-----. 1 42415 42415 0 22 nov. 12:03 image_cache_db_init > drwxr-x---. 2 42415 42415 6 27 janv. 12:19 incomplete > drwxr-x---. 2 42415 42415 6 22 nov. 12:03 invalid > drwxr-x---. 2 42415 42415 6 22 nov. 12:03 queue > > on s1 > openstack image list > +--------------------------------------+-----------------------------+--------+ > | ID | Name > | Status | > +--------------------------------------+-----------------------------+--------+ > ….. > | 7fc7f9a6-ab0e-45cf-9c29-7e59f6aa68a5 | rocky8.4 > | active | > …. > | 7490e914-8001-4d56-baea-fabf80f425e1 | win10_2104 > | active | > …. > +———————————————————+-----------------------------+————+ > > > openstack image show 7fc7f9a6-ab0e-45cf-9c29-7e59f6aa68a5 > disk_format | raw > > when I try to add an instance from this image (2G RAM, 40G HDD): > [Error : Build of instance baa06bef-9628-407f-8bae-500ef7bce065 > aborted: Volume be0f28eb-1045-4687-8bdb-5a6d385be6fa did not finish > being created even after we waited 187 seconds or 61 attempts. And > its status is downloading. > > it’s impossible. I need to add the volume from image first, and > after add instance from volume. > > Is it normal ? > > > Franck > >> Le 7 févr. 2022 à 10:55, Eugen Block <eblock(a)nde.ag> a écrit : >> >> Hi Franck, >> >> although it's a different topic than your original question I >> wanted to comment on the volume creation time (maybe a new thread >> would make sense). What is your storage back end? If it is ceph, >> are your images in raw format? Otherwise cinder has to download the >> image from glance (to /var/lib/cinder/conversion) and convert it, >> then upload it back to ceph. It's similar with nova, nova stores >> base images in /var/lib/nova/instances/_base to prevent the compute >> nodes from downloading it every time. This may save some time for >> the download, but the upload has to happen anyway. And if you don't >> use shared storage for nova (e.g. for live-migration) you may >> encounter that some compute nodes are quicker creating an instance >> because they only have to upload, others will first have to >> download, convert and then upload it. >> >> You would see the conversion in the logs of cinder: >> >> INFO cinder.image.image_utils >> [req-f2062570-4006-464b-a1f5-d0d5ac34670d >> d71f59600f1c40c394022738d4864915 31b9b4900a4d4bdaabaf263d0b4021be - >> - -] Converted 2252.00 MB image at 757.52 MB/s >> >> Hope this helps. >> >> Eugen >> >> >> Zitat von Franck VEDEL <franck.vedel(a)univ-grenoble-alpes.fr>: >> >>> Sunday morning: my openstack works…. OUF. >>> the "kolla-ansible -i multimode mariadb_recovery" command (which >>> is magic anyway) fixed the problem and then the mariadb and nova >>> containers started. >>> Once solved the problems between my serv3 and the iscsi bay, >>> restart the container glance, everything seems to work. >>> >>>> 4 minutes to create a 20GB empty volume seems too long to me. For >>>> an actual 20GB image, it's going to depend on the speed of the >>>> backing storage tech. >>> 4 minutes is for a volume from an image. I will see this problem >>> next summer , I will retry to change the MTU value. >>> >>> Thanks a lot, really >>> >>> >>> Franck >>> >>>> Le 5 févr. 2022 à 17:08, Laurent Dumont >>>> <laurentfdumont(a)gmail.com> a écrit : >>>> >>>> Any chance to revert back switches + server? That would indicate >>>> that MTU was the issue. >>>> Dont ping the iscsi bay, ping between the controllers in >>>> Openstack, they are the ones running mariadb/galera. >>>> Since the icmp packets are small, it might not trigger the MTU >>>> issues. Can you try something like "ping -s 8972 -M do -c 4 >>>> $mariadb_host_2" from $ mariadb_host_1? >>>> What is your network setup on the servers? Two ports in a bond? >>>> Did you change both physical interface MTU + bond interface itself? >>>> >>>> 4 minutes to create a 20GB empty volume seems too long to me. For >>>> an actual 20GB image, it's going to depend on the speed of the >>>> backing storage tech. >>>> >>>> On Sat, Feb 5, 2022 at 1:51 AM Franck VEDEL >>>> <franck.vedel(a)univ-grenoble-alpes.fr >>>> <mailto:franck.vedel@univ-grenoble-alpes.fr>> wrote: >>>> Thanks for your help. >>>> >>>> >>>>> What was the starting value for MTU? >>>> 1500 >>>>> What was the starting value changed to for MTU? >>>> 9000 >>>>> Can ping between all your controllers? >>>> yes, all container starts except nova-conductor, nova-scheduler, maraidb >>>> >>>> >>>>> Do you just have two controllers running mariadb? >>>> yes >>>>> How did you change MTU? >>>> >>>> On the 3 servers: >>>> nmcli connection modify team0-port1 802-3-ethernet.mtu 9000 >>>> nmcli connection modify team1-port2 802-3-ethernet.mtu 9000 >>>> nmcli connection modify type team0 team.runner lack ethernet.mtu 9000 >>>> nmcli con down team0 >>>> nmcli con down team1 >>>> >>>> >>>>> Was the change reverted at the network level as well (switches >>>>> need to be configured higher or at the same MTU value then the >>>>> servers) >>>> I didn’t change Mtu on network (switches) , but ping -s >>>> 10.0.5.117 (iscsi bay) was working from serv3. >>>> >>>> I changed the value of the mtu because the creation of the >>>> volumes takes a lot of time I find (4 minutes for 20G, which is >>>> too long for what I want to do, the patience of the students >>>> decreases with the years) >>>> >>>> Franck >>>> >>>>> Le 4 févr. 2022 à 23:12, Laurent Dumont >>>>> <laurentfdumont(a)gmail.com <mailto:laurentfdumont@gmail.com>> a >>>>> écrit : >>>>> >>>>> What was the starting value for MTU? >>>>> What was the starting value changed to for MTU? >>>>> Can ping between all your controllers? >>>>> Do you just have two controllers running mariadb? >>>>> How did you change MTU? >>>>> Was the change reverted at the network level as well (switches >>>>> need to be configured higher or at the same MTU value then the >>>>> servers) >>>>> 4567 seems to be the port for galera (clustering for mariadb) <> >>>>> On Fri, Feb 4, 2022 at 11:52 AM Franck VEDEL >>>>> <franck.vedel(a)univ-grenoble-alpes.fr >>>>> <mailto:franck.vedel@univ-grenoble-alpes.fr>> wrote: >>>>> Hello, >>>>> I am in an emergency situation, quite catastrophic situation >>>>> because I do not know what to do. >>>>> >>>>> I have an Openstack cluster with 3 servers (serv1, serv2, >>>>> serv3). He was doing so well… >>>>> >>>>> >>>>> A network admin came to me and told me to change an MTU on the >>>>> cards. I knew it shouldn't be done...I shouldn't have done it. >>>>> I did it. >>>>> Of course, it didn't work as expected. I went back to my >>>>> starting configuration and there I have a big problem with >>>>> mariadb which is set up on serv1 and serv2. >>>>> >>>>> Here are my errors: >>>>> >>>>> >>>>> 2022-02-04 17:40:36 0 [ERROR] WSREP: failed to open gcomm >>>>> backend connection: 110: failed to reach primary view: 110 >>>>> (Connection timed out) >>>>> at gcomm/src/pc.cpp:connect():160 >>>>> 2022-02-04 17:40:36 0 [ERROR] WSREP: >>>>> gcs/src/gcs_core.cpp:gcs_core_open():209: Failed to open backend >>>>> connection: -110 (Connection timed out) >>>>> 2022-02-04 17:40:36 0 [ERROR] WSREP: >>>>> gcs/src/gcs.cpp:gcs_open():1475: Failed to open channel >>>>> 'openstack' at 'gcomm://10.0.5.109:4567,10.0.5.110:4567': <> >>>>> -110 (Connection timed out) >>>>> 2022-02-04 17:40:36 0 [ERROR] WSREP: gcs connect failed: >>>>> Connection timed out >>>>> 2022-02-04 17:40:36 0 [ERROR] WSREP: >>>>> wsrep::connect(gcomm://10.0.5.109:4567,10.0.5.110:4567 <>) >>>>> failed: 7 >>>>> 2022-02-04 17:40:36 0 [ERROR] Aborting >>>>> >>>>> >>>>> >>>>> >>>>> I do not know what to do. My installation is done with >>>>> kolla-ansible, mariadb docker restarts every 30 seconds. >>>>> >>>>> Can the "kolla-ansible reconfigure mariadb" command be a solution? >>>>> Could the command "kolla-ansible mariadb recovery" be a solution? >>>>> >>>>> Thanks in advance if you can help me. >>>>> >>>>> >>>>> >>>>> Franck >>>>> >>>>> >>>> >> >> >> >>

2 2

nova rabbitmq strange bug
by Satish Patel 14 Feb '22

14 Feb '22

Folks, I am running wallaby and Today i had rabbitMQ issue and i rebuild RabbitMQ. but now my all compute node throwing following error. not sure what is going on up they are not trying to come up and keep crashing with following error 2022-02-10 00:52:27.843 3660531 ERROR oslo_service.service [req-6c3cdaa3-ecf9-4bef-9def-6b6a69dfd30b - - - - -] Error starting thread.: oslo_messaging.exceptions.MessagingTimeout: Timed out waiting for a reply to message ID 9510bd6c0d6a48e782ed7bc2887f32c8 2022-02-10 00:52:27.843 3660531 ERROR oslo_service.service Traceback (most recent call last): 2022-02-10 00:52:27.843 3660531 ERROR oslo_service.service File "/openstack/venvs/nova-23.1.1/lib/python3.8/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 433, in get 2022-02-10 00:52:27.843 3660531 ERROR oslo_service.service return self._queues[msg_id].get(block=True, timeout=timeout) 2022-02-10 00:52:27.843 3660531 ERROR oslo_service.service File "/openstack/venvs/nova-23.1.1/lib/python3.8/site-packages/eventlet/queue.py", line 322, in get 2022-02-10 00:52:27.843 3660531 ERROR oslo_service.service return waiter.wait() 2022-02-10 00:52:27.843 3660531 ERROR oslo_service.service File "/openstack/venvs/nova-23.1.1/lib/python3.8/site-packages/eventlet/queue.py", line 141, in wait 2022-02-10 00:52:27.843 3660531 ERROR oslo_service.service return get_hub().switch() 2022-02-10 00:52:27.843 3660531 ERROR oslo_service.service File "/openstack/venvs/nova-23.1.1/lib/python3.8/site-packages/eventlet/hubs/hub.py", line 313, in switch 2022-02-10 00:52:27.843 3660531 ERROR oslo_service.service return self.greenlet.switch() 2022-02-10 00:52:27.843 3660531 ERROR oslo_service.service _queue.Empty 2022-02-10 00:52:27.843 3660531 ERROR oslo_service.service 2022-02-10 00:52:27.843 3660531 ERROR oslo_service.service During handling of the above exception, another exception occurred: 2022-02-10 00:52:27.843 3660531 ERROR oslo_service.service 2022-02-10 00:52:27.843 3660531 ERROR oslo_service.service Traceback (most recent call last): 2022-02-10 00:52:27.843 3660531 ERROR oslo_service.service File "/openstack/venvs/nova-23.1.1/lib/python3.8/site-packages/oslo_service/service.py", line 807, in run_service 2022-02-10 00:52:27.843 3660531 ERROR oslo_service.service service.start() 2022-02-10 00:52:27.843 3660531 ERROR oslo_service.service File "/openstack/venvs/nova-23.1.1/lib/python3.8/site-packages/nova/service.py", line 159, in start 2022-02-10 00:52:27.843 3660531 ERROR oslo_service.service self.manager.init_host() 2022-02-10 00:52:27.843 3660531 ERROR oslo_service.service File "/openstack/venvs/nova-23.1.1/lib/python3.8/site-packages/nova/compute/manager.py", line 1413, in init_host 2022-02-10 00:52:27.843 3660531 ERROR oslo_service.service self.driver.init_host(host=self.host) 2022-02-10 00:52:27.843 3660531 ERROR oslo_service.service File "/openstack/venvs/nova-23.1.1/lib/python3.8/site-packages/nova/virt/libvirt/driver.py", line 792, in init_host 2022-02-10 00:52:27.843 3660531 ERROR oslo_service.service self._register_instance_machine_type() 2022-02-10 00:52:27.843 3660531 ERROR oslo_service.service File "/openstack/venvs/nova-23.1.1/lib/python3.8/site-packages/nova/virt/libvirt/driver.py", line 811, in _register_instance_machine_type 2022-02-10 00:52:27.843 3660531 ERROR oslo_service.service for instance in objects.InstanceList.get_by_host(context, hostname): 2022-02-10 00:52:27.843 3660531 ERROR oslo_service.service File "/openstack/venvs/nova-23.1.1/lib/python3.8/site-packages/oslo_versionedobjects/base.py", line 175, in wrapper 2022-02-10 00:52:27.843 3660531 ERROR oslo_service.service result = cls.indirection_api.object_class_action_versions( 2022-02-10 00:52:27.843 3660531 ERROR oslo_service.service File "/openstack/venvs/nova-23.1.1/lib/python3.8/site-packages/nova/conductor/rpcapi.py", line 240, in object_class_action_versions 2022-02-10 00:52:27.843 3660531 ERROR oslo_service.service return cctxt.call(context, 'object_class_action_versions', 2022-02-10 00:52:27.843 3660531 ERROR oslo_service.service File "/openstack/venvs/nova-23.1.1/lib/python3.8/site-packages/oslo_messaging/rpc/client.py", line 175, in call 2022-02-10 00:52:27.843 3660531 ERROR oslo_service.service self.transport._send(self.target, msg_ctxt, msg, 2022-02-10 00:52:27.843 3660531 ERROR oslo_service.service File "/openstack/venvs/nova-23.1.1/lib/python3.8/site-packages/oslo_messaging/transport.py", line 123, in _send 2022-02-10 00:52:27.843 3660531 ERROR oslo_service.service return self._driver.send(target, ctxt, message, 2022-02-10 00:52:27.843 3660531 ERROR oslo_service.service File "/openstack/venvs/nova-23.1.1/lib/python3.8/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 680, in send 2022-02-10 00:52:27.843 3660531 ERROR oslo_service.service return self._send(target, ctxt, message, wait_for_reply, timeout, 2022-02-10 00:52:27.843 3660531 ERROR oslo_service.service File "/openstack/venvs/nova-23.1.1/lib/python3.8/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 669, in _send 2022-02-10 00:52:27.843 3660531 ERROR oslo_service.service result = self._waiter.wait(msg_id, timeout, 2022-02-10 00:52:27.843 3660531 ERROR oslo_service.service File "/openstack/venvs/nova-23.1.1/lib/python3.8/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 559, in wait 2022-02-10 00:52:27.843 3660531 ERROR oslo_service.service message = self.waiters.get(msg_id, timeout=timeout) 2022-02-10 00:52:27.843 3660531 ERROR oslo_service.service File "/openstack/venvs/nova-23.1.1/lib/python3.8/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 435, in get 2022-02-10 00:52:27.843 3660531 ERROR oslo_service.service raise oslo_messaging.MessagingTimeout( 2022-02-10 00:52:27.843 3660531 ERROR oslo_service.service oslo_messaging.exceptions.MessagingTimeout: Timed out waiting for a reply to message ID 9510bd6c0d6a48e782ed7bc2887f32c8 2022-02-10 00:52:27.843 3660531 ERROR oslo_service.service

2 5

[largescale-sig] Next meeting: Feb 16th, 15utc
by Thierry Carrez 14 Feb '22

14 Feb '22

Hi everyone, The Large Scale SIG will be meeting this Wednesday in #openstack-operators on OFTC IRC, at 15UTC. You can doublecheck how that time translates locally at: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20220216T15 We'll look back at the new format for the Large Scale OpenStack show and discuss the next episode. Feel free to add other topics to the agenda: https://etherpad.openstack.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez

1 0

[neutron] Bug deputy report (week starting on 2022-02-07)
by Bernard Cafarelli 14 Feb '22

14 Feb '22

Hi neutrinos, I was bug deputy last week, here is the list of reported bugs A quiet week overall, no high importance bugs without assignee High * [fullstack] Test "test_east_west_traffic" randomly failing - https://bugs.launchpad.net/neutron/+bug/1960338 Mostly affecting Wallaby, https://review.opendev.org/c/openstack/neutron/+/828231 backports seem to have helped * "ovn_agent._run_process" ovs-appctl fails setting the service log configuration - https://bugs.launchpad.net/neutron/+bug/1960514 devstack deployment issue for DPDK environments, OVN_BUILD_MODULES=True, patch by ralonsoh https://review.opendev.org/c/openstack/devstack/+/828877 Medium * snat is used instead of dnat_and_snat when L3GW resides on chassis - https://bugs.launchpad.net/neutron/+bug/1960405 elvira is checking this bug * [OVN] OVN_BUILD_MODULES/OVN_BUILD_FROM_SOURCE differences - https://bugs.launchpad.net/neutron/+bug/1960397 An ask-for-opinion bug on these variables, are they both needed? Low * Logging service writing errors in the logs when RPC required - https://bugs.launchpad.net/neutron/+bug/1960533 Service itself works fine, but it is better not to generate this kind of error message -- Bernard Cafarelli

1 0

[election][Cyborg]PTL candidacy for Z
by Brin Zhang(张百林) 14 Feb '22

14 Feb '22

Hi all, I write to submit my candidacy for the Cyborg PTL position during the Z cycle. I have been PTL for the Yoga cycle, and I would like to serve the community for another cycle. In yoga cycle, we have competed get device profile by name, clearly resource provide, updated devices, deployables' API docs, etc.. But we also have some new feature need to trace, e.g. vGPU support (splite a new spec wit usage of new trait of OWNER_NOVA, need to be down with Nova team), add xilinx FPGA driver, and add the UT to cover many scenarios. Another thing is to attract more contributors to the Cyborg contribution, to increase the activity of the Cyborg project, although I have started to do so. In summary, I want to keep the stability and diversity of accelerator devices in OpenStack. Best regards for you. Brin Zhang (brinzhang)

1 0

OpenStack Trove experimental datastores
by Ришат Азизов 12 Feb '22

12 Feb '22

Hello! Why were the experimental datastores removed in the Trove OpenStack Victoria release? https://review.opendev.org/c/openstack/trove/+/728419 <https://review.opendev.org/c/openstack/trove/+/728419> Thanks!

3 2

[elections][ptl][keystone] PTL Candidacy for Keystone
by Douglas Mendizabal 11 Feb '22

11 Feb '22

Hi All, I would like to announce my candidacy for Keystone PTL. Keystone is an important project for OpenStack and I would like to help ensure things keep moving forward. I'm very much interested in the Secure RBAC effort and I want to make sure that the Keystone project has everything it needs to support the greater community pursue the completion of this goal. Thanks, Douglas Mendizábal OFTC: dmendiza[m]

1 0

[elections][ptl][barbican]
by Douglas Mendizabal 11 Feb '22

11 Feb '22

Hi All, I would like to continue to serve as Barbican PTL for the Z cycle. Barbican is slowly moving forward, and I would like to see improvements continue for the next cycle. Thanks, Douglas Mendizábal OFTC: dmendiza[m]

1 0

[all][tc] What's happening in Technical Committee: summary 11th Feb, 21: Reading: 5 min
by Ghanshyam Mann 11 Feb '22

11 Feb '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week meeting yesterday. Most of the meeting discussions are summarized below (Completed or in-progress activities section). Meeting full logs are available @https://meetings.opendev.org/meetings/tc/2022/tc.2022-02-10-15.00.log.html * Next week's meeting is on 17th Feb Thursday 15:00 UTC, feel free add the topic on the agenda[1] by 16th Feb. 2. What we completed this week: ========================= * Reverted the neutron-fwaas deprecation and it is maintained under neutron stadium now[2]. * Removed security-specs from security sig[3]. 3. Activities In progress: ================== TC Tracker for Yoga cycle ------------------------------ * This etherpad includes the Yoga cycle targets/working items for TC[4]. 2 out of 9 items are completed. Open Reviews ----------------- * Four open reviews for ongoing activities[5]. Dropping tags framework ------------------------------ yoctozepto has updated the part1 of dropping the tag framework[6] which is ready for review. He will continue working on part2 which is to update the release scripts and openstack navigation sites to remove the tag usage. Z release cycle name ------------------------- TC selection on proposed names is closed and selected names are under trademark checks by foundation, follow the ML[7] for updates. Z release cycle Technical Election --------------------------------------- Nomination for PTL and TC election are in-progress and will be open until 15th Feb[8]. I would like to encourage project leaders to stand for PTL and community members to run for TC. Please add your nomination before deadline[9]. TC position on release cadence ------------------------------------- We had separate call to discuss the next step and TC position on release cadence[10] and as discussed Dan has proposed the new release model as TC resolution[11]. Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[12]. Project updates ------------------- * Retire js-openstack-lib (waiting on Adjutant to have new PTL/maintainer) [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/+/828078 [3] https://review.opendev.org/c/openstack/governance/+/828018 [4] https://etherpad.opendev.org/p/tc-yoga-tracker [5] https://review.opendev.org/q/projects:openstack/governance+status:open [6] https://review.opendev.org/c/openstack/governance/+/822900 [7] http://lists.openstack.org/pipermail/openstack-discuss/2022-January/026810.… [8] http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027117… [9] https://governance.openstack.org/election/ [10] https://meetpad.opendev.org/OpenStackReleasecadence [11] https://review.opendev.org/c/openstack/governance/+/828777 [12] https://etherpad.opendev.org/p/zuul-config-error-openstack [13] https://review.opendev.org/c/openstack/governance/+/798540 [14] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [15] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[Manila] Yoga Collab reviews
by Fernando Ferraz 11 Feb '22

11 Feb '22

Hi Team, Would like to invite you to our collaborative review session occurring next Monday and Thursday (Feb. 14tth and 17th). Following our proposals targeted to the Yoga cycle, all patches partially implement the release independent spec "*Add spec for multiple subnet share servers" *[1]. *February 14th (16:00-17:30 UTC):* - 825110: Add multiple subnets per AZ support https://review.opendev.org/c/openstack/manila/+/825110 *February 17th (16:00-17:30 UTC):* - 825155: NetApp ONTAP: Add support to multiple subnets per AZ https://review.opendev.org/c/openstack/manila/+/825155 - 826462: Container: Multiple subnets per AZ https://review.opendev.org/c/openstack/manila/+/826462 [1] https://review.opendev.org/c/openstack/manila-specs/+/619925 Regards, Fernando

2 2

[release] Release countdown for week R-6, Feb 14-18
by Előd Illés 11 Feb '22

11 Feb '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 February 17th, 2022. Only bugfixes releases will be allowed beyond this point. When requesting those library releases, you can also include the stable/yogabranching 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" (February 24th, 2022) * Deliverables following a cycle-with-rc model (that would be most services), which observe a Feature freeze on that same date, February 24th, 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/yogabranches, this would be a good point for teams to review membership in their $project-stable-maint groups. Once the stable/yogabranches are cut for a repo, the ability to approve any necessary backports into those branches for Yogawill 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: February 17th, 2022(R-6 week) Client library freeze: February 24th, 2022(R-5 week) Yoga-3 milestone: February 24th, 2022(R-5 week) Cycle Highlights Due: February 24th, 2022(R-5 week) Yogafinal release: March 30th, 2022 Next PTG: April 4 - 8, 2022 (virtual) ElődIllés irc: elodilles

1 0

[election][nova] Sylvain to throw his hat into the Nova PTL ring again
by Sylvain Bauza 11 Feb '22

11 Feb '22

Hello again Nova (and Placement) fellows, This went fast, but it's time for me to run again for the Nova PTL position, this time for the Zen/Zombie/Zeta [1] release cycle, after having been the PTL for the Yoga cycle. Just a quick look at this current cycle. First, it was quick but : - we added a new way to help contributors to say they are reviewing some change - we now have a new nova-core - we have around 25 accepted feature requests and 15 of them are already reviewed. What we had't yet time to discuss and what I'd like us to start to look are : - given some operators want to upgrade at least every year, we should try to start seeing how to support two-cycle-older computes - sometimes we want to do things that we'd like but that we don't have time for. Some of them are actually simple to implement. Maybe then we should organize back ways to share ideas to new contributors and provide them mentoring efforts (eg. with Outreachy or any engineering interns wanting to work on OpenStack and Nova in particular) As you know, I'm also open to any idea. I'm not a leader, I'm just a herder. Thanks, -Sylvain [1] Pick any Z name you want given we don't know yet the result.

1 0

[cinder][nova][ironic][glance][downstream distro] raising requirements minima in yoga os-brick
by Brian Rosmaita 11 Feb '22

11 Feb '22

Hello os-brick consumers, I have a patch up raising the minima in {test-}requirements.txt for the yoga os-brick release. I seem to remember that when I did this without warning last cycle, it caused a few issues (I think mostly a cascade of updates at an inconvenient time for people still maintaining lower-constraints.txt; probably nothing more serious because we're all testing in the gates with the latest versions allowed by upper-constraints anyway). The commit message on the patch explains what changes are made (and some that aren't): https://review.opendev.org/c/openstack/os-brick/+/828802 Please respond before 18:00 UTC on Monday 14 Feb if you see any issues. (Sorry this email is a bit late, but that's how I roll.) cheers, brian

1 0

[election][trove][ptl] PTL non-candidacy
by Lingxian Kong 11 Feb '22

11 Feb '22

Hi all, I'm writing this email to let you know that I'm not going to run for Trove PTL for Z dev cycle. I've been serving Trove PTL since Train, trying the best to revive the project back to production ready, lots of changes have been made since then, and also helped my former employer successfully deploy Trove in production and pass the security review conducted by the 3rd party security company. However, I changed my job recently and shifted the focus, can't guarantee the contribution for this open source project, hopefully someone could pick that up and drive the project. I'm willing to provide help if needed. --- Lingxian Kong

1 0

[neutron] Drivers meeting - Friday 11.2.2022 - cancelled
by Lajos Katona 10 Feb '22

10 Feb '22

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

1 0

[kolla][ceilometer][gnocchi] Error in ceilometer_central service
by Mahendra Paipuri 10 Feb '22

10 Feb '22

Hello, I am playing around Openstack using kolla-ansible deployment on a single node. I am facing the same issue as here -> https://bugs.launchpad.net/kolla-ansible/+bug/1920095. I see that there is an PR here -> https://review.opendev.org/c/openstack/kolla-ansible/+/781595 but has not been merged. Is it still a bug or am I missing something in kolla configuration? Cheers Mahendra

1 1

[TaskFlow]
by 黄一心 10 Feb '22

10 Feb '22

Hi, In our project, the taskflow is used to back up and restore data. After the task is submitted or started to run, the task may be suspended. However, the program process still exists. It seems that the thread for executing the task is missing. After the program process is restarted, the task can be resumed. Can you give us some advice. Thank you.

1 0

[TaskFlow]
by 黄一心 10 Feb '22

10 Feb '22

发自我的iPhone

1 0

[all][tc] Technical Committee next weekly meeting on Feb 10th at 1500 UTC
by Ghanshyam Mann 10 Feb '22

10 Feb '22

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

1 1

[election][tc] Non-candidacy
by Belmiro Moreira 09 Feb '22

09 Feb '22

Dear all, I would like to let you know that I won't run for the Technical Committee (TC). After 2 years in this role I believe that it’s time for some rotation. It was a pleasure to work with all of you. Thank you for this amazing experience. cheers, Belmiro

4 3

[openstacksdk] create object (eg. snapshot) on behalf of user as admin
by Benedikt Trefzer 09 Feb '22

09 Feb '22

Hi list I like to connect as an amin user to an openstack cloud and create a snapshot of a volume in the same project as the volume exists. I use the openstacksdk to achive this in python. So far I can connect as admin and create the snapshot but the snapshot is in the admins project, not in the project of the volume. Code so far: from openstack import connect import openstack.config conn=connect() conn.volume.create_snapshot(name='test', description='testing', volume='volumeIDinANYproject') I tried to use conn.connect_as_project('ProjectID') but was not successfull. Please direct me in the correct direction to achive this ! Any help appreciated. Greeting Benedikt

2 2

[Skyline] Project mascot to review
by James Cole 09 Feb '22

09 Feb '22

Greetings everyone, I’m James, a designer with the OpenInfra Foundation. We have a been working on a new project mascot for Skyline and wanted to share a couple of options with you. The reference we were provided alluded to a nine-color-deer, so we created a deer illustration in the style of the other project mascots. The two options are essentially the same, but one is white with spots and the other is yellow with spots. Let me know if you like one or the other—or if we’re totally off on the theme—and we will add the text to the logo and finalize the assets. There is a PDF attached to this message or you can view the document by visiting this link <https://www.dropbox.com/s/d2ikaphzhml7tqb/20220120%20Mascots%20Project.pdf?…>. Thank you! -James

11 20

[ironic] kickstart/iso configuration
by Carol Bouchard 09 Feb '22

09 Feb '22

Ironic folks: I've set-up bifrost which is spawning two VMs to test with. I'm using the xena branch for both bifrost and ironic. Bifrost sets these VMs up as whole-disk-images. I've undeployed one VM and trying to deploy the same VM by using the default kickstart file and a RHEL7 ISO file but I'm not having any success. Could you suggest what configuration changes are expected in this case to get this to work? What would you expect deploy-interface and instance-info to look like? BTW And I've applied portions (changes to cache_ramdisk_kernel() only) of the patch for https://review.opendev.org/c/openstack/ironic/+/827924. Carol

2 1

[Update Process]
by Joshua Crawford 09 Feb '22

09 Feb '22

Hi, I have been given the task of updating our openstack/swift setup. Currently, we are on openstack 2.3.1 with python-swiftclient 3.0.0 on Ubuntu 16.04. My plan is to upgrade Ubuntu to 18.04 and then to 20.04. Then focus on updating openstack and swift. I do not have any previous experience with openstack or swift, but from what I have read so far, our current version is not supported on anything newer than Ubuntu 16.04. Should I revise my plan and look at updating openstack/swift first, or is my plan to update Ubuntu first a good path forward. Thank you, joshua. [cid:d105ac7d-e828-4289-8ff1-70d919cdb057.jpg] [cid:Quadrivium-Logo_Horizontal-OneColor-CyberSecurityServices_456360a7-a556-4b83-b682-08dcceeef14a.jpg] Joshua Crawford | Senior Engineer Quadrivium Inc. | 5537 Bleaux Ave. Springdale, AR 72762 479.419.4600 | quadrivium.com<https://quadrivium.com> [cid:cyber-verify-2021-AAA_2ce098a9-58cb-442b-9293-b75ce40d6ff4.jpg] This message is confidential. It may also be privileged or otherwise protected by work product immunity or other legal rules. If you have received it by mistake, please let us know by e-mail reply and delete it from your system; you may not copy this message or disclose its contents to anyone. The integrity and security of this message cannot be guaranteed on the Internet.

2 3

[election][Neutron]PTL candidacy for Z
by Lajos Katona 09 Feb '22

09 Feb '22

Hello Openstack Community, I write to submit my candidacy for the Neutron PTL position during the Z cycle. I have been PTL for the Yoga cycle, and I would like to serve the community for another cycle. During the last few cycles the team faced a lot of challenges, like: * Lack of review capacity, which on the other hand means that we have a lot to review, and that is good. * Channel in developers from new companies. * Keep Neutron stable while at the same time keep the speed of feature development. * CI instabilities. * Keep coverage and decrease the load Neutron jobs cause in the infra. The team tried to address these, so we have biweekly video meeting for CI issues (on the other week we kept the IRC for CI meeting), we increased the size of the drivers team, we included back some retired stadium project with new developers who would like to maintain them, or worked actively to decrease the amount of jobs we execute for each commit. As a summary I would like to continue with a focus on these items to keep Networking in Openstack stable and inclusive. Thank you for your time and consideration. Lajos Katona (lajoskatona)

1 0

[kolla] [horizon] Custom logos (WAS: [Openstack-operators] Horizon Custom Logos (Queens, 13.0.1))
by Gregory Orange 09 Feb '22

09 Feb '22

We have been using Ubuntu VMs for the control plane until now, so it was a simple matter of inserting our logo-splash.svg and logo.svg into /var/lib/openstack-dashboard/static/dashboard/img/ and then restarting services. Now we're switching to Kolla, and the relevant path isn't mounted as is the case with the likes of /etc/kolla/horizon and /var/log/kolla. We don't (yet?) build our own container images, so I'm wondering what next. Did anyone get any further with this? On 21/8/18 9:28 pm, Nick Jones wrote: > Hi Erich. > > Yeah, I battled against this myself quite recently. Here's what I did > to add a logo to the Horizon splash page and to the header of each page > itself. > > Create a file called _splash.html, containing: > > <div class="text-center"> > <img class="splash-logo" src={% themable_asset "img/logo.png" %}> > </div> > > And a file called _brand.html, containing: > > {% load branding %} > {% load themes %} > > <a class="navbar-brand" href="{% site_branding_link %}" target="_self"> > <img class="openstack-logo" src="{% themable_asset 'img/logo.png' %}" > alt="{% site_branding %}"> > </a> > > I then created a folder > called /usr/share/openstack-dashboard/openstack_dashboard/themes/default/templates/auth/ > and copied _splash.html into there, copied _brand.html > into /usr/share/openstack-dashboard/openstack_dashboard/templates/header/, > and finally my 'logo.png' was copied > into /usr/lib/python2.7/site-packages/openstack_dashboard/static/dashboard/img/ > > Note that this approach might differ slightly from your setup, as in my > case it's a Kolla-based deployment so these changes are applied to the > image I'm using to deploy a Horizon container. But it's the same > release (Queens) and a CentOS base image, so in principle the steps > should work for you. > > Hope that helps. > > -- > > -Nick > > On 20 August 2018 at 17:40, Erich Weiler <weiler(a)soe.ucsc.edu > <mailto:weiler@soe.ucsc.edu>> wrote: > > Hi Y'all, > > I've been banging my head against a wall for days on this item and > can't find anything via google on how to get around it - I am trying > to install a custom logo onto my Horizon Dashboard front page (the > splash page). I have my logo ready to go, logo-splash.png. I have > tried following the instructions here on how to install a custom logo: > > https://docs.openstack.org/horizon/queens/admin/customize-configure.html > <https://docs.openstack.org/horizon/queens/admin/customize-configure.html> > > But it simply doesn't work. It seems this stanza... > > #splash .login { > background: #355796 url(../img/my_cloud_logo_medium.png) no-repeat > center 35px; > } > > ...doesn't actually replace the logo (which is logo-splash.svg), it > only seems to put my file, logo-splash.png as the *background* to > the .svg logo. And since the option there is "no-repeat center", it > appears *behind* the svg logo and I can't see it. I played around > with those options, removing "no-repeat" for example, and it > dutifully shows my logo repeating in the background. But I need the > default logo-splash.svg file to actually be gone and my logo to > exist in it's place. Maybe I'm missing something simple? > > I'm restarting apache and memchached after every change I make when > I was testing. > > And because the images directory is rebuilt every time I restart > apache, I can't even copy in a custom logo-splash.svg file. Which > wouldn't help anyway, as I want my .png file in there instead. I > don't have the means to create a .svg file at this time. ;) > > Help! > > As a side note, I'm using the Queens distribution via RedHat. > > Many thanks in advance, > erich > > _______________________________________________ > OpenStack-operators mailing list > OpenStack-operators(a)lists.openstack.org > <mailto:OpenStack-operators@lists.openstack.org> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators> > > > > _______________________________________________ > OpenStack-operators mailing list > OpenStack-operators(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > -- Gregory Orange Cloud System Administrator Scientific Platforms Team building representative Pawsey Supercomputing Centre, CSIRO

3 3

Recently Upgraded to XENA and getting this error
by Adivya Singh 09 Feb '22

09 Feb '22

Hello, We have recently upgraded to XENA release of Openstack, and getting this error while trying to Resize instance using GUI, it is telling "Danger , Please try Later" Same is working properly from CLI without any issue Any thoughts on this Regards Adivya Singh

9 11

[kolla-ansible] custom configuration override issue.
by Satish Patel 09 Feb '22

09 Feb '22

Folks, I have a working kolla-ansible environment and now I want to push out some nova custom changes to specific compute nodes and I am trying the following override but somehow it doesn't work for me. Ansible inventory file multinode [control] 192.168.75.141 ansible_ssh_private_key_file=/root/.ssh/nodes_ssh_key 192.168.75.142 ansible_ssh_private_key_file=/root/.ssh/nodes_ssh_key 192.168.75.143 ansible_ssh_private_key_file=/root/.ssh/nodes_ssh_key [compute] 192.168.75.[144:175] ansible_ssh_private_key_file=/root/.ssh/nodes_ssh_key I want to change some option on 192.168.75.199 compute server, I don't have compute name in inventory so i am using IP address for override but somehow that doesn't work /etc/kolla/config/nova/192.168.75.199/nova.conf I have tried the following to use hypervisor hostname but that doesn't work. What am I doing wrong here? /etc/kolla/config/nova/COMP01.local/nova.conf Following works for me but they are for global not for specific nodes. How do i override specific node file? /etc/kolla/config/nova/nova-compute.conf

2 4

Error: Not authorized for image
by Michael STFC 09 Feb '22

09 Feb '22

Hi All, I have a problem with vm. Its in error state and rebooting won’t fixed it and still no luck. Error: Failed to perform requested operation on instance “xxx-production-db”, the instance has an error status: Please try again later [Error: Not authorized for image 3457dd8a-037a-4360-b77a-059d2782cbbf.].

1 0

[neutron] Bug deputy report for week of January 31
by Lajos Katona 09 Feb '22

09 Feb '22

Hi Neutron Team I was bug deputy in neutron last week. Summary ======= Needs attention ============ * Neutron-dynamic-routing does not work with OVN ( https://bugs.launchpad.net/neutron/+bug/1959666) * [stein][neutron] Static rules losed ( https://bugs.launchpad.net/neutron/+bug/1959884) * VM gets wrong ipv6 address from neutron-dhcp-agent after ipv6 address on port was changed (https://bugs.launchpad.net/neutron/+bug/1959697) Bugs with assignees ================ * Random Tempest test failures(SSH failure) in openvswitch jobs ( https://bugs.launchpad.net/neutron/+bug/1959564) ** https://review.opendev.org/c/openstack/neutron/+/827315 * QoS Ingress bandwidth limit with OVS backend may not work as expected ( https://bugs.launchpad.net/neutron/+bug/1959567) ** WIP: https://review.opendev.org/c/openstack/neutron/+/827112 * test_local_ip_connectivity test failing in stable/xena jobs ( https://bugs.launchpad.net/neutron/+bug/1959573): ** MERGED: https://review.opendev.org/c/openstack/neutron/+/827057 * pip 22 breaks python3.6 jobs (Victoria and older CI jobs) ( https://bugs.launchpad.net/neutron/+bug/1959600) ** MERGED: https://review.opendev.org/q/Iab2c391d5388461fe9e9037cee81884ce8032e72 * minimum_packet_rate qos rule type is not visible in the GET /v2.0/qos/rule-types response ( https://bugs.launchpad.net/neutron/+bug/1959749) ** https://review.opendev.org/q/topic:bug%252F1959749 * "get_rule_type" should not check the context admin status ( https://bugs.launchpad.net/neutron/+bug/1959778) ** https://review.opendev.org/c/openstack/neutron-lib/+/827533 * ovn-octavia loadbalancer not working when VIP is on a dual-stack provider network (https://bugs.launchpad.net/neutron/+bug/1959903 ) ** https://review.opendev.org/c/openstack/ovn-octavia-provider/+/827670 * [ovn] Stale ports in the OVN database at churn ( https://bugs.launchpad.net/neutron/+bug/1960006) ** https://review.opendev.org/c/openstack/neutron/+/827834 * neutron-tempest-with-uwsgi job failing tempest tests with: Floating ip <fip> failed to associate with server <server id> in time ( https://bugs.launchpad.net/neutron/+bug/1960022 ) ** MERGED: https://review.opendev.org/c/openstack/tempest/+/814085 * NullQuota driver returns None that breaks client API ( https://bugs.launchpad.net/neutron/+bug/1960032) ** https://review.opendev.org/c/openstack/neutron/+/827875 Low hanging fruit ============= * potential performance issue when scheduling network segments ( https://bugs.launchpad.net/neutron/+bug/1959750) Need more information ================== * Disallow users to allocate gateway ip of external subnets as floating ip ( https://bugs.launchpad.net/neutron/+bug/1959699 ) Regards Lajos Katona (lajoskatona)

2 1

OpenInfra Summit Berlin- CFP Deadline in 24 Hours!
by Erin Disney 09 Feb '22

09 Feb '22

The deadline for the upcoming OpenInfra Summit’s Call for Presentations is in 24 hours! CFP for the Berlin Summit (June 7-9th) is still open until February 9th at 22:59 UTC (4:59 PM CT). Reminder that Summit attendance fees are waived for all accepted speakers. Submit your talk for the OpenInfra Summit here: https://cfp.openinfra.dev/app/berlin-2022 2022 Summit Tracks: 5G, NFV & Edge AI, Machine Learning & HPC CI/CD Container Infrastructure Getting Started Hands-on Workshops NEW: Hardware Enablement Open Development Private & Hybrid Cloud Public Cloud Security More Summit resources: Registration is live at Early Bird pricing: https://openinfrasummitberlin.eventbrite.com/ Sponsorships are available: https://openinfra.dev/summit-sponsor Apply for the Travel Support Program: https://openinfrafoundation.formstack.com/forms/TSP_Berlin2022 Questions or issues with your submission? Email speakersupport(a)openinfra.dev and we will be happy to help you sort it out. Thanks, Erin Erin Disney Event Marketing Open Infrastructure Foundation Erin Disney Event Marketing Open Infrastructure Foundation

1 0

[all][Neutron][Octavia][Nova][Kuryr] Bump pyroute2 version to 0.6.5 in stable/wallaby
by Lucas Alvares Gomes 08 Feb '22

08 Feb '22

Hi, I currently have a patch up for openstack/requirements [0] bumping the version of the pyroute2 library from 0.5.14 to 0.6.5 as the older version have a memory leak issue [1] in the NDB module which can cause the service using the library to be killed by the OOM killer because of an out-of-memory condition. This email was a suggestion by a core reviewer to raise awareness from the broader community to this change/issue. Please if you have any concerning about this version bump let us know here on in the patch itself [0] [0] https://review.opendev.org/c/openstack/requirements/+/828091 [1] https://github.com/svinota/pyroute2/issues/789 Cheers, Lucas

2 2

[ironic]Anaconda deploy interface config
by Carol Bouchard 08 Feb '22

08 Feb '22

Ironic folks: I'm trying to spawn a RHEL7 image using a kickstart file and having issues with stage2 file. First I used bifrost to initially setup a couple of VMs. (There is no openstack/glance). I'm now using one of those VMs to boot up with RHEL7. I changed the VM config with the following: *| deploy_interface | anaconda* * | instance_info | {'kernel': 'http://myip:8080/RHEL7/vmlinuz <http://myip:8080/RHEL7/vmlinuz>', 'ramdisk': 'http://myip:8080/RHEL7/initrd.img <http://myip:8080/RHEL7/initrd.img>', 'image_source': 'http://myip:8080/RHEL7/initrd.img <http://myip:8080/RHEL7/initrd.img>', 'stage2': 'http://myip:8080/RHEL7/squashfs.img <http://myip:8080/RHEL7/squashfs.img>', 'ks_cfg': 'http://myip:8080/RHEL7/ks.cfg.template <http://myip:8080/RHEL7/ks.cfg.template>', 'ks_template': 'http://myip:8080/RHEL7/ks.cfg.template <http://myip:8080/RHEL7/ks.cfg.template>'}* ironic.conf changes I made are as follows: *enabled_deploy_interfaces = direct,ramdisk,anaconda* *[anaconda]default_ks_template = file:///etc/ironic/ks.cfg.template* The error I'm getting is as follows: *$ baremetal node show testvm1 --field last_error* *| last_error | Deploy step deploy.deploy failed with IsADirectoryError: [Errno 21] Is a directory: '/httpboot/4e41df61-84b1-5856-bfb6-6b5f2cd3dd11/LiveOS/squashfs.img'.* Tail end of traceback is as follows: * ironic-conductor[]: ERROR ironic.conductor.utils File "/opt/stack/bifrost/lib64/python3.9/site-packages/ironic/common/pxe_utils.py", line 1245, in cache_ramdisk_kernel ironic-conductor[]: ERROR ironic.conductor.utils deploy_utils.fetch_images(ctx, TFTPImageCache(), list(t_pxe_info.values()), ironic-conductor[]: ERROR ironic.conductor.utils File "/opt/stack/bifrost/lib64/python3.9/site-packages/ironic/drivers/modules/deploy_utils.py", line 240, in fetch_images ironic-conductor[]: ERROR ironic.conductor.utils cache.fetch_image(href, path, ctx=ctx, force_raw=force_raw) ironic-conductor[]: ERROR ironic.conductor.utils File "/opt/stack/bifrost/lib64/python3.9/site-packages/ironic/drivers/modules/image_cache.py", line 120, in fetch_image ironic-conductor[]: ERROR ironic.conductor.utils dest_up_to_date = _delete_dest_path_if_stale(master_path, ironic-conductor[]: ERROR ironic.conductor.utils File "/opt/stack/bifrost/lib64/python3.9/site-packages/ironic/drivers/modules/image_cache.py", line 460, in _delete_dest_path_if_stale ironic-conductor[]: ERROR ironic.conductor.utils os.unlink(dest_path) ironic-conductor[]: ERROR ironic.conductor.utils IsADirectoryError: [Errno 21] Is a directory: '/httpboot/4e41df61-84b1-5856-bfb6-6b5f2cd3dd11/LiveOS/squashfs.img'* Please advise. Carol

3 5

[election][cinder] PTL Candidacy for Z
by Rajat Dhasmana 08 Feb '22

08 Feb '22

Hi All, I would like to announce my candidacy for PTL of the Cinder project for the Z cycle. Since this is the first time I'm proposing my candidacy, I would like to briefly introduce myself. I started contributing to OpenStack back in the Queens release (although not very actively) and started focusing on the Cinder project in the Rocky release. I became a core reviewer in Cinder in the mid of the Stein release and since then I've been actively contributing to the Cinder project in terms of features, bug fixes, reviews etc. I'm also a part of Cinder's core security group and a stable core and currently serving as release liaison for Cinder for the past 3 releases. Coming to the focus for the Z release, Cinder receives an abundance of commits every cycle in terms of new drivers, driver features, core cinder features, bug fixes, improvements etc and we've always faced a shortage in reviews. It is not due to fewer people working actively but more of a priority issue in their respective roles. I would like to encourage contributors to discuss with their managers about the importance of code review in opensource and how it is helpful for the community and the individuals as well. Apart from that, I would like to revisit the security issues backlog since that hasn't been looked upon in quite some time and if we encounter something that needs attention, we can also hold core security meetings from time to time to address the issues. We are also getting active driver contributions every cycle which is a good thing, but sadly the driver implementation patches seem to have a lot of mistakes which are well documented in the driver contribution docs and something I would like to highlight in the Z PTG (as most of the vendors join it and propose their driver ideas). Again, the documentation is not perfect as we discussed in Yoga PTG. Following up upon this and improving it is another focus I support for Cinder. Lastly, I would like to put more emphasis upon the 3rd Party CI compliance check which we haven't done in a while and it would be good to know how many vendors are actually maintaining their CI consistently. There are some new ideas started by Brian in the past releases which I would like to continue. Some examples include the last cinder meeting being a video+IRC meeting and every third Friday of the month, we have a festival of XS reviews which significantly reduced the backlog of open patches. In the end, I would like to say, I want to continue the good trends set in the Cinder community and improve on certain areas where there is not much attention being given. I will do my best to address the above mentioned items during my time as PTL. Thanks for considering me. Rajat Dhasmana (whoami-rajat)

1 0

[election][tc] My TC non-candidacy
by Radosław Piliszek 08 Feb '22

08 Feb '22

Dears, I am hereby announcing my TC non-candidacy. It was a great pleasure to work with you but my personal and professional life has shifted away from OpenStack enough to make it hard for me to dedicate the time the TC deserves. Kind regards, -yoctozepto

4 3

[all][elections][ptl][tc] Combined PTL/TC z cycle Election Nominations Kickoff
by Ghanshyam Mann 08 Feb '22

08 Feb '22

Hello Everyone, Nominations for OpenStack PTLs (Project Team Leads) and TC (Technical Committee) positions (5 positions) are now open and will remain open until Feb 15, 2022 23:45 UTC. All nominations must be submitted as a text file to the openstack/election repository as explained at https://governance.openstack.org/election/#how-to-submit-a-candidacy Please make sure to follow the candidacy file naming convention: candidates/z/<Project_Name or "TC">/<email_address> (for example, "candidates/z/TC/stacker(a)example.org"). The name of the file should match an email address for your current OpenStack Foundation Individual Membership. Take this opportunity to ensure that your OSF member profile contains current information: https://www.openstack.org/profile/ Any OpenStack Foundation Individual Member can propose their candidacy for an available, directly-elected seat on the Technical Committee. In order to be an eligible candidate for PTL you must be an OpenStack Foundation Individual Member. PTL candidates must also have contributed to the corresponding team during the Xena to Yoga timeframe, Mar 26, 2021 00:00 UTC - Feb 15, 2022 00:00 UTC. Your Gerrit account must also have a verified email address matching the one used in your candidacy filename. Both PTL and TC elections will be held from Feb 22, 2022 23:45 UTC through to Mar 01, 2022 23:45 UTC. The electorate for the TC election are the OpenStack Foundation Individual Members who have a code contribution to one of the official teams over the Xena to Yoga timeframe, Mar 26, 2021 00:00 UTC - Feb 15, 2022 00:00 UTC, as well as any Extra ATCs who are acknowledged by the TC. The electorate for a PTL election are the OpenStack Foundation Individual Members who have a code contribution over the Xena to Yoga timeframe, Mar 26, 2021 00:00 UTC - Feb 15, 2022 00:00 UTC, in a deliverable repository maintained by the team which the PTL would lead, as well as the Extra ATCs who are acknowledged by the TC for that specific team. The list of project teams can be found at https://governance.openstack.org/tc/reference/projects/ and their individual team pages include lists of corresponding Extra ATCs. Please find below the timeline: PTL + TC nomination starts @ Feb 08, 2022 23:45 UTC PTL + TC nomination ends @ Feb 15, 2022 23:45 UTC TC campaigning starts @ Feb 15, 2022 23:45 UTC TC campaigning ends @ Feb 22, 2022 23:45 UTC PTL + TC elections start @ Feb 22, 2022 23:45 UTC PTL + TC elections end @ Mar 01, 2022 23:45 UTC Shortly after election officials approve candidates, they will be listed on the https://governance.openstack.org/election/ page. The electorate is requested to confirm their email addresses in Gerrit prior to 2022-02-15 00:00:00+00:00, so that the emailed ballots are sent to the correct email address. This email address should match one which was provided in your foundation member profile as well. Gerrit account information and OSF member profiles can be updated at https://review.openstack.org/#/settings/contact and https://www.openstack.org/profile/ accordingly. If you have any questions please be sure to either ask them on the mailing list or to the elections officials: https://governance.openstack.org/election/#election-officials -gmann & The OpenStack Technical Election Officials

1 0

[stable] sphinx docs jobs fail on old stable branches (no more py2 support)
by Előd Illés 08 Feb '22

08 Feb '22

Hi stable maintainers, This mail is about to get some attention to build-openstack-sphinx-docs job that recently started to fail on old stable branches (Queens and Pike) and block gates for about ~30 repositories. (The failures are also visible in periodic stable jobs). This is because py27 support from sphinx jobs were removed [1] recently. (Python 3 (py35) support was mostly done in Rocky so that branch is not affected) To unblock the gates I see the following options: 1. fix sphinx jobs to work with py35 (most probably requires some patches to backport - in a squashed patch - and maybe some resolution of requirement conflicts) 2. set sphinx jobs to non-voting (even better to remove them to do not use resources unnecessarily) 3. revert the patch [1] that removed the py2 support of sphinx (maybe the easiest thing to do, though i understand that py2 support is something that shouldn't be kept forever) 4. teams examine their old branches and if they are not really maintained, haven't merged patches recently, then probably it is a good time to propose their EOL transition according to the EOL process [1] Some additional thoughts: - When Extended Maintenance was introduced the community agreed that certain CI jobs can be removed, CI coverage can be reduced as time goes. - To keep open an old branch in Extended Maintenance helps the cooperation between vendors / users as instead of maintaining it by themselves it can be done with a common effort, which could be beneficial for everyone. On the other hand, if there are no maintainers or invested efforts to keep the branch and CI alive, then it is a reasonable decision to transition the branch to End of Life. Please consider the above options and act to eliminate the gate failures / periodic stable job failures. [1] https://review.opendev.org/c/zuul/zuul-jobs/+/827588 <https://review.opendev.org/#/q/I98c3da5b02a4ac7fb9d7bd8e00170762e77b9f40>[2] https://docs.openstack.org/project-team-guide/stable-branches.html#end-of-l… Thanks, Előd

2 1