January 2022 - openstack-discuss - lists.openstack.org

[watcher][core] Resignation from Watcher core
by info＠dantalion.nl 31 Jan '22

31 Jan '22

Dear all, Unfortunately I have had increasingly little available free time to spent on the Watcher project over the years. Combined with loss of access to a test environment to debug an actual Watcher deployment for which it has become apparent it will not be reinstated. These combined events inhibit me from effectively making and reviewing patches. As of such I feel it is only right to resign as Watcher core reviewer. I will remove my roles from opendev and launchpad where appropriate as well as remove myself as reviewer from any pending patches. Kind regards & stay safe, Corne (Dantali0n)

1 0

[neutron] Bug Deputy Report January 24 - 30
by Nurmatov Mamatisa 31 Jan '22

31 Jan '22

Hi, I was bug deputy last week. Below is the week summary. I would like to highlight critical bug that affects CI and unassigned #1955008 '[functional] Failure of "test_floatingip_mac_bindings"' Also let me ask OVN team to help with triage OVN related bugs (end of list below). Details: Critical --------- - https://bugs.launchpad.net/neutron/+bug/1955008 - [functional] Failure of "test_floatingip_mac_bindings" - Confirmed - Unassigned! Note: Reported in December but was new occurrences - https://bugs.launchpad.net/neutron/+bug/1959196 - New Secure RBAC policies broke devstack-enforce-scope job - Confirmed - Assigned to Slawek Kaplonski High ---- - https://bugs.launchpad.net/neutron/+bug/1959028 - [OVN][Octavia] Fix the functional CI jobs - Fix Released: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/826323 - Assigned to Rodolfo Alonso - https://bugs.launchpad.net/neutron/+bug/1959176 - neutron fullstack/functional jobs TIMED_OUT randomly - Confirmed - Unassigned - https://bugs.launchpad.net/neutron/+bug/1959151 - Don't set HA ports down while L3 agent restart - In progress: https://review.opendev.org/c/openstack/neutron/+/826545 - Assigned to Krzysztof Tomaszewski Medium ------ - https://bugs.launchpad.net/neutron/+bug/1959125 - OVN mech driver failing to check the L2/L3 connectivity - In progress: https://review.opendev.org/c/openstack/neutron/+/826502 - Assigned to Rodolfo Alonso - https://bugs.launchpad.net/neutron/+bug/1959331 - Router's external gateway isn't properly updated when new subnet is added - In progress: https://review.opendev.org/c/openstack/neutron/+/826828 - Assigned to Slawek Kaplonski - https://bugs.launchpad.net/neutron/+bug/1959332 - With new secure RBAC external gateway ports can't be visible in the API - Confirmed - Assigned to Slawek Kaplonski - https://bugs.launchpad.net/neutron/+bug/1959333 - Error 500 after request with Invalid Scope - In progress: https://review.opendev.org/c/openstack/neutron/+/826872 - Assigned to Slawek Kaplonski - https://bugs.launchpad.net/neutron/+bug/1959184 - [tempest] Test "test_list_policy_filter_by_name" failing - Fix released: https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/826827 - Assigned to yatin - https://bugs.launchpad.net/neutron/+bug/1958964 - Fully Populated Load Balancer creation with OVN provider leaves pools as PENDING_CREATE - In progress: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/826257 - Assigned to Fernando Royo Undecided --------- - https://bugs.launchpad.net/neutron/+bug/1959098 - [ovn] metadata route missing on the guest - New - Unassigned - https://bugs.launchpad.net/neutron/+bug/1958961 - [ovn-octavia-provider] lb create failing with with ValueError: invalid literal for int() with base 10: '24 2001:db8::131/64' - In progress: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/826896 - Assigned to Slawek Kaplonski Thanks, Mamatisa --- Advanced Software Technology Lab Huawei, Moscow

2 1

[neutron] CI meeting 1.02.2022 cancelled
by Slawek Kaplonski 31 Jan '22

31 Jan '22

Hi, Due to overlapping internal meetings tomorrow I have to cancel this week Neutron CI meeting. Next week I will be on PTO but meeting (8.02) will be chair by ralonsoh - thx for that. I will be back on the CI meetings in two weeks - 15.02. -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

Re: Can neutron-fwaas project be revived?
by Heng Zhou (周恒)-浪潮数据 31 Jan '22

31 Jan '22

Hi Lajos， I understand that the process is to retire neutron-fwaas first, and then create a new project in the X namespace. If want to retire the project, do we need to wait until the stable version(Victoria) of the project is no longer maintained(Extended Maintenance estimated 2022-04-27)? 发件人: Lajos Katona [mailto:katonalala@gmail.com] 发送时间: 2022年1月18日 0:15 收件人: Dazhong Qin (秦海中)-云数据中心集团 <qinhaizhong01(a)inspur.com> 抄送: miguel(a)mlavalle.com; openstack-discuss(a)lists.openstack.org; Heng Zhou (周恒)-浪潮数据 <zhouhenglc(a)inspur.com> 主题: Re: Can neutron-fwaas project be revived? Hi, Neutron team discussed this question on the Drivers meeting, see the logs: https://meetings.opendev.org/meetings/neutron_drivers/2022/neutron_drivers.… The agreement is to move neutron-fwaas to x/ namespace, and revive it as x/neutron-fwaas. Best regards Lajos Katona (lajoskatona) Dazhong Qin (秦海中)-云数据中心集团 <qinhaizhong01(a)inspur.com <mailto:qinhaizhong01@inspur.com> > ezt írta (időpont: 2022. jan. 6., Cs, 2:30): Hi，Miguel， Ok，let’s meet at January 14th. Best regards 发件人: Miguel Lavalle [mailto:miguel@mlavalle.com <mailto:miguel@mlavalle.com> ] 发送时间: 2022年1月6日 9:12 收件人: Dazhong Qin (秦海中)-云数据中心集团 <qinhaizhong01(a)inspur.com <mailto:qinhaizhong01@inspur.com> > 抄送: openstack-discuss(a)lists.openstack.org <mailto:openstack-discuss@lists.openstack.org> 主题: Re: Can neutron-fwaas project be revived? Hi Qin, Unfortunately, this coming January 7th several members of the drivers team will be off on holiday. We won't have a quorum to discuss your proposal. I hope that January 14th works for you and your team. Best regards Miguel On Fri, Dec 24, 2021 at 10:18 AM Miguel Lavalle <miguel(a)mlavalle.com <mailto:miguel@mlavalle.com> > wrote: Hi Qin, I have added this topic to the drivers meeting agenda (see on demand agenda close to the bottom): https://wiki.openstack.org/wiki/Meetings/NeutronDrivers Cheers On Thu, Dec 23, 2021 at 7:42 PM Dazhong Qin (秦海中)-云数据中心集团 <qinhaizhong01(a)inspur.com <mailto:qinhaizhong01@inspur.com> > wrote: Hi Miguel, Thank you for your suggestion. My colleague HengZhou will submit relevant documents as soon as possible in accordance with the official neutron rules. Yes，we will attend the neutron drivers meeting on January 7th. Merry Christmas! Best wish for you! 发件人: Miguel Lavalle [mailto:miguel@mlavalle.com <mailto:miguel@mlavalle.com> ] 发送时间: 2021年12月24日 0:43 收件人: Dazhong Qin (秦海中)-云数据中心集团 <qinhaizhong01(a)inspur.com <mailto:qinhaizhong01@inspur.com> > 抄送: openstack-discuss(a)lists.openstack.org <mailto:openstack-discuss@lists.openstack.org> 主题: Re: Can neutron-fwaas project be revived? Hi Qin, In preparation for your meeting with the drivers team, I suggest we follow as a starting point the Neutron Stadium Governance rules and processes as outlined in the official documentation: https://docs.openstack.org/neutron/latest/contributor/stadium/governance.ht…. In the past, we have re-incorporated projects to the Stadium, like for example in the case of neutron-vpnaas. This document in the Neutron specs repo summarizes how we assessed the readiness of vpnaas for the stadium: https://specs.openstack.org/openstack/neutron-specs/specs/stadium/queens/ne… (https://review.opendev.org/c/openstack/neutron-specs/+/506012) I suggest you start a similar document for fwaas in the folder for the current cycle: https://specs.openstack.org/openstack/neutron-specs/specs/yoga/index.html. As soon as you can, please push it to gerrit, so we can start reviewing it. Did I understand correctly that you will attend the drivers meeting on January 7th? Best regards Miguel On Wed, Dec 22, 2021 at 8:09 PM Dazhong Qin (秦海中)-云数据中心集团 <qinhaizhong01(a)inspur.com <mailto:qinhaizhong01@inspur.com> > wrote: Hi Miguel, I am glad to hear this news. How about our discussion on January 7th, this Friday is not convenient, what do I need to prepare before the discussion, do I need to submit rfe or other descriptions? 发件人: Miguel Lavalle [mailto: <mailto:miguel@mlavalle.com> miguel(a)mlavalle.com] 发送时间: 2021年12月23日 0:20 收件人: Dazhong Qin (秦海中)-云数据中心集团 < <mailto:qinhaizhong01@inspur.com> qinhaizhong01(a)inspur.com> 抄送: <mailto:openstack-discuss@lists.openstack.org> openstack-discuss(a)lists.openstack.org 主题: Re: Can neutron-fwaas project be revived? Hi Qin, I think that in principle the community will be delighted if you and your team can reactivate the project and maintain it. Probably the best next step is for you to attend the next Neutron drivers meeting (https://wiki.openstack.org/wiki/Meetings/NeutronDrivers) so we can discuss the specifics of your proposal. This meeting takes place on Fridays at 1400 UTC over IRC in oftc.net <http://oftc.net> , channel #openstack-neutron. Due to the end of year festivities in much of Europe and America, the next meeting will take place until January 7th. Is that a good next step for you? If yes, I'll add this topic to the meeting's agenda. Best regards On Tue, Dec 21, 2021 at 10:29 AM Dazhong Qin (秦海中)-云数据中心集团 <qinhaizhong01(a)inspur.com <mailto:qinhaizhong01@inspur.com> > wrote: Hi： The firewall project is a necessary function when the project is delivered. The lack of firewall function after switching OVN is not acceptable to customers. We intend to maintain this project and develop the fwaas driver based on ovn. Whether the neutron-fwaas project can be reactivate? What should I do ?

5 9

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

29 Jan '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-01-27-15.00.log.html * Next week's meeting is on 3rd Feb Thursday 15:00 UTC, feel free add the topic on the agenda[1] by 2nd Feb. 2. What we completed this week: ========================= * "FIPS compatibility and compliance" community-wide goal proposal is merged[2] * Renamed Skyline repo to openstack/ namespace[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 ----------------- * 3 open reviews for ongoing activities[5]. Renaming all `master` branches on all repos to `main` --------------------------------------------------------------- lourot brought this topic and we discussed if we want to do that. Key point here is how much effort it will take to do for all the existing repo in term of make it working in CI/integration testing tooling/other scripts or not. And we should do it for new repo only. All these are unknown as of now. As first step, lourot will try the project-config importing of dummy project with 'main' branch from GitHub. Based on that, we will discuss it further. Z release cycle name ------------------------- Name nomination is closed, election for proposed names are in-progress. Follow the ML thread for updates[6]. Z release cycle Technical Election --------------------------------------- Election schedule is under review [7], please review and add your feedback. Remove the tags framework --------------------------------- yoctozepto has proposed the WIP patch to remove the tag framework, feel free to review and provide early feedback[8]. OpenStack Pain points discussion ---------------------------------------- No updates in this week. Stay tuned on the ML thread[9] and Rico will inform you about the next meeting details. TC position on release cadence ------------------------------------- Dan started the skip level upgrade in grenade and made its working for stable/wallaby to master[10]. TC is planning to meet and discuss the release cadence on 3rd Feb 16 UTC. Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[11]. Project updates ------------------- * Retire js-openstack-lib (waiting on Adjutant to have new PTL/maintainer) [12] 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[13]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [14] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://governance.openstack.org/tc/goals/proposed/fips.html [3] https://review.opendev.org/c/openstack/governance/+/826243 [4] https://etherpad.opendev.org/p/tc-yoga-tracker [5] https://review.opendev.org/q/projects:openstack/governance+status:open [6] http://lists.openstack.org/pipermail/openstack-discuss/2022-January/026810.… [7] https://review.opendev.org/c/openstack/election/+/825017 [8] https://review.opendev.org/c/openstack/governance/+/822900 [9] http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026245… [10] https://review.opendev.org/c/openstack/grenade/+/826101 [11] https://etherpad.opendev.org/p/zuul-config-error-openstack [12] https://review.opendev.org/c/openstack/governance/+/798540 [13] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [14] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

Secure Boot VM issues (libvirt / SMM) | Secure boot requires SMM feature enabled
by Imran Hussain 28 Jan '22

28 Jan '22

Hi, Deployed Wallaby on Ubuntu 20.04 nodes. Having issues with libvirt XML being incorrect, I need the smm bit (<smm state='on'/>) and it isn't being added to the XML. Anyone seen this before? Or any ideas? More info below... Error message: : libvirt.libvirtError: unsupported configuration: Secure boot requires SMM feature enabled Versions: libvirt version: 6.0.0, package: 0ubuntu8.15 QEMU emulator version 4.2.1 (Debian 1:4.2-3ubuntu6.18) Nova 23.1.1 (deployed via kolla, so kolla/ubuntu-source-nova-compute:wallaby is the image) ovmf 0~20191122.bd85bf54-2ubuntu3.3 Context: https://specs.openstack.org/openstack/nova-specs/specs/wallaby/implemented/… Image metadata: hw_firmware_type: uefi hw_machine_type: q35 os_secure_boot: required os_hidden: false hw_disk_bus: scsi hw_qemu_guest_agent: yes hw_scsi_model: virtio-scsi hw_video_model: virtio os_require_quiesce: yes os_secure_boot: required os_hidden: false XML snippets taken from nova-compute.log: <sysinfo type="smbios"> <system> <entry name="manufacturer">OpenStack Foundation</entry> <entry name="product">OpenStack Nova</entry> <entry name="version">23.1.1</entry> <entry name="serial">2798e3fe-ffae-4c26-955b-ef150b849561</entry> <entry name="uuid">2798e3fe-ffae-4c26-955b-ef150b849561</entry> <entry name="family">Virtual Machine</entry> </system> </sysinfo> <os> <type machine="q35">hvm</type> <loader type="pflash" readonly="yes" secure="yes">/usr/share/OVMF/OVMF_CODE.ms.fd</loader> <nvram template="/usr/share/OVMF/OVMF_VARS.ms.fd"/> <boot dev="cdrom"/> <smbios mode="sysinfo"/> </os> <features> <acpi/> <apic/> </features> Other info: # cat /usr/share/qemu/firmware/40-edk2-x86_64-secure-enrolled.json { "description": "UEFI firmware for x86_64, with Secure Boot and SMM, SB enabled, MS certs enrolled", "interface-types": [ "uefi" ], "mapping": { "device": "flash", "executable": { "filename": "/usr/share/OVMF/OVMF_CODE.ms.fd", "format": "raw" }, "nvram-template": { "filename": "/usr/share/OVMF/OVMF_VARS.ms.fd", "format": "raw" } }, "targets": [ { "architecture": "x86_64", "machines": [ "pc-q35-*" ] } ], "features": [ "acpi-s3", "amd-sev", "enrolled-keys", "requires-smm", "secure-boot", "verbose-dynamic" ], "tags": [ ] }

2 3

[release] Release countdown for week R-8, Jan 31 - Feb 04
by Előd Illés 28 Jan '22

28 Jan '22

General Information ------------------- The following cycle-with-intermediary deliverables have not done any intermediary release yet during this cycle. The cycle-with-rc release model is more suited for deliverables that plan to be released only once per cycle. As a result, we have proposed[1] to change the release model for the following deliverables: ovn-octavia-provider ironic-prometheus-exporter ironic-python-agent-builder ironic-ui networking-baremetal networking-generic-switch patrole swift [1] https://review.opendev.org/q/topic:not-yet-released-yoga PTLs and release liaisons for each of those deliverables can either +1 the release model change, or propose an intermediary release for that deliverable. In absence of answer by the end of R-8week we'll consider that the switch to cycle-with-rc is preferable. We also published a proposed release schedule for the upcoming Zcycle. Please check out the separate thread: http://lists.openstack.org/pipermail/openstack-discuss/2022-January/026696.… 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) Yoga final release: March 30th, 2022 Next PTG: April 4 - 8, 2022 (virtual) Előd Illés irc: elodilles

1 0

[sdk][devstack] openstacksdk-functional-devstack job failing on stable branches
by Brian Rosmaita 28 Jan '22

28 Jan '22

openstacksdk-functional-devstack began failing in the stable branches (xena through ussuri) shortly after 2022-01-24 11:53:49 with the error openstack.exceptions.ResourceNotFound: ResourceNotFound: 404: Client Error for url: https://{ip_address}:9696/v2.0/qos/policies/69e472c0-37d2-46e0-9b9e-727c962c5511/minimum_packet_rate_rules, The resource could not be found. for these four tests: openstack.tests.functional.network.v2.test_qos_minimum_packet_rate_rule.TestQoSMinimumPacketRateRule.test_find openstack.tests.functional.network.v2.test_qos_minimum_packet_rate_rule.TestQoSMinimumPacketRateRule.test_get openstack.tests.functional.network.v2.test_qos_minimum_packet_rate_rule.TestQoSMinimumPacketRateRule.test_list openstack.tests.functional.network.v2.test_qos_minimum_packet_rate_rule.TestQoSMinimumPacketRateRule.test_update job build history: https://zuul.opendev.org/t/openstack/builds?job_name=openstacksdk-functiona… It's passing in master and stable/{train,stein,rocky}. Anyone know what's up?

6 6

[nova][powervm][zvm] Time to mark powervm and zvm drivers as deprecated for removal?
by Stephen Finucane 28 Jan '22

28 Jan '22

I've had a PR open against the pypowervm library for over a fortnight now [1] with no activity. This has prompted me to go looking into the state of the powervm driver and what I've found isn't great. It doesn't seem there has been any feature development on the driver for many years, and the last change I can see that wasn't simply of a case of "I need to do this to get tests to pass" was over three years ago [2]. The CI also doesn't appear to have been touched in years. The situation for zvm isn't any better. The last functional change to that driver was nearly 2 years ago and I wasn't able to spot any CI running (though it's possible I just missed this). This means the powervm and zvm drivers stand out from the other non-libvirt drivers in-tree, each of which are getting at least some activity (albeit out- of-tree for Hyper-V, from what I recall). It also begs the question: are these drivers something we want to keep around? If we do, how are we going to maintain them long term? If not, how aggressive should we be in removing that now dead code? I'll open patches to mark both powervm and zvm as deprecated shortly so that, assuming nothing changes in the interim, we can look to remove it early in the Z cycle. Please respond here or on the reviews if you have concerns. Stephen [1] https://github.com/powervm/pypowervm/pull/17 [2] Change ID I89ad36f19672368a1f795e1f29c5af6368ccfeec

1 1

[cyborg] cancel weekly meeting in on February 4, 2022
by Brin Zhang(张百林) 28 Jan '22

28 Jan '22

Hi all, February 1~ February 6, 2022 are the Spring Festival of China, so we will cancel next weekly meeting, if you have some questions you can ping us by email. best regard brinzhang

1 0

[neutron] Drivers meeting agenda - 28.01.2022
by Lajos Katona 27 Jan '22

27 Jan '22

Hi Neutron Drivers, The agenda for tomorrow's drivers meeting is at [1]. There is no RFE proposed this week, but I would like to discuss again how to handle neutron-fwaas. To simplify things TC asked to keep neutron-fwaas under openstack/ namespace, see the discussion on #openstack-tc: https://meetings.opendev.org/irclogs/%23openstack-tc/%23openstack-tc.2022-0… [1] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers#Agenda See you at the meeting tomorrow. Lajos Katona (lajoskatona)

1 0

[rbac][keystone][kolla][osa][tripleo][charms] RBAC in Yoga for deployment projects
by Mark Goddard 27 Jan '22

27 Jan '22

Hi, If you haven't been paying close attention, it would be easy to miss some of the upcoming RBAC changes which will have an impact on deployment projects. I thought I'd start a thread so that we can share how we are approaching this, get answers to open questions, and ideally all end up with a fairly consistent approach. The secure RBAC work has a long history, and continues to evolve. According to [1], we should start to see some fairly substantial changes over the next few releases. That spec is fairly long, but worth a read. In the yoga timeline [2], there is one change in particular that has an impact on deployment projects, "3. Keystone enforces scope by default". After this change, all of the deprecated policies that many still rely on in Keystone will be removed. In kolla-ansible, we have an etherpad [5] with some notes, questions and half-baked plans. We made some changes in Xena [3] to use system scope in some places when interacting with system APIs in Ansible tasks. The next change we have staged is to add the service role to all service users [4], in preparation for [2]. Question: should the role be added with system scope or in the existing service project? The obvious main use for this is token validation, which seems to allow system or project scope. We anticipate that some service users may still require some project-scoped roles, e.g. when creating resources for octavia. We'll deal with those on a case by case basis. In anticipation of keystone setting enforce_scope=True and removing old default policies (which I assume effectively removes enforce_new_defaults?), we will set this in kolla-ansible, and try to deal with any fallout. Hopefully the previous work will make this minimal. How does that line up with other projects' approaches? What have we missed? Mark [1] https://opendev.org/openstack/governance/src/branch/master/goals/selected/c… [2] https://opendev.org/openstack/governance/src/branch/master/goals/selected/c… [3] https://opendev.org/openstack/kolla-ansible/commit/2e933dceb591c3505f35c2c1… [4] https://review.opendev.org/c/openstack/kolla-ansible/+/815577 [5] https://etherpad.opendev.org/p/enabling-system-scope-in-kolla-ansible

6 23

[manila][cinder][glance][nova] Pop-up team for design and development of a Cephadm DevStack plugin
by Victoria Martínez de la Cruz 27 Jan '22

27 Jan '22

Hi all, I'm reaching out to you to let you know that we will start the design and development of a Cephadm DevStack plugin. Some of the reasons on why we want to take this approach: - devstack-plugin-ceph worked for us for a lot of years, but the development of it relies on several hacks to adapt to the different Ceph versions we use and the different distros we support. This led to a monolithic script that sometimes is hard to debug and break our development environments and our CI - cephadm is the deployment tool developed and maintained by the Ceph community, it allows their users to get specific Ceph versions very easily and enforces good practices for Ceph clusters. From their docs, "Cephadm manages the full lifecycle of a Ceph cluster. It starts by bootstrapping a tiny Ceph cluster on a single node (one monitor and one manager) and then uses the orchestration interface (“day 2” commands) to expand the cluster to include all hosts and to provision all Ceph daemons and services. [0]" - OpenStack deployment tools are starting to use cephadm as their way to deploy Ceph, so it would be nice to include cephadm in our development process to be closer with what is being done in the field I started the development of this in [1], but it might be better to change devstack-plugin-ceph to do this instead of having a new plugin. This is something I would love to discuss in a first meeting. Having said this, I propose using the channel #openstack-cephadm in the OFTC network to talk about this and set up a first meeting with people interested in contributing to this effort. Thanks, Victoria [0] https://docs.ceph.com/en/pacific/cephadm/ [1] https://github.com/vkmc/devstack-plugin-cephadm

5 6

[TripleO] gate blocker centos-9 please hold rechecks
by Marios Andreou 27 Jan '22

27 Jan '22

o/ Hi folks please hold rechecks especially if you see failing centos9 jobs (should be all of master tripleo repos now) we have a gate blocker there https://bugs.launchpad.net/tripleo/+bug/1959181 thank you, marios (on behalf of tripleo-ci team - #oooq and #tripleo channels)

1 1

Neutron issue || Remote error: TimeoutError QueuePool limit of size 5 overflow 50 reached
by Md. Hejbul Tawhid MUNNA 27 Jan '22

27 Jan '22

Hi, Suddenly we have observed few VM down . then we have found some agent are getting down (XXX) , agents are getting UP and down randomly. Please check the attachment. //////////////////////////////////////////////////////////////////////////////////////////////////// /sqlalchemy/pool.py", line 788, in _checkout\n fairy = _ConnectionRecord.checkout(pool)\n', u' File "/usr/lib64/python2.7/site-packages/sqlalchemy/pool.py", line 532, in checkout\n rec = pool._do_get()\n', u' File "/usr/lib64/python2.7/site-packages/sqlalchemy/pool.py", line 1186, in _do_get\n (self.size(), self.overflow(), self._timeout), code="3o7r")\n', u'TimeoutError: QueuePool limit of size 5 overflow 50 reached, connection timed out, timeout 30 (Background on this error at: http://sqlalche.me/e/3o7r)\n']. 2022-01-24 01:05:39.592 302841 ERROR neutron.agent.l3.agent Traceback (most recent call last): 2022-01-24 01:05:39.592 302841 ERROR neutron.agent.l3.agent File "/usr/lib/python2.7/site-packages/neutron/agent/l3/agent.py", line 837, in _report_state 2022-01-24 01:05:39.592 302841 ERROR neutron.agent.l3.agent True) 2022-01-24 01:05:39.592 302841 ERROR neutron.agent.l3.agent File "/usr/lib/python2.7/site-packages/neutron/agent/rpc.py", line 97, in report_state 2022-01-24 01:05:39.592 302841 ERROR neutron.agent.l3.agent return method(context, 'report_state', **kwargs) 2022-01-24 01:05:39.592 302841 ERROR neutron.agent.l3.agent File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/client.py", line 179, in call 2022-01-24 01:05:39.592 302841 ERROR neutron.agent.l3.agent retry=self.retry) 2022-01-24 01:05:39.592 302841 ERROR neutron.agent.l3.agent File "/usr/lib/python2.7/site-packages/oslo_messaging/transport.py", line 133, in _send 2022-01-24 01:05:39.592 302841 ERROR neutron.agent.l3.agent retry=retry) 2022-01-24 01:05:39.592 302841 ERROR neutron.agent.l3.agent File "/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 645, in send 2022-01-24 01:05:39.592 302841 ERROR neutron.agent.l3.agent call_monitor_timeout, retry=retry) 2022-01-24 01:05:39.592 302841 ERROR neutron.agent.l3.agent File "/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 636, in _send 2022-01-24 01:05:39.592 302841 ERROR neutron.agent.l3.agent raise result 2022-01-24 01:05:39.592 302841 ERROR neutron.agent.l3.agent RemoteError: Remote error: TimeoutError QueuePool limit of size 5 overflow 50 reached, connection timed out, timeout 30 (Background on this error at: http://sqlalche.me/e/3o7r) 2022-01-24 01:05:39.592 302841 ERROR neutron.agent.l3.agent [u'Traceback (most recent call last):\n', u' File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/server.py", line 163, in _process_incoming\n res = self.dispatcher.dispatch(message)\n', u' File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 265, in dispatch\n return self._do_dispatch(endpoint, method, ctxt, args)\n', u' File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 194, in _do_dispatch\n ///////////////////////////////////////////////////////////////////////////////// Is there anything related with the following default configuration. /etc/neutron/neutron.conf #max_pool_size = 5 #max_overflow = 50 regards, Munna

4 7

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

27 Jan '22

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

1 1

[cinder] Bug deputy report for week of 01-26-2022
by Sofia Enriquez 26 Jan '22

26 Jan '22

This is a bug report from 01-19-2022 to 01-26-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- The cinder bug meeting will return on Feb 16th. If you have an urgent bug, please bring it to the main cinder meeting! Medium - https://bugs.launchpad.net/cinderlib/+bug/1958159 "stable/ussuri: cinderlib-lvm-functional job is failing." Fix proposed to stable/ussuri and master. Assigned to Takashi Kajinami. - https://bugs.launchpad.net/cinder/+bug/1958632 "SVC storwize regression after fixing 1913363." Unassigned. Incompleted - https://bugs.launchpad.net/cinder/+bug/1958845 "Rbd: possibility of data loss during revert-to-snap." Fix proposed to master. Cheers -- 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

[swift] Dropping support for py27
by Timothy Burke 26 Jan '22

26 Jan '22

The Swift team plans for the coming Yoga release to be the final Swift release to support Python 2.7. This is long overdue; it is now two years since the official Python 2.7 end-of-life. We were relatively late in adding Python 3 support, however, and wanted to ensure a long-enough period to root out Python 3 bugs and transition existing Python 2 clusters. We've used that time effectively; now it's time to move forward. We'll do what we can to ensure subsequent releases are *not* considered for installation on unsupported versions of Python. Notably, we'll ensure wheels are no longer flagged as universal, and `python_requires` will be set. If you have a continued interest in running latest Swift on Python 2.7, please get in touch with us, either here on the mailing list or in #openstack-swift on OFTC. Tim Burke Swift PTL

1 0

[cinder] Bug deputy report for week of 01-19-2022
by Sofia Enriquez 26 Jan '22

26 Jan '22

This is a bug report from 01-12-2022 to 01-19-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Medium - https://bugs.launchpad.net/cinder/+bug/1957804 "RBD deferred deletion causes undeletable RBD snapshots." In Progress. Assigned to Eric. - https://bugs.launchpad.net/cinder/+bug/1958122 "HPE 3PAR: In multi host env, multi-detach works partially if volume is attached to instances from separate hosts." In Progress. Assigned to Raghavendra Tilay. Low - https://bugs.launchpad.net/cinder/+bug/1958023 "Solidfire: there are some references to the removed parameters left." In Progress. Assigned to kajinamit. - https://bugs.launchpad.net/cinder/+bug/1958245 "NetApp ONTAP driver shows type error exception when replicating FlexGroups." Unassigned. Cheers, -- 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>

2 2

[heat][interop] StackBuildErrorException on a master job
by Martin Kopec 26 Jan '22

26 Jan '22

Hi there, our interop master job (jobs for older OpenStack releases are fine) is constantly failing on 2 heat tests: heat_tempest_plugin.tests.functional.test_software_config.ParallelDeploymentsTest.test_deployments_metadata heat_tempest_plugin.tests.functional.test_software_config.ParallelDeploymentsTest.test_deployments_timeout_failed Full log at: https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/… Patch where you can see all the jobs - master one failing and the rest passing: https://review.opendev.org/c/openinfra/refstack-client/+/819918 We can't figure out what's going on there. Maybe additional configuration of the deployment is required? New requirements? Any ideas what the job is missing? Thank you, -- Martin Kopec Senior Software Quality Engineer Red Hat EMEA

2 3

2021 OpenInfra Foundation Annual Report Now Available
by Kendall Nelson 26 Jan '22

26 Jan '22

Hello Everyone! The 2021 OpenInfra Annual Report is live! It includes sections on all OpenInfra projects, Foundation updates, open infrastructure growth, SIG and WG updates, and more. You can find the 2021 OpenInfra Annual Report here: https://openinfra.dev/annual-report/2021 Thanks! Kendall (diablo_rojo)

1 0

[release][infra] SSH host key issue - RedFlag stop approving
by Előd Illés 26 Jan '22

26 Jan '22

Hi, tag-release jobs started to fail today and what i see is mostly that ECDSA host key for IP address X not in list of known hosts [1][2][3] Please don't approve release patches until we haven't figure out what is the problem. [1] https://zuul.opendev.org/t/openstack/build/a490703c83514eb7ba9d0ff6307f7371… [2] https://zuul.opendev.org/t/openstack/build/00d3f765ea6847a3bf7ea53294cf2a88… [3] https://zuul.opendev.org/t/openstack/build/d8aaeff52dac442e89fd3e253596e0c2… Thanks, Előd irc:elodilles @ #openstack-release

2 4

[monasca] [Release-job-failures] Release of openstack/monasca-agent for ref refs/tags/4.0.1 failed
by Előd Illés 26 Jan '22

26 Jan '22

Hi Monasca team, The forwarded mail contains a release job failure, specifically the publish-monasca-agent-docker-images job failed [1] with a missing package during docker image build. Can you please have a look at the issue? [1] https://zuul.opendev.org/t/openstack/build/2ebcbfec634c4c068e9f7625473ea726 Thanks in advance, Előd irc:elodilles @ #openstack-release -------- Forwarded Message -------- Subject: [Release-job-failures] Release of openstack/monasca-agent for ref refs/tags/4.0.1 failed Date: Wed, 26 Jan 2022 11:57:09 +0000 From: zuul(a)openstack.org Reply-To: openstack-discuss(a)lists.openstack.org To: release-job-failures(a)lists.openstack.org Build failed. - openstack-upload-github-mirror https://zuul.opendev.org/t/openstack/build/bba91d0025a2496087a29803451a314f : SUCCESS in 45s - release-openstack-python https://zuul.opendev.org/t/openstack/build/a749eb25de1d426e845740cae1876afe : SUCCESS in 3m 50s - announce-release https://zuul.opendev.org/t/openstack/build/551dd5bd118347908b7113a5e2fa5c5e : SUCCESS in 5m 37s - propose-update-constraints https://zuul.opendev.org/t/openstack/build/e95a5bee9817491d84c89f89758872d6 : SUCCESS in 4m 18s - publish-monasca-agent-docker-images https://zuul.opendev.org/t/openstack/build/2ebcbfec634c4c068e9f7625473ea726 : POST_FAILURE in 7m 08s _______________________________________________ Release-job-failures mailing list Release-job-failures(a)lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/release-job-failures

2 1

Z Release Naming ...
by Jay Bryant 26 Jan '22

26 Jan '22

All, As in the past, I would like the community's input on the 'Z' release name [1] . I have narrowed the list down to my top 4 choices. Please take a few minutes to vote. The poll closes around 14:30 UTC on 1/28/22. Thanks for your input! Jay (jungleboyj) [1] https://twitter.com/jungleboyj/status/1486344910693441541

1 0

[horizon] Cancelling Today's weekly meeting
by vishal manchanda 26 Jan '22

26 Jan '22

Hello Team, Since there are no agenda items [1] to discuss for today's horizon weekly meeting. Also, Today is a holiday for me. So let's cancel today's weekly meeting. The next weekly meeting will be on 2nd February. Thanks & Regards, Vishal Manchanda [1] https://etherpad.opendev.org/p/horizon-release-priorities

1 0