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

[Kolla] how to build kolla containers with kolla-build for specific branch
by wodel youchi 16 May '23

16 May '23

Hi, Could you help me understand the process of building kolla containers from source? I am not a developer but I want to be to build containers rapidly especially when there is an urgent patch. I am using Yoga branch which is the 14th version, do I need to use the same version of kolla-build to build containers or it matters not? Regards.

3 5

[neutron] CI meeting cancelled this week
by Slawek Kaplonski 16 May '23

16 May '23

Hi, I can't attend and chair today's Neutron CI meeting so we decided that we will cancel it if there will be no anything urgent. I think that CI in overall is running fine this week. Here's short summary of what I found: * Stadium projects - it seems that many projects may be affected by [1] - @Lajos, are You aware of those? * Grafana - it looks good this week * Rechecks - all good this week * Periodic jobs - looks good, only neutron-functional-with-sqlalchemy-master is still failing See You on the neutron team meeting today and on CI meeting next week. [1] https://review.opendev.org/c/openstack/neutron/+/879827 -- Slawek Kaplonski Principal Software Engineer Red Hat

2 1

[tc] Technical Committee next weekly meeting on May 16, 2023
by Nikolla, Kristi 16 May '23

16 May '23

Hi all, This is a reminder that the next weekly Technical Committee meeting is to be held on Tuesday, May 16, 2023 at 1800 UTC on #openstack-tc on OFTC IRC. I’m out of office this week, therefore this week’s meeting will be chaired by Jay Faulkner. Thank you Jay! The meeting’s agenda can be found on the wiki page at https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting Thank you, Kristi Nikolla

1 0

[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 15 May '23

15 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 14 May '23

14 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

[ironic] Meeting cancelled; Metal3 PTG next Monday
by Jay Faulkner 11 May '23

11 May '23

Hi all, The Metal3 team informed us they are having a one day PTG, which will take place on May 15th, 2023 from 14:00 to 17:00 UTC. I strongly encourage any interested Ironic cores to review the invitation[1] and attend if interested. Because this overlaps our regularly scheduled Ironic meeting, and there is significant overlap between the Metal3 and Ironic communities, the Ironic meeting for Monday, May 15h is cancelled to allow our communities to collaborate without distraction. Thanks, Jay Faulkner Ironic PTL 1: https://groups.google.com/g/metal3-dev/c/62PCloXk-zQ

1 0

[kolla] [train] [neutron]
by Albert Braden 11 May '23

11 May '23

1 0

Extending the Forum
by Kendall Nelson 11 May '23

11 May '23

Hello Everyone, We received feedback that critical Forum conversations were not able to make the schedule due to the intentional work on our part to avoid PTG / Forum overlap which ended up restricting the number of Forum discussion proposals we were able to accept. To mitigate this, we have opened up the Forum room for a third day. We have created a form to collect critical Forum proposals. We will leave the form open for one week to give all timezones fair representation. The deadline to submit a proposal for a forum discussion is Thursday May, 18th at 7:00 UTC. Shortly after, the OpenInfra Foundation will make final decisions and program the Forum on Thursday. -Kendall Nelson [1] https://openinfrafoundation.formstack.com/forms/forum_expansion

1 0

[publiccloud-sig] Bi-weekly meeting times adjusted to 0700 UTC
by Felix Kronlage-Dammers 11 May '23

11 May '23

Hi, since some of us (to be honest, probably mostly me ;) have a conflicting meeting during summer time with the slot of the publiccloud-sig we discussed moving it to 0700 UTC during summer time. Since nobody in the past two meetings spoke against that, this was concluded yesterday. During summer time the publiccloud SIG will meet at 0700 UTC, not at 0800 UTC. The change is also reflected in the wiki page: https://wiki.openstack.org/wiki/PublicCloudSIG See you next time (and I'll set myself reminder to send out the reminder ;) felix -- GPG: 824CE0F0 / 2082 651E 5104 F989 4D18 BB2E 0B26 6738 824C E0F0 https://hazardous.org/ - fkr(a)hazardous.org - fkr@irc - @felixkronlage

1 0

[OSSA-2023-003] cinder, glance_store, nova, os-brick: Unauthorized volume access through deleted volume attachments (CVE-2023-2088)
by Jeremy Stanley 10 May '23

10 May '23

============================================================================ OSSA-2023-003: Unauthorized volume access through deleted volume attachments ============================================================================ :Date: May 10, 2023 :CVE: CVE-2023-2088 Affects ~~~~~~~ - Cinder: <20.2.1, >=21.0.0 <21.2.1, ==22.0.0 - Glance_store: <3.0.1, >=4.0.0 <4.1.1, >=4.2.0 <4.3.1 - Nova: <25.1.2, >=26.0.0 <26.1.2, ==27.0.0 - Os-brick: <5.2.3, >=6.0.0 <6.1.1, >=6.2.0 <6.2.2 Description ~~~~~~~~~~~ An unauthorized access to a volume could occur when an iSCSI or FC connection from a host is severed due to a volume being unmapped on the storage system and the device is later reused for another volume on the same host. **Scope:** Only deployments with iSCSI or FC volumes are affected. However, the fix for this issue includes a configuration change in Nova and Cinder that may impact you on your next upgrade regardless of what backend storage technology you use. See the *Configuration change* section below, and item 4(B) in the *Patches and Associated Deployment Changes* for details. This data leak can be triggered by two different situations. **Accidental case:** If there is a problem with network connectivity during a normal detach operation, OpenStack may fail to clean the situation up properly. Instead of force-detaching the compute node device, Nova ignores the error, assuming the instance has already been deleted. Due to this incomplete operation OpenStack may end up selecting the wrong multipath device when connecting another volume to an instance. **Intentional case:** A regular user can create an instance with a volume, and then delete the volume attachment directly in Cinder, which neglects to notify Nova. The compute node SCSI plumbing (over iSCSI/FC) will continue trying to connect to the original host/port/LUN, not knowing the attachment has been deleted. If a subsequent volume attachment re-uses the host/port/LUN for a different instance and volume, the original instance will gain access to it once the SCSI plumbing reconnects. Configuration Change -------------------- To prevent the intentional case, the Block Storage API provided by Cinder must only accept attachment delete requests from Nova for instance-attached volumes. A complicating factor is that Nova deletes an attachment by making a call to the Block Storage API on behalf of the user (that is, by passing the user's token), which makes the request indistinguishable from the user making this request directly. The solution is to have Nova include a service token along with the user's token so that Cinder can determine that the detach request is coming from Nova. The ability for Nova to pass a service token has been supported since Ocata, but has not been required until now. Thus, deployments that are not currently sending service user credentials from Nova will need to apply the relevant code changes and also make configuration changes to solve the problem. Patches and Associated Deployment Changes ----------------------------------------- Given the above analysis, a thorough fix must include the following elements: 1. The os-brick library must implement the ``force`` option for fibre channel, which which has only been available for iSCSI until now (covered by the linked patches). 2. Nova must call os-brick with the ``force`` option when disconnecting volumes from deleted instances (covered by the linked patches). 3. In deployments where Glance uses the cinder glance_store driver, glance must call os-brick with the ``force`` option when disconnecting volumes (covered by the linked patches). 4. Cinder must distinguish between safe and unsafe attachment delete requests and reject the unsafe ones. This part of the fix has two components: a. The Block Storage API will return a 409 (Conflict) for a request to delete an attachment if there is an instance currently using the attachment, **unless** the request is being made by a service (for example, Nova) on behalf of a user (covered by the linked patches). b. In order to recognize that a request is being made by a service on behalf of a user, Nova must be configured to send a service token along with the user token. If this configuration change is not made, the cinder change will reject **any** request to delete an attachment associated with a volume that is attached to an instance. Nova must be configured to send a service token to Cinder, and Cinder must be configured to accept service tokens. This is described in the following document and **IS NOT AUTOMATICALLY APPLIED BY THE LINKED PATCHES:** (Using service tokens to prevent long-running job failures) https://docs.openstack.org/cinder/latest/configuration/block-storage/servic… The Nova patch mentioned in step 2 includes a similar document more focused on Nova: doc/source/admin/configuration/service-user-token.rst 5. The cinder glance_store driver does not attach volumes to instances; instead, it attaches volumes directly to the Glance node. Thus, the Cinder change in step 4 will recognize an attachment-delete request coming from Glance as safe and allow it. (Of course, we expect that you will have applied the patches in steps 1 and 3 to your Glance nodes.) Errata ~~~~~~ An additional nova patch is required to fix a minor regression in periodic tasks and some nova-manage actions (errata 1). Also a patch to tempest is needed to account for behavior changes with fixes in place (errata 2). Patches ~~~~~~~ - https://review.opendev.org/882836 (2023.1/antelope cinder) - https://review.opendev.org/882851 (2023.1/antelope glance_store) - https://review.opendev.org/882858 (2023.1/antelope nova) - https://review.opendev.org/882859 (2023.1/antelope nova errata 1) - https://review.opendev.org/882843 (2023.1/antelope os-brick) - https://review.opendev.org/882835 (2023.2/bobcat cinder) - https://review.opendev.org/882834 (2023.2/bobcat glance_store) - https://review.opendev.org/882847 (2023.2/bobcat nova) - https://review.opendev.org/882852 (2023.2/bobcat nova errata 1) - https://review.opendev.org/882840 (2023.2/bobcat os-brick) - https://review.opendev.org/882876 (2023.2/bobcat tempest errata 2) - https://review.opendev.org/882869 (Wallaby nova) - https://review.opendev.org/882870 (Wallaby nova errata 1) - https://review.opendev.org/882839 (Xena cinder) - https://review.opendev.org/882855 (Xena glance_store) - https://review.opendev.org/882867 (Xena nova) - https://review.opendev.org/882868 (Xena nova errata 1) - https://review.opendev.org/882848 (Xena os-brick) - https://review.opendev.org/882838 (Yoga cinder) - https://review.opendev.org/882854 (Yoga glance_store) - https://review.opendev.org/882863 (Yoga nova) - https://review.opendev.org/882864 (Yoga nova errata 1) - https://review.opendev.org/882846 (Yoga os-brick) - https://review.opendev.org/882837 (Zed cinder) - https://review.opendev.org/882853 (Zed glance_store) - https://review.opendev.org/882860 (Zed nova) - https://review.opendev.org/882861 (Zed nova errata 1) - https://review.opendev.org/882844 (Zed os-brick) Credits ~~~~~~~ - Jan Wasilewski from Atman (CVE-2023-2088) - Gorka Eguileor from Red Hat (CVE-2023-2088) References ~~~~~~~~~~ - https://launchpad.net/bugs/2004555 - http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-2088 Notes ~~~~~ - Limited Protection Against Accidents... If you are only concerned with protecting against the accidental case described earlier in this document, steps 1-3 above should be sufficient. Note, however, that only applying steps 1-3 leaves your cloud wide open to the intentional exploitation of this vulnerability. Therefore, we recommend that the full fix be applied to all deployments. - Using Configuration as a Short-Term Mitigation... An alternative approach to mitigation can be found in OSSN-0092 https://wiki.openstack.org/wiki/OSSN/OSSN-0092 - The stable/xena and stable/wallaby branches are under extended maintenance and will receive no new point releases, but patches for them are provided as a courtesy where available. OSSA History ~~~~~~~~~~~~ - 2023-05-10 - Errata 2 - 2023-05-10 - Errata 1 - 2023-05-10 - Original Version -- Jeremy Stanley OpenStack Vulnerability Management Team

1 0

Cinder Bug Report 2023-05-10
by Sofia Enriquez 10 May '23

10 May '23

Hello Argonauts, Cinder Bug Meeting Etherpad <https://etherpad.opendev.org/p/cinder-bug-squad-meeting> *Medium* - [rbac] Volume type's extra_specs dict is empty. <https://bugs.launchpad.net/cinder/+bug/2018467> - *Status:* Unassigned. - cinder services report_state hangs for a longer period than report_interval when losing database connection. <https://bugs.launchpad.net/cinder/+bug/2018595> - *Status:* Unassigned. *Low* - HPE 3par - Unable to use small QoS Latency value (less than 1) <https://bugs.launchpad.net/cinder/+bug/2018994> - *Status:* Fix proposed to master <https://review.opendev.org/c/openstack/cinder/+/882266>. 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

[cinder] create a multiattach volume in two ways?
by Tony Liu 10 May '23

10 May '23

Hi, [1] says "Currently you can create a multiattach volume in two ways." I see one way is with volume type. What's the another way? [1] https://docs.openstack.org/cinder/xena/admin/blockstorage-volume-multiattac… Thanks! Tony

2 3

[heat][magnum][tacker] Future of SoftwareDeployment support
by Takashi Kajinami 10 May '23

10 May '23

Hello, We discussed this briefly in the past thread where we discussed maintenance of os-*-agent repos, and also talked about this topic during Heat PTG, but I'd like to formalize the discussion to get a clear agreement. Heat has been supporting SoftwareDeployment resources to configure software in instances using some agents such as os-collect-config[1]. [1] https://docs.openstack.org/heat/latest/template_guide/software_deployment.h… This feature was initially developed to be used by TripleO (IIUC), but TripleO is retired now and we are losing the first motivation to maintain the feature. # Even TripleO replaced most of its usage of softwaredeployment by config-download lately. Because the heat project team has drunk dramatically recently, we'd like to put more focus on core features. For that aim we are now wondering if we can deprecate and remove this feature, and would like to hear from anyone who has any concerns about this. Quickly looking through the repos, it seems currently Magnum and Tacker are using SoftwareDeployment, and it'd be nice especially if we can understand their current requirements. 1. Magnum It seems SoftwareDeployment is used by k8s_fedora_atomic_v1 driver but I'm not too sure whether this driver is still supported, because Fedora Atomic was EOLed a while ago, right ? 2. Tacker SoftwareDeployment can be found in only test code in the tacker repo. We have some references kept in heat-translator which look related to TOSCA templates. Thank you, Takashi Kajinami

4 8

Unable to provision HCI node | Wallaby
by Swogat Pradhan 09 May '23

09 May '23

Hi, When i am running node provision command i am getting the following error: The full traceback is: File "/tmp/ansible_metalsmith_instances_payload_tmufs89r/ansible_metalsmith_instances_payload.zip/ansible/modules/metalsmith_instances.py", line 427, in main File "/tmp/ansible_metalsmith_instances_payload_tmufs89r/ansible_metalsmith_instances_payload.zip/ansible/modules/metalsmith_instances.py", line 340, in provision File "/usr/lib64/python3.6/concurrent/futures/thread.py", line 56, in run result = self.fn(*self.args, **self.kwargs) File "/tmp/ansible_metalsmith_instances_payload_tmufs89r/ansible_metalsmith_instances_payload.zip/ansible/modules/metalsmith_instances.py", line 372, in _provision_instance File "/usr/lib/python3.6/site-packages/metalsmith/_provisioner.py", line 488, in wait_for_provisioning raise exceptions.DeploymentFailed(str(exc)) "networks": [ { "network": "ctlplane", "vif": true }, { "network": "internal_api", "subnet": "internal_apis2_subnet" }, { "network": "tenant", "subnet": "tenants2_subnet" }, { "network": "storage", "subnet": "storages2_subnet" }, { "network": "storage_mgmt", "subnet": "storage_mgmts2_subnet" } ], "nics": [ { "network": "ctlplane" } ], "ssh_public_keys": "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQCb/KTQTouURPWFO0R1zGEIKXYUDQb4+pIgNuTJ7zA43jz9nyGt/pH1pnZAq71NmfL+sICFPf4uvhqFkMU7T0eC3TVuP87kZ8pAMh0D+NPqtRQJxK0WZO2h67dUKBAtW5WamxABhDh+XqmRPXE8Fl1VvzlKO/KZGUClk24BNGjt/nqho9FGskNY/vZLQV/gZzrKfHUYpcDxIg6NpnNE6bGdy4tyL4JwYcdTP8ovU1JhKMXSTjk8WrGz/OQB8a4Pgq0WWgIRWvwZDuUwFWiK6aV7gkjhMXwwtZ7jq9fQOs/hcleATX7Cq77ayJW8DusxQLynbMrh/dBs3Smgp1Ncd3rthpJz2ujBg7ymScCq4ya0W1RkbzZ6H8kVT0hppO93Ip8VFTMnPDoWONQFdAbAVhaamycVMxxbGatHVYGGXIMMBEL1MO4ncIW4f46vNffIhmoTvG20ncy2zba7hk9D4NMbqEpyR3NG1BnMHW0h9bYp2K9+jOWS9MUfakD8kNi8Ff0= stack(a)hkg2director.bdxworld.com ", 2023-05-09 22:18:08.565576 | 48d539a1-1679-0477-63a8-000000000018 | FATAL | Provision instances | localhost | error={ "changed": false, "invocation": { "module_args": { "api_timeout": null, "auth": null, "auth_type": null, "availability_zone": null, "ca_cert": null, "clean_up": false, "client_cert": null, "client_key": null, "concurrency": 1, "instances": [ { "config_drive": { "meta_data": { "instance-type": "DistributedComputeHCI" } }, "hostname": "dcn01-hci-2", "image": { "href": "file:///var/lib/ironic/images/overcloud-full.raw", "kernel": "file:///var/lib/ironic/images/overcloud-full.vmlinuz", "ramdisk": "file:///var/lib/ironic/images/overcloud-full.initrd" }, "name": "17107583-48da-43eb-9e38-63e250848d05", "network_config": { "template": "/home/stack/dcn01/hci_network_bond.j2" }, "networks": [ { "network": "ctlplane", "vif": true }, { "network": "internal_api", "subnet": "internal_apis2_subnet" }, { "network": "tenant", "subnet": "tenants2_subnet" }, { "network": "storage", "subnet": "storages2_subnet" }, { "network": "storage_mgmt", "subnet": "storage_mgmts2_subnet" } ], "nics": [ { "network": "ctlplane" } ], "ssh_public_keys": "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQCb/KTQTouURPWFO0R1zGEIKXYUDQb4+pIgNuTJ7zA43jz9nyGt/pH1pnZAq71NmfL+sICFPf4uvhqFkMU7T0eC3TVuP87kZ8pAMh0D+NPqtRQJxK0WZO2h67dUKBAtW5WamxABhDh+XqmRPXE8Fl1VvzlKO/KZGUClk24BNGjt/nqho9FGskNY/vZLQV/gZzrKfHUYpcDxIg6NpnNE6bGdy4tyL4JwYcdTP8ovU1JhKMXSTjk8WrGz/OQB8a4Pgq0WWgIRWvwZDuUwFWiK6aV7gkjhMXwwtZ7jq9fQOs/hcleATX7Cq77ayJW8DusxQLynbMrh/dBs3Smgp1Ncd3rthpJz2ujBg7ymScCq4ya0W1RkbzZ6H8kVT0hppO93Ip8VFTMnPDoWONQFdAbAVhaamycVMxxbGatHVYGGXIMMBEL1MO4ncIW4f46vNffIhmoTvG20ncy2zba7hk9D4NMbqEpyR3NG1BnMHW0h9bYp2K9+jOWS9MUfakD8kNi8Ff0= stack(a)hkg2director.bdxworld.com ", "user_name": "heat-admin" } ], "interface": "public", "log_level": "info", "region_name": null, "state": "present", "timeout": 3600, "validate_certs": null, "wait": true } }, "logging": "Created port dcn01-hci-2-ctlplane (UUID ce763b38-b047-40bc-be44-9c9da8bd2e30) for node singapore-HCI3 (UUID 17107583-48da-43eb-9e38-63e250848d05) with {'network_id': '1fad76a3-aa2a-4213-8c37-eb89629da523', 'name': 'dcn01-hci-2-ctlplane'}\nAttached port dcn01-hci-2-ctlplane (UUID ce763b38-b047-40bc-be44-9c9da8bd2e30) to node singapore-HCI3 (UUID 17107583-48da-43eb-9e38-63e250848d05)\nProvisioning started on node singapore-HCI3 (UUID 17107583-48da-43eb-9e38-63e250848d05)\n", "msg": "Node 17107583-48da-43eb-9e38-63e250848d05 reached failure state \"deploy failed\"; the last error is Deploy step deploy.prepare_instance_boot failed: Failed to install a bootloader when deploying node 17107583-48da-43eb-9e38-63e250848d05. Error: Installing GRUB2 boot loader to device /dev/sda failed with Unexpected error while running command.\nCommand: chroot /tmp/tmp8_wa6g6q /bin/sh -c \"grub2-install /dev/sda\"\nExit code: 1\nStdout: ''\nStderr: 'grub2-install: error: this utility cannot be used for EFI platforms because it does not support UEFI Secure Boot.\\n'." I have already provisioned 2 other nodes using the same hardware, but the node provisioning is failing in this particular node. With regards, Swogat Pradhan

2 1

[neutron] When num of port mappings is substantial, the response time of List API so slow
by 韩光宇 09 May '23

09 May '23

Hello， I have a Victoria cluster with 1 controller node(also have nova-compute service) and two compute node. ALL node boasts 128 CPU cores and 512GB of memory. I established 1500 port mappings for a single floating IP A. At this point, the response time for the "List Floating IP Port Forwardings" API[1] becomes remarkably slow, approaching a duration of 9 minutes. Does anyone comprehend the cause of this phenomenon or how should I investigate it? I am immensely grateful for any assistance provided. Best regards, Han Guangyu [1] https://docs.openstack.org/api-ref/network/v2/index.html#list-floating-ip-p…

2 2

[Octavia] importlib fails to read first 5 chars from file
by Mihai Gheorghe 09 May '23

09 May '23

Hello, We are experiencing a strange problem with Octavia API in an Openstack deployment. A bit of context: we have an Openstack Ussuri deployment (HA) on Ubuntu Focal. Most Openstack services are running on LXD containers on 3 baremetals. There are also two OVN-dedicated-chassis which act as gateways and nova-compute nodes. A couple of days ago we updated all the packages in the environment to the latest versions (baremetals and lxc containers). After the updates, we started seeing problems with the Octavia API. The API would randomly give an internal server error. Octavia API is running under Apache2 WSGI on 3 LXD containers on 3 separate nodes. Looking into one of the Octavia container under /var/log/apache2/octavia_error.log, we found the following error: [Fri Apr 28 10:11:07.509268 2023] [wsgi:error] [pid 1312420:tid 140012169602816] [remote 127.0.0.1:59914] mod_wsgi (pid=1312420): Failed to exec Python script file '/usr/bin/octavia-wsgi'. [Fri Apr 28 10:11:07.509455 2023] [wsgi:error] [pid 1312420:tid 140012169602816] [remote 127.0.0.1:59914] mod_wsgi (pid=1312420): Exception occurred processing WSGI script '/usr/bin/octavia-wsgi'. [Fri Apr 28 10:11:07.511688 2023] [wsgi:error] [pid 1312420:tid 140012169602816] [remote 127.0.0.1:59914] Traceback (most recent call last): [Fri Apr 28 10:11:07.511884 2023] [wsgi:error] [pid 1312420:tid 140012169602816] [remote 127.0.0.1:59914] File "/usr/bin/octavia-wsgi", line 52, in <module> [Fri Apr 28 10:11:07.512260 2023] [wsgi:error] [pid 1312420:tid 140012169602816] [remote 127.0.0.1:59914] application = setup_app() [Fri Apr 28 10:11:07.512343 2023] [wsgi:error] [pid 1312420:tid 140012169602816] [remote 127.0.0.1:59914] File "/usr/lib/python3/dist-packages/octavia/api/app.py", line 59, in setup_app [Fri Apr 28 10:11:07.512435 2023] [wsgi:error] [pid 1312420:tid 140012169602816] [remote 127.0.0.1:59914] pecan_config = get_pecan_config() [Fri Apr 28 10:11:07.512513 2023] [wsgi:error] [pid 1312420:tid 140012169602816] [remote 127.0.0.1:59914] File "/usr/lib/python3/dist-packages/octavia/api/app.py", line 40, in get_pecan_config [Fri Apr 28 10:11:07.512529 2023] [wsgi:error] [pid 1312420:tid 140012169602816] [remote 127.0.0.1:59914] return pecan_configuration.conf_from_file(filename) [Fri Apr 28 10:11:07.512543 2023] [wsgi:error] [pid 1312420:tid 140012169602816] [remote 127.0.0.1:59914] File "/usr/lib/python3/dist-packages/pecan/configuration.py", line 176, in conf_from_file [Fri Apr 28 10:11:07.512553 2023] [wsgi:error] [pid 1312420:tid 140012169602816] [remote 127.0.0.1:59914] SourceFileLoader(module_name, abspath).load_module(module_name) [Fri Apr 28 10:11:07.512567 2023] [wsgi:error] [pid 1312420:tid 140012169602816] [remote 127.0.0.1:59914] File "<frozen importlib._bootstrap_external>", line 522, in _check_name_wrapper [Fri Apr 28 10:11:07.512705 2023] [wsgi:error] [pid 1312420:tid 140012169602816] [remote 127.0.0.1:59914] File "<frozen importlib._bootstrap_external>", line 1027, in load_module [Fri Apr 28 10:11:07.512725 2023] [wsgi:error] [pid 1312420:tid 140012169602816] [remote 127.0.0.1:59914] File "<frozen importlib._bootstrap_external>", line 852, in load_module [Fri Apr 28 10:11:07.512737 2023] [wsgi:error] [pid 1312420:tid 140012169602816] [remote 127.0.0.1:59914] File "<frozen importlib._bootstrap>", line 265, in _load_module_shim [Fri Apr 28 10:11:07.512750 2023] [wsgi:error] [pid 1312420:tid 140012169602816] [remote 127.0.0.1:59914] File "<frozen importlib._bootstrap>", line 702, in _load [Fri Apr 28 10:11:07.512763 2023] [wsgi:error] [pid 1312420:tid 140012169602816] [remote 127.0.0.1:59914] File "<frozen importlib._bootstrap>", line 671, in _load_unlocked [Fri Apr 28 10:11:07.512775 2023] [wsgi:error] [pid 1312420:tid 140012169602816] [remote 127.0.0.1:59914] File "<frozen importlib._bootstrap_external>", line 844, in exec_module [Fri Apr 28 10:11:07.512788 2023] [wsgi:error] [pid 1312420:tid 140012169602816] [remote 127.0.0.1:59914] File "<frozen importlib._bootstrap_external>", line 981, in get_code [Fri Apr 28 10:11:07.512800 2023] [wsgi:error] [pid 1312420:tid 140012169602816] [remote 127.0.0.1:59914] File "<frozen importlib._bootstrap_external>", line 911, in source_to_code [Fri Apr 28 10:11:07.512839 2023] [wsgi:error] [pid 1312420:tid 140012169602816] [remote 127.0.0.1:59914] File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed [Fri Apr 28 10:11:07.512869 2023] [wsgi:error] [pid 1312420:tid 140012169602816] [remote 127.0.0.1:59914] File "/usr/lib/python3/dist-packages/octavia/api/config.py", line 1 [Fri Apr 28 10:11:07.512893 2023] [wsgi:error] [pid 1312420:tid 140012169602816] [remote 127.0.0.1:59914] Copyright 2014 Rackspace [Fri Apr 28 10:11:07.512921 2023] [wsgi:error] [pid 1312420:tid 140012169602816] [remote 127.0.0.1:59914] ^ [Fri Apr 28 10:11:07.512938 2023] [wsgi:error] [pid 1312420:tid 140012169602816] [remote 127.0.0.1:59914] IndentationError: unexpected indent The original /usr/lib/python3/dist-packages/octavia/api/config.py file is added to the bug report. As seen in the file, the first line starts with a comment, but python is trying to run it as code. Removing the first 5 charactersin the file so that string above starts right after the comment yelds the following traceback: [Wed Apr 26 17:08:22.609980 2023] [wsgi:error] [pid 330647:tid 140629468657408] [remote 127.0.0.1:55142] mod_wsgi (pid=330647): Failed to exec Python script file '/usr/bin/octavia-wsgi'. [Wed Apr 26 17:08:22.610114 2023] [wsgi:error] [pid 330647:tid 140629468657408] [remote 127.0.0.1:55142] mod_wsgi (pid=330647): Exception occurred processing WSGI script '/usr/bin/octavia-wsgi'. [Wed Apr 26 17:08:22.611039 2023] [wsgi:error] [pid 330647:tid 140629468657408] [remote 127.0.0.1:55142] Traceback (most recent call last): [Wed Apr 26 17:08:22.611097 2023] [wsgi:error] [pid 330647:tid 140629468657408] [remote 127.0.0.1:55142] File "/usr/bin/octavia-wsgi", line 52, in <module> [Wed Apr 26 17:08:22.611106 2023] [wsgi:error] [pid 330647:tid 140629468657408] [remote 127.0.0.1:55142] application = setup_app() [Wed Apr 26 17:08:22.611125 2023] [wsgi:error] [pid 330647:tid 140629468657408] [remote 127.0.0.1:55142] File "/usr/lib/python3/dist-packages/octavia/api/app.py", line 59, in setup_app [Wed Apr 26 17:08:22.611135 2023] [wsgi:error] [pid 330647:tid 140629468657408] [remote 127.0.0.1:55142] pecan_config = get_pecan_config() [Wed Apr 26 17:08:22.611152 2023] [wsgi:error] [pid 330647:tid 140629468657408] [remote 127.0.0.1:55142] File "/usr/lib/python3/dist-packages/octavia/api/app.py", line 40, in get_pecan_config [Wed Apr 26 17:08:22.611160 2023] [wsgi:error] [pid 330647:tid 140629468657408] [remote 127.0.0.1:55142] return pecan_configuration.conf_from_file(filename) [Wed Apr 26 17:08:22.611178 2023] [wsgi:error] [pid 330647:tid 140629468657408] [remote 127.0.0.1:55142] File "/usr/lib/python3/dist-packages/pecan/configuration.py", line 168, in conf_from_file [Wed Apr 26 17:08:22.611327 2023] [wsgi:error] [pid 330647:tid 140629468657408] [remote 127.0.0.1:55142] compiled = compile(f.read(), abspath, 'exec') [Wed Apr 26 17:08:22.611355 2023] [wsgi:error] [pid 330647:tid 140629468657408] [remote 127.0.0.1:55142] File "/usr/lib/python3/dist-packages/octavia/api/config.py", line 1 [Wed Apr 26 17:08:22.611381 2023] [wsgi:error] [pid 330647:tid 140629468657408] [remote 127.0.0.1:55142] right 2014 Rackspace [Wed Apr 26 17:08:22.611419 2023] [wsgi:error] [pid 330647:tid 140629468657408] [remote 127.0.0.1:55142] ^ [Wed Apr 26 17:08:22.611437 2023] [wsgi:error] [pid 330647:tid 140629468657408] [remote 127.0.0.1:55142] SyntaxError: invalid syntax It seems that when the source file is read by python, the first 5 characters are skipped for some reason. Digging deeper, I see no reason for importlib to trim those characters. Internally it uses _io.open_code().read() which should return the entire file without trimming anything If adding the comment after the 5th char on the first line, the file is read as is should but the error moves to a different file: [Fri Apr 28 10:20:24.730194 2023] [wsgi:error] [pid 1316806:tid 140384699016960] [remote 127.0.0.1:41802] mod_wsgi (pid=1316806): Failed to exec Python script file '/usr/bin/octavia-wsgi'. [Fri Apr 28 10:20:24.730379 2023] [wsgi:error] [pid 1316806:tid 140384699016960] [remote 127.0.0.1:41802] mod_wsgi (pid=1316806): Exception occurred processing WSGI script '/usr/bin/octavia-wsgi'. [Fri Apr 28 10:20:24.732137 2023] [wsgi:error] [pid 1316806:tid 140384699016960] [remote 127.0.0.1:41802] Traceback (most recent call last): [Fri Apr 28 10:20:24.732294 2023] [wsgi:error] [pid 1316806:tid 140384699016960] [remote 127.0.0.1:41802] File "/usr/bin/octavia-wsgi", line 52, in <module> [Fri Apr 28 10:20:24.732316 2023] [wsgi:error] [pid 1316806:tid 140384699016960] [remote 127.0.0.1:41802] application = setup_app() [Fri Apr 28 10:20:24.732340 2023] [wsgi:error] [pid 1316806:tid 140384699016960] [remote 127.0.0.1:41802] File "/usr/lib/python3/dist-packages/octavia/api/app.py", line 62, in setup_app [Fri Apr 28 10:20:24.732353 2023] [wsgi:error] [pid 1316806:tid 140384699016960] [remote 127.0.0.1:41802] return pecan_make_app( [Fri Apr 28 10:20:24.732381 2023] [wsgi:error] [pid 1316806:tid 140384699016960] [remote 127.0.0.1:41802] File "/usr/lib/python3/dist-packages/pecan/__init__.py", line 86, in make_app [Fri Apr 28 10:20:24.732400 2023] [wsgi:error] [pid 1316806:tid 140384699016960] [remote 127.0.0.1:41802] app = Pecan(root, **kw) [Fri Apr 28 10:20:24.732453 2023] [wsgi:error] [pid 1316806:tid 140384699016960] [remote 127.0.0.1:41802] File "/usr/lib/python3/dist-packages/pecan/core.py", line 832, in __init__ [Fri Apr 28 10:20:24.732475 2023] [wsgi:error] [pid 1316806:tid 140384699016960] [remote 127.0.0.1:41802] super(Pecan, self).__init__(*args, **kw) [Fri Apr 28 10:20:24.732516 2023] [wsgi:error] [pid 1316806:tid 140384699016960] [remote 127.0.0.1:41802] File "/usr/lib/python3/dist-packages/pecan/core.py", line 240, in __init__ [Fri Apr 28 10:20:24.732536 2023] [wsgi:error] [pid 1316806:tid 140384699016960] [remote 127.0.0.1:41802] root = self.__translate_root__(root) [Fri Apr 28 10:20:24.732582 2023] [wsgi:error] [pid 1316806:tid 140384699016960] [remote 127.0.0.1:41802] File "/usr/lib/python3/dist-packages/pecan/core.py", line 275, in __translate_root__ [Fri Apr 28 10:20:24.732618 2023] [wsgi:error] [pid 1316806:tid 140384699016960] [remote 127.0.0.1:41802] module = __import__(name, fromlist=fromlist) [Fri Apr 28 10:20:24.732645 2023] [wsgi:error] [pid 1316806:tid 140384699016960] [remote 127.0.0.1:41802] File "/usr/lib/python3/dist-packages/octavia/api/root_controller.py", line 24, in <module> [Fri Apr 28 10:20:24.732716 2023] [wsgi:error] [pid 1316806:tid 140384699016960] [remote 127.0.0.1:41802] from octavia.api.v2 import controllers as v2_controller [Fri Apr 28 10:20:24.732760 2023] [wsgi:error] [pid 1316806:tid 140384699016960] [remote 127.0.0.1:41802] File "/usr/lib/python3/dist-packages/octavia/api/v2/controllers/__init__.py", line 19, in <module> [Fri Apr 28 10:20:24.732821 2023] [wsgi:error] [pid 1316806:tid 140384699016960] [remote 127.0.0.1:41802] from octavia.api.v2.controllers import availability_zone_profiles [Fri Apr 28 10:20:24.732908 2023] [wsgi:error] [pid 1316806:tid 140384699016960] [remote 127.0.0.1:41802] File "/usr/lib/python3/dist-packages/octavia/api/v2/controllers/availability_zone_profiles.py", line 1 [Fri Apr 28 10:20:24.732952 2023] [wsgi:error] [pid 1316806:tid 140384699016960] [remote 127.0.0.1:41802] Copyright 2019 Verizon Media [Fri Apr 28 10:20:24.733024 2023] [wsgi:error] [pid 1316806:tid 140384699016960] [remote 127.0.0.1:41802] ^ [Fri Apr 28 10:20:24.733107 2023] [wsgi:error] [pid 1316806:tid 140384699016960] [remote 127.0.0.1:41802] SyntaxError: invalid syntax As far as we can tell, this problem appears when importlib reads the file and hands it over incomplete (missing the first 5 chars). This issue only occurs on the Octavia containers and not on the other Openstack services. The other thing is that the fault is not consistent. It happens at Apache2 reload or restart but not everytime. Once in a few restarts. When the problem occurs, Octavia API is down. Env details: OS: Ubuntu 20.04 Kernel: 5.4.0-147-generic Openstack: Ussuri Octavia: ii octavia-api 6.2.2-0ubuntu1 all OpenStack Load Balancer as a Service - API frontend ii octavia-common 6.2.2-0ubuntu1 all OpenStack Load Balancer as a Service - Common files ii octavia-driver-agent 6.2.2-0ubuntu1 all OpenStack Load Balancer Service - Driver Agent ii octavia-health-manager 6.2.2-0ubuntu1 all OpenStack Load Balancer Service - Health manager ii octavia-housekeeping 6.2.2-0ubuntu1 all OpenStack Load Balancer Service - Housekeeping manager ii octavia-worker 6.2.2-0ubuntu1 all OpenStack Load Balancer Service - Worker ii python3-octavia 6.2.2-0ubuntu1 all OpenStack Load Balancer as a Service - Python libraries ii python3-octavia-lib 2.0.0-0ubuntu1 all Library to support Octavia provider drivers ii python3-ovn-octavia-provider 0.1.0-0ubuntu1 all OpenStack Octavia Integration with OVN - Python 3 library Python: Python 3.8.10 LXD: lxd 5.13-cea5ee2 24758 latest/stable canonical✓ - A bug was filled on launchpad for this issue: https://bugs.launchpad.net/ubuntu/+source/importlib/+bug/2018011 Thanks! Bug #2018011 “python3 - importlib fails to read first 5 chars fr...” : Bugs : importlib package : Ubuntu<https://bugs.launchpad.net/ubuntu/+source/importlib/+bug/2018011> A bit of context: we have an Openstack Ussuri deployment (HA) on Ubuntu Focal. Most Openstack services are running on LXD containers on 3 baremetals. There are also two OVN-dedicated-chassis which act as gateways and nova-compute nodes. A couple of days ago we updated all the packages in the environment to the latest versions (baremetals and lxc containers). After the updates, we started seeing problems with the Octavia API. The API would randomly give an internal server error. Octavia API is... bugs.launchpad.net

1 0

[kolla-ansible][xena][vmware][neutron]
by Andrej Moravčík 09 May '23

09 May '23

Hello community, I am evaluating OpenStack release Xena with VMware vSphere deployed using Kolla-ansible. I would really appreciate if someone with similar environment can confirm my findings or share his/her experience. I did some research and choose Xena, because it is still maintained release and vmware-nsx latest stable branch is xena. I have built customised Docker images with additional Neutron plugins from opendev.org/x/vmware-nsx<http://opendev.org/x/vmware-nsx>, then I deployed single controller using all-in-one Ansible inventory with customised globals.yml according https://docs.openstack.org/kolla-ansible/xena/reference/compute/vmware-guid… 1) Neutron creates flat or VLAN type provider networks and add related Distributed Virtual Port Group (PG) to vSphere Distributed Switch (vDS or DVS). PG is automatically created with naming convention “<network name>”-“<network ID suffix>", which may not be suitable for same use cases, eg. PG was created by Cisco ACI ahead of Neutron and is part of ACI EPG. Question: is this PG naming convention fixed by design or is it configurable? If I want to use existing vDS PG with Neutron how this can be achieved? 2) Neutron metadata and DHCP agents are not accessible to Nova instance attached to DVS PG. I can deploy simple instance from Cirros image, but I cannot provision DHCP or fixed IP address. Provisioning via config drive doesn’t work either, I filled bug report to Nova … https://bugs.launchpad.net/nova/+bug/2018973 The documentation says … "For VMware DVS, the Neutron DHCP agent does not attaches to Open vSwitch inside VMware environment, but attach to the Open vSwitch bridge called br-dvs on the OpenStack side and replies to/receives DHCP packets through VLAN. Similar to what the DHCP agent does, Neutron metadata agent attaches to br-dvs bridge and works through VLAN.” Question: Is it expected that Kolla-ansible creates working configurations for Nova and Neutron, if all related options in globals.yml are set up? Or further adjustment is needed on Openstack or vCenter side? Thank you. — Andrej Moravcik ________________________________ Táto správa a jej prílohy sú dôverné. Prosím, narábajte s týmito informáciami ako s dôvernými a nezverejňujte, nekopírujte ani neposielajte tieto informácie bez predchádzajúceho súhlasu spoločnosti Aliter Technologies, a.s. Ak nie ste adresátom indikovaným v záhlaví tejto správy alebo želaný príjemca, upovedomte prosím spoločnosť Aliter Technologies, a.s. odpoveďou na tento e-mail a pôvodnú správu vymažte zo svojho systému. Aliter Technologies - registrovaná ochranná známka pre EU, USA This message and any attachments are confidential. Please treat the information as confidential, and do not disclose, copy or deliver this message to anyone without Aliter Technologies' approval. If you are not the addressee indicated in this message or an intended recipient please notify Aliter Technologies a.s. by return e-mail and delete the message from your system. Aliter Technologies - Registered in WIPO & U.S. Patent and Trademark Office

1 0

[neutron][Secure RBAC] New policies enabled by default
by Slawek Kaplonski 09 May '23

09 May '23

Hi, It's just a heads up that [1] was merged recently and Neutron is using new, secure RBAC policies by default now. If You would see any issues with that, please report bug(s) and let me know. [1] https://review.opendev.org/c/openstack/neutron/+/879827 -- Slawek Kaplonski Principal Software Engineer Red Hat

3 4

[neutron] Bug deputy May 01 - May 07
by Rodolfo Alonso Hernandez 09 May '23

09 May '23

Hello Neutrinos: This is the bug report from last week. High: * https://bugs.launchpad.net/neutron/+bug/2018727: [SRBAC] API policies for get_policy_*_rule are wrong. Assigned to Slawek. Medium: * https://bugs.launchpad.net/neutron/+bug/2018009: ML2 context not considering tags at network creation and update. Assigned to Miro. * https://bugs.launchpad.net/neutron/+bug/2018289: OVN trunk subport missing bounding information. Assigned to Arnau. * https://bugs.launchpad.net/neutron/+bug/2018529: [OVN] Virtual ports cannot be used as VM ports. Assigned to Rodolfo. * https://bugs.launchpad.net/neutron/+bug/2018585: [SRBAC]New policies change the behavior for check rule type. Assigned to Rodolfo. * https://bugs.launchpad.net/neutron/+bug/2018599: Disable config option use_random_fully does not work. *Not assigned*. * https://bugs.launchpad.net/neutron/+bug/2018737: neutron-dynamic-routing announces routes for disabled routers. Assigned to Felix. Low: * https://bugs.launchpad.net/neutron/+bug/2018474: Unnecessary agent resource version. *Not assigned*. Regards.

1 0

Stepping down as Ironic core
by Arne Wiebalck 09 May '23

09 May '23

Dear all, With a change in my role at work about a year ago, the time I have had available for upstream technical work has dropped significantly. I would therefore like to step down from my role as one of the Ironic cores. I am really grateful to have worked closely with this team of incredibly talented, helpful and kind people, and would like to use this occasion to thank them for all the support they have provided during these past years ... and of course for all the fun we had! Cheers, Arne -- Arne Wiebalck CERN IT

4 3

Using Veeam
by Robert Winbladh 09 May '23

09 May '23

Hi, Not sure I am in the right place but thought I would give it a go. We have a s3 service using IBM Spectrum Scale that builds on/uses Openstack Swift. The problem that we are having is that if the client/user is using Veeam the bucket gets locked. IBM explains that it has something to do with outstanding requests/timeouts. And the bucket gets locked, and the client/user/Veeam cannot access it any longer. This happens all the time. So my questions is: * What can I do about it? Anything that can be tuned in Swift? * IBM tells me to spread the load across multiple buckets - but Veeam does not have support for that (as far as I understand) * Any kind of tuning that needs to be done in Veeam (if anyone would know) * We have tried lowering "concurrent tasks" to 1, but still the bucket gets locked. [cid:image001.png@01D98259.E2C0B2C0] Robert Winbladh Seniorkonsult Technical Operations Manager Incident Manager Problem Manager Change Control Board member Asigra Certified Engineer IBM Spectrum Protect

1 0

[gate][tripleo] gate blocker
by Ananya Banerjee 09 May '23

09 May '23

Hello, All Centos 8 jobs which deploy standalone are failing at the moment. Please hold rechecks if you hit standalone deploy failure on Centos 8 jobs. We are working on the bug: https://bugs.launchpad.net/tripleo/+bug/2018588 Thanks, Ananya -- Ananya Banerjee, RHCSA, RHCE-OSP Software Engineer Red Hat EMEA <https://www.redhat.com/> anbanerj(a)redhat.com M: +491784949931 IM: frenzy_friday @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 1

[all][tc][release] Hold the Python3.8 dropping
by Ghanshyam Mann 09 May '23

09 May '23

Hello Everyone, As you know the gate is breaking due to Python3.8 drop[1][2], which we discussed in the TC channel and meeting[3]. TC is preparing the guidelines on not dropping Python3.8 in 2023.2 pti. Meanwhile, governance guidelines are prepared, this email is a heads-up to hold the dropping of Python3.8 from your project/repo. Do not bump the min py version in setup.cfg (do not bump version in python_requires ). @Release team, It will be helpful if you can check/hold the release of any project/lib dropping the Python3.8. [1] https://lists.openstack.org/pipermail/openstack-discuss/2023-April/033450.h… [2] https://lists.openstack.org/pipermail/openstack-discuss/2023-April/033454.h… [3] https://meetings.opendev.org/meetings/tc/2023/tc.2023-04-25-18.00.log.html#… -gmann

1 1

[tc] Technical Committee next weekly meeting on May 9, 2023
by Nikolla, Kristi 09 May '23

09 May '23

Hi all, This is a reminder that the next weekly Technical Committee meeting is to be held on Tuesday, May 9, 2023 at 1800 UTC on #openstack-tc on OFTC IRC Please propose items to the agenda by editing the wiki page at https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting At the end of today I will send out an email with the finalized agenda. Thank you, Kristi Nikolla

1 1

[Diversity] Diversity and Inclusion WG Meeting reminder
by Amy Marrich 08 May '23

08 May '23

This is a reminder that the Diversity and Inclusion WG will be meeting tomorrow at 14:00 UTC in the #openinfra-diversity channel on OFTC. We hope members of all OpenInfra projects join us as we review the Foundation-wide diversity survey questions for release at Summit. Thanks, Amy (spotz)

1 0

Fwd: (Openstack-Cinder) Error
by Adivya Singh 08 May '23

08 May '23

HI, Can you please guide me, There is this error which i am getting "fatal: [t1w_cinder_volumes_container-29d71abf]: FAILED! => {"msg": "The conditional check 'cinder_backend_lvm_inuse | bool' failed. The error was: error while evaluating conditional (cinder_backend_lvm_inuse | bool): {{ (cinder_backends|default(\"\")|to_json).find(\"cinder.volume.drivers.lvm.LVMVolumeDriver\") != -1 }}: {'lvm': {'iscsi_ip_address': '{{ 172.29.244.50 }}', 'volume_backend_name': 'LVM_iSCSI', 'volume_driver': 'cinder.volume.drivers.lvm.LVMVolumeDriver', 'volume_group': 'cloud'}}: float object has no element 244\n\nThe error appears to be in '/opt/openstack-ansible/playbooks/common-playbooks/cinder.yml': line 67, column 7, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n - name: Configure container (cinder-volume) when lvm is in-use\n ^ here\n"} I understand this error to some extent, but want to confirm with you if any body have seen similiar kind of error storage_hosts: s1w: ip: 172.29.236.50 container_vars: #cinder_storage_availability_zone: nova #cinder_default_availability_zone: nova cinder_backends: lvm: volume_backend_name: LVM_iSCSI volume_driver: cinder.volume.drivers.lvm.LVMDriver volume_group: cloud-volume iscsi_ip_address: "{{ cinder_storage_address }}" limit_container_types: cinder_volume Regards Adivya Singh

1 0

[tc][all] Technical Committee Weekly Summary -- May 5, 2023
by Nikolla, Kristi 08 May '23

08 May '23

Hi all, Here’s another edition of “What’s happening on the Technical Committee.” Meeting ======= The Technical Committee met on May 2, 2023 on the Zoom. A recording of the meeting can be found on Youtube at https://youtu.be/e-IUZ1ymi_A The next meeting will be held on May 9, 2023 at 18:00UTC. For more information visit https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting Happenings ========== Adding Python 3.8 to PTI and expectation of Python support ---------------------------------------------------------- Based on the TC discussion during the last weekly meeting, the TC proposed a change adding Python 3.8 as a PTI requirement for libraries[0] and a proposal attempting to clarify which Python versions we should aim to support in general[1]. [0]. https://review.opendev.org/c/openstack/governance/+/882165 [1]. https://review.opendev.org/c/openstack/governance/+/882154 Changes ======= • Merged • Align release naming terminology (documentation-change) | https://review.opendev.org/c/openstack/governance/+/881706 • Appoint Jerry Zhou as Sahara PTL (formal-vote) | https://review.opendev.org/c/openstack/governance/+/881186 • Retire puppet-rally - Step 3: Retire Repository (project-update) | https://review.opendev.org/c/openstack/governance/+/880018 • New Open • Appoint Dmitriy Rabotyagov as Vitrage PTL (formal-vote) | https://review.opendev.org/c/openstack/governance/+/882139 • Appoint Hasan Acar as Monasca PTL (formal-vote) | https://review.opendev.org/c/openstack/governance/+/882374 • Add py38 as a PTI requirement for libraries (formal-vote) | https://review.opendev.org/c/openstack/governance/+/882165 • Clarify expectations on keeping Python versions (formal-vote) | https://review.opendev.org/c/openstack/governance/+/882154 • Abandoned • All Open • https://review.opendev.org/q/project:openstack/governance+status:open How to contact the TC ===================== If you would like to discuss or give feedback to TC, you can reach out to us in multiple ways: 1. Email: you can send an email with the tag [tc] on the openstack-discuss mailing list. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 16:00 UTC 3. IRC: Ping us using the 'tc-members' keyword on the #openstack-tc IRC channel on OFTC.

1 0

[Nova] Clean up dead vms entries from DB
by Satish Patel 07 May '23

07 May '23

Folks, I have a small environment where controllers and computers run on the same nodes and yes that is a bad idea. But now what happened the machine got OOM out and crashed and stuck somewhere in Zombie stat. I have deleted all vms but it didn't work. Later I used the "virsh destroy" command to delete those vms and everything recovered but my openstack hypervisor state show" command still says you have 91 VMs hanging in DB. How do i clean up vms entered from nova DB which doesn't exist at all. I have tried the command "nova-manage db archive_deleted_rows" but it didn't help. How does nova sync DB with current stat? # openstack hypervisor stats show This command is deprecated. +----------------------+--------+ | Field | Value | +----------------------+--------+ | count | 3 | | current_workload | 11 | | disk_available_least | 15452 | | free_disk_gb | 48375 | | free_ram_mb | 192464 | | local_gb | 50286 | | local_gb_used | 1911 | | memory_mb | 386570 | | memory_mb_used | 194106 | | running_vms | 91 | | vcpus | 144 | | vcpus_used | 184 | +----------------------+--------+ Technically I have only single VM # openstack server list --all +--------------------------------------+---------+--------+---------------------------------+------------+----------+ | ID | Name | Status | Networks | Image | Flavor | +--------------------------------------+---------+--------+---------------------------------+------------+----------+ | b33fd79d-2b90-41dd-a070-29f92ce205e7 | foo1 | ACTIVE | 1=100.100.75.22, 192.168.1.139 | ubuntu2204 | m1.small | +--------------------------------------+---------+--------+---------------------------------+------------+----------+

2 1

Re: openstack-discuss Digest, Vol 55, Issue 17
by BEDDA Fadhel 07 May '23

07 May '23

Good morning, I set up openstack, on an Ubuntu 22.04 VM. Installation went well: I created an account and a project, as well as all the steps for creating an Ubuntu 18 instance. But when launching the instance, I only have error messages. My question: Is there someone who can help me and provide me with a procedure complete and tested. With my sincere thanks Le sam. 6 mai 2023 à 10:21, <openstack-discuss-request(a)lists.openstack.org> a écrit : > Send openstack-discuss mailing list submissions to > openstack-discuss(a)lists.openstack.org > > To subscribe or unsubscribe via the World Wide Web, visit > > https://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. [Nova] Clean up dead vms entries from DB (Satish Patel) > 2. [OPENSTACK][rabbitmq] using quorum queues (Nguy?n H?u Kh?i) > 3. Re: openstack-discuss Digest, Vol 55, Issue 16 (BEDDA Fadhel) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 5 May 2023 15:14:18 -0400 > From: Satish Patel <satish.txt(a)gmail.com> > To: OpenStack Discuss <openstack-discuss(a)lists.openstack.org> > Subject: [Nova] Clean up dead vms entries from DB > Message-ID: > <CAPgF-fqVSj3YKx7cYSF3gzAbL54veXM= > S18K5-sX6XMCbjTWKA(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Folks, > > I have a small environment where controllers and computers run on the same > nodes and yes that is a bad idea. But now what happened the machine got OOM > out and crashed and stuck somewhere in Zombie stat. I have deleted all vms > but it didn't work. Later I used the "virsh destroy" command to delete > those vms and everything recovered but my openstack hypervisor state show" > command still says you have 91 VMs hanging in DB. > > How do i clean up vms entered from nova DB which doesn't exist at all. > > I have tried the command "nova-manage db archive_deleted_rows" but it > didn't help. How does nova sync DB with current stat? > > # openstack hypervisor stats show > This command is deprecated. > +----------------------+--------+ > | Field | Value | > +----------------------+--------+ > | count | 3 | > | current_workload | 11 | > | disk_available_least | 15452 | > | free_disk_gb | 48375 | > | free_ram_mb | 192464 | > | local_gb | 50286 | > | local_gb_used | 1911 | > | memory_mb | 386570 | > | memory_mb_used | 194106 | > | running_vms | 91 | > | vcpus | 144 | > | vcpus_used | 184 | > +----------------------+--------+ > > > Technically I have only single VM > > # openstack server list --all > > +--------------------------------------+---------+--------+---------------------------------+------------+----------+ > | ID | Name | Status | Networks > | Image | Flavor | > > +--------------------------------------+---------+--------+---------------------------------+------------+----------+ > | b33fd79d-2b90-41dd-a070-29f92ce205e7 | foo1 | ACTIVE | 1=100.100.75.22, > 192.168.1.139 | ubuntu2204 | m1.small | > > +--------------------------------------+---------+--------+---------------------------------+------------+----------+ >

2 1

Re: openstack-discuss Digest, Vol 55, Issue 16
by BEDDA Fadhel 06 May '23

06 May '23

Bonjour, J’ai mis en place openstack, sur une VM Ubuntu 22.04. L’installation s’est bien passé: J’ai créé un compte et un projet, ainsi que toute les étapes pour la création d’une instance Ubuntu 18. Mais lors de lancement de l’instance, je n’ai que des messages d’erreur. Ma question: Est ce qu’il y’a quelqu’un qui peut m’aider et me fournir une procédure complète et testée. Avec mes vifs remerciements Le ven. 5 mai 2023 à 20:09, <openstack-discuss-request(a)lists.openstack.org> a écrit : > Send openstack-discuss mailing list submissions to > openstack-discuss(a)lists.openstack.org > > To subscribe or unsubscribe via the World Wide Web, visit > > https://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. [release] Release countdown for week R-21, May 08-12 (El?d Ill?s) > 2. Re: Kubernetes Conformance 1.24 + 1.25 (Guilherme Steinm?ller) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 5 May 2023 14:30:58 +0000 > From: El?d Ill?s <elod.illes(a)est.tech> > To: "openstack-discuss(a)lists.openstack.org" > <openstack-discuss(a)lists.openstack.org> > Subject: [release] Release countdown for week R-21, May 08-12 > Message-ID: > < > VI1P18901MB07511B14C9655567C4A5EC88FF729(a)VI1P18901MB0751.EURP189.PROD.OUTLOOK.COM > > > > Content-Type: text/plain; charset="utf-8" > > Development Focus > ----------------- > > The Bobcat-1 milestone is next week, on May 11th, 2023! Project team > plans for the 2023.2 Bobcat cycle should now be solidified. > > General Information > ------------------- > > Libraries need to be released at least once per milestone period. Next > week, the release team will propose releases for any library which had > changes but has not been otherwise released since the 2023.1 Antelope > release. > PTLs or release liaisons, please watch for these and give a +1 to > acknowledge them. If there is some reason to hold off on a release, let > us know that as well, by posting a -1. If we do not hear anything at all > by the end of the week, we will assume things are OK to proceed. > > NB: If one of your libraries is still releasing 0.x versions, start > thinking about when it will be appropriate to do a 1.0 version. The > version number does signal the state, real or perceived, of the library, > so we strongly encourage going to a full major version once things are > in a good and usable state. > > Upcoming Deadlines & Dates > -------------------------- > > Bobcat-1 milestone: May 11th, 2023 > OpenInfra Summit Vancouver (including PTG): June 13-15, 2023 > Final 2023.2 Bobcat release: October 4th, 2023 > > > El?d Ill?s > irc: elodilles @ #openstack-release >

1 0

[release] Release countdown for week R-21, May 08-12
by Elõd Illés 05 May '23

05 May '23

Development Focus ----------------- The Bobcat-1 milestone is next week, on May 11th, 2023! Project team plans for the 2023.2 Bobcat cycle should now be solidified. General Information ------------------- Libraries need to be released at least once per milestone period. Next week, the release team will propose releases for any library which had changes but has not been otherwise released since the 2023.1 Antelope release. PTLs or release liaisons, please watch for these and give a +1 to acknowledge them. If there is some reason to hold off on a release, let us know that as well, by posting a -1. If we do not hear anything at all by the end of the week, we will assume things are OK to proceed. NB: If one of your libraries is still releasing 0.x versions, start thinking about when it will be appropriate to do a 1.0 version. The version number does signal the state, real or perceived, of the library, so we strongly encourage going to a full major version once things are in a good and usable state. Upcoming Deadlines & Dates -------------------------- Bobcat-1 milestone: May 11th, 2023 OpenInfra Summit Vancouver (including PTG): June 13-15, 2023 Final 2023.2 Bobcat release: October 4th, 2023 Előd Illés irc: elodilles @ #openstack-release

1 0

[neutron] Drivers meeting cancelled today
by Rodolfo Alonso Hernandez 05 May '23

05 May '23

Hello Neutrinos: Due to the lack of agenda [1], today's drivers meeting is cancelled. Have a nice weekend. [1]https://wiki.openstack.org/wiki/Meetings/NeutronDrivers

1 0

[dev][ceilometer] Add custom uptime metric to Ceilometer
by Angel Santana 04 May '23

04 May '23

Guys, I deployed Ceilometer into my OpenStack deployment using the Juju charm. I’m trying to add a custom metric that records the uptime of instances every hour. I’m totally lost on how to archive this or if it’s possible. Any help would be appreciate. So far I tried playing around with the meters.yaml and polling.yaml to see if I could pull it off with no luck. Is this possible? how should I do it? Thanks in advance. Regards, Ángel

3 2

Certbot auto renew
by Derek O keeffe 04 May '23

04 May '23

Hi all, We're having a problem with renewing letsencrypt certs via certbot in an external Neutron network where a security group is locking down HTTP+HTTPS access to select IP ranges. As far as we know the IP address for the Certbot ACME challenge server is always changing and therefore a static security group can't be set up to allow in traffic from that server. We have experimented with using UFW rules instead thinking we may be able to write a script to open port 80 periodically to allow the ACME challenge through, then close it back up, but it hasn't worked as we'd hoped either (either all traffic is blocked or the security group immediately takes precedence). Is there any way to programmatically enable + disable a security group as needed using something like OpenstackSDK to achieve the same thing? Thanks in advance. Regards,Derek

3 3

[openstack-ansible] Proposing Neil Hanlon for core reviewer
by Dmitriy Rabotyagov 04 May '23

04 May '23

Hi everyone, I'm pleased to propose Neil Hanlon as OpenStack-Ansible Core Reviewer. Neil has helped us a lot lately with maintenance of RHEL-like distros - both CentOS Stream and Rocky Linux, and basically has brought in support for the last one. Neil is present at meetings and always is responsive in IRC. At the same time they were providing useful reviews lately [1] If there are no objections, I will add Neil to the team on 25th of April 2023. Until then, please feel free to provide your feedback/opinions on the matter. [1] https://www.stackalytics.io/report/contribution?module=openstackansible-gro…

6 7

[openstack-helm] Nominate Karl Kloppenborg for openstack-helm-core
by Vladimir Kozhukalov 04 May '23

04 May '23

Dear Openstack-helmers, I would like to suggest Karl Kloppenborg as a member of the core review team. He's been actively doing code review recently and also contributed as a developer. He has been using Openstack-Helm for a few years now, so his experience as a user is also to our advantage. I hope for your support. -- Best regards, Kozhukalov Vladimir

2 2

[all][tc][vitrage] Final call for Vitrage project maintainers
by Ghanshyam Mann 03 May '23

03 May '23

Hello Everyone, You might have noticed that the Vitrage project is leaderless in this cycle[1]. Eyal, who was the previous PTL and the only maintainer of this project for more than two years[2], will not be able to continue in this project[3]. We thank and appreciate all previous maintainers' work on this project. This is the final call for maintainers. If anyone is using or interested in this project, this is the right time to step up and let us know in this email or IRC(OFTC) #openstack-tc channel. If there is no response by the end of April 2023, we will discuss the retirement of this project. [1] https://etherpad.opendev.org/p/2023.2-leaderless [2] https://www.stackalytics.io/?module=vitrage-group&release=wallaby [3] https://lists.openstack.org/pipermail/openstack-discuss/2023-April/033333.h… -gmann

2 2

OpenInfra Live - May 4, 2023 at 9 a.m. CT / 14:00 UTC
by Kristin Barrientos 03 May '23

03 May '23

Hi everyone, This week’s OpenInfra Live episode is brought to you by the OpenInfra Foundation Staff. Episode: May the OpenInfra Force Be With You: Preview of the OpenInfra Summit! Join us for an insightful and informative discussion as we give you the inside scoop on what’s in store at the OpenInfra Summit, Vancouver, happening, June 13-15! Don’t miss your chance to learn how you can get involved! Speakers: Wes Wilson, Allison Price, Jimmy McArthur, Kendall Nelson Date and time: May 4, 2023, at 9 a.m. CT. (14:00 UTC) You can watch us live on: YouTube: https://www.youtube.com/live/g_nTOpLGftw?feature=share LinkedIn: https://www.linkedin.com/events/7056677974057648128/comments/ WeChat: recording will be posted on OpenStack WeChat after the live stream Have an idea for a future episode? Share it now at ideas.openinfra.live. Thanks, Kristin Barrientos Marketing Coordinator OpenInfra Foundation

1 0

[dev][infra][qa][tact-sig] Future of Fedora and CentOS Stream Test Images
by Jeremy Stanley 03 May '23

03 May '23

tl;dr is that the OpenDev Collaboratory is looking at potentially scaling back on Fedora-based test platform support. Several options are presented in this service-discuss post: https://lists.opendev.org/archives/list/service-discuss@lists.opendev.org/t… If you have an opinion on using Fedora in our CI jobs, please follow up to the discussion there. -- Jeremy Stanley

1 0

[largescale-sig] Next meeting: May 3, 8utc
by Thierry Carrez 03 May '23

03 May '23

Hi everyone, The Large Scale SIG will be meeting this Wednesday in #openstack-operators on OFTC IRC, at 8UTC, our EU+APAC-friendly time. You can doublecheck how that UTC time translates locally at: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230503T08 Feel free to add topics to the agenda: https://etherpad.opendev.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez

1 1

Getting 403 from keystone as admin user.
by Andy Speagle 03 May '23

03 May '23

We're getting strange 403's from keystone on the CLI when trying to list users, groups, and role assignments. Running keystone 17.0.1 on ussuri. I've looked through our policy.json... can't find anything strange. Has anyone seen this behavior? Any ideas what can be done? Thanks.

2 1

Cinder Bug Report 2023-05-03
by Sofia Enriquez 03 May '23

03 May '23

Hello Argonauts, Cinder Bug Meeting Etherpad <https://etherpad.opendev.org/p/cinder-bug-squad-meeting> *Low* - Infinidat driver should use the pool's compression setting when creating volumes. <https://bugs.launchpad.net/cinder/+bug/2017815> - *Status: *Fix proposed to master <https://review.opendev.org/c/openstack/cinder/+/881188>. - Cinder retype fails with "no host supplied" for SolidFire driver. <https://bugs.launchpad.net/cinder/+bug/2018001> - *Status*: Unassigned. *Incomplete* - When cinder-backup and nova-compute at the same node,backup restore will delete multipath. <https://bugs.launchpad.net/cinder/+bug/2017952> - *Status*: Waiting for reported reply. 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

[OpenvSwitch][Neutron] native flow based firewall Vs LinuxBridge Iptables firewall
by Satish Patel 02 May '23

02 May '23

Folks, As we know, openvswitch uses a linuxbridge based firewall to implement security-groups on openstack. It works great but it has so many packet hops. It also makes troubleshooting a little complicated. OpenvSwitch does support native firewall features in flows, Does it mature enough to implement in production and replace it with LinuxBridge based IPtables firewall? ~S

3 3

[tc] Reminder: 2023-05-10 OpenInfra Board Sync
by Jeremy Stanley 02 May '23

02 May '23

The Open Infrastructure Foundation Board of Directors is endeavoring to engage in regular check-ins with official OpenInfra projects. The goal is for a loosely structured discussion one-hour in length, involving members of the board and the OpenStack TC, along with other interested community members. This is not intended to be a formal presentation, and no materials need to be prepared in advance. I've started an Etherpad where participants can brainstorm potential topics of conversation, time-permitting: https://etherpad.opendev.org/p/2023-05-board-openstack-sync As previously announced[*], we're planning to hold the next call at 20:00 UTC on Wednesday, May 10. A link to the conference bridge will be added to the pad prior to that time. [*] https://lists.openstack.org/pipermail/openstack-discuss/2023-April/033244.h… -- Jeremy Stanley

1 0

[horizon][nova][masakari] Instances created with "Any AZ" problem
by Nguyễn Hữu Khôi 02 May '23

02 May '23

Hello guys. I playing with Nova AZ and Masakari https://docs.openstack.org/nova/latest/admin/availability-zones.html Masakari will move server by nova scheduler. Openstack Docs describe that: If the server was not created in a specific zone then it is free to be moved to other zones, i.e. the AvailabilityZoneFilter <https://docs.openstack.org/nova/latest/admin/scheduling.html#availabilityzo…> is a no-op. I see that everyone usually creates instances with "Any Availability Zone" on Horzion and also we don't specify AZ when creating instances by cli. By this way, when we use Masakari or we miragrated instances( or evacuate) so our instance will be moved to other zones. Can we attach AZ to server create requests API based on Any Availability Zone to limit instances moved to other zones? Thank you. Regards Nguyen Huu Khoi

5 20

[kolla-ansible][all][nova][zed][latest] USB passthrough / Hot-plug / Cold-plug
by Modyngs 02 May '23

02 May '23

090c090cFolks, A USB device (not necessarily a mass/Flash drive) needs to be connected to one of the VMs (an openstack instance). Openstack installed with kolla-ansible{Latest version/ Also tested on Zed} ALL IN ONE Deployments on ubuntu server 22.04 ( Core i9 12900K). I found the [nova-libvirt] container which contains *virsh *and is able to edit it or use custom config for VMs. I've gone through lots of the docs, to name a few: https://libvirt.org/formatdomain.html https://wiki.openstack.org/wiki/Nova/USB_device_hot_cold_plug https://wiki.openstack.org/wiki/Nova/proposal_about_usb_passthrough https://documentation.suse.com/sles/15-SP1/html/SLES-all/cha-libvirt-config… https://wiki.openstack.org/wiki/Nova/USB_device_hot_cold_plug https://docs.nxp.com/bundle/GUID-487B2E69-BB19-42CB-AC38-7EF18C0FE3AE/page/… but none of them worked for me!! To reproduce: *Cold-Plug :* *$ lsusb (on host)* Bus 001 Device 014: ID 090c:1000 Silicon Motion >>>> Note Device number changed every time I disconnect the device. So it might be different in the changed attempt shown below) *$ docker exec -it nova_libvirt /bin/bash* *%Turn the Desired VM off* *# virsh list --all* Id Name State --------------------------------------------- 2 instance-00000002 running 19 instance-00000008 running - instance-0000000a shut off *# virsh edit instance-0000000a* Add the changes [1][2][3][4],... ( many efforts have been done but few samples of them are) [1]: under <devices> added <hostdev mode='subsystem' type='usb'> <source> <vendor id='0x090c'/> <product id='0x1000'/> </source> </hostdev> [2]:under <devices> added <controller type='usb' index='0'/> <hostdev mode='subsystem' type='usb'> <source> <vendor id='0x090c'/> <product id='0x1000'/> </source> </hostdev> [3]: under <devices> added <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x090c'/> <product id='0x1000'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </hostdev> [4]: under <devices> added <controller type='usb' model='nec-xhci' index='0'/> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x090c'/> <product id='0x1000'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </hostdev> [5]: <controller type='usb' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x090c'/> <product id='0x1000'/> </source> <address type='usb' bus='1' port='2'/> <controller type='usb' index='0'/> </hostdev> *%Start the VM* *expected behavior:* when login to the VM, lsusb or df -h shows the USB *what happened:* it wont show the USB from the VM *OR *virsh dumpxml instance-0000000a > instance-0000000a.xml and then change the configs as above and then virsh attach-device instance-0000000a --file /path/to/updated-instance-0000000a.xml --config *Hot-Plug :* *$ lsusb (on host)* Bus 001 Device 014: ID 090c:1000 Silicon Motion >>>> Note Device number changed every time I disconnect the device. So it might be different in the changed attempt shown below) *$ docker exec -it nova_libvirt /bin/bash* *# virsh list --all* Id Name State --------------------------------------------- 2 instance-00000002 running 19 instance-00000008 running 20 instance-0000000a running *#nano USB.xml* *%add changes explained in *[1][2][3][4],... *$ virsh attach-device instance-0000000a /path/to/USB.xml/file* *expected behavior:* lsusb or df -h shows the USB *what happened:* it wont show the USB from the VM *Can you please guide me through this? Any recommendation would be much appreciated!Any custom changes comes to your mind ( Reply it) would be solution for this problem /;* Thanks Best regards

2 1

[cinder][kolla][OpenstackAnsible] 2023.1 Antelope Cycle-Trailing Release Deadline
by Elõd Illés 02 May '23

02 May '23

Hello teams with trailing projects, The 2023.1 Antelope cycle-trailing release deadline is in ~1 months [1], and all projects following the cycle-trailing release model must release their 2023.1 Antelope deliverables by June 1st, 2023. The following trailing projects haven't been released yet for 2023.1 Antelope (aside the release candidates versions if exists). Cinder team's deliverables: - cinderlib OSA team's deliverables: - openstack-ansible-roles - openstack-ansible Kolla team's deliverables: - kayobe - kolla - kolla-ansible - ansible-collection-kolla This is just a friendly reminder to allow you to release these projects in time. Do not hesitate to ping us if you have any questions or concerns. [1] https://releases.openstack.org/bobcat/schedule.html#b-cycle-trail Thanks, Előd irc: elodilles @ #openstack-release

1 0

[openstack-helm] Cancelling monthly meetings
by Vladimir Kozhukalov 02 May '23

02 May '23

Dear Openstack-helmers, I would like to announce that we are going to stop having monthly IRC meetings due to the lack of interest. There are two major concerns: 1) It is usually not a good idea to wait few weeks for the next meeting to happen if you have something to discuss 2) If only few people are attending the meeting then it is anyway not enough to have a strong community consensus and to make any important decisions We discussed this a couple months ago in the IRC meeting and now it is time to do the next step and to cancel it. So, if you have something to discuss please feel free to start the discussion directly in the #openstack-helm Slack chat (Slack is our preferable way of communication). Today's meeting (May/02/2023) is also canceled. -- Best regards, Kozhukalov Vladimir

1 0

[tripleo] hold rechecks content provider gate blocker - CentOS-9 stream mirrors
by Ronelle Landy 02 May '23

02 May '23

Hello All, We have a check/gate blocker impacting all CentOS-9 jobs. Details are in: https://bugs.launchpad.net/tripleo/+bug/2018265 - CentOS-9 stream mirrors are returning Status code: 404. Per https://review.opendev.org/868392 - the Rackspace mirrors are being used to sync CentOS-9 repos - so possibly there is a lag/roll back there. We will post out once there is a fix/workaround or if the situation gets unblocked dueto an update. Thank you.

1 1

Offline Openstack Release:Train Deployment
by Vineet Thakur 02 May '23

02 May '23

Greetings openstack community members, It's regarding the deployment of openstack release: train on CentoOS 7.9 environment by using openstack-ansible tool. (Offline environment) We are facing challenges to download the packages, some package links are not accessible or somewhere PIP packages are not available as per the constraint requirement list. See: https://artifacts.ci.centos.org/sig-cloudinstance/centos-7-191001/x86-64/ce… For pip packages: https://opendev.org/openstack/requirements/raw/0cfc2ef6318b639bb4287fa051ea… During installation we are facing a lot of errors, and not sure what would be the best approach in such scenarios where packages are not available or need to be downloaded from random sites. We are in the mid of a mega deployment and appreciate it if you can guide us through. Awaiting your response, thank you. Kind Regards, Vineet Thakur

3 3

[tc] Technical Committee next weekly meeting on May 2, 2023
by Nikolla, Kristi 02 May '23

02 May '23

Hi all, This is a reminder that the next weekly Technical Committee meeting is to be held tomorrow (May 2) at 1800 UTC on Zoom. Items can be proposed by editing the wiki page at https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting At the end of today I will send out an email with the finalized agenda. Thank you, Kristi Nikolla

1 1

[kolla-ansible] How to test local docker registry
by Satish Patel 01 May '23

01 May '23

Folks, I have 3 controller nodes and on controller01 I have configured the local registry and pushed all images into the local registry. I have pointed out 2 other nodes to use controller01 local registry. When i run "kolla-ansible -i multinode deploy" it works on controller01 and docker start all containers but one controller02 and 03 I encounter error related docker registry Error: https://paste.opendev.org/show/bmwbM3PB33a8hrA1Wi6e/ docker daemon.json file on controller02 and 03 (docker-reg is point to controller01) root@controller02:~# cat /etc/docker/daemon.json { "bridge": "none", "insecure-registries": [ "docker-reg:4000" ], "ip-forward": false, "iptables": false, "log-opts": { "max-file": "5", "max-size": "50m" } How do I check my docker registry is functioning? I have tried following commands on 02 and 03 nodes but following error. root@controller02:~# docker pull docker-reg:4000/openstack.kolla/ubuntu-source-fluentd Using default tag: latest Error response from daemon: manifest for docker-reg:4000/openstack.kolla/ubuntu-source-fluentd:latest not found: manifest unknown: manifest unknown Are there any way to test if my registry is functional and nothing wrong. There are no network issues. I have a test with port ping using the nc command.

1 1

[Neutron] Bug deputy Apr 24 - May 1
by Jakub Libosvar 01 May '23

01 May '23

Hi all, I was the bug deputy for the last week. There are 2 critical bugs, one is pending merge at this time and one needs an assignee: https://bugs.launchpad.net/neutron/+bug/2017992 You can find the full report below. Kuba Critical - Jobs running on vexxhost provider failing with Mirror Issues https://bugs.launchpad.net/neutron/+bug/2017992 Needs an assignee - [master][functional] test_cascading_del_in_txn fails with ovsdbapp=2.3.0 https://bugs.launchpad.net/neutron/+bug/2018130 In progress: https://review.opendev.org/c/openstack/neutron/+/881896 Assigned to Yatin High - Tenant user cannot delete a port associated with an FIP belonging to the admin tenant https://bugs.launchpad.net/neutron/+bug/2017680 In progress: https://review.opendev.org/c/openstack/neutron/+/881827 Assigned to Fernando - OVN: ovnmeta namespaces missing during scalability test causing DHCP issues https://bugs.launchpad.net/neutron/+bug/2017748 In progress: https://review.opendev.org/c/openstack/neutron/+/881487 Assigned to Lucas - Incorrect use of "db_api.CONTEXT_*” decorators https://bugs.launchpad.net/neutron/+bug/2017784 In progress: https://review.opendev.org/c/openstack/neutron/+/881569 Assigned to Rodolfo - OVN trunk subport bouncing between compute while live-migrating https://bugs.launchpad.net/neutron/+bug/2017912 Assigned to Arnau Medium - Move OVN Metadata Agent code to the new OVN Neutron Agent https://bugs.launchpad.net/neutron/+bug/2017871 Assigned to Lucas - ML2 context not considering tags at network creation and update https://bugs.launchpad.net/neutron/+bug/ Low - Remove "neutron-ovn-tempest-ovs-release-ubuntu-old” job https://bugs.launchpad.net/neutron/+bug/2017500 In progress: https://review.opendev.org/c/openstack/neutron/+/881342 Assigned to Rodolfo - ``cmd.sanity.checks._get_ovn_version`` is returning a 3 element tuple, instead of 2 https://bugs.launchpad.net/neutron/+bug/2017878 In progress: https://review.opendev.org/c/openstack/neutron/+/881708 Assigned to Rodolfo - SQL warning retrieving ports if the network list is empty https://bugs.launchpad.net/neutron/+bug/2018000 In progress: https://review.opendev.org/c/openstack/neutron/+/881830 Assigned to Rodolfo

1 0

[tc][all] Technical Committee Weekly Summary -- April 28, 2023
by Nikolla, Kristi 01 May '23

01 May '23

Hi all, Here’s another edition of “What’s happening on the Technical Committee.” Meeting ======= The Technical Committee met on April 25 on the #openstack-tc channel on OFTC IRC. The next meeting will be held on May 2 at 18:00UTC on Zoom. For more information visit https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting Happenings ========== Holding on dropping Python 3.8 ------------------------------ We are drafting guidelines to keep Python 3.8 support in OpenStack for 2023.2. This was discussed during Tuesday's TC meeting as it was causing significant breakage to the gate. [0]. https://lists.openstack.org/pipermail/openstack-discuss/2023-April/033469.h… New proposal to add release naming recommendations for package maintainers ------------------------------------------------------- During the last TC meeting we discussed the confusion arising from upstream OpenStack standardizing on the release names (ex. 2023.2) whereas some distros were favoring codenames (ex. Bobcat). We have a proposal up to recommend package maintainers follow our naming.[1] [0]. https://meetings.opendev.org/meetings/tc/2023/tc.2023-04-25-18.00.log.html#… [1]. https://review.opendev.org/c/openstack/governance/+/881712 New Upstream Investment Opportunity: Ironic ARM Support ------------------------------------------------------- Thanks to Jay Faulkner for proposing a new investment opportunity that we just merged![0] "The OpenStack community is seeking ARM hardware and system administrators or developers with background in provisioning ARM devices to partner with the Ironic bare metal team. The Ironic project produces the OpenStack service and libraries to manage and provision physical machines." [0]. https://governance.openstack.org/tc/reference/upstream-investment-opportuni… Changes ======= • Merged • Add charmed openstack-hypervisor OpenStack Charms | https://review.opendev.org/c/openstack/governance/+/879437 • Update to hacking v6 (code-change) | https://review.opendev.org/c/openstack/governance/+/881266 • Switch to 2023.2 testing runtime py version (code-change) | https://review.opendev.org/c/openstack/governance/+/881137 • Correct the old deprecated policies removal timeline for SLURP release (formal-vote) | https://review.opendev.org/c/openstack/governance/+/880238 • Deprecate TripleO (formal-vote) | https://review.opendev.org/c/openstack/governance/+/877132 • Add Contribution Opportunity: Ironic ARM support (formal-vote) | https://review.opendev.org/c/openstack/governance/+/879080 • New Open • Appoint Jerry Zhou as Sahara PTL (formal-vote) | https://review.opendev.org/c/openstack/governance/+/881186 • Add recommendations for release naming to package maintainers (formal-vote) | https://review.opendev.org/c/openstack/governance/+/881712 • Align release naming terminology (documentation-change) | https://review.opendev.org/c/openstack/governance/+/881706 • Abandoned • All Open • https://review.opendev.org/q/project:openstack/governance+status:open How to contact the TC ===================== If you would like to discuss or give feedback to TC, you can reach out to us in multiple ways: 1. Email: you can send an email with the tag [tc] on the openstack-discuss mailing list. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 16:00 UTC 3. IRC: Ping us using the 'tc-members' keyword on the #openstack-tc IRC channel on OFTC.

1 0

[kolla-ansible][zed][15.1.0] Horizon failed to load trunk and QoS
by Stefan Bryzga 01 May '23

01 May '23

Hi all, Some time ago I deployed a small cluster with kolla-ansible v15.1.0. Before deployment I enabled neutron_qos and neutron_trunk flags in /etc/kolla/globals.yml. Both functions work fine via cli and I can create new entries via dashboard however horizon won't display created trunks/qos on the page (It shows "No items to display"). In web browser console I get this error while loading page: TypeError: Cannot read properties of undefined (reading 'data') at addTrackBy (output.0a9483334bbd.js:1115:59) at processQueue (output.43a09e34a303.js:1581:786) at output.43a09e34a303.js:1585:110 at Scope.$digest (output.43a09e34a303.js:1636:200) at Scope.$apply (output.43a09e34a303.js:1643:269) at done (output.43a09e34a303.js:1356:123) at completeRequest (output.43a09e34a303.js:1375:20) at XMLHttpRequest.requestLoaded (output.43a09e34a303.js:1368:1) 'Possibly unhandled rejection: {}' Does anyone knows how to fix this? Should I modify any configs to display new entries in horizon? Best Regards, Stefan

2 1