February 2024 - openstack-discuss

[kolla][magnum] Creating Magnum trustee user role
by Satish Patel 23 Feb '24

23 Feb '24

Folks, I am deploying magnum using openstack release 2023.1 but getting this error. But I have a similar deployment running in another datacenter which didn't give any error. What could be the problem? TASK [magnum : Creating Magnum trustee user] **************************************************************************************** ok: [os-eng-ctrl-01] TASK [magnum : Creating Magnum trustee user role] *********************************************************************************** fatal: [os-eng-ctrl-01]: FAILED! => {"action": "os_user_role", "changed": false, "extra_data": {"data": null, "details": "None", "response": "None"}, "msg": "Must specify either a user or a group"}

4 6

[release] Release countdown for week R-5
by Thierry Carrez 23 Feb '24

23 Feb '24

General Information ------------------- This coming week is the deadline for client libraries: their last feature release needs to happen before "Client library freeze" on February 29th, 2024. Only bugfix releases will be allowed beyond this point. When requesting those library releases, you can also include the stable/2024.1 branching request with the review. As an example, see the "branches" section here: https://opendev.org/openstack/releases/src/branch/master/deliverables/pike/… February 29th, 2024 is also the deadline for feature work in all OpenStack deliverables following the cycle-with-rc model. To help those projects produce a first release candidate in time, only bugfixes should be allowed in the master branch beyond this point. Any feature work past that deadline has to be raised as a Feature Freeze Exception (FFE) and approved by the team PTL. Finally, feature freeze is also a good time for submitting a first version of your cycle-highlights. Cycle highlights are the raw data that helps shape what is communicated in press releases and other release activity at the end of the cycle, avoiding direct contacts from marketing folks. See https://docs.openstack.org/project-team-guide/release-management.html#cycle… for more details. Upcoming Deadlines & Dates -------------------------- Caracal-3 milestone (feature freeze): February 29th, 2024 (R-5 week) Cycle Highlights Due: March 7th, 2024 (R-4 week) RC1 deadline: March 14, 2024 (R-3 week) Final RC deadline: March 28, 2024 (R-1 week) 2024.1 Caracal final release: April 3rd, 2024 Dalmatian PTG: April 8-12, 2024 -- Thierry Carrez (ttx)

1 0

[openstack-ansible][live migration/migration of Paused VM] Need to migrate Paused VM on different host.
by Danish Khan 23 Feb '24

23 Feb '24

Hello Team, Is it possible to live migrate or migrate VM which is in paused state? I have few VMs which are in paused state which I need to migrate to a different host. Regards, Danish Khan

2 1

[neutron][ovs] br-tun bridge setup
by Jaime Ibar 23 Feb '24

23 Feb '24

Hi all, I'm setting up neutron and ovs and I can't make br-tun work and pick up the ip address configured in openvswitch_agent.ini file. If I tcpdump br-tun tcpdump -l -n -i br-tun 'port 4789' I don't see any traffic getting through however(it goes through the physical interface) if I spin up a vm, it reaches the internet, I can ping it from another machine after allocating a floating ip but can't ssh into it. Can anyone please share the /etc/network/interfaces file configuration for br-tun? Should the br-tun ip address be configured on the bridge or in the physical interface the bridge is attached to? Should the vxlan traffic go through br-tun bridge? Thanks Jaime -- salu2 Jaime

3 5

PTG April 2024 Teams List
by Kendall Nelson 23 Feb '24

23 Feb '24

Hello Everyone! The April 2024 Project Teams List is official! Projects + Teams - OpenInfra Foundation Teams - - Diversity & Inclusion Working Group - OpenInfra Edge Computing Group - Kata Containers - OpenDev - StarlingX - OpenStack - - Services - - Blazar - Cinder - CloudKitty - Designate - Glance - Horizon - Ironic - Keystone - Kolla - Magnum - Manila - Neutron - Nova - Octavia - OpenStackAnsible - OpenStack-Helm - OpenStackSDK/CLI - Quality Assurance - Release Management - Tacker - Other OpenStack Teams - - OpenStack Security SIG - OpenStack Technical Committee - PublicCloud SIG - RBAC - VDI If your team was planning to meet and isn’t on this list, please contact ptg(a)openinfra.dev IMMEDIATELY. Soon, I will be contacting moderators to sign up for time via the PTGBot[1] once I have it configured for the teams that are signed up to attend the event. Otherwise, please don't forget to register[2] — it's FREE! As usual, feel free to let us know if you have any questions! Thanks! -Kendall (diablo_rojo) [1] PTGBot Docs: https://github.com/openstack/ptgbot#open-infrastructure-ptg-bot [2] PTG Registration: https://ptg2024.openinfra.dev/ <http://ptg2023.openinfra.dev/>

1 1

[election][ptl][sunbeam] non-candidacy for Sunbeam
by James Page 23 Feb '24

23 Feb '24

Hi All I'm not going to stand for PTL of the Sunbeam project for the upcoming cycle in order to allow others in the core dev team to stand for this position. Cheers James

1 0

[all][diversity] Final call for mentors and projects for the May 2024 Outreachy round
by Dmitry Tantsur 22 Feb '24

22 Feb '24

Hi folks, Sorry for the late heads-up. We don't currently have any projects submitted for OpenStack this cycle. If you have a project and would like to contribute to make the world a better place, please submit at https://www.outreachy.org/communities/cfp/openstack/ until tomorrow, Feb 23rd, 4pm UTC. Don't hesitate to reach out with any questions! Dmitry

1 0

[antelope][kolla-ansible][magnum]Multidomain problem
by Franck VEDEL 22 Feb '24

22 Feb '24

Hello I'm coming back to you with a new problem, which has already been submitted. I thought it worked with Antelope but maybe not. I have a kolla-ansible installation, antelope, on Ubuntu22.04, multinode. everything works as I want. If I leave only one domain (Default), I add heat and magnum. This works (with /etc/kolla/config/magnum.conf and cluster_user_trust = True). I add a second domain (users from an Active Directory). And there, adding magnum no longer works. When I do a "kolla-ansible reconfigure.....), I get the error: "action": "os_user_role", "changed": false OK, a search gives me this link: https://github.com/ansible/ansible/issues/57099 But I'm in the antelope version. Is this problem still relevant? How can we solve it? Thanks for your advices. Franck.

1 0

kolla-ansible all in one reconfigure fails
by KK CHN 22 Feb '24

22 Feb '24

I have a kolla-ansible all-in-one openstack installation working on a Virtual Machine (Ubuntu22.04 on a ESXi 7.0 host) Reference: https://kifarunix.com/create-and-upload-custom-linux-image-into-openstack/?… All went well and able to get the horizon dashboard and default Cirros image and demo networks up and running. Able to create instances using the default image. To create cloud OS images from the ISO files , I have done additionally the following iinstallation in the same Ubuntu22.04 VM . STEP 1. *$ sudo apt install -y qemu-kvm virt-manager libvirt-daemon-system virtinst libvirt-clients bridge-utils* $ sudo systemctl enable --now libvirtd $ sudo systemctl start libvirtd Everything went well. I am able to get virt-manager up and running and able to create the Cloud Image from an Ubuntu22.04 Server ISO. Then I uploaded this cloud image to the All-IN-ONE kolla-ansible openstack horizon dashboard, the image creation was successful. 2. But when I tried to create an instance by using this image through the horizon dashboard the instance dialog doesn't show any availability zone (nova). I am sure before doing the step 1 I am able to create Linux instances using the default Cirros image multiple times and the instances up and running successfully with the default availability zone "nova" ( I mean kolla-ansible all-in-one openstack installation was working fine before doing the step 1). But now there is no availability zones showing in horizon for creating new instances. Availability Zone There are no Availability Zones. I checked in CLI also $ openstack hypervisor list //it also shows ( down) availability zones also down 3. So I decided to reconfigure the $ kolla-ansible -i all-in-one reconfigure step, but the step fails with the following. RUNNING HANDLER [nova-cell : Restart nova-ssh container] *********************** changed: [localhost] RUNNING HANDLER [nova-cell : Restart nova-libvirt container] ******************* changed: [localhost] RUNNING HANDLER [nova-cell : Checking libvirt container is ready] ************** FAILED - RETRYING: [localhost]: Checking libvirt container is ready (10 retries left). FAILED - RETRYING: [localhost]: Checking libvirt container is ready (9 retries left). FAILED - RETRYING: [localhost]: Checking libvirt container is ready (8 retries left). FAILED - RETRYING: [localhost]: Checking libvirt container is ready (7 retries left). FAILED - RETRYING: [localhost]: Checking libvirt container is ready (6 retries left). FAILED - RETRYING: [localhost]: Checking libvirt container is ready (5 retries left). FAILED - RETRYING: [localhost]: Checking libvirt container is ready (4 retries left). FAILED - RETRYING: [localhost]: Checking libvirt container is ready (3 retries left). FAILED - RETRYING: [localhost]: Checking libvirt container is ready (2 retries left). FAILED - RETRYING: [localhost]: Checking libvirt container is ready (2 retries left). FAILED - RETRYING: [localhost]: Checking libvirt container is ready (1 retries left). fatal: [localhost]: FAILED! => {"attempts": 10, "changed": true, "cmd": "set -o pipefail && docker exec -i nova_libvirt ls /run/libvirtd.pid\n", "delta": "0:00:00.016249", "end": "2024-02-21 16:21:22.750454", "msg": "non-zero return code", "rc": 1, "start": "2024-02-21 16:21:22.734205", "stderr": "Error response from daemon: container 46d139a236f57e41cfcf3121b3879ea01eae774d771415c5418b003c839f3257 is not running", "stderr_lines": ["Error response from daemon: container 46d139a236f57e41cfcf3121b3879ea01eae774d771415c5418b003c839f3257 is not running"], "stdout": "", "stdout_lines": []} Each time I do reconfigure, the reconfiguration fails by reaching the step RUNNING HANDLER [nova-cell : Restart nova-libvirt container] ******************* changed: [localhost] 4. Why it fails, what the root cause of it, I suspect due to step 1 all the errors happened . 4. How can I recover the all-in-one openstack installation back and be able to create instances and images as earlier? Only option is to fresh deploy the kolla-ansible -i all-in-one ? Then all the current VM and images will all be lost ? ( If it in production what the method is to recover ?? OR will loss all data in production by running deployment again ? ) Greetings, Krish

1 1

[manila] Collab Review discussion for Snapshot/Replication based backups for NetApp shares and Generic solution for human readable export locations
by Saravanan Manickam 21 Feb '24

21 Feb '24

Hello Zorillas and other interested stackers, We'll have collab review discussion on a couple of features the NetApp team is building in Caracal release. * Snapshot/Replication based backups for NetApp shares (Gireesh Awasthi) * Generic solution for human readable export locations and relevant implementation for NetApp and LVM drivers (Jayaanand Borra) Date: 22nd February 2024 Time: 1400 UTC https://etherpad.opendev.org/p/ptg-backup-manila https://etherpad.opendev.org/p/manila-share-backup <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fetherpad.…> https://etherpad.opendev.org/p/caracal-ptg-manila-human-readable-export-loc… Zoom: https://netapp.zoom.com/j/96908608436?pwd=aCtNSngxMWVTVlV6Ykx6OW85UDZndz09 Thanks, Saravanan

1 0