May 2023 - openstack-discuss - lists.openstack.org

[neutron] Bug Deputy Report May 8 - May 14
by Nurmatov Mamatisa 15 May '23

15 May '23

Hi, Below is the week summary of bug deputy report for last week. 2 bugs are not assigned. Details: Critical -------- - https://bugs.launchpad.net/neutron/+bug/2019097 - CI tests neutron-dynamic-routing broken - In progress: https://review.opendev.org/c/openstack/neutron-dynamic-routing/+/882815 - Assigned to Felix Huettner High ---- - https://bugs.launchpad.net/neutron/+bug/2018727 - [SRBAC] API policies for get_policy_*_rule are wrong - Fix released: https://review.opendev.org/c/openstack/neutron/+/882688 - Assigned to Slawek Kaplonski - https://bugs.launchpad.net/neutron/+bug/2019449 - Neutron server log file full of tracebacks in neutron-tempest-plugin-ovn job - Confirmed - Miguel Lavalle - https://bugs.launchpad.net/neutron/+bug/2019314 - On shutdown, linuxbridge agent queue on rabbitmq is not cleared - Confirmed - Unassigned Medium ------ - https://bugs.launchpad.net/neutron/+bug/2018967 - [fwaas] test_update_firewall_group fails randomly - Confirmed - Unassigned - https://bugs.launchpad.net/neutron/+bug/2018737 - neutron-dynamic-routing announces routes for disabled routers - In progress: https://review.opendev.org/c/openstack/neutron-dynamic-routing/+/882560 - Assigned to Felix Huettner - https://bugs.launchpad.net/neutron/+bug/2018989 - [SRBAC] FIP Port Forwarding policies should be available for PARENT_OWNER with proper role - Fix released: https://review.opendev.org/c/openstack/neutron/+/882691 - Assigned to Slawek Kaplonski - https://bugs.launchpad.net/neutron/+bug/2019119 - [sqlalchemy-20] Add the corresponding context to the upgrade checks methods - In progress: https://review.opendev.org/c/openstack/neutron/+/882865 - Assigned to Rodolfo Alonso - https://bugs.launchpad.net/neutron/+bug/2019132 - [OVN] ``OVNClient._add_router_ext_gw`` should use the context passed by the API call - In progress: https://review.opendev.org/c/openstack/neutron/+/882857 - Assigned to Rodolfo Alonso - https://bugs.launchpad.net/neutron/+bug/2019186 - [PostgreSQL] Issue with "get_scoped_floating_ips" query - In progress: https://review.opendev.org/c/openstack/neutron/+/882935 - Assigned to Rodolfo Alonso Low --- - https://bugs.launchpad.net/neutron/+bug/2019217 - [OVN] L3 port scheduler, defaults to use all chassis; stop this behavior - New - Assigned to Rodolfo Alonso Undecided --------- - https://bugs.launchpad.net/neutron/+bug/2019012 - When num of port mappings is substantial, the response time of List API so slow Best regards, Mamatisa Nurmatov Advanced Software Technology Lab / Cloud Technologies Research

1 0

(Openstack-glance) Image service Failing
by Adivya Singh 14 May '23

14 May '23

Hi Team, I have a scenario, where my glance nfs mount point are no longer require as the nfs external.server is down, i have remove all NFS variables from open stack user config file and user variable and delete the glance containet and try to bulid it again. But still it is trying to mount that path. Is therr any user variables to ignore this Regards Adivya Singh

1 1

Destroy an Openstack deployment and Keep Cinder Volumes
by A Monster 14 May '23

14 May '23

I have a deployment of openstack using kolla-ansible and LVM as a cinder backend, I want to make a kolla-ansible destroy to remove all openstack components and re deploy it again from scratch, however I want to keep the lvm volumes which is the backend for cinder, to re-use them for the fresh openstack deployment, and I was wondering if kolla-ansible destroys the lvm volumes used by cinder or no, and if you can suggest me a better alternative for what I'm trying to do. Thank you.

1 0

[kolla-ansible][yoga] fluentd problem with elasticsearch after update
by wodel youchi 13 May '23

13 May '23

Hi, I have finished the update of my openstack platform with newer containers. While verifying I noticed that fluentd container keeps restarting. In the log file I am having this : > 2023-05-03 16:07:59 +0100 [error]: #0 config error > file="/etc/td-agent/td-agent.conf" error_class=Fluent::ConfigError > error="Using Elasticsearch client 8.7.1 is not compatible for your > Elasticsearch server. Please check your using elasticsearch gem version and > Elasticsearch server." > 2023-05-03 16:07:59 +0100 [error]: Worker 0 finished unexpectedly with > status 2 > 2023-05-03 16:07:59 +0100 [info]: Received graceful stop > Those are the images I am using : (yogavenv) [deployer@rscdeployer ~]$ sudo docker images | grep -i elas 192.168.1.16:4000/openstack.kolla/centos-source-prometheus-elasticsearch-exporter yoga030523 b48f63ed0072 12 hours ago 539MB 192.168.1.16:4000/openstack.kolla/centos-source-elasticsearch yoga030523 3558611b0cf4 12 hours ago 1.2GB 192.168.1.16:4000/openstack.kolla/centos-source-elasticsearch-curator yoga030523 83a6b48339ea 12 hours ago 637MB (yogavenv) [deployer@rscdeployer ~]$ sudo docker images | grep -i fluen 192.168.1.16:4000/openstack.kolla/centos-source-fluentd yoga030523 bf6596e139e2 12 hours ago 847MB Any ideas? Regards. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free.www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

2 6

[neutron] Gate broken, please don't recheck
by Brian Haley 12 May '23

12 May '23

Hi, With the latest release of neutronclient version 10.0.0 the neutron gate pep8 job is now failing. Please hold your rechecks until a fix [0] merges. There's also some old unused devstack code that uses this neutron-debug code, will remove that in a follow-up. Thanks, -Brian [0] https://review.opendev.org/c/openstack/neutron/+/883081

1 0

[release] Release countdown for week R-20, May 15-19
by Elõd Illés 12 May '23

12 May '23

Development Focus ----------------- We are now past the Bobcat-1 milestone. Teams should now be focused on feature development. General Information ------------------- Our next milestone in this development cycle will be Bobcat-2, on July 6th, 2023. This milestone is when we freeze the list of deliverables that will be included in the 2023.2 Bobcat final release, so if you plan to introduce new deliverables in this release, please propose a change to add an empty deliverable file in the deliverables/bobcat directory of the openstack/releases repository. Now is also generally a good time to look at bugfixes that were introduced in the master branch that might make sense to be backported and released in a stable release. If you have any question around the OpenStack release process, feel free to ask on this mailing-list or on the #openstack-release channel on IRC. Upcoming Deadlines & Dates -------------------------- OpenInfra Summit & PTG in Vancouver: June 13-15, 2023 Bobcat-2 Milestone: July 6th, 2023 Előd Illés irc: elodilles @ #openstack-release

1 0

Ussuri - Volume delete status not updated in horizon dashboard
by Vineet Thakur 12 May '23

12 May '23

Hi Team, The issue is about quota update in the horizon dashboard where volume deletion status is not updated. For example: We deleted the volume, cinder logs showing the deletion status as success and even in the dashboard's "volume" section as well. But in the dashboard quota view, the entry for volume existence is still available, and this problem is only for one volume . (not for all volumes) We have tried almost all the possible ways suggested in online blogs to remove this volume id. But still that volume is persisting in the dashboard quota. Could you please guide us what is the best practice to remove this volume id from the quota without affecting the production environment. Appreciate your help. Thank you. Kind Regards, Vineet

1 0

Did StarlingX Break?
by John van Ommen 12 May '23

12 May '23

I've installed StarlingX 10+ times using the iso "bootimage.iso" from their website. I opted to do a reinstall yesterday, and it keeps hitting the same error at the same spot in the install. I've been able to replicate the error three times using two different HP servers. The installer basically reaches the point where it's installing package number 866 out of 1,217 packages, and fails with this error: process [/usr/libexec/anaconda/anaconda-yum --config /tmp/anaconda-yum.conf --tsfile /mnt/sysimage/anaconda-yum.yumtx --rpmlog /tmp/rpm-script.log --installroot /mnt/sysimage --release 7 --arch x86_64 --macro __dbi_htconfig hash nofsync /etc/selinux/targeted/contexts/files/file_contexts exited with status 1 I did a Google search on this error, and there's a slightly similar error reported on a RedHat forum from someone who had a bad ISO. But I know my ISO is working; it's the exact same ISO I've already installed from 10+ times. In the event that I have a bad DIMM or a bad NVME, I tried an identical server, and was able to reproduce the same error. In an earlier message on the list today, someone reported that missing repos may be impacting StarlingX, which definitely makes me wonder if I'm being impacted by that. I'm on the CentOS based version of StarlingX, version 7.0 I also tried to install from the Debian based version (8.0) and that one wouldn't even boot properly. It basically asks you what type of install you want to do, then crashes.

2 1

[kolla-ansible] TLS and internal VIP
by Nicolas Froger 12 May '23

12 May '23

Hello, I was debugging the monitoring stack of our deployment and I noticed that our Prometheus could not reach the OpenStack Exporter. The error is about a certificate name mismatch because Prometheus is scraping the exporter with the internal IP address instead of the internal FQDN while the certificate we have is only valid for the internal FQDN. Indeed, the Prometheus config specifies kolla_internal_vip_address as a target and uses HTTPS when kolla_enable_tls_internal is true. Replacing the target with kolla_internal_fqdn which is a DNS name for which the certificate is valid fixed my issue. My question is the following: should the internal certificate also be valid for the internal VIP when kolla_enable_tls_internal is set to true or is it okay if it's only valid for the FQDN? In the later case, does it make sense if I open an issue to use the FQDN instead of the IP address in the Prometheus config? Regards, -- Nicolas Froger

1 0

[neutron][ironic] Postgres support?
by Julia Kreger 11 May '23

11 May '23

Greetings folks, I have spent a substantial amount of time investigating CI issues as of recent, and I noticed that at some point the legacy "ironic-tempest-pxe_ipmitool-postgres" CI job which has been kept around as a non-voting postgres support canary, is now failing on the master branch. Specifically, looking through the logs[0], it appears that structurally the queries are no longer compatible. np0033933847 neutron-server[90677]: WARNING oslo_db.sqlalchemy.exc_filters [None req-155d0299-07ef-433a-8576-467127c82be4 None None] DBAPIError exception wrapped.: psycopg2.errors.GroupingError: column "subnetpools.address_scope_id" must appear in the GROUP BY clause or be used in an aggregate function May 03 18:41:57.893335 np0033933847 neutron-server[90677]: LINE 2: ...standard_attr_id AS floatingips_standard_attr_id, subnetpool... May 03 18:41:57.893335 np0033933847 neutron-server[90677]: ^ May 03 18:41:57.893335 np0033933847 neutron-server[90677]: ERROR oslo_db.sqlalchemy.exc_filters Traceback (most recent call last): May 03 18:41:57.893335 np0033933847 neutron-server[90677]: ERROR oslo_db.sqlalchemy.exc_filters File "/usr/local/lib/python3.8/dist-packages/sqlalchemy/engine/base.py", line 1900, in _execute_context May 03 18:41:57.893335 np0033933847 neutron-server[90677]: ERROR oslo_db.sqlalchemy.exc_filters self.dialect.do_execute( May 03 18:41:57.893335 np0033933847 neutron-server[90677]: ERROR oslo_db.sqlalchemy.exc_filters File "/usr/local/lib/python3.8/dist-packages/sqlalchemy/engine/default.py", line 736, in do_execute May 03 18:41:57.893335 np0033933847 neutron-server[90677]: ERROR oslo_db.sqlalchemy.exc_filters cursor.execute(statement, parameters) May 03 18:41:57.893335 np0033933847 neutron-server[90677]: ERROR oslo_db.sqlalchemy.exc_filters psycopg2.errors.GroupingError: column "subnetpools.address_scope_id" must appear in the GROUP BY clause or be used in an aggregate function May 03 18:41:57.893335 np0033933847 neutron-server[90677]: ERROR oslo_db.sqlalchemy.exc_filters LINE 2: ...standard_attr_id AS floatingips_standard_attr_id, subnetpool... May 03 18:41:57.893335 np0033933847 neutron-server[90677]: ERROR oslo_db.sqlalchemy.exc_filters ^ >From Ironic's point of view, we're wondering if this is expected? Is it likely to be fixed? If there are no plans to fix the DB queries, Ironic will have no choice but to drop the CI job. Thanks in advance! -Julia [0]: https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/…

5 6