February 2024 - openstack-discuss

[tc][powervmstacker-sig] Status of the PowerVMStacker SIG
by Takashi Kajinami 20 Feb '24

20 Feb '24

Hello, # I'm adding TC tag because this is a governance topic I happened to notice that none of the repositories[1] owned by the PowerVMStacker sig have not been updated for ~5 years. May I know the current status of this SIG ? The SIG list page[2] says this SIG is active but I don't think it's true now based on the update in these repos. If no one is actually working in the SIG then I'd suggest that we retire the SIG and its repositories. Note: It seems these repositories still have old stable branches(ocata, pike) and we may need some help from the release team with retirement of these branches. Thank you, Takashi Kajinami irc: tkajinam [1] https://opendev.org/openstack/ceilometer-powervm https://opendev.org/openstack/nova-powervm https://opendev.org/openstack/networking-powervm [2] https://governance.openstack.org/sigs/

2 3

Re: [Cinder] PTL non-candidacy
by Rajat Dhasmana 20 Feb '24

20 Feb '24

Thanks everyone! Good to know I was able to do justice to the PTL role and I will continue to be an active contributor in the Cinder project. On Mon, Feb 19, 2024 at 10:31 AM Tilay, Raghavendra < raghavendra-uddhav.tilay(a)hpe.com> wrote: > Thanks Rajat for all the help & guidance. > > > > *From:* Rajat Dhasmana <rdhasman(a)redhat.com> > *Sent:* Friday, February 16, 2024 9:51 PM > *To:* OpenStack Discuss <openstack-discuss(a)lists.openstack.org> > *Subject:* [Cinder] PTL non-candidacy > > > > Hello everyone, > > > > I'm sending this email out to let everyone know that I will not be running > for PTL for the Cinder project during the 2024.2 (Dalmatian) cycle. > > I started my PTL journey with the Zed cycle and it's been a great > experience leading the Cinder project for 4 cycles. > > > > I think it is time for someone else to step up and bring their insights > into the PTL tasks since I believe a new perspective will surely benefit > > the project. > > > > I would like to thank the Cinder team for their support, without which, it > would have been a very hard task to accomplish. > > Last but not the least, Brian and Jay (former Cinder PTLs) helped out a > lot to run things smoothly and in making complex decisions so a special > > thanks for all their help and support. > > > > Thanks > > Rajat Dhasmana >

1 0

Re: [neutron] qrouter namespace missing in controllers - opensack ussuri
by Sławek Kapłoński 20 Feb '24

20 Feb '24

Hi, Please don't drop openstack-discuss ML from the thread. Dnia piątek, 16 lutego 2024 04:39:05 CET keshav bareja pisze: > Hi > > I can see below status in the neutron command: > > [image: image] > > and qrouter namespace is missing in controller nodes for most of the > projects. > so instances are not accessible. > I tried to check errors in l3-agent but no major indication. tried > restarting all neutron services in all the 3 controllers but no success. > Also tried turning ha-mode disabled/enable but it seems qrouter namespace > is not getting generated. > All this issue started after reboot of one of the control nodes. > > How can I trigger the creation of qrouter namespace or any other > suggestions? Is it only qrouter namespace missing? Are snat-<router_id> namespaces for example created fine or also missing? Regarding triggering it manually You can't really do that in other way than restarting L3 agent on the node. But I guess there may be something in logs if the namespaces aren't created fine. Please enable debug logs in L3 agent, restart it and then share its logs with us. > > Regards > Keshav Bareja > > On Thu, Feb 15, 2024 at 9:19 PM keshav bareja <keshav.bareja(a)gmail.com> > wrote: > > > Hi > > > > We have DVR ha-mode activated , router for each project and showing as > > qrouter-() on each of the controller. > > > > For some project router , there is no qrouter-(router-id) in any of the > > controller node. > > > > Regards > > Keshav > > > > > > Sent from my iPhone > > > > > On 15 Feb 2024, at 8:27 PM, Sławek Kapłoński <skaplons(a)redhat.com> > > wrote: > > > > > > Hi, > > > > > > Dnia czwartek, 15 lutego 2024 18:37:01 CET keshav bareja pisze: > > >> Hi Team > > >> > > >> We are experiencing an issue of reachability in some of the projects, > > >> instances in the project are not reachable. It is a project specific > > issue. > > >> I tried to check router details and could observe . > > >> For the project having issues, I checked the router and could see that > > the > > >> qrouter namespace is not present in the command "ip netns" in any of the > > >> controllers. > > >> > > >> Problem started after a reboot of one controller. > > >> > > >> Do any one has faced a similar issue and any suggestions to recover > > this? > > >> > > >> Regards > > >> Keshav Bareja > > >> > > > > > > Any errors in the L3 agent logs on controllers? Are those DVR or > > centralized routers? > > > > > > -- > > > Slawek Kaplonski > > > Principal Software Engineer > > > Red Hat > > > -- Slawek Kaplonski Principal Software Engineer Red Hat

2 1

Red Cinder-volume detaching error
by Rohit Sansiya 20 Feb '24

20 Feb '24

Hello all, please help me i m unable to detach volume with the help of gui. i checked logs also no error it shows. [image: image.png] Your message is ready to be sent with the following file or link attachments: Rohit Sansiya https://sites.google.com/view/rpgcloud/research-india Note: To protect against computer viruses, e-mail programs may prevent sending or receiving certain types of file attachments. Check your e-mail security settings to determine how attachments are handled.

2 1

[publiccloud-sig] Reminder - next meeting February 21st - 0800 UTC
by Felix Kronlage-Dammers 20 Feb '24

20 Feb '24

Hi everyone, This Wednesday (February 21st) the next meeting of the public cloud sig is going to happen. Since the majority of participants in the sessions started to like the videocalls, we’ll be doing this as a videocall again. We’ll be meeting at 0800 UTC here: https://conf.scs.koeln:8443/OIF-public-cloud-sig See also here for all other details: https://wiki.openstack.org/wiki/PublicCloudSIG We’ve had a lively discussion couple of weeks ago and Artem (gtema) did make a good head start in regards to sketching out the discovery service. I’m fairly certain that this will be part of tomorrow’s meeting ;) See you tomorrow! felix -- Felix Kronlage-Dammers Product Owner IaaS & Operations Sovereign Cloud Stack Sovereign Cloud Stack — standardized, built and operated by many Ein Projekt der Open Source Business Alliance - Bundesverband für digitale Souveränität e.V. Tel.: +49-30-206539-205 | Matrix: @fkronlage:matrix.org | fkr(a)osb-alliance.com

1 0

kolla ansible all in one VM instance creation fails
by KK CHN 20 Feb '24

20 Feb '24

List 1. I followed the tutorial https://kifarunix.com/deploy-all-in-one-openstack-with- kolla-ansible-on-ubuntu-22-04/?expand_article=1 and able to get things up and running upto horizon dashboard login.( with the runinit once script ) which brings the default cirros image and default flavors and default networks. 2. When I tried to create a cirros instance either through the horizon dashboard or through openstack CLI the instance not up and running resulting in error . 3. NOTE: This kolla-ansible-all-in-one I am trying on a VM( Ubuntu22.04 VM deployed on ESXi 7.0 host). 4. Do I need to edit or enable something on the ESXi host machine or the Ubuntu base VM where I am trying the all-in-one installation ? ERROR as follows 2024-02-19 22:14:17.881 7 ERROR nova.compute.manager [instance: ca98a487-8214-4b41-bdbc-6eed0a9390cf] libvirt.libvirtError: unsupported configuration: Emulator '/usr/bin/qemu-system-x86_64' does not support virt type 'kvm' 2024-02-19 22:14:17.881 7 ERROR nova.compute.manager [instance: ca98a487-8214-4b41-bdbc-6eed0a9390cf] 2024-02-19 22:14:17.885 7 INFO os_vif [None req-133b5da1-40ad-45d4-af54-7e4fa299aeed 76b826e348324acb8ebf005721c0213a e83c8d350df24c51851c44bf6d6fc7d5 - - default default] Successfully unplugged vif VIFBridge(active=False,address=fa:16:3e:cc:95:02,bridge_name='qbr40ec669f-fc',has_traffic_filtering=True,id=40ec669f-fc19-4c1e-af03-5180819758a6,network=Network(db91c3c3-d0ca-41d1-9497-6511e79f2b10),plugin='ovs',port_profile=VIFPortProfileOpenVSwitch,preserve_on_delete=False,vif_name='tap40ec669f-fc') 2024-02-19 22:14:18.176 7 INFO nova.compute.manager [None req-133b5da1-40ad-45d4-af54-7e4fa299aeed 76b826e348324acb8ebf005721c0213a e83c8d350df24c51851c44bf6d6fc7d5 - - default default] [instance: ca98a487-8214-4b41-bdbc-6eed0a9390cf] Took 0.29 seconds to deallocate network for instance. 2024-02-19 22:14:18.280 7 INFO nova.scheduler.client.report [None req-133b5da1-40ad-45d4-af54-7e4fa299aeed 76b826e348324acb8ebf005721c0213a e83c8d350df24c51851c44bf6d6fc7d5 - - default default] Deleted allocations for instance ca98a487-8214-4b41-bdbc-6eed0a9390cf 2024-02-19 22:14:20.426 7 WARNING nova.virt.libvirt.driver [None req-00027f3f-4666-4f97-a672-085105be0946 - - - - - -] This host appears to have multiple sockets per NUMA node. The `socket` PCI NUMA affinity will not be supported. 2024-02-19 22:15:20.419 7 WARNING nova.virt.libvirt.driver [None req-00027f3f-4666-4f97-a672-085105be0946 - - - - - -] This host appears to have multiple sockets per NUMA node. The `socket` PCI NUMA affinity will not be supported. root@ubuntu-VM:/home/ubuntu# Greetings Krish

1 1

[tc] Next Meeting Tomorrow, Feb 20, 1800 UTC
by Jay Faulkner 19 Feb '24

19 Feb '24

Hi all, the next weekly meeting of the OpenStack Technical Committee is tomorrow, Feb 20, at 1800 UTC. The proposed agenda is: Agenda - Roll call - Follow up on tracked action items - Gate health check - Implementation of Unmaintained branch statuses - Testing runtime for 2024.2 release (gmann) - https://review.opendev.org/c/openstack/governance/+/908862 - 2024.1 TC Tracker - https://etherpad.opendev.org/p/tc-2024.1-tracker - Open Discussion and Reviews Thanks, Jay Faulkner OpenStack TC Chair

1 0

Request for support for the openstack trial
by Richard Buregeya 19 Feb '24

19 Feb '24

Hello team, My nova-compute is in disable mode and here are the logs and nova-compute is down... 2024-02-19 10:49:43.131 7 ERROR oslo_service.service File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 638, in init_host 2024-02-19 10:49:43.131 7 ERROR oslo_service.service self._do_quality_warnings() 2024-02-19 10:49:43.131 7 ERROR oslo_service.service File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 604, in _do_quality_warnings 2024-02-19 10:49:43.131 7 ERROR oslo_service.service caps = self._host.get_capabilities() 2024-02-19 10:49:43.131 7 ERROR oslo_service.service File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/host.py", line 705, in get_capabilities 2024-02-19 10:49:43.131 7 ERROR oslo_service.service xmlstr = self.get_connection().getCapabilities() 2024-02-19 10:49:43.131 7 ERROR oslo_service.service File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/host.py", line 516, in get_connection 2024-02-19 10:49:43.131 7 ERROR oslo_service.service raise exception.HypervisorUnavailable(host=CONF.host) 2024-02-19 10:49:43.131 7 ERROR oslo_service.service HypervisorUnavailable: Connection to the hypervisor is broken on host: node001 2024-02-19 10:49:43.131 7 ERROR oslo_service.service Regards Richard.

2 1

Removal of boto from Debian
by Thomas Goirand 19 Feb '24

19 Feb '24

Hi, There's currently an ongoing effort to remove boto from Debian. The reason is: there's boto3, and boto is not maintained anymore. These a number of packages that are still using it. Affected packages in the OpenStack world are (at least for Bobcat, we'll see for Caracal): - glance-store - swift - heat-cfntools This IMO requires immediate action from the concerned team, to hopefully get rid of this requirement before Caracal is released. My excuses in advance if the work has already been done. Cheers, Thomas Goirand (zigo)

2 1

[kolla-ansible][Antelope][Senlin] Stop In Progress Updates
by Devin Patterson 19 Feb '24

19 Feb '24

Hello, We are using Senlin to create scaling groups and monitor VM health as well as do rolling updates. Does anyone know of a way to stop an in progress rolling update? For example, if we trigger Senlin to use a new profile, can we stop the update once it is started? Even better, is there a way to connect Senlin health policies to the rolling updates to stop the update if previous node health fails? Regards, Devin

1 0