April 2022 - openstack-discuss - lists.openstack.org

[neutron][ovn] Need VM accessible on Internet, and able to access DC resources
by Chris DiLorenzo 14 Apr '22

14 Apr '22

To Internet To Data Center Resources (10.x) - -/ - -/ / -/ / -/ / -/ -/ -/ / -/ / Public Provider Network / Private Provider Network / +------------------------+ +-------------------------+ | | | | | | | | | Router #1 |--------------| Router #2 | | SNAT Enabled | .2| SNAT Enabled | | | | | | | | | +------------------------+ +-------------------------+ | 192.168.1.1 | | | | | | | | | 192.168.1.10 (FIP: Public IP) +---------|-------------+ | | | | | | | VM | | | | | +-----------------------+ I am running Openstack Xena with OVN and distributed FIP enabled. We are trying to come up with a way to make a VM accessible from the Internet and still have it able to access internal Data Center services. Our thought is to setup a router between the tenant network and an internet accessible provider network. We'll assign a FIP to the VM. Then, we create an additional router that connects to the same tenant network but routes to a provider network that has access to everything inside the DC. We would then add a static route on Router #1 like 10.0.0.0/8 nexthop 192.168.1.2. I've tried setting this up in our lab, but it's not working. I can't ping to anything inside the DC. Should this work? Any best practice here we should look at? Thanks Chris

1 0

[cinder] Bug deputy report for week of 04-13-2022
by Sofia Enriquez 13 Apr '22

13 Apr '22

This is a bug report from 03-30-2022 to 04-13-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- High - https://bugs.launchpad.net/os-brick/+bug/1967790 " Encryptor connect_volume not changing the symlink." Fix proposed to marter. Medium - https://bugs.launchpad.net/cinder/+bug/1968746 "cinder-manage db sync fails due to row size too large." Unassigned. - https://bugs.launchpad.net/cinder/+bug/1968645 "Concurrent migration of vms with the same multiattach volume fails." Unassigned. Low - https://bugs.launchpad.net/cinder/+bug/1968170 "reimage_volume failure message action does not exist." Unassigned. Cheers, -- Sofía Enriquez she/her Software Engineer Red Hat PnT <https://www.redhat.com> IRC: @enriquetaso @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com>

1 0

Error while creating attached to an external interface
by A Monster 13 Apr '22

13 Apr '22

I'm trying to launch an instance attached to an external network, but I get an all host exhausted error message, and the neutron log file show the following error : *ERROR neutron.plugins.ml2.managers [req-6979d5fd-8e6a-4802-a758-e4882b7ac5b6 397fa0267ae340e1b24a3a96ae302f32 05b9f31fca434f7a96b63a1d17e8b14c - default default] Failed to bind port d57ac8f5-7904-495f-a4b9-9b23df681634 on host compute1.localdomain for vnic_type normal using segments [{'id': '475c70c2-6a35-4721-a726-cbf8c0b7e778', 'network_type': 'flat', 'physical_network': 'physnet2', 'segmentation_id': None, 'network_id': 'a1c2cc8f-6a04-48ce-9d87-a351da1d3f3e'}]* But when I try to launch an instance using another external network, it works just fine.

1 0

[neutron] Zed PTG Summary
by Lajos Katona 13 Apr '22

13 Apr '22

Hi, I will try to summarize the Neutron PTG sessions during the last week. The etherpad which we used: https://etherpad.opendev.org/p/neutron-zed-ptg # Day 1 (Monday April 4.) ## Yoga retrospective (I just list here the topics, not every discussion under them): * Good things ** New active people around the team ** Revived project: neutron-fwaas ** video CI meetings every second week are very good IMO ** OVN backend is getting more and more attention and there are less gaps between OVN and OVS backends * Bad / Not so good: ** less and less active people ** to much depends on Red Hat - ~66% of reviews, ~62% of commits (in Neutron official projects) ** lack of maintainers for some stadium projects (neutron-vpnaas) and some backends/drivers (linuxbridge) * As action we previously decided to have a forum session during the Berlin Summit to discuss the lack of activity/maintainers for some backends and stadium projects hopefully with some operators also. ## Short update on bgp related blueprints https://etherpad.opendev.org/p/neutron-zed-ptg#L111 The development of these blueprints are stopped, we will revert the already merged code. # Day 2 (Tuesday April 5.) ## Have nova / os-vif delete the trunk bridges to avoid race conditions The creation of trunk bridges now done by os-vif, and the deletion is done by Neutron, to avoid the race condition we agreed to have both operations done by os-vif. ## skip-level upgrade (tick-tick) We discussed together how this affects Neutron, what is working currently and what is in front of us. We have periodic jobs for ovs and ovn backend. Actions: * Make ovn grenade upgrade jobs green ## When we say something is not supported? * Recently from the Neutron stadium neutron-vpnaas project was that lost all maintainers. Neutron core team keeps an eye on the gate of networking projects, and keep them green, but if there is nobody with specific knowledge for the given area we can't solve the bugs. * We have similar problems with "in-tree" drivers also, a good example is the linuxbridge driver. Agreement was to keep the current approach for stadium project, so send out mail to openstack-discuss, asking for help, and if nobody appears, make the project retired and delete the code but keep git history for it. For in-tree code (drivers, extensions....): * We keep existing jobs for linuxbridge driver for example, but when the tests start to fail we skip them and finally we stop the job also. To make it clear for operators we add warning logs highlighting that the given feature/driver is experimental, and introduce cfg option to enable such features explicitly. We plan to discuss these questions during the Berlin Summit with operators. ## Prefix delegation for Openstack Neutron aka: dibbler tool for dhcpv6 is concluded The original bug: https://bugs.launchpad.net/neutron/+bug/1916428 * The tool behind PD, Dibbler is no more maintained and the suggested tool ISC Kea has no DHCP client actually. * this feature is not tested in upstream CI Due to these we decided to mark prefix delegation as experimental feature. # Day 3 (Wednesday April 6.) ## neutron-dynamic-routing + OVN Redhat works on a BGP solution for OVN, that is ovn-bgp-agent, and currently it doesn't need the existing API in neutron-dynamic-routing. The current approach to make neutron-dynamic-routing work with OVN will be checked. ## Option for OVN to disable DHCP/DNS and use dhcp-agent instead Technically it is possible, a new RFE will be proposed and the drivers team will discuss the usecase behind it. ## CI status / zuul job config errors In the list of zuul cfg errors ( https://zuul.opendev.org/t/openstack/config-errors ) old Neutron stadium branches are listed. * Decision was to EOL these old branches where fixing is not possible. Another topic was from Slawek if we want to have neutron-tempest-plugin-api-ovs job, and the agreement was to merge OVS scenario and API jobs. ## inconsistencies in OVS firewall on an agent restart We will go for a cfg option to select between OVS flow installation in batches and per port, and operators can select which is best for their environment. ## Pain Points TC started a discussion to cover the collected operator pain points, last week we checked again the list for Neutron ( https://etherpad.opendev.org/p/pain-point-elimination#L268) * neutron (via python calls) and OVN (via C calls) can have different ideas about what the hostname is, particulary if a deployer (rightly or wrongly) sets their hostname to be an FQDN ** it was fixed: https://review.opendev.org/q/Iea2533f4c52935b4ecda9ec22fb619c131febfa1 * Useful error msg when network deletion fails due to existing resources on it ** done: https://review.opendev.org/c/openstack/neutron/+/821935 * Open vSwitch Agent excess logging at INFO level ** we check if we can change some to debug, Slawek create a DNM job with only info logs to discuss during one of the coming meetings. * OVN: Spoofing of DNS reponses seems very wrong behavior ** We agreed that for this we need an RFE (see above for disabling OVN DNS/DHCP) ## Edge topics Together with the Designate team we agreed that this is more a documentation problem based on our current understanding. Based on Redhat downstream bugs for edge deployments we try to cover these in this cycle. # Day 4 (Thursday April 7.) We have no sassions. # Day 5 (Friday April 8.) ## Nova - Neutron xproject ### How to require ml2 plugins to implement multiple port bindings The problem is that there are old drivers (hyperv perhaps and others) that do not implement it and this cause a lot of extra code path in Nova. Sean suggested a Forum topic for Berlin to discuss it with operators also. ### Is heal_instance_info_cache_interval still needed? Let's create a job which sets heal_instance_info_cache_interval to 0, and decide the next steps based on the results. The happy moment with the team screenshot: https://photos.app.goo.gl/P6YuYgxzqEiv2gHt8 I hope next time we can meet in person :-) Thanks to everybody for the great discussions. Lajos Katona (lajoskatona)

1 0

[horizon] Cancelling Today's Weekly meeting
by vishal manchanda 13 Apr '22

13 Apr '22

Hello Team, I won't be able to chair today's horizon weekly meeting due to some travel. So if someone from team can host it on my behalf or we can skip this week meeting. Note: I will join office from thrusday so if anything urgent please reach out to horizon core team. Thanks & regards, Vishal Manchanda

1 0

[Trove][Xena] Errors when creating postgresql insances
by wodel youchi 13 Apr '22

13 Apr '22

Hi, I defined a postgresql data store with two versions 10 and 12. When creating db instances I am getting different errors : *For Postgresql 10, I am getting : * Traceback (most recent call last): File "/var/lib/kolla/venv/lib/python3.6/site-packages/trove/taskmanager/models.py", line 436, in wait_for_instance time_out=timeout) File "/var/lib/kolla/venv/lib/python3.6/site-packages/trove/common/utils.py", line 223, in poll_until return wait_for_task(task) File "/var/lib/kolla/venv/lib/python3.6/site-packages/trove/common/utils.py", line 207, in wait_for_task return polling_task.wait() File "/var/lib/kolla/venv/lib/python3.6/site-packages/eventlet/event.py", line 125, in wait result = hub.switch() File "/var/lib/kolla/venv/lib/python3.6/site-packages/eventlet/hubs/hub.py", line 313, in switch return self.greenlet.switch() File "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_service/loopingcall.py", line 150, in _run_loop result = func(*self.args, **self.kw) File "/var/lib/kolla/venv/lib/python3.6/site-packages/trove/common/utils.py", line 194, in poll_and_check obj = retriever() File "/var/lib/kolla/venv/lib/python3.6/site-packages/trove/taskmanager/models.py", line 791, in _service_is_active raise TroveError(_("Service not active, status: %s") % status) trove.common.exception.TroveError: Service not active, status: failed to spawn ==> trove-conductor.log <== 2022-04-13 00:26:52.334 124 ERROR trove.conductor.manager [-] Guest exception on request req-b5bd49e8-e147-41b2-8292-2900bb4022a1: ['Traceback (most recent call last):\n', ' File "/opt/guest-agent-venv/lib/python3.6/site-packages/trove/guestagent/datastore/manager.py", line 218, in prepare\n ds_version=ds_version)\n', ' File "/opt/guest-agent-venv/lib/python3.6/site-packages/trove/guestagent/datastore/manager.py", line 234, in _prepare\n cluster_config, snapshot, ds_version=ds_version)\n', ' File "/opt/guest-agent-venv/lib/python3.6/site-packages/osprofiler/profiler.py", line 160, in wrapper\n result = f(*args, **kwargs)\n', ' File "/opt/guest-agent-venv/lib/python3.6/site-packages/trove/guestagent/datastore/postgres/manager.py", line 161, in do_prepare\n self.app.start_db(ds_version=ds_version, command=command)\n', ' File "/opt/guest-agent-venv/lib/python3.6/site-packages/trove/guestagent/datastore/postgres/service.py", line 229, in start_db\n raise exception.TroveError("Failed to start database service")\n', *'trove.common.exception.TroveError: Failed to start database service\n']* *And for Postgresql 12, I am getting :* Server type: guest Traceback (most recent call last): File "/opt/guest-agent-venv/lib/python3.6/site-packages/trove/guestagent/datastore/manager.py", line 845, in create_user self.adm.create_users(users) File "/opt/guest-agent-venv/lib/python3.6/site-packages/trove/guestagent/datastore/postgres/service.py", line 516, in create_users self.create_user(models.PostgreSQLUser.deserialize(user), None) File "/opt/guest-agent-venv/lib/python3.6/site-packages/trove/guestagent/datastore/postgres/service.py", line 549, in create_user [models.PostgreSQLSchema.deserialize(db) for db in user.databases]) File "/opt/guest-agent-venv/lib/python3.6/site-packages/trove/guestagent/datastore/postgres/service.py", line 558, in _grant_access [db.name for db in databases], File "/opt/guest-agent-venv/lib/python3.6/site-packages/trove/guestagent/datastore/postgres/service.py", line 432, in grant_access database=database, File "/opt/guest-agent-venv/lib/python3.6/site-packages/trove/guestagent/datastore/postgres/service.py", line 723, in psql return self.connection.execute(statement) File "/opt/guest-agent-venv/lib/python3.6/site-packages/trove/guestagent/datastore/postgres/service.py", line 763, in execute autocommit=True) File "/opt/guest-agent-venv/lib/python3.6/site-packages/trove/guestagent/datastore/postgres/service.py", line 776, in _execute_stmt cursor.execute(cmd, data_values) psycopg2.errors.InvalidCatalogName: database "dbweb01" does not exist And this error from > ==> trove-conductor.log <== > 2022-04-12 23:58:11.689 46 ERROR trove.conductor.manager [-] Guest > exception on request req-7c0e005a-2b02-4acf-bdc5-e9d7a964cd7e: > ['Traceback (most recent call last):\n', ' File > "/opt/guest-agent-venv/lib/python3.6/site-packages/trove/guestagent/datastore/manager.py", > line 808, in create_database\n return > self.adm.create_databases(databases)\n', ' File > "/opt/guest-agent-venv/lib/python3.6/site-packages/trove/guestagent/datastore/postgres/service.py", > line 464, in create_databases\n > self.create_database(models.PostgreSQLSchema.deserialize(database))\n', ' > File > "/opt/guest-agent-venv/lib/python3.6/site-packages/trove/guestagent/datastore/postgres/service.py", > line 477, in create_database\n collation=database.collate,\n', ' File > "/opt/guest-agent-venv/lib/python3.6/site-packages/trove/guestagent/datastore/postgres/service.py", > line 723, in psql\n return self.connection.execute(statement)\n', ' > File > "/opt/guest-agent-venv/lib/python3.6/site-packages/trove/guestagent/datastore/postgres/service.py", > line 763, in execute\n autocommit=True)\n', ' File > "/opt/guest-agent-venv/lib/python3.6/site-packages/trove/guestagent/datastore/postgres/service.py", > line 776, in _execute_stmt\n cursor.execute(cmd, data_values)\n', > 'psycopg2.errors.ActiveSqlTransaction: *CREATE DATABASE cannot run inside > a transaction block\n\n']* > Regards.

1 0

[openstack-helm] Dropping train support
by Gage Hugo 13 Apr '22

13 Apr '22

Hi all, One of the topics from the latest PTG discussions[0] was looking to drop support of the Train release from our charts due to a lack of interest in maintaining them and several issues with broken images due to dependencies. As a result of those discussions, we'd like to make dropping Train support a goal for this cycle. If anyone is still using Train and has a pressing issue where they cannot upgrade, please reach out and we can discuss a path forward. [0] https://etherpad.opendev.org/p/openstack-helm-zed-ptg Thanks

1 0

[openstack-helm] openstack-helm-addons and docs repository retirement
by Gage Hugo 13 Apr '22

13 Apr '22

Hey everyone, We recently had a PTG session and one of the topics that was discussed was the retirement of the openstack-helm-addons and openstack-helm-docs repositories. This topic has been mentioned now for several PTGs and from our discussion at the latest one, it was determined that due to the lack of updates to the repos as well as the charts themselves receiving no real maintenance, we would look to retire both these repositories this cycle. If anyone is still using the 3 charts that still exist in the repos and would like to maintain them, please let us know. Thanks!

1 0

[nova] final release before Victoria Extended Maintenance transition?
by Előd Illés 13 Apr '22

13 Apr '22

Hi Nova folks! We have released from stable/victoria quite recently, but there are still many open bug fixes on it [1]. If anyone from vendors / operators / developers would like to have any bugfix to be released in Victoria before the Extended Maintenance transition, please feel free to add it / mark them at our nova-stable-victoria-em etherpad [1]. Please consider that the transition deadline is in 2 weeks, so this needs to be ready as soon as possible. Nova stable cores are also welcome to review any patches. If there will be merged patches that we could release before the deadline, then I'll prepare the release patch. [1] https://etherpad.opendev.org/p/nova-stable-victoria-em Thanks, Előd

1 0

Network Node Scaling
by Adivya Singh 13 Apr '22

13 Apr '22

Hi Team, Is there any specified link available which i can go through and do "Network Node Scaling" in my Environment. We are running Openstack Xena in my environment Regards Adivya Singh

3 3