- openstack-discuss - lists.openstack.org

[openstack-ansible] release job failure for ansible-collections-openstack
by Előd Illés 16 Nov '21

16 Nov '21

Hi Openstack-Ansible team! This mail is just to inform you that there was a release job failure [1] yesterday and the job could not be re-run as part of the job was finished successfully in the 1st run (so the 2nd attempt failed [2]). Could you please review if everything is OK with the release? Thanks, Előd (elodilles @ #openstack-release) [1] http://lists.openstack.org/pipermail/release-job-failures/2021-November/001… [2] http://lists.openstack.org/pipermail/release-job-failures/2021-November/001…

5 5

[neutron] CI meeting - agenda for 16.11.2021
by Slawek Kaplonski 16 Nov '21

16 Nov '21

Hi, Just quick reminder for those interested in the Neutron CI. Today at 1500 UTC we will have our weekly meeting. Agenda for the meeting is in the etherpad: [1]. This week's meeting will be also on the meetpad [2]. See You all there :) [1] https://etherpad.opendev.org/p/neutron-ci-meetings [2] https://meetpad.opendev.org/neutron-ci-meetings -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

error "haproxy[]: proxy horizon has no server available!" when internal tls is activated
by alex souppart 16 Nov '21

16 Nov '21

Hello, I try to deploy an overcloud openstack in victoria version. My configuration to deploy is : openstack overcloud deploy --templates -r /home/stack/templates/roles_data.yaml \ -n /home/stack/network_data.yaml \ -e /home/stack/templates/scheduler_hints_env.yaml \ -e /home/stack/templates/network-isolation.yaml \ -e /home/stack/templates/os-net-config-mapping.yaml \ -e /home/stack/templates/node-info.yaml \ -e /home/stack/containers-prepare-parameter.yaml \ -e /home/stack/templates/host-map.yaml \ -e /home/stack/templates/ips-from-pool-all.yaml \ -e /home/stack/templates/network-environment.yaml \ -e /home/stack/templates/net-multiple-nics-vlans.yaml \ -e /home/stack/templates/ceph-ansible-external.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/ssl/enable-internal-tls.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/services/haproxy-internal-tls-certmonger.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/ssl/tls-endpoints-public-ip.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/services/octavia.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/ssl/tls-everywhere-endpoints-dns.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/disable-telemetry.yaml \ -e /home/stack/templates/tls-parameters.yaml \ -e /home/stack/templates/inject-trust-anchor.yaml \ The generated configuration of horizon httpd contains SSLVerifyClient. But Haproxy fails to check server available, because haproxy does not send a client certificate when check attempt. the generated configuration of haproxy backend is : server host1 ip_host1:5000 ca-file /etc/ipa/ca.crt check fall 5 inter 2000 rise 2 ssl verify required verifyhost host1 server host2 ip_host2:5000 ca-file /etc/ipa/ca.crt check fall 5 inter 2000 rise 2 ssl verify required verifyhost host2 server host3 ip_host3:5000 ca-file /etc/ipa/ca.crt check fall 5 inter 2000 rise 2 ssl verify required verifyhost host3 if i try adding manualy "crt /etc/pki/tls/certs/haproxy/overcloud-haproxy-internal_api.pem" in server configuration in haproxy.conf, horizon/dashboard works via haproxy. But i'm not sure that's the right way. Did I forget an environment file in deploy configuration ? Thank you in advance for your assistance with this. Best regards Souppart Alexandre

1 0

[openstack-helm] No meeting tomorrow
by Gage Hugo 15 Nov '21

15 Nov '21

Hey team, Since there are no agenda items [0] for the IRC meeting tomorrow, the meeting is cancelled. Our next meeting will be November 23rd. Thanks [0] https://etherpad.opendev.org/p/openstack-helm-weekly-meeting

1 0

Adjutant needs contributors (and a PTL) to survive!
by Adrian Turjak 15 Nov '21

15 Nov '21

Hello fellow OpenStackers! I'm moving on to a different opportunity and my new role will not involve OpenStack, and there sadly isn't anyone at Catalystcloud who will be able to take over project responsibilities for Adjutant any time soon (not that I've been very onto it lately). As such Adjutant needs people to take over, and lead it going forward. I believe the codebase is in a reasonably good position for others to pick up, and I plan to go through and document a few more of my ideas for where it should go in storyboard so some of those plans exist somewhere should people want to pick up from where I left off before going fairly silent upstream. Plus if people want/need to they can reach out to me or add me to code review and chances are I'll comment/review because I do care about the project. Or I may contract some time to it. There are a few clouds running Adjutant, and people who have previously expressed interest in using it, so if you still are, the project isn't in a bad place at all. The code is stable, and the last few major refactors have cleaned up much of my biggest pain points with it. Best of luck! - adriant

5 6

[all][tc] Canceling Technical Committee 18th Nov weekly meeting
by Ghanshyam Mann 15 Nov '21

15 Nov '21

Hello Everyone, Due to OpenInfra Keynotes happening on 17-18 Nov, this week (18th Nov) TC meeting is cancelled. -gmann

1 0

[Openstack][cinder] scheduler filters
by Ignazio Cassano 15 Nov '21

15 Nov '21

Hello All, I read that capacity filters for cinder is the default, so, if I understood well, a volume is placed on the backend where more space is available. Since my two backends are on storage with same features, I wonder if I must specify a default storage backend in cinder.conf or not. Must I create a cinder volume without cinder type and scheduler evaluate where there is more space available? Thanks Ignazio

2 3

[Nova] - OS_TYPE - Setting after the fact.
by Steven Relf 15 Nov '21

15 Nov '21

Hello List, I have the following situation and would be thankful for any help or suggestions. We provide images to our customers, upon which we set the os_type metadata. We use this to help schedule instances to host aggregates, so we can control where certain OS's land. This works great for new instances, that are created from our images. We have the following problems though. 1. Instances created prior to the introduction of the os_type metadata existing on the image, this metadata is not flowed down, and as such these instances have NULL 2. Instances created from a snapshot do not seem to get the os_type flowed down 3. Instances imported using our migration tool do not end up with the os_type being set either. Currently the only way I can see to set os_type on an instance is to manually (yuk) update the database for each and every instance, which is missing it. Does anyone have any ideas how this can be updated without manually modifying the database. My second thought was to maybe make use of the instance metadata that you can set via the CLI or API, but then I run in to the issue that there is not a nova filter that is able to use instance metadata, and in my brief play with the code, it looks like (user) metadata is not passed in as part of the instance spec dict that is used to schedule instances. I was thinking of writing a custom filter, but I'm not sure how compliant it would be to have a function making a call to try and collect the instance metadata. In summary, I need to solve two things. 1. How do I set os_type on instances in a way that doesn't involve editing the database. 2. Or How can I use another piece of metadata that I can set via the api, which also is exposed to the filter scheduler. Rgds Steve. The future has already arrived. It's just not evenly distributed yet - William Gibson

2 3

[nova][placement] Spec review day on Nov 16th
by Sylvain Bauza 15 Nov '21

15 Nov '21

As agreed on our last Nova meeting [1], please sharpen your pen and prepare your specs ahead of time as we'll have a spec review day on Nov 16th Reminder: the idea of a spec review day is to ensure that contributors and reviewers are available on the same day for prioritizing Gerrit comments and IRC discussions about specs in order to facilitate and accelerate the reviewing of open specs. If you care about some fancy new feature, please make sure your spec is ready for review on time and you are somehow joinable so reviewers can ping you, or you are able to quickly reply on their comments and ideally propose a new revision if needed. Nova cores, I appreciate your dedication about specs on this particular day. -Sylvain [1] https://meetings.opendev.org/meetings/nova/2021/nova.2021-11-02-16.00.log.h…

1 1

[all] Openstack CI Log Processing project
by Daniel Pawlik 15 Nov '21

15 Nov '21

Hello Everyone, By moving the Opendev Elasticsearch to Openstack Elasticsearch service (in the future), a new repository was created in the Openstack project: ci-log-processing. The new repository will be used to store configuration related to the Opensearch service and all tools required to process logs from Zuul CI system to Opensearch. By moving to the new Elasticsearch system, we would like to take this opportunity to use a new service to replace the legacy submit-logstash-jobs system [1][2]. I would like to ask for volunteers to review changes in the Openstack ci-log-processing repository? [3] Please reply to this ML or ping me on #openstack-infra IRC channel so that we can plan to expand the core member list of this repo. Dan [1] https://opendev.org/opendev/base-jobs/src/branch/master/roles/submit-logsta… [2] https://docs.opendev.org/opendev/system-config/latest/logstash.html [3] https://review.opendev.org/q/project:openstack%252Fci-log-processing+status…

4 3

[neutron] Bug deputy report - week of November 8th
by Slawek Kaplonski 15 Nov '21

15 Nov '21

Hi, I was bug deputy last week. Here is the list of new issues opened in Neutron: ## Critical * https://bugs.launchpad.net/neutron/+bug/1950275 - openstack-tox-py36-with- neutron-lib-master job is failing since 05.11.2021 - gate failure in periodic job, Lajos is working on that, * https://bugs.launchpad.net/neutron/+bug/1950346 - [stable/train] neutron- tempest-plugin-designate-scenario-train fails with AttributeError: 'Manager' object has no attribute 'zones_client' - gate failure, in progress, assigned to Lajos, * https://bugs.launchpad.net/neutron/+bug/1950795 - neutron-tempest-plugin- scenario jobs on stable/rocky and stable/queens are failing with POST_FAILURE every time - assigned to slaweq ## High * https://bugs.launchpad.net/neutron/+bug/1950273 - Error 500 during log update - unassigned, happened in the CI, ovn related * https://bugs.launchpad.net/neutron/+bug/1950679 - [ovn] neutron_ovn_db_sync_util hangs on sync_routers_and_rports - Assigned to Daniel Speichert, fix in progress https://review.opendev.org/c/openstack/neutron/+/ 817637 ## Medium * https://bugs.launchpad.net/neutron/+bug/1950686 - [OVN] dns- nameserver=0.0.0.0 for a subnet isn't treated properly - unassigned, ovn related * https://bugs.launchpad.net/neutron/+bug/1899207 - [OVN][Docs] admin/config- dns-res.html should be updated for OVN - unassinged, docs bug, ovn related ## Low * https://bugs.launchpad.net/neutron/+bug/1950662 - [DHCP] Improve RPC server methods - assigned to ralonsoh, fix proposed https://review.opendev.org/c/ openstack/neutron/+/816850 ## Whishlist (RFEs) * https://bugs.launchpad.net/neutron/+bug/1950454 - [RFE] GW IP and FIP QoS to inherit from network - assigned to ralonsoh -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[neutron] CI meeting time slot
by Slawek Kaplonski 15 Nov '21

15 Nov '21

Hi, As per PTG discussion, I prepared doodle to check what would be the best time slot for most of the people. Doodle is at [1]. Please fill it in if You are interested attending the weekly Neutron CI meeting. Meeting is on the #openstack-neutron irc channel, but we are also planning to do it on video from time to time. The timeslots in doodle have dates for next week, but please ignore them. It's just to pick the best time slot for the meeting to use it weekly. Next week meeting will be for sure still in the current time slot, which is Tuesday 1500 UTC. [1] https://doodle.com/poll/3n2im4ebyxhs45ne?utm_source=poll&utm_medium=link -- Slawek Kaplonski Principal Software Engineer Red Hat

1 1

[barbican][sdk] Barbican's quota API is missing CLI support?
by Jordan Ansell 14 Nov '21

14 Nov '21

Hello, I was wondering why the quota API for Barbican doesn't have a CLI command in python-barbicanclient? Thanks, Jordan Ansell

1 0

[all][tc] What's happening in Technical Committee: summary 12th Nov, 21: Reading: 10 min
by Ghanshyam Mann 12 Nov '21

12 Nov '21

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * TC this week IRC meeting held on Nov 11th Thursday. * 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/2021/tc.2021-11-11-15.00.log.html * Next week's meeting is canceled due to OpenInfra Keynotes and we will continue weekly meeting on 25th Nov, Thursday 15:00 UTC, feel free the topic on agenda[1] by Nov 24th. 2. What we completed this week: ========================= * Changes in stable core team process[2] * Decouple the community-wide goals from cycle release[3] (I will write up summary on this once we have RBAC goal merged as an example) * Merged 'Technical Writing' SIG into TC[4] 3. Activities In progress: ================== TC Tracker for Yoga cycle ------------------------------ * This etherpad includes the Yoga cycle targets/working items for TC[5]. Open Reviews ----------------- * 12 open reviews for ongoing activities[6]. Review volunteer required for Openstack CI Log Processing project -------------------------------------------------------------------------------- dpawlik sent the email on openstack-discuss[7] about seeking help to review on new Openstack CI Log Processing project. Please respond there if you can help at some extent even not as full time. Remove office hours in favor of weekly meetings ----------------------------------------------------------- We decided to remove the TC in-active office hours[8] in favor of weekly meetings which are serving the purpose of office hours. RBAC discussion: continuing from PTG ---------------------------------------------- We had a discussion on Wed 10th too and agreed on what all we can target for Yoga cycle. Complete notes are in this etherpad[9]. Please review the goal rework[10]. Discussion on open items will be continued in policy popup team meeting[11] Community-wide goal updates ------------------------------------ * With the continuing the discussion on RBAC, we are re-working on the RBAC goal, please wait until we finalize the implementation[8] * There is one more goal proposal for 'FIPS compatibility and compliance'[12]. Adjutant need maintainers and PTLs ------------------------------------------- No volunteer to lead/maintain the Adjutant project, I have sent another reminder to the email[13]. New project 'Skyline' proposal ------------------------------------ * We discussed it in TC PTG and there are few open points about python packaging, repos, and plugins plan which we are discussion on ML. * Still waiting from skyline team to work on the above points[14]. Updating the Yoga testing runtime ---------------------------------------- * As centos stream 9 is released, I have updated the Yoga testing runtime[15] with: 1. Add Debian 11 as tested distro 2. Change centos stream 8 -> centos stream 9 3. Bump lowest python version to test to 3.8 and highest to python 3.9 TC tags analysis ------------------- * TC agreed to remove the framework and it is communicated in ML[16]. Project updates ------------------- * Rename ‘Extended Maintenance’ SIG to the ‘Stable Maintenance’[17] * Retire training-labs repo[18] * Retire puppet-senlin[19] * Add ProxySQL repository for OpenStack-Ansible[20] * Retire js-openstack-lib [21] 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[22]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [23] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025741… [3] https://review.opendev.org/c/openstack/governance/+/816387 [4] https://review.opendev.org/c/openstack/governance/+/815869 [5] https://etherpad.opendev.org/p/tc-yoga-tracker [6] https://review.opendev.org/q/projects:openstack/governance+status:open [7] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025758… [8] https://review.opendev.org/c/openstack/governance/+/817493 [9] https://etherpad.opendev.org/p/policy-popup-yoga-ptg [10] https://review.opendev.org/c/openstack/governance/+/815158 [11] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025760… [12] https://review.opendev.org/c/openstack/governance/+/816587 [13] http://lists.openstack.org/pipermail/openstack-discuss/2021-October/025555.… [14] https://review.opendev.org/c/openstack/governance/+/814037 [15] https://review.opendev.org/c/openstack/governance/+/815851 [16] http://lists.openstack.org/pipermail/openstack-discuss/2021-October/025571.… [17] https://review.opendev.org/c/openstack/governance-sigs/+/817499 [18] https://review.opendev.org/c/openstack/governance/+/817511 [19] https://review.opendev.org/c/openstack/governance/+/817329 [20] https://review.opendev.org/c/openstack/governance/+/817245 [21] https://review.opendev.org/c/openstack/governance/+/807163 [22] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [23] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[all][tc][policy] RBAC discussions: policy popup team meeting time/place change
by Ghanshyam Mann 12 Nov '21

12 Nov '21

Hello Everyone, As you might aware that we had post-PTG discussion on new secure RBAC[1] and figured out a lot of things but still lot of things pending to figure out :). We are at least in good shape on "what to target in Yoga cycle" (this proposal - https://review.opendev.org/c/openstack/governance/+/815158) We will use policy popup team biweekly meeting to continue the discussion on open questions and with video call on meetpad. Details of meeting: https://wiki.openstack.org/wiki/Consistent_and_Secure_Default_Policies_Popu… Ical: https://meetings.opendev.org/#Secure_Default_Policies_Popup-Team_Meeting Next meeting is on 18th Nov Thursday at 18:00 UTC and then biweekly. [1] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025619… -gmann

1 0

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

12 Nov '21

Development Focus ----------------- The Yoga-1 milestone is next week, on November 18, 2021! Project team plans for the Yogacycle should now be solidified. General Information ------------------- Libraries need to be released at least once per milestone period. Next week, the release team will propose releases for any library which had changes but has not been otherwise released since the Xenarelease. PTL's or release liaisons, please watch for these and give a +1 to acknowledge them. If there is some reason to hold off on a release, let us know that as well, by posting a -1. If we do not hear anything at all by the end of the week, we will assume things are OK to proceed. NB: If one of your libraries is still releasing 0.x versions, start thinking about when it will be appropriate to do a 1.0 version. The version number does signal the state, real or perceived, of the library, so we strongly encourage going to a full major version once things are in a good and usable state. Upcoming Deadlines & Dates -------------------------- Yoga-1 milestone: November 18, 2021 Yoga final release: March 30, 2022 Előd Illés irc: elodilles

1 0

[ops][keystone][cinder][swift][neutron][nova] Rename Availability Zone
by DHilsbos＠performair.com 12 Nov '21

12 Nov '21

All; We recently decided to change our naming convention. As such I'd like to rename our current availability zone. The configuration files are the obvious places to do so. Is there anything I need to change in the database? Properties of images, volumes, servers, etc.? Should I just give this up as a bad deal? Maybe rebuild the cluster from scratch? Thank you, Dominic L. Hilsbos, MBA Vice President - Information Technology Perform Air International Inc. DHilsbos(a)PerformAir.com www.PerformAir.com

2 1

[neutron] openflow rules tools
by Arnaud Morin 12 Nov '21

12 Nov '21

Hello, When using native ovs in neutron, we endup with a lot of openflow rules on ovs side. Debugging it with regular ovs-ofctl --color dump-flows is kind of painful. Is there any tool that the community is using to manage that? Thanks in advance! Arnaud.

5 5

[ops][nova] Error trying to migrate
by DHilsbos＠performair.com 11 Nov '21

11 Nov '21

All; I'm running into a strange issue when I try to migrate a server from one host to another. The only messages I'm seeing are in nova-conductor.log: 2021-11-11 15:16:49.118 1887742 WARNING nova.scheduler.utils [req-d648901b-d000-47ec-9497-bcc51586c381 d7c514813e5d4fe6815f5f59e8e35f2f a008ad02d16f436a9e320882ca497055 - default default] Failed to compute_task_migrate_server: Timed out waiting for a reply to message ID 237323d0824a43588f6394e5a505248b: oslo_messaging.exceptions.MessagingTimeout: Timed out waiting for a reply to message ID 237323d0824a43588f6394e5a505248b 2021-11-11 15:16:49.122 1887742 WARNING nova.scheduler.utils [req-d648901b-d000-47ec-9497-bcc51586c381 d7c514813e5d4fe6815f5f59e8e35f2f a008ad02d16f436a9e320882ca497055 - default default] [instance: 5935c07d-0c7f-48cc-a4b9-674504fc6005] Setting instance to STOPPED state.: oslo_messaging.exceptions.MessagingTimeout: Timed out waiting for a reply to message ID 237323d0824a43588f6394e5a505248b 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server [req-d648901b-d000-47ec-9497-bcc51586c381 d7c514813e5d4fe6815f5f59e8e35f2f a008ad02d16f436a9e320882ca497055 - default default] Exception during message handling: oslo_messaging.exceptions.MessagingTimeout: Timed out waiting for a reply to message ID 237323d0824a43588f6394e5a505248b 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server Traceback (most recent call last): 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 433, in get 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server return self._queues[msg_id].get(block=True, timeout=timeout) 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/eventlet/queue.py", line 322, in get 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server return waiter.wait() 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/eventlet/queue.py", line 141, in wait 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server return get_hub().switch() 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/eventlet/hubs/hub.py", line 298, in switch 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server return self.greenlet.switch() 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server queue.Empty 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server During handling of the above exception, another exception occurred: 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server Traceback (most recent call last): 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_messaging/rpc/server.py", line 165, in _process_incoming 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server res = self.dispatcher.dispatch(message) 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_messaging/rpc/dispatcher.py", line 309, in dispatch 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server return self._do_dispatch(endpoint, method, ctxt, args) 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_messaging/rpc/dispatcher.py", line 229, in _do_dispatch 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server result = func(ctxt, **new_args) 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_messaging/rpc/server.py", line 241, in inner 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server return func(*args, **kwargs) 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/nova/conductor/manager.py", line 99, in wrapper 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server return fn(self, context, *args, **kwargs) 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/nova/compute/utils.py", line 1434, in decorated_function 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server return function(self, context, *args, **kwargs) 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/nova/conductor/manager.py", line 303, in migrate_server 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server host_list) 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/nova/conductor/manager.py", line 397, in _cold_migrate 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server else 'cold migrate', instance=instance) 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_utils/excutils.py", line 220, in __exit__ 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server self.force_reraise() 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_utils/excutils.py", line 196, in force_reraise 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server six.reraise(self.type_, self.value, self.tb) 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/six.py", line 703, in reraise 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server raise value 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/nova/conductor/manager.py", line 354, in _cold_migrate 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server task.execute() 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/nova/conductor/tasks/base.py", line 26, in wrap 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server self.rollback(ex) 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_utils/excutils.py", line 220, in __exit__ 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server self.force_reraise() 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_utils/excutils.py", line 196, in force_reraise 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server six.reraise(self.type_, self.value, self.tb) 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/six.py", line 703, in reraise 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server raise value 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/nova/conductor/tasks/base.py", line 23, in wrap 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server return original(self) 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/nova/conductor/tasks/base.py", line 40, in execute 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server return self._execute() 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/nova/conductor/tasks/migrate.py", line 384, in _execute 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server selection = self._schedule() 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/nova/conductor/tasks/migrate.py", line 434, in _schedule 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server return_objects=True, return_alternates=True) 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/nova/scheduler/client/query.py", line 42, in select_destinations 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server instance_uuids, return_objects, return_alternates) 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/nova/scheduler/rpcapi.py", line 160, in select_destinations 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server return cctxt.call(ctxt, 'select_destinations', **msg_args) 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_messaging/rpc/client.py", line 179, in call 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server transport_options=self.transport_options) 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_messaging/transport.py", line 128, in _send 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server transport_options=transport_options) 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 682, in send 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server transport_options=transport_options) 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 670, in _send 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server call_monitor_timeout) 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 559, in wait 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server message = self.waiters.get(msg_id, timeout=timeout) 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 437, in get 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server 'to message ID %s' % msg_id) 2021-11-11 15:16:49.291 1887742 ERROR oslo_messaging.rpc.server oslo_messaging.exceptions.MessagingTimeout: Timed out waiting for a reply to message ID 237323d0824a43588f6394e5a505248b No messages are generated in nova-schedule, or any of the nova-compute logs on the hosts. Thank you, Dominic L. Hilsbos, MBA Vice President - Information Technology Perform Air International Inc. DHilsbos(a)PerformAir.com www.PerformAir.com

2 1

[TripleO] directord to opendev
by James Slagle 11 Nov '21

11 Nov '21

Hello TripleO'ers, We are proposing to move the directord repo[1] from github to opendev as a top level organization. Moving to the opendev[2] hosting will make it easier to integrate with the existing tripleo-core team, our existing CI, and developer processes. The benefits seem to outweigh leaving it on github. At the same time, we want to encourage external contribution from outside TripleO, so felt that making it it's own organization under opendev would be better suited towards that than under the openstack organization. If there are concerns, please raise them. Thank you! [1] https://github.com/Directord/ [2] https://opendev.org/ -- -- James Slagle --

1 1

[neutron] Drivers meeting agenda - 12.11.2021
by Lajos Katona 11 Nov '21

11 Nov '21

Hi Neutron Drivers, The agenda for tomorrow's drivers meeting is at [1]. We have 1 RFE to discuss: * https://bugs.launchpad.net/neutron/+bug/1950454 : [RFE] GW IP and FIP QoS to inherit from network [1] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers#Agenda See you at the meeting tomorrow. Lajos Katona (lajoskatona)

1 0

[Ussuri] [Zun] Container deployment problem with Zun "There are not enough hosts available"
by Pavlos Basaras 11 Nov '21

11 Nov '21

Hello, I have an Openstack cluster, with basic services and functionality working based on ussuri release. I am trying to install the Zun service to be able to deploy containers, following [controller] -- https://docs.openstack.org/zun/ussuri/install/controller-install.html and [compute] -- https://docs.openstack.org/zun/ussuri/install/compute-install.html I used the git branch based on ussuri for all components. I veryfined kuryr-libnetwork operation issuing from the compute node # docker network create --driver kuryr --ipam-driver kuryr --subnet 10.10.0.0/16 --gateway=10.10.0.1 test_net and seeing the network created successfully, etc. I am not very sure about the zun.conf file. What is the "endpoint_type = internalURL" parameter? Do I need to change internalURL? >From sudo systemctl status zun-compute i see: Nov 05 14:34:58 compute5 zun-compute[8962]: 2021-11-05 14:34:58.828 8962 ERROR oslo_service.periodic_task File "/usr/local/lib/python3.6/dist-packages/retrying.py", line 49, in wrapped_f Nov 05 14:34:58 compute5 zun-compute[8962]: 2021-11-05 14:34:58.828 8962 ERROR oslo_service.periodic_task return Retrying(*dargs, **dkw).call(f, *args, **kw) Nov 05 14:34:58 compute5 zun-compute[8962]: 2021-11-05 14:34:58.828 8962 ERROR oslo_service.periodic_task File "/usr/local/lib/python3.6/dist-packages/retrying.py", line 206, in call Nov 05 14:34:58 compute5 zun-compute[8962]: 2021-11-05 14:34:58.828 8962 ERROR oslo_service.periodic_task return attempt.get(self._wrap_exception) Nov 05 14:34:58 compute5 zun-compute[8962]: 2021-11-05 14:34:58.828 8962 ERROR oslo_service.periodic_task File "/usr/local/lib/python3.6/dist-packages/retrying.py", line 247, in get Nov 05 14:34:58 compute5 zun-compute[8962]: 2021-11-05 14:34:58.828 8962 ERROR oslo_service.periodic_task six.reraise(self.value[0], self.value[1], self.value[2]) Nov 05 14:34:58 compute5 zun-compute[8962]: 2021-11-05 14:34:58.828 8962 ERROR oslo_service.periodic_task File "/usr/lib/python3/dist-packages/six.py", line 703, in reraise Nov 05 14:34:58 compute5 zun-compute[8962]: 2021-11-05 14:34:58.828 8962 ERROR oslo_service.periodic_task raise value Nov 05 14:34:58 compute5 zun-compute[8962]: 2021-11-05 14:34:58.828 8962 ERROR oslo_service.periodic_task File "/usr/local/lib/python3.6/dist-packages/retrying.py", line 200, in call Nov 05 14:34:58 compute5 zun-compute[8962]: 2021-11-05 14:34:58.828 8962 ERROR oslo_service.periodic_task attempt = Attempt(fn(*args, **kwargs), attempt_number, False) Nov 05 14:34:58 compute5 zun-compute[8962]: 2021-11-05 14:34:58.828 8962 ERROR oslo_service.periodic_task File "/usr/local/lib/python3.6/dist-packages/zun/compute/compute_node_tracker.py", line 350, in _update_to_placement Nov 05 14:34:58 compute5 zun-compute[8962]: 2021-11-05 14:34:58.828 8962 ERROR oslo_service.periodic_task context, node_rp_uuid, name=compute_node.hostname) Nov 05 14:34:58 compute5 zun-compute[8962]: 2021-11-05 14:34:58.828 8962 ERROR oslo_service.periodic_task File "/usr/local/lib/python3.6/dist-packages/zun/scheduler/client/report.py", line 846, in get_provider_tree_and_ensure_r Nov 05 14:34:58 compute5 zun-compute[8962]: 2021-11-05 14:34:58.828 8962 ERROR oslo_service.periodic_task parent_provider_uuid=parent_provider_uuid) Nov 05 14:34:58 compute5 zun-compute[8962]: 2021-11-05 14:34:58.828 8962 ERROR oslo_service.periodic_task File "/usr/local/lib/python3.6/dist-packages/zun/scheduler/client/report.py", line 628, in _ensure_resource_provider Nov 05 14:34:58 compute5 zun-compute[8962]: 2021-11-05 14:34:58.828 8962 ERROR oslo_service.periodic_task parent_provider_uuid=parent_provider_uuid) Nov 05 14:34:58 compute5 zun-compute[8962]: 2021-11-05 14:34:58.828 8962 ERROR oslo_service.periodic_task File "/usr/local/lib/python3.6/dist-packages/zun/scheduler/client/report.py", line 514, in _create_resource_provider Nov 05 14:34:58 compute5 zun-compute[8962]: 2021-11-05 14:34:58.828 8962 ERROR oslo_service.periodic_task global_request_id=context.global_id) Nov 05 14:34:58 compute5 zun-compute[8962]: 2021-11-05 14:34:58.828 8962 ERROR oslo_service.periodic_task File "/usr/local/lib/python3.6/dist-packages/zun/scheduler/client/report.py", line 225, in post Nov 05 14:34:58 compute5 zun-compute[8962]: 2021-11-05 14:34:58.828 8962 ERROR oslo_service.periodic_task headers=headers, logger=LOG) Nov 05 14:34:58 compute5 zun-compute[8962]: 2021-11-05 14:34:58.828 8962 ERROR oslo_service.periodic_task File "/usr/lib/python3/dist-packages/keystoneauth1/adapter.py", line 392, in post Nov 05 14:34:58 compute5 zun-compute[8962]: 2021-11-05 14:34:58.828 8962 ERROR oslo_service.periodic_task return self.request(url, 'POST', **kwargs) Nov 05 14:34:58 compute5 zun-compute[8962]: 2021-11-05 14:34:58.828 8962 ERROR oslo_service.periodic_task File "/usr/lib/python3/dist-packages/keystoneauth1/adapter.py", line 248, in request Nov 05 14:34:58 compute5 zun-compute[8962]: 2021-11-05 14:34:58.828 8962 ERROR oslo_service.periodic_task return self.session.request(url, method, **kwargs) Nov 05 14:34:58 compute5 zun-compute[8962]: 2021-11-05 14:34:58.828 8962 ERROR oslo_service.periodic_task File "/usr/lib/python3/dist-packages/keystoneauth1/session.py", line 968, in request Nov 05 14:34:58 compute5 zun-compute[8962]: 2021-11-05 14:34:58.828 8962 ERROR oslo_service.periodic_task raise exceptions.from_response(resp, method, url) *Nov 05 14:34:58 compute5 zun-compute[8962]: 2021-11-05 14:34:58.828 8962 ERROR oslo_service.periodic_task keystoneauth1.exceptions.http.Conflict: Conflict (HTTP 409) (Request-ID: req-9a158c41-a485-4937-99e7-e38cdce7fded)* What is this problem? any advice? I used the default configuration values ([keystone_auth] and [keystone_authtoken]) values based on the configuration from the above links. Aslo from the controller *openstack appcontainer service list* +----+----------+-------------+-------+----------+-----------------+----------------------------+-------------------+ | Id | Host | Binary | State | Disabled | Disabled Reason | Updated At | Availability Zone | +----+----------+-------------+-------+----------+-----------------+----------------------------+-------------------+ | 1 | compute5 | zun-compute | up | False | None | 2021-11-05T14:39:01.000000 | nova | +----+----------+-------------+-------+----------+-----------------+----------------------------+-------------------+ *openstack appcontainer host show compute5* +----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Field | Value | +----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | uuid | ee3a5b44-8ffa-463e-939d-0c61868a596f | | links | [{'href': ' http://controller:9517/v1/hosts/ee3a5b44-8ffa-463e-939d-0c61868a596f', 'rel': 'self'}, {'href': ' http://controller:9517/hosts/ee3a5b44-8ffa-463e-939d-0c61868a596f', 'rel': 'bookmark'}] | | hostname | compute5 | | mem_total | 7975 | | mem_used | 0 | | total_containers | 1 | | cpus | 10 | | cpu_used | 0.0 | | architecture | x86_64 | | os_type | linux | | os | Ubuntu 18.04.6 LTS | | kernel_version | 4.15.0-161-generic | | labels | {} | | disk_total | 63 | | disk_used | 0 | | disk_quota_supported | False | | runtimes | ['io.containerd.runc.v2', 'io.containerd.runtime.v1.linux', 'runc'] | | enable_cpu_pinning | False | +----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ seems to work fine. However when i issue e.g., openstack appcontainer run --name container --net network=$NET_ID cirros ping 8.8.8.8 i get the error: | status_reason | There are not enough hosts available. Any ideas? One final thing is that I did see in the Horizon dashboard the container tab, to be able to deploy containers from horizon. Is there an extra configuration for this? sorry for the long mail. best, Pavlos

2 4

[all] Anyone use or would like to maintain openstack/training-labs repo
by Ghanshyam Mann 10 Nov '21

10 Nov '21

Hello Everyone, During the TC weekly meeting and PTG discussion to merge the 'Technical Writing' SIG into TC, we found that openstack/training-labs is no maintained now a days. Even we do not know who use this repo for training. I have checked that upstream institute training or CoA are not using this repo in their training. If you are using it for your training please reply to this email pr ping us on #openstack-tc IRC OFTC channel otherwise we will start the retirement process. - https://opendev.org/openstack/training-labs -gmann

1 1

[all] Stable Core Team Process changed
by Ghanshyam Mann 10 Nov '21

10 Nov '21

Hello Everyone, We discussed this in many PTG (Shanghai and in Xena) to decentralize the stable branch process and make it more distributed towards projects. The technical Committee has merged the resolution on this and I thought of putting it on ML in case you have not read it. With the new process, the individual project teams can manage their own stable core team in the same way that the regular core team. Also, project teams will be empowered to create/enforce polices that best meet the needs of that project. Existing stable policies stay valid and will serve the purpose as it is doing currently. And if you have any questions or seeking guidance regarding stable policies, you can reach out to the existing "Extended Maintenance" SIG which will be renamed to "Stable Maintenance". [1] https://governance.openstack.org/tc/resolutions/20210923-stable-core-team.h… -gmann

1 0

[all][tc] Technical Committee next weekly meeting on Nov 11th at 1500 UTC
by Ghanshyam Mann 10 Nov '21

10 Nov '21

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

1 1

[cinder][kolla][OSA][release] Xena cycle-trailing release deadline
by Előd Illés 10 Nov '21

10 Nov '21

Hello teams with deliverables following the cycle-trailing release model! This is just a reminder to wrap up your trailing deliverables for Xena. A few cycles ago the deadline for cycle-trailing projects was extended to give more time. The deadline for Xena is *16 December, 2021* [1]. If things are ready sooner than that though, all the better for our downstream consumers. For reference, the following cycle-trailing deliverables will need final releases at some point until the above deadline: cinderlib kayobe kolla-ansible kolla openstack-ansible-roles openstack-ansible Thanks! Előd Illés irc: elodilles [1] https://releases.openstack.org/yoga/schedule.html#y-cycle-trail

2 1

[largescale-sig] Next meeting: Nov 10th, 15utc
by Thierry Carrez 10 Nov '21

10 Nov '21

Hi everyone, The Large Scale SIG meeting is back this Wednesday in #openstack-operators on OFTC IRC, at 15UTC. It will be chaired by Belmiro Moreira. You can doublecheck how that time translates locally at: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20211110T15 Feel free to add topics to our agenda at: https://etherpad.openstack.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez

2 1

[all][tc] Continuing the RBAC PTG discussion
by Ghanshyam Mann 10 Nov '21

10 Nov '21

Hello Everyone, As decided in PTG, we will continue the RBAC discussion from where we left in PTG. We will have a video call next week based on the availability of most of the interested members. Please vote your available time in below doodle vote by Thursday (or Friday morning central time). - https://doodle.com/poll/6xicntb9tu657nz7 NOTE: this is not specific to TC or people working in RBAC work but more to wider community to get feedback and finalize the direction (like what we did in PTG session). Meanwhile, feel free to review the lance's updated proposal for community-wide goal - https://review.opendev.org/c/openstack/governance/+/815158 -gmann

1 3

[cinder] Bug deputy report for week of 11-10-2021
by Sofia Enriquez 10 Nov '21

10 Nov '21

This is a bug report from 10-03-2021 to 11-10-2021. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Medium - https://bugs.launchpad.net/cinder/+bug/1950291 tempest-integrated-compute-centos-8-stream fails with version conflict in boto. Unassigned. Incomplete - https://bugs.launchpad.net/cinder/+bug/1950134 InstanceLocality filter use results in AttributeError: 'Client' object has no attribute 'list_extensions'. Unassigned. Invalid - https://bugs.launchpad.net/cinder/+bug/1950128 NFS backend initialisation fails because an immutable directory exists. Unassigned. -- 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

OVN with SSL
by nabeel.tariq＠rapidcompute.com 10 Nov '21

10 Nov '21

Hi, We have configured OVN with SSL which is working while using SSL from third party. When we implement self-signed certificate, it shows certificate verification failed in logs. ERROR LOG: 2021-11-10 10:11:14.703 88854 ERROR neutron.service OpenSSL.SSL.Error: [('SSL routines', 'tls_process_server_certificate', 'certificate verify failed')] By using openssl verify command selfsigned server is showing verified. openssl verify -verbose -CAfile <self-signed-cacertificate>.pem <main>.crt

1 0

[sdk]: Get server fault message
by dmeng 10 Nov '21

10 Nov '21

Hello there, Hope everything is going well. I'm wondering if there is any method that could show the error message of a server whose status is "ERROR"? Like from openstack cli, "openstack server show server_name", if the server is in "ERROR" status, this will return a field "fault" with a message shows the error. I tried the compute service get_server and find_server, but neither of them show the error messages. Thanks and have a great day! Catherine

2 1

[puppet] Propose retiring puppet-senlin
by Takashi Kajinami 09 Nov '21

09 Nov '21

Hello, I remember I raised a similar discussion recently[1] but we need the same for a different module. puppet-selin was introduced back in 2018, but the module has had only the portion made by cookiecutter and has no capability to manage fundamental resources yet. Because we haven't seen any interest in creating implementations to support even basic usage, I'll propose retiring this module. I'll be open for any feedback for a while, and will propose a series of patches for retirement if no concern is raised here for one week. Thank you, Takashi [1] http://lists.openstack.org/pipermail/openstack-discuss/2021-September/02468… [2] https://opendev.org/openstack/puppet-senlin

2 2

[keystone] failed auth takes a while
by Tony Liu 09 Nov '21

09 Nov '21

Hi, I am using Keystone 17.0.0 with Ussuri. When issue a request by openstack cli (eg. network list) with wrong password, it takes 1+ minute to get auth failure 401 back. After correct the password, for the first request, it still takes 1+ minute to return success. After that, all following request is as fast as usual, around 1s. "openstack user password set" also takes that much time to return success. Any clues? Thanks! Tony

1 0

[qa] Moving office hour one hour later
by Martin Kopec 09 Nov '21

09 Nov '21

Hi everyone, we have decided to move the weekly office hour (held on Tuesdays) one later to 15:00 UTC effective November 16th [1]. It was discussed during our last office hour [2]. [1] https://review.opendev.org/c/opendev/irc-meetings/+/817224 [2] https://meetings.opendev.org/meetings/qa/2021/qa.2021-11-09-14.00.log.html#… Regards, -- Martin Kopec Senior Software Quality Engineer Red Hat EMEA

1 0

[openstack-helm] No meeting tomorrow
by Gage Hugo 08 Nov '21

08 Nov '21

Hey team, Since there are no agenda items [0] for the IRC meeting tomorrow, the meeting is cancelled. Our next meeting will be November 16th. Thanks [0] https://etherpad.opendev.org/p/openstack-helm-weekly-meeting

1 0

Opendaylight integration Openstack
by Hojii GZNI 08 Nov '21

08 Nov '21

Hi everyone I am trying to use Opendaylight as an Openstack SDN controller but have this error for "mechanism_dirver". Xena Ubuntu 20.04 Opendaylight 8 /etc/neutron/plugins/ml2/ml2_conf.ini mechanism_drivers = opendaylight Neutron server log: CRITICAL neutron.plugins.ml2.managers [-] The following mechanism drivers were not found: {'opendaylight'} All configuration is in my Github[1] Regards, Hojat. [1]: https://github.com/hojat-gazestani/openstack

2 1

OpenInfra Live - November 11 at 9am CT
by Ashlee Ferguson 08 Nov '21

08 Nov '21

Hi everyone, This week’s OpenInfra Live episode is brought to you by the OpenStack Community. The 2021 User Survey shows that the footprint of OpenStack clouds grew by 66% over the last year, totaling over 25 million cores in production. This increase has been contributed by organizations of all sizes around the world. During this episode of OpenInfra Live, we are going to talk to operators from Kakao, LINE, Schwarz IT, NeCTAR and T-Systems about what’s causing this OpenStack growth at their organization. Episode: OpenStack Is Alive: Explosive Growth Among Production Deployments Date and time: November 11 at 9am CT (1500 UTC) You can watch us live on: YouTube: https://www.youtube.com/watch?v=RhMJO82lDxc <https://www.youtube.com/watch?v=RhMJO82lDxc> LinkedIn: https://www.linkedin.com/feed/update/urn:li:ugcPost:6862068514526756864 <https://www.linkedin.com/feed/update/urn:li:ugcPost:6862068514526756864> Facebook: https://www.facebook.com/104139126308032/posts/4493822407339660/ <https://www.facebook.com/104139126308032/posts/4493822407339660/> WeChat: recording will be posted on OpenStack WeChat after the live stream Speakers: Paul Coddington (ARDC Nectar) Reedip Banerjee (LINE) Yushiro Furukawa (LINE) Andrew Kong (Kakao) Nils Magnus (T-Systems) Adrian Seiffert (Schwarz) Marvin Titus (Schwarz) Carmel Walsh (ARDC Nectar) Have an idea for a future episode? Share it now at ideas.openinfra.live <https://openinfrafoundation.formstack.com/forms/openinfralive>. Register now for OpenInfra Live: Keynotes, a special edition of OpenInfra Live on November 17-18th starting at 1500 UTC: https://openinfralivekeynotes.eventbrite.com/ Thanks, Ashlee OpenInfra Foundation Community & Events ashlee(a)openinfra.dev

1 0

[ironic] Proposing Aija Jauntēva for sushy-core
by Iury Gregory 08 Nov '21

08 Nov '21

Hello everyone! I would like to propose Aija Jauntēva (irc: ajya) to be added to the sushy-core group. Aija has been in the ironic community for a long time, she has a lot of knowledge about redfish and is always providing good reviews. ironic-cores please vote with +/- 1. -- *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>*

8 8

[neutron] Neutron drivers Meeting - vote on time of the meeting
by Lajos Katona 08 Nov '21

08 Nov '21

Hi Neutrinos, As we discussed during the PTG, let's start a poll to see which time fits best the need of the team for the Neutron drivers meeting. I prepared a doodle, please check which time slot would be best for you: https://doodle.com/poll/6vdugxp7g54smdv6?utm_source=poll&utm_medium=link The dates for the doodle now for next week, but please ignore that. Lajos Katona (lajoskatona)

1 0

[kuryr] Using kuryr-kubernetes CNI without neutron agent(s)?
by Jason Anderson 08 Nov '21

08 Nov '21

Hello all, I’m interested in letting Neutron provide the network configuration frontend for networks realized on k8s kubelets. I have been reading a lot about kuryr-kubernetes and it looks like it fits the bill, but some of the older architecture diagrams I’ve seen indicate that OVS and the neutron-openvswitch-agent (or similar) must also run on the kubelet node. Is this still accurate? I am hoping to avoid this because my understanding is that running the OVS agent means giving the kubelet node access to RabbitMQ and potentially storing admin keystone creds on the node as well. Can kuryr-kubernetes work without such an agent co-located? Thanks! Jason Anderson --- Chameleon DevOps Lead Department of Computer Science, University of Chicago Mathematics and Computer Science, Argonne National Laboratory

2 5

[neutron] Bug deputy report (week starting on 2021-11-01)
by Bernard Cafarelli 08 Nov '21

08 Nov '21

Hey neutrinos, Now that we are past the biannual DST calendar mess, it is also time for a new bug deputy rotation! Here is the list of bugs reported for last week, kudos to Rodolfo for both reporting most of them and also having a fix for them! All bugs have assignees, almost have patches and some are just waiting for CI Critical * "neutron-tempest-plugin-scenario-ovn" job timing out frequently - https://bugs.launchpad.net/neutron/+bug/1949557 Change merged increasing timeout by ralonsoh: https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/816438 * "openstack-tox-py38" CI job is timing out frequently in gate - https://bugs.launchpad.net/neutron/+bug/1949704 Timeout change by ralonsoh in https://review.opendev.org/c/openstack/neutron/+/816631 * [CI] "neutron-ovs-rally-task" job failing due to an authentication problem - https://bugs.launchpad.net/neutron/+bug/1949945 Change to create keystone endpoint merged by ralonsoh: https://review.opendev.org/c/openstack/neutron/+/816792 High * [OVN] Stateless SG Extension Support - https://bugs.launchpad.net/neutron/+bug/1949451 Extension missing in the OVN supported extensions list, fix by Ihar https://review.opendev.org/c/openstack/neutron/+/816612 * "openstack-tox-py39" is timing out frequently - https://bugs.launchpad.net/neutron/+bug/1949476 Similar fix as py38 in https://review.opendev.org/c/openstack/neutron/+/816631 Medium * [OVS][QoS] Dataplane enforcement is limited to minimum bandwidth egress rule - https://bugs.launchpad.net/neutron/+bug/1949607 Patch in progress by ralonsoh: https://review.opendev.org/c/openstack/neutron/+/816530 * FIP ports count into quota as they get a project_id set - https://bugs.launchpad.net/neutron/+bug/1949767 Change in train bulk port binding, suggested fix https://review.opendev.org/c/openstack/neutron/+/816722 * [OVN] OVN mech driver does not map new segments - https://bugs.launchpad.net/neutron/+bug/1949967 WIP patch by ralonsoh https://review.opendev.org/c/openstack/neutron/+/816856 Low * [OVN] Check OVN support for stateless NAT - https://bugs.launchpad.net/neutron/+bug/1949494 Patch in progress by ralonsoh: https://review.opendev.org/c/openstack/neutron/+/816376 * [OVN] Check OVN support virtual port type - https://bugs.launchpad.net/neutron/+bug/1949496 Patch in progress by ralonsoh: https://review.opendev.org/c/openstack/neutron/+/816383 * direct-physical port creation fails with QoS minimum bandwidth rule - https://bugs.launchpad.net/neutron/+bug/1949877 Assigned to gibi -- Bernard Cafarelli

1 0

[neutron] Neutron Team meeting - vote on time of the meeting
by Lajos Katona 08 Nov '21

08 Nov '21

Hi Neutrinos As we discussed during the PTG, let's start a poll to see which time fits best the need of the team for the Neutron Team meeting. I prepared a doodle, please check which time slot would be best for you: https://doodle.com/poll/m973q9eyag8k385w?utm_source=poll&utm_medium=link The dates for the doodle now for next week, but please ignore that. Lajos Katona (lajoskatona)

1 0

[all][tc] What's happening in Technical Committee: summary 5th Nov, 21: Reading: 10 min
by Ghanshyam Mann 05 Nov '21

05 Nov '21

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * TC this week IRC meeting held on Nov 5th Thursday. * Most of the meeting discussions are summarized below (Completed or in-progress activities section). Meeting full recording are available @ - https://www.youtube.com/watch?v=4bt6iNaR3oI - IRC chat summary (topics and links): https://meetings.opendev.org/meetings/tc/2021/tc.2021-11-04-15.02.log.html * Next week's meeting will be on IRC on Nov 11th, Thursday 15:00 UTC, feel free the topic on agenda[1] by Nov 10th. 2. What we completed this week: ========================= * Retired kolla-cli [2] * Removed oslo independent deliverables from stable policy[3] * Magnum PTL is changed from Feilong Wang to Spryos[4] 3. Activities In progress: ================== TC Tracker for Yoga cycle ------------------------------ * I have started the etherpad to collect the Yoga cycle targets for TC[5]. Open Reviews ----------------- * Eleven open reviews for ongoing activities[6]. RBAC discussion: continuing from PTG ---------------------------------------------- We had a discussion on Wed and sort out the many points especially on get-all-project resources or system and project scoped isolation. Complete notes are in this etherpad[7]. Lance is re-working on the goal and new implementation/details, feel free to review it for more feedback[8]. We will continue the discussion on next Wed Nov 10th same time[9], feel free to join for any additional query related to your project specific and we will also discuss about what all bits we can do in Yoga cycle and what all to move as next targets. Decouple the community-wide goals from cycle release ----------------------------------------------------------------- * As discussed in PTG, we are de-coupling the community-wide goals from release cycle so that we can improve the community-wide goal selection and its completion workflow where goals are multi-cycle like RBAC etc. * Proposal is up, please review and add your feedback[10]. Yoga release community-wide goal ----------------------------------------- * With the continuing the discussion on RBAC, we are re-working on the RBAC goal, please wait until we finalize the implementation[11] * There is one more goal proposal for 'FIPS compatibility and compliance'[12]. Adjutant need maintainers and PTLs ------------------------------------------- You might have seen the email[13] from Adrian to call the maintainer for Adjutant project, please reply to that email or here or on openstack-tc channel if you are interested to maintain this project. We will wait for next week also and if no-one shows up for help then we will start the retirement process. New project 'Skyline' proposal ------------------------------------ * We discussed it in TC PTG and there are few open points about python packaging, repos, and plugins plan which we are discussion on ML. * Still waiting from skyline team to work on the above points[14]. Updating the Yoga testing runtime ---------------------------------------- * As centos stream 9 is released, I have updated the Yoga testing runtime[15] with: 1. Add Debian 11 as tested distro 2. Change centos stream 8 -> centos stream 9 3. Bump lowest python version to test to 3.8 and highest to python 3.9 Stable Core team process change --------------------------------------- * Current proposal is under review[16]. Feel free to provide early feedback if you have any. * This is ready to merge and I will do that week early, feel free to add feedback if any. Merging 'Technical Writing' SIG Chair/Maintainers to TC ------------------------------------------------------------------ * Work to merge this SIG to TC is up for review[17]. * No response on usage and maintaining help for openstack/training-labs repo[18] and in TC meeting we decided to retire it next week. If you use or would like to maintain this, this is last chance to raise hand. TC tags analysis ------------------- * TC agreed to remove the framework and it is communicated in ML[19]. Project updates ------------------- * Retiring js-openstack-lib [20] 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[21]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [22] 3. Office hours: The Technical Committee offers a weekly office hour every Tuesday at 0100 UTC [23] 4. 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/+/814603 [3] https://review.opendev.org/c/openstack/governance/+/816828 [4] https://review.opendev.org/c/openstack/governance/+/816431 [5] https://etherpad.opendev.org/p/tc-yoga-tracker [6] https://review.opendev.org/q/projects:openstack/governance+status:open [7] https://etherpad.opendev.org/p/policy-popup-yoga-ptg [8] https://review.opendev.org/c/openstack/governance/+/815158 [9] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025666… [10] https://review.opendev.org/c/openstack/governance/+/816387 [11] https://review.opendev.org/c/openstack/governance/+/815158 [12] https://review.opendev.org/c/openstack/governance/+/816587 [13] http://lists.openstack.org/pipermail/openstack-discuss/2021-October/025555.… [14] https://review.opendev.org/c/openstack/governance/+/814037 [15] https://review.opendev.org/c/openstack/governance/+/815851 [16] https://review.opendev.org/c/openstack/governance/+/810721 [17] https://review.opendev.org/c/openstack/governance/+/815869 [18] http://lists.openstack.org/pipermail/openstack-discuss/2021-October/025586.… [19] http://lists.openstack.org/pipermail/openstack-discuss/2021-October/025571.… [20] https://review.opendev.org/c/openstack/governance/+/807163 [21] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [22] http://eavesdrop.openstack.org/#Technical_Committee_Meeting [23] http://eavesdrop.openstack.org/#Technical_Committee_Office_hours -gmann

1 0

[docs] Double headings on every page
by Peter Matulis 04 Nov '21

04 Nov '21

Hi, I'm hitting an oddity in one of my projects where the titles of all pages show up twice. Example: https://docs.openstack.org/project-deploy-guide/charm-deployment-guide/wall… Source file is here: https://opendev.org/openstack/charm-deployment-guide/src/branch/master/depl… Does anyone see what can be causing this? It appears to happen only for the current stable release ('wallaby') and 'latest'. Thanks, Peter

5 6

[neutron] Drivers meeting - Friday 5.11.2021 - cancelled
by Lajos Katona 04 Nov '21

04 Nov '21

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

[baremetal-sig][ironic] Tue Nov 9, 2021, 2pm UTC: Hardware burn-in
by Arne Wiebalck 04 Nov '21

04 Nov '21

Dear all, The Bare Metal SIG will meet next week on Tue Nov 9, 2021, at 2pm UTC on zoom. The meeting will feature a "topic-of-the-day" presentation by Emmanouil Bagakis (CERN) on "Hardware Burn-in with Ironic" As usual, all details on https://etherpad.opendev.org/p/bare-metal-sig Everyone is welcome! Cheers, Arne

1 0

[barbican] Simple Crypto Plugin kek issue
by Ammad Syed 03 Nov '21

03 Nov '21

Hi, I have installed barbican and using it with openstack magnum. When I am using the default kek describe in document below, works fine and magnum cluster creation goes successful. https://docs.openstack.org/barbican/latest/install/barbican-backend.html But when I generate a new kek with below command. python3 -c "from cryptography.fernet import Fernet ; key = Fernet.generate_key(); print(key)" and put it in barbican.conf, the magnum cluster failed to create and I see below logs in barbican. 2021-10-29 12:53:28.932 568554 INFO barbican.plugin.crypto.simple_crypto [req-aaac01e9-82af-421b-b85a-ff998d904972 ad702ac807f44c73a32a9b7a795b693c d782069f335041138f0cb141fde9933f - default default] Software Only Crypto initialized 2021-10-29 12:53:28.932 568554 DEBUG barbican.model.repositories [req-aaac01e9-82af-421b-b85a-ff998d904972 ad702ac807f44c73a32a9b7a795b693c d782069f335041138f0cb141fde9933f - default default] Getting session... get_session /usr/lib/python3/dist-packages/barbican/model/repositories.py:364 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers [req-aaac01e9-82af-421b-b85a-ff998d904972 ad702ac807f44c73a32a9b7a795b693c d782069f335041138f0cb141fde9933f - default default] Secret creation failure seen - please contact site administrator.: cryptography.fernet.InvalidToken 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers Traceback (most recent call last): 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers File "/usr/lib/python3/dist-packages/cryptography/fernet.py", line 113, in _verify_signature 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers h.verify(data[-32:]) 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers File "/usr/lib/python3/dist-packages/cryptography/hazmat/primitives/hmac.py", line 70, in verify 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers ctx.verify(signature) 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers File "/usr/lib/python3/dist-packages/cryptography/hazmat/backends/openssl/hmac.py", line 76, in verify 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers raise InvalidSignature("Signature did not match digest.") 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers cryptography.exceptions.InvalidSignature: Signature did not match digest. 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers During handling of the above exception, another exception occurred: 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers Traceback (most recent call last): 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers File "/usr/lib/python3/dist-packages/barbican/api/controllers/__init__.py", line 102, in handler 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers return fn(inst, *args, **kwargs) 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers File "/usr/lib/python3/dist-packages/barbican/api/controllers/__init__.py", line 88, in enforcer 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers return fn(inst, *args, **kwargs) 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers File "/usr/lib/python3/dist-packages/barbican/api/controllers/__init__.py", line 150, in content_types_enforcer 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers return fn(inst, *args, **kwargs) 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers File "/usr/lib/python3/dist-packages/barbican/api/controllers/secrets.py", line 456, in on_post 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers new_secret, transport_key_model = plugin.store_secret( 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers File "/usr/lib/python3/dist-packages/barbican/plugin/resources.py", line 108, in store_secret 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers secret_metadata = _store_secret_using_plugin(store_plugin, secret_dto, 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers File "/usr/lib/python3/dist-packages/barbican/plugin/resources.py", line 279, in _store_secret_using_plugin 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers secret_metadata = store_plugin.store_secret(secret_dto, context) 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers File "/usr/lib/python3/dist-packages/barbican/plugin/store_crypto.py", line 96, in store_secret 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers response_dto = encrypting_plugin.encrypt( 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers File "/usr/lib/python3/dist-packages/barbican/plugin/crypto/simple_crypto.py", line 76, in encrypt 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers kek = self._get_kek(kek_meta_dto) 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers File "/usr/lib/python3/dist-packages/barbican/plugin/crypto/simple_crypto.py", line 73, in _get_kek 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers return encryptor.decrypt(kek_meta_dto.plugin_meta) 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers File "/usr/lib/python3/dist-packages/cryptography/fernet.py", line 76, in decrypt 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers return self._decrypt_data(data, timestamp, ttl, int(time.time())) 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers File "/usr/lib/python3/dist-packages/cryptography/fernet.py", line 125, in _decrypt_data 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers self._verify_signature(data) 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers File "/usr/lib/python3/dist-packages/cryptography/fernet.py", line 115, in _verify_signature 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers raise InvalidToken 2021-10-29 12:53:28.991 568554 ERROR barbican.api.controllers cryptography.fernet.InvalidToken Any advise how to fix it ? - Ammad

2 1

[all][tc] Technical Committee next weekly meeting on Nov 4th at 1500 UTC
by Ghanshyam Mann 03 Nov '21

03 Nov '21

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

1 1

[TripleO] Branching our documentation
by James Slagle 03 Nov '21

03 Nov '21

Hello TripleO Owls, Our documentation, particularly the deploy guide, has become overly complex with all the branches that TripleO has supported over the years. I see notes that document functionality specific to releases all the way back to Mitaka! In ancient history, we made the decision to not branch our documentation because the work to maintain multiple branches outweighed the effort to just document all releases at once in the same branch. I think the scale has now tipped in the other direction. I propose that we create a stable/wallaby in tripleo-docs, and begin making the master branch specific to Yoga. This would also mean we could clean up all the old notes and admonitions about previous releases on the master branch. Going forward, if you make a change to the docs that applies to Yoga and Wallaby, you would need to backport that change to stable/wallaby. If you needed to make a change that applied only to Wallaby (or a prior release), you would make that change only on stable/wallaby. I'm not sure of all the plumbing required to make it so that the OpenStack Wallaby deploy guide builds from stable/wallaby, etc, but I wanted to get the idea out there first for feedback. Please let me know your thoughts. Thank you! -- -- James Slagle --

4 4

[ptl][release][stable][EM] Extended Maintenance - Ussuri
by Előd Illés 03 Nov '21

03 Nov '21

Hi, As Xena was released last week and we are in a less busy period, now it is a good time to call your attention to the following: In a month Ussuri is planned to transition to Extended Maintenance phase [1] (planned date: 2021-11-12). I have generated the list of the current *open* and *unreleased* changes in stable/ussuri for the follows-policy tagged repositories [2] (where there are such patches). These lists could help the teams who are planning to do a *final* release on Ussuri before moving stable/ussuri branches to Extended Maintenance. Feel free to edit and extend these lists to track your progress! * At the transition date the Release Team will tag the *latest* Ussuri releases of repositories with *ussuri-em* tag. * After the transition stable/ussuri will be still open for bug fixes, but there won't be official releases anymore. *NOTE*: teams, please focus on wrapping up your libraries first if there is any concern about the changes, in order to avoid broken (final!) releases! Thanks, Előd [1] https://releases.openstack.org/ [2] https://etherpad.opendev.org/p/ussuri-final-release-before-em

1 1