February 2025 - openstack-discuss

[tc][all] OpenStack Technical Committee Weekly Summary and Meeting Agenda (2025.1/R-7)
by Goutham Pacha Ravi 11 Feb '25

11 Feb '25

Hello Stackers, We're 7 weeks from the coordinated 2025.1 ("Epoxy") release [1]. Perhaps more importantly, we have three weeks until Feature Freeze, a code merge deadline for project teams with deliverables as part of that coordinated release. I'd recommend reading through the great summary of release deadlines and activities that Thierry Carrez (ttx) from the OpenStack Release Team sent to this list [2]. If you'd like to be a Project Team Lead or a member of the OpenStack TC, now is a great time to nominate yourself. Nominations are accepted until 23:45 UTC on 2025-02-19 [3]. In TC news this week, a couple of governance changes were merged, where we retired a redundant Ansible role project and added the OpenStack Libraries (Oslo) project team to the list of project teams requiring a PTL election. There are several governance changes open for the community's review. A number of contributors and operators participated in FOSDEM 2025 and met up at a Birds of a Feather session hosted by Amy Marrich (spotz). The meeting gathered some interesting thoughts [4] that we'll dive into during our weekly meeting this week. The OpenInfra Foundation is hosting two open community feedback meetings to discuss a proposal to join the Linux Foundation. One of these calls is today, 2025-02-11, at 16:00 UTC [5]. === Weekly Meeting === The OpenStack TC met over IRC [6] and video (Zoom) [7] last week. The meeting was well attended. We reviewed the state of participation of project liaisons in Oslo. The team behind Oslo has a tough job maintaining many disparate code repositories that aid service project teams. Members of the TC felt that the project might see more traction if they re-evaluated their leadership model. After the meeting, we added Oslo to the list of projects requiring a PTL election. The TC expressed that resetting the DPL model every cycle has been beneficial in identifying inactive maintainers and ensuring project continuity. A new release of PBR was made earlier in the day, and project maintainers were advised to report any packaging or obscure issues that may have arisen as a result in the #opendev channel on OFTC. We went on to discuss the state of the CI. Concerns were raised about heavy test loads and project teams running a large number of jobs on every change, which can impact the overall quota and cause other jobs to wait or be queued. Some projects are running upwards of 60 jobs on a single change, with many being multi-node jobs that can consume 10-20% of the overall quota. The TC is concerned about the high number of node hours being consumed by projects and encourages teams to review their test jobs to identify redundant or unnecessary tests. Some strategies to do this include identifying jobs that have remained non-voting for a long time and considering moving them to a periodic pipeline. Project teams should also be mindful of perma-failing test jobs and ensure these are removed until the underlying issue is fixed. The next meeting of the OpenStack TC is today, 2025-02-11, and will be held on the #openstack-tc IRC channel on OFTC at 18:00 UTC. Please find the agenda within the meeting wiki [8]. I hope you're able to join us. === Governance Proposals === ==== Merged ==== - Retire qdrouterd role | https://review.opendev.org/c/openstack/governance/+/938193 - Reset the DPL model for the Oslo project | https://review.opendev.org/c/openstack/governance/+/939485 ==== Open for Review ==== - Define testing runtime for the 2025.2 release | https://review.opendev.org/c/openstack/governance/+/941141 - Cleanup policy popup leads list | https://review.opendev.org/c/openstack/governance/+/941148 - Add Watcher project update liaison | https://review.opendev.org/c/openstack/governance/+/940168 - Define 2025 upstream investment opportunities | https://review.opendev.org/c/openstack/governance/+/939507 - Resolve to adhere to non-biased language | https://review.opendev.org/c/openstack/governance/+/934907 === How to Contact the TC === You can reach the TC in several ways: - Email: send an email with the tag [tc] on this mailing list. - Ping us using the 'tc-members' keyword on the #openstack-tc IRC channel on OFTC. - Join us at our weekly meeting: The Technical Committee meets every week on Tuesdays at 18:00 UTC [8]. === Upcoming Events === - 2025-02-19: Nominations submission deadline for 2025.2 TC/PTL Elections: https://governance.openstack.org/election/ - 2025-02-28: 2025.1 ("Epoxy") Feature Freeze and release milestone 3 [1] - 2025-03-06: SCALE 2025 + OpenInfra Days NA (https://www.socallinuxexpo.org/scale/22x) - 2025-03-11: OpenInfra Board Meeting: https://board.openinfra.org/ Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] 2025.1 "Epoxy" Release Schedule: https://releases.openstack.org/epoxy/schedule.html [2] Release countdown for week R-7: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [3] How to submit your candidacy in OpenStack elections: https://governance.openstack.org/election/#how-to-submit-a-candidacy [4] OpenStack BoF @ FOSDEM '25 Etherpad: https://etherpad.opendev.org/p/r.f28603feec88c9e91ff1ced894af35c9 [5] Join the discussion regarding OpenInfra Foundation joining the Linux Foundation: https://board.openinfra.org/strategic-consideration [6] TC Meeting IRC Log 2025-02-04: https://meetings.opendev.org/meetings/tc/2025/tc.2025-02-04-18.00.log.html [7] TC Meeting Video Recording, 2025-02-04: https://youtu.be/92afQSmLk08 [8] TC Meeting Agenda, 2025-02-11: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

[openstack][manila][cephfs]About access rule
by Nguyễn Hữu Khôi 11 Feb '25

11 Feb '25

Hello. I setup Manila with Cephfs driver-CephFS NFS shares and I use NFS-Ganesha based “ceph nfs” service. I can create a share and can mount after creating access rule: openstack share access create cephnfsshare ip 10.10.11.76 But I can mount my share from any ip. Is it a bug, or do I understand it wrong? My env: Openstack 2024 with Kolla-Ansible deployment Ceph Quincy Thank you. Regards Nguyen Huu Khoi

2 12

[publiccloud-sig] Reminder: Next meeting of Public Cloud SIG upcoming - February 12th at 0800 UTC
by Felix Kronlage-Dammers 11 Feb '25

11 Feb '25

Hi everyone, This upcoming Wednesday (February 12th) the next meeting of the publiccloud-sig is going to happen. We’ll be meeting at 0800 UTC here: https://meetpad.opendev.org/publiccloud-sig See also here for all other details: https://wiki.openstack.org/wiki/PublicCloudSIG Thanks to a very interesting FOSDEM (with an OpenStack BoF session) I do hope, that we'll have some newcomers to the SIG! See ya Wednesday! felix -- Felix Kronlage-Dammers Tel.: +49-30-206539-205 | Matrix: @fkronlage:matrix.org | fkr(a)osb-alliance.com

1 0

[openstack-ansible][masakari][yoga]Masakari ignoring host failure
by Danish Khan 11 Feb '25

11 Feb '25

Dear All, *Although, Masakari service seems to be working fine with few warning in one of my cluster but it is still ignoring all host failure:* Feb 10 10:34:04 compute7 masakari-introspectiveinstancemonitor[2379]: 2025-02-10 10:34:04.965 2379 WARNING masakarimonitors.introspectiveinstancemonitor.qemu_utils [-] Failed to connect socket to '/var/run/libvirt/libvirt-sock': Permission denied: libvirt.libvirtError: Failed to connect socket to '/var/run/libvirt/libvirt-sock': Permission denied *Crm status shows no resources:* root@compute7:~# crm status Cluster Summary: * Stack: corosync * Current DC: compute6 (version 2.0.3-4b1f869f0f) - partition with quorum * Last updated: Mon Feb 10 10:24:49 2025 * Last change: Fri Feb 7 11:05:54 2025 by hacluster via crmd on compute7 * 6 nodes configured * 0 resource instances configured Node List: * Online: [ compute2 compute3 compute4 compute5 compute6 compute7 ] Full List of Resources: * No resources *From horizon instance-ha notification:* Notification UUID 0e745a900479 Source Host UUID 21c0d6d8e9f1 Type COMPUTE_HOST Status ignored Generated Time Feb. 10, 2025, 3:35 p.m. Created At Feb. 10, 2025, 3:35 p.m. Updated At Feb. 10, 2025, 3:35 p.m. Payload {'event': 'STOPPED', 'cluster_status': 'OFFLINE', 'host_status': 'UNKNOWN'} Regards, Danish Khan

2 3

[elections][PTL][Telemetry] Non-candidacy
by Erno Kuvaja 11 Feb '25

11 Feb '25

Hi all, After a recent shift on the work focus, I'd like to thank you all for the efforts and support navigating the Telemetry boat around. I've been blessed working with this small but actively pushing for better community and truly wish someone finds the energy to keep the momentum going. Especially after Jadnesh moved on to next journey recently as well. Can't wait to see what's next ahead for the project. - Erno "jokke" Kuvaja

1 0

[blazar] virtual instance scheduling
by Winicius Allan 10 Feb '25

10 Feb '25

When applying Blazar filter to check if have available hosts, it is considering allocation ratio? File "/var/lib/kolla/venv/lib/python3.10/site-packages/blazar/plugins/instances/instance_plugin.py", line 310, in pickup_hosts ERROR oslo_messaging.rpc.server raise mgr_exceptions.NotEnoughHostsAvailable() ERROR oslo_messaging.rpc.server blazar.manager.exceptions.NotEnoughHostsAvailable: Not enough hosts available The host in blazar aggregate has 48 vcpus and 8.0 allocation ratio, 40 of this vcpus are consumed. Considering the allocation ratio, I must be able to create a lease with more than 8vCPU. Anyone can help? Regards.

2 2

[neutron] Bug deputy report (week starting on February 3)
by Bernard Cafarelli 10 Feb '25

10 Feb '25

Hey neutrinos, here are the reported during the first week of February All bugs have a fix (merged in several cases) or assignee. Only pending one is the last one reported on neutron-vpnaas (but on EOL branch) Critical * [OVN] Neutron OVN metadata agent broken - https://bugs.launchpad.net/neutron/+bug/2097273 Fixed by https://review.opendev.org/c/openstack/neutron/+/940679 * networking-bagpipe CI is broken since linuxbridge driver removal - https://bugs.launchpad.net/neutron/+bug/2097367 Mentioned in last week team meeting, picked up by Lajos High * test_async_process_respawns_with_race_condition functional test fails randomly - https://bugs.launchpad.net/neutron/+bug/2097284 Recent new functional test failure - fixed with https://review.opendev.org/c/openstack/neutron/+/940687 * test_async_process_respawns functional test failing in fips functional job - https://bugs.launchpad.net/neutron/+bug/2095598 Another recent failure - fixed in the end with previous fix + https://review.opendev.org/c/openstack/neutron/+/939627 Medium * [eventlet-removal] Use ``ThreadPoolExecutor`` for ``periodics.PeriodicWorker`` - https://bugs.launchpad.net/neutron/+bug/2097257 Title says it all - reported and picked up by Rodolfo * devstack-tobiko-neutron failing in zed and 2023.1 with missing designate - https://bugs.launchpad.net/neutron/+bug/2097286 Tobiko job failures in unmaintained branches since job config cleanup - should be good with https://review.opendev.org/c/x/devstack-plugin-tobiko/+/940694 * [OVN] OVN metadata agent should build the response according to the content - https://bugs.launchpad.net/neutron/+bug/2097431 Fix when body response is empty with merged https://review.opendev.org/c/openstack/neutron/+/940679 Untriaged * No connection from outside host to VPNaaS host after upgrading from Ussuri to Victoria/Wallaby - https://bugs.launchpad.net/neutron/+bug/2097610 VPNaaS issue on EOL branch - I did not close immediately in case vpnaas experts have an idea -- Bernard Cafarelli

1 0

[cinder] Bug report about cinder-migrate
by Gioh Kim (김기오) 10 Feb '25

10 Feb '25

Hi, I'd like to report a bug I found when doing cinder-migrate test. I really would appreciate it if somebody inform me if it is solved at the latest tag or not solved yet. I checked the latest tag 24.2.0 (https://github.com/openstack/cinder/releases/tag/24.2.0) but failed to find a bug patch looking relevant to my issue. I tested the volume migration of nvme volume (nvme-tcp volume with LVM) with "openstack volume migrate --host <servername@diskname#typename> <UUID>" command. The first migration worked well but the second migration failed always with "Skipping remove_export. No NVMe subsystem for volume: <uuid>" error. Below is what I found If the original volume UUID is '23c5155e' that exists in server-0002: = The first migration: server-0002 => server-0001 = - Create a new LVM volume with a different name UUID 'ed7a9c7b' => new nvme subsystem name is 'ed7a9c7b' (server-0001) - Set the UUID of new volume 'A' and set new attribute "os-vol-mig-status-attr:name_id | ed7a9c7b" - Remove/unmap the original volume on server-0002: unmap nvme subsystem name is '23c5155e' = The second migration server-0002 => server-0001 = - Create a new LVM volume with a different name UUID 'af60b1c7' on server-0001 - Try to unmap the nvme subsystem of 'af60b1c7' of server-0001 ==> it failed because there is no subsystem 'af60b1c7'. It should've unmap the subsystem "ed7a9c7b". I guess there is a problem at unmapping a subsystem of already migrated volume. It happens 100% whenever I migrated a volume twice. FYI, I am still using a ZED version. I hope it's solved at the latest tag. The HEAD commit of my repository is below: commit 51dbd1e8061012bee4baca8aa60bf16a459279f9 Merge: d854529c2 cb4682fb8 Author: Zuul <zuul(a)review.opendev.org> Date: Thu May 11 18:00:27 2023 +0000 Merge "Reject unsafe delete attachment calls" into stable/zed Gioh Kim (김기오) Cloud Storage Email gurugio(a)linecorp.com

1 0

[tacker] Cancelling the next meetings
by Yasufumi Ogawa 10 Feb '25

10 Feb '25

Hi all, Since I'm going to be out of office tomorrow, I'd skip the next IRC meeting. Thanks, Yasufumi

1 0

[kayobe][a-universe-from-nothing] How does one restart controller0/compute0 after a reboot?
by Jordan Olin (OLINSolutions) 10 Feb '25

10 Feb '25

Hello, I’m following a-universe-from-nothing (2024.2) here <https://github.com/stackhpc/a-universe-from-nothing/blob/stable/2024.2/READ…>.in order to upskill on OpenStack deployment technologies. I’ve played a bit with the RDO-based installs, but a-u-f-n seemed closer to reality. My host VM is running Jammy (hostname: aufn-seed-jammy), with 64GB RAM and 100GB disk. I successfully made it through "Configure and deploy OpenStack to the control plane”, had running “seed”, “controller0”, “compute0” VMs, and was able to login to Horizon. I thought, “great! Let’s snapshot it all and keep going." So, I shutdown the host VM, aufn-seed-jammy (the one that is hosting “seed”, “controller0”, and “compute0”. I created a snapshot. I then restarted the host VM. The host VM (aufn-seed-jammy), and the seed VM started and I’m able to “ssh stack@seed” from the Host VM without problems. But… neither “controller0” nor “compute0” started up on their own. After sourcing Kayobe, from the host VM, I can “sudo virsh list —all” and see the following: (kayobe in ${KAYOBE_ENVIRONMENT:-base}) ubuntu@aufn-seed-jammy:~/deployment/src/kayobe-config/etc/kayobe$ sudo virsh list --all Id Name State ------------------------------ 1 seed running - compute0 shut off - controller0 shut off I then tried to manually start them: (kayobe in ${KAYOBE_ENVIRONMENT:-base}) ubuntu@aufn-seed-jammy:~/deployment/src/kayobe-config/etc/kayobe$ sudo virsh start controller0 error: Failed to start domain 'controller0' error: Cannot get interface MAC on 'p-contr0-0-tap': No such device I then ran an “ip a” to see what interfaces I have, but did not find one with that name. (kayobe in ${KAYOBE_ENVIRONMENT:-base}) ubuntu@aufn-seed-jammy:~/deployment/src/kayobe-config/etc/kayobe$ ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 52:54:00:37:79:fd brd ff:ff:ff:ff:ff:ff inet 192.168.4.131/24 brd 192.168.4.255 scope global dynamic noprefixroute enp1s0 valid_lft 277sec preferred_lft 277sec inet6 fe80::a8ed:6b67:f6ac:d095/64 scope link noprefixroute valid_lft forever preferred_lft forever 3: braio: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1442 qdisc noqueue state UP group default qlen 1000 link/ether de:55:16:2e:d0:3c brd ff:ff:ff:ff:ff:ff inet 192.168.33.4/24 brd 192.168.33.255 scope global braio valid_lft forever preferred_lft forever inet 10.0.2.1/24 scope global braio valid_lft forever preferred_lft forever inet6 fe80::dc55:16ff:fe2e:d03c/64 scope link valid_lft forever preferred_lft forever 4: p-braio-ovs@p-braio-phy: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1442 qdisc noqueue state UP group default qlen 1000 link/ether 66:18:cb:57:05:41 brd ff:ff:ff:ff:ff:ff inet6 fe80::6418:cbff:fe57:541/64 scope link valid_lft forever preferred_lft forever 5: p-braio-phy@p-braio-ovs: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1442 qdisc noqueue master braio state UP group default qlen 1000 link/ether 52:23:1b:ab:1d:0c brd ff:ff:ff:ff:ff:ff 6: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 52:54:00:d3:fa:cc brd ff:ff:ff:ff:ff:ff inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0 valid_lft forever preferred_lft forever 7: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1442 qdisc noqueue master braio state UNKNOWN group default qlen 1000 link/ether fe:54:00:aa:0f:f6 brd ff:ff:ff:ff:ff:ff inet6 fe80::fc54:ff:feaa:ff6/64 scope link valid_lft forever preferred_lft forever 8: dummy1: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1442 qdisc noqueue master braio state UNKNOWN group default qlen 1000 link/ether 8a:a1:62:09:27:46 brd ff:ff:ff:ff:ff:ff The only interfaces starting with “p-“ are “p-braio-ovs@p-braio-phy” and “p-braio-phy@p-braoi-ovs”. I’m not clear on and would appreciate any suggestions and advice on the following: 1) What are the commands and sequence to properly/cleanly bring down an “a-universe-from-nothing” based environment? 2) What are the commands and sequence to properly/cleanly start up an “a-universe-from-nothing” based environment? Thank you in advance for your time and considerations. Kind regards, Jordan. =========================== Jordan Olin, TOGAF EA President and Chief Solutioneer OLINSolutions, Inc. e: jordan(a)olinsolutions.com p: +1 508-982-4872 w: olinsolutions.com This email and any files transmitted with it are confidential and are intended solely for the use of the individual or entity to which they are addressed. This communication may contain material protected by government legislation. If you are not the intended recipient or the person responsible for delivering this email to the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing or copying of this email is strictly prohibited. If you have received this email in error, please notify the sender by replying to this email and then delete the email from your computer.

1 0