February 2022 - openstack-discuss

SUBJECT: [ ironic][QA] Cycle With Intermediary Unreleased Deliverables
by Armstrong Foundjem 23 Feb '22

23 Feb '22

Quick reminder that we'll need a release very soon for a number of deliverables following a cycle-with-intermediary release model but which have not done *any* release yet in the Yoga cycle: ironic-prometheus-exporter ironic-python-agent-builder ironic-ui networking-baremetal networking-generic-switch patrole Those should be released ASAP, and in all cases before the March 10th deadline, so that we have a release to include in the final Yoga release. Best regards, Armstrong Foundjem irc: @armstrong

2 1

[cinder] Bug deputy report for week of 02-23-2022
by Sofia Enriquez 23 Feb '22

23 Feb '22

This is a bug report from 02-03-2022 to 02-23-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting The bug report is back! Today's meeting is on video. ----------------------------------------------------------------------------------------- Medium - https://bugs.launchpad.net/cinder/+bug/1960206 "[RBD] Amend the formula of retrieving total_capacity for a rbd pool." Fix proposed to master. Assigned to Gorka. - https://bugs.launchpad.net/os-brick/+bug/1961102 "NVMe-oF doesn't disconnect." Unassigned. Problem with request ID: - https://bugs.launchpad.net/cinder/+bug/1960329 "Wrong request ID on API middleware filters." Fix proposed to master. Assigned to Gorka. - https://bugs.launchpad.net/cinder/+bug/1960021 "Request to list REST API versions doesn't return the request id." Fix proposed to master. Assigned to Gorka. - https://bugs.launchpad.net/cinder/+bug/1960020 "Duplicated request ids in the logs." Fix proposed to master. Assigned to Gorka. - https://bugs.launchpad.net/cinder/+bug/1960019 "REST API responses have wrong request ID when using noauth." Fix proposed to master. Assigned to Gorka. Low - https://bugs.launchpad.net/cinder/+bug/1960315 "[IBM Storwize] Delete volume issue in reverse replication." Unassigned. - https://bugs.launchpad.net/cinder/+bug/1960314 "[IBM Storwize] Resize issue in reverse replication." Unassigned. - https://bugs.launchpad.net/cinder/+bug/1961548 "[Storwize] Fix multiple SVC CLI calls to create volume operation." Fix proposed to master. - https://bugs.launchpad.net/cinder/+bug/1959178 "SolidFire: Error message logged when creating volume from image." Fix proposed to master. Have a +2! Wishlist - https://bugs.launchpad.net/cinder/+bug/1960574 "Provide back-end Qos support for spdk driver." Unassigned. Incomplete - https://bugs.launchpad.net/cinder/+bug/1959350 " [RBD] Volume status becomes available after force delete." Unassigned. Invalid - https://bugs.launchpad.net/cinder/+bug/1961685 "cinder-volume.service crashes: no module named 'wrapt'." If I'm missing bugs please let me know! 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

[infra] Gerrit email outage?
by Stephen Finucane 23 Feb '22

23 Feb '22

I haven't received any emails from Gerrit since midday (UTC) yesterday. Chatting on IRC, it seems I'm not alone. Has something changed in Gerrit or is this a simple outage? Cheers, Stephen

2 2

[kolla][rabbitmq] Trouble with RMQ 3.8 in Train
by Albert Braden 23 Feb '22

23 Feb '22

We are running kolla-ansible Train and I successfully followed the recommendations in [1] to change our RMQ settings, and our RMQ works a lot better now, but one of the recommendations is to run RMQ 3.8 and so far I haven’t been able to make it work. Our working RMQ container has these settings in the Dockerfile to force 3.7 and the appropriate erlang version: 'erlang-21.3*', 'rabbitmq-server-3.7.23*' I changed those settings to allow 3.8: 'rabbitmq-server-3.*.*el8ost*' Now my RMQ container fails to start with: {"log":"20:29:28.440 [error] Supervisor rabbit_prelaunch_sup had child prelaunch started with rabbit_prelaunch:run_prelaunch_first_phase() at undefined exit with reason no_configuration_schema_found in context start_error\r\n","stream":"stdout","time":"2022-02-22T20:29:28.441064637Z"} What am I missing? [1] https://wiki.openstack.org/wiki/Large_Scale_Configuration_Rabbit

2 1

[qa] Zed PTG planning
by Martin Kopec 23 Feb '22

23 Feb '22

Hi everyone, virtual PTG for the Zed cycle will be held between 4th - 8th April [1]. I've created a Doodle [2] to collect the best time slots for our team. Please fill it in rather sooner than later (the deadline for team signup is March 11th). I've also created an etherpad [3] to collect ideas/topics for the PTG sessions. If you have anything to discuss, please don't hesitate to write it there. [1] http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027051… [2] https://doodle.com/poll/q5yzatzh45brt5v2 [3] https://etherpad.opendev.org/p/qa-zed-ptg Thanks, -- Martin Kopec Senior Software Quality Engineer Red Hat EMEA IM: kopecmartin

1 0

[neutron] Stale Tap Ports
by Ammad Syed 23 Feb '22

23 Feb '22

Hi, I am using neutron 19.1 and ovn 21.09. There is a strange behavior I am seeing on compute nodes that ovs logs shows below logs 2022-02-23T06:14:06.426Z|00226|bridge|WARN|could not open network device tapea0dca9a-32 (No such device) 2022-02-23T06:14:06.428Z|00227|bridge|WARN|could not open network device tapaeaa1749-b5 (No such device) 2022-02-23T06:14:06.429Z|00228|bridge|WARN|could not open network device tap53f06ea0-70 (No such device) 2022-02-23T06:14:06.431Z|00229|bridge|WARN|could not open network device tap724cf0cc-7b (No such device) 2022-02-23T06:14:06.433Z|00230|bridge|WARN|could not open network device tap18864125-6d (No such device) In the ovs-vsctl show I also see alot of ports with these status. Port tapaeaa1749-b5 Interface tapaeaa1749-b5 error: "could not open network device tapaeaa1749-b5 (No such device)" Port tap18864125-6d Interface tap18864125-6d error: "could not open network device tap18864125-6d (No such device)" Port tap54415fc0-dd Interface tap54415fc0-dd error: "could not open network device tap54415fc0-dd (No such device)" I have checked in neutron port list and there is no port found for these tap interfaces. openstack port list --long | grep -i 18864125-6d I have checked in database in ports table, there is also no ports there with these ids. mysql> select * from ports where id like '%18864125-6d%'; These ports even show on compute node even if there is no instance running on it. Are these stale ports ? If yes, is there any tool or utility to run audit and delete these ports ? Ammad

1 0

Re: [Tempest] OpenSack Powered * vs OpeStack Compatible
by yahoo yahho 23 Feb '22

23 Feb '22

Sent from Yahoo Mail on Android

1 0

[all] [requirements] Artificially inflated requirements in os-brick
by Thomas Goirand 22 Feb '22

22 Feb '22

Hi, I've been quite surprised to see $topic. Most requirements for os-brick are now to be found in Yoga only. I've asked why, and I've been told that the reason is because "we've been testing with the new versions only for the number of months". Well, the reason why someone would increase a minimum requirement *must* be only because of the need of a new feature, and should be treated with care. Otherwise, this makes upgrading very dangerous and annoying to do. As much as possible, I would strongly recommend that any dependency in Stable can be found in Stable-1 (only when a new feature is mandatory, then it's ok-ish to require that new version, though I would advocate for a possible fallback if that's not too complex to write). Now, if that's the path we're taking, all is going backward 5 years ago, and then my thinking is: we must reintroduce lower-constraints testing ASAP. Your thoughts everyone? Cheers, Thomas Goirand (zigo) P.S: Please note that this is absolutely not about os-brick, I'm not pointing my finger to any team, it's a global thinking for the whole OpenStack project.

5 10

LetsEncrypt OS Ansible Ussuri
by Marc-Antoine Godde 22 Feb '22

22 Feb '22

Hello, I have a question on how to setup LetsEncrypt with OpenStack Ansible. We are still on OpenStack Ussuri. We added the following variables to user_variables.yml. ================================================================================== haproxy_ssl_letsencrypt_enable: True haproxy_ssl_letsencrypt_install_method: "distro" haproxy_ssl_letsencrypt_setup_extra_params: "--http-01-address {{ ansible_host }} --http-01-port 8888" haproxy_ssl_letsencrypt_email: email(a)example.com haproxy_interval: 2000 user avatar user avatar haproxy_extra_services: # an internal only service for acme-challenge whose backend is certbot on the haproxy host - service: haproxy_service_name: letsencrypt haproxy_backend_nodes: - name: localhost ip_addr: {{ ansible_host }} #certbot binds to the internal IP backend_rise: 1 #quick rise and fall time for multinode deployment to succeed backend_fall: 2 haproxy_bind: - 127.0.0.1 #bind to 127.0.0.1 as the local internal address will be used by certbot haproxy_port: 8888 #certbot is configured with http-01-port to be 8888 haproxy_balance_type: http ================================================================================== Yet, Horizon config for HAproxy is already defined in the default vars (https://github.com/openstack/openstack-ansible/blob/stable/ussuri/inventory… <https://github.com/openstack/openstack-ansible/blob/stable/ussuri/inventory…>) and we don’t know where ta add the required ACL to redirect the traffic from 80 port to 8888: ==================================== haproxy_frontend_acls: #use a frontend ACL specify the backend to use for acme-challenge letsencrypt-acl: rule: "path_beg /.well-known/acme-challenge/" backend_name: letsencrypt ==================================== We know that this is fixed in OpenStack Ansible Victoria. Is it possible with Ussuri tho ? Many thanks, Best, Marc-Antoine Godde

2 5

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

22 Feb '22

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

1 0