- openstack-discuss - lists.openstack.org

[Openstack-victoria] [LIBVIRT] Live migration doesn't work, error in libvirt
by Swogat Pradhan 17 Oct '21

17 Oct '21

Hi, I am using openstack victoria and i am facing an issue when using the live-migration feature. After choosing the live-migration of an instance from Compute1 to compute2 i am getting an error in nova-compute.log (of compute 1) stating: *ERROR nova.virt.libvirt.driver [-] [instance: 59c95d46-2cbc-4787-89f7-8b36b826ffad] Live Migration failure: operation failed: Failed to connect to remote libvirt URI qemu+tcp://compute2/system: unable to connect to server at 'compute2:16509': Connection refused: libvirt.libvirtError: operation failed: Failed to connect to remote libvirt URI qemu+tcp://compute2/system: unable to connect to server at 'compute2:16509': Connection refused* Which states that the libvirtd.tcp socket is not running (libvirtd should run on 16509 port inorder for live-migration to succeed). Journalctl -xe output *Oct 18 06:32:52 compute2 systemd[1]: libvirtd-tcp.socket: Socket service libvirtd.service already active, refusing.Oct 18 06:32:52 compute2 systemd[1]: Failed to listen on Libvirt non-TLS IP socket.* I am trying to solve the above issue by adding --listen in the libvirtd_opts parameter in the service file and also in the /etc/default/libvirtd file. But after doing that the libvirtd service doesn't start. Can someone suggest a way forward for this? Thank you With regards, Swogat Pradhan

1 1

Re: The best linux distribution on which to deploy Openstack
by Radosław Piliszek 17 Oct '21

17 Oct '21

On Sun, 17 Oct 2021 at 10:03, A Monster <amonster369(a)gmail.com> wrote: > > What about Centos 7 , what are the openstack releases that it supports ? You have said that already. Train is the latest release on CentOS 7. -yoctozepto > On Sun, 17 Oct 2021 at 08:19, Radosław Piliszek <radoslaw.piliszek(a)gmail.com> wrote: >> >> On Sat, 16 Oct 2021 at 22:46, A Monster <amonster369(a)gmail.com> wrote: >> > >> > As a centos 7 user I have many experience using this distribution however centos 7 doesn't support the newest openstack releases ( after train ) and centos 8 will soon lose the support from Redhat since it's EOL is scheduled for 31/12/2021 and the centos stream distributions are upstreams for RHEL therefor is most likely unstable. >> > >> > So which distribution should I use ? >> >> Use the one that you are most familiar/comfortable with and that is >> supported by OpenStack deployment projects. >> >> For example, with Kolla Ansible, at the moment, you can choose from >> CentOS Stream 8, Debian Bullseye and Ubuntu 20.04 (sorted >> alphabetically; all have equal support). >> Soon, it will support Rocky Linux 8 as well (and then newer releases >> as they start coming). >> >> Kolla Ansible docs for Xena: https://docs.openstack.org/kolla-ansible/xena/ >> >> -yoctozepto

1 0

The best linux distribution on which to deploy Openstack
by A Monster 17 Oct '21

17 Oct '21

As a centos 7 user I have many experience using this distribution however centos 7 doesn't support the newest openstack releases ( after train ) and centos 8 will soon lose the support from Redhat since it's EOL is scheduled for 31/12/2021 and the centos stream distributions are upstreams for RHEL therefor is most likely unstable. So which distribution should I use ?

4 3

[dev][cinder] snapshot revert to any point
by Seena Fallah 16 Oct '21

16 Oct '21

Hi, There is a lack of feature to revert to any snapshot point in supported drivers like RBD. I've made a change to support this feature. Can someone please review them? https://review.opendev.org/c/openstack/cinder-tempest-plugin/+/812032 https://review.opendev.org/c/openstack/cinder/+/806807 Thanks

1 0

How to use hosts with no storage disks
by A Monster 15 Oct '21

15 Oct '21

In Openstack, is it possible to create compute nodes with no hard drives and use PXE in order to boot the host's system and therefore launch instances with no local drive which is needed to boot the VM's image. If not, what's the minimum storage needed to be given to hosts in order to get a fully functional system.

6 8

[release] Release countdown for week R-24, Oct 11-15
by Előd Illés 15 Oct '21

15 Oct '21

Welcome back to the release countdown emails! These will be sent at major points in the Yogadevelopment cycle, which should conclude with a final release on March 30, 2022. Development Focus ----------------- At this stage in the release cycle, focus should be on planning the Yogadevelopment cycle, assessing Yogacommunity goals and approving Yogaspecs. General Information ------------------- Yoga is a 25 weeks long development cycle.In case you haven't seen it yet, please take a look over the schedule for this release: https://releases.openstack.org/ <https://releases.openstack.org/yoga/schedule.html>yoga <https://releases.openstack.org/yoga/schedule.html>/schedule.html <https://releases.openstack.org/yoga/schedule.html> By default, the team PTL is responsible for handling the release cycle and approving release requests. This task can (and probably should) be delegated to release liaisons. Now is a good time to review release liaison information for your team and make sure it is up to date: https://opendev.org/openstack/releases/src/branch/master/data/release_liais… <https://opendev.org/openstack/releases/src/branch/master/data/release_liais…> By default, all your team deliverables from the Yogarelease are continued in Yogawith a similar release model. Upcoming Deadlines & Dates -------------------------- Yoga PTG: October 18-22 Yoga-1 milestone:November 18, 2021 Előd Illés irc: elodilles

1 0

[ironic] Yoga PTG schedule
by Iury Gregory 15 Oct '21

15 Oct '21

Hello Ironicers! In our etherpad [1] we have 18 topics for this PTG and we have a total of 11 slots. This is the proposed schedule (we will discuss in our upstream meeting on Monday). *Monday (18 Oct) - Room Juno 15:00 - 17:00 UTC* * Support OpenBMC * Persistent memory Support * Redfish Host Connection Interface * Boot from Volume + UEFI *Tuesday (19 Oct) - Room Juno 14:00 - 17:00 UTC* * Posting to placement ourselves * The rise of compossible hardware, again * Self-configuring Ironic Service * Is there any way we can drive a co-operative use mode of ironic amongst some of the users? *Wednesday (18 Oct) - Room Juno 14:00 - 16:00 UTC* * Prioritize 3rd party CI in a box * Secure RBAC items in Yoga * Bulk operations *Thursday (18 Oct) - Room Kilo 14:00 - 16:00 UTC* * having to go look at logs is an antipattern * pxe-grub * Remove instance (non-BFV, non-ramdisk) networking booting * Direct SDN Integrations *Friday (22 Oct) - Room Kilo 14:00 - 16:00 UTC* * Eliminate manual commands * Certificate Management * Stopping use of wiki.openstack.org In case we don't have enough time we can book more slots if the community is ok and the slots are available. We will also have a section in the etherpad for last-minute topics =) [1] https://etherpad.opendev.org/p/ironic-yoga-ptg -- *Att[]'sIury Gregory Melo Ferreira * *MSc in Computer Science at UFCG* *Part of the ironic-core and puppet-manager-core team in OpenStack* *Software Engineer at Red Hat Czech* *Social*: https://www.linkedin.com/in/iurygregory *E-mail: iurygregory(a)gmail.com <iurygregory(a)gmail.com>*

1 1

[nova][dev] Reattaching mediated devices to instance coming back from suspended state
by Gustavo Faganello Santos 15 Oct '21

15 Oct '21

Hello, everyone! I'm working on a solution for Nova to reattach previously used mediated devices (vGPU instances, in my case) to VMs coming back from suspension, which seems to have been left on hold in the past [1] because of an old libvirt limitation, and I'm having a bit of a hard time doing so, since I'm not too familiar with the repo. I have tried creating a function that does the opposite of the mdev detach function, but the get_all_devices method seems to return an empty list when looking for mdevs at the moment of resuming the VM. Looking at the instance's XML file, I noticed that the mdev property remains while the VM is suspended, but it disappears AFTER the whole resume function is executed. I'm failing to understand why the mdev list returns empty, even though the mdev property exists in the instance's XML, and also why the mdev is removed from the XML after the resume function is executed. With that in mind, does anyone know if there's been any attempt to solve this issue since it was left on hold? If not, is there anything I should know while I attempt to do so? Thanks in advance. Gustavo [1] https://opendev.org/openstack/nova/src/branch/master/nova/virt/libvirt/driv…

2 2

OpenStack Xena for Ubuntu 21.10 and Ubuntu 20.04 LTS
by Corey Bryant 15 Oct '21

15 Oct '21

The Ubuntu OpenStack team at Canonical is pleased to announce the general availability of OpenStack Xena on Ubuntu 21.10 (Impish Indri) and Ubuntu 20.04 LTS (Focal Fossa) via the Ubuntu Cloud Archive. Details of the Xena release can be found at: https://www.openstack.org/software/xena To get access to the Ubuntu Xena packages: == Ubuntu 21.10 == OpenStack Xena is available by default for installation on Ubuntu 21.10. == Ubuntu 20.04 LTS == The Ubuntu Cloud Archive for OpenStack Xena can be enabled on Ubuntu 20.04 by running the following command: sudo add-apt-repository cloud-archive:xena The Ubuntu Cloud Archive for Xena includes updates for: aodh, barbican, ceilometer, ceph (16.2.6), cinder, designate, designate-dashboard, dpdk (20.11.3), glance, gnocchi, heat, heat-dashboard, horizon, ironic, ironic-ui, keystone, magnum, magnum-ui, manila, manila-ui, masakari, mistral, murano, murano-dashboard, networking-arista, networking-bagpipe, networking-baremetal, networking-bgpvpn, networking-hyperv, networking-l2gw, networking-mlnx, networking-odl, networking-sfc, neutron, neutron-dynamic-routing, neutron-vpnaas, nova, octavia, octavia-dashboard, openstack-trove, openvswitch (2.16.0), ovn (21.09.0), ovn-octavia-provider, placement, sahara, sahara-dashboard, senlin, swift, trove-dashboard, vmware-nsx, vitrage, watcher, watcher-dashboard, zaqar, and zaqar-ui. For a full list of packages and versions, please refer to: https://openstack-ci-reports.ubuntu.com/reports/cloud-archive/xena_versions… == Known issues == OVN 21.09.0 coming soon: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1947003 == Reporting bugs == If you have any issues please report bugs using the ‘ubuntu-bug’ tool to ensure that bugs get logged in the right place in Launchpad: sudo ubuntu-bug nova-conductor Thank you to everyone who contributed to OpenStack Xena! Corey (on behalf of the Ubuntu OpenStack Engineering team)

1 0

[TripleO] Hackfest at the PTG on Thursday
by James Slagle 15 Oct '21

15 Oct '21

Hi TripleO, As previously mentioned, we're going to have a hackfest on Thursday next week during the PTG from 1300-1700UTC. The topic will be directord+task-core -- the proposed new task execution engine for TripleO. I've prepared an etherpad for the hackfest ahead of time: https://etherpad.opendev.org/p/tripleo-directord-hackfest There are details in the etherpad about how to set up 2 nodes for the hackfest. Virtual machines would work great for this, on any platform. I've run through it on a private OpenStack cloud, and also just using local libvirt. It would be good to get those setup ahead of the hackfest if you have time between now and Thursday. I'm looking forward to Thursday and some informal hacking! -- -- James Slagle --

1 0

[Diversity] [PTG] Diversity nd Inclusion Session at PTG
by Amy Marrich 15 Oct '21

15 Oct '21

Hi Everyone, The Diversity and Inclusion WG will be meeting during the PTG on Monday October 18th at 14:00 UTC in the Diablo room. We welcome all Open Infrastructure project to attend and we would be happy to assist you with any questions you might have in regards to the Inclusive Naming initiative that OIF began last year, We plan to do a review of the current CoC or going through the current code base for the projects to find instances where changes are needed to provide both examples and patches where appropriate to assist in these endeavours. The activities we focus on will be determined by attendance during the session, Thanks, Amy (spotz) on behalf of the Diversity and Inclusion WG

1 0

[cinder][PTG] yoga PTG schedule
by Brian Rosmaita 15 Oct '21

15 Oct '21

The Cinder project team will be meeting on Tuesday 19 October through Friday 22 October from 1300-1700 UTC. For the most part, the scheduling is flexible, and we'll discuss topics roughly in the order given on the etherpad: https://etherpad.opendev.org/p/yoga-ptg-cinder We'll try to keep the "Currently at the PTG" page updated, but you know how that goes. https://ptg.opendev.org/ptg.html For your scheduling convenience, here's an outline of the schedule in a spreadsheet: https://ethercalc.openstack.org/wfno9g46fa7p - topics in red: cross-project, so the times for those are accurate - topics in blue: participatory activities for the team - topics in green: happy hour We'll be meeting in BlueJeans (except for the happy hour, which will be in meetpad). The sessions (except for happy hour) will be recorded. Connection info is on the etherpad: https://etherpad.opendev.org/p/yoga-ptg-cinder All OpenStack community members are welcome (especially for the happy hour). Looking forward to seeing everyone next week! brian

1 0

[telemetry]Yoga vPTG
by Matthias Runge 15 Oct '21

15 Oct '21

Hello there, Next week, we’ll have PTG. There will be a telemetry session on Tuesday from 4pm to 5pm UTC. The planning ether pad used is at https://etherpad.opendev.org/p/telemetry-yoga-ptg Matthias

1 0

[wallaby][neutron][ovn] SSL connection to OVN-NB/SB OVSDB
by Faisal Sheikh 15 Oct '21

15 Oct '21

Hi, I am using Openstack Wallaby release with OVN on Ubuntu 20.04. My environment consists of 2 compute nodes and 1 controller node. ovs-vswitchd (Open vSwitch) 2.15.0 Ubuntu Kernel Version: 5.4.0-88-generic compute node1 172.16.30.1 compute node2 172.16.30.3 controller/Network node IP 172.16.30.46 I want to configure the ovn southbound and northbound database to listen on SSL connection. Set a certificate, private key, and CA certificate on both compute nodes and controller nodes in /etc/neutron/plugins/ml2/ml2_conf.ini and using string ssl:IP:Port to connect the southbound/northbound database but I am unable to establish connection on SSL. It's not connecting to ovsdb-server on 6641/6642. Error in the neutron logs is like below: 2021-10-12 17:15:27.728 50561 WARNING neutron.quota.resource_registry [req-94a8acc2-e0ca-4431-8bed-f26864e7740a - - - - -] security_group_rule is already registered 2021-10-12 17:15:27.754 50561 WARNING keystonemiddleware.auth_token [req-94a8acc2-e0ca-4431-8bed-f26864e7740a - - - - -] AuthToken middleware is set with keystone_authtoken.service_token_roles_required set to False. This is backwards compatible but deprecated behaviour. Please set this to True. 2021-10-12 17:15:27.761 50561 INFO oslo_service.service [req-94a8acc2-e0ca-4431-8bed-f26864e7740a - - - - -] Starting 1 workers 2021-10-12 17:15:27.768 50561 INFO neutron.service [req-94a8acc2-e0ca-4431-8bed-f26864e7740a - - - - -] Neutron service started, listening on 0.0.0.0:9696 2021-10-12 17:15:27.776 50561 ERROR ovsdbapp.backend.ovs_idl.idlutils [req-94a8acc2-e0ca-4431-8bed-f26864e7740a - - - - -] Unable to open stream to ssl:172.16.30.46:6641 to retrieve schema: Unknown error -1 2021-10-12 17:15:27.779 50561 CRITICAL neutron [req-94a8acc2-e0ca-4431-8bed-f26864e7740a - - - - -] Unhandled error: neutron_lib.callbacks.exceptions.CallbackFailure: Callback neutron.plugins.ml2.drivers.ovn.mech_driver.mech_driver.OVNMechanismDriver.pre_fork_initialize-373793 failed with "Could not retrieve schema from ssl:172.16.30.46:6641" 2021-10-12 17:15:27.779 50561 ERROR neutron Traceback (most recent call last): 2021-10-12 17:15:27.779 50561 ERROR neutron File "/usr/bin/neutron-server", line 10, in <module> 2021-10-12 17:15:27.779 50561 ERROR neutron sys.exit(main()) 2021-10-12 17:15:27.779 50561 ERROR neutron File "/usr/lib/python3/dist-packages/neutron/cmd/eventlet/server/__init__.py", line 19, in main 2021-10-12 17:15:27.779 50561 ERROR neutron server.boot_server(wsgi_eventlet.eventlet_wsgi_server) 2021-10-12 17:15:27.779 50561 ERROR neutron File "/usr/lib/python3/dist-packages/neutron/server/__init__.py", line 68, in boot_server 2021-10-12 17:15:27.779 50561 ERROR neutron server_func() 2021-10-12 17:15:27.779 50561 ERROR neutron File "/usr/lib/python3/dist-packages/neutron/server/wsgi_eventlet.py", line 24, in eventlet_wsgi_server 2021-10-12 17:15:27.779 50561 ERROR neutron neutron_api = service.serve_wsgi(service.NeutronApiService) 2021-10-12 17:15:27.779 50561 ERROR neutron File "/usr/lib/python3/dist-packages/neutron/service.py", line 94, in serve_wsgi 2021-10-12 17:15:27.779 50561 ERROR neutron registry.publish(resources.PROCESS, events.BEFORE_SPAWN, service) 2021-10-12 17:15:27.779 50561 ERROR neutron File "/usr/lib/python3/dist-packages/neutron_lib/callbacks/registry.py", line 60, in publish 2021-10-12 17:15:27.779 50561 ERROR neutron _get_callback_manager().publish(resource, event, trigger, payload=payload) 2021-10-12 17:15:27.779 50561 ERROR neutron File "/usr/lib/python3/dist-packages/neutron_lib/callbacks/manager.py", line 149, in publish 2021-10-12 17:15:27.779 50561 ERROR neutron return self.notify(resource, event, trigger, payload=payload) 2021-10-12 17:15:27.779 50561 ERROR neutron File "/usr/lib/python3/dist-packages/neutron_lib/db/utils.py", line 110, in _wrapped 2021-10-12 17:15:27.779 50561 ERROR neutron raise db_exc.RetryRequest(e) 2021-10-12 17:15:27.779 50561 ERROR neutron File "/usr/lib/python3/dist-packages/oslo_utils/excutils.py", line 227, in __exit__ 2021-10-12 17:15:27.779 50561 ERROR neutron self.force_reraise() 2021-10-12 17:15:27.779 50561 ERROR neutron File "/usr/lib/python3/dist-packages/oslo_utils/excutils.py", line 200, in force_reraise 2021-10-12 17:15:27.779 50561 ERROR neutron raise self.value 2021-10-12 17:15:27.779 50561 ERROR neutron File "/usr/lib/python3/dist-packages/neutron_lib/db/utils.py", line 105, in _wrapped 2021-10-12 17:15:27.779 50561 ERROR neutron return function(*args, **kwargs) 2021-10-12 17:15:27.779 50561 ERROR neutron File "/usr/lib/python3/dist-packages/neutron_lib/callbacks/manager.py", line 174, in notify 2021-10-12 17:15:27.779 50561 ERROR neutron raise exceptions.CallbackFailure(errors=errors) 2021-10-12 17:15:27.779 50561 ERROR neutron neutron_lib.callbacks.exceptions.CallbackFailure: Callback neutron.plugins.ml2.drivers.ovn.mech_driver.mech_driver.OVNMechanismDriver.pre_fork_initialize-373793 failed with "Could not retrieve schema from ssl:172.16.30.46:6641" 2021-10-12 17:15:27.779 50561 ERROR neutron 2021-10-12 17:15:27.783 50572 ERROR ovsdbapp.backend.ovs_idl.idlutils [-] Unable to open stream to ssl:172.16.30.46:6641 to retrieve schema: Unknown error -1 2021-10-12 17:15:27.784 50572 ERROR neutron_lib.callbacks.manager [-] Error during notification for neutron.plugins.ml2.drivers.ovn.mech_driver.mech_driver.OVNMechanismDriver.post_fork_initialize-373774 process, after_init: Exception: Could not retrieve schema from ssl:172.16.30.46:6641 2021-10-12 17:15:27.784 50572 ERROR neutron_lib.callbacks.manager Traceback (most recent call last): 2021-10-12 17:15:27.784 50572 ERROR neutron_lib.callbacks.manager File "/usr/lib/python3/dist-packages/neutron_lib/callbacks/manager.py", line 197, in _notify_loop 2021-10-12 17:15:27.784 50572 ERROR neutron_lib.callbacks.manager callback(resource, event, trigger, **kwargs) 2021-10-12 17:15:27.784 50572 ERROR neutron_lib.callbacks.manager File "/usr/lib/python3/dist-packages/neutron/plugins/ml2/drivers/ovn/mech_driver/mech_driver.py", line 294, in post_fork_initialize 2021-10-12 17:15:27.784 50572 ERROR neutron_lib.callbacks.manager self._wait_for_pg_drop_event() 2021-10-12 17:15:27.784 50572 ERROR neutron_lib.callbacks.manager File "/usr/lib/python3/dist-packages/neutron/plugins/ml2/drivers/ovn/mech_driver/mech_driver.py", line 357, in _wait_for_pg_drop_event 2021-10-12 17:15:27.784 50572 ERROR neutron_lib.callbacks.manager ovn_conf.get_ovn_nb_connection(), self.nb_schema_helper, self, 2021-10-12 17:15:27.784 50572 ERROR neutron_lib.callbacks.manager File "/usr/lib/python3/dist-packages/neutron/plugins/ml2/drivers/ovn/mech_driver/mech_driver.py", line 136, in nb_schema_helper 2021-10-12 17:15:27.784 50572 ERROR neutron_lib.callbacks.manager return impl_idl_ovn.OvsdbNbOvnIdl.schema_helper 2021-10-12 17:15:27.784 50572 ERROR neutron_lib.callbacks.manager File "/usr/lib/python3/dist-packages/neutron/common/utils.py", line 721, in __get__ 2021-10-12 17:15:27.784 50572 ERROR neutron_lib.callbacks.manager return self.func(owner) 2021-10-12 17:15:27.784 50572 ERROR neutron_lib.callbacks.manager File "/usr/lib/python3/dist-packages/neutron/plugins/ml2/drivers/ovn/mech_driver/ovsdb/impl_idl_ovn.py", line 102, in schema_helper 2021-10-12 17:15:27.784 50572 ERROR neutron_lib.callbacks.manager cls._schema_helper = idlutils.get_schema_helper(cls.connection_string, 2021-10-12 17:15:27.784 50572 ERROR neutron_lib.callbacks.manager File "/usr/lib/python3/dist-packages/ovsdbapp/backend/ovs_idl/idlutils.py", line 215, in get_schema_helper 2021-10-12 17:15:27.784 50572 ERROR neutron_lib.callbacks.manager return create_schema_helper(fetch_schema_json(connection, schema_name)) 2021-10-12 17:15:27.784 50572 ERROR neutron_lib.callbacks.manager File "/usr/lib/python3/dist-packages/ovsdbapp/backend/ovs_idl/idlutils.py", line 204, in fetch_schema_json 2021-10-12 17:15:27.784 50572 ERROR neutron_lib.callbacks.manager raise Exception("Could not retrieve schema from %s" % connection) 2021-10-12 17:15:27.784 50572 ERROR neutron_lib.callbacks.manager Exception: Could not retrieve schema from ssl:172.16.30.46:6641 2021-10-12 17:15:27.784 50572 ERROR neutron_lib.callbacks.manager 2021-10-12 17:15:27.787 50572 INFO neutron.wsgi [-] (50572) wsgi starting up on http://0.0.0.0:9696 2021-10-12 17:15:27.924 50572 INFO oslo_service.service [-] Parent process has died unexpectedly, exiting 2021-10-12 17:15:27.925 50572 INFO neutron.wsgi [-] (50572) wsgi exited, is_accepting=True 2021-10-12 17:15:29.709 50573 INFO neutron.common.config [-] Logging enabled! 2021-10-12 17:15:29.710 50573 INFO neutron.common.config [-] /usr/bin/neutron-server version 18.0.0 2021-10-12 17:15:29.712 50573 INFO neutron.common.config [-] Logging enabled! 2021-10-12 17:15:29.713 50573 INFO neutron.common.config [-] /usr/bin/neutron-server version 18.0.0 2021-10-12 17:15:29.899 50573 INFO keyring.backend [-] Loading KWallet 2021-10-12 17:15:29.904 50573 INFO keyring.backend [-] Loading SecretService 2021-10-12 17:15:29.907 50573 INFO keyring.backend [-] Loading Windows 2021-10-12 17:15:29.907 50573 INFO keyring.backend [-] Loading chainer 2021-10-12 17:15:29.908 50573 INFO keyring.backend [-] Loading macOS 2021-10-12 17:15:29.927 50573 INFO neutron.manager [-] Loading core plugin: ml2 2021-10-12 17:15:30.355 50573 INFO neutron.plugins.ml2.managers [-] Configured type driver names: ['flat', 'geneve'] 2021-10-12 17:15:30.357 50573 INFO neutron.plugins.ml2.drivers.type_flat [-] Arbitrary flat physical_network names allowed 2021-10-12 17:15:30.358 50573 INFO neutron.plugins.ml2.managers [-] Loaded type driver names: ['flat', 'geneve'] 2021-10-12 17:15:30.358 50573 INFO neutron.plugins.ml2.managers [-] Registered types: dict_keys(['flat', 'geneve']) 2021-10-12 17:15:30.359 50573 INFO neutron.plugins.ml2.managers [-] Tenant network_types: ['geneve'] 2021-10-12 17:15:30.359 50573 INFO neutron.plugins.ml2.managers [-] Configured extension driver names: ['port_security', 'qos'] 2021-10-12 17:15:30.360 50573 INFO neutron.plugins.ml2.managers [-] Loaded extension driver names: ['port_security', 'qos'] 2021-10-12 17:15:30.360 50573 INFO neutron.plugins.ml2.managers [-] Registered extension drivers: ['port_security', 'qos'] 2021-10-12 17:15:30.360 50573 INFO neutron.plugins.ml2.managers [-] Configured mechanism driver names: ['ovn'] 2021-10-12 17:15:30.415 50573 INFO neutron.plugins.ml2.managers [-] Loaded mechanism driver names: ['ovn'] 2021-10-12 17:15:30.415 50573 INFO neutron.plugins.ml2.managers [-] Registered mechanism drivers: ['ovn'] 2021-10-12 17:15:30.415 50573 INFO neutron.plugins.ml2.managers [-] No mechanism drivers provide segment reachability information for agent scheduling. 2021-10-12 17:15:30.456 50573 INFO neutron.plugins.ml2.managers [-] Initializing driver for type 'flat' 2021-10-12 17:15:30.456 50573 INFO neutron.plugins.ml2.drivers.type_flat [-] ML2 FlatTypeDriver initialization complete 2021-10-12 17:15:30.456 50573 INFO neutron.plugins.ml2.managers [-] Initializing driver for type 'geneve' 2021-10-12 17:15:30.456 50573 INFO neutron.plugins.ml2.drivers.type_tunnel [-] geneve ID ranges: [(1, 65536)] 2021-10-12 17:15:32.555 50573 INFO neutron.plugins.ml2.managers [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Initializing extension driver 'port_security' 2021-10-12 17:15:32.555 50573 INFO neutron.plugins.ml2.extensions.port_security [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] PortSecurityExtensionDriver initialization complete 2021-10-12 17:15:32.556 50573 INFO neutron.plugins.ml2.managers [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Initializing extension driver 'qos' 2021-10-12 17:15:32.556 50573 INFO neutron.plugins.ml2.managers [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Initializing mechanism driver 'ovn' 2021-10-12 17:15:32.556 50573 INFO neutron.plugins.ml2.drivers.ovn.mech_driver.mech_driver [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Starting OVNMechanismDriver 2021-10-12 17:15:32.562 50573 WARNING neutron.plugins.ml2.drivers.ovn.mech_driver.mech_driver [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Firewall driver configuration is ignored 2021-10-12 17:15:32.586 50573 INFO neutron.services.logapi.drivers.ovn.driver [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] OVN logging driver registered 2021-10-12 17:15:32.588 50573 INFO neutron.plugins.ml2.plugin [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Modular L2 Plugin initialization complete 2021-10-12 17:15:32.589 50573 INFO neutron.plugins.ml2.managers [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Got port-security extension from driver 'port_security' 2021-10-12 17:15:32.589 50573 INFO neutron.extensions.vlantransparent [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Disabled vlantransparent extension. 2021-10-12 17:15:32.589 50573 INFO neutron.manager [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loading Plugin: ovn-router 2021-10-12 17:15:32.597 50573 INFO neutron.services.ovn_l3.plugin [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Starting OVNL3RouterPlugin 2021-10-12 17:15:32.597 50573 INFO neutron.manager [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loading Plugin: qos 2021-10-12 17:15:32.600 50573 INFO neutron.manager [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loading Plugin: metering 2021-10-12 17:15:32.603 50573 INFO neutron.manager [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loading Plugin: port_forwarding 2021-10-12 17:15:32.605 50573 INFO neutron.manager [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loading service plugin ovn-router, it is required by port_forwarding 2021-10-12 17:15:32.606 50573 INFO neutron.manager [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loading Plugin: segments 2021-10-12 17:15:32.684 50573 INFO neutron.manager [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loading Plugin: auto_allocate 2021-10-12 17:15:32.685 50573 INFO neutron.manager [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loading Plugin: tag 2021-10-12 17:15:32.687 50573 INFO neutron.manager [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loading Plugin: timestamp 2021-10-12 17:15:32.689 50573 INFO neutron.manager [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loading Plugin: network_ip_availability 2021-10-12 17:15:32.691 50573 INFO neutron.manager [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loading Plugin: flavors 2021-10-12 17:15:32.693 50573 INFO neutron.manager [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loading Plugin: revisions 2021-10-12 17:15:32.695 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Initializing extension manager. 2021-10-12 17:15:32.696 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Extension address-group not supported by any of loaded plugins 2021-10-12 17:15:32.697 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: address-scope 2021-10-12 17:15:32.697 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Extension router-admin-state-down-before-update not supported by any of loaded plugins 2021-10-12 17:15:32.698 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: agent 2021-10-12 17:15:32.699 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Extension agent-resources-synced not supported by any of loaded plugins 2021-10-12 17:15:32.700 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: allowed-address-pairs 2021-10-12 17:15:32.701 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: auto-allocated-topology 2021-10-12 17:15:32.701 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: availability_zone 2021-10-12 17:15:32.702 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Extension availability_zone_filter not supported by any of loaded plugins 2021-10-12 17:15:32.703 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Extension data-plane-status not supported by any of loaded plugins 2021-10-12 17:15:32.703 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: default-subnetpools 2021-10-12 17:15:32.704 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Extension dhcp_agent_scheduler not supported by any of loaded plugins 2021-10-12 17:15:32.705 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Extension dns-integration not supported by any of loaded plugins 2021-10-12 17:15:32.706 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Extension dns-domain-ports not supported by any of loaded plugins 2021-10-12 17:15:32.706 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Extension dvr not supported by any of loaded plugins 2021-10-12 17:15:32.707 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Extension empty-string-filtering not supported by any of loaded plugins 2021-10-12 17:15:32.708 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Extension expose-l3-conntrack-helper not supported by any of loaded plugins 2021-10-12 17:15:32.708 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: expose-port-forwarding-in-fip 2021-10-12 17:15:32.709 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: external-net 2021-10-12 17:15:32.710 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: extra_dhcp_opt 2021-10-12 17:15:32.710 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: extraroute 2021-10-12 17:15:32.711 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Extension extraroute-atomic not supported by any of loaded plugins 2021-10-12 17:15:32.712 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Extension filter-validation not supported by any of loaded plugins 2021-10-12 17:15:32.712 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: floating-ip-port-forwarding-description 2021-10-12 17:15:32.713 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: fip-port-details 2021-10-12 17:15:32.714 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: flavors 2021-10-12 17:15:32.715 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: floating-ip-port-forwarding 2021-10-12 17:15:32.715 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Extension floatingip-pools not supported by any of loaded plugins 2021-10-12 17:15:32.716 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: ip_allocation 2021-10-12 17:15:32.717 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Extension ip-substring-filtering not supported by any of loaded plugins 2021-10-12 17:15:32.717 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: l2_adjacency 2021-10-12 17:15:32.718 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: router 2021-10-12 17:15:32.719 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Extension l3-conntrack-helper not supported by any of loaded plugins 2021-10-12 17:15:32.720 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: ext-gw-mode 2021-10-12 17:15:32.721 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Extension l3-ha not supported by any of loaded plugins 2021-10-12 17:15:32.721 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Extension l3-flavors not supported by any of loaded plugins 2021-10-12 17:15:32.722 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Extension l3-port-ip-change-not-allowed not supported by any of loaded plugins 2021-10-12 17:15:32.723 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Extension l3_agent_scheduler not supported by any of loaded plugins 2021-10-12 17:15:32.724 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Extension logging not supported by any of loaded plugins 2021-10-12 17:15:32.725 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: metering 2021-10-12 17:15:32.725 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: metering_source_and_destination_fields 2021-10-12 17:15:32.726 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: multi-provider 2021-10-12 17:15:32.727 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: net-mtu 2021-10-12 17:15:32.727 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: net-mtu-writable 2021-10-12 17:15:32.728 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: network_availability_zone 2021-10-12 17:15:32.729 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: network-ip-availability 2021-10-12 17:15:32.729 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Extension network-segment-range not supported by any of loaded plugins 2021-10-12 17:15:32.730 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: pagination 2021-10-12 17:15:32.731 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: port-device-profile 2021-10-12 17:15:32.731 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Extension port-mac-address-regenerate not supported by any of loaded plugins 2021-10-12 17:15:32.732 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: port-numa-affinity-policy 2021-10-12 17:15:32.733 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: port-resource-request 2021-10-12 17:15:32.733 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: binding 2021-10-12 17:15:32.734 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Extension binding-extended not supported by any of loaded plugins 2021-10-12 17:15:32.735 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: port-security 2021-10-12 17:15:32.735 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: project-id 2021-10-12 17:15:32.736 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: provider 2021-10-12 17:15:32.736 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: qos 2021-10-12 17:15:32.737 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: qos-bw-limit-direction 2021-10-12 17:15:32.738 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: qos-bw-minimum-ingress 2021-10-12 17:15:32.738 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: qos-default 2021-10-12 17:15:32.739 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: qos-fip 2021-10-12 17:15:32.740 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Extension qos-gateway-ip not supported by any of loaded plugins 2021-10-12 17:15:32.740 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: qos-port-network-policy 2021-10-12 17:15:32.741 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: qos-rule-type-details 2021-10-12 17:15:32.741 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: qos-rules-alias 2021-10-12 17:15:32.742 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: quotas 2021-10-12 17:15:32.743 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: quota_details 2021-10-12 17:15:32.744 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: rbac-policies 2021-10-12 17:15:32.744 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Extension rbac-address-group not supported by any of loaded plugins 2021-10-12 17:15:32.745 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: rbac-address-scope 2021-10-12 17:15:32.746 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Extension rbac-security-groups not supported by any of loaded plugins 2021-10-12 17:15:32.746 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Extension rbac-subnetpool not supported by any of loaded plugins 2021-10-12 17:15:32.747 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: revision-if-match 2021-10-12 17:15:32.748 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: standard-attr-revisions 2021-10-12 17:15:32.748 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: router_availability_zone 2021-10-12 17:15:32.749 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Extension router-service-type not supported by any of loaded plugins 2021-10-12 17:15:32.749 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: security-groups-normalized-cidr 2021-10-12 17:15:32.750 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Extension port-security-groups-filtering not supported by any of loaded plugins 2021-10-12 17:15:32.751 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: security-groups-remote-address-group 2021-10-12 17:15:32.756 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: security-group 2021-10-12 17:15:32.757 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: segment 2021-10-12 17:15:32.758 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: segments-peer-subnet-host-routes 2021-10-12 17:15:32.758 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: service-type 2021-10-12 17:15:32.759 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: sorting 2021-10-12 17:15:32.759 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: standard-attr-segment 2021-10-12 17:15:32.760 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: standard-attr-description 2021-10-12 17:15:32.760 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Extension stateful-security-group not supported by any of loaded plugins 2021-10-12 17:15:32.761 50573 WARNING neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Did not find expected name "Stdattrs_common" in /usr/lib/python3/dist-packages/neutron/extensions/stdattrs_common.py 2021-10-12 17:15:32.762 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Extension subnet-dns-publish-fixed-ip not supported by any of loaded plugins 2021-10-12 17:15:32.762 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Extension subnet_onboard not supported by any of loaded plugins 2021-10-12 17:15:32.763 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: subnet-segmentid-writable 2021-10-12 17:15:32.763 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Extension subnet-service-types not supported by any of loaded plugins 2021-10-12 17:15:32.764 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: subnet_allocation 2021-10-12 17:15:32.765 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Extension subnetpool-prefix-ops not supported by any of loaded plugins 2021-10-12 17:15:32.765 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Extension tag-ports-during-bulk-creation not supported by any of loaded plugins 2021-10-12 17:15:32.766 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: standard-attr-tag 2021-10-12 17:15:32.767 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Loaded extension: standard-attr-timestamp 2021-10-12 17:15:32.767 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Extension trunk not supported by any of loaded plugins 2021-10-12 17:15:32.768 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Extension trunk-details not supported by any of loaded plugins 2021-10-12 17:15:32.769 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Extension uplink-status-propagation not supported by any of loaded plugins 2021-10-12 17:15:32.769 50573 INFO neutron.api.extensions [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Extension vlan-transparent not supported by any of loaded plugins 2021-10-12 17:15:32.771 50573 INFO neutron.quota.resource_registry [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Creating instance of TrackedResource for resource:network 2021-10-12 17:15:32.771 50573 INFO neutron.quota.resource_registry [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Creating instance of TrackedResource for resource:subnet 2021-10-12 17:15:32.772 50573 INFO neutron.quota.resource_registry [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Creating instance of TrackedResource for resource:subnetpool 2021-10-12 17:15:32.772 50573 INFO neutron.quota.resource_registry [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Creating instance of TrackedResource for resource:port 2021-10-12 17:15:32.774 50573 INFO neutron.quota.resource_registry [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Creating instance of TrackedResource for resource:router 2021-10-12 17:15:32.774 50573 INFO neutron.quota.resource_registry [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Creating instance of TrackedResource for resource:floatingip 2021-10-12 17:15:32.778 50573 INFO neutron.quota.resource_registry [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Creating instance of CountableResource for resource:rbac_policy 2021-10-12 17:15:32.778 50573 INFO neutron.quota.resource_registry [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Creating instance of TrackedResource for resource:security_group 2021-10-12 17:15:32.779 50573 INFO neutron.quota.resource_registry [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Creating instance of TrackedResource for resource:security_group_rule 2021-10-12 17:15:32.781 50573 INFO neutron.quota.resource_registry [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Creating instance of TrackedResource for resource:router 2021-10-12 17:15:32.781 50573 WARNING neutron.quota.resource_registry [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] router is already registered 2021-10-12 17:15:32.781 50573 INFO neutron.quota.resource_registry [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Creating instance of TrackedResource for resource:floatingip 2021-10-12 17:15:32.782 50573 WARNING neutron.quota.resource_registry [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] floatingip is already registered 2021-10-12 17:15:32.783 50573 INFO neutron.quota.resource_registry [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Creating instance of CountableResource for resource:rbac_policy 2021-10-12 17:15:32.783 50573 WARNING neutron.quota.resource_registry [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] rbac_policy is already registered 2021-10-12 17:15:32.783 50573 INFO neutron.quota.resource_registry [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Creating instance of TrackedResource for resource:security_group 2021-10-12 17:15:32.783 50573 WARNING neutron.quota.resource_registry [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] security_group is already registered 2021-10-12 17:15:32.784 50573 INFO neutron.quota.resource_registry [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Creating instance of TrackedResource for resource:security_group_rule 2021-10-12 17:15:32.784 50573 WARNING neutron.quota.resource_registry [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] security_group_rule is already registered 2021-10-12 17:15:32.810 50573 WARNING keystonemiddleware.auth_token [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] AuthToken middleware is set with keystone_authtoken.service_token_roles_required set to False. This is backwards compatible but deprecated behaviour. Please set this to True. 2021-10-12 17:15:32.816 50573 INFO oslo_service.service [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Starting 1 workers 2021-10-12 17:15:32.824 50573 INFO neutron.service [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Neutron service started, listening on 0.0.0.0:9696 2021-10-12 17:15:32.831 50573 ERROR ovsdbapp.backend.ovs_idl.idlutils [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Unable to open stream to ssl:172.16.30.46:6641 to retrieve schema: Unknown error -1 2021-10-12 17:15:32.834 50573 CRITICAL neutron [req-06f63d07-b8d8-4c20-aa87-bdf06a3b17f5 - - - - -] Unhandled error: neutron_lib.callbacks.exceptions.CallbackFailure: Callback neutron.plugins.ml2.drivers.ovn.mech_driver.mech_driver.OVNMechanismDriver.pre_fork_initialize-904549 failed with "Could not retrieve schema from ssl:172.16.30.46:6641" 2021-10-12 17:15:32.834 50573 ERROR neutron Traceback (most recent call last): 2021-10-12 17:15:32.834 50573 ERROR neutron File "/usr/bin/neutron-server", line 10, in <module> 2021-10-12 17:15:32.834 50573 ERROR neutron sys.exit(main()) 2021-10-12 17:15:32.834 50573 ERROR neutron File "/usr/lib/python3/dist-packages/neutron/cmd/eventlet/server/__init__.py", line 19, in main 2021-10-12 17:15:32.834 50573 ERROR neutron server.boot_server(wsgi_eventlet.eventlet_wsgi_server) 2021-10-12 17:15:32.834 50573 ERROR neutron File "/usr/lib/python3/dist-packages/neutron/server/__init__.py", line 68, in boot_server 2021-10-12 17:15:32.834 50573 ERROR neutron server_func() 2021-10-12 17:15:32.834 50573 ERROR neutron File "/usr/lib/python3/dist-packages/neutron/server/wsgi_eventlet.py", line 24, in eventlet_wsgi_server 2021-10-12 17:15:32.834 50573 ERROR neutron neutron_api = service.serve_wsgi(service.NeutronApiService) 2021-10-12 17:15:32.834 50573 ERROR neutron File "/usr/lib/python3/dist-packages/neutron/service.py", line 94, in serve_wsgi 2021-10-12 17:15:32.834 50573 ERROR neutron registry.publish(resources.PROCESS, events.BEFORE_SPAWN, service) 2021-10-12 17:15:32.834 50573 ERROR neutron File "/usr/lib/python3/dist-packages/neutron_lib/callbacks/registry.py", line 60, in publish 2021-10-12 17:15:32.834 50573 ERROR neutron _get_callback_manager().publish(resource, event, trigger, payload=payload) 2021-10-12 17:15:32.834 50573 ERROR neutron File "/usr/lib/python3/dist-packages/neutron_lib/callbacks/manager.py", line 149, in publish 2021-10-12 17:15:32.834 50573 ERROR neutron return self.notify(resource, event, trigger, payload=payload) 2021-10-12 17:15:32.834 50573 ERROR neutron File "/usr/lib/python3/dist-packages/neutron_lib/db/utils.py", line 110, in _wrapped 2021-10-12 17:15:32.834 50573 ERROR neutron raise db_exc.RetryRequest(e) 2021-10-12 17:15:32.834 50573 ERROR neutron File "/usr/lib/python3/dist-packages/oslo_utils/excutils.py", line 227, in __exit__ 2021-10-12 17:15:32.834 50573 ERROR neutron self.force_reraise() 2021-10-12 17:15:32.834 50573 ERROR neutron File "/usr/lib/python3/dist-packages/oslo_utils/excutils.py", line 200, in force_reraise 2021-10-12 17:15:32.834 50573 ERROR neutron raise self.value 2021-10-12 17:15:32.834 50573 ERROR neutron File "/usr/lib/python3/dist-packages/neutron_lib/db/utils.py", line 105, in _wrapped 2021-10-12 17:15:32.834 50573 ERROR neutron return function(*args, **kwargs) 2021-10-12 17:15:32.834 50573 ERROR neutron File "/usr/lib/python3/dist-packages/neutron_lib/callbacks/manager.py", line 174, in notify 2021-10-12 17:15:32.834 50573 ERROR neutron raise exceptions.CallbackFailure(errors=errors) 2021-10-12 17:15:32.834 50573 ERROR neutron neutron_lib.callbacks.exceptions.CallbackFailure: Callback neutron.plugins.ml2.drivers.ovn.mech_driver.mech_driver.OVNMechanismDriver.pre_fork_initialize-904549 failed with "Could not retrieve schema from ssl:172.16.30.46:6641" 2021-10-12 17:15:32.834 50573 ERROR neutron 2021-10-12 17:15:32.838 50582 ERROR ovsdbapp.backend.ovs_idl.idlutils [-] Unable to open stream to ssl:172.16.30.46:6641 to retrieve schema: Unknown error -1 2021-10-12 17:15:32.840 50582 ERROR neutron_lib.callbacks.manager [-] Error during notification for neutron.plugins.ml2.drivers.ovn.mech_driver.mech_driver.OVNMechanismDriver.post_fork_initialize-904522 process, after_init: Exception: Could not retrieve schema from ssl:172.16.30.46:6641 2021-10-12 17:15:32.840 50582 ERROR neutron_lib.callbacks.manager Traceback (most recent call last): 2021-10-12 17:15:32.840 50582 ERROR neutron_lib.callbacks.manager File "/usr/lib/python3/dist-packages/neutron_lib/callbacks/manager.py", line 197, in _notify_loop 2021-10-12 17:15:32.840 50582 ERROR neutron_lib.callbacks.manager callback(resource, event, trigger, **kwargs) 2021-10-12 17:15:32.840 50582 ERROR neutron_lib.callbacks.manager File "/usr/lib/python3/dist-packages/neutron/plugins/ml2/drivers/ovn/mech_driver/mech_driver.py", line 294, in post_fork_initialize 2021-10-12 17:15:32.840 50582 ERROR neutron_lib.callbacks.manager self._wait_for_pg_drop_event() 2021-10-12 17:15:32.840 50582 ERROR neutron_lib.callbacks.manager File "/usr/lib/python3/dist-packages/neutron/plugins/ml2/drivers/ovn/mech_driver/mech_driver.py", line 357, in _wait_for_pg_drop_event 2021-10-12 17:15:32.840 50582 ERROR neutron_lib.callbacks.manager ovn_conf.get_ovn_nb_connection(), self.nb_schema_helper, self, 2021-10-12 17:15:32.840 50582 ERROR neutron_lib.callbacks.manager File "/usr/lib/python3/dist-packages/neutron/plugins/ml2/drivers/ovn/mech_driver/mech_driver.py", line 136, in nb_schema_helper 2021-10-12 17:15:32.840 50582 ERROR neutron_lib.callbacks.manager return impl_idl_ovn.OvsdbNbOvnIdl.schema_helper 2021-10-12 17:15:32.840 50582 ERROR neutron_lib.callbacks.manager File "/usr/lib/python3/dist-packages/neutron/common/utils.py", line 721, in __get__ 2021-10-12 17:15:32.840 50582 ERROR neutron_lib.callbacks.manager return self.func(owner) 2021-10-12 17:15:32.840 50582 ERROR neutron_lib.callbacks.manager File "/usr/lib/python3/dist-packages/neutron/plugins/ml2/drivers/ovn/mech_driver/ovsdb/impl_idl_ovn.py", line 102, in schema_helper 2021-10-12 17:15:32.840 50582 ERROR neutron_lib.callbacks.manager cls._schema_helper = idlutils.get_schema_helper(cls.connection_string, 2021-10-12 17:15:32.840 50582 ERROR neutron_lib.callbacks.manager File "/usr/lib/python3/dist-packages/ovsdbapp/backend/ovs_idl/idlutils.py", line 215, in get_schema_helper 2021-10-12 17:15:32.840 50582 ERROR neutron_lib.callbacks.manager return create_schema_helper(fetch_schema_json(connection, schema_name)) 2021-10-12 17:15:32.840 50582 ERROR neutron_lib.callbacks.manager File "/usr/lib/python3/dist-packages/ovsdbapp/backend/ovs_idl/idlutils.py", line 204, in fetch_schema_json 2021-10-12 17:15:32.840 50582 ERROR neutron_lib.callbacks.manager raise Exception("Could not retrieve schema from %s" % connection) 2021-10-12 17:15:32.840 50582 ERROR neutron_lib.callbacks.manager Exception: Could not retrieve schema from ssl:172.16.30.46:6641 2021-10-12 17:15:32.840 50582 ERROR neutron_lib.callbacks.manager 2021-10-12 17:15:32.842 50582 INFO neutron.wsgi [-] (50582) wsgi starting up on http://0.0.0.0:9696 2021-10-12 17:15:32.961 50582 INFO oslo_service.service [-] Parent process has died unexpectedly, exiting 2021-10-12 17:15:32.963 50582 INFO neutron.wsgi [-] (50582) wsgi exited, is_accepting=True 2021-10-12 17:15:34.722 50583 INFO neutron.common.config [-] Logging enabled! I would really appreciate any input in this regard. Best regards, Faisal Sheikh

2 2

[kolla] Cancelling next weeks meeting (20 Oct 2021)
by Michał Nasiadka 15 Oct '21

15 Oct '21

Hello koalas, Since next week is PTG - I’m cancelling the meeting on 20th Oct 2021. Best regards, Michal

1 0

[tacker] Yoga vPTG planning
by yasufum 15 Oct '21

15 Oct '21

Hi everyone, The next vPTG will be held on 18-22 October as I shared at the previous IRC meeting [1]. Registration has already opened [2]. We've decided to have the next vPTG session on the same timeslots, 6-8 UTC, as previous for most of us join from India and APAC regions. I've prepared etherpad for the next vPTG [3]. If you have any suggestion, please add your topic on it. [1] http://lists.openstack.org/pipermail/openstack-discuss/2021-July/023540.html [2] https://openinfra-ptg.eventbrite.com/ [3] https://etherpad.opendev.org/p/tacker-yoga-ptg Thanks, Yasufumi

2 1

[Heat][PTG] PTG plan
by Rico Lin 15 Oct '21

15 Oct '21

Dear all Apologize for the late notice Next week Heat team will have PTG <https://ptg.opendev.org/ptg.html> schedule at: Monday 14 -15 UTC Feel free to join and suggest topic to https://etherpad.opendev.org/p/oct2021-ptg-heat *Rico Lin* OIF Individual Board of directors, OpenStack TC, Multi-arch SIG chair, Heat PTL, Senior Software Engineer@EasyStack

1 0

[Multi-arch SIG][PTG] PTG plan
by Rico Lin 15 Oct '21

15 Oct '21

Dear all Next week, Multi-arch SIG will have PTG <https://ptg.opendev.org/ptg.html> at: 10/19 Tuesday 07 - 08 UTC time 10/19 Tuesday 14 -15 UTC time SIG have been low activity for months and we need more volunteers to join. Please sign up for PTG if you're interested. Also feel free to suggest topics PTG etherpad: https://etherpad.opendev.org/p/oct2021-ptg-multi-arch *Rico Lin* OIF Individual Board of directors, OpenStack TC, Multi-arch SIG chair, Heat PTL, Senior Software Engineer@EasyStack

1 0

[neutron] Drivers meeting agenda - 15.10.2021
by Lajos Katona 15 Oct '21

15 Oct '21

Hi Neutron Drivers! As we have no quorum last week to decide on https://bugs.launchpad.net/neutron/+bug/1946251 tomorrow we can check it again and vote. The logs of the meeting from last week: https://meetings.opendev.org/meetings/neutron_drivers/2021/neutron_drivers.… (Sorry it is 4 days long as I missed to end the meeting.....) As we have PTG next week, let's cancel drivers meeting for that Friday, and I will be on PTO the week after (29. October) so I can't chair that one. See you online tomorrow. Lajos Katona (lajoskatona)

2 1

Problème with image from snapshot
by Franck VEDEL 14 Oct '21

14 Oct '21

Hello and first sorry for my english… thanks google. Something is wrong with what I want to do: I use Wallaby, it works very well (apart from VpnaaS, I wasted too much time this summer to make it work, without success, and the bug does not seem to be fixed). Here is what I want to do and which does not work as I want: - With an admin account, I launch a Win10 instance from the image I created. The instance is working but it takes about 10 minutes to get Win10 up and running. I wanted to take a snapshot of this instance and then create a new image from this snapshot. And that users use this new image. I create the snapshot, I place the "--public" parameter on the new image. I'm trying to create a new instance from this snapshot with the admin account: it works. I create a new user, who has his project, and sees all the images. I try to create an instance with this new image and I get the message: Block Device Mapping is Invalid: failed to get snapshot f12c04f2-51e7-4817-ab9b-eda63c5b9aff. (HTTP 400) (Request-ID: req-c26dab86-c25f-409a-8390-8aa0ea8fe1cb) Is it a legal problem? Is it possible to do as I do? otherwise how should we do it? Thanks if you have ideas for helping me Franck VEDEL

3 8

[tc] No TC weekly meeting next week due to meeting in PTG
by Ghanshyam Mann 14 Oct '21

14 Oct '21

Hello Everyone, As we will be meeting in PTG next week, we are cancelling the TC's next week (21st Oct) IRC meeting. -gmann

1 0

[dev][cinder] Consultation about new cinder-backup features
by Daniel de Oliveira Pereira 14 Oct '21

14 Oct '21

Hello everyone, We have prototyped some new features on Cinder for our clients, and we think that they are nice features and good candidates to be part of upstream Cinder, so we would like to get feedback from OpenStack community about these features and if you would be willing to accept them in upstream OpenStack. Our team implemented the following features for cinder-backup service: 1. A multi-backend backup driver, that allow OpenStack users to choose, via API/CLI/Horizon, which backup driver (Ceph or NFS, in our prototype) will be used during a backup operation to create a new volume backup. 2. An improved NFS backup driver, that allow OpenStack users to back up their volumes to private NFS servers, providing the NFS hostpath at runtime via API/CLI/Horizon, while creating the volume backup. Considering that cinder was configured to use the multi-backend backup driver, this is how it works: During a volume backup operation, the user provides a "location" parameter to indicate which backend will be used, and the backup hostpath, if applicable (for NFS driver), to create the volume backup. For instance: - Creating a backup using Ceph backend: $ openstack volume backup create --name <backup_name> --location ceph <volume_id> - Creating a backup using the improved NFS backend: $ openstack volume backup create --name <backup_name> --location nfs://my.nfs.server:/backups <volume_id> If the user chooses Ceph backend, the Ceph driver will be used to create the backup. If the user chooses the NFS backend, the improved NFS driver, previously mentioned, will be used to create the backup. The backup location, if provided, is stored on Cinder database, and can be seen fetching the backup details: $ openstack volume backup show <backup_name> Briefly, this is how the features were implemented: - Cinder API was updated to add an optional location parameter to "create backup" method. Horizon, and OpenStack and Cinder CLIs were updated accordingly, to handle the new parameter. - Cinder backup controller was updated to handle the backup location parameter, and a validator for the parameter was implemented using the oslo config library. - Cinder backup object model was updated to add a nullable location property, so that the backup location could be stored on cinder database. - a new backup driver base class, that extends BackupDriver and accepts a backup context object, was implemented to handle the backup configuration provided at runtime by the user. This new backup base class requires that the concrete drivers implement a method to validate the backup context (similar to BackupDriver.check_for_setup_error) - the 2 new backup drivers, previously mentioned, were implemented using these new backup base class. - in BackupManager class, the "service" attribute, that on upstream OpenStack holds the backup driver class name, was re-implemented as a factory function that accepts a backup context object and return an instance of a backup driver, according to the backup driver configured on cinder.conf file and the backup context provided at runtime by the user. - All the backup operations continue working as usual. Could you please let us know your thoughts about these features and if you would be open to adding them to upstream Cinder? If yes, we would be willing to submit the specs and work on the upstream implementation, if they are approved. Regards, Daniel Pereira

5 6

[manila][ptg] No IRC meetings on 21st and 28th Oct 2021
by Goutham Pacha Ravi 14 Oct '21

14 Oct '21

Hi Zorillas, Since we'll be at the PTG [1], we'll skip the IRC meeting [2] on the 21st of Oct; and since a number of us may be taking some time off the week after, we'll skip that weekly occurrence (28th Oct) as well. Please feel free to grab attention to any issue via this mailing list, or hop over to #openstack-manila on OFTC. Our next weekly IRC meeting will be on 4th Nov 2021. Thanks, and see you at the PTG! Goutham [1] https://etherpad.opendev.org/p/yoga-ptg-manila-planning [2] https://wiki.openstack.org/wiki/Manila/Meetings

1 0

[neutron][PTG] Schedule for yoga PTG
by Lajos Katona 14 Oct '21

14 Oct '21

Hi, I made a first schedule for the PTG next week, please check it: https://etherpad.opendev.org/p/neutron-yoga-ptg If you have anything to change or add please raise your voice :-) There's still some parts which can change, as we will have multiple cross-project sessions. See you next week. Lajos Katona (lajoskatona)

1 0

[neutron] Team meeting
by Lajos Katona 14 Oct '21

14 Oct '21

Hi Neutrinos, As we have PTG next week, let's cancel the team meeting. Cheers Lajos Katona (lajoskatona)

1 0

[neutron] CI meeting Tuesday 19.10
by Slawek Kaplonski 14 Oct '21

14 Oct '21

Hi, As we have PTG next week, let's cancel CI meeting. See You all at the PTG sessions and on the CI meeting on Tuesday 26th of October. -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[cinder][backup] backup big volumes leads to oom kill of cinder-backup
by Stefan Hoffmann 14 Oct '21

14 Oct '21

Hi cinder team, we have the issue, that doing backups of big volumes (5TB) fails and cinder-backup get oom killed. Looks like cinder-backup is allocating memory but didn't release it correctly. Badly we are still using cinder queens. Is this a known issue and fixed in newer releases or should I create a bug report? We found a similar bug [1] with backup restore, that got fixed. I guess something like this is also needed for backup create. Thanks for you help Stefan [1] https://bugs.launchpad.net/cinder/+bug/1865011 -- Stefan Hoffmann DevOps-Engineer Cloud&Heat Technologies GmbH Königsbrücker Straße 96 (Halle 15) | 01099 Dresden +49 351 479 367 36 stefan.hoffmann(a)cloudandheat.com | www.cloudandheat.com Die grüne Cloud für KI und ML. Think Green: Mach Deine Anwendung grüner. https://thinkgreen.cloudandheat.com/ Commercial Register: District Court Dresden Register Number: HRB 30549 VAT ID No.: DE281093504 Managing Director: Nicolas Röhrs Authorized signatory: Dr. Marius Feldmann Authorized signatory: Kristina Rübenkamp

1 0

Networks in openstack
by Midhunlal Nb 14 Oct '21

14 Oct '21

Hi Team, I have some doubt in different network types Vlan,Vxlan and flat networks. How these networks helps in openstack.What is the use of each network? Could you Please provide me a detailed answer or suggest me any document regarding this networks. Show quoted text

3 3

[kayobe][kolla][ironic] kayobe overcloud provision fails because ironic compute hosts use their inspection DHCP pool IPs
by Manuel Holtgrewe 14 Oct '21

14 Oct '21

Dear list, I am experimenting with kayobe to deploy a test installation of OpenStack wallaby. You can find my configuration here: https://github.com/openstack/kayobe-config/compare/stable/wallaby...holtgre… I am following the kayobe documentation and have successfully setup a controller and a seed node. I am at the point where I have the nodes configured and they show up in bifrost baremetal node list. I can control them via IPMI/iDRAC/RedFish and boot them into the IPA image and the nodes can be inspected and actually go into the "manageable" status. kayobe is capable of using the inspection results and assigning the root device, so far, so good. I don't know whether my network configuration is good. I want to pin the IPs of stack-1 to stack-4 and the names resolve the correct IP addresses throughout my network. Below are some more details. In summary, I have trouble because `kayobe overcloud provision` makes my 4 overcloud bare metal host boot into IPA with DHCP enabled and they get the same IPs assigned that were given to them earlier in inspection. This means that the overcloud provision command cannot SSH into the nodes because it knows them by the wrong IPs. I must be really missing something here. What is it? Below are more details. Here is what kayobe pulled from the bifrost inspection (I believe). # cat etc/kayobe/inventory/overcloud [controllers] stack-1 ipmi_address=172.16.66.41 bmc_type=idrac stack-2 ipmi_address=172.16.66.42 bmc_type=idrac stack-3 ipmi_address=172.16.66.43 bmc_type=idrac stack-4 ipmi_address=172.16.66.44 bmc_type=idrac The IPs are also fixed here # etc/kayobe/network-allocation.yml compute_net_ips: stack-1: 172.16.32.11 stack-2: 172.16.32.12 stack-3: 172.16.32.13 stack-4: 172.16.32.14 stack-seed: 172.16.32.6 However, I thought I had to provide allocation ranges for DHCP for getting introspection to work. Thus, I have the following # etc/kayobe/networks.yml compute_net_cidr: 172.16.32.0/19 compute_net_gateway: 172.16.32.1 compute_net_vip_address: 172.16.32.2 compute_net_allocation_pool_start: 172.16.32.101 compute_net_allocation_pool_end: 172.16.32.200 compute_net_inspection_allocation_pool_start: 172.16.32.201 compute_net_inspection_allocation_pool_end: 172.16.32.250 This leads to the following dnsmasq leases in the bifrost host. # cat /var/lib/dnsmasq/dnsmasq.leases 1634187260 REDACTED 172.16.32.215 * REDACTED 1634187271 REDACTED 172.16.32.243 * REDACTED 1634187257 REDACTED 172.16.32.207 * REDACTED 1634187258 REDACTED 172.16.32.218 * REDACTED What am I missing? Best wishes, Manuel

2 1

[tripleo] Unable to deploy Overcloud Nodes
by Anirudh Gupta 14 Oct '21

14 Oct '21

Hi Team, As per the link below, While executing the command to deploy the overcloud nodes https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/deploym… I am executing the command - openstack overcloud deploy --templates On running this command, I am getting the following error *ERROR: (pymysql.err.OperationalError) (1045, "Access denied for user 'heat'@'10.255.255.4' (using password: YES)")(Background on this error at: http://sqlalche.me/e/e3q8 <http://sqlalche.me/e/e3q8>)* 2021-10-13 05:46:28.390 183680 ERROR tripleoclient.v1.overcloud_deploy.DeployOvercloud [-] Exception occured while running the command: subprocess.CalledProcessError: Command '['sudo', 'podman', 'run', '--rm', '--user', 'heat', '--volume', '/home/stack/overcloud-deploy/overcloud/heat-launcher/heat.conf:/etc/heat/heat.conf:z', '--volume', '/home/stack/overcloud-deploy/overcloud/heat-launcher:/home/stack/overcloud-deploy/overcloud/heat-launcher:z', 'localhost/tripleo/openstack-heat-api:ephemeral', 'heat-manage', 'db_sync']' returned non-zero exit status 1. 2021-10-13 05:46:28.390 183680 ERROR tripleoclient.v1.overcloud_deploy.DeployOvercloud Traceback (most recent call last): 2021-10-13 05:46:28.390 183680 ERROR tripleoclient.v1.overcloud_deploy.DeployOvercloud File "/usr/lib/python3.6/site-packages/tripleoclient/command.py", line 34, in run 2021-10-13 05:46:28.390 183680 ERROR tripleoclient.v1.overcloud_deploy.DeployOvercloud super(Command, self).run(parsed_args) 2021-10-13 05:46:28.390 183680 ERROR tripleoclient.v1.overcloud_deploy.DeployOvercloud File "/usr/lib/python3.6/site-packages/osc_lib/command/command.py", line 39, in run 2021-10-13 05:46:28.390 183680 ERROR tripleoclient.v1.overcloud_deploy.DeployOvercloud return super(Command, self).run(parsed_args) 2021-10-13 05:46:28.390 183680 ERROR tripleoclient.v1.overcloud_deploy.DeployOvercloud File "/usr/lib/python3.6/site-packages/cliff/command.py", line 185, in run 2021-10-13 05:46:28.390 183680 ERROR tripleoclient.v1.overcloud_deploy.DeployOvercloud return_code = self.take_action(parsed_args) or 0 2021-10-13 05:46:28.390 183680 ERROR tripleoclient.v1.overcloud_deploy.DeployOvercloud File "/usr/lib/python3.6/site-packages/tripleoclient/v1/overcloud_deploy.py", line 1277, in take_action 2021-10-13 05:46:28.390 183680 ERROR tripleoclient.v1.overcloud_deploy.DeployOvercloud self.setup_ephemeral_heat(parsed_args) 2021-10-13 05:46:28.390 183680 ERROR tripleoclient.v1.overcloud_deploy.DeployOvercloud File "/usr/lib/python3.6/site-packages/tripleoclient/v1/overcloud_deploy.py", line 767, in setup_ephemeral_heat 2021-10-13 05:46:28.390 183680 ERROR tripleoclient.v1.overcloud_deploy.DeployOvercloud utils.launch_heat(self.heat_launcher, restore_db=restore_db) 2021-10-13 05:46:28.390 183680 ERROR tripleoclient.v1.overcloud_deploy.DeployOvercloud File "/usr/lib/python3.6/site-packages/tripleoclient/utils.py", line 2706, in launch_heat 2021-10-13 05:46:28.390 183680 ERROR tripleoclient.v1.overcloud_deploy.DeployOvercloud launcher.heat_db_sync(restore_db) 2021-10-13 05:46:28.390 183680 ERROR tripleoclient.v1.overcloud_deploy.DeployOvercloud File "/usr/lib/python3.6/site-packages/tripleoclient/heat_launcher.py", line 530, in heat_db_sync 2021-10-13 05:46:28.390 183680 ERROR tripleoclient.v1.overcloud_deploy.DeployOvercloud subprocess.check_call(cmd) 2021-10-13 05:46:28.390 183680 ERROR tripleoclient.v1.overcloud_deploy.DeployOvercloud File "/usr/lib64/python3.6/subprocess.py", line 311, in check_call 2021-10-13 05:46:28.390 183680 ERROR tripleoclient.v1.overcloud_deploy.DeployOvercloud raise CalledProcessError(retcode, cmd) 2021-10-13 05:46:28.390 183680 ERROR tripleoclient.v1.overcloud_deploy.DeployOvercloud subprocess.CalledProcessError: Command '['sudo', 'podman', 'run', '--rm', '--user', 'heat', '--volume', '/home/stack/overcloud-deploy/overcloud/heat-launcher/heat.conf:/etc/heat/heat.conf:z', '--volume', '/home/stack/overcloud-deploy/overcloud/heat-launcher:/home/stack/overcloud-deploy/overcloud/heat-launcher:z', 'localhost/tripleo/openstack-heat-api:ephemeral', 'heat-manage', 'db_sync']' returned non-zero exit status 1. 2021-10-13 05:46:28.390 183680 ERROR tripleoclient.v1.overcloud_deploy.DeployOvercloud 2021-10-13 05:46:28.400 183680 ERROR openstack [-] Command '['sudo', 'podman', 'run', '--rm', '--user', 'heat', '--volume', '/home/stack/overcloud-deploy/overcloud/heat-launcher/heat.conf:/etc/heat/heat.conf:z', '--volume', '/home/stack/overcloud-deploy/overcloud/heat-launcher:/home/stack/overcloud-deploy/overcloud/heat-launcher:z', 'localhost/tripleo/openstack-heat-api:ephemeral', 'heat-manage', 'db_sync']' returned non-zero exit status 1.: subprocess.CalledProcessError: Command '['sudo', 'podman', 'run', '--rm', '--user', 'heat', '--volume', '/home/stack/overcloud-deploy/overcloud/heat-launcher/heat.conf:/etc/heat/heat.conf:z', '--volume', '/home/stack/overcloud-deploy/overcloud/heat-launcher:/home/stack/overcloud-deploy/overcloud/heat-launcher:z', 'localhost/tripleo/openstack-heat-api:ephemeral', 'heat-manage', 'db_sync']' returned non-zero exit status 1. 2021-10-13 05:46:28.401 183680 INFO osc_lib.shell [-] END return value: 1 Can someone please help in resolving this issue. Are there any parameters, templates that need to be passed in order to make it work. Regards Anirudh Gupta

2 1

[tc] [ptl] 2021 User Survey Project Specific Feedback Responses
by helena＠openstack.org 13 Oct '21

13 Oct '21

4 3

[all][tc] Technical Committee next weekly meeting on Oct 14th at 1500 UTC
by Ghanshyam Mann 13 Oct '21

13 Oct '21

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

1 1

[Designate] After rebuilding Queens clusters on Train, race condition causes Designate record creation to fail
by Braden, Albert 13 Oct '21

13 Oct '21

After enabling redis, and allowing TCP 6379 and 26379, I see it in /etc/designate/designate.conf in the designate_producer container: backend_url = redis://admin:<key>@10.221.176.48:26379?sentinel=kolla&sentinel_fallback=10.221.176.173:26379&sentinel_fallback=10.221.177.38:26379&db=0&socket_timeout=60&retry_on_timeout=yes And I can get to ports 6379 and 26379 with nc: (designate-producer)[root@dva3-ctrl3 /]# nc 10.221.176.173 26379 / -ERR unknown command `/`, with args beginning with: But I still see the DB error when TF rebuilds a VM: 2021-10-13 15:35:23.941 26 ERROR oslo_messaging.notify.dispatcher designate.exceptions.DuplicateRecord: Duplicate Record What am I missing? -----Original Message----- From: Michael Johnson <johnsomor(a)gmail.com> Sent: Tuesday, October 12, 2021 11:33 AM To: Braden, Albert <abraden(a)verisign.com> Cc: openstack-discuss(a)lists.openstack.org Subject: [EXTERNAL] Re: Re: Re: After rebuilding Queens clusters on Train, race condition causes Designate record creation to fail Caution: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. I don't have a good answer for you on that as it pre-dates my history with Designate a bit. I suspect it has to do with the removal of the pool-manager and the restructuring of the controller code. Maybe someone else on the discuss list has more insight. Michael On Tue, Oct 12, 2021 at 5:47 AM Braden, Albert <abraden(a)verisign.com> wrote: > > Thank you Michael, this is very helpful. Do you have any insight into why we don't experience this in Queens clusters? We aren't running a lock manager there either, and I haven't been able to duplicate the problem there. > > -----Original Message----- > From: Michael Johnson <johnsomor(a)gmail.com> > Sent: Monday, October 11, 2021 4:24 PM > To: Braden, Albert <abraden(a)verisign.com> > Cc: openstack-discuss(a)lists.openstack.org > Subject: [EXTERNAL] Re: Re: After rebuilding Queens clusters on Train, race condition causes Designate record creation to fail > > Caution: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. > > You will need one of the Tooz supported distributed lock managers: > Consul, Memcacded, Redis, or zookeeper. > > Michael > > On Mon, Oct 11, 2021 at 11:57 AM Braden, Albert <abraden(a)verisign.com> wrote: > > > > After investigating further, I realized that we're not running redis, and I think that means that redis_connection_string doesn't get set. Does this mean that we must run redis, or is there a workaround? > > > > -----Original Message----- > > From: Braden, Albert > > Sent: Monday, October 11, 2021 2:48 PM > > To: 'johnsomor(a)gmail.com' <johnsomor(a)gmail.com> > > Cc: 'openstack-discuss(a)lists.openstack.org' <openstack-discuss(a)lists.openstack.org> > > Subject: RE: [EXTERNAL] Re: After rebuilding Queens clusters on Train, race condition causes Designate record creation to fail > > > > I think so. I see this: > > > > ansible/roles/designate/templates/designate.conf.j2:backend_url = {{ redis_connection_string }} > > > > ansible/group_vars/all.yml:redis_connection_string: "redis://{% for host in groups['redis'] %}{% if host == groups['redis'][0] %}admin:{{ redis_master_password }}@{{ 'api' | kolla_address(host) | put_address_in_context('url') }}:{{ redis_sentinel_port }}?sentinel=kolla{% else %}&sentinel_fallback={{ 'api' | kolla_address(host) | put_address_in_context('url') }}:{{ redis_sentinel_port }}{% endif %}{% endfor %}&db=0&socket_timeout=60&retry_on_timeout=yes" > > > > Did anything with the distributed lock manager between Queens and Train? > > > > -----Original Message----- > > From: Michael Johnson <johnsomor(a)gmail.com> > > Sent: Monday, October 11, 2021 1:15 PM > > To: Braden, Albert <abraden(a)verisign.com> > > Cc: openstack-discuss(a)lists.openstack.org > > Subject: [EXTERNAL] Re: After rebuilding Queens clusters on Train, race condition causes Designate record creation to fail > > > > Caution: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. > > > > Hi Albert, > > > > Have you configured your distributed lock manager for Designate? > > > > [coordination] > > backend_url = <DLM URL> > > > > Michael > > > > On Fri, Oct 8, 2021 at 7:38 PM Braden, Albert <abraden(a)verisign.com> wrote: > > > > > > Hello everyone. It’s great to be back working on OpenStack again. I’m at Verisign now. I can hardly describe how happy I am to have an employer that does not attach nonsense to the bottom of my emails! > > > > > > > > > > > > We are rebuilding our clusters from Queens to Train. On the new Train clusters, customers are complaining that deleting a VM and then immediately creating a new one with the same name (via Terraform for example) intermittently results in a missing DNS record. We can duplicate the issue by building a VM with terraform, tainting it, and applying. > > > > > > > > > > > > Before applying the change, we see the DNS record in the recordset: > > > > > > > > > > > > $ openstack recordset list dva3.vrsn.com. --all |grep openstack-terra > > > > > > | f9aa73c1-84ba-4854-be71-cbb616de672c | 8d1c84082a044a53abe0d519ed9e8c60 | openstack-terra-test-host.dev-ostck.dva3.vrsn.com. | A | 10.220.4.89 | ACTIVE | NONE | > > > > > > $ > > > > > > > > > > > > and we can pull it from the DNS server on the controllers: > > > > > > > > > > > > $ for i in {1..3}; do dig @dva3-ctrl${i}.cloud.vrsn.com -t axfr dva3.vrsn.com. |grep openstack-terra; done > > > > > > openstack-terra-test-host.dev-ostck.dva3.vrsn.com. 1 IN A 10.220.4.89 > > > > > > openstack-terra-test-host.dev-ostck.dva3.vrsn.com. 1 IN A 10.220.4.89 > > > > > > openstack-terra-test-host.dev-ostck.dva3.vrsn.com. 1 IN A 10.220.4.89 > > > > > > > > > > > > After applying the change, we don’t see it: > > > > > > > > > > > > $ openstack recordset list dva3.vrsn.com. --all |grep openstack-terra > > > > > > | f9aa73c1-84ba-4854-be71-cbb616de672c | 8d1c84082a044a53abe0d519ed9e8c60 | openstack-terra-test-host.dev-ostck.dva3.vrsn.com. | A | 10.220.4.89 | ACTIVE | NONE | > > > > > > $ > > > > > > $ for i in {1..3}; do dig @dva3-ctrl${i}.cloud.vrsn.com -t axfr dva3.vrsn.com. |grep openstack-terra; done > > > > > > $ openstack recordset list dva3.vrsn.com. --all |grep openstack-terra > > > > > > $ > > > > > > > > > > > > We see this in the logs: > > > > > > > > > > > > 2021-10-09 01:53:44.307 27 ERROR oslo_messaging.notify.dispatcher oslo_db.exception.DBDuplicateEntry: (pymysql.err.IntegrityError) (1062, "Duplicate entry 'c70e693b4c47402db088c43a5a177134-openstack-terra-test-host.de...' for key 'unique_recordset'") > > > > > > 2021-10-09 01:53:44.307 27 ERROR oslo_messaging.notify.dispatcher [SQL: INSERT INTO recordsets (id, version, created_at, zone_shard, tenant_id, zone_id, name, type, ttl, reverse_name) VALUES (%(id)s, %(version)s, %(created_at)s, %(zone_shard)s, %(tenant_id)s, %(zone_id)s, %(name)s, %(type)s, %(ttl)s, %(reverse_name)s)] > > > > > > 2021-10-09 01:53:44.307 27 ERROR oslo_messaging.notify.dispatcher [parameters: {'id': 'dbbb904c347241a791aa01ca33a87b23', 'version': 1, 'created_at': datetime.datetime(2021, 10, 9, 1, 53, 44, 182652), 'zone_shard': 3184, 'tenant_id': '8d1c84082a044a53abe0d519ed9e8c60', 'zone_id': 'c70e693b4c47402db088c43a5a177134', 'name': 'openstack-terra-test-host.dev-ostck.dva3.vrsn.com.', 'type': 'A', 'ttl': None, 'reverse_name': '.moc.nsrv.3avd.kctso-ved.tsoh-tset-arret-kcatsnepo'}] > > > > > > > > > > > > It appears that Designate is trying to create the new record before the deletion of the old one finishes. > > > > > > > > > > > > Is anyone else seeing this on Train? The same set of actions doesn’t cause this error in Queens. Do we need to change something in our Designate config, to make it wait until the old records are finished deleting before attempting to create the new ones?

1 0

Open stack Ansible 23.1.0.dev35 VM launching errors
by Midhunlal Nb 13 Oct '21

13 Oct '21

Hi team, -->Successfully I installed Openstack ansible 23.1.0.dev35. --->I logged in to horizon and created a new network and launched a vm but I am getting an error. Error: Failed to perform requested operation on instance "hope", the instance has an error status: Please try again later [Error: Build of instance b6f42229-06d6-4365-8a20-07df869f1610 aborted: Failed to allocate the network(s), not rescheduling.]. -->Then I checked log | fault | {'code': 500, 'created': '2021-10-08T12:26:44Z', 'message': 'Build of instance b6f42229-06d6-4365-8a20-07df869f1610 aborted: Failed to allocate the network(s), not rescheduling.', 'details': 'Traceback (most recent call last):\n File "/openstack/venvs/nova-23.1.0.dev42/lib/python3.6/site-packages/nova/virt/libvirt/driver.py", line 7235, in _create_guest_with_network\n post_xml_callback=post_xml_callback)\n File "/usr/lib/python3.6/contextlib.py", line 88, in __exit__\n next(self.gen)\n File "/openstack/venvs/nova-23.1.0.dev42/lib/python3.6/site-packages/nova/compute/manager.py", line 479, in wait_for_instance_event\n actual_event = event.wait()\n File "/openstack/venvs/nova-23.1.0.dev42/lib/python3.6/site-packages/eventlet/event.py", line 125, in wait\n result = hub.switch()\n File "/openstack/venvs/nova-23.1.0.dev42/lib/python3.6/site-packages/eventlet/hubs/hub.py", line 313, in switch\n return self.greenlet.switch()\neventlet.timeout.Timeout: 300 seconds\n\nDuring handling of the above exception, another exception occurred:\n\nTraceback (most recent call last):\n File "/openstack/venvs/nova-23.1.0.dev42/lib/python3.6/site-packages/nova/compute/manager.py", line 2397, in _build_and_run_instance\n accel_info=accel_info)\n File "/openstack/venvs/nova-23.1.0.dev42/lib/python3.6/site-packages/nova/virt/libvirt/driver.py", line 4200, in spawn\n cleanup_instance_disks=created_disks)\n File "/openstack/venvs/nova-23.1.0.dev42/lib/python3.6/site-packages/nova/virt/libvirt/driver.py", line 7258, in _create_guest_with_network\n raise exception.VirtualInterfaceCreateException()\nnova.exception.VirtualInterfaceCreateException: Virtual Interface creation failed\n\nDuring handling of the above exception, another exception occurred:\n\nTraceback (most recent call last):\n File "/openstack/venvs/nova-23.1.0.dev42/lib/python3.6/site-packages/nova/compute/manager.py", line 2219, in _do_build_and_run_instance\n filter_properties, request_spec, accel_uuids)\n File "/openstack/venvs/nova-23.1.0.dev42/lib/python3.6/site-packages/nova/compute/manager.py", line 2458, in _build_and_run_instance\n reason=msg)\nnova.exception.BuildAbortException: Build of instance b6f42229-06d6-4365-8a20-07df869f1610 aborted: Failed to allocate the network(s), not rescheduling.\n'} | Please help me with this error. Thanks & Regards Midhunlal N B

3 9

Learn how users are using OpenStack at OpenInfra Live Keynotes
by Kendall Nelson 13 Oct '21

13 Oct '21

Hello Everyone, You might have heard that the OpenInfra Foundation is hosting its largest free virtual event of this year—OpenInfra Live: Keynote OpenInfra Live: Keynotes: https://openinfra.dev/live/keynotes Date and time: November 17-18 (1500-1700 UTC on each day) Register for free: https://www.eventbrite.com/e/openinfra-live-keynotes-tickets-169507530587 This two day special episode is your best opportunity to meet the newest players to the OpenInfra space and hear about how open source projects, such as OpenStack and Kubernetes, are supporting OpenInfra use cases like hybrid cloud. You will also have the chance to deep dive into the OpenStack user survey results since the launch of the OpenStack User Survey in 2013. Here is a preview of the OpenStack user survey results findings: - Over 300 OpenStack deployments were logged this year, including a significant number of new clouds—in the last 18 months, over 100 new OpenStack clouds have been built, growing the total number of cores under OpenStack management to more than 25,000,000. - Hybrid cloud scenarios continue to be popular, but over half of User Survey respondents indicated that the majority of their cloud infrastructure runs on OpenStack. Upgrades continue to be a challenge that the upstream community tackles with each additional release, but the User Survey shows the majority of organizations are running within the last seven releases. The full report of the OpenStack user survey will be distributed during the OpenInfra Live: Keynotes, so make sure you are registered for the event [2]. Can’t make it to the event? Register anyway, and we will email you a link to the recording after the event! At OpenInfra Live Keynotes, you will also have the opportunity to - interact with leaders of open source projects like OpenStack and Kubernetes to hear how the projects are supporting OpenInfra use cases like hybrid cloud - gain insight into public cloud economics and the role open source technologies play - celebrate as we announce this year’s Superuser Awards winner. This will be the one time everyone will be coming together this year. Come interact with the global OpenInfra community—Live! -Kendall Nelson (diablo_rojo) [1]: https://openinfra.dev/live/keynotes [2]: https://www.eventbrite.com/e/openinfra-live-keynotes-tickets-169507530587

1 0

[cinder] festival of XS reviews 15 October 2021
by Brian Rosmaita 13 Oct '21

13 Oct '21

Hello Cinder community members, This is a reminder that the most recent edition of the Cinder Festival of XS Reviews will be held at the end of this week on Friday 15 October. who: Everyone! what: The Cinder Festival of XS Reviews when: Friday 15 October 2021 from 1400-1600 UTC where: https://meetpad.opendev.org/cinder-festival-of-reviews This recurring meeting can be placed on your calendar by using this handy ICS file: http://eavesdrop.openstack.org/calendars/cinder-festival-of-reviews.ics See you there! brian

1 0

[nova][placement] No meeting next week
by Sylvain Bauza 13 Oct '21

13 Oct '21

As agreed during yesterday's meeting [1], Tuesday Oct 19th's meeting is *CANCELLED* as all of us will be attending the virtual PTG. I'm more than happy tho to see all of you next week thru video ! I'll add the PTG connection details in https://etherpad.opendev.org/p/nova-yoga-ptg -Sylvain [1] https://meetings.opendev.org/meetings/nova/2021/nova.2021-10-12-16.00.log.h…

1 0

[tripleo] Unable to execute pre-introspection and pre-deployment command
by Anirudh Gupta 13 Oct '21

13 Oct '21

3 6

[docs] has_project_guide key
by Peter Matulis 13 Oct '21

13 Oct '21

Does the has_project_guide key in the www/project-data/<RELEASE>.yaml file have any meaning? One of my projects has been dragging this key along from release to release and I do not see it documented [1]. I want to avoid unintended results if that key is removed. Thanks. [1]: https://docs.openstack.org/doc-contrib-guide/doc-tools/template-generator.h… Peter

1 0

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

13 Oct '21

This is a bug report from 10-06-2021-15-09 to 10-13-2021. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Medium - https://bugs.launchpad.net/cinder/+bug/1946736 'Powerflex driver: update supported storage versions'. - https://bugs.launchpad.net/cinder/+bug/1946350 '[gate-failure] nova-live-migration evacuation failure due to slow lvchange -a command in c-vol during volume attachment update'. - https://bugs.launchpad.net/cinder/+bug/1946340 '[gate-failure] Unable to stack on fedora34 due to cinder pulling in oslo.vmware and suds-jurko that uses use_2to3 that is invalid with setuptools >=58.0.0'. - https://bugs.launchpad.net/cinder/+bug/1946263 'NetApp ONTAP Failing migrating volume from/to FlexGroup pool'. Low - https://bugs.launchpad.net/cinder/+bug/1946618 'Add same volume to the group-update does not show proper error'. Wishlist - https://bugs.launchpad.net/cinder/+bug/1946645 '[doc] Install and configure a storage node in cinder'. Cheers -- Sofía Enriquez she/her Software Engineer Red Hat PnT <https://www.redhat.com> IRC: @enriquetaso @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com>

1 0

[KEYSTONE][POLICIES] - Overrides that don't work?
by Gaël THEROND 13 Oct '21

13 Oct '21

Hi team, I'm having a weird behavior with my Openstack platform that makes me think I may have misunderstood some mechanisms on the way policies are working and especially the overriding. So, long story short, I've few services that get custom policies such as glance that behave as expected, Keystone's one aren't. All in all, here is what I'm understanding of the mechanism: This is the keystone policy that I'm looking to override: https://paste.openstack.org/show/bwuF6jFISscRllWdUURL/ This policy default can be found in here: https://opendev.org/openstack/keystone/src/branch/master/keystone/common/po… Here is the policy that I'm testing: https://paste.openstack.org/show/bHQ0PXvOro4lXNTlxlie/ I know, this policy isn't taking care of the admin role but it's not the point. >From my understanding, any user with the project-manager role should be able to add any available user on any available group as long as the project-manager domain is the same as the target. However, when I'm doing that, keystone complains that I'm not authorized to do so because the user token scope is 'PROJECT' where it should be 'SYSTEM' or 'DOMAIN'. Now, I wouldn't be surprised of that message being thrown out with the default policy as it's stated on the code with the following: https://opendev.org/openstack/keystone/src/branch/stable/ussuri/keystone/co… So the question is, if the custom policy doesn't override the default scope_types how am I supposed to make it work? I hope it was clear enough, but if not, feel free to ask me for more information. PS: I've tried to assign this role with a domain scope to my user and I've still the same issue. Thanks a lot everyone!

2 4

[kolla-ansible][neutron] configuration question
by Ignazio Cassano 13 Oct '21

13 Oct '21

Hello Everyone, I need to know if it possible configure kolla neutron ovs with more than one bridge mappings, for example: bridge_mappings = physnet1:br-ex,physnet2:br-ex2 I figure out that in standard configuration ansible playbook create br-ex and add the interface with variable "neutron_external_interface" under br-ex. What can I do if I need to do if I wand more than one bridge ? How kolla ansible playbook can help in this case ? I could use multiple bridges in /etc/kolla/config neutron configuration files, but I do not know how ansible playbook can do the job. because I do not see any variable can help me in /etc/kolla/globals.yml Thanks Ignazio

2 3

Re: [neutron] OVN and dynamic routing
by Francois 13 Oct '21

13 Oct '21

...forgot to add the mailing list in the reply On Wed, 13 Oct 2021 at 10:01, Francois <rigault.francois(a)gmail.com> wrote: > > On Tue, 12 Oct 2021 at 21:46, Dan Sneddon <dsneddon(a)redhat.com> wrote: > > > > On 10/12/21 07:03, Francois wrote: > > > Hello Neutron! > > > I am looking into running stacks with OVN on a leaf-spine network, and > > > have some floating IPs routed between racks. > > > > > > Basically each rack is assigned its own set of subnets. > > > Some VLANs are stretched across all racks: the provisioning VLAN used > > > by tripleo to deploy the stack, and the VLANs for the controllers API > > > IPs. However, each tenant subnet is local to a rack: for example each > > > OVN chassis has a ovn-encap-ip with an IP of the tenant subnet of its > > > own rack. Traffic between 2 racks is sent to a spine, and leaves and > > > spines run some eVPN-like thing: each pair of ToR is a vtep, traffic > > > is encapsulated as VXLAN, and routes between vteps are exchanged with > > > BGP. > > > > > > > There has been a lot of work put into TripleO to allow you to provision > > hosts across L3 boundaries using DHCP relay. You can create a routed > > provisioning network using "helper-address" or vendor-specific commands > > on your top-of-rack switches, and a different subnet and DHCP address > > pool per rack. > Yes I saw that in the doc. I was not planning on using this for reasons I mentioned in another reply (this provisioning network is ""useless most of the time"" since there is almost no provisioning happening :D ) If any, I would love to work on Ironic DHCP-less deployments which was almost working last time I tried and I saw Ironic team contributing fixes since then. > > > > > > I am looking into supporting floating IPs in there: I expect floating > > > IPs to be able to move between racks, as such I am looking into > > > publishing the route for a FIP towards an hypervisor, through BGP. > > > Each fip is a /32 subnet with an hypervisor tenant's IP as next hop. > > > > This is becoming a very common architecture, and that is why there are > > several projects working to achieve the same goal with slightly > > different implementations. > > > > > > > > It seems there are several ideas to achieve this (it was discussed > > > [before][1] in ovs conference) > > > - using [neutron-dynamic-routing][2] - that seems to have some gaps > > > for OVN. It uses os-ken to talk to switches and exchange routes > > > - using [OVN BGP agent][3] that uses FRR, it seems there is a related > > > [RFE][4] for integration in tripleo > > > > > > There is btw also a [BGPVPN][5] project (it does not match my usecase > > > as far as I tried to understand it) that also has some code that talks > > > BGP to switches, already integrated in tripleo. > > > > > > For my tests, I was able to use the neutron-dynamic-routing project > > > (almost) as documented, with a few changes: > > > - for traffic going from VMs to outside the stack, the hypervisor was > > > trying to resolve the "gateway of fIPs" with ARP request which does > > > not make any sense. I created a dummy port with the mac address of the > > > virtual router of the switches: > > > ``` > > > $ openstack port list --mac-address 00:1c:73:00:00:11 -f yaml > > > - Fixed IP Addresses: > > > - ip_address: 10.64.254.1 > > > subnet_id: 8f37 > > > ID: 4028 > > > MAC Address: 00:1c:73:00:00:11 > > > Name: lagw > > > Status: DOWN > > > ``` > > > this prevent the hypervisor to send ARP requests to a non existent gateway > > > - for traffic coming back, we start the neutron-bgp-dragent agent on > > > the controllers. We create the right bgp speaker, peers, etc. > > > - neutron-bgp-dragent seems to work primarily with ovs ml2 plugin, it > > > selects fips and join with ports owned by a "floatingip_agent_gateway" > > > which does not exist on OVN. We can define ourselves some ports so > > > that the dragent is able to find the tenant IP of a host: > > > ``` > > > openstack port create --network provider --device-owner > > > network:floatingip_agent_gateway --host cpu35d.cloud --fixed-ip > > > ip-address=10.64.245.102 ag2 > > > ``` > > > - when creating a floating IP and assigning a port to it, Neutron > > > reads changes from OVN SB and fills the binding information into the > > > port: > > > ``` > > > $ openstack port show -c binding_host_id `openstack floating ip show > > > 10.64.254.177 -f value -c port_id` > > > +-----------------+----------------------------------------+ > > > | Field | Value | > > > +-----------------+----------------------------------------+ > > > | binding_host_id | cpu35d.cloud | > > > +-----------------+----------------------------------------+ > > > ``` > > > this allows the dragent to publish the route for the fip > > > ``` > > > $ openstack bgp speaker list advertised routes bgpspeaker > > > +------------------+---------------+ > > > | Destination | Nexthop | > > > +------------------+---------------+ > > > | 10.64.254.177/32 | 10.64.245.102 | > > > +------------------+---------------+ > > > ``` > > > - traffic reaches the hypervisor but (for reason I don't understand) I > > > had to add a rule > > > ``` > > > $ ip rule > > > 0: from all lookup local > > > 32765: from all iif vlan1234 lookup ovn > > > 32766: from all lookup main > > > 32767: from all lookup default > > > $ ip route show table ovn > > > 10.64.254.177 dev vlan1234 scope link > > > ``` > > > so that the traffic coming for the fip is not immediately discarded by > > > the hypervisor (it's not an ideal solution but it is a workaround that > > > makes my one fIP work!) > > > > > > So all in all it seems it would be possible to use the > > > neutron-dynamic-routing agent, with some minor modifications (eg: to > > > also publish the fip of the OVN L3 gateway router). > > > > > > I am wondering whether I have overlooked anything, and if such kind of > > > deployment (OVN + neutron dynamic routing or similar) is already in > > > use somewhere. Does it make sense to have a RFE for better integration > > > between OVN and neutron-dynamic-routing? > > > > I have been helping to contribute to integrating FRR with OVN in order > > to advertise FIPs and provider network IPs into BGP. The OVN BGP Agent > > is very new, and I'm pretty sure that nobody is using it in production > > yet. However the initial implementation is fairly simple and hopefully > > it will mature quickly. > > > > As you discovered, the solution that uses neutron-bgp-dragent and os-ken > > is not compatible with OVN > Pretty much the contrary, it basically worked. There are a few differences but the gap seems very tiny (unless I overlooked something and I'm fundamentally wrong) I don't understand why a new project would be needed to make it work for OVN. > > >, that is why ovs-bgp-agent is being > > developed. You should be able to try the ovs-bgp-agent with FRR and > > properly configured routing switches, it functions for the basic use case. > > > > The OVN BGP Agent will ensure that FIP and provider network IPs are > > present in the kernel as a /32 or /128 host route, which is then > > advertised into the BGP fabric using the FRR BGP daemon. If the default > > route is received from BGP it will be installed into the kernel by the > > FRR zebra daemon which syncs kernel routes with the FRR BGP routing > > table. The OVN BGP agent installs flows for the Neutron network gateways > > that hand off traffic to the kernel for routing. Since the kernel > > routing table is used, the agent isn't compatible with DPDK fast > > datapath yet. > > > > We don't have good documentation for the OVN BGP integration yet. I've > > only recently been able to make it my primary priority, and some of the > > other engineers which have done the initial proof of concept are moving > > on to other projects. There will be some discussions at the upcoming > > OpenStack PTG about this work, but I am hopeful that the missing pieces > > for your use case will come about in the Yoga cycle. > I did not try to run the OVN BGP agent but I saw your blog posts and I think it's enough to get started with. I still don't get why an extra OVN BGP agent would be needed. One thing I was wondering from the blog posts (and your reply here) is whether every single compute would need connectivity to the physical switches to publish the routes - as the dragent runs on the controller node you only need to configure connectivity between the controllers and the physical switches while in the FRR case you need to open much more. > Would the developments in the Yoga cycle be focused on the OVN BGP agent only, and so there is no interest in improving the neutron-dynamic-routing project ? > Thanks for your insightful comments :) > > > > > > > > > Thanks > > > Francois

1 0

[TripleO] Timeout while introspecting Overcloud Node
by Anirudh Gupta 12 Oct '21

12 Oct '21

Hi Team, We were trying to provision Overcloud Nodes using the Tripleo wallaby release. For this, on Undercloud machine (Centos 8.4), we downloaded the ironic-python and overcloud images from the following link: https://images.rdoproject.org/centos8/wallaby/rdo_trunk/current-tripleo/ After untarring, we executed the command *openstack overcloud image upload* This command setted the images at path /var/lib/ironic/images folder successfully. Then we uploaded our instackenv.json file and executed the command *openstack overcloud node introspect --all-manageable* On the overcloud node, we are getting the Timeout error while getting the agent.kernel and agent.ramdisk image. *http://10.0.1.10/8088/agent.kernel......Connection <http://10.0.1.10/8088/agent.kernel......Connection> timed out (http://ipxe.org/4c0a6092 <http://ipxe.org/4c0a6092>)* *http://10.0.1.10/8088/agent.kernel......Connection <http://10.0.1.10/8088/agent.kernel......Connection> timed out (http://ipxe.org/4c0a6092 <http://ipxe.org/4c0a6092>)* However, from another test machine, when I tried *wget http://10.0.1.10/8088/agent.kernel <http://10.0.1.10/8088/agent.kernel>* - It successfully worked Screenshot is attached for the reference Can someone please help in resolving this issue. Regards Anirudh Gupta

1 1

[TripleO] Issue in running Pre-Introspection
by Anirudh Gupta 12 Oct '21

12 Oct '21

Hi Team, I tried installing Undercloud using the below link: https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/deploym… I am getting the following error: (undercloud) [stack@undercloud ~]$ openstack tripleo validator run --group pre-introspection Selected log directory '/home/stack/validations' does not exist. Attempting to create it. +--------------------------------------+---------------------------------+--------+------------+-----------------+-------------------+-------------+ | UUID | Validations | Status | Host_Group | Status_by_Host | Unreachable_Hosts | Duration | +--------------------------------------+---------------------------------+--------+------------+-----------------+-------------------+-------------+ | 7029c1f6-5ab4-465d-82d7-3f29058012ce | check-cpu | PASSED | localhost | localhost | | 0:00:02.531 | | db059017-30f1-4b97-925e-3f55b586d492 | check-disk-space | PASSED | localhost | localhost | | 0:00:04.432 | | e23dd9a1-90d3-4797-ae0a-b43e55ab6179 | check-ram | PASSED | localhost | localhost | | 0:00:01.324 | | 598ca02d-258a-44ad-b78d-3877321cdfe6 | check-selinux-mode | PASSED | localhost | localhost | | 0:00:01.591 | | c4435b4c-b432-4a1e-8a99-00638034a884 | *check-network-gateway | FAILED* | undercloud | *No host matched* | | | | cb1eed23-ef2f-4acd-a43a-86fb09bf0372 | *undercloud-disk-space | FAILED* | undercloud | *No host matched* | | | | abde5329-9289-4b24-bf16-c4d82b03e67a | *undercloud-neutron-sanity-check | FAILED* | undercloud | *No host matched* | | | | d0e5fdca-ece6-4a37-b759-ed1fac31a10f | *ctlplane-ip-range | FAILED* | undercloud | No host matched | | | | 91511807-225c-4852-bb52-6d0003c51d49 | *dhcp-introspection | FAILED* | undercloud | No host matched | | | | e96f7704-d2fb-465d-972b-47e2f057449c |* undercloud-tokenflush | FAILED *| undercloud | No host matched | | | As per the validation link, https://docs.openstack.org/tripleo-validations/wallaby/validations-pre-intr… check-network-gateway If gateway in undercloud.conf is different from local_ip, verify that the gateway exists and is reachable Observation - In my case IP specified in local_ip and gateway, both are pingable, but still this error is being observed ctlplane-ip-range¶ <https://docs.openstack.org/tripleo-validations/wallaby/validations-pre-intr…> Check the number of IP addresses available for the overcloud nodes. Verify that the number of IP addresses defined in dhcp_start and dhcp_end fields in undercloud.conf is not too low. - ctlplane_iprange_min_size: 20 Observation - In my case I have defined more than 20 IPs Similarly for disk related issue, I have dedicated 100 GB space in /var and / Filesystem Size Used Avail Use% Mounted on devtmpfs 12G 0 12G 0% /dev tmpfs 12G 84K 12G 1% /dev/shm tmpfs 12G 8.7M 12G 1% /run tmpfs 12G 0 12G 0% /sys/fs/cgroup /dev/mapper/cl-root 100G 2.5G 98G 3% / /dev/mapper/cl-home 47G 365M 47G 1% /home /dev/mapper/cl-var 103G 1.1G 102G 2% /var /dev/vda1 947M 200M 747M 22% /boot tmpfs 2.4G 0 2.4G 0% /run/user/0 tmpfs 2.4G 0 2.4G 0% /run/user/1000 Despite setting al the parameters, still I am not able to pass pre-introspection checks. *"NO Host Matched" *is found in the table. Regards Anirudh Gupta

2 3

[neutron] OVN and dynamic routing
by Francois 12 Oct '21

12 Oct '21

Hello Neutron! I am looking into running stacks with OVN on a leaf-spine network, and have some floating IPs routed between racks. Basically each rack is assigned its own set of subnets. Some VLANs are stretched across all racks: the provisioning VLAN used by tripleo to deploy the stack, and the VLANs for the controllers API IPs. However, each tenant subnet is local to a rack: for example each OVN chassis has a ovn-encap-ip with an IP of the tenant subnet of its own rack. Traffic between 2 racks is sent to a spine, and leaves and spines run some eVPN-like thing: each pair of ToR is a vtep, traffic is encapsulated as VXLAN, and routes between vteps are exchanged with BGP. I am looking into supporting floating IPs in there: I expect floating IPs to be able to move between racks, as such I am looking into publishing the route for a FIP towards an hypervisor, through BGP. Each fip is a /32 subnet with an hypervisor tenant's IP as next hop. It seems there are several ideas to achieve this (it was discussed [before][1] in ovs conference) - using [neutron-dynamic-routing][2] - that seems to have some gaps for OVN. It uses os-ken to talk to switches and exchange routes - using [OVN BGP agent][3] that uses FRR, it seems there is a related [RFE][4] for integration in tripleo There is btw also a [BGPVPN][5] project (it does not match my usecase as far as I tried to understand it) that also has some code that talks BGP to switches, already integrated in tripleo. For my tests, I was able to use the neutron-dynamic-routing project (almost) as documented, with a few changes: - for traffic going from VMs to outside the stack, the hypervisor was trying to resolve the "gateway of fIPs" with ARP request which does not make any sense. I created a dummy port with the mac address of the virtual router of the switches: ``` $ openstack port list --mac-address 00:1c:73:00:00:11 -f yaml - Fixed IP Addresses: - ip_address: 10.64.254.1 subnet_id: 8f37 ID: 4028 MAC Address: 00:1c:73:00:00:11 Name: lagw Status: DOWN ``` this prevent the hypervisor to send ARP requests to a non existent gateway - for traffic coming back, we start the neutron-bgp-dragent agent on the controllers. We create the right bgp speaker, peers, etc. - neutron-bgp-dragent seems to work primarily with ovs ml2 plugin, it selects fips and join with ports owned by a "floatingip_agent_gateway" which does not exist on OVN. We can define ourselves some ports so that the dragent is able to find the tenant IP of a host: ``` openstack port create --network provider --device-owner network:floatingip_agent_gateway --host cpu35d.cloud --fixed-ip ip-address=10.64.245.102 ag2 ``` - when creating a floating IP and assigning a port to it, Neutron reads changes from OVN SB and fills the binding information into the port: ``` $ openstack port show -c binding_host_id `openstack floating ip show 10.64.254.177 -f value -c port_id` +-----------------+----------------------------------------+ | Field | Value | +-----------------+----------------------------------------+ | binding_host_id | cpu35d.cloud | +-----------------+----------------------------------------+ ``` this allows the dragent to publish the route for the fip ``` $ openstack bgp speaker list advertised routes bgpspeaker +------------------+---------------+ | Destination | Nexthop | +------------------+---------------+ | 10.64.254.177/32 | 10.64.245.102 | +------------------+---------------+ ``` - traffic reaches the hypervisor but (for reason I don't understand) I had to add a rule ``` $ ip rule 0: from all lookup local 32765: from all iif vlan1234 lookup ovn 32766: from all lookup main 32767: from all lookup default $ ip route show table ovn 10.64.254.177 dev vlan1234 scope link ``` so that the traffic coming for the fip is not immediately discarded by the hypervisor (it's not an ideal solution but it is a workaround that makes my one fIP work!) So all in all it seems it would be possible to use the neutron-dynamic-routing agent, with some minor modifications (eg: to also publish the fip of the OVN L3 gateway router). I am wondering whether I have overlooked anything, and if such kind of deployment (OVN + neutron dynamic routing or similar) is already in use somewhere. Does it make sense to have a RFE for better integration between OVN and neutron-dynamic-routing? Thanks Francois [1]: https://www.openvswitch.org/support/ovscon2020/slides/OVS-CONF-2020-OVN-WIT… [2]: https://docs.openstack.org/neutron/latest/admin/config-bgp-dynamic-routing.… [3]: https://ltomasbo.wordpress.com/2021/02/04/openstack-networking-with-bgp/ [4]: https://specs.openstack.org/openstack/tripleo-specs/specs/wallaby/triplo-bg… [5]: https://github.com/openstack/tripleo-heat-templates/blob/master/environment…

4 5

After rebuilding Queens clusters on Train, race condition causes Designate record creation to fail
by Braden, Albert 12 Oct '21

12 Oct '21

Hello everyone. It's great to be back working on OpenStack again. I'm at Verisign now. I can hardly describe how happy I am to have an employer that does not attach nonsense to the bottom of my emails! We are rebuilding our clusters from Queens to Train. On the new Train clusters, customers are complaining that deleting a VM and then immediately creating a new one with the same name (via Terraform for example) intermittently results in a missing DNS record. We can duplicate the issue by building a VM with terraform, tainting it, and applying. Before applying the change, we see the DNS record in the recordset: $ openstack recordset list dva3.vrsn.com. --all |grep openstack-terra | f9aa73c1-84ba-4854-be71-cbb616de672c | 8d1c84082a044a53abe0d519ed9e8c60 | openstack-terra-test-host.dev-ostck.dva3.vrsn.com. | A | 10.220.4.89 | ACTIVE | NONE | $ and we can pull it from the DNS server on the controllers: $ for i in {1..3}; do dig @dva3-ctrl${i}.cloud.vrsn.com -t axfr dva3.vrsn.com. |grep openstack-terra; done openstack-terra-test-host.dev-ostck.dva3.vrsn.com. 1 IN A 10.220.4.89 openstack-terra-test-host.dev-ostck.dva3.vrsn.com. 1 IN A 10.220.4.89 openstack-terra-test-host.dev-ostck.dva3.vrsn.com. 1 IN A 10.220.4.89 After applying the change, we don't see it: $ openstack recordset list dva3.vrsn.com. --all |grep openstack-terra | f9aa73c1-84ba-4854-be71-cbb616de672c | 8d1c84082a044a53abe0d519ed9e8c60 | openstack-terra-test-host.dev-ostck.dva3.vrsn.com. | A | 10.220.4.89 | ACTIVE | NONE | $ $ for i in {1..3}; do dig @dva3-ctrl${i}.cloud.vrsn.com -t axfr dva3.vrsn.com. |grep openstack-terra; done $ openstack recordset list dva3.vrsn.com. --all |grep openstack-terra $ We see this in the logs: 2021-10-09 01:53:44.307 27 ERROR oslo_messaging.notify.dispatcher oslo_db.exception.DBDuplicateEntry: (pymysql.err.IntegrityError) (1062, "Duplicate entry 'c70e693b4c47402db088c43a5a177134-openstack-terra-test-host.de...' for key 'unique_recordset'") 2021-10-09 01:53:44.307 27 ERROR oslo_messaging.notify.dispatcher [SQL: INSERT INTO recordsets (id, version, created_at, zone_shard, tenant_id, zone_id, name, type, ttl, reverse_name) VALUES (%(id)s, %(version)s, %(created_at)s, %(zone_shard)s, %(tenant_id)s, %(zone_id)s, %(name)s, %(type)s, %(ttl)s, %(reverse_name)s)] 2021-10-09 01:53:44.307 27 ERROR oslo_messaging.notify.dispatcher [parameters: {'id': 'dbbb904c347241a791aa01ca33a87b23', 'version': 1, 'created_at': datetime.datetime(2021, 10, 9, 1, 53, 44, 182652), 'zone_shard': 3184, 'tenant_id': '8d1c84082a044a53abe0d519ed9e8c60', 'zone_id': 'c70e693b4c47402db088c43a5a177134', 'name': 'openstack-terra-test-host.dev-ostck.dva3.vrsn.com.', 'type': 'A', 'ttl': None, 'reverse_name': '.moc.nsrv.3avd.kctso-ved.tsoh-tset-arret-kcatsnepo'}] It appears that Designate is trying to create the new record before the deletion of the old one finishes. Is anyone else seeing this on Train? The same set of actions doesn't cause this error in Queens. Do we need to change something in our Designate config, to make it wait until the old records are finished deleting before attempting to create the new ones?

2 6

[Octavia] Can not create LB on SRIOV network
by Zhang, Jing C. (Nokia - CA/Ottawa) 12 Oct '21

12 Oct '21

I can not create Octavia LB on SRIOV network in Train. I went to Octavia story board, did a search but was unable to figure out (the story for SRIOV...). I left a comment under this story, I re-post my questions there, hoping someone knows the answer. Thank you so much Jing https://storyboard.openstack.org/#!/story/2006886 Add VM SRIOV Interface Config Guide (Openstack) Hi, In Openstack train release, creating Octavia LB on SRIOV network fails. I come here to search if there is already a plan to add this support, and see this story. This story gives the impression that the capability is already supported, it is a matter of adding user guide. So, my question is, in which Openstack release, creating LB on SRIOV network is supported? Thank you

3 7

[Xena] It works!
by tjoen 12 Oct '21

12 Oct '21

Just testing every release since Train on an LFS system with Python-3.9 cryptography-35.0.0 is necessary Thank you all

3 5

[ironic] No weekly meeting on Oct18
by Iury Gregory 12 Oct '21

12 Oct '21

Hello ironicers! Just a reminder that on Oct 18, we won't have our weekly meeting because we have a session in the PTG. -- *Att[]'sIury Gregory Melo Ferreira * *MSc in Computer Science at UFCG* *Part of the ironic-core and puppet-manager-core team in OpenStack* *Software Engineer at Red Hat Czech* *Social*: https://www.linkedin.com/in/iurygregory *E-mail: iurygregory(a)gmail.com <iurygregory(a)gmail.com>*

1 0