February 2025 - openstack-discuss

[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

[ovn][neutron] sriov port not able to get ip from DHCP
by Satish Patel 10 Feb '25

10 Feb '25

Folks, I have built a new openstack using kolla-ansible with 2024.1 with OVN plugin. So far everything is working good. Today I have added a new compute node with SRIOV port and it turns out vm is not able to obtain IP from DHCP. With the same subnet if I create general vm then it works and obtains IP but with sriov port it doesn't work. If I assign IP static on the vm interface then my VM is able to ping the outside world. I have deployed many clouds with OVN and SRIOV and never had an issue so I never dig into any kind of troubleshooting. This is the first time I have seen this issue. I have checked port mapping etc and all looks good. In SRIOV case what is the flow of DHCP? does physical interface send DHCP request on wire or DHCP request route via OVN br-int bridge? How will handle that DHCP request? Following two SRIOV port I have created but they are not able to obtain IP address via dhcp (ovn-nb-db)[root@os-chn-ctrl03 /]# ovn-nbctl --no-leader-only find Logical_Switch_Port type=external _uuid : a274df3b-6967-4f73-91ff-8f6eb46f70e0 addresses : ["fa:16:3e:03:55:44 10.74.2.35"] dhcpv4_options : 7829902c-5cdf-49cf-b478-7b683669c726 dhcpv6_options : [] dynamic_addresses : [] enabled : true external_ids : {"neutron:cidrs"="10.74.2.35/23", "neutron:device_id"="f4b91945-32f9-4961-a2cf-26b408218e35", "neutron:device_owner"="compute:sriov", "neutron:mtu"="", "neutron:network_name"=neutron-87131346-90d6-48ca-a045-214ff02ee9c0, "neutron:port_capabilities"="rx;tx;sg;tso;gso;gro;rxvlan;txvlan;rxhash;txudptnl", "neutron:port_name"=my-sriov-port, "neutron:project_id"="0c4956dce56a4503878007355850a04a", "neutron:revision_number"="32", "neutron:security_group_ids"="0bd505e8-d086-4d72-8e56-b913a8672f08", "neutron:subnet_pool_addr_scope4"="", "neutron:subnet_pool_addr_scope6"="", "neutron:vnic_type"=direct} ha_chassis_group : 0c41026b-3b01-485e-908a-523202aefcf9 mirror_rules : [] name : "0cbe012e-902a-4503-91a2-191b5f4acac5" options : {} parent_name : [] port_security : ["fa:16:3e:03:55:44 10.74.2.35"] tag : [] tag_request : [] type : external up : true _uuid : 1b245b6d-b720-41cd-a09c-79dc7eab3149 addresses : ["fa:16:3e:d8:4b:ab 10.74.2.181"] dhcpv4_options : 7829902c-5cdf-49cf-b478-7b683669c726 dhcpv6_options : [] dynamic_addresses : [] enabled : true external_ids : {"neutron:cidrs"="10.74.2.181/23", "neutron:device_id"="ac767d12-cff0-484e-b014-f3e42160cd8c", "neutron:device_owner"="compute:sriov", "neutron:mtu"="", "neutron:network_name"=neutron-87131346-90d6-48ca-a045-214ff02ee9c0, "neutron:port_capabilities"="rx;tx;sg;tso;gso;gro;rxvlan;txvlan;rxhash;txudptnl", "neutron:port_name"=my-sriov-p1, "neutron:project_id"="0c4956dce56a4503878007355850a04a", "neutron:revision_number"="5", "neutron:security_group_ids"="0bd505e8-d086-4d72-8e56-b913a8672f08", "neutron:subnet_pool_addr_scope4"="", "neutron:subnet_pool_addr_scope6"="", "neutron:vnic_type"=direct} ha_chassis_group : 0c41026b-3b01-485e-908a-523202aefcf9 mirror_rules : [] name : "bdf9261c-5cfc-4df1-9c11-c8ec26535eef" options : {} parent_name : [] port_security : ["fa:16:3e:d8:4b:ab 10.74.2.181"] tag : [] tag_request : [] type : external up : true

1 2

[nova] Wondering about dynamic overcommit scheduling
by Jacquet, Pierre 10 Feb '25

10 Feb '25

Hello, I am exploring the potential for resource consolidation from the initial placement perspective, specifically within the filter scheduler. From my research, I understand that OpenStack Watcher can addresses consolidation in a dynamic manner (monitoring resource usage and using live migration), while consolidation in nova seems to rely on a static overcommitment ratio, without accounting for real resource usage. Has dynamic overcommitment been considered for the initial placement phase? If not, I would like to propose implementing such a feature and would greatly appreciate any feedback or guidance from the community on this idea. Specifically, a custom filter could be interfaced with a monitoring stack to deploy servers as long as some thresholds are not exceeded Thank you for your time and input. Best regards, Pierre

3 2

[kolla-ansible] stuck at Discover nova hosts
by Satish Patel 08 Feb '25

08 Feb '25

Folks, I am deploying kolla-ansible 2024.1 but somehow it has been stuck here for the last 2 hours not giving me any kind of clue or error even when I run in -vvvv mode. Any idea what it's trying to discover and why there is no timeout for this task? TASK [nova-cell : Fail if cell settings not found] ************************************************************************************************************************ task path: /usr/local/share/kolla-ansible/ansible/roles/nova-cell/tasks/discover_computes.yml:7 skipping: [os-chn-gen-comp-001] => { "changed": false, "false_condition": "not nova_cell_settings", "skip_reason": "Conditional result was False" } TASK [nova-cell : Discover nova hosts] ************************************************************************************************************************************ task path: /usr/local/share/kolla-ansible/ansible/roles/nova-cell/tasks/discover_computes.yml:14 Using module file /usr/local/lib/python3.10/dist-packages/ansible/modules/command.py Pipelining is enabled. <os-chn-ctrl01> ESTABLISH SSH CONNECTION FOR USER: None <os-chn-ctrl01> SSH: EXEC ssh -C -o ControlMaster=auto -o ControlPersist=60s -o StrictHostKeyChecking=no -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o ConnectTimeout=10 -o 'ControlPath="/root/.ansible/cp/eaac57fe12"' os-chn-ctrl01 '/bin/sh -c '"'"'sudo -H -S -n -u root /bin/sh -c '"'"'"'"'"'"'"'"'echo BECOME-SUCCESS-pnxqbtjwqxuxexfjfrnpukckzrfbkegh ; /usr/bin/python3'"'"'"'"'"'"'"'"' && sleep 0'"'"'' Escalation succeeded

2 1

[release] Release countdown for week R-7
by Thierry Carrez 07 Feb '25

07 Feb '25

Development Focus ----------------- We are entering the last weeks of the 2025.1 Epoxy development cycle. From now until the final release, we'll send a countdown email like this every week. It's probably a good time for teams to take stock of their library and client work that needs to be completed yet. The non-client library freeze is coming up, followed closely by the client lib freeze. Please plan accordingly to avoid any last minute rushes to get key functionality in. General Information ------------------- Next week is the Extra-AC freeze, in preparation for elections. All contributions to OpenStack are valuable, but some are not expressed as Gerrit code changes. Please list active contributors to your project team who do not have a code contribution this cycle, and therefore won't automatically be considered an Active Contributor and allowed to vote. This is done by adding extra-acs to https://opendev.org/openstack/governance/src/branch/master/reference/projec… before the Extra-AC freeze on February 13th. A quick reminder of the upcoming freeze dates. Those vary depending on deliverable type: * Oslo libraries are entering feature freeze next week, February 13th. * General libraries (except client libraries) need to have their last feature release before Non-client library freeze (February 20th). Their stable branches are cut early. * Client libraries (think python-*client libraries) need to have their last feature release before Client library freeze (February 27th) * Deliverables following a cycle-with-rc model (that would be most services) observe a Feature freeze on that same date, February 27th. Any feature addition beyond that date should be discussed on the mailing list and get PTL approval. After feature freeze, cycle-with-rc deliverables need to produce a first release candidate (and a stable branch) before RC1 deadline (March 14th) * Deliverables following cycle-with-intermediary model can release as necessary, but in all cases before Final RC deadline (March 28th) Finally, now is also a good time to start planning what highlights you want for your deliverables in the cycle highlights. The deadline to submit an initial version for those is set to one week after Feature freeze (March 6th). Background on cycle-highlights: http://lists.openstack.org/pipermail/openstack-dev/2017-December/125613.html Project Team Guide, Cycle-Highlights: https://docs.openstack.org/project-team-guide/release-management.html#cycle… jeremy [at] openstack.org/fungi on IRC is available if you need help selecting or writing your highlights. Upcoming Deadlines & Dates -------------------------- Extra-AC freeze: February 13th (R-7 week) Oslo feature freeze: February 13th (R-7 week) Non-client library freeze: February 20th (R-6 week) Client library freeze: February 27th (R-5 week) epoxy-3 milestone: February 27th (R-5 week) Cycle highlights deadline: March 6th (R-4 week) -- Thierry Carrez (ttx)

1 0

[openstack-ansible][masakari][yoga]pcs cluster not getting started
by Danish Khan 07 Feb '25

07 Feb '25

Dear All, I have upgraded my openstack cluster from wallaby to Yoga. And I am facing issue with masakari services. pacemaker service is running fine on all nodes but pacemaker_remote.service is not getting started on any of the nodes. And Masakari containers doesn't have any idea of it monitor nodes. I purged the masakari cluster and tried to deploy it again. Playbook is running successfully again and again but it is not setting up the cluster. Playbook is not installing corosync service on masakari containers and now pacemaker server is also not getting installed on masakari api containers. I idea to run masakari in a way that it can create the cluster and install required services on its own? I tried with below but that did not work:

1 2

[Monasca][Masakari][Requirements] Migrate of of oslosphinx
by Tony Breeds 07 Feb '25

07 Feb '25

Hello all, This is a heads up to let you know that the requirements team have approved 940215: Drop oslosphinx | https://review.opendev.org/c/openstack/requirements/+/940215 which will mean any changes to Monasca or Masakari that touch a requirements file will fail. The solution is to remove your dependency on oslosphinx, as many projects have done this I expect there is plenty of knowledge in git epos for what needs to be done. In the short term if your gate is blocked you can land a change that switches check-requirements to non-voting -- Yours Tony.

1 0