- openstack-discuss - lists.openstack.org

Cinder NFS Encryption
by Hitesh Mathur 23 Nov '21

23 Nov '21

Hi, I am not able to find whether Cinder support NFS data-in-transit encryption or not. Can you please provide the information on this and how to use it ? -- Regards Hitesh

2 1

[magnum] [victoria] [fedora-coreos]
by Namrata Sitlani 23 Nov '21

23 Nov '21

Hello All, We run release Victoria(11.1.1) and we deployed Kubernetes version 1.18.20 on Magnum with Fedora CoreOS version 33 and recently we ran into issues with Cinder CSI plugin. Multiple master nodes break the CSI plugin, but if I use a single master everything works fine. In my understanding it could be related to Fedora CoreOS version. It is not clear which versions are supported. Can somebody give me information on which version is supported? Thanks, Namrata Sitlani

1 0

[openstack-helm] No Meeting Tomorrow
by Gage Hugo 22 Nov '21

22 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 30th. [0] https://etherpad.opendev.org/p/openstack-helm-weekly-meeting

1 0

[all][refstack][neutron][kolla][ironic][heat][trove][senlin][barbican][manila] Fixing Zuul Config Errors
by Clark Boylan 22 Nov '21

22 Nov '21

Hello, The OpenStack tenant in Zuul currently has 134 config errors. You can find these errors at https://zuul.opendev.org/t/openstack/config-errors or by clicking the blue bell icon in the top right of https://zuul.opendev.org/t/openstack/status. The vast majority of these errors appear related to project renames that have been requested of OpenDev or project retirements. Can you please look into fixing these as they can be an attractive nuisance when debugging Zuul problems (they also indicate that a number of your jobs are probably not working). Project renames creating issues: * openstack/python-tempestconf -> osf/python-tempestconf -> openinfra/python-tempestconf * openstack/refstack -> osf/refstack -> openinfra/refstack * x/tap-as-a-service -> openstack/tap-as-a-service * openstack/networking-l2gw -> x/networking-l2gw Project retirements creating issues: * openstack/neutron-lbaas * recordsansible/ara Projects whose configs have errors: * openinfra/python-tempestconf * openstack/heat * openstack/ironic * openstack/kolla-ansible * openstack/kuryr-kubernetes * openstack/murano-apps * openstack/networking-midonet * openstack/networking-odl * openstack/neutron * openstack/neutron-fwaas * openstack/python-troveclient * openstack/senlin * openstack/tap-as-a-service * openstack/zaqar * x/vmware-nsx * openinfra/openstackid * openstack/barbican * openstack/cookbook-openstack-application-catalog * openstack/heat-dashboard * openstack/manila-ui * openstack/python-manilaclient Let us know if we can help decipher any errors, Clark

6 8

[requirements][cinder][manila] pyparsing update needs handling
by Matthew Thode 22 Nov '21

22 Nov '21

https://review.opendev.org/818614 For cinder it looks like operatorPrecedence is gone now. For manila it looks like the same thing. -- Matthew Thode

2 1

[manila] First Yoga cycle bug squash - Nov 29th - 3rd Dec
by Carlos Silva 22 Nov '21

22 Nov '21

Greetings Zorillas and interested stackers! As mentioned in the previous weekly meetings, we will soon be meeting for the first bugsquash of the Yoga release! The event will be held from Nov 29th to 3rd December, 2021, providing an extended contribution window. We will start the event with a call on the first day (Nov 29th). There will be three calls (one of them using our Manila upstream meeting time slot). All of the three calls of the week will be held in a Jitsi room [1]. Nov 29th - 1500 to 1540 UTC - Event opening and bug assignments Dec 2nd - 1500 to 1600 UTC - Collab review session (no regular Manila meeting on this day) Dec 3rd - 1500 to 1540 UTC - Status update and event wrap up A list of selected bugs will be shared here [2]. Please feel free to add any additional bugs you would like to address during the event. [1] https://meetpad.opendev.org/ManilaYogaM1Bugsquash [2] https://ethercalc.openstack.org/wvb2oa23rxbb Thank you in advance! Hope to see you there :) carloss

1 0

[manila] No IRC meeting on 25th Nov
by Goutham Pacha Ravi 22 Nov '21

22 Nov '21

Hello Zorillas, In lieu of holidays this week, we'll be skipping the weekly meeting earlier scheduled at 1500 UTC on 25th Nov 2021. Please reach out here or on OFTC's #openstack-manila should you have any matters that need to be addressed. Thanks, Goutham

1 0

[cinder] reminder: this week's meeting in video+IRC
by Brian Rosmaita 22 Nov '21

22 Nov '21

Quick reminder that this week's Cinder team meeting on Wednesday 24 November, being the final meeting of the month, will be held in both videoconference and IRC at the regularly scheduled time of 1400 UTC. These are the video meeting rules we've agreed to: * Everyone will keep IRC open during the meeting. * We'll take notes in IRC to leave a record similar to what we have for our regular IRC meetings. * Some people are more comfortable communicating in written English. So at any point, any attendee may request that the discussion of the current topic be conducted entirely in IRC. * The meeting will be recorded. connection info: https://bluejeans.com/3228528973 meeting agenda: https://etherpad.opendev.org/p/cinder-yoga-meetings cheers, brian

1 0

Migration from Midonet to OVN
by Jake Yip 22 Nov '21

22 Nov '21

Hi all, We are planning a migration from Midonet to OVN. The general idea is to: - pause neutron - do a `neutron-ovn-db-sync-util` - change networks/ports to geneve/ovs - hard reboot the instances We are wondering if anyone has done a migration like this before, and will like to share their experiences. Any input will be greatly appreciated. Regards, Jake -- Jake Yip DevOps Engineer, ARDC Nectar Research Cloud

2 1

[kolla-ansible][wallaby][magnum] calico works, flannel does not work
by wodel youchi 22 Nov '21

22 Nov '21

Hi, I don't have any experience in kubernetes yet, my goal in the present is to test that the auto-sacele of a kubernetes cluster is working properly using magnum. I followed some tutorials to get the test done. I tried to configure the test but I had problems with magnum-metrics-server not being able to provide metrics, after digging and reading a lot of things on the web, I found out that kubernetes master couldn't connect to the metrics server (curl -k https://ip_metrics_server didn't work) So I created another template but this time using calico as a network provider, and this time it worked. How can I find why flannel does not work? where should I look? Regards.

2 1

[neutron] Bug deputy report (Nov 15 - 21)
by Hongbin Lu 21 Nov '21

21 Nov '21

Hi, I am the bug deputy this week. Please find the report below: High * https://bugs.launchpad.net/neutron/+bug/1951010 Restarting Neutron floods Nova with segment aggregates calls * https://bugs.launchpad.net/neutron/+bug/1951225 [OVN] Agent can't be found in functional test sometimes Medium * https://bugs.launchpad.net/neutron/+bug/1951149 [OVN] If "chassis" register is deleted, "chassis_private" can have 0 "chassis" associated * https://bugs.launchpad.net/neutron/+bug/1951559 [OVN] Router ports gateway_mtu option should not always be set * https://bugs.launchpad.net/neutron/+bug/1951564 snat random-fully supported with iptables 1.6.0 Low * https://bugs.launchpad.net/neutron/+bug/1951272 [OVN] OVS to OVN migration should be stopped if OVS agent firewall is "iptables_hybrid" * https://bugs.launchpad.net/neutron/+bug/1951429 Neutron API responses should not contain tracebacks * https://bugs.launchpad.net/neutron/+bug/1951569 Undecided (might need further traiging from domain experts) * https://bugs.launchpad.net/neutron/+bug/1951074 [OVN] default setting leak nameserver config from the host to instances * https://bugs.launchpad.net/neutron/+bug/1951493 OVS DPDK restart results in that tap interfaces in network namespaces can't be opened * https://bugs.launchpad.net/neutron/+bug/1951517 Segmentation ID should be lower or equal to 4095 Best regards, Hongbin

1 0

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

19 Nov '21

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We cancelled this week's meeting due to Open Infra Keynotes at the same time. * Next week's meeting is on IRC on 25th Nov, Thursday 15:00 UTC, feel free the topic on the agenda[1] by Nov 24th. 2. What we completed this week: ========================= * Updated Yoga testing runtime [2] * Retire puppet-senlin[3] * Removed TC office hours in favour of weekly meetings [4] 3. Activities In progress: ================== TC Tracker for Yoga cycle ------------------------------ * This etherpad includes the Yoga cycle targets/working items for TC[5]. Open Reviews ----------------- * 8 open reviews for ongoing activities[6]. Fixing Zuul config error -------------------------- Clark sent a email tagging projects need action for zuul config error in their projects[7]. Please fix those config error which is not causing failure now but will fail on changes in those repo or at least is not testing what we think they are. Few projects are fixing those but still we need to clean it up completly. RBAC discussion: continuing from PTG ---------------------------------------------- We had another meeting on Wed and figured out the open question and schedule. Meeting notes are in this etherpad[8]. Final design and schedule is up in this goal rework patch[9]. Please review that and provide feedback from your project perspective. Community-wide goal updates ------------------------------------ * RBAC goal is pretty much in good shape now, feel free to review it[9] * There is one more goal proposal for 'FIPS compatibility and compliance' which needs feedback from community as well from TC[10]. * TC is working to prepare the final goal(s) soon, please wait for some more time. Adjutant need maintainers and PTLs ------------------------------------------- We received response from Braden, Albert on ML, so let's wait on the final call to help here[11]. New project 'Skyline' proposal ------------------------------------ * We discussed it in TC PTG, we are ok to have Skyline as official project but we have few open queries on gerrit and still waiting from skyline team to respond[12]. TC tags analysis ------------------- * TC agreed to remove the framework and it is communicated in ML[13]. Project updates ------------------- * Rename ‘Extended Maintenance’ SIG to the ‘Stable Maintenance’[14] * Retire training-labs repo[15] * Add ProxySQL repository for OpenStack-Ansible[16] * Retire js-openstack-lib [17] 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[18]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [19] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://review.opendev.org/c/openstack/governance/+/815851 [3] https://review.opendev.org/c/openstack/governance/+/817329 [4] https://review.opendev.org/c/openstack/governance/+/817493 [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://etherpad.opendev.org/p/policy-popup-yoga-ptg [9] https://review.opendev.org/c/openstack/governance/+/815158 [10] https://review.opendev.org/c/openstack/governance/+/816587 [11] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025786… [12] https://review.opendev.org/c/openstack/governance/+/814037 [13] http://lists.openstack.org/pipermail/openstack-discuss/2021-October/025571.… [14] https://review.opendev.org/c/openstack/governance-sigs/+/817499 [15] https://review.opendev.org/c/openstack/governance/+/817511 [16] https://review.opendev.org/c/openstack/governance/+/817245 [17] https://review.opendev.org/c/openstack/governance/+/807163 [18] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [19] http://eavesdrop.openstack.org/#Technical_Committee_Meeting-gmann

1 0

[keystone] No weekly meeting next week
by Douglas Mendizabal 19 Nov '21

19 Nov '21

Hi Keystone friends, I'll be out on PTO next week, so I'm canceling the Keystone weekly meeting for November 23. Meetings will resume the following week on November 30. Thanks, - Douglas Mendizábal (redrobot)

1 0

[requirements][keystone] pysaml2 and oslo.policy not able to be updated due to keystone test failures
by Matthew Thode 19 Nov '21

19 Nov '21

more or less as the title states the following reviews show the failures pysaml2: https://review.opendev.org/818612 oslo.policy: https://review.opendev.org/815820 -- Matthew Thode

2 1

[sdk][tc] A new home for Gophercloud
by Emilien Macchi 19 Nov '21

19 Nov '21

Hi everyone, The Gophercloud project is a stable OpenStack SDK in Golang, which has been widely used by many communities now, including Terraform and all the Kubernetes on OpenStack projects. The project was initiated by Rackspace in 2013 and has already successfully managed their departure as a principal contributor. Fast forward to 2021, Joe Topjian (major maintainer) who used to be an active contributor in Puppet modules and also a voice in the OpenStack operators space, has reached out to me so we can discuss a transition for maintenance: https://github.com/gophercloud/gophercloud/issues/2246 We have discussed this internally and here are our notes: https://github.com/gophercloud/gophercloud/issues/2246#issuecomment-9575894… . To make it short, we are figuring out whether it would make sense to find a new home for the project and if yes, where. The main reason we're reaching out to the opendev community first is because we think this is the most logical place to host the project, alongside OpenStack: Some ideas: - The project would potentially have more visibility in the community, it’s a SDK therefore strongly relying on OpenStack APIs stability. - Use (some) opendev tools, mainly Zuul & nodepool resources - integrate with other projects. - Governance: - Gerrit / not Gerrit: we don’t think we would move to Gerrit yet, as the existing contributors are probably more used to the Github workflow, and we clearly don’t want to lose anyone in the process). - IRC: we could have an IRC channel, potentially Slack as well. Many things to figure out and before we answer these questions, we would like to poll the community: what do you think? Have you contributed to the project? What's your feeling about the ideas here? We welcome any feedback and will take it in consideration in our discussions. Thanks everyone, -- Emilien Macchi, on behalf of the Gophercloud contributors

8 13

[nova][all] Adding /healthcheck support in Nova, and better healthcheck in every projects
by Thomas Goirand 19 Nov '21

19 Nov '21

Hi, About a year and a half ago, I attempted to add /healthcheck support by default in all projects. For Nova, this resulted in this patch: https://review.opendev.org/c/openstack/nova/+/724684 For other projects, it's been merged almost everywhere (I'd have to survey all project to see if that's the case, or if I still have debian specific patches somewhere). Though for Nova, this sparked a discussion where it's been said that the current implementation of /healthcheck wasn't good enough. This resulted in threads about how to better do it. Unfortunately, this blocked my patch from being merged in Nova. It is my point of view to recognize a failure here. The /healthcheck URL was added in oslo.middleware so one can use it with something like haproxy to verify that the API is up, and responds. It was never designed to check, for example, if nova-api has a valid connectivity to MySQL and RabbitMQ. Yes, this is welcome, but in the mean time, operators must tweak the default file to have a valid, useable /etc/nova/api-paste.ini. So I am hereby asking the nova team: Can we please move forward and agree that 1.5 years waiting for such a minor patch is too long, and that such patch should be approved, prior to having a better healtcheck mechanism? I don't think it's a good idea to ask Nova users to wait potentially more development cycles to have a good-by-default api-paste.ini file. At the same time, I am wondering: is anyone even working on a better healthcheck system? I haven't heard that anyone is working on this. Though it would be more than welcome. Currently, to check that a daemon is alive and well, operators are stuck with: - checking with ss if the daemon is correctly connected to a given port - check the logs for rabbitmq and mysql errors (with something like filebeat + elastic search and alarming) Clearly, this doesn't scale. When running many large OpenStack clusters, it is not trivial to have a monitoring system that works and scales. The effort to deploy such a monitoring system is also not trivial at all. So what's been discussed at the time for improving the monitoring would be very much welcome, though not only for the API service: something to check the health of other daemons would be very much welcome. I'd very much would like to participate in a Yoga effort to improve the current situation, and contribute the best I can, though I'm not sure I'd be the best person to drive this... Is there anyone else willing to work on this? Hoping this message is helpful, Cheers, Thomas Goirand (zigo)

6 9

[neutron] Drivers meeting - Friday 18.11.2021 - cancelled
by Lajos Katona 18 Nov '21

18 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

[all] tempest-integrated-compute-centos-8-stream job is failing
by Balazs Gibizer 18 Nov '21

18 Nov '21

Hi, The centos 8 stream job is failing in 100% of the cases with mirror issues [2]. You probably need to hold you recheck until it is resolved. cheers, gibi [1] https://zuul.opendev.org/t/openstack/builds?job_name=tempest-integrated-com… [2] https://zuul.opendev.org/t/openstack/build/67dc088859d1435c9a5097e7469e5c12…

3 5

[all][sdk][neutronclient][neutron] List of projects that use python-neutronclient as "client"
by Lajos Katona 18 Nov '21

18 Nov '21

Hi, During the Yoga PTG we discussed the possibility of deprecating python-neutronclient (see [0]). The CLI part of python-neutronclient is already deprecated (see [1]), but we have python bindings for Neutron both in python-neutronclient and in openstacksdk. As python-neutronclient's binding code is widely used as "client" code (i.e.: Heat, Horizon, Nova), but python-openstackclient uses openstacksdk's binding code for "client" this means duplicated work and maintenance for all the bindings. If we have a new API feature the binding code must go both to python-neutronclient to make it available in Heat, and to openstacksdk to have openstackclient support for it. The best would be to have the binding code in openstacksdk and deprecate python-neutronclient, but before we plan anything we would like to have a list of projects that depend on python-neutronclient. We identified a few but for sure with python-neutronclient's long history there are a lot more: * Heat * Horizon * Nova * various Networking projects * ...... Please share Your thoughts about this topic and the projects which use python-neutronclient, it would be really helpful to see how we can move forward. [0]: https://etherpad.opendev.org/p/neutron-yoga-ptg#L372 [1]: https://review.opendev.org/c/openstack/python-neutronclient/+/795475 Regards Lajos Katona (lajoskatona)

1 0

[sdk]: Check instance error message
by dmeng 17 Nov '21

17 Nov '21

Hello there, Hope everything is going well. I'm wondering if there is any method that could check the error message of an instance 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 of an instance. Thanks and have a great day! Catherine

3 3

[cinder] yoga R-17 virtual midcycle on 1 december
by Brian Rosmaita 17 Nov '21

17 Nov '21

As decided at today's weekly meeting, the Cinder Yoga R-17 virtual midcycle will be held: DATE: Wednesday 1 December 2021 TIME: 1400-1600 UTC LOCATION: https://bluejeans.com/3228528973 The meeting will be recorded. Please add topics to the midcycle etherpad: https://etherpad.opendev.org/p/cinder-yoga-midcycles cheers, brian

1 0

[tacker] Skip next IRC meeting
by Yasufumi Ogawa 17 Nov '21

17 Nov '21

Hi team, Due to my absence from work, I would like to skip the next IRC meeting on November 23. Thanks, Yasufumi

1 0

[barbican] No weekly meeting next week
by Douglas Mendizabal 17 Nov '21

17 Nov '21

Hi Barbicaneers, I'll be out on PTO next week, so I'm canceling the Barbican weekly meeting for November 23. Meeting will resume the following week on November 30. Thanks, - Douglas Mendizábal (redrobot)

1 0

[all] git-review broken by git version 2.34.0
by Pierre Riteau 17 Nov '21

17 Nov '21

Hello, I recently upgraded to the latest git release 2.34.0 and noticed it breaks git-review (output below is with -v): Errors running git rebase -p -i remotes/gerrit/stable/xena fatal: --preserve-merges was replaced by --rebase-merges I submitted a patch [1], but since it would break compatibility with git versions older than 2.18 that don't support the --rebase-merges (-r) option, it may need to be refined before being merged. Cheers, Pierre [1] https://review.opendev.org/c/opendev/git-review/+/818219

2 2

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

17 Nov '21

No meeting today :( This is a bug report from 11-10-2021 to 11-17-2021. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- High - https://bugs.launchpad.net/cinder/+bug/1950474 "Xena accept transfer policy breaks volume transfer workflow". Unassigned. Medium - https://bugs.launchpad.net/cinder/+bug/1950291 "tempest-integrated-compute-centos-8-stream fails with version conflict in boto3". Unassigned. - https://bugs.launchpad.net/cinder/+bug/1951163 "Unable to import/manage an encrypted volume". Unassigned. - https://bugs.launchpad.net/cinder/+bug/1951046 "DS8000 driver terminates volume connection when there still has volume attached to instances - Ussuri". Unassigned. Cheers, -- Sofía Enriquez she/her Software Engineer Red Hat PnT <https://www.redhat.com> IRC: @enriquetaso @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com> -- 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

[nova] weird python stacktrace in nova-compute
by Arnaud Morin 17 Nov '21

17 Nov '21

Hey all, We have some python stacktrace in our nova-compute journalctl logs, which looks like that: $ journalctl -u nova-compute ... Nov 01 09:04:03 host1234 python3[161354]: Exception in thread tpool_thread_6: Nov 01 09:04:03 host1234 python3[161354]: Traceback (most recent call last): Nov 01 09:04:03 host1234 python3[161354]: File "/opt/openstack/nova/lib/python3.6/threading.py", line 916, in _bootstrap_inner Nov 01 09:04:03 host1234 python3[161354]: self.run() Nov 01 09:04:03 host1234 python3[161354]: File "/opt/openstack/nova/lib/python3.6/threading.py", line 864, in run Nov 01 09:04:03 host1234 python3[161354]: self._target(*self._args, **self._kwargs) Nov 01 09:04:03 host1234 python3[161354]: File "/opt/openstack/nova/lib/python3.6/site-packages/eventlet/tpool.py", line 96, in tworker Nov 01 09:04:03 host1234 python3[161354]: _wsock.sendall(_bytetosend) Nov 01 09:04:03 host1234 python3[161354]: TimeoutError: [Errno 110] Connection timed out Nov 01 09:04:03 host1234 python3[161354]: Traceback (most recent call last): Nov 01 09:04:03 host1234 python3[161354]: File "/opt/openstack/nova/lib/python3.6/site-packages/eventlet/hubs/poll.py", line 109, in wait Nov 01 09:04:03 host1234 python3[161354]: listener.cb(fileno) Nov 01 09:04:03 host1234 python3[161354]: File "/opt/openstack/nova/lib/python3.6/site-packages/eventlet/tpool.py", line 58, in tpool_trampoline Nov 01 09:04:03 host1234 python3[161354]: assert _c Nov 01 09:04:03 host1234 python3[161354]: AssertionError Nov 01 09:04:03 host1234 python3[161354]: Removing descriptor: 16 ... After this, nova-compute is "stuck" and does nothing more, but still continue to answer on RPC (it is still up in nova services) We am not experts of python threading / eventlet stuff, and we have no idea how to debug this. Our current solution is to restart nova-compute, but it's more a dirty workaround than a real fix. Does it ring a bell to someone in the community? Cheers, Arnaud

1 0

[edge][neutron][all] Edge related documentation
by Lajos Katona 16 Nov '21

16 Nov '21

Hi, During Yoga PTG the Neutron team had a very useful discussion together with some Designate folks, see the etherpad [1]. >From Neutron team's perspective the task is to document how to set up an edge site with AZ, DNS.... etc. This is a cross project effort (even if just do it for Neutron-Designate today), is there a place for such documentation? [1]: https://etherpad.opendev.org/p/octavia-designate-neutron-ptg#L16

1 0

[cinder][rbd] festival of RBD driver reviews 11 november 1500 utc
by Brian Rosmaita 16 Nov '21

16 Nov '21

By popular demand (really!), I'm scheduling a RBD driver review festival for next week. It's a community driver, and we've got a backlog of patches: https://review.opendev.org/q/project:openstack/cinder+status:open+file:cind… If your patch is currently in merge conflict, it would be helpful if you could get conflicts resolved before the festival. Also, if you have questions about comments that have been left on your patch, this would be a good time to get them answered. who: Everyone! what: The Cinder Festival of RBD Driver Reviews when: Thursday 11 November 2021 from 1500-1600 UTC where: https://meet.google.com/fsb-qkfc-qun etherpad: https://etherpad.opendev.org/p/cinder-festival-of-driver-reviews (Note that we're trying google meet for this session.)

3 3

[ Tacker ] Passing a shell script/parameters as a file in cloud config
by Lokendra Rathour 16 Nov '21

16 Nov '21

Hi, *In Tacker, while deploying VNFD can we pass a file ( parameter file) and keep it at a defined path using cloud-config way?* Like in *generic hot template*s, we have the below-mentioned way to pass a file directly as below: parameters: foo: default: bar resources: the_server: type: OS::Nova::Server properties: # flavor, image etc user_data: str_replace: template: {get_file: the_server_boot.sh} params: $FOO: {get_param: foo} *but when using this approach in Tacker BaseHOT it gives an error saying * "nstantiation wait failed for vnf 77693e61-c80e-41e0-af9a-a0f702f3a9a7, error: VNF Create Resource CREATE failed: resources.obsvrnnu62mb: resources.CAS_0_group.Property error: resources.soft_script.properties.config: No content found in the "files" section for get_file path: Files/scripts/install.py 2021-10-28 00:46:35.677 3853831 ERROR oslo_messaging.rpc.server " do we have a defined way to use the hot capability in TACKER? Defined Folder Structure for CSAR: . ├── BaseHOT │ └── default │ ├── RIN_vnf_hot.yaml │ └── nested │ ├── RIN_0.yaml │ └── RIN_1.yaml ├── Definitions │ ├── RIN_df_default.yaml │ ├── RIN_top_vnfd.yaml │ ├── RIN_types.yaml │ ├── etsi_nfv_sol001_common_types.yaml │ └── etsi_nfv_sol001_vnfd_types.yaml ├── Files │ ├── images │ └── scripts │ └── install.py ├── Scripts ├── TOSCA-Metadata │ └── TOSCA.meta ├── UserData │ ├── __init__.py │ └── lcm_user_data.py *Objective: * To pass a file at a defined path on the VDU after the VDU is instantiated/launched. -- ~ Lokendra skype: lokendrarathour

2 3

Error while getting network agents
by Muhammad Faisal 16 Nov '21

16 Nov '21

Hi, While executing openstack network agent list we are getting below mentioned error. We have run "ovn-sbctl chassis-del 650be87c-b581-467a-b523-ce454e753780" command on controller node. OS: Ubuntu 20 Openstack version: Wallaby Number of controller/network node: 1 (172.16.30.46) Number of compute node: 2 (172.16.30.1, 172.16.30.3) OVN Version: 21.09.0 /var/log/ovn/ovn-northd.log: 2021-11-15T15:29:22.184Z|00053|northd|WARN|Dropped 7 log messages in last 127 seconds (most recently, 120 seconds ago) due to excessive rate 2021-11-15T15:29:22.184Z|00054|northd|WARN|Chassis does not exist for Chassis_Private record, name: 7d07ed32-996f-48da-9ac1-7f0455ea7ec7 2021-11-15T15:31:11.516Z|00055|northd|WARN|Dropped 14 log messages in last 110 seconds (most recently, 52 seconds ago) due to excessive rate 2021-11-15T15:31:11.516Z|00056|northd|WARN|Chassis does not exist for Chassis_Private record, name: 7d07ed32-996f-48da-9ac1-7f0455ea7ec7 2021-11-15T15:35:25.738Z|00057|northd|WARN|Dropped 6 log messages in last 254 seconds (most recently, 243 seconds ago) due to excessive rate 2021-11-15T15:35:25.738Z|00058|northd|WARN|Chassis does not exist for Chassis_Private record, name: 7d07ed32-996f-48da-9ac1-7f0455ea7ec7 2021-11-15T15:44:34.663Z|00059|northd|WARN|Dropped 12 log messages in last 549 seconds (most recently, 512 seconds ago) due to excessive rate 2021-11-15T15:44:34.663Z|00060|northd|WARN|Chassis does not exist for Chassis_Private record, name: 7d07ed32-996f-48da-9ac1-7f0455ea7ec7 2021-11-15T15:47:39.947Z|00061|northd|WARN|Dropped 2 log messages in last 185 seconds (most recently, 185 seconds ago) due to excessive rate 2021-11-15T15:47:39.948Z|00062|northd|WARN|Chassis does not exist for Chassis_Private record, name: 7d07ed32-996f-48da-9ac1-7f0455ea7ec7 /var/log/neutron/neutron-server.log: 2021-11-15 20:55:24.025 678149 DEBUG futurist.periodics [req-df627767-441c-4b46-8487-91604cd3033a - - - - -] Submitting periodic callback 'neutron.plugins.ml2.drivers.ovn.mech_driver.ovsdb.maintenance.HashRingHealt hCheckPeriodics.touch_hash_ring_nodes' _process_scheduled /usr/lib/python3/dist-packages/futurist/periodics.py:641 2021-11-15 20:55:30.531 678146 DEBUG neutron.wsgi [-] (678146) accepted ('172.16.30.46', 49782) server /usr/lib/python3/dist-packages/eventlet/wsgi.py:992 2021-11-15 20:55:30.893 678146 DEBUG ovsdbapp.backend.ovs_idl.transaction [req-04604530-8f57-428b-8359-e1bd2648d417 - - - - -] Running txn n=1 command(idx=0): CheckLivenessCommand() do_commit /usr/lib/python3/dist-packages/ovsdbapp/backend/ovs_idl/transaction.py:90 2021-11-15 20:55:30.925 678146 DEBUG neutron.plugins.ml2.drivers.ovn.mech_driver.ovsdb.ovsdb_monitor [req-04604530-8f57-428b-8359-e1bd2648d417 - - - - -] Hash Ring: Node 8318cb4d-c002-41f2-a17d-bb33d35d8b99 (host: controller-khi01) handling event "update" for row b4926d80-2c2a-488f-bd27-49c7191f0c3a (table: NB_Global) notify /usr/lib/python3/dist-packages/neutron/plugins/ml2/drivers/ovn/mech_driver/o vsdb/ovsdb_monitor.py:666 2021-11-15 20:55:30.927 678147 DEBUG neutron.plugins.ml2.drivers.ovn.mech_driver.ovsdb.ovsdb_monitor [-] ChassisAgentWriteEvent : Matched Chassis_Private, update, None None matches /usr/lib/python3/dist-packages/neutron/plugins/ml2/drivers/ovn/mech_driver/o vsdb/ovsdb_monitor.py:61 2021-11-15 20:55:30.930 678147 DEBUG neutron.plugins.ml2.drivers.ovn.mech_driver.ovsdb.ovsdb_monitor [-] ChassisMetadataAgentWriteEvent : Matched Chassis_Private, update, None None matches /usr/lib/python3/dist-packages/neutron/plugins/ml2/drivers/ovn/mech_driver/o vsdb/ovsdb_monitor.py:61 2021-11-15 20:55:30.931 678146 DEBUG neutron.plugins.ml2.drivers.ovn.mech_driver.ovsdb.ovsdb_monitor [req-04604530-8f57-428b-8359-e1bd2648d417 - - - - -] Hash Ring: Node 8318cb4d-c002-41f2-a17d-bb33d35d8b99 (host: controller-khi01) handling event "update" for row b4926d80-2c2a-488f-bd27-49c7191f0c3a (table: NB_Global) notify /usr/lib/python3/dist-packages/neutron/plugins/ml2/drivers/ovn/mech_driver/o vsdb/ovsdb_monitor.py:666 2021-11-15 20:55:30.934 678146 DEBUG neutron.plugins.ml2.drivers.ovn.mech_driver.ovsdb.ovsdb_monitor [req-04604530-8f57-428b-8359-e1bd2648d417 - - - - -] Hash Ring: Node 8318cb4d-c002-41f2-a17d-bb33d35d8b99 (host: controller-khi01) handling event "update" for row b4926d80-2c2a-488f-bd27-49c7191f0c3a (table: NB_Global) notify /usr/lib/python3/dist-packages/neutron/plugins/ml2/drivers/ovn/mech_driver/o vsdb/ovsdb_monitor.py:666 2021-11-15 20:55:30.936 678146 ERROR neutron.api.v2.resource [req-db3a5256-a3de-41a9-a135-710ce024a698 92e064e5e77c4e32b97e6c056a86c5eb 7eb59a51503f48ddbc936c40990e2177 - default default] index failed: No details.: AttributeError: 'Chassis_Private' object has no attribute 'hostname' 2021-11-15 20:55:30.936 678146 ERROR neutron.api.v2.resource Traceback (most recent call last): 2021-11-15 20:55:30.936 678146 ERROR neutron.api.v2.resource File "/usr/lib/python3/dist-packages/neutron/api/v2/resource.py", line 98, in resource 2021-11-15 20:55:30.936 678146 ERROR neutron.api.v2.resource result = method(request=request, **args) 2021-11-15 20:55:30.936 678146 ERROR neutron.api.v2.resource File "/usr/lib/python3/dist-packages/neutron_lib/db/api.py", line 139, in wrapped 2021-11-15 20:55:30.936 678146 ERROR neutron.api.v2.resource setattr(e, '_RETRY_EXCEEDED', True) 2021-11-15 20:55:30.936 678146 ERROR neutron.api.v2.resource File "/usr/lib/python3/dist-packages/oslo_utils/excutils.py", line 227, in __exit__ 2021-11-15 20:55:30.936 678146 ERROR neutron.api.v2.resource self.force_reraise() 2021-11-15 20:55:30.936 678146 ERROR neutron.api.v2.resource File "/usr/lib/python3/dist-packages/oslo_utils/excutils.py", line 200, in force_reraise 2021-11-15 20:55:30.936 678146 ERROR neutron.api.v2.resource raise self.value 2021-11-15 20:55:30.936 678146 ERROR neutron.api.v2.resource File "/usr/lib/python3/dist-packages/neutron_lib/db/api.py", line 135, in wrapped 2021-11-15 20:55:30.936 678146 ERROR neutron.api.v2.resource return f(*args, **kwargs) 2021-11-15 20:55:30.936 678146 ERROR neutron.api.v2.resource File "/usr/lib/python3/dist-packages/oslo_db/api.py", line 154, in wrapper 2021-11-15 20:55:30.936 678146 ERROR neutron.api.v2.resource ectxt.value = e.inner_exc 2021-11-15 20:55:30.936 678146 ERROR neutron.api.v2.resource File "/usr/lib/python3/dist-packages/oslo_utils/excutils.py", line 227, in __exit__ 2021-11-15 20:55:30.936 678146 ERROR neutron.api.v2.resource self.force_reraise() 2021-11-15 20:55:30.936 678146 ERROR neutron.api.v2.resource File "/usr/lib/python3/dist-packages/oslo_utils/excutils.py", line 200, in force_reraise 2021-11-15 20:55:30.936 678146 ERROR neutron.api.v2.resource raise self.value 2021-11-15 20:55:30.936 678146 ERROR neutron.api.v2.resource File "/usr/lib/python3/dist-packages/oslo_db/api.py", line 142, in wrapper 2021-11-15 20:55:30.936 678146 ERROR neutron.api.v2.resource return f(*args, **kwargs) 2021-11-15 20:55:30.936 678146 ERROR neutron.api.v2.resource File "/usr/lib/python3/dist-packages/neutron_lib/db/api.py", line 183, in wrapped 2021-11-15 20:55:30.936 678146 ERROR neutron.api.v2.resource LOG.debug("Retry wrapper got retriable exception: %s", e) 2021-11-15 20:55:30.936 678146 ERROR neutron.api.v2.resource File "/usr/lib/python3/dist-packages/oslo_utils/excutils.py", line 227, in __exit__ 2021-11-15 20:55:30.936 678146 ERROR neutron.api.v2.resource self.force_reraise() 2021-11-15 20:55:30.936 678146 ERROR neutron.api.v2.resource File "/usr/lib/python3/dist-packages/oslo_utils/excutils.py", line 200, in force_reraise 2021-11-15 20:55:30.936 678146 ERROR neutron.api.v2.resource raise self.value 2021-11-15 20:55:30.936 678146 ERROR neutron.api.v2.resource File "/usr/lib/python3/dist-packages/neutron_lib/db/api.py", line 179, in wrapped 2021-11-15 20:55:30.936 678146 ERROR neutron.api.v2.resource return f(*dup_args, **dup_kwargs) 2021-11-15 20:55:30.936 678146 ERROR neutron.api.v2.resource File "/usr/lib/python3/dist-packages/neutron/api/v2/base.py", line 369, in index 2021-11-15 20:55:30.936 678146 ERROR neutron.api.v2.resource return self._items(request, True, parent_id) 2021-11-15 20:55:30.936 678146 ERROR neutron.api.v2.resource File "/usr/lib/python3/dist-packages/neutron/api/v2/base.py", line 304, in _items 2021-11-15 20:55:30.936 678146 ERROR neutron.api.v2.resource obj_list = obj_getter(request.context, **kwargs) 2021-11-15 20:55:30.936 678146 ERROR neutron.api.v2.resource File "/usr/lib/python3/dist-packages/neutron/plugins/ml2/drivers/ovn/mech_driver/ mech_driver.py", line 1118, in fn 2021-11-15 20:55:30.936 678146 ERROR neutron.api.v2.resource return op(results, new_method(*args, _driver=self, **kwargs)) 2021-11-15 20:55:30.936 678146 ERROR neutron.api.v2.resource File "/usr/lib/python3/dist-packages/neutron/plugins/ml2/drivers/ovn/mech_driver/ mech_driver.py", line 1182, in get_agents 2021-11-15 20:55:30.936 678146 ERROR neutron.api.v2.resource agent_dict = agent.as_dict() 2021-11-15 20:55:30.936 678146 ERROR neutron.api.v2.resource File "/usr/lib/python3/dist-packages/neutron/plugins/ml2/drivers/ovn/agent/neutro n_agent.py", line 59, in as_dict 2021-11-15 20:55:30.936 678146 ERROR neutron.api.v2.resource 'host': self.chassis.hostname, 2021-11-15 20:55:30.936 678146 ERROR neutron.api.v2.resource AttributeError: 'Chassis_Private' object has no attribute 'hostname' 2021-11-15 20:55:30.936 678146 ERROR neutron.api.v2.resource 2021-11-15 20:55:30.937 678146 INFO neutron.wsgi [req-db3a5256-a3de-41a9-a135-710ce024a698 92e064e5e77c4e32b97e6c056a86c5eb 7eb59a51503f48ddbc936c40990e2177 - default default] 172.16.30.46 "GET /v2.0/agents HTTP/1.1" status: 500 len: 368 time: 0.4032691 2021-11-15 20:55:30.938 678146 DEBUG neutron.plugins.ml2.drivers.ovn.mech_driver.ovsdb.ovsdb_monitor [req-5efca86e-8945-43c5-a492-76e8ad16ef6e - - - - -] Hash Ring: Node 8318cb4d-c002-41f2-a17d-bb33d35d8b99 (host: controller-khi01) handling event "update" for row 2bd437c4-9173-4d1b-ad01-d27cf0a11c8a (table: SB_Global) notify /usr/lib/python3/dist-packages/neutron/plugins/ml2/drivers/ovn/mech_driver/o vsdb/ovsdb_monitor.py:666 2021-11-15 20:55:30.939 678146 DEBUG neutron.plugins.ml2.drivers.ovn.mech_driver.ovsdb.ovsdb_monitor [req-5efca86e-8945-43c5-a492-76e8ad16ef6e - - - - -] ChassisAgentWriteEvent : Matched Chassis_Private, update, None None matches /usr/lib/python3/dist-packages/neutron/plugins/ml2/drivers/ovn/mech_driver/o vsdb/ovsdb_monitor.py:61 2021-11-15 20:55:30.939 678146 DEBUG neutron.plugins.ml2.drivers.ovn.mech_driver.ovsdb.ovsdb_monitor [req-5efca86e-8945-43c5-a492-76e8ad16ef6e - - - - -] Hash Ring: Node 8318cb4d-c002-41f2-a17d-bb33d35d8b99 (host: controller-khi01) handling event "update" for row 03ce3887-1007-48fa-9f40-b2fe88246a69 (table: Chassis_Private) notify /usr/lib/python3/dist-packages/neutron/plugins/ml2/drivers/ovn/mech_driver/o vsdb/ovsdb_monitor.py:666 2021-11-15 20:55:30.940 678146 DEBUG neutron.plugins.ml2.drivers.ovn.mech_driver.ovsdb.ovsdb_monitor [req-5efca86e-8945-43c5-a492-76e8ad16ef6e - - - - -] ChassisMetadataAgentWriteEvent : Matched Chassis_Private, update, None None matches /usr/lib/python3/dist-packages/neutron/plugins/ml2/drivers/ovn/mech_driver/o vsdb/ovsdb_monitor.py:61 2021-11-15 20:55:30.940 678146 DEBUG neutron.plugins.ml2.drivers.ovn.mech_driver.ovsdb.ovsdb_monitor [req-5efca86e-8945-43c5-a492-76e8ad16ef6e - - - - -] Hash Ring: Node 8318cb4d-c002-41f2-a17d-bb33d35d8b99 (host: controller-khi01) handling event "update" for row 03ce3887-1007-48fa-9f40-b2fe88246a69 (table: Chassis_Private) notify /usr/lib/python3/dist-packages/neutron/plugins/ml2/drivers/ovn/mech_driver/o vsdb/ovsdb_monitor.py:666 2021-11-15 20:55:37.389 678146 INFO neutron.wsgi [req-85f09a48-f50f-4776-b110-5d07dd1dc39e 9888a6e6da764fd28a72b1a7b25b8967 3e076bf2747b40ed8792ebf85d14d719 - default default] 172.16.30.3 "GET /v2.0/ports?device_id=21999c50-740c-4a26-970b-8e07ba37b5ac&fields=binding%3A host_id&fields=binding%3Avif_type HTTP/1.1" status: 200 len: 271 time: 0.0680673 2021-11-15 20:55:37.476 678146 DEBUG neutron.pecan_wsgi.hooks.policy_enforcement [req-4099412f-d724-48d7-8786-add0c5b47f56 9888a6e6da764fd28a72b1a7b25b8967 3e076bf2747b40ed8792ebf85d14d719 - default default] Attributes excluded by policy engine: ['standard_attr_id'] _exclude_attributes_by_policy /usr/lib/python3/dist-packages/neutron/pecan_wsgi/hooks/policy_enforcement.p y:255 2021-11-15 20:55:37.477 678146 INFO neutron.wsgi [req-4099412f-d724-48d7-8786-add0c5b47f56 9888a6e6da764fd28a72b1a7b25b8967 3e076bf2747b40ed8792ebf85d14d719 - default default] 172.16.30.3 "GET /v2.0/ports?tenant_id=7eb59a51503f48ddbc936c40990e2177&device_id=21999c50-74 0c-4a26-970b-8e07ba37b5ac HTTP/1.1" status: 200 len: 1175 time: 0.0565202 2021-11-15 20:55:37.618 678146 DEBUG neutron.pecan_wsgi.hooks.policy_enforcement [req-eebf3e86-206a-45ed-92f3-804007a39cca 9888a6e6da764fd28a72b1a7b25b8967 3e076bf2747b40ed8792ebf85d14d719 - default default] Attributes excluded by policy engine: ['standard_attr_id', 'vlan_transparent'] _exclude_attributes_by_policy /usr/lib/python3/dist-packages/neutron/pecan_wsgi/hooks/policy_enforcement.p y:255 2021-11-15 20:55:37.619 678146 INFO neutron.wsgi [req-eebf3e86-206a-45ed-92f3-804007a39cca 9888a6e6da764fd28a72b1a7b25b8967 3e076bf2747b40ed8792ebf85d14d719 - default default] 172.16.30.3 "GET /v2.0/networks?id=ed4ee148-2562-41ed-93ac-7341948ac4dc HTTP/1.1" status: 200 len: 904 time: 0.1111536 2021-11-15 20:55:37.674 678146 INFO neutron.wsgi [req-71885d0c-4aa2-4377-a014-33768c9160ae 9888a6e6da764fd28a72b1a7b25b8967 3e076bf2747b40ed8792ebf85d14d719 - default default] 172.16.30.3 "GET /v2.0/floatingips?fixed_ip_address=192.168.100.199&port_id=f9c17ae5-c07b-441 1-a0be-551686e6ba8e HTTP/1.1" status: 200 len: 217 time: 0.0442567 2021-11-15 20:55:37.727 678146 DEBUG neutron.pecan_wsgi.hooks.policy_enforcement [req-d35a3b5e-82ea-4e80-b1c6-c8b39205a1f7 9888a6e6da764fd28a72b1a7b25b8967 3e076bf2747b40ed8792ebf85d14d719 - default default] Attributes excluded by policy engine: ['standard_attr_id', 'shared'] _exclude_attributes_by_policy /usr/lib/python3/dist-packages/neutron/pecan_wsgi/hooks/policy_enforcement.p y:255 2021-11-15 20:55:37.731 678146 INFO neutron.wsgi [req-d35a3b5e-82ea-4e80-b1c6-c8b39205a1f7 9888a6e6da764fd28a72b1a7b25b8967 3e076bf2747b40ed8792ebf85d14d719 - default default] 172.16.30.3 "GET /v2.0/subnets?id=74e3b294-5fcc-4685-8bc4-5200be3af09e HTTP/1.1" status: 200 len: 858 time: 0.0468309 2021-11-15 20:55:37.774 678146 INFO neutron.wsgi [req-7a57b86f-75bf-4381-9447-0b1d7262aae8 9888a6e6da764fd28a72b1a7b25b8967 3e076bf2747b40ed8792ebf85d14d719 - default default] 172.16.30.3 "GET /v2.0/ports?network_id=ed4ee148-2562-41ed-93ac-7341948ac4dc&device_owner=net work%3Adhcp HTTP/1.1" status: 200 len: 210 time: 0.0335791 2021-11-15 20:55:37.891 678146 INFO neutron.wsgi [req-7cf3c09b-b5ee-4372-84c2-d738abd1a47a 9888a6e6da764fd28a72b1a7b25b8967 3e076bf2747b40ed8792ebf85d14d719 - default default] 172.16.30.3 "GET /v2.0/networks/ed4ee148-2562-41ed-93ac-7341948ac4dc?fields=segments HTTP/1.1" status: 200 len: 212 time: 0.1059954 2021-11-15 20:55:37.991 678146 INFO neutron.wsgi [req-3ed1edbd-9f33-4b4e-89c8-a2291f23e8ef 9888a6e6da764fd28a72b1a7b25b8967 3e076bf2747b40ed8792ebf85d14d719 - default default] 172.16.30.3 "GET /v2.0/networks/ed4ee148-2562-41ed-93ac-7341948ac4dc?fields=provider%3Aphysic al_network&fields=provider%3Anetwork_type HTTP/1.1" status: 200 len: 277 time: 0.0903363 2021-11-15 20:55:49.083 678146 INFO neutron.wsgi [req-0328379e-d381-48be-a209-a94acc297baa 9888a6e6da764fd28a72b1a7b25b8967 3e076bf2747b40ed8792ebf85d14d719 - default default] 172.16.30.1 "GET /v2.0/ports?device_id=82e90d49-bbc4-4c2c-8ae1-7a4bcf84bb7d&fields=binding%3A host_id&fields=binding%3Avif_type HTTP/1.1" status: 200 len: 271 time: 0.2884536

3 2

[Triple0] Gate blocker - standalone failures on master and wallaby
by Ronelle Landy 16 Nov '21

16 Nov '21

Hello All, We have a check/gate blocker on master and wallaby that started on Saturday. Standalone jobs are failing tempest tests. The related bug is linked below: https://bugs.launchpad.net/tripleo/+bug/1950916 The networking team is helping debug this. Please don't recheck for now. We will update this list when we have more info/a fix. Thank you!

1 2

[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