February 2023 - openstack-discuss

[election][ptl][nova][placement] Candidacy for 2023.2 Bobcat
by Sylvain Bauza 13 Feb '23

13 Feb '23

Hey Nova and Placement folks, Despite me saying that Antelope would have been my last cycle as PTL, I have to fight the evidence : our project needs more contributors and we're struggled by our current dynamics. That's why I'm hereby proposing to act as PTL for this Bobcat release. When looking at the mirror, we tried a couple of things te lower the entry barrier in order to contribute to the Nova/Placement community : - we had a productive meet-and-greet session at the Berlin summit - we introduced a Review-Priority Gerrit label for identifying upstream interest - people volunteered for upstream bug triage on a weekly basis - we tried to minimize merge conflicts by ordering API changes Those different efforts worked pretty well for helping the Nova project to get more hands willing to solve problems, but it didn't helped that far the reviewing dynamics. Yes, we not only need contributors that contribute but we also need contributors that review what others contribute. During this Bobcat cycle, I'll propose a couple of incentives in that direction. This release is also special because it will be our first 'not-SLURP' [1] one. As a PTL, I'll take an attention to track all the developments so we can identify the necessary knobs in order to make this 'skipped' release a painless experience for our operators. Last but certainly not the least, the recent weeks showed us how fragile we are when our Zuul gate gets cold. I'll continue to propose help, support and visibility for our beloved firefighters that dig into those problems, including the stable branches which are crucial for many consumers of those branches. Anyway, nothing can happen magically, we need hands. Thanks, -Sylvain [1] https://governance.openstack.org/tc/resolutions/20220210-release-cadence-ad…

1 0

[neutron] Bug Deputy Report February 6 - 12
by Elvira Garcia Ruiz 13 Feb '23

13 Feb '23

Hi! Here you have the Neutron bug report from February 6th to 12th: Critical --------- - https://bugs.launchpad.net/neutron/+bug/2004656 - "rpc_workers" config variable needs to be registered in stadium projects Fix proposed https://review.opendev.org/c/openstack/neutron/+/872644 Assigned to ralonsoh High ------ - https://bugs.launchpad.net/neutron/+bug/2006112 - [OVN] Error during execution of "add_vnic_type_and_pb_capabilities_to_lsp" Fix proposed: https://bugs.launchpad.net/neutron/+bug/2006112 Assigned to ralonsoh - https://bugs.launchpad.net/neutron/+bug/2006603 - [FT] Test "OVSInterfaceEventTestCase.test_port_creation_and_deletion" randomly failing Fix proposed: https://review.opendev.org/c/openstack/neutron/+/873118 Assigned to ralonsoh - https://bugs.launchpad.net/neutron/+bug/2006612 - [FT] Test "TestOVNNeutronAgent.test_ovs_and_ovs_events" failing randomly Fix proposed: https://review.opendev.org/c/openstack/neutron/+/873126 Assigned to ralonsoh - https://bugs.launchpad.net/neutron/+bug/2006734 - [OVN] OVN trunk driver is not bumping the OVN LSP "external_ids:revision_number" Fix proposed: https://review.opendev.org/c/openstack/neutron/+/873296 - https://bugs.launchpad.net/neutron/+bug/2006735 - [OVN] OVN trunk driver is not bumping the OVN LSP "external_ids:revision_number" Fix proposed: https://review.opendev.org/c/openstack/neutron/+/873247 Assigned to ralonsoh - https://bugs.launchpad.net/neutron/+bug/2006264 - [CI] tox-py311 job timing out some times Unassigned https://bugs.launchpad.net/neutron/+bug/2006953 - [stable/wallaby] test_established_tcp_session_after_re_attachinging_sg is unstable on ML2/OVS iptables_hybrid job Unassigned - https://bugs.launchpad.net/neutron/+bug/2006683 - fwaas scenario job fails randomly Unassigned Medium ----------- - https://bugs.launchpad.net/neutron/+bug/2004581 - Neutron API query error, implicit cast does not exist in postgresql Fix proposed: https://review.opendev.org/c/openstack/neutron/+/872745 Assigned to ralonsoh - https://bugs.launchpad.net/neutron/+bug/2006496 - [L3-HA] "max_l3_agents_per_router" not honored when the redundancy is reduced Fix proposed: https://review.opendev.org/c/openstack/neutron/+/873107 Assigned to ralonsoh https://bugs.launchpad.net/neutron/+bug/2006949 - SLAAC and stateless DHCP are not working with stateless SG Assigned to Ihar Low ----- https://bugs.launchpad.net/neutron/+bug/2006122 - ExternalGatewayForFloatingIPNotFound returns misleading http status code Fix proposed: https://review.opendev.org/c/openstack/neutron-lib/+/872748 Assigned to Felix Huettner Undecided -------------- - https://bugs.launchpad.net/neutron/+bug/2006145 - BGP Speaker peer sessions down when rabbitmq offline I looked for the l3 bgp lieutenants for better triaging but I was not able to find them online. Kind regards, Elvira

1 0

[kolla]RabbitMQ HA policies define
by Satish Patel 13 Feb '23

13 Feb '23

Folks, I have deployed 3 node kolla controllers and notice rabbitMQ doesn't have any HA policy for queues. when i rebooted one of the nodes and found some messages got lost. Any reason kolla doesn't use HA policies by default? If i want to add policies then where should i specify them or any doc you can point me to define policies.

4 11

[trove] Larger than max_request_body_size
by Jorge Visentini 13 Feb '23

13 Feb '23

Hi all. I'm noob in Openstack, so I'm testing/studying the features. At the moment I am testing the Trove but I can't start a database instance... This error appears for me. 2023-02-10 18:07:19.888 1651 ERROR trove.taskmanager.models [-] Failed to create server for instance 58558983-e67e-465d-894f-456b118ff555 *Request is too large. Larger than max_request_body_size (114688). * (HTTP 413) (Request-ID: req-7993a97f-0738-4edf-aa6c-0c4c37f609c5) Traceback (most recent call last): File "/usr/lib/python3.9/site-packages/trove/taskmanager/models.py", line 844, in _create_server_volume server = self._create_server( File "/usr/lib/python3.9/site-packages/trove/taskmanager/models.py", line 999, in _create_server server = self.nova_client.servers.create( File "/usr/lib/python3.9/site-packages/novaclient/v2/servers.py", line 1562, in create return self._boot(response_key, *boot_args, **boot_kwargs) File "/usr/lib/python3.9/site-packages/novaclient/v2/servers.py", line 887, in _boot return self._create('/servers', body, response_key, File "/usr/lib/python3.9/site-packages/novaclient/base.py", line 363, in _create resp, body = self.api.client.post(url, body=body) File "/usr/lib/python3.9/site-packages/keystoneauth1/adapter.py", line 401, in post return self.request(url, 'POST', **kwargs) File "/usr/lib/python3.9/site-packages/novaclient/client.py", line 78, in request raise exceptions.from_response(resp, body, url, method) novaclient.exceptions.OverLimit: Request is too large. Larger than max_request_body_size (114688). (HTTP 413) (Request-ID: req-7993a97f-0738-4edf-aa6c-0c4c37f609c5) : novaclient.exceptions.OverLimit: Request is too large. Larger than max_request_body_size (114688). 2023-02-10 18:07:19.913 1651 ERROR oslo_messaging.rpc.server [-] Exception during message handling: trove.common.exception.TroveError: Failed to create server for instance 58558983-e67e-465d-894f-456b118ff555 Request is too large. Larger than max_request_body_size (114688). Can you help me? I don't know where I change this parameter... Have a good weekend for us! -- Att, Jorge Visentini +55 55 98432-9868

2 1

[all][tc] What's happening in Technical Committee: summary 2023 Feb 10: Reading: 5 min
by Ghanshyam Mann 11 Feb '23

11 Feb '23

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Feb 8. Most of the meeting discussions are summarized in this email. The meeting logs are available @ https://meetings.opendev.org/meetings/tc/2023/tc.2023-02-08-16.00.log.html * The next TC weekly meeting will be on Feb 15 Wed at 16:00 UTC, Feel free to add the topic to the agenda[1] by Feb 14. 2. What we completed this week: ========================= * Defined 2023.2 cycle testing runtime[2] I have pushed the job template change which needs to wait until 2023.1 release[3] 3. Activities In progress: ================== TC Tracker for the 2023.1 cycle ------------------------------------- * Current cycle working items and their progress are present in the 2023.1 tracker etherpad[4]. Open Reviews ----------------- * Six open reviews for ongoing activities[5]. OpenInfra Board + OpenStack Syncup Call -------------------------------------------------- We continued the sync-up call with Board members on Feb 8[6]. We continued the discussion from the previous meeting on below two topics: 1. Renovate translation SIG i18 Brian gave the updates on this and weblate license is purchased. There is a discussion going on about hosting the service. Another thing pending on this is to find the maintainer to help in weblate hosting and translation work. Brian will discuss it with Ian and Seongsoo about it. 2. Less Diversity (of organization contributing to OpenStack) This was continued to know if there is any actual progress to solve this problem. We always discuss spreading the word about benefits to the community and hope more companies will come forward for help. We are still facing less diversity from organizations involved in upstream activities. Many projects are/will face a single company maintaining them and will end up on retirement if that company changes their plan. TripelO is a recent example of it. Proposal was to Guidelines for using the OpenStack/project release version/name in 1. releasenotes 2. Documentation ------------------------------------------------------------------------------------------------------------------------- As discussed in the last vPTG, there was some confusion about using the OpenStack release name or version and project version in release notes and documentation. Slawek proposed guidelines about it[7] which is up fore review. Defining 2023 upstream investment opportunities ------------------------------------------------------------ Every calendar year, TC defines the upstream investment opportunities where we need help and the organization can help. I have pushed the patch[8] to define the 2023 calendar year which is nothing but continuing last year's opportunities. Please let TC know if any of the areas/projects you think need help and should be added to this list. Cleanup of PyPI maintainer list for OpenStack Projects ---------------------------------------------------------------- The audit process is going on and a few projects have been completed [9]. There is a discussion also going on in ML[10]. JayF is working on an email template which can be used to communicate to additional developers to transfer the ownership to 'openstackci' account and remove them from the maintainer's list. The process to find the less active projects early in the cycle: ------------------------------------------------------------------------ No update this week. JayF started the etherpad to collect the data and define the criteria to help in this process[11]. Project updates ------------------- * Add Cinder Huawei charm[12] * Add the woodpecker charm to Openstack charms[13] * Retire xstatic-font-awesome[14] * mistral adopting PTL model[15] 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[16]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15:00 UTC [17] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Agenda_Suggesti… [2] https://review.opendev.org/c/openstack/governance/+/872232 [3] https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/873051 [4] https://etherpad.opendev.org/p/tc-2023.1-tracker [5] https://review.opendev.org/q/projects:openstack/governance+status:open [6] https://etherpad.opendev.org/p/2023-02-board-openstack-sync [7] https://review.opendev.org/c/openstack/governance/+/872769 [8] https://review.opendev.org/c/openstack/governance/+/872233 [9] https://etherpad.opendev.org/p/openstack-pypi-maintainers-cleanup [10] https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031848… [11] https://etherpad.opendev.org/p/project-health-check [12] https://review.opendev.org/c/openstack/governance/+/867588 [13] https://review.opendev.org/c/openstack/governance/+/869752 [14] https://review.opendev.org/c/openstack/governance/+/872837 [15] https://review.opendev.org/c/openstack/governance/+/873260 [16] hhttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [17] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

Trove configuration - Larger than max_request_body_size
by Jorge Visentini 11 Feb '23

11 Feb '23

Hi all. I'm noob in Openstack, so I'm testing/studying the features. At the moment I am testing the Trove but I can't start a database instance... This error appears for me. 2023-02-10 18:07:19.888 1651 ERROR trove.taskmanager.models [-] Failed to create server for instance 58558983-e67e-465d-894f-456b118ff555 *Request is too large. Larger than max_request_body_size (114688). * (HTTP 413) (Request-ID: req-7993a97f-0738-4edf-aa6c-0c4c37f609c5) Traceback (most recent call last): File "/usr/lib/python3.9/site-packages/trove/taskmanager/models.py", line 844, in _create_server_volume server = self._create_server( File "/usr/lib/python3.9/site-packages/trove/taskmanager/models.py", line 999, in _create_server server = self.nova_client.servers.create( File "/usr/lib/python3.9/site-packages/novaclient/v2/servers.py", line 1562, in create return self._boot(response_key, *boot_args, **boot_kwargs) File "/usr/lib/python3.9/site-packages/novaclient/v2/servers.py", line 887, in _boot return self._create('/servers', body, response_key, File "/usr/lib/python3.9/site-packages/novaclient/base.py", line 363, in _create resp, body = self.api.client.post(url, body=body) File "/usr/lib/python3.9/site-packages/keystoneauth1/adapter.py", line 401, in post return self.request(url, 'POST', **kwargs) File "/usr/lib/python3.9/site-packages/novaclient/client.py", line 78, in request raise exceptions.from_response(resp, body, url, method) novaclient.exceptions.OverLimit: Request is too large. Larger than max_request_body_size (114688). (HTTP 413) (Request-ID: req-7993a97f-0738-4edf-aa6c-0c4c37f609c5) : novaclient.exceptions.OverLimit: Request is too large. Larger than max_request_body_size (114688). 2023-02-10 18:07:19.913 1651 ERROR oslo_messaging.rpc.server [-] Exception during message handling: trove.common.exception.TroveError: Failed to create server for instance 58558983-e67e-465d-894f-456b118ff555 Request is too large. Larger than max_request_body_size (114688). Can you help me? I don't know where I change this parameter... Have a good weekend for us! -- Att, Jorge Visentini +55 55 98432-9868

1 0

[neutron][releases] Issue with neutron-tempest-plugin in T, U and V
by Rodolfo Alonso Hernandez 10 Feb '23

10 Feb '23

Hello: I've started to see an error in the neutron-tempest-plugin job executions, in T, U and V. The hash used for these versions is the same [1]. This has been marked as the last version of this project in these releases. However I found [2] today. The library "guestmount" seems to be not present in Ubuntu 20.04 and we need to install it. That was done in [3] and is present in newer releases. My question here is: how do I push a patch for these versions (tag=1.6.0) and release a 2nd "last" version (if possible)? Thanks in advance. U and V last release: https://review.opendev.org/c/openstack/releases/+/864342 T last release: da9745f8b12dcb7e6f52d9ee868bc402cb44055e [1]https://paste.opendev.org/show/bkKq38Moq2qBXwpr4vSv/ [2]https://bugs.launchpad.net/neutron/+bug/2006763 [3]https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/813195

3 5

[election][ptl][tacker] PTL Candidacy for 2023.2 (Bobcat)
by Yasufumi Ogawa 10 Feb '23

10 Feb '23

Hi, I'd like to propose my candidacy for Tacker PTL for Bobcat cycle. I have been a Tacker's PTL since Victoria and mainly contributed to provide the latest features of ETSI-NVF standard features to enable operators to deploy their services. As Tacker team, we have focused on introducing container management support while revising the standard features to follow the latest API specifications. Our interest has been shifting to more practical usecases such as providing 5GC services with VRAN features on Tacker and OpenStack. I'd like to make a progress for expanding these usecases required by operators in the next cycle. Regards, Yasufumi (yasufum)

1 0

[heat][release] Proposing to EOL Train, Ussuri and Victoria
by Brendan Shephard 10 Feb '23

10 Feb '23

Hi folks, We’re looking to move Train, Ussuri and Victoria branches to EOL for Heat projects. Just reaching out to see if there are any objections, if I don’t hear anything back I’ll move forward with that this week. Cheers, Brendan Shephard Senior Software Engineer Red Hat Australia

2 3

[release] Release countdown for week R-5, Feb 13-17
by Thierry Carrez 10 Feb '23

10 Feb '23

Development Focus ----------------- We are getting close to the end of the 2023.1 Antelope cycle! Next week on February 16 is the Antelope-3 milestone, also known as feature freeze. It's time to wrap up feature work in the services and their client libraries, and defer features that won't make it to the 2023.2 Bobcat cycle. General Information ------------------- This coming week is the deadline for client libraries: their last feature release needs to happen before "Client library freeze" on February 16. Only bugfix releases will be allowed beyond this point. When requesting those library releases, you can also include the stable/2023.1 branching request with the review. As an example, see the "branches" section here: https://opendev.org/openstack/releases/src/branch/master/deliverables/pike/… February 16 is also the deadline for feature work in all OpenStack deliverables following the cycle-with-rc model. To help those projects produce a first release candidate in time, only bugfixes should be allowed in the master branch beyond this point. Any feature work past that deadline has to be raised as a Feature Freeze Exception (FFE) and approved by the team PTL. Finally, feature freeze is also a good time for submitting a first version of your cycle-highlights, ahead of the deadline on February 23. Cycle highlights are the raw data that helps shape what is communicated in press releases and other release activity at the end of the cycle, avoiding direct contacts from marketing folks. See https://docs.openstack.org/project-team-guide/release-management.html#cycle… for more details. Upcoming Deadlines & Dates -------------------------- Early bird deadline for OpenInfra Summit registration: February 15 Antelope-3 milestone (feature freeze): February 16 (R-5 week) Cycle Highlights Due: February 23 (R-4 week) RC1 deadline: March 2 (R-3 week) Final RC deadline: March 16 (R-1 week) Final 2023.1 Antelope release: March 22 Virtual PTG: March 27-31 -- Thierry Carrez (ttx)

1 0