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

[election][Release_Management] Proposal to change to Distributed PTL model
by Előd Illés 30 Aug '22

30 Aug '22

Hi, This is my 2nd cycle (Yoga + Zed) as PTL of the Release Management team and this is the time when usually a PTL role is handed over. We had a discussion in our team and decided that now that OpenStack moves from Zed to Antelope and the cycles starts again from the beginning of the alphabet + the new naming is going to be introduced (2023.1 Antelope) this is a good time to change the leadership model of the team to a group leadership model (or DPTL; distributed project team leadership). @TC: so this mail is to inform the TC that we want to move to this direction & let us know if there is something we need to sort out for the model change. Thanks, Előd Illés irc: elodilles

2 1

PTG October 2022 Teams List
by Kendall Nelson 30 Aug '22

30 Aug '22

Hello Everyone! The October 2022 Project Teams List is official! Projects + Teams: - Computing Force Network (CFN) Working Group - Diversity& Inclusion Working Group - Environmental Sustainability Working Group - Kata Containers - Magma - OpenInfra Edge Computing Group - OpenStack Teams - - Ansible OpenStack Modules - Barbican - Blazar - Cinder - CloudKitty - Designate - First Contact SIG - Glance - Heat - Horizon - Interop WG - Ironic - Keystone - Kolla - Kuryr - Manila - Neutron - Nova/Placement - Octavia - OpenStack Charms - OpenStack Helm - OpenStack Operators - OpenStack SDK/CLI - OpenStack Security SIG - OpenStack Technical Committee - Openstack-Ansible - OpenStack-Helm - QA - Release Management - Swift - Tacker - Telemetry - TripleO - StarlingX If your team was planning to meet and isn’t in this list, please contact ptg(a)openinfra.dev IMMEDIATELY. Soon I will be contacting moderators to sign up for time via the PTGBot[1] once I have it configured for the teams that are signed up to attend the event. Otherwise, please don't forget to register[2] — its FREE! As usual, feel free to let us know if you have any questions. Thanks! -Kendall (diablo_rojo) [1] PTGBot Docs: https://github.com/openstack/ptgbot#open-infrastructure-ptg-bot [2] PTG Registration: https://openinfra-ptg.eventbrite.com

1 0

[election][Neutron] PTL candidacy for Antelope cycle
by Rodolfo Alonso Hernandez 30 Aug '22

30 Aug '22

Hello all: I would like to announce my candidacy for the role of PTL of Neutron for the Antelope cycle. Let me introduce myself first. I started contributing to OpenStack in Liberty release (2015). I've contributed to several projects, mainly Neutron, neutron-lib, os-ken and os-vif, in addition to Nova and devstack. During the last two years I've been focused on the ML2/OVN integration, QoS and Placement related features and helping on the Neutron CI improvement and stabilization. For this new release, those are the main goals I would like to focus on: * Take care and focus on the approved and merged Neutron specs [1]. Those RFEs should be actively attended by the community, from the spec proposal to the code review. In order to increase the attention of the community on these new RFEs, new ways of tracking them should be proposed (a topic that should be discussed during the PTG). For example, having a core reviewer “godfather” for each RFE. * Continue with the improvement of CI stability. The job done during the last 2 or 3 releases has been impressive, probably the hardest and the most continued effort on the CI in the Neutron community ever. We *must* continue with this effort and the current processes to track the healthiness of the CI. * Start working on the smart NIC / hardware offload testing. The number of backends (ML2/OVS, ML2/OVN, ML2/SR-IOV) make non-viable to test any possible combination. But at least, depending on the available hardware, we would be able to test the stability of those backends with the newest hardware offload NICs. Note: that will imply an external CI support. * Work with users and operators, providing an active channel with them. The goal is to attract customers to be actively involved in the community, participating in the Neutron meetings (team meeting, CI meeting, drivers meeting) or even creating a specific meeting with them in order to capture new needs or issues. * Live migration improvement, specially in ML2/OVN. This feature is still being tested and has not proven to be very stable. There are several core OVN and Neutron efforts right now but we still need to make this feature stable enough to be delivered to customers. A part from those main goals, we should always keep an eye on: * The SQLAlchemy 2.0 migration and any possible issue detected. * The Neutron's stadium ecosystem alive and healthy: this is a permanent goal in any release. The Neutron ecosystem is wide and diverse and it is maintained with few resources. We should focus on those active projects and communities that support their respective repositories. * Still closing the ML2/OVS - ML2/OVN feature gap, that is smaller every cycle. Thank you in advance. Rodolfo Alonso Hernandez (ralonsoh, ralonsoh(a)redhat.com)

1 0

[TripleO] quay.io namespace local mirror using harbor. Quay.io do not list repos/images
by Ruslanas Gžibovskis 30 Aug '22

30 Aug '22

Hi all, I am trying to make a local repo/copy to be able to deploy OSP onsite behind firewall. I have found out from harbor, that Quay.io do not return repos/image anonymously also I have created account in quay.io with my RH account. Later reset quay.io password, so quay.io connection verify works. I can get it as a proxy, or exact image, but not full offline installation. Could you help/suggest any tool that could do a local repo? I have also tried foreman, but it only can sync repo in namespace, not whole namespace. Thank you for your advice and comments. -- Ruslanas Gžibovskis +370 6030 7030

2 1

[kolla] [nova] Rogue AggregateMultiTenancyIsolation filter
by Albert Braden 30 Aug '22

30 Aug '22

We're running kolla train, and we use the AggregateMultiTenancyIsolation for some aggregates by setting filter_tenant_id. Today customers reported build failures when they try to build VMs in a non-filtered region. I am able to duplicate the issue: os server create --image <image> --flavor medium --network private --availability-zone open alberttest1 | 5dd44105-2045-4d53-be43-5f521ddb420b | alberttest1 | ERROR | | <image> | medium | 2022-08-26 18:39:38.977 30 INFO nova.filters [req-342d065a-cd47-4edf-bc4b-3f84b34ab97c 25b53bdb96fb5f9f6e7331d7e03eee0a12c45746a9e8b978858b2140a5275a09 fdcf1553db504c8f82a2b54851a4c262 - 8793b235debf49e6aba6bd1e2bf65360 8793b235debf49e6aba6bd1e2bf65360] Filtering removed all hosts for the request with instance ID '5dd44105-2045-4d53-be43-5f521ddb420b'. Filter results: ['ComputeFilter: (start: 50, end: 50)', 'RetryFilter: (start: 50, end: 50)', 'AggregateNumInstancesFilter: (start: 50, end: 50)', 'AvailabilityZoneFilter: (start: 50, end: 6)', 'AggregateInstanceExtraSpecsFilter: (start: 6, end: 6)', 'ImagePropertiesFilter: (start: 6, end: 6)', 'ServerGroupAntiAffinityFilter: (start: 6, end: 6)', 'ServerGroupAffinityFilter: (start: 6, end: 6)', 'AggregateMultiTenancyIsolation: (start: 6, end: 0)'] Region "open" does not have any properties specified, so the AggregateMultiTenancyIsolation filter should not be active. qde3:admin]$ os aggregate show open|grep properties | properties | This is what we would see if it had the filter active: :qde3:admin]$ os aggregate show closed|grep properties | properties | filter_tenant_id='1c41e088b35f4b438023d081a6f70292,3e9727aaf03e4459a176c28dbdb3965e,f9b4b7dc8c614bb09d66657afc3b21cd,121a5da3dd0b489986908bee7eea61ae,d580ccc4b07e478a9efc2d71acf04cc1,107e14eeda01400988e58f5aac8b2772', closed='true' What could be causing this filter to remove hosts when we haven't set filter_tenant_id for that aggregate?

2 2

[cinder] This week's meeting will be in video+IRC
by Rajat Dhasmana 30 Aug '22

30 Aug '22

Hello Argonauts, As we keep last meeting of the month in video + IRC mode, this week's meeting (tomorrow) will be held in video + IRC mode with details as follows: Date: 31st August, 2022 Time: 1400 UTC Meeting link: https://bluejeans.com/556681290 IRC Channel: #openstack-meeting-alt Make sure you're connected to both the bluejeans meeting and IRC since we do roll call and also discuss topics on IRC (if the author is more comfortable in written format). Thanks and regards Rajat Dhasmana

1 0

[election][nova][placement] Candidating for the Antelope cycle.
by Sylvain Bauza 30 Aug '22

30 Aug '22

Hi Nova and Placement folks, Yet again, I want to help our community for this cycle by working on papers. If you accept me for being Antelope Nova/Placement PTL, it would be my last cycle for it after already two of them (unless nobody runs for this). For the moment, we are not yet done with Zed but I'm happy to see that we have 13 open blueprints that are reviewed and where some of them are from contributors that aren't everyday Nova developers. That's the reason why I wanted to help those on-off contributors that have not a large time for upstream work and that's why we added a Gerrit review label value for them (saying "I want to review as a contributor"). We also tried a new way for discussing about open changes creating a new API microversion and even if it hadn't really needed, I think we could use this way next time if needed. So, what would I like for us to discuss during Antelope then ? Well, at least three points : - given Antelope will be the first 'tick' release, I want to make sure we won't have any issues in Nova or Placement for this cycle, and I also would like to prepare for the 'tock' release. - I would like to discuss with our community how to find some opportunities for new contributors that would like to work on Nova. - as we discussed with operators in the Berlin Summit, I would like to find a way for them to discuss with us and see how they could be in our community even if they're not developers. At least, I'd love to see some operators in our meetings and in our PTG sessions. Thanks, -Sylvain (again, not a leader but just a herder.)

1 0

[all] [oslo.messaging] Interest in collaboration on a NATS driver
by Tobias Urdin 30 Aug '22

30 Aug '22

Hello, Please note that the list provided was just from my own notes and I didn’t put much emphasis on making it complete or accurate. If you think back to the early days of OpenStack the pain was in OpenStack itself, today it’s a challenge instead to manage OpenStack scale and fit into the things we see, like moving OpenStack into containers (for example managed by Kubernetes). I would like OpenStack design to more embrace the distributed, cloud-native approach that Ceph and Kubernetes brings, and the resiliency of Ceph (and yes, I’m a major Ceph enthusiast) and there I’m seeing messaging and database as potential blockers to continue on that path. I’m not saying that’s the only thing, for example stuff like [1] _really_ matter in real world deployments so working on other OpenStack parts for resilience is also crucial. There is things I’m interested in that would impact the overall design, I can list some of them but I think it might be to broad of a subject for this thread. * Like brought up my Mohammed Naser before, I would like to investigate an effort for containers as an OpenStack deliverable for projects * Investigate cloud-native, highly available and resilient alternatives for messaging and database * Make OpenStack more resilient with above and [1] is a great example on what I mean I’ll respond to your questions with my views inline below. P.S The opionions stated here is my own personal opinions and should not be assumed to be the opinions of any other entity. Best regards Tobias [1] https://bugs.launchpad.net/neutron/+bug/1987780 Begin forwarded message: From: Radosław Piliszek <radoslaw.piliszek(a)gmail.com<mailto:radoslaw.piliszek@gmail.com>> Subject: Re: [all] [oslo.messaging] Interest in collaboration on a NATS driver Date: 29 August 2022 at 18:33:15 CEST To: Tobias Urdin <tobias.urdin(a)binero.com<mailto:tobias.urdin@binero.com>> Cc: openstack-discuss <openstack-discuss(a)lists.openstack.org<mailto:openstack-discuss@lists.openstack.org>> Hi Tobias, Good to see RMQ alternatives appearing. A couple of questions from me. On Mon, 29 Aug 2022 at 15:47, Tobias Urdin <tobias.urdin(a)binero.com<mailto:tobias.urdin@binero.com>> wrote: • Do retries and acknowledgements in the library (since NATS does NOT persist messages like RabbitMQ could) What do you mean? Is NATS only a router? (I have not used this technology yet.) It does not persist messages, if there is no backend to respond, the message will be dropped without any action hence why I want the RPC layer in oslo.messaging (that already does acknowledge calls in the driver) to notify client side that it’s being processed before client side waits for reply. • Find or maintain a NATS python library that doesn't use async like the official one does Why is async a bad thing? For messaging it's the right thing. This is actually just myself, I would love to just being able to use the official that is async based instead it’s just me that doesn’t understand how that would be implemented. https://github.com/nats-io/nats.py instead of the one in POC https://github.com/Gr1N/nats-python which has a lot of shortcomings and issues, my idea was just to investigate if was even possible to implement in a feasible way. Finally, have you considered just trying out ZeroMQ? Does not exist anymore. I mean, NATS is probably an overkill for OpenStack services since the majority of them stay static on the hosts they control (think nova-compute, neutron agents - and these are also the pain points that operators want to ease). I don’t think it it, or even if it is, why not use a better solution or stable approach than RabbitMQ? This is also the whole point, I don’t want OpenStack to become or be static, I want it to be more dynamic and cloud-native in it’s approach and support viable integrations that takes it there, we cannot live in the past forever, let’s envision and dream of the future as we want it! :) NATS seems to me to cater for a different use case. It actually caters to a lot of use cases. I might be wrong because I have read only the front page but that is the feeling I have. Cheers, Radek -yoctozepto Begin forwarded message: From: Radosław Piliszek <radoslaw.piliszek(a)gmail.com<mailto:radoslaw.piliszek@gmail.com>> Subject: Re: [all] [oslo.messaging] Interest in collaboration on a NATS driver Date: 29 August 2022 at 20:20:15 CEST To: Sean Mooney <smooney(a)redhat.com<mailto:smooney@redhat.com>> Cc: Tobias Urdin <tobias.urdin(a)binero.com<mailto:tobias.urdin@binero.com>>, openstack-discuss <openstack-discuss(a)lists.openstack.org<mailto:openstack-discuss@lists.openstack.org>> On Mon, 29 Aug 2022 at 20:03, Sean Mooney <smooney(a)redhat.com<mailto:smooney@redhat.com>> wrote: Finally, have you considered just trying out ZeroMQ? ZeroMQ used to be supported in the past but then it was remvoed if i understand correctly it only supprot notificaiton or RPC but not both i dont recall which but perhapse im miss rememebrign on that point. I believe it would be better suited for RPC than notifications, at least in the simplest form. As it’s advertised as scalable and performant I would argue that, why not use it for notifications as well? If anything according to your observations above it’s more suited for that than RPC, even though request-reply (that we can use for RPC) is a strong first-class implementation in NATS as well. I mean, NATS is probably an overkill for OpenStack services since the majority of them stay static on the hosts they control (think nova-compute, neutron agents - and these are also the pain points that operators want to ease). its not any more overkill then rabbitmq is True that. Probably. I agree with that, also if you think about it, how many issues related to stability, performance and outages is related to RabbitMQ? It’s quite a few if you ask me. Just the resource utilization and clustering in RabbitMQ makes me feel bad. It’s here that I mean that the cloud-native and scalable implementation would shine, you should be able to rely on it, if sometimes dies so what, things should just continue to work and that’s not my experience with RabbitMQ but it is my experience with Ceph because in the end the design really matters. i also dont know waht you mean when you say "majority of them stay static on the hosts they control" NATS is intended a s a cloud native horrizontally scaleable message bus. which is exactly what openstack need IMO. NATS seems to be tweaked for "come and go" situations which is an exception in the OpenStack world, not the rule (at least in my view). I mean, one normally expects to have a preset number of hypervisors and not them coming and going (which, I agree, is a nice vision, could be a proper NATS driver, with more awareness in the client projects I believe, would be an enabler for more dynamic clouds). It could, but it also doesn’t have to be that. Why not strive for more dynamic? I don’t think anybody would argue that more dynamic is a bad thing even if you were to have a more static approach to your cloud. Cheers, Radek -yoctozepto

2 2

[publiccloud-sig] Bi-weekly meeting reminder
by Tobias Rydberg 29 Aug '22

29 Aug '22

Hi all, Tomorrow we will have our bi-weekly meeting at 0800 UTC in #openstack-operators. Agenda can be fond here [0]. Feel free to suggest topics to the agenda if you like. Hope to chat with you tomorrow! [0] https://etherpad.opendev.org/p/publiccloud-sig-meeting BR, Tobias Rydberg

1 0

RE: Openstack OVN (Open Virtual Network) HA deployment - running OVN in active/passive mode?
by 박경원 29 Aug '22

29 Aug '22

1 0

[infra][puppet] Old mirror contents in apt-puppetlabs
by Takashi Kajinami 29 Aug '22

29 Aug '22

Hello Infra team, I noticed the contents in the apt-puppetlabs directory in our CI mirror are old. The mirror repository provides puppet 6.23 while the upstream repository provides newer versions such as 6.28. Recently we bumped puppetlabs-mysql in our CI to 13.0.0 which requires puppet >= 6.24.0 and our Ubuntu jobs are failing now at a quite early stage because of the old puppet package. May someone please look into this ? I've checked mirror.iad3.inmotion.opendev.org and mirror.bhs1.ovh.opendev.org but it seems the contents in the directory have not been synced since July, 2021. Thank you, Takashi

2 3

Skyline apiserver can't connect to keystone and given error endpoint not found
by mahdi n 29 Aug '22

29 Aug '22

Skyline apiserver can't connect to keystone and given endpoint not found I install skyline api server and console But Apiserver get error : endpoint not found I attached pictures of this problem Please help me

1 1

[all][elections][ptl][tc] Combined PTL/TC antelope cycle Election Nominations Last Days
by Amy Marrich 29 Aug '22

29 Aug '22

A quick reminder that we are in the last hours for declaring PTL and TC candidacies. Nominations are open until Aug 31, 2022 23:45 UTC. Should we find that many of the community members were off on vacation this date may get extended pushing the elections out. If you want to stand for election, don't delay, follow the instructions at [1] to make sure the community knows your intentions. Make sure your nomination has been submitted to the openstack/election repository and approved by election officials. Election statistics[2]: Nominations started @ 2022-08-24 23:45:00 UTC Nominations end @ 2022-08-31 23:45:00 UTC Nominations duration : 7 days, 0:00:00 Nominations remaining : 2 days, 5:50:21 Nominations progress : 67.95% --------------------------------------------------- Projects[1] : 52 Projects with candidates : 5 ( 9.62%) Projects with election : 0 ( 0.00%) --------------------------------------------------- Need election : 0 () Need appointment : 47 (Adjutant Barbican Blazar Cinder Cloudkitty Cyborg Designate Freezer Glance Heat Horizon Ironic Keystone Manila Masakari Mistral Monasca Murano Neutron Nova Octavia OpenStackAnsible OpenStackSDK OpenStack_Charms OpenStack_Helm Openstack_Chef Oslo Puppet_OpenStack Quality_Assurance Rally Release_Management Requirements Sahara Senlin Skyline Solum Storlets Swift Tacker Telemetry Tripleo Trove Venus Vitrage Watcher Zaqar Zun) =================================================== Stats gathered @ 2022-08-29 17:54:39 UTC This means that with approximately 2 days left, 47 projects will be deemed leaderless. In this case the TC will oversee PTL selection as described by [3]. Thank you, [1] https://governance.openstack.org/election/#how-to-submit-a-candidacy [2] Any open reviews at https://review.openstack.org/#/q/is:open+project:openstack/election have not been factored into these stats. [3] https://governance.openstack.org/resolutions/20141128-elections-process-for…

1 0

[tacker][elections] PTL candidacy for Antelope cycle
by Yasufumi Ogawa 29 Aug '22

29 Aug '22

Hi, I'd like to propose my candidacy for Tacker PTL for Antelope cycle. I have contributed to Tacker as a PTL from Victoria for providing the latest features of ETSI-NVF standard features to enable operators to deploy their services. In the latest cycles, we have developed several supports for deploying CNFs, multi-version APIs for mixed environment of legacy and cutting edge-products provided by several vendors and more. We also have had several collaborative sessions with ETSI NFV for accelerating each activity of standardization and deployment of required features. In the next release, I would like to focus our target more on to develop features for reliability and avairability such as monitoring physical resources in addition to VMs and containers. Best regards, Yasufumi (yasufum)

1 0

[TripleO Wallaby] - Multi-attach Volume showing different files
by Lokendra Rathour 29 Aug '22

29 Aug '22

Hi Team, On TripleO Wallaby deployment, I have tried creating multi-attach type volume, which if I am attaching this volume to two VM, it is getting attached. After mounting the same in each VM, if I am creating the folders in one VM at the mount path, I am not seeing the same on the other VM at the mount path [image: image.png] Ideally if the backend volume is same and if I am understanding the idea correctly, then the content should be same in both the location, as the back is same. Checking at horizon I also see that Volume is showing attached to both the VMs. [image: image.png] Document followed to create this: https://docs.openstack.org/cinder/latest/admin/volume-multiattach.html Please advice -- ~ Lokendra skype: lokendrarathour

3 4

[Neutron] How to add Fake ML2 extension to Neutron?
by Igor Zhukov 29 Aug '22

29 Aug '22

Hi all! Sorry for a complete noob question but I can't figure it out 😿 So if I want to add Fake ML2 extension what should I do? I have neutron server installed and I have the file: https://github.com/openstack/neutron/blob/master/neutron/tests/unit/plugins… How to configure neutron server, where should I put the file, should I create another files? How can I test that it works?

2 7

[xena][placement] Xena placement upgrade leads to 500 on ubuntu focal
by CHANU ROMAIN 29 Aug '22

29 Aug '22

Hello, I just did upgrade my Placement to Xena on Ubuntu Focal (20.04). When I tried to start the process I got this error and all HTTP requests receive an HTTP 500 error: 2022-08-19 15:05:43.960573 2022-08-19 15:05:43.960 43 INFO placement.requestlog [req-f4c4d4f1-5d59-49d3-aa3e-1e8a09fe02fe 3ec54dee59424109913d4628ae8dac4c 19e62bc767484849a2763937883a256e - default default] 192.168.236.5 "GET /resource_providers/791c09ed-57f3- 4bfc-9278-4af6c5c137d8/allocations" status: 500 len: 244 microversion: 1.0\x1b[00m 2022-08-19 15:05:44.094951 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap [req-527dce52-c207-43ee-80f2-016a6f031cf5 3ec54dee59424109913d4628ae8dac4c 19e62bc767484849a2763937883a256e - default default] Placement API unexpected error: unsupported callable: TypeError: unsupported callable 2022-08-19 15:05:44.094973 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap Traceback (most recent call last): 2022-08-19 15:05:44.094977 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3.8/inspect.py", line 1135, in getfullargspec 2022-08-19 15:05:44.094980 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap sig = _signature_from_callable(func, 2022-08-19 15:05:44.094998 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3.8/inspect.py", line 2233, in _signature_from_callable 2022-08-19 15:05:44.095001 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap sig = _signature_from_callable( 2022-08-19 15:05:44.095004 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3.8/inspect.py", line 2304, in _signature_from_callable 2022-08-19 15:05:44.095007 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return _signature_from_function(sigcls, obj, 2022-08-19 15:05:44.095010 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3.8/inspect.py", line 2168, in _signature_from_function 2022-08-19 15:05:44.095013 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap parameters.append(Parameter(name, annotation=annotation, 2022-08-19 15:05:44.095015 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3.8/inspect.py", line 2491, in __init__ 2022-08-19 15:05:44.095018 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap self._kind = _ParameterKind(kind) 2022-08-19 15:05:44.095021 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap RecursionError: maximum recursion depth exceeded 2022-08-19 15:05:44.095024 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap 2022-08-19 15:05:44.095026 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap The above exception was the direct cause of the following exception: 2022-08-19 15:05:44.095029 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap 2022-08-19 15:05:44.095032 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap Traceback (most recent call last): 2022-08-19 15:05:44.095035 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/placement/fault_wrap.py", line 39, in __call__ 2022-08-19 15:05:44.095038 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return self.application(environ, start_response) 2022-08-19 15:05:44.095040 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/webob/dec.py", line 129, in __call__ 2022-08-19 15:05:44.095043 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap resp = self.call_func(req, *args, **kw) 2022-08-19 15:05:44.095046 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/webob/dec.py", line 193, in call_func 2022-08-19 15:05:44.095049 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return self.func(req, *args, **kwargs) 2022-08-19 15:05:44.095052 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/microversion_parse/middleware.py", line 80, in __call__ 2022-08-19 15:05:44.095055 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap response = req.get_response(self.application) 2022-08-19 15:05:44.095057 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/webob/request.py", line 1313, in send 2022-08-19 15:05:44.095060 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap status, headers, app_iter = self.call_application( 2022-08-19 15:05:44.095063 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/webob/request.py", line 1278, in call_application 2022-08-19 15:05:44.095065 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap app_iter = application(self.environ, start_response) 2022-08-19 15:05:44.095068 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/placement/handler.py", line 215, in __call__ 2022-08-19 15:05:44.095071 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return dispatch(environ, start_response, self._map) 2022-08-19 15:05:44.095074 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/placement/handler.py", line 149, in dispatch 2022-08-19 15:05:44.095077 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return handler(environ, start_response) 2022-08-19 15:05:44.095083 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/webob/dec.py", line 129, in __call__ 2022-08-19 15:05:44.095086 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap resp = self.call_func(req, *args, **kw) 2022-08-19 15:05:44.095089 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/placement/wsgi_wrapper.py", line 29, in call_func 2022-08-19 15:05:44.095092 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap super(PlacementWsgify, self).call_func(req, *args, **kwargs) 2022-08-19 15:05:44.095094 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/webob/dec.py", line 193, in call_func 2022-08-19 15:05:44.095097 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return self.func(req, *args, **kwargs) 2022-08-19 15:05:44.095100 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/placement/util.py", line 64, in decorated_function 2022-08-19 15:05:44.095103 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return f(req) 2022-08-19 15:05:44.095106 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/placement/handlers/allocation.py", line 299, in list_for_resource_provider 2022-08-19 15:05:44.098861 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 80, in _check 2022-08-19 15:05:44.098864 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return rule(*rule_args) 2022-08-19 15:05:44.098867 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 211, in __call__ 2022-08-19 15:05:44.098870 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap if _check(rule, target, cred, enforcer, current_rule): 2022-08-19 15:05:44.098873 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 80, in _check 2022-08-19 15:05:44.098876 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return rule(*rule_args) 2022-08-19 15:05:44.098893 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 211, in __call__ 2022-08-19 15:05:44.098896 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap if _check(rule, target, cred, enforcer, current_rule): 2022-08-19 15:05:44.098899 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 80, in _check 2022-08-19 15:05:44.098905 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return rule(*rule_args) 2022-08-19 15:05:44.098907 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 255, in __call__ 2022-08-19 15:05:44.098910 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return _check( 2022-08-19 15:05:44.098913 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 80, in _check 2022-08-19 15:05:44.098916 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return rule(*rule_args) 2022-08-19 15:05:44.098919 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 255, in __call__ 2022-08-19 15:05:44.098922 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return _check( 2022-08-19 15:05:44.098925 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 80, in _check 2022-08-19 15:05:44.098928 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return rule(*rule_args) 2022-08-19 15:05:44.098930 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 211, in __call__ 2022-08-19 15:05:44.098933 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap if _check(rule, target, cred, enforcer, current_rule): 2022-08-19 15:05:44.098936 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 80, in _check 2022-08-19 15:05:44.098939 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return rule(*rule_args) 2022-08-19 15:05:44.098941 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 211, in __call__ 2022-08-19 15:05:44.098944 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap if _check(rule, target, cred, enforcer, current_rule): 2022-08-19 15:05:44.098947 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 80, in _check 2022-08-19 15:05:44.098950 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return rule(*rule_args) 2022-08-19 15:05:44.098952 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 255, in __call__ 2022-08-19 15:05:44.098955 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return _check( 2022-08-19 15:05:44.098958 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 80, in _check 2022-08-19 15:05:44.098960 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return rule(*rule_args) 2022-08-19 15:05:44.098963 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 255, in __call__ 2022-08-19 15:05:44.098966 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return _check( 2022-08-19 15:05:44.098968 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 80, in _check 2022-08-19 15:05:44.098971 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return rule(*rule_args) 2022-08-19 15:05:44.098974 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 211, in __call__ 2022-08-19 15:05:44.098977 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap if _check(rule, target, cred, enforcer, current_rule): 2022-08-19 15:05:44.098980 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 80, in _check 2022-08-19 15:05:44.098982 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return rule(*rule_args) 2022-08-19 15:05:44.098985 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 211, in __call__ 2022-08-19 15:05:44.098991 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap if _check(rule, target, cred, enforcer, current_rule): 2022-08-19 15:05:44.098993 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 80, in _check 2022-08-19 15:05:44.098996 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return rule(*rule_args) 2022-08-19 15:05:44.098999 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 255, in __call__ 2022-08-19 15:05:44.099002 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return _check( 2022-08-19 15:05:44.099004 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 75, in _check 2022-08-19 15:05:44.099007 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap argspec = inspect.getfullargspec(rule.__call__) 2022-08-19 15:05:44.099010 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3.8/inspect.py", line 1144, in getfullargspec 2022-08-19 15:05:44.099013 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap raise TypeError('unsupported callable') from ex 2022-08-19 15:05:44.099016 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap TypeError: unsupported callable 2022-08-19 15:05:44.099018 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap \x1b[00m Placement-api is deployed in a container, so I got a fresh policy.yaml file. Did someone already face this? Do you have any idea how to fix this? Best regards, Romain

3 3

[Triple0] [Wallaby] External Ceph Integration getting failed
by Lokendra Rathour 29 Aug '22

29 Aug '22

Hi Team, I was trying to integrate External Ceph with Triple0 Wallaby, and at the end of deployment in step4 getting the below error: 2022-08-03 18:37:21,158 p=507732 u=stack n=ansible | 2022-08-03 18:37:21.157962 | 525400fe-86b8-65d9-d100-0000000080d2 | TASK | Create containers from /var/lib/tripleo-config/container-startup-config/step_4 2022-08-03 18:37:21,239 p=507732 u=stack n=ansible | 2022-08-03 18:37:21.238718 | 69e98219-f748-4af7-a6d0-f8f73680ce9b | INCLUDED | /usr/share/ansible/roles/tripleo_container_manage/tasks/create.yml | overcloud-controller-2 2022-08-03 18:37:21,273 p=507732 u=stack n=ansible | 2022-08-03 18:37:21.272340 | 525400fe-86b8-65d9-d100-0000000086d9 | TASK | Create containers managed by Podman for /var/lib/tripleo-config/container-startup-config/step_4 2022-08-03 18:37:24,532 p=507732 u=stack n=ansible | 2022-08-03 18:37:24.530812 | | WARNING | ERROR: Can't run container nova_libvirt_init_secret stderr: 2022-08-03 18:37:24,533 p=507732 u=stack n=ansible | 2022-08-03 18:37:24.532811 | 525400fe-86b8-65d9-d100-0000000082ec | FATAL | Create containers managed by Podman for /var/lib/tripleo-config/container-startup-config/step_4 | overcloud-novacompute-0 | error={"changed": false, "msg": "Failed containers: nova_libvirt_init_secret"} 2022-08-03 18:37:44,282 p=507732 u *external-ceph.conf:* parameter_defaults: # Enable use of RBD backend in nova-compute NovaEnableRbdBackend: True # Enable use of RBD backend in cinder-volume CinderEnableRbdBackend: True # Backend to use for cinder-backup CinderBackupBackend: ceph # Backend to use for glance GlanceBackend: rbd # Name of the Ceph pool hosting Nova ephemeral images NovaRbdPoolName: vms # Name of the Ceph pool hosting Cinder volumes CinderRbdPoolName: volumes # Name of the Ceph pool hosting Cinder backups CinderBackupRbdPoolName: backups # Name of the Ceph pool hosting Glance images GlanceRbdPoolName: images # Name of the user to authenticate with the external Ceph cluster CephClientUserName: admin # The cluster FSID CephClusterFSID: 'ca3080-aaaa-4d1a-b1fd-4aaaa9a9ea4c' # The CephX user auth key CephClientKey: 'AQDgRjhiuLMnAxAAnYwgERERFy0lzH6ufSl70A==' # The list of Ceph monitors CephExternalMonHost: 'abcd:abcd:abcd::11,abcd:abcd:abcd::12,abcd:abcd:abcd::13' ~ Have tried checking and validating the ceph client details and they seem to be correct, further digging the container log I could see something like this : [root@overcloud-novacompute-0 containers]# tail -f nova_libvirt_init_secret.log tail: cannot open 'nova_libvirt_init_secret.log' for reading: No such file or directory tail: no files remaining [root@overcloud-novacompute-0 containers]# tail -f stdouts/nova_libvirt_init_secret.log 2022-08-04T11:48:47.689898197+05:30 stdout F ------------------------------------------------ 2022-08-04T11:48:47.690002011+05:30 stdout F Initializing virsh secrets for: ceph:admin 2022-08-04T11:48:47.690590594+05:30 stdout F Error: /etc/ceph/ceph.conf was not found 2022-08-04T11:48:47.690625088+05:30 stdout F Path to nova_libvirt_init_secret was ceph:admin 2022-08-04T16:20:29.643785538+05:30 stdout F ------------------------------------------------ 2022-08-04T16:20:29.643785538+05:30 stdout F Initializing virsh secrets for: ceph:admin 2022-08-04T16:20:29.644785532+05:30 stdout F Error: /etc/ceph/ceph.conf was not found 2022-08-04T16:20:29.644785532+05:30 stdout F Path to nova_libvirt_init_secret was ceph:admin ^C [root@overcloud-novacompute-0 containers]# tail -f stdouts/nova_compute_init_log.log -- ~ Lokendra skype: lokendrarathour

3 10

[nova] Changes for out-of-tree drivers
by Rajat Dhasmana 29 Aug '22

29 Aug '22

Hi, I'm working on a nova feature which adds support for rebuilding volume backed instances which modifies the arguments for 'rebuild' method. It adds a 'reimage_boot_volume' parameter which signifies if the user has requested a rebuild operation for a volume backed instance. Currently it is only implemented by the ironic driver in the in-tree drivers. If you're a maintainer of an out of tree driver then you will need to account for it. Thanks and regards Rajat Dhasmana

1 1

Lagging of vm
by Naveen j 29 Aug '22

29 Aug '22

Hi Team. When i create a vm, my vms are lagging so much when I run any application in ubuntu Regards Naveen j

2 2

Questions about High Availability setup
by 박경원 29 Aug '22

29 Aug '22

5 6

[requirement][all] Nose being removed from Debian and Ubuntu: let's remove it from our global requirements
by Thomas Goirand 29 Aug '22

29 Aug '22

Hi, It's no surprise for anyone that's been following it: Nose was deprecated years ago, and now, we're trying to remove it from Debian. Therefore, 49 bugs were filled against the Debian OpenStack package. It'd be nice if upstream OpenStack was also following this move, and removing nose from global-requirements. I'm not sure if it'd be a big deal if that wasn't the case, as I could use a different test runner in Debian, but I very much would prefer if it was the case. Probably Ubuntu will follow the same path, since Nose isn't in main (it's in Universe, meaning Debian maintained...). Your thoughts? Cheers, Thomas Goirand (zigo)

2 1

[neutron] Bug deputy report - week of 22 Aug
by Slawek Kaplonski 29 Aug '22

29 Aug '22

Hi, I was Neutron's bug deputy last week. Here is summary of what happend during this time: ## Critical https://bugs.launchpad.net/neutron/+bug/1987308 - [ovn-octavia-provider] ovn compilation is failing in "ovn-octavia-provider-tempest-master " job - assigned to Fernando, patch proposed https://review.opendev.org/c/openstack/ovn-octavia-provider/+/854008 ## High https://bugs.launchpad.net/neutron/+bug/1987530 - Duplicate external_ip in NAT table lead to loss of N/S connectivity - needs attention ## Medium https://bugs.launchpad.net/neutron/+bug/1987396 - masquerading behavior changed between queens and train - assigned to David Hill, patch proposed already: https://review.opendev.org/c/openstack/neutron/+/854041 https://bugs.launchpad.net/neutron/+bug/1987780 - Nova notifications with error response are not retried - assigned to Szymon Wróblewski https://bugs.launchpad.net/neutron/+bug/1987666 - Race condition when adding two subnet with same cidr to router - unassigned currently ## Low https://bugs.launchpad.net/neutron/+bug/1987281 - Create a method to add multiple IP addresses in one call - assigned to Rodolfo https://bugs.launchpad.net/neutron/+bug/1988026 - Neutron should not create security group with project==None - needs assignment, it seems like low hanging fruit bug to fix for me, ## Whishlist (RFEs) https://bugs.launchpad.net/neutron/+bug/1987378 - [RFE] Add DSCP mark 44 - assigned to Rodolfo, marked by him as an RFE but I don't really think we need to discuss and approve it in the drivers meeting. We discussed that during last drivers meeting and it's already triaged. ## Incomlete https://bugs.launchpad.net/neutron/+bug/1987377 - neutron-metadata-agent the memory usage is increasing, Lajos and Oleg already have some comments on that one, ## Needs attention https://bugs.launchpad.net/cloud-init/+bug/1899487 - cloud-init hard codes MTU configuration at initial deploy time - bug which was reported for cloud-init first but now after long discussion it's on Neutron and we need to check it, -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

Openstack OVN (Open Virtual Network) HA deployment - running OVN in active/passive mode?
by 박경원 29 Aug '22

29 Aug '22

1 0

[neutron][elections] PTL non-candidacy for Antelope cycle
by Lajos Katona 29 Aug '22

29 Aug '22

Hi, It was a great pleasure and honor to be Neutron PTL for 2 cycles, thanks everybody for the help and support during this time (actually not just for these cycles but for all). It's not just smoke and ruins around networking after my PTLship, so after all I would say it was a success :-) My main focus was to keep the Neutron team as encouraging and inclusive as possible and work on cooperation with new contributor groups and even with other projects of whom we are consuming in Openstack. It is time to change and allow new ideas and energies to form Networking. I remain and I hope I can help the community in the next cycles also. Cheers Lajos Katona

10 9