- openstack-discuss - lists.openstack.org

[all][neutron][neutron-vpnaas] Maintainers needed
by Lajos Katona 26 Apr '22

26 Apr '22

Hi, In the last few cycles neutron-vpnaas has no serious maintainers, and most patches merged were from Neutron core team or from Release team. Recently even neutron-vpnaas gate jobs started to fail. During the Zed PTG we discussed this topic (see [1]), For the maintenance we need someone to be the contact person for the project, who takes care of the project’s CI and review patches, answers bugs. Of course that’s only a minimal requirement. If the new maintainer works on new features for the project, it’s even better :) If we don’t have any new maintainer(s) before milestone Zed-2, which is July 11 - July 15 week according to [2], we will start marking neutron-vpnaas as deprecated and in the next cycle (AA, or perhapc 2023.1) we will propose to retire the project. So if You are using this project now, or if You have customers who are using it, please consider the possibility of maintaining it. Otherwise, please be aware that it is highly possible that the project will be deprecated and moved out from the official OpenStack projects. [1]: https://etherpad.opendev.org/p/neutron-zed-ptg#L201 [2]: https://releases.openstack.org/zed/schedule.html Lajos Katona (lajoskatona)

2 2

[cinder] how cinder gets the volume name when restore from a backup?
by Tony Liu 26 Apr '22

26 Apr '22

Hi, Here is what I do. * Create a volume. * Create a backup of this volume. * Delete the volume. * Restore the volume from backup. The restored volume has different UUID, but the same name. I don't see volume name is stored in backup metadata. How does Cinder know the volume name when restore it from backup, given the volume is already deleted? Thanks! Tony

2 2

retention policy for deleted resource in database
by Tony Liu 26 Apr '22

26 Apr '22

Hi, I see the record for deleted resource stay in database. What's the retention policy for those records? Is it configurable? Any manual cleanup is required? Thanks! Tony

2 2

[neutron] Bug Deputy Report Apr 18 - Apr 24
by Oleg Bondarev 25 Apr '22

25 Apr '22

Hello Team, Bug report for the week of Apr 18 is below. Two OVN bugs (including Invalid one) need triage from the OVN team. High ------ - https://bugs.launchpad.net/neutron/+bug/1969615 - OVS: flow loop is created with openvswitch version 2.16 - Opinion - seems more an issue in OVS rather than a bug in Neutron - Unassigned Undecided -------------- - https://bugs.launchpad.net/neutron/+bug/1969592 - [OVN] Frequent DB leader changes causes 'VIF creation failed' on nova side - New - Unassigned Invalid --------- - https://bugs.launchpad.net/neutron/+bug/1969354 - ovn-controller don't update new flows - Invalid - but reporter updated with additional info - Unassigned Thanks, Oleg

1 0

[ironic][ptg] Zed PTG Summary
by Iury Gregory 25 Apr '22

25 Apr '22

Hello Ironicers! Sorry for the delay to provide a summary about our PTG =) First of all, thank you to all contributors that took some time to join our sessions! During the sessions we had a peak of 13 attendees on the last three days. Day1 We only had two topics: Feedback about the Yoga Cycle and What should we do about specs. During the of we did a retrospective about the Yoga Cycle, we discussed the good and bad things that happened during the cycle and how we can make things better. In the discussion about what we should do about specs we come up with some ideas to improve our process when we think a spec should be required. Day2: On this day most of the discussions were around topics that can be managing machines. How we can decrease the cost of Data Centers that needs to keep all their machine on even if they are not active or taking minimal load, we would provide a way to power tuning nodes that are already deployed (in the ironic perspective this is a way to reconfigure a node that is already active), we also talked about turning down power usage if we are able to identify that IPA is idle. The custom deploy timeout topic had no strong objections, since we have a single configuration that handles the timeout for all steps we think we can improve this, we still need to define some details related to the implementation after we have the RFE. We discussed how we can generate the inspector.ipxe configuration if we notice some changes in the configuration of the deployment. Day3: We started this day looking at the survey results, this gave us some ideas on possible areas we should improve. The ironic safeguard topic was focusing on two main things: queuing (limit the max number of concurrent cleaning operations) and data disk protection (only clean the root disk (or give a list of skip-disks/disks-to-clean). The community decided that this seems like a good idea and we defined some of the possible paths forwards related to how it could be implemented. The redfish gateway and related ideas topic brought an interesting idea to have an ironic driver that can execute a "script" that is required for their HW to start working properly, there is a recording from the first meeting that can provide more details =). The per-node clean steps topic had no objections, we think this will improve the operators experience for scenarios where they would need specific steps for running on a node that has different disk configuration. Day4: Most of the topics on this day were focused on networking. We discussed the status of OVN DHCP support and how we will move forward on our side to make things work after Neutron and OVN have all the necessary bits in place. During the next topic we talked about adding device configuration capabilities for networking-baremetal since in multi-tenant BMaaS there is a need to configure the ToR network devices (Access/Edge Switches) and many vendors have abandoned their ML2 mechanism plug-ins to support this, so now we are looking to add support for new mechanisms that have more features that could improve the operators experience. We focused on discussing the pros/cons about Netconf and Yang but also other alternatives solutions. The other topic we discussed were: - netboot deprecation: we discussed how we should move forward with some of our testing for partition images + UEFI. - Bluefield DPU: not much discussion since we didn't have many folks interested on the topic. - Anaconda driver: we talked about how we can get a CI for testing the driver. You can find more information about the topics and the discussions in our etherpad: https://etherpad.opendev.org/p/ironic-zed-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

[largescale-sig] Skipping meeting this week
by Thierry Carrez 25 Apr '22

25 Apr '22

Hi everyone, Due to a shortage of participants and meeting chairs, we will skip the meeting planned this week for the Large Scale SIG. Our next meeting will be May 11th at 15UTC in #openstack-operators. You can add topics to discuss to our agenda etherpad: https://etherpad.opendev.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez (ttx)

1 0

error
by Firas Hlel 25 Apr '22

25 Apr '22

Firas Hlel <firashlel750(a)gmail.com> jeu. 21 avr. 09:02 (il y a 4 jours) À openstack-discuss Hi all, I am working on a project Openstack in linux ubuntu 20.04. I want to create a cluster hadoop with one master-node and three worker-nodes and i have a problem with a cluster that doesn't work. Status ERROR: Creating cluster failed for the following reason(s): Failed to create trust Error ID: ef5e8b0a-8e6d-4878-bebb-f37f4fa50a88, Failed to create trust Error ID: 43157255-86af-4773-96c1-a07ca7ac66ed. links: https://docs.openstack.org/devstack/latest/ File local.conf : [[local|localrc]] ADMIN_PASSWORD=secret DATABASE_PASSWORD=secret RABBIT_PASSWORD=secret SERVICE_PASSWORD=$ADMIN_PASSWORD HOST_IP=10.0.2.15 LOGFILE=$DEST/logs/stack.sh.log SWIFT_REPLICAS=1SWIFT_HASH=66a3d6b56c1f479c8b4e70ab5c2000f5 SWIFT_DATA_DIR=$DEST/data enable_plugin sahara https://opendev.org/openstack/sahara enable_plugin sahara-dashboard https://opendev.org/openstack/sahara-dashboard enable_plugin heat https://opendev.org/openstack/heat Can you guys advise me about these errors. Is there anything to worry about?

1 0

[openstack-helm] No Meeting This Week
by Gage Hugo 25 Apr '22

25 Apr '22

Hey team, Since I will be busy during our normal meeting time this week and there's nothing on the agenda, the meeting for this week has been cancelled. We will meet again next week at the usual time. Thanks

1 0

[Xena][Cloudkitty] I have no rating in the dashboard
by wodel youchi 24 Apr '22

24 Apr '22

Hi, I've deployed Cloudkitty using Kolla-ansible, then I followed this example to test if the service is working : https://docs.openstack.org/cloudkitty/xena/user/rating/hashmap.html#examples I don't fully understand the service. I waited a day, and until now I don't have any results. The only errors I had is this once is : 2022-04-20 11:57:37.834 31 ERROR cloudkitty.orchestrator [-] [scope: a50e58ff494441b3b78ab096bca747d9, worker: 0 ] Error while collecting metric image.size at timestamp 2022-04-01 00:00:00+01:00: {'cause': "Metrics can't being aggregated", 'reason': 'Granularities are missing', 'detail': [['image.size', 'mean', 3600.0]]} (HTTP 400). Exiting.: gnocchiclient.exceptions.BadRequest: {'cause': "Metrics can't being aggregated", 'reason': 'Granularitie:are missing', 'detail': [['image.size', 'mean', 3600.0]]} (HTTP 400) 2022-04-20 11:57:37.834 31 ERROR cloudkitty.orchestrator Traceback (most recent call last): 2022-04-20 11:57:37.834 31 ERROR cloudkitty.orchestrator File "/var/lib/kolla/venv/lib/python3.6/site-packages/cloudkitty/orchestrator.py", line 308, in _get_result 2022-04-20 11:57:37.834 31 ERROR cloudkitty.orchestrator return self._collect(metric, timestamp) 2022-04-20 11:57:37.834 31 ERROR cloudkitty.orchestrator File "/var/lib/kolla/venv/lib/python3.6/site-packages/cloudkitty/orchestrator.py", line 297, in _collect 2022-04-20 11:57:37.834 31 ERROR cloudkitty.orchestrator self._tenant_id, 2022-04-20 11:57:37.834 31 ERROR cloudkitty.orchestrator File "/var/lib/kolla/venv/lib/python3.6/site-packages/cloudkitty/collector/__init__.py", line 240, in retrieve 2022-04-20 11:57:37.834 31 ERROR cloudkitty.orchestrator q_filter=q_filter, 2022-04-20 11:57:37.834 31 ERROR cloudkitty.orchestrator File "/var/lib/kolla/venv/lib/python3.6/site-packages/cloudkitty/collector/gnocchi.py", line 450, in fetch_all 2022-04-20 11:57:37.834 31 ERROR cloudkitty.orchestrator q_filter=q_filter, 2022-04-20 11:57:37.834 31 ERROR cloudkitty.orchestrator File "/var/lib/kolla/venv/lib/python3.6/site-packages/cloudkitty/collector/gnocchi.py", line 329, in _fetch_metric 2022-04-20 11:57:37.834 31 ERROR cloudkitty.orchestrator measurements = self._conn.aggregates.fetch(op, **agg_kwargs) 2022-04-20 11:57:37.834 31 ERROR cloudkitty.orchestrator File "/var/lib/kolla/venv/lib/python3.6/site-packages/gnocchiclient/v1/aggregates.py", line 72, in fetch 2022-04-20 11:57:37.834 31 ERROR cloudkitty.orchestrator data=ujson.dumps(data)).json() 2022-04-20 11:57:37.834 31 ERROR cloudkitty.orchestrator File "/var/lib/kolla/venv/lib/python3.6/site-packages/gnocchiclient/v1/base.py", line 41, in _post 2022-04-20 11:57:37.834 31 ERROR cloudkitty.orchestrator return self.client.api.post(*args, **kwargs) 2022-04-20 11:57:37.834 31 ERROR cloudkitty.orchestrator File "/var/lib/kolla/venv/lib/python3.6/site-packages/keystoneauth1/adapter.py", line 401, in post 2022-04-20 11:57:37.834 31 ERROR cloudkitty.orchestrator return self.request(url, 'POST', **kwargs) 2022-04-20 11:57:37.834 31 ERROR cloudkitty.orchestrator File "/var/lib/kolla/venv/lib/python3.6/site-packages/gnocchiclient/client.py", line 52, in request 2022-04-20 11:57:37.834 31 ERROR cloudkitty.orchestrator raise exceptions.from_response(resp, method) 2022-04-20 11:57:37.834 31 ERROR cloudkitty.orchestrator gnocchiclient.exceptions.BadRequest: {'cause': "Metrics can't being aggregated", 'reason': 'Granularities are missing', 'detail': [['image.size', 'mean', 3600.0]]} (HTTP 400) 2022-04-20 11:57:37.834 31 ERROR cloudkitty.orchestrator I searched the web and I found this post : https://storyboard.openstack.org/#!/story/2008598 Could that be the problem? If so , how to correct it? i tried to create this file on my kolla-ansible deployer vim /etc/kolla/config/cloudkitty.conf [DEFAULT] debug = True [collect] metrics_conf = /etc/*cloudkitty-api*/metrics.yml (I don't know if this path is correct, since there is no /etc/cloudkitty on the nodes) And I created a directory like this : mkdir /etc/kolla/config/cloudkitty/ wget https://raw.githubusercontent.com/openstack/cloudkitty/master/etc/cloudkitt… -O /etc/kolla/config/cloudkitty/metrics.yml I executed then kolla-ansible -i multinode reconfigure -t cloudkitty All I have in the logs is : 2022-04-21 15:13:32.691 8 INFO cotyledon._service_manager [-] Child 1304 exited with status 1 2022-04-21 15:13:32.693 8 INFO cotyledon._service_manager [-] Child 1310 exited with status 1 2022-04-21 15:13:32.695 8 INFO cotyledon._service_manager [-] Child 1312 exited with status 1 2022-04-21 15:13:32.697 8 INFO cotyledon._service_manager [-] Child 1314 exited with status 1 2022-04-21 15:13:33.097 8 INFO cotyledon._service_manager [-] Child 1325 exited with status 1 2022-04-21 15:13:33.101 8 INFO cotyledon._service_manager [-] Child 1327 exited with status 1 2022-04-21 15:13:33.102 8 INFO cotyledon._service_manager [-] Forking too fast, sleeping 2022-04-21 15:13:38.109 8 INFO cotyledon._service_manager [-] Child 1329 exited with status 1 2022-04-21 15:13:38.112 8 INFO cotyledon._service_manager [-] Child 1331 exited with status 1 2022-04-21 15:13:38.114 8 INFO cotyledon._service_manager [-] Child 1333 exited with status 1 Any ideas? Regards.

1 1

Re: Openstack Trove - Polling request timed out
by Hirotaka Wakabayashi 24 Apr '22

24 Apr '22

Hello Manish! "openstack database instance show" command shows you the current status of an instance. If the status is not ACTIVE, guest-agent fails to start the database service for some reasons. Please see the following page for further debug. https://docs.openstack.org/trove/latest/admin/troubleshooting.html FYI: I think the error occurs here in your case. https://opendev.org/openstack/trove/src/branch/master/trove/taskmanager/mod… Best Regards, Hirotaka On Saturday, April 23, 2022, 12:05:26 AM GMT+9, openstack-discuss-request(a)lists.openstack.org <openstack-discuss-request(a)lists.openstack.org> wrote: Send openstack-discuss mailing list submissions to openstack-discuss(a)lists.openstack.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss or, via email, send a message with subject or body 'help' to openstack-discuss-request(a)lists.openstack.org You can reach the person managing the list at openstack-discuss-owner(a)lists.openstack.org When replying, please edit your Subject line so it is more specific than "Re: Contents of openstack-discuss digest..." Today's Topics: 1. Openstack Trove - Polling request timed out (Manish Bharti) ---------------------------------------------------------------------- Message: 1 Date: Fri, 22 Apr 2022 17:00:31 +0530 From: Manish Bharti <manishbhartigt(a)gmail.com> To: openstack-discuss(a)lists.openstack.org Subject: Openstack Trove - Polling request timed out Message-ID: <CAFTsyOU7D3xf9c4tYb8KhnJQePjCBJvTK_ccHxAOntz_ia69Cg(a)mail.gmail.com> Content-Type: text/plain; charset="utf-8" Dear Team, We are trying to deploy OpenStack environment for our application and while deploying trove service we are facing the below error(attached screenshot)- Traceback (most recent call last): File "/usr/lib/python3/dist-packages/trove/common/utils.py", line 207, in wait_for_task return polling_task.wait() File "/usr/lib/python3/dist-packages/eventlet/event.py", line 125, in wait result = hub.switch() File "/usr/lib/python3/dist-packages/eventlet/hubs/hub.py", line 313, in switch return self.greenlet.switch() File "/usr/lib/python3/dist-packages/oslo_service/loopingcall.py", line 154, in _run_loop idle = idle_for_func(result, self._elapsed(watch)) File "/usr/lib/python3/dist-packages/oslo_service/loopingcall.py", line 349, in _idle_for raise LoopingCallTimeOut( oslo_service.loopingcall.LoopingCallTimeOut: Looping call timed out after 870.99 seconds During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/trove/taskmanager/models.py", line 434, in wait_for_instance utils.poll_until(self._service_is_active, File "/usr/lib/python3/dist-packages/trove/common/utils.py", line 223, in poll_until return wait_for_task(task) File "/usr/lib/python3/dist-packages/trove/common/utils.py", line 209, in wait_for_task raise exception.PollTimeOut trove.common.exception.PollTimeOut: Polling request timed out. Please help us on this issue. -- Thank you , Manish Bharti Jodhpur, Raj - 342001. Contact:8875033000

1 0