February 2024 - openstack-discuss

[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 20 Feb '24

20 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 20 Feb '24

20 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

[neutron] bug deputy report for week of 2024-02-12
by Bence Romsics 19 Feb '24

19 Feb '24

Hi All, We had a handful of new bug reports last week: gate-failure: * https://bugs.launchpad.net/neutron/+bug/2052915 "neutron-ovs-grenade-multinode" and "neutron-ovn-grenade-multinode" failing in 2023.1 and Zed proposed fixes: https://review.opendev.org/q/topic:bug/2052915 * https://bugs.launchpad.net/neutron/+bug/2053227 [ovn-octavia-provider] ovn-octavia-provider-functional-master is broken by ovn build failure proposed fix: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/909074 unassigned: * https://bugs.launchpad.net/neutron/+bug/2053274 [ovn] mtu for metadata veth interface is not set high: * https://bugs.launchpad.net/neutron/+bug/2052937 Policy: binding operations are prohibited for service role proposed fixes: https://review.opendev.org/q/topic:bug/2052937 * https://bugs.launchpad.net/neutron/+bug/2054203 Default flag change in netaddr breaks (at least) unit tests proposed fix: https://review.opendev.org/c/openstack/neutron/+/909317 rfe: * https://bugs.launchpad.net/neutron/+bug/2052906 [RFE] OpenVSwitch HTB QoS not efficient for a lot of interfaces Cheers, Bence

1 0

[Cinder] PTL non-candidacy
by Rajat Dhasmana 19 Feb '24

19 Feb '24

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

7 6

[all] Upcoming incompatible changes in netaddr 1.0.x
by Takashi Kajinami 17 Feb '24

17 Feb '24

Hello, While looking into some test failures in an attempt to bump netaddr from 0.10.x to 1.0.x[1], we learned that there are a few changes in netaddr 10.0.x impacting our current usage. I'll attempt to summarize a few important ones in this email, and would like to ask each team to look into your project to assess the impacts caused by these changes. 1. INET_PTON (more restrictive check by default) is used by default In 1.0.1, all features dependent on ip address parsing uses INET_PTON by default instead of INET_ATON. With this change a few "strange" address values such as '192.0' or even '1' is no longer accepted. In case you want to restore the previous behavior then you have to add flags=netaddr.core.INET_ATON to each call. See [2] for example. This is caught in neutron unit tests[4] but my need to be further check in libraries handling IP addresses. 2. valid_ipvN raises exception for non-string value. Previously netaddr.valid_ipv(4|6) returned False for non-string values such as None. This was (unintentionally) changed in 1.0.x. I proposed restoring the old behavior but the maintainer preferred strictness about the input type, and we eventually agreed on throwing more explicit exception (TypeError). At this moment this affects only manila unit tests which I'm fixing by [5], but I wonder if there is any specific use case in any project dependent on the previous behavior. If so then probably we can add our own logic to handle non-string value, for example in oslo_utils.netutils. 3. A few deprecated interfaces are removed. At this moment I'm aware of only impact on heat (caused by implicit_prefix removed), but double-check my be better. Thank you, Takashi [1] https://review.opendev.org/c/openstack/requirements/+/909300 [2] https://review.opendev.org/c/openstack/oslo.utils/+/909307 [3] https://github.com/netaddr/netaddr/issues/368 [4] https://bugs.launchpad.net/neutron/+bug/2054203 [5] https://review.opendev.org/c/openstack/manila/+/909298 -- Takashi Kajinami irc: tkajinam github: https://github.com/kajinamit launchpad: https://launchpad.net/~kajinamit

1 0

[kolla][rabbitmq]: Error when ensuring rabbitmq users exists
by Winicius Allan 17 Feb '24

17 Feb '24

Hello o/, After an upgrade of nodes packages, we have been facing a problem when reconfiguring RabbitMQ and Nova. In the tasks that ensures RabbitMQ users exists the output of task is: FAILED - RETRYING: [xxxx]: nova | Ensure RabbitMQ users exist (5 retries left). FAILED - RETRYING: [xxxx]: nova | Ensure RabbitMQ users exist (4 retries left). FAILED - RETRYING: [xxxx]: nova | Ensure RabbitMQ users exist (3 retries left). FAILED - RETRYING: [xxxx]: nova | Ensure RabbitMQ users exist (2 retries left). FAILED - RETRYING: [xxxx]: nova | Ensure RabbitMQ users exist (1 retries left). I've already tried to redeploy rabbit and reconfigure after that, but does not work neither Anyone can help? I'm unable to perform any operation in my environment. Thanks! Winicius.

3 6

How to enable or disable a hypervisor via openstack python module
by Saeed 16 Feb '24

16 Feb '24

Hello, I use this module to find if any hypervisors are disabled: https://github.com/openstack/openstacksdk I can find and see if any hypervisor is disabled and see the reason, but I didn't find any docs about how to enable (or even disable) a hypervisor. This is my code to find disabled hypervisors: import openstack > regions = ['region1', 'region2', 'region3'] > openstack.enable_logging(debug=False)disabled_hypervisors = [] > for region in regions: > conn = openstack.connect(cloud=region) # clouds.yaml > for server in conn.compute.hypervisors(details=True): > a = server.to_dict() > if a['status'] == 'disabled' and > a['service_details']['disabled_reason'] != None: > disabled_hypervisors.append({'name': a['name'], 'ip': > a['host_ip'], 'disabled_reason': a['service_details']['disabled_reason']}) Regards, Saeed

2 2

Subject: [tc][election] gouthamr's TC Candidacy for 2024.2
by Goutham Pacha Ravi 16 Feb '24

16 Feb '24

Hello Stackers, I'm expressing my interest to join the OpenStack Technical Committee with your acceptance. I have had a long and exciting stint with OpenStack; and can probably claim to have evolved along with it. I began my active contribution journey in the Liberty release, and have had the pleasure to build a community around the OpenStack Manila project for most of this time. In many ways, my efforts here were rooted in the core ideology of this community: the fervent desire for openness that drives each decision [1]. I coupled that with my own penchant for mentoring; the result of which is a vast number of new contributors in the form of Outreachy, Google Summer of Code, Grace Hopper Celebrations, and student projects with numerous universities. All of this was done with similarly motivated fellow conspirators. This experience has helped me foster the diversity of thought in our community, and provided sustained energy to a small group of people chopping wood and carrying water around software whose relevance transcends hype cycles. I now wish to employ this energy and experience in service as a member of the TC. I set out the following goals to drive within the team: * Sustain and improve collaboration: I wish to extend TC's charter on investment opportunities with the "formal" mentorship engagements we have had in the community, including but not limited to Outreachy, GSOC, GSOD, GHC and university projects. I've new ideas here, and feel like a TC member can add a ton of excitement to this niche area of people enthusiastic to do this year on year. * Commit to a closer collaboration with adjacent communities: I am inspired by our willingness to engage with maintainers of software that work with OpenStack. My pitch is for us to identify TC representation within projects like Ceph, Kubernetes and others for active and periodic communication. * Drive long running efforts to completion: prime examples here are efforts for coherence for operators and users: Unified CLI, Limits, and Secure RBAC defaults. Thank you for considering my candidacy. I look forward to the opportunity to serve our community and contribute to the continued success of OpenStack. Warm regards, Goutham Pacha Ravi (gouthamr) [1] https://openinfra.dev/four-opens/ [2] https://review.opendev.org/c/openstack/election/+/909239

1 0

[manila][ceph] Collab Review/design discussion for Cback Share Backup driver
by Goutham Pacha Ravi 16 Feb '24

16 Feb '24

Hello Zorillas and other interested stackers, Folks at CERN have been working with Manila's share backup feature and are authoring a new backup driver for CBack [1]. We are hosting a call to dive into the implementation and discuss how the feature works with CephFS shared file systems. If this is of interest to you, please join us on: Date: 22nd February 2024 Time: 1600 UTC Location: https://meetpad.opendev.org/manila-caracal-cback-driver Etherpad: https://etherpad.opendev.org/manila-caracal-cback-driver <https://meetpad.opendev.org/manila-caracal-cback-driver> [1] https://cds.cern.ch/record/2767135?ln=en Thanks, Goutham

1 0

[ironic] PTL non-candidacy
by Jay Faulkner 16 Feb '24

16 Feb '24

As I've mentioned in IRC, and various times throughout the cycle -- I do not intend to run for PTL of Ironic for Dalmation. I encourage Ironic contributors to run for PTL and will gladly offer any assistance to whomever is elected. Thanks, Jay Faulkner Ironic PTL

1 0

[release] Release countdown for week R-6, Feb 19-23
by Elõd Illés 16 Feb '24

16 Feb '24

Development Focus ----------------- Work on libraries should be wrapping up, in preparation for the various library-related deadlines coming up. Now is a good time to make decisions on deferring feature work to the next development cycle in order to be able to focus on finishing already-started feature work. General Information ------------------- We are now getting close to the end of the cycle, and will be gradually freezing feature work on the various deliverables that make up the OpenStack release. This coming week is the deadline for general libraries (except client libraries): their last feature release needs to happen before "Non-client library freeze" on February 22nd, 2024. Only bugfixes 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/… In the next weeks we will have deadlines for: * Client libraries (think python-*client libraries), which need to have their last feature release before "Client library freeze" (February 29th, 2024) * Deliverables following a cycle-with-rc model (that would be most services), which observe a Feature freeze on that same date, February 29th, 2024. Any feature addition beyond that date should be discussed on the mailing-list and get PTL approval. As we are getting to the point of creating stable/2024.1 branches, this would be a good point for teams to review membership in their $project-stable-maint groups. Once the stable/2024.1 branches are cut for a repo, the ability to approve any necessary backports into those branches for 2024.1 Caracal will be limited to the members of that stable team. If there are any questions about stable policy or stable team membership, please reach out in the #openstack-stable channel. Upcoming Deadlines & Dates -------------------------- Non-client library freeze: February 22nd, 2024 (R-6 week) Client library freeze: February 29th, 2024 (R-5 week) Caracal-3 milestone: February 29th, 2024 (R-5 week) Cycle Highlights Due: March 7th, 2024 (R-4 week) 2024.1 Caracal final release: April 3rd, 2024 Dalmatian PTG: April 8-12, 2024 Előd Illés irc: elodilles @ #openstack-release

1 0

[keystone] Reviewathon canceled
by Dave Wilde 16 Feb '24

16 Feb '24

I’m on PTO today and won’t be able to host the reviewathon so I’m cancelling it. Please reach out if you need anything. Thanks! /Dave

1 0

[Cinder] User visible information in Volume Types
by Josephine Seifert 16 Feb '24

16 Feb '24

Hi, as discussed in the Cinder midcycle meeting: I would like to add something to the volume types to be able to see certain information. I am also working out a spec for this, but here are the options I have in mind/we have discussed yesterday: Use Cases -------------- As a non-admin user creating a volume I would like to see various information about the volume type. Some of them are already available (e.g. multiattach). While others are either not available at all or not available for non-admin users. Two of those information are: 1. Whether a volume type can be used to create encrypted volumes 2. Whether a volume type creates replicated volumes, either through Cinder or through a configured backend like ceph The first information comes from the encryption type within the volume, that is only accessible for the admin role. The second information can either be set and directly seen in the volume type extra_specs or is indirectly a part of the configuration of the backend. There might be other use cases, where an operator wants to set certain information about the volume type. As there are more and more tools that automatically create IaaS resources, those information should be accessible in a uniform way. Possible changes ------------------------ Here are a few ways to solve this problem. 1. Using the already existing user facing "properties" field. Administrators can already set key,value pairs here and user visible extra_specs can be seen in this field. This would lead to a problem in the volume scheduler, as EVERY input is going into the extra_specs table and the scheduler will try to fulfill every key=value pair a volume type requests when looking for a fitting backend for the volume. 1.a) This could be solved in creating a whitelist or blacklist, so not every extra_spec is checked in the scheduler. Either all only informational extra_specs should be ignored or a list of extra_specs, that will be checked could be created. 1.b) Another option would be to create another database table: metadata and put every key=value pair in there at the time of their creation, that should not be used in the scheduling process. The "properties" field would then be build in the API from a merge of the extra_specs and the metadata table. (This may also prevent the volume type from getting unusable, when some adds a key=value pair to the "properties", that is not meant for the scheduler - right now this would break the volume creation process) 2. Creating a new "metadata" field, that will contain such user facing information. This would include API changes to address the new view of the volume type as well as a new API endpoint to set information as key value pairs for this metadata field. A new database table for those metadata is also necessary. The downside on this is, it might confuse people, as user facing information would be in two different fields: "propertied" for multiattach, replication_enabled and AZ, but "metadata" for some things like encryption_enabled and backend_replication, etc... It would also not solve the problem, that key-value pairs not meant for scheduling purposes can still be put into the properties/extra_specs and will only lead to Errors in the scheduling process later on. 3. Facing use cases individually: 3.a) Information about whether a volume type creates encrypted volumes or not could be calculated in the API calls for list/show volume types from the presence of an encryption type. The information would be shown in the "properties" field. This would be a very minimal patch, but will not solve other use cases, that would benefit from user facing information. 3.b) Creating an extra field for the encryption in the volume type table, that is automatically set when creating or deleting an encryption type. This would need a database change and a change of the view of the volume_types. 3.c) Looking into the different drivers and how they handle internal configurable replication and whether there are ways to let OpenStack know this and propagate it to users. This is very hard to achieve, maybe even impossible without input from an operator, who configured the backends and volume types. ----- If you have any other options in mind or want to state your opinion on this, please let me know. greetings Josephine (Luzi)

2 2

Reg cinder because Iscsi and TGT giving problems
by Rohit Sansiya 16 Feb '24

16 Feb '24

Hello all, i want a new cinder because iscsi and tgt giving some problem. tell me how to configure give some handouts. version: openstack yoga os: ubuntu 20.04 multi -node i m working please help its urgent 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.

1 0

How to enable or disable a hypervisor via openstack python module
by Saeed 16 Feb '24

16 Feb '24

Hello, I use this module to find if any hypervisors are disabled: https://github.com/openstack/openstacksdk I can find and see if any hypervisor is disabled and see the reason, but I didn't find any docs about how to enable (or even disable) a hypervisor. This is my code to find disabled hypervisors: import openstack > regions = ['region1', 'region2', 'region3'] > openstack.enable_logging(debug=False)disabled_hypervisors = [] > for region in regions: > conn = openstack.connect(cloud=region) # clouds.yaml > for server in conn.compute.hypervisors(details=True): > a = server.to_dict() > if a['status'] == 'disabled' and > a['service_details']['disabled_reason'] != None: > disabled_hypervisors.append({'name': a['name'], 'ip': > a['host_ip'], 'disabled_reason': a['service_details']['disabled_reason']}) Regards, Saeed

1 0

OpenStack SAML Integration and Application Cred, CLI usage
by Nazan Cengiz 16 Feb '24

16 Feb '24

Hello I want to do SAML integration in OpenStack keystone. How can SAML integration be done? How can I use Application credential and OpenStack CLI with SAML-OpenStack integration? Environment version openstack:stein keystone: 15.0.1-0ubuntu1~cloud0 keystone federation: SAML Authentication Flows: SAML2.0 WebSSO Apache authentication method: Mellon

1 0

[neutron] qrouter namespace missing in controllers - opensack ussuri
by keshav bareja 16 Feb '24

16 Feb '24

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

2 2

[Kolla][Ironic] Ironic node validation failed
by Jayesh Chaudhari 15 Feb '24

15 Feb '24

Hi All, I am following the below document for implementing Ironic in my Kolla-Ansible Cloud which is on yoga version. https://docs.openstack.org/kolla-ansible/yoga/reference/bare-metal/ironic-g… I can add a baremetal node with this in the "baremetal node list" and make it available. But when I am trying to create a nova server it fails trying to find the host. I tried to troubleshoot and find that "openstack baremetal node validate <nodeid>" command shows 1. bios - Driver ipmi does not support bios (disabled or not implemented) 2. console - Driver ipmi does not support console (disabled or not implemented) 3. deploy - Node failed to validate deploy image info. Some parameters were missing. Missing are ['instance_info.image_source'] 4. inspect - Driver ipmi does not support inspect (disabled or not implemented) 5. raid - Driver ipmi does not support raid (disabled or not implemented) 6. rescue - Driver ipmi does not support rescue (disabled or not implemented) Can you please guide me with documentation for setting these options. Or correct me if I am missing anything. Also above documents show steps to create deploy-vmlinuz and deploy-initrd only. Please guide me for steps creating deploy_kernel and deploy_ramdisk. Thanks, Jayesh

3 4

Encountering a live migration issue on Kolla Ansible Deployment
by khurshidsx＠gmail.com 15 Feb '24

15 Feb '24

Hello all, I recently set up a cluster using Kolla Ansible, but I'm encountering a live migration issue. I would appreciate any advice or insights you can provide. Error Message is rule:create_port_binding is disallowed by policy Neutron server returns request_ids: ['req-dce2d22c-349b-4759-a0f2-8bebbfbb1aee'] Here are some logs: 2024-01-25 04:55:51.599 23 INFO neutron.api.v2.resource [req-a380e1bc-a94b-4935-be0d-76fcc94becc4 req-dce2d22c-349b-4759-a0f2-8bebbfbb1aee 636854b888d7441eafcd21255e1378f1 b07c4b6d7b2241c187ed84f30b163817 - - default default] create failed (client error): Access was denied to this resource. 2024-01-25 04:55:51.601 23 INFO neutron.wsgi [req-a380e1bc-a94b-4935-be0d-76fcc94becc4 req-dce2d22c-349b-4759-a0f2-8bebbfbb1aee 636854b888d7441eafcd21255e1378f1 b07c4b6d7b2241c187ed84f30b163817 - - default default] 192.168.252.254,192.168.252.12 "POST /v2.0/ports/e70fab29-d0cd-4db4-8fbc-a572da1bff64/bindings HTTP/1.1" status: 403 len: 308 time: 0.0207033 Neutron server returns request_ids: ['req-dce2d22c-349b-4759-a0f2-8bebbfbb1aee'] 2024-01-25 04:55:51.815 19 ERROR nova.conductor.manager Neutron server returns request_ids: ['req-dce2d22c-349b-4759-a0f2-8bebbfbb1aee'] 2024-01-25 04:55:51.815 19 ERROR nova.conductor.manager Neutron server returns request_ids: ['req-dce2d22c-349b-4759-a0f2-8bebbfbb1aee'] Neutron server returns request_ids: ['req-dce2d22c-349b-4759-a0f2-8bebbfbb1aee']: nova.exception.Forbidden: rule:create_port_binding is disallowed by policy

3 5

The issue of not being able to create application credentials with federated users
by Nazan Cengiz 15 Feb '24

15 Feb '24

Hello, I implemented Cyberark integration in OpenStack. I used the SAML protocol during the integration. I created user groups in Active Directory and defined these groups in Openstack. I added users to the created groups. My goal is to send requests to the OpenStack API by creating application credentials. However, the federated user added to the groups created as a result of the Cyberark integration cannot create and use application credentials. It gives the following error: Unable to create application credential. Inventory openstack:stein keystone: 15.0.1-0ubuntu1~cloud0 Can you help me solve this problem? Thanks

1 0

[cinder] 2024.1 Caracal Midcycle-2 Summary
by Rajat Dhasmana 15 Feb '24

15 Feb '24

Hello Argonauts, Following is the summary of the 2024.1 Caracal Midcycle-2 held on 14th February, 2024. https://wiki.openstack.org/wiki/CinderCaracalMidCycleSummary#Session_Two:_R… Please go through the discussion points and action items assigned to you and let me know if any modification is required. Thanks Rajat Dhasmana

1 0

[elections][tc] Self-nomination for a TC seat
by Sylvain Bauza 15 Feb '24

15 Feb '24

Howdy folks, That's now been a long time I'm thinking about running for a TC seat but I never really thought about it until today. Now, I think this is the best time for me asking you to accept me as a TC member and I'll explain why below. First, in case you don't know me yet, I'm Sylvain Bauza (bauzas on IRC), working on OpenStack since... wow, 11 years already ? I first started to test OpenStack Diablo and Essex for a SME company but eventually moved to another (and then another) position and became contributor, first to the Blazar (that time named Climate) project and then Nova for 10 years now, eventually becoming nova-core and PTL. Time flies and now I'm still there, happy with what OpenStack became. Of course, it changed. But honestly, I haven't seen more operators using it previously than now, which means that we succeeded as a team to make OpenStack useful for our users. As a Nova PTL for the previous cycles, I know how important it is to get feedback from our operators and how much this is crucial to provide help for them. The last discussions I had with the community led to me think that this motto needs to be addressed as a whole and not only on a per-project basis, hence convincing myself that I should run for a TC seat. As someone evolving from a operations position in a SME company to a core developer working with large cloud deployments, I wish I could help the TC driving some efforts into shortening the feedback loop within the community. I'd also want to help the TC provide some guidance on the new SLURP release cadence model to all the projects so that we could really achieve a skip-release upgrade that would benefit to our operators. There are a couple of other stuff I do really care and I wish to help them. CI gate stability is one of them. Having transient failures close to a milestone is not a good experience for us and we need to really address those failures as top priorities when they occur. We should somehow recognize the very fews who dedicate time on chasing those issues and fixing them, as their contributors are mostly valuable, since not a single code of code can't merge when a gate is down. Maintaining our code is another important aspect to me. Recent experiences on not-so-well-maintained dependencies led us force to evaluate all the options and those decisions aren't easy to make. As someone caring about maintaining our code for stable releases, I wish I could help the TC to correctly identify risks and benefits of breaking changes and evaluate the impact it may have on our feature delivery. Enough talk, I'll end up here, saying that after those 10 years in the community, I'm still enjoying being part of it and how much I do love working with all of you. Cheers, -Sylvain

1 0

nova-compute error
by Rohit Sansiya 15 Feb '24

15 Feb '24

Hii Sir, my all 3 compute nodes are down. and error is shown " 2024-02-15 10:27:36.467 4154697 ERROR oslo.messaging._drivers.impl_rabbit [req-650474a9-f2f3-4e05-ade4-cbedf826d16e - - - - -] Connection failed: timed out (retrying in 5.0 seconds): socket.timeout: timed out" [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.

1 0

[qa][centos] devstack-platform-centos-9 jobs failing
by Martin Kopec 15 Feb '24

15 Feb '24

Hello, centos-9 jobs started failing a week ago for various reasons, most often I see that tempest tests failed with 'No valid host found' https://zuul.openstack.org/builds?job_name=tempest-full-centos-9-stream&job… Any ideas what went wrong with centos? Thanks, -- Martin Kopec Principal Software Quality Engineer Red Hat EMEA IM: kopecmartin

4 3

Cinder-volume
by Rohit Sansiya 15 Feb '24

15 Feb '24

Hi sir, I am unable to attach and detach the volume through gui, When I tried so it was stuck and error shows that it is unable to attach or detach. help me how to attach and detach through gui. but I can attach and detach through cmd. 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.

3 3

Can't see Orchestration menu from left side in the Horizon to build VDI
by Artemio Mendoza 15 Feb '24

15 Feb '24

Hello, I'm a bit new in OpenStack but really interested and wanted to build a VDI management system based on OpenStack. So I started setting up OpenStack on VirtualBox using devstack. I used Ubuntu22.04 jammy and configured local.conf like the attached file. I tried setting up Nova, cinder, neutron, swift, glance, ceph, heat, and ceilometer components. But even though I was able to run the stack.sh command successfully, when I logged in horizon dashboard, I couldn't see the Orchestration menu item from the left side. Here is a link that I referred. https://contactchanaka.medium.com/mastering-openstack-from-installation-to-… Anybody help me please to set up a work environment to see the Orchestration menu item? Also, I would be very appreciative if anyone could share the open source/reference link to develop VDI based on OpenStack. Regards, Artemio

1 0

[all][elections][ptl][tc] Combined PTL/TC 2024.2 cycle Election Season
by Ian Y. Choi 14 Feb '24

14 Feb '24

Election details: https://governance.openstack.org/election/ The nomination period officially begins Feb 14, 2024 23:45 UTC. Please read the stipulations and timelines for candidates and electorate contained in these governance documents[1][2][3]. Due to circumstances of timing, PTL and TC elections for the coming cycle will run concurrently; deadlines for their nomination and voting activities are synchronized but will still use separate ballots. Please note, if only one candidate is nominated as PTL for a project team during the PTL nomination period, that candidate will win by acclaim, and there will be no poll. There will only be a poll if there is more than one candidate stepping forward for a project team's PTL position. Similarly, there will only be a TC poll if there are more than 5 candidates stepping forward the available TC positions. All members of the community are encouraged to confirm their email address as described at: https://governance.openstack.org/election/#electorate There will be further announcements posted to the mailing list as action is required from the electorate or candidates. This email is for information purposes only. If you have any questions which you feel affect others please reply to this email thread. If you have any questions that you wish to discuss in private please email any of the election officials[4] so that we may address your concerns. Thank you, /Ian [1] https://governance.openstack.org/tc/reference/charter.html [2] https://governance.openstack.org/tc/reference/role-of-the-tc.html [3] https://docs.openstack.org/project-team-guide/ptl.html [4] https://governance.openstack.org/election/#election-officials

1 0

[Octavia] today's weekly meeting cancelled
by Gregory Thiemonge 14 Feb '24

14 Feb '24

Hi Folks, Unfortunately, I'm not able to join the weekly meeting today, so we have to cancel it. Thanks.

1 0

[cinder] 2024.1 (Caracal) R-7 virtual mid cycle - 2 (14th Feb, 2024)
by Rajat Dhasmana 14 Feb '24

14 Feb '24

Hello Argonauts, We will be conducting the second midcycle of 2024.1 (Caracal) on 14th February, 2024. Following are the details: Date: 14th February, 2024 Time: 1400-1600 UTC Meeting link: https://meet.google.com/cqw-kbpn-sxx Etherpad: https://etherpad.opendev.org/p/cinder-caracal-midcycles We have 1 week so please add your topics timely. Thanks Rajat Dhasmana

1 1

Kolla-Ansible on Ubuntu 22.04 Fluentd Image peesnt for Label Check Error
by KK CHN 14 Feb '24

14 Feb '24

List, 1. I am trying kolla-ansible all-in-one on an Ubuntu VM on Esxi7.0 ( 22.04 Desktop OS. ) 2. Followed https://docs.openstack.org/kolla-ansible/latest/user/quickstart.html *All went well upto here * * 3. Kolla-ansible -i ./all-in-one deploy * fails with message as follows.. Ensure Fluentd Image peesnt for Label Check *vNICs on this Ubuntu VM as follows* 1. "ens192" IP => 10.x.0.128 A DHCP IP of our organization's internal N/W) 2. "ens224 IP => 10.220.0.51 3. Added another interface ens160 without IP ( UP running) in globals.yml I have used 1. "ens224" for network_interface: "ens224" 2. "ens160" for neutron_external_interface: "ens160" 3. an unused 10.220.0.24 ip as kolla_internal_vip_address: "10.220.0.24" Hope I am right doing the interface configurations in globals.yml ? correct me if I am wrong. All went well up to * pre checks .*. *1. (kolla_ansible_venv) ubuntu@ubuntu-VM:~$ kolla-ansible -i ./all-in-one bootstrap-servers* Bootstrapping servers : ansible-playbook -e @/etc/kolla/globals.yml -e @/etc/kolla/passwords.yml -e CONFIG_DIR=/etc/kolla -e kolla_action=bootstrap-servers /home/ubuntu/ PLAY RECAP ************************************************************ ********* localhost : ok=30 changed=2 unreachable=0 failed=0 skipped=24 rescued=0 ignored=0 2. (kolla_ansible_venv) ubuntu@ubuntu-VM:~$ kolla-ansible -i ./all-in-one prechecks PLAY RECAP ************************************************************ ********* localhost : ok=99 changed=0 unreachable=0 failed=0 skipped=158 rescued=0 ignored=0 *But * * 3. Kolla-ansible -i ./all-in-one deploy * fails with message as follows.. Ensure Fluentd Image peesnt for Label Check (kolla_ansible_venv) ubuntu@ubuntu-VM:~$ kolla-ansible -i ./all-in-one deploy TASK [common : Ensure fluentd image is present for label check] **************** fatal: [localhost]: FAILED! => {"changed": true, "msg": "'Traceback (most recent call last):\\n File \"/usr/local/lib/python3.10/dist-packages/docker/api/cli PLAY RECAP ********************************************************************* localhost : ok=6 changed=0 unreachable=0 failed=1 skipped=4 rescued=0 ignored=0 What went wrong? Any hints are much appreciated !!!! Full Error Report: Fatal: [localhost]: FAILED! => {"changed": true, "msg": "'Traceback (most recent call last):\\n File \"/usr/local/lib/python3.10/dist-packages/docker/api/client.py\", line 268, in _raise_for_status\\n response.raise_for_status()\\n File \"/usr/local/lib/python3.10/dist-packages/requests/models.py\", line 1021, in raise_for_status\\n raise HTTPError(http_error_msg, response=self)\\nrequests.exceptions.HTTPError: 404 Client Error: Not Found for url: http+docker://localhost/v1.44/images/create?tag=master-ubuntu-jammy-aarch64&fromImage= quay.io%2Fopenstack.kolla%2Ffluentd\\n\\nThe above exception was the direct cause of the following exception:\\n\\nTraceback (most recent call last):\\n File \"/tmp/ansible_kolla_container_payload_fnpt9ldm/ansible_kolla_container_payload.zip/ansible/modules/kolla_container.py\", line 425, in main\\n File \"/tmp/ansible_kolla_container_payload_fnpt9ldm/ansible_kolla_container_payload.zip/ansible/module_utils/kolla_docker_worker.py\", line 522, in ensure_image\\n self.pull_image()\\n File \"/tmp/ansible_kolla_container_payload_fnpt9ldm/ansible_kolla_container_payload.zip/ansible/module_utils/kolla_docker_worker.py\", line 209, in pull_image\\n json.loads(line.strip().decode(\\'utf-8\\')) for line in self.dc.pull(\\n File \"/usr/local/lib/python3.10/dist-packages/docker/api/image.py\", line 429, in pull\\n self._raise_for_status(response)\\n File \"/usr/local/lib/python3.10/dist-packages/docker/api/client.py\", line 270, in _raise_for_status\\n raise create_api_error_from_http_exception(e) from e\\n File \"/usr/local/lib/python3.10/dist-packages/docker/errors.py\", line 39, in create_api_error_from_http_exception\\n raise cls(e, response=response, explanation=explanation) from e\\ndocker.errors.NotFound: 404 Client Error for http+docker://localhost/v1.44/images/create?tag=master-ubuntu-jammy-aarch64&fromImage= quay.io%2Fopenstack.kolla%2Ffluentd: Not Found (\"manifest for quay.io/openstack.kolla/fluentd:master-ubuntu-jammy-aarch64 not found: manifest unknown: manifest unknown\")\\n'"} While installing kolla I have executed this as in the doc. pip install git+https://opendev.org/openstack/kolla-ansible@master Is the error above related to this step ?? If so what the solution ?/ More details as follows.. globals.yml parameters enabled ubuntu@ubuntu-VM:~$ grep ^[^#] /etc/kolla/globals.yml --- workaround_ansible_issue_8743: yes kolla_base_distro: "ubuntu" openstack_tag_suffix: "-aarch64" kolla_internal_vip_address: "10.220.0.24" network_interface: "ens224" neutron_external_interface: "ens160" ubuntu@ubuntu-VM:~$ VM details *ubuntu@ubuntu-VM:~$ cat /etc/lsb-release* DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04.3 LTS" *ubuntu@ubuntu-VM:~$ cat /etc/hosts* 127.0.0.1 localhost 10.220.0.51 localhost # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters # BEGIN ANSIBLE GENERATED HOSTS 10.220.0.51 ubuntu-VM # END ANSIBLE GENERATED HOSTS *Thanks in advance * *Krishane*

4 3

[tc][releases][ptl][all] you don't need your own unmaintained-core group!
by Brian Rosmaita 14 Feb '24

14 Feb '24

Hello Stackers, Thank you for your help in transitioning the Yoga series to Unmaintained status. We want to stress that there is a global openstack-unmaintained-core team that, by default, has merge permissions on *all* branches in the unmaintained/* namespace. Therefore, you do *not* need to create a specific core group for your project's unmaintained branches. The aim of Unmaintained status is to free up project teams from worrying about the maintenance of old branches. Thus, by design, project core teams do not have merge powers on these branches. Instead, the merry group of stalwart volunteers who have an interest in keeping legacy branches open have taken on this responsibility. If you are interested in helping to keep Unmaintained branches alive, reach out to the openstack-unmaintained-core team members [0] and let them know your interest. They will also be following up with an email, sometime this week, outlining how to join them. To summarize: you should only create your own separate group if you want to maintain the unmaintained branches yourself and don't want the larger group to do it for you. Otherwise you have no such obligation. If you are interested in helping with the unmaintained branches, it will help the community more if you join the global team instead creating your own. Finally, anyone can propose patches to an unmaintained branch, and can +1 or -1 reviews, just like for any other branch. So there's plenty you can do even without being part of an unmaintained-core team. Thanks for your attention to this email! [0] https://review.opendev.org/admin/groups/4d728691952c04b8b2ec828eabc96b98dc1…

1 0

[nova][nova-novncproxy] handler exception: Origin header protocol does not match this host.
by Satish Patel 13 Feb '24

13 Feb '24

Folks, Life was good till I restarted nova-novncproxy services on all controller nodes after that my vnc console stopped working. I can directly connect to the vm console using vnc viewer but not from Horizon. This is not a new setup or something. What could be wrong here and how do I debug this protocol issue? This is what I have on controller nodes [vnc] novncproxy_host = 192.168.8.14 novncproxy_port = 6080 server_listen = 192.168.8.14 server_proxyclient_address = 192.168.8.14 This is what I have on all computes nodes [vnc] novncproxy_host = 192.168.8.18 novncproxy_port = 6080 server_listen = 192.168.8.18 server_proxyclient_address = 192.168.8.18 novncproxy_base_url = https://os2.example.com:6080/vnc_lite.html 2024-02-13 20:08:16.315 7 INFO nova.console.websocketproxy [-] In exit 2024-02-13 20:08:30.402 7 INFO nova.console.websocketproxy [-] WebSocket server settings: 2024-02-13 20:08:30.403 7 INFO nova.console.websocketproxy [-] - Listen on 192.168.8.14:6080 2024-02-13 20:08:30.403 7 INFO nova.console.websocketproxy [-] - Web server (no directory listings). Web root: /usr/share/novnc 2024-02-13 20:08:30.404 7 INFO nova.console.websocketproxy [-] - No SSL/TLS support (no cert file) 2024-02-13 20:08:30.404 7 INFO nova.console.websocketproxy [-] - proxying from 192.168.8.14:6080 to None:None 2024-02-13 20:08:42.800 7 DEBUG nova.console.websocketproxy [-] 192.168.8.15: new handler Process vmsg /var/lib/kolla/venv/lib/python3.10/site-packages/websockify/websockifyserver.py:605 2024-02-13 20:08:42.810 71 INFO nova.console.websocketproxy [-] 192.168.8.15 - - [13/Feb/2024 20:08:42] 192.168.8.15: Plain non-SSL (ws://) WebSocket connection 2024-02-13 20:08:42.810 71 INFO nova.console.websocketproxy [-] 192.168.8.15 - - [13/Feb/2024 20:08:42] 192.168.8.15: Path: '/?token=03ad44a0-b876-4725-a71f-d383c15efb63' 2024-02-13 20:08:42.832 71 DEBUG oslo_db.sqlalchemy.engines [None req-dc3e111c-7a79-4d56-8077-688c9e813700 - - - - - -] MySQL server mode set to STRICT_TRANS_TABLES,STRICT_ALL_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,TRADITIONAL,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION _check_effective_sql_mode /var/lib/kolla/venv/lib/python3.10/site-packages/oslo_db/sqlalchemy/engines.py:335 2024-02-13 20:08:42.923 71 DEBUG nova.objects.console_auth_token [None req-dc3e111c-7a79-4d56-8077-688c9e813700 - - - - - -] Validated token - console connection is ConsoleAuthToken(access_url_base='https://os2.example.com:6080/vnc_lite.html',console_type='novnc',created_at=2024-02-13T20:08:41Z,host='192.168.8.18',id=3993,instance_uuid=7b6e0c71-ea3c-4314-9a4c-1fc86d5680f2,internal_access_path=None,port=5920,token='***',updated_at=None) validate /var/lib/kolla/venv/lib/python3.10/site-packages/nova/objects/console_auth_token.py:153 2024-02-13 20:08:42.961 71 DEBUG oslo_concurrency.lockutils [None req-dc3e111c-7a79-4d56-8077-688c9e813700 - - - - - -] Acquiring lock "compute-rpcapi-router" lock /var/lib/kolla/venv/lib/python3.10/site-packages/oslo_concurrency/lockutils.py:312 2024-02-13 20:08:42.961 71 DEBUG oslo_concurrency.lockutils [None req-dc3e111c-7a79-4d56-8077-688c9e813700 - - - - - -] Acquired lock "compute-rpcapi-router" lock /var/lib/kolla/venv/lib/python3.10/site-packages/oslo_concurrency/lockutils.py:315 2024-02-13 20:08:42.967 71 INFO nova.compute.rpcapi [None req-dc3e111c-7a79-4d56-8077-688c9e813700 - - - - - -] Automatically selected compute RPC version 6.2 from minimum service version 66 2024-02-13 20:08:42.968 71 DEBUG oslo_concurrency.lockutils [None req-dc3e111c-7a79-4d56-8077-688c9e813700 - - - - - -] Releasing lock "compute-rpcapi-router" lock /var/lib/kolla/venv/lib/python3.10/site-packages/oslo_concurrency/lockutils.py:333 2024-02-13 20:08:43.008 71 INFO nova.console.websocketproxy [None req-dc3e111c-7a79-4d56-8077-688c9e813700 - - - - - -] handler exception: Origin header protocol does not match this host. 2024-02-13 20:08:43.008 71 DEBUG nova.console.websocketproxy [None req-dc3e111c-7a79-4d56-8077-688c9e813700 - - - - - -] exception vmsg /var/lib/kolla/venv/lib/python3.10/site-packages/websockify/websockifyserver.py:605 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy Traceback (most recent call last): 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy File "/var/lib/kolla/venv/lib/python3.10/site-packages/websockify/websockifyserver.py", line 662, in top_new_client 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy client = self.do_handshake(startsock, address) 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy File "/var/lib/kolla/venv/lib/python3.10/site-packages/websockify/websockifyserver.py", line 590, in do_handshake 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy self.RequestHandlerClass(retsock, address, self) 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy File "/var/lib/kolla/venv/lib/python3.10/site-packages/nova/console/websocketproxy.py", line 93, in __init__ 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy websockify.ProxyRequestHandler.__init__(self, *args, **kwargs) 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy File "/var/lib/kolla/venv/lib/python3.10/site-packages/websockify/websockifyserver.py", line 87, in __init__ 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy super().__init__(req, addr, server) 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy File "/usr/lib/python3.10/http/server.py", line 668, in __init__ 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy super().__init__(*args, **kwargs) 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy File "/usr/lib/python3.10/socketserver.py", line 747, in __init__ 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy self.handle() 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy File "/var/lib/kolla/venv/lib/python3.10/site-packages/websockify/websockifyserver.py", line 297, in handle 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy super().handle() 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy File "/usr/lib/python3.10/http/server.py", line 433, in handle 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy self.handle_one_request() 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy File "/var/lib/kolla/venv/lib/python3.10/site-packages/websockify/websocketserver.py", line 40, in handle_one_request 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy super().handle_one_request() 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy File "/usr/lib/python3.10/http/server.py", line 421, in handle_one_request 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy method() 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy File "/var/lib/kolla/venv/lib/python3.10/site-packages/websockify/websocketserver.py", line 50, in _websocket_do_GET 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy self.handle_upgrade() 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy File "/var/lib/kolla/venv/lib/python3.10/site-packages/websockify/websockifyserver.py", line 203, in handle_upgrade 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy super().handle_upgrade() 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy File "/var/lib/kolla/venv/lib/python3.10/site-packages/websockify/websocketserver.py", line 77, in handle_upgrade 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy self.handle_websocket() 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy File "/var/lib/kolla/venv/lib/python3.10/site-packages/websockify/websockifyserver.py", line 241, in handle_websocket 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy self.new_websocket_client() 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy File "/var/lib/kolla/venv/lib/python3.10/site-packages/nova/console/websocketproxy.py", line 215, in new_websocket_client 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy raise exception.ValidationError(detail=detail) 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy nova.exception.ValidationError: Origin header protocol does not match this host. 2024-02-13 20:08:43.008 71 ERROR nova.console.websocketproxy

1 0

[openstack-helm] Ceph-osd + Jammy + loop device is broken now
by Vladimir Kozhukalov 13 Feb '24

13 Feb '24

Hi team, Due to this [1] some of our test jobs which utilize the ceph-osd chart and which run on Ubuntu Jammy are broken now. Recent changes in ioctl are incompatible with parted when used with loop devices. Ceph-osd chart uses parted in the osd init script. So it does not work now with the error like this ``` Error: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64 on /dev/loop100 have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should reboot now before making further changes. ``` The issue appears only on Ubuntu Jammy. My suggestion is to temporarily disable the 2023.2 TLS job which is broken now. And to use the 2023.1 TLS job on Focal. Please review https://review.opendev.org/c/openstack/openstack-helm/+/908947 [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049689 -- Best regards, Kozhukalov Vladimir

1 0

[openstack-ansible] Bug fighting day
by Dmitriy Rabotyagov 13 Feb '24

13 Feb '24

Hey everyone. During the previous meeting we decided that it might be a good idea to take a couple hours together to work on the project bug tracker [1]. We are going to focus on closing irrelevant bugs that were issued towards EOLed releases and do not apply to any supported code or were already fixed. Along with that we will try to triage and prioritize ones that are still relevant and need some attention. In order to decide on the date/time when this activity will take place I have created a poll [2]. It will be open till Sunday, Feb 11. Everyone who is willing to help us is very welcome to join the poll. If you have an outstanding bug that somehow slipped our attention - this is really a good chance to bring it up to the team as well. [1] https://bugs.launchpad.net/openstack-ansible [2] https://doodle.com/meeting/organize/id/enGV50Wa

1 2

http://apps.openstack.org/#tab=murano-apps unavailable
by Karera Tony 13 Feb '24

13 Feb '24

I have deployed Murano in my environment, However when I tried to get the application budle following the Murano guide from http://apps.openstack.org/#tab=murano-apps. I realized that the site is down. Is there an alternative ? Regards Regards Tony Karera

2 1

[nova]: openstack-ansible Ussuri - rabbitmq connection distribution
by keshav bareja 13 Feb '24

13 Feb '24

2 1

[magnum] Weekly meeting (14/Feb/2024) cancelled
by Michał Nasiadka 13 Feb '24

13 Feb '24

Hello, Due to absence of key team members - the weekly meeting tomorrow (14/Feb/2024) is cancelled. See you next week! Best regards, Michal

1 0

[all][tc] OpenStack 2024.2 testing runtime
by Ghanshyam Mann 13 Feb '24

13 Feb '24

Hi All, Its time to deifne the testing runtime for next cycle 2024.2. I have proposed it in gerrit, feel free to review/feedback there. - https://review.opendev.org/c/openstack/governance/+/908862 Changes from previous cycle testing runtime for quick ref: * Removing python 3.8 support because it is EOLing in oct 2024[1] which means python 3.9 will be the minimum python version in testing runtime. * Remove Debian 11 from Additional testing support because 2024.2 is non-SLURP release and previous SLURP release 2024.1 supported Debian 12 also which is what can be used as smooth upgrade to future SLURP release 2025.1 * Removing Nodejs from runtime: Nodejs is not a runtime requirement for Horizon instead it is one of the test dependency. It does not fit as a runtime and can be handle by Horizon team based. Added Horizon team to review this change. -gmann

1 0

[neutron][vpnaas][ovn] Pushing VPNaaS support through OVN
by Mohammed Naser 12 Feb '24

12 Feb '24

Hi all! One of the biggest show stoppers for us for OVN is VPNaaS but I think it’s time that we’d like to be involved in getting it over the line, I want to thank Bodo who has shown a lot of patience in getting the code necessary, and it seems that the code works for them in production as well. I’d like to ask if possible for folks to review these two outstanding changes: https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/847007 https://review.opendev.org/c/openstack/neutron-vpnaas/+/765353 I know Slawek had some concerns, so hoping that raising via the email list if Bodo can address those and over the next bit of time we can get this landed in, since it even has actual proper testing both in CI and with user feedback. Thanks! Mohammed

6 8

[neutron] Bugs deputy report February 5th to 11th
by Rodolfo Alonso Hernandez 12 Feb '24

12 Feb '24

Hello all: This is the bug list from the past week: Critical ======================== https://bugs.launchpad.net/neutron/+bug/2052509. "[CI][ovs/ovn sqlalchemy master] jobs broken with Exception: Not enough arguments given". Assigned. Patch: https://review.opendev.org/c/openstack/devstack/+/908572 https://bugs.launchpad.net/neutron/+bug/2052787. "SSH timeouts due to problems with metadata server in ML2/OVN backend". Assigned. High ======================== https://bugs.launchpad.net/neutron/+bug/2052628. "[stable-only][ovn-octavia-provider] Multiple listener-pool-member on IPv6 LB getting second pool in ERROR". Assigned. Patch: https://review.opendev.org/q/I37e660d5eaa45deb38ff127cf69195b0a9ef0846 (merged). Medium ======================== https://bugs.launchpad.net/neutron/+bug/2052484. "[DEFAULT] rpc_worker=0 leaves one rpc worker". Assigned. Patch: https://review.opendev.org/c/openstack/neutron/+/908173 https://bugs.launchpad.net/neutron/+bug/2052681. " Many stale neutron-keepalived-state-change processes left after upgrade to native pyroute2 state-change". Not assigned. https://bugs.launchpad.net/neutron/+bug/2052821. "[OVN] Pin a Logical_Router to a chassis when the external network is tunnelled". Assigned. https://bugs.launchpad.net/neutron/+bug/2052843. "[OVN Octavia Provider] subnet with multiple router gateways lb association". Assigned. Patch: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/908679 https://bugs.launchpad.net/neutron/+bug/2052419. "SG list retrieval is slow because we are always loading "synthetic_fields"". Assigned. Patches: https://review.opendev.org/q/I300464472f2348d148f2a3ddac384c883d9d815b Low ======================== https://bugs.launchpad.net/neutron/+bug/2052508. " [doc][troubleshooting] how to enable ovs vswitchd debug logs". Not assigned. https://bugs.launchpad.net/neutron/+bug/2052786. " Add "socket" to NUMA affinity policy". Assigned. Patch: https://review.opendev.org/c/openstack/neutron-lib/+/903531 Regards.

1 0

PTG April 2024 Team Signup Deadline Approaching!
by Kendall Nelson 12 Feb '24

12 Feb '24

Hello Everyone, This is your *last call *to sign up your team up for the next Project Teams Gathering (PTG)[1], which will be held from Monday, April 8 to Friday, April 12 2024! If you haven't already done so and your team is interested in participating, *you need to complete the survey[2] by February 18, 2024 at 7:00 UTC*. Thanks! -Kendall Nelson (diablo_rojo) [1] PTG Site: https://openinfra.dev/ptg/ [2] Team Survey: https://openinfrafoundation.formstack.com/forms/april2024_ptg_survey

1 0

[openstack-ansible] [kolla-ansible] 2023.1 Antelope - In series upgrade - All/few neutron agents dead
by Shrishail K 11 Feb '24

11 Feb '24

Hi Team, I would like to seek some help regarding the issue I am facing while performing in series upgrade on the Antelope version. We have currently deployed our cluster with *2023.1 Antelope *version. The cluster was deployed on a clean environment by cleaning up any previous kolla openstack installation. We have not observed any issues with this environment so far. For a feature I am working on, I had to *put a patch into GLANCE image* and rebuild all *kolla images with a new tag*. I have attempted to upgrade the cluster using both *kolla-deploy *and *kolla-upgrade *methods, but both methods have left the *cluster in degraded condition*. The issue seems to be mainly with failure of communication between *neutron-server *and all/some *neutron-agents, *due to which the neutron-server sees *all/some* *neutron-agents dead*. *Rabbitmq *itself seems to be doing fine. The issue is very consistent. Is this a known behavior? And am I using the correct kolla tools to perform the in series upgrade. Appreciate any help. Thanks, Shrishail

1 0

OpenSUSE packages
by Kai Jellinghaus 11 Feb '24

11 Feb '24

Hello, I hope it's OK to ask a question like this here, not totally sure how else to reach someone knowledgeable from the community. I'm playing with OpenStack on OpenSUSE, but I'm a bit confused where to get the latest packages. From what I can tell 2023.2 is the latest (non-dev) version, sometimes also called "Bobcat", but the website only lists it as 2023.2, so I'm guessing codenames have been discontinued? This page: https://docs.openstack.org/install-guide/environment-packages-obs.html only goes up to Ussuri Browsing OBS I can find builds & repos for > Ussuri, but it seems builds are largely broken. I'd appreciate any help here, I'm not that experienced with OpenStack, OpenSUSE or mailinglists, so I hope I'm not doing/asking for something stupid. Please do point it out if I do, thank you! Kind Regards, Kai Jellinghaus

2 2

haproxy running configuration change openstack-ansible (ussuri)
by keshav bareja 10 Feb '24

10 Feb '24

Hi All I need to change haproxy configuration in the openstack-ussuri environment using openstack-ansible. for glance-api service I need to change backend load-balancing algorithm from source to least-connect I can see this configuration as part of group_vars of the source package* /opt/openstack-ansible <https://opendev.org/openstack/openstack-ansible/src/commit/6520d0bb2c689ed7…>/inventory <https://opendev.org/openstack/openstack-ansible/src/commit/6520d0bb2c689ed7…>/group_vars <https://opendev.org/openstack/openstack-ansible/src/commit/6520d0bb2c689ed7…>/haproxy <https://opendev.org/openstack/openstack-ansible/src/commit/6520d0bb2c689ed7…>/haproxy.yml* -service: haproxy_service_name: glance_api haproxy_backend_nodes: "{{ groups['glance_api'] | default([]) }}" haproxy_ssl: "{{ haproxy_ssl }}" haproxy_port: 9292 *haproxy_balance_alg: source* haproxy_balance_type: http haproxy_backend_options: Can you please let me know how to do so?

2 3

Re: Welcome to the "openstack-discuss" mailing list
by keshav bareja 10 Feb '24

10 Feb '24

Hi All I need to change haproxy configuration in the openstack-ussuri environment using openstack-ansible. for glance-api service I need to change backend load-balancing algorithm from source to least-connect I can see this configuration as part of group_vars of the source package* /opt/openstack-ansible <https://opendev.org/openstack/openstack-ansible/src/commit/6520d0bb2c689ed7…>/inventory <https://opendev.org/openstack/openstack-ansible/src/commit/6520d0bb2c689ed7…>/group_vars <https://opendev.org/openstack/openstack-ansible/src/commit/6520d0bb2c689ed7…>/haproxy <https://opendev.org/openstack/openstack-ansible/src/commit/6520d0bb2c689ed7…>/haproxy.yml* -service: haproxy_service_name: glance_api haproxy_backend_nodes: "{{ groups['glance_api'] | default([]) }}" haproxy_ssl: "{{ haproxy_ssl }}" haproxy_port: 9292 *haproxy_balance_alg: source* haproxy_balance_type: http haproxy_backend_options: Can you please let me know how to do so? Regards Keshav On Fri, Feb 9, 2024 at 8:27 PM < openstack-discuss-request(a)lists.openstack.org> wrote: > Welcome to the "openstack-discuss" mailing list! > > To post to this list, send your message to: > > openstack-discuss(a)lists.openstack.org > > You can unsubscribe or make adjustments to your options via email by > sending a message to: > > openstack-discuss-request(a)lists.openstack.org > > with the word 'help' in the subject or body (don't include the > quotes), and you will get back a message with instructions. You will > need your password to change your options, but for security purposes, > this password is not included here. If you have forgotten your > password you will need to reset it via the web UI. >

2 1

[release] Release countdown for week R-7
by Thierry Carrez 09 Feb '24

09 Feb '24

Development Focus ----------------- We are entering the last weeks of the 2024.1 Caracal 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 15, 2024. A quick reminder of the upcoming freeze dates. Those vary depending on deliverable type: * Oslo libraries are entering feature freeze next week, February 15, 2024. * General libraries (except client libraries) need to have their last feature release before Non-client library freeze (February 22, 2024). Their stable branches are cut early. * Client libraries (think python-*client libraries) need to have their last feature release before Client library freeze (February 29, 2024) * Deliverables following a cycle-with-rc model (that would be most services) observe a Feature freeze on that same date, February 29, 2024. 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 15, 2024) * Deliverables following cycle-with-intermediary model can release as necessary, but in all cases before Final RC deadline (March 29, 2024) 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 7, 2024). 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 15, 2024 (R-7 week) Oslo feature freeze: February 15, 2024 (R-7 week) Non-client library freeze: February 22, 2024 (R-6 week) Client library freeze: February 29, 2024 (R-5 week) caracal-3 milestone: February 29, 2024 (R-5 week) Cycle highlights deadline: March 7, 2024 (R-4 week) Dalmatian PTG: April 8-12, 2024 -- Thierry Carrez (ttx)

1 0

[Neutron][OVN] Flat routed provider network has external traffic broadcasted to all VMs
by Daniel Failing 09 Feb '24

09 Feb '24

Dear all, I'm currently debugging a (testing) deployment with neutron/OVN, currently most ports in external flat network. So far I'm happy everything can communicate, but we see a strong performance degradation with increasing number of VMs/ports hosted on a hypervisor. The setup is similar to the one described in the routed provider networks docs [1]. For routing between the different segments, we have physical routers, that are not managed by neutron. Debugging the issue showed traffic originating from the DC router to VMs go perfectly as unicast traffic through OVN. Communicating from the VM to other networks via the DC router, however, will broadcast the traffic to all attached ports on the internal bridge. Is there a way to tell neutron/OVN to use a specific MAC address for the router and forward the traffic through the patch port instead of broadcasting it? I could not find any documentation of whether I am missing a neutron port or some other configuration on the hypervisor. Just to make sure: The VM and DC routers have the right ARP information of itself, the traffic that is duplicated is from VM to router/external network. (via default route to router) As far as I could see, this issue does not appear with private networks, since all MAC addresses are known to OVN/Neutron. Versions: Nova/Neutron: Yoga ovs-vswitchd (Open vSwitch) 3.1.4 ovn-northd 22.12.1 kernel 5.14.0-284.30.1.el9_2.x86_64 Best, Daniel [1] https://docs.openstack.org/neutron/latest/admin/config-routed-networks.html

2 4

[manila] multi az replication
by garcetto 09 Feb '24

09 Feb '24

good afternoon, i am using zed, on streched ceph as backend on multiple az. i would like to emulate aws efs multiple nfs mount points for each user tenant (one on each different az) using manila, is it possible? ideally i would like to expose to each users tenant a manila vm as nfs exporter to custormer' instances, and as backend (of manila) use a cinder volume on ceph (rbd? cephfs? nfs?) my problem is how can i create say 3 different manila service vms (one in each az) with different frontend ips all pointing to same rbd/cephfs volume? am i doing wrong? thank you.

2 1

[neutron] Drivers meeting cancelled tomorrow
by Brian Haley 09 Feb '24

09 Feb '24

Hello Neutrinos: Due to the lack of agenda, Friday's drivers meeting is cancelled. Have a nice weekend! -Brian

1 0

[kolla] [Ironic] Is ironic_cleaning_network is tenant network?
by Jayesh Chaudhari 08 Feb '24

08 Feb '24

Hi, I am trying to implement Ironic in my kolla-ansible yoga setup. I am following below document https://docs.openstack.org/kolla-ansible/yoga/reference/bare-metal/ironic-g… Here in ironic_cleaning_network and dnsmasq_dhcp_range is from tenant network?

2 1

[manila] share replication still experimental?
by garcetto 08 Feb '24

08 Feb '24

good evening, is still experimental even in zed or later? https://docs.openstack.org/manila/latest/admin/shared-file-systems-share-re… thank you.

2 1

[magnum] Is magnum support region_name in keystone auth config?
by Seongsoo Cho 08 Feb '24

08 Feb '24

Hi magnum team. It seems that a magnum does not support region_name which is in the keystone_auth and keystone_authtoken section in magnum conf. The internal keystone client of keystoneauth1 only uses the lowest UUID of endpoints for keystone url. [1] And also KeystoneClientV3 's get_auth[2] and get_legacy_auth[3] also don't support region_name as an argument. So, My question is how can I make magnum only use the keystone URL written in the config? Best regards Seongsoo Cho [1] https://github.com/openstack/keystoneauth/blob/master/keystoneauth1/access/… [2] https://github.com/openstack/magnum/blob/master/magnum/common/keystone.py#L… [3] https://github.com/openstack/magnum/blob/master/magnum/common/keystone.py#L… -- Seongsoo Cho OpenStack Korea User Group / Community Leader IRC #seongsoocho

2 2

about magnum capi for production
by Nguyễn Hữu Khôi 07 Feb '24

07 Feb '24

Hello guys. Could you share with me some experience about using Magnum CAPI in production? https://github.com/vexxhost/magnum-cluster-api Thank you so much. Nguyen Huu Khoi

6 44

Cinder Bug Report 2024-02-07
by Jon Bernard 07 Feb '24

07 Feb '24

Hello Argonauts, Cinder Bug Meeting Etherpad <https://etherpad.opendev.org/p/cinder-bug-squad-meeting> Undecided - Service cinder-backup failed when Swift with TLS enabled <https://bugs.launchpad.net/cinder/+bug/2051985> - Status: In Progress - hpe xp: wrong copyrights in test scripts <https://bugs.launchpad.net/cinder/+bug/2052409> - Status: In Progress - GRUB menu format error <https://bugs.launchpad.net/cinder/+bug/2052414> - Status: New Thanks, -- Jon

1 0

[cinder][vendors] Third party CI compliance check
by Rajat Dhasmana 07 Feb '24

07 Feb '24

Hello Vendors, This is related to the original discussion on the ML thread[1]. We have noticed that a lot of the drivers don't have their CI reported on a patch in 2024. Based on the last CI report that I checked[2], the number comes out to be 32 though it's not an accurate measure of the inactivity in the project. The following cases are possible: 1. The driver that doesn't have active CI reporting is already marked unsupported 2. The driver is supported but CI is not actively maintained 3. The CI information is not accurate in the wiki page If it's case 2, vendors should look into their CI and fix it else the driver will be marked unsupported in the current or upcoming release. If it's case 3, make sure to have updated CI info in the wiki page. Let's take an example of the HPE driver. The last seen status is shown as: last seen: 2016-08-09 but the driver is actively reporting on patches. The issue here is either: 1. The CI name in the volume driver is not pointing to the correct wiki page[3] 2. The wiki page does not have correct information about CI[4] Vendors should look into updating their CI related information before the midcycle-2, which is going to be held on 14th Feb, 2024 from 1400-1600 UTC[5]. Since we only have the cireport[2] as the source of truth, we will be looking at the vendor drivers that don't have a recent last seen date and start marking them unsupported during the midcycle-2. Any query is welcome on this thread or during the midcycle-2 topic discussion. [1] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [2] http://cinderstats.ivehearditbothways.com/cireport.txt [3] https://opendev.org/openstack/cinder/src/branch/master/cinder/volume/driver… [4] https://wiki.openstack.org/wiki/ThirdPartySystems/HPE_Storage_CI [5] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… Thanks Rajat Dhasmana

3 2

[all] SLURP support survey
by Mark Goddard 07 Feb '24

07 Feb '24

Hi, The Kolla project is planning to support SLURP upgrades [1] in the Caracal release cycle, allowing users to upgrade from Antelope to Caracal. There are two areas in which I'd like to request information from the various project teams. # 1. SLURP support We understand that for various reasons there can be a gap between TC resolutions and implementation across projects. Using some rudimentary grepping through various codebases I found that many projects have added the grenade-skip-level job (or a variation of it) to their CI pipelines, and a few mention SLURP in their release notes. There's little mention of it in documentation at this stage. AFAICT the following projects have SLURP upgrade jobs: Cinder, Glance, Ironic, Manila, Neutron, Nova, Octavia While I could not find a SLURP job in these: Barbican, Bifrost, Blazar, Cloudkitty, Designate, Heat, Horizon, Keystone, Magnum, Placement Question: Does your project explicitly support SLURP upgrades? Do you have or are you planning to add testing and documentation for SLURP upgrades? # 2. Rolling SLURP upgrades The TC resolution [1] states that rolling upgrades are optional for SLURP releases. This could affect the upgrade procedure required in Kolla Ansible. Nova mentions in its Antelope release notes that it supports rolling SLURP upgrades, but I could not find any information from other projects. It would be helpful if this was documented for each project. Question: Does your project support or plan to support rolling upgrades? If changes to the upgrade procedure for SLURP are required, are they documented? Thank you in advance for your responses. Apologies if I have missed any obvious source of information on this. Regards, Mark [1] https://governance.openstack.org/tc/resolutions/20220210-release-cadence-ad…

7 7

[largescale-sig] Next meeting: February 7, 9utc
by Thierry Carrez 07 Feb '24

07 Feb '24

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

2 2

[Kolla][Octavia] worker unable to connect amphora instance
by Jayesh Chaudhari 06 Feb '24

06 Feb '24

Folks, I have set up kolla-ansible yoga openstack and configured Octavia using VLAN. But when I am trying to create a LB, it is stuck in pending create then eventually failed. And in logs I can see octavia-worker unable to connect to amphora instance. Is there any sanity which I can do to check if my implementation is correct ? Or am I missing something? Please advise. My configuration in global.yml enable_octavia: yes octavia_network_interface: "vlan.2140" octavia_auto_configure: yes octavia_amp_flavor: name: "amphora" is_public: yes vcpus: 2 ram: 1024 disk: 5 octavia_amp_security_groups: mgmt-sec-group: name: "lb-mgmt-sec-grp" rules: - protocol: icmp - protocol: tcp src_port: 22 dst_port: 22 octavia_amp_network: name: lb-mgmt-net provider_network_type: vlan provider_segmentation_id: 2140 provider_physical_network: physnet1 external: false shared: false subnet: name: lb-mgmt-subnet cidr: "10.145.50.128/26" allocation_pool_start: "10.145.50.135" allocation_pool_end: "10.145.50.190" gateway_ip: "10.145.50.129" enable_dhcp: yes octavia_amp_image_tag" "amphora" octavia_loadbalancer_topology: "SINGLE" Thanks, Jayesh

3 8

[tc] Next Technical Committee Meeting Tomorrow, Feb 3, 1800 UTC
by Jay Faulkner 06 Feb '24

06 Feb '24

Hi all, The next scheduled meeting of the Technical Committee is tomorrow. This meeting will be held primarily in Zoom, with minutes kept in IRC. Interested parties can join at https://us06web dot zoom dot us/j/87108541765?pwd=emlXVXg4QUxrUTlLNDZ2TTllWUM3Zz09 (repair the URL first). The proposed agenda ia: Agenda - Roll call - Follow up on tracked action items - Gate health check - Implementation of Unmaintained branch statuses - 2024.1 TC Tracker - https://etherpad.opendev.org/p/tc-2024.1-tracker - Open Discussion and Reviews

1 1

[openstack-helm] Remove Calico chart
by Vladimir Kozhukalov 06 Feb '24

06 Feb '24

Hi everyone, I would like to suggest removing the calico chart from the openstack-helm-infra repository which does not seem worth it to support any more. Tigera provides great tools for managing Calico deployments (helm chart, operator and even plain kubectl manifest). Also there are plenty of other networking solutions on the market and it looks like users can choose on their own the CNI implementation. There have not been many contributions to this chart for quite some time and we don't use this chart in any test jobs. In the deploy-env role we use the upstream Calico manifest [1]. Having said that, I think that we can remove it immediately even without any depreciation period. Opinions are welcome. [1] https://opendev.org/openstack/openstack-helm-infra/src/branch/master/roles/… -- Best regards, Kozhukalov Vladimir

4 3

Glance image import to AWS S3 fails for files larger than 5GB
by Shrishail K 06 Feb '24

06 Feb '24

Hi Team, I have a use case where I need to replicate images from file store to S3 store. While image creation directly on S3 works fine with large files over 5G. The same fails when attempted via image-import with copy-image method. The failure is due to AWS rejecting a single object upload operation where the object size is over 5GB. What I see from logs is that direct image creation on S3 uses multipart upload when images are large. However, I fail to see the same happening when image import was used to copy an image from file to s3. Is this a known issue? Or Am I missing some configs related to image-import? Openstack version: Antelope Client version: 6.4.0 Thanks, Shrishail

3 14

[puppet] EOL plan of wallaby, xena and yoga
by Takashi Kajinami 06 Feb '24

06 Feb '24

Hello, I'm sending this as an early announcement of my current plan about these old stable branches in Puppet OpenStack project. Because we've not see any interest to backport changes to these stable branches and we have limited capacity to maintain our project, I'd propose transitioning EOL these old stable branches by the following steps. * stable/yoga is transitioned to unmaintained/yoga but we may not work on maintaining it now (which eventually means it's abandoned right after its transition to unmaintained status). We'll move it to EOL at the next cadence, when zed is transitioned to unmaintained). * wallaby and xena will become immediate candidates for EOL so we'll just move the EOL process forward. If you have any concern, then please let me know. We'll formally work on these processes in the release patches. [1] https://docs.openstack.org/project-team-guide/stable-branches.html#unmainta… -- Takashi Kajinami irc: tkajinam github: https://github.com/kajinamit launchpad: https://launchpad.net/~kajinamit

1 0

[puppet] Retiring puppet-qdr
by Takashi Kajinami 06 Feb '24

06 Feb '24

Hello, Let me restore my old proposal[1] about puppet-qdr. # I lost access to my old emails so I'm starting a new thread. In the previous mail I proposed deprecation instead of retirement, because the module has been used by TripleO. However I noticed that TripleO is now under the process of complete retirement[2]. So, I'd like to revise my proposal, and propose retiring the module completely. Please let me know if you have any concern with this module retired. Unless I hear any objections, I'll start the official retirement process. [1] https://lists.openstack.org/pipermail/openstack-discuss/2023-August/034742.… [2] https://review.opendev.org/c/openstack/governance/+/905145 Thank you, Takashi Kajinami irc: tkajinam

2 2

[neutron] Bugs deputy report January 29th to February 4th
by Miguel Lavalle 06 Feb '24

06 Feb '24

Here's this week's bugs deputy report: Critical ====== https://bugs.launchpad.net/neutron/+bug/2051831 [ovn] neutron-ovn-tempest-slow job fail tests relying on FIP. Assignee ralonsoh. Proposed fix: https://review.opendev.org/c/openstack/neutron/+/907312 High ==== https://bugs.launchpad.net/neutron/+bug/2051729 issue dhcp cleaning stale devices process when enable action. Assignee Sahid Orentino. Proposed fix: https://review.opendev.org/c/openstack/neutron/+/907250 https://bugs.launchpad.net/neutron/+bug/2051928 tests - Python 3.12 - TypeError: Object of type _SentinelObject is not JSON serializable. Needs an owner https://bugs.launchpad.net/neutron/+bug/2051935 [OVN] SNAT only happens for subnets directly connected to a router. Owner haleyb Medium ====== https://bugs.launchpad.net/neutron/+bug/2051510 [OVN] Audit the L2/L3 extensions support. Assignee: https://bugs.launchpad.net/neutron/+bug/2051869 OVS agent DHCP extension fail if not set subnet gateway_ip. Assigned to Liu Yulong https://bugs.launchpad.net/neutron/+bug/2052367 neutron-keepalived-state-change run neutron-rootwrap-daemon anyway regardless of config. Assigned to Liu Yulong. Proposed fix https://review.opendev.org/c/openstack/neutron/+/653378 Need follow up: ============ https://bugs.launchpad.net/neutron/+bug/2051863 Race condition during VM creation - could not open network device tapXXX (No such device). Liu Yulong created an associated LP bug for Nova, but might require a follow from us in the future. Incomplete ========= https://bugs.launchpad.net/neutron/+bug/2052299 neutron-tempest-plugin - HaRoutersTest.test_convert_legacy_router Test "ha" Check Error

1 0

[publiccloud-sig] Reminder - next meeting February 7th - 0800 UTC
by Felix Kronlage-Dammers 05 Feb '24

05 Feb '24

Hi everyone, This Wednesday (February 7th) 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 Some of us met at FOSDEM last weekend, so we can share a bit about our discussions and findings there :) See you Wednesday! 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

[storlets] Transition wallaby, xena and yoga to EOL
by Takashi Kajinami 05 Feb '24

05 Feb '24

Hello, As you know, stable/yoga already reached its end of maintenance phase and is now being transitioned to the unmaintained branch. Because we've not seen any attempt to backport changes to it and even older branches, I'd propose retiring yoga and older branches (wallaby and xena) instead of keeping inactive branches. Please let me know if you have any concern. -- Takashi Kajinami irc: tkajinam github: https://github.com/kajinamit launchpad: https://launchpad.net/~kajinamit

1 1

[fwaas][devstack] help configuring dashboard
by garcetto 05 Feb '24

05 Feb '24

good morning, is there some tutorial on how to configure fwaas web dashboard on devstack? thank you.

2 1

[nova] Help with support to SGX
by Winicius Allan 05 Feb '24

05 Feb '24

Hello o/ Anyone already work with Nova to provide VMs with SGX support?

6 7

nova-compute down and no data in log file
by russell.stather＠ignitiongroup.co.za 05 Feb '24

05 Feb '24

nova-compute showing as enabled but down. Log files are not being written to. Service is showing as running. This is a juju installation. Have tried pausing and resuming the nova-compute, and rabbitmq, and nova-cloud-controller.

1 0

[cinder] volume type properties / extra_specs
by Josephine Seifert 05 Feb '24

05 Feb '24

Hi, I was experimenting with the extra_specs of volume types for a project. And while I was able to set and unset properties freely, the volumes created from volume types with random properties could not be created. They always went into Error state. When I removed the properties from the volume type, volumes could be created again. Is it meant to behave like this? So in other words: Are custom properties not allowed for volume types? And if so, why am I allowed to set custom properties? I would expect an Error to happen in the volume type set --property ... process and not when creating a volume. greetings. Josephine (Luzi)

2 2

[oslo] Feature freeze.
by Daniel Bengtsson 04 Feb '24

04 Feb '24

Hi there, Just a friendly reminder that oslo's feature freeze will happen in 2 weeks (R-7 - Feb 12 - Feb 16). To know more about the freeze, we have a policy[1] that discusses it. The main thing is that if you have features you want to get into Oslo libraries this cycle, please make sure they merge by Friday. After that we will need to go through the FFE process and there is no guarantee we can land them. Feel free to ping us on IRC if you need code review. [1] http://specs.openstack.org/openstack/oslo-specs/specs/policy/feature-freeze… -- Daniel Bengtsson Software Engineer

3 2

[all] SQLAlchemy 2.x support in Bobcat
by Thomas Goirand 02 Feb '24

02 Feb '24

Hi, As you may know, and to my great frustration, I'm not the maintainer of SQLAlchemy in Debian, even though OpenStack is the biggest consumer of it. The current maintainer insists that he wants to upload SQLA 2.x in Unstable, potentially breaking all of OpenStack. At the present moment, if I understand correctly, we're not there yet, and Bobcat doesn't have such a support. It would be ok for me, *IF* there are patches available on master, that I could backport to Bobcat and maintain in the debian/patches folder of each project. However, the biggest current annoyance, is that I have no idea where we are at. Are we close to such a support? Is there a list of patches to apply on top of Bobcat that is maintained somewhere? Please enlighten me... :) Cheers, Thomas Goirand (zigo)

5 10

RE: [cinder] Inactive 3rd party CIs
by Roquesalane, Jean-Pierre 02 Feb '24

02 Feb '24

Thanks Takashi for driving this. As far as Dell is concerned, those CIs should be marked as unsupported as they are now EOL. * DellEMC SC CI * DellEMC VNX CI * DellEMC XtremIO CI I'll have the CI team to take a look at the Dell PowerMax CI which is supposed to be active. JP Jean-Pierre Roquesalane SW System Sr Principal Engineer - OpenStack Champion Dell Technologies | Security and Ecosystem Software Mobile +33 6 21 86 79 04<tel:1-613-314-8106> Email : jeanpierre.roquesalane(a)dell.com<mailto:jeanpierre.roquesalane@dell.com> [cid:image001.png@01DA545A.5A50B740] Dell SAS, Si?ge Social 1 rond point Benjamin Franklin 34000 Montpellier. Capital 1,946,545.26 Euros, 351 528 229 RCS Montpellier -APE 4651Z -TVA Intracommunautaire FR 20 351 528 229. SIRET 351 528 229 00088 Vat Number : FR 20351528229 (France) / IT00001709997 (Italy) / ESN0012622G (Spain) Internal Use - Confidential

3 7

OpenStack Service.exe killing the svchost.exe process on Windows Server
by evandro.semedo＠skymail.com.br 01 Feb '24

01 Feb '24

Hi guys, I have a Cloudbase Panel and some windows hosts are shutting down in sometimes randomly, i see in windows dumps the OpenStack Service.exe killing the svchost.exe process on Windows Server. There is a bug or some Known issue? In dump i see the OpenStackService.exe process svchost.exe (ffffa38c`8f501a90 fffff802`819d4b35 : ffffe487`000004f0 ffffe487`7bf4c080 ffffe487`61e5b300 00000000`00000128 : nt!NtTerminateProcess+0xa9) Owning Process ffffe4875d4ab080 Image: OpenStackService.exe Attached Process ffffe48761e5b300 Image: svchost.exe Follow below the dump result: ###||### For analysis of this file, run !analyze -v 14: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* CRITICAL_PROCESS_DIED (ef) A critical system process died Arguments: Arg1: ffffe48761e5b300, Process object or thread object Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died. Arg3: 0000000000000000 Arg4: 0000000000000000 Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.Sec Value: 4 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on WINOPS1 Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.Sec Value: 5 Key : Analysis.Memory.CommitPeak.Mb Value: 88 Key : Analysis.System Value: CreateObject BUGCHECK_CODE: ef BUGCHECK_P1: ffffe48761e5b300 BUGCHECK_P2: 0 BUGCHECK_P3: 0 BUGCHECK_P4: 0 PROCESS_NAME: svchost.exe CRITICAL_PROCESS: svchost.exe ERROR_CODE: (NTSTATUS) 0x7bf4c080 - <Unable to get error code text> BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXPNP: 1 (!blackboxpnp) STACK_TEXT: ffffa38c`8f501938 fffff802`820927e8 : 00000000`000000ef ffffe487`61e5b300 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx ffffa38c`8f501940 fffff802`81fd4a0f : ffffe487`61e5b300 fffff802`818fe82d ffffe487`61e5b300 fffff802`818f2bac : nt!PspCatchCriticalBreak+0x148 ffffa38c`8f5019e0 fffff802`81ec836c : ffffe487`00000000 00000000`00000000 ffffe487`61e5b300 ffffe487`61e5b5d8 : nt!PspTerminateAllThreads+0x10dcab ffffa38c`8f501a50 fffff802`81e69e39 : ffffffff`ffffffff ffffa38c`8f501b80 ffffe487`5d4ab080 fffff802`81dd7e01 : nt!PspTerminateProcess+0xe0 ffffa38c`8f501a90 fffff802`819d4b35 : ffffe487`000004f0 ffffe487`7bf4c080 ffffe487`61e5b300 00000000`00000128 : nt!NtTerminateProcess+0xa9 ffffa38c`8f501b00 00007ffc`eb980174 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25 00000033`b7efad38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!NtTerminateProcess+0x14 SYMBOL_NAME: ntdll!NtTerminateProcess+14 MODULE_NAME: ntdll IMAGE_NAME: ntdll.dll STACK_COMMAND: .thread ; .cxr ; kb BUCKET_ID_FUNC_OFFSET: 14 FAILURE_BUCKET_ID: 0xEF_svchost.exe_BUGCHECK_CRITICAL_PROCESS_7bf4c080_ntdll!NtTerminateProcess OS_VERSION: 10.0.17763.1 BUILDLAB_STR: rs5_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {8930391e-0eee-85dc-14a9-6e289649b678} Followup: MachineOwner --------- 14: kd> !thread [-p] [-t] [Address [Flags]] THREAD ffffe4877bf4c080 Cid 29f8.42a0 Teb: 00000033b7d92000 Win32Thread: 0000000000000000 RUNNING on processor e Not impersonating DeviceMap ffffd10732013240 Owning Process ffffe4875d4ab080 Image: OpenStackService.exe Attached Process ffffe48761e5b300 Image: svchost.exe Wait Start TickCount 9007284 Ticks: 0 Context Switch Count 73 IdealProcessor: 13 UserTime 00:00:00.031 KernelTime 00:00:00.187 Win32 Start Address 0x00007ff7e08b2534 Stack Init ffffa38c8f501c90 Current ffffa38c8f501360 Base ffffa38c8f502000 Limit ffffa38c8f4fc000 Call 0000000000000000 Priority 8 BasePriority 8 PriorityDecrement 0 IoPriority 2 PagePriority 5 Child-SP RetAddr : Args to Child : Call Site ffffa38c`8f501938 fffff802`820927e8 : 00000000`000000ef ffffe487`61e5b300 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx ffffa38c`8f501940 fffff802`81fd4a0f : ffffe487`61e5b300 fffff802`818fe82d ffffe487`61e5b300 fffff802`818f2bac : nt!PspCatchCriticalBreak+0x148 ffffa38c`8f5019e0 fffff802`81ec836c : ffffe487`00000000 00000000`00000000 ffffe487`61e5b300 ffffe487`61e5b5d8 : nt!PspTerminateAllThreads+0x10dcab ffffa38c`8f501a50 fffff802`81e69e39 : ffffffff`ffffffff ffffa38c`8f501b80 ffffe487`5d4ab080 fffff802`81dd7e01 : nt!PspTerminateProcess+0xe0 ffffa38c`8f501a90 fffff802`819d4b35 : ffffe487`000004f0 ffffe487`7bf4c080 ffffe487`61e5b300 00000000`00000128 : nt!NtTerminateProcess+0xa9 ffffa38c`8f501b00 00007ffc`eb980174 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25 (TrapFrame @ ffffa38c`8f501b00) 00000033`b7efad38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!NtTerminateProcess+0x14

1 0

Re: [kolla-ansible][magnum] question
by Oliver Weinmann 01 Feb '24

01 Feb '24

Hi Franck, glad that I was able to help. Sorry I don't know about this one. But a quick google revealed this: https://docs.fedoraproject.org/en-US/fedora-coreos/sysconfig-configure-swap… Looks as if the FCOS image has this enabled somehow. I have updated my blogpost on CAPI in MAGNUM. It is finally working and its way faster to deploy Kubernetes. This will no longer use FCOS images but Ubuntu or FLATCAR. Maybe you want to give it a try: https://www.roksblog.de/openstack-magnum-cluster-api-driver/ Have a nice weekend. Cheers, Oliver Am 05.01.2024 um 17:07 schrieb Franck VEDEL: > Hi Oliver. > Thanks for you help !! > > I took the time to consult the help concerning > Magnum(https://docs.openstack.org/magnum/2023.1/user/) and this > article > (https://www.roksblog.de/deploy-kubernetes-clusters-in-openstack-within-minu…) > > > > I understood a lot of things, even though I'm not a Kubernetes expert. > Everything works as I wanted, except for one detail. > Do you know why we get this type of message (and quite a few minutes > to wait) when creating a node: > Capture d’écran 2024-01-05 à 15.43.04.png > > zram_generator…………. no configuration found. > > This is the last point that I cannot improve. Maybe there's nothing we > can do. > Thank you once again, that’s really very nice. > > > Franck VEDEL > > > > >> Le 3 janv. 2024 à 12:26, Oliver Weinmann <oliver.weinmann(a)me.com> a >> écrit : >> >> Hi Franck, >> >> Great. Glad it works. That is the k8s version and the url where >> magnum will pull the container from. The official docs are quite >> helpful. In the latest Openstack release bobcat there is already some >> support for CAPI. It is not 100% working out of the Box but it looks >> very promising. I have taken my blog post offline since I didn’t >> manage to get it working. But I will look into it again in the next >> couple of days. >> >> Cheers, >> Oliver >> >> Von meinem iPhone gesendet >> >>> Am 03.01.2024 um 12:21 schrieb Franck VEDEL >>> <franck.vedel(a)univ-grenoble-alpes.fr>: >>> >>> Hi Oliver, >>> and thanks a lot for your help. >>> I followed the instructions on the blog and indeed, with [trust] it >>> works. >>> I'm trying to understand everything. what are the parameters for: >>> >>> |--labels kube_tag=v1.21.11-rancher1,hyperkube_prefix=docker.io/rancher/| >>> >>> Thanks in advance >>> >>> Franck >>> >>> >>> >>>> Le 25 déc. 2023 à 19:26, Franck VEDEL >>>> <franck.vedel(a)univ-grenoble-alpes.fr> a écrit : >>>> >>>> Hi Oliver and thanks you for this help. >>>> >>>> I was wrong in my explications. >>>> I had seen this article (roksblog.de ) and I did what it said: >>>> I first tried: >>>> enable_cluster_user_trust = True in globals.yml >>>> It didn't work. >>>> >>>> I then made the modification in /etc/kolla/config/magnum.conf: >>>> cluster_user_trust = True >>>> >>>> Same problem. >>>> >>>> That's why I asked the question. Is this really the way to do it? >>>> If so, I will have to restart the containers (keystone?) >>>> >>>> Franck >>>> >>>> >>>> >>>>> Le 25 déc. 2023 à 18:40, Oliver Weinmann <oliver.weinmann(a)me.com> >>>>> a écrit : >>>>> >>>>> Hi Frank, >>>>> >>>>> According to the official kolla docs the option needs to be in >>>>> globals.yml >>>>> >>>>> Ensure that you understand the consequences before enabling this >>>>> option. In|globals.yml|: >>>>> >>>>> In case this also doesn’t work, you can try: >>>>> >>>>> yoga) [vagrant@seed ~]$ cat /etc/kolla/config/magnum.conf >>>>> [trust] >>>>> cluster_user_trust = True >>>>> >>>>> *www.roksblog.de >>>>> >>>>> Cheers, >>>>> Oliver >>>>> >>>>> Von meinem iPhone gesendet >>>>> >>>>>> Am 25.12.2023 um 18:10 schrieb Franck VEDEL >>>>>> <franck.vedel(a)univ-grenoble-alpes.fr>: >>>>>> >>>>>> enable_cluster_user_trust = True >>>> >>> >

2 2

Keystone LDAP backend: need to change user_id_attribute from CN to SAMAccountName
by Michel Jouvin 01 Feb '24

01 Feb '24

Hi, For historical (and bad) resons, we decided 10 years ago when we created our cloud that the Keystone LDAP backend will use the CN as the user_id_attribute rather than the usual SAMAccountName. Since then it has been a source of various problems with CN changes, accented characters in CN... We'd like to change it to SAMAccountName but there is clearly no easy/supported way of doing it and we are looking for some information on the best way to do it and the risks if somebody has some clues... It should impact ~30 users so not a huge number... What we have in mind is basically: - Change the backend attribute - Import new accounts - Assign the new accounts to the same projects as the ol accounts, with the same role One of the foreseen problemsis that old and new accounts will share the same user_name_attribute, based on SAMAccountName. It is not allowed by openstack if I'm right so for the scenario to work we need to change the user_name_attribute of old accounts to something different (we don't care that the user cannot use the account during the transition peroid as long as it doesn't impact active resources). Is it enough to update it in the database? We'd prefer to keep the old accounts in OpenStack until the end of the transition... Another minor issue is the reassignment of keypairs to the new account. It is poosble to ask the user to reload its public keys but we were wondering it there was a not too risky way of doing it for him/her by updating the DB (I guess there is no API for this). Thanks in advance if you have any thought/information to share. Best regards. Michel

3 5

sqlite vs NULL
by Pete Zaitcev 01 Feb '24

01 Feb '24

Greetings: In short: Should it be possible to select by key that is NULL in our DBs? This is needed for Cinder, review 657543[1]. Tests run on sqlite. Long explanation: The review tinkers with SQL Alchemy's query, so it may be doing it wrong. However, I looked at the queries and this seems to happen. A query for everything finds the NULL entry. The query looks like this: SELECT backups.created_at AS backups_created_at, (... very many AS ...) FROM backups LEFT OUTER JOIN backup_metadata AS backup_metadata_1 ON backup_metadata_1.backup_id = backups.id AND backup_metadata_1.deleted = false WHERE backups.deleted = false AND backups.host = %(host_1)s So, the entry is in the database. However, this one returns everything that matches the arguments, but not the one with key of NULL: SELECT backups.created_at AS backups_created_at, (... very many AS ...) FROM backups LEFT OUTER JOIN backup_metadata AS backup_metadata_1 ON backup_metadata_1.backup_id = backups.id AND backup_metadata_1.deleted = false WHERE backups.deleted = false AND backups.status IN (%(status_1)s, %(status_2)s, %(status_3)s, %(status_4)s, %(status_5)s, %(status_6)s, NULL) AND backups.host = %(host_1)s ORDER BY backups.created_at DESC, backups.id DESC The backup with a NULL status is in the DB, but I cannot get it with objects.BackupList.get_all(ctxt, filters={'status': (None,)}) One other thing: Is there an easy way to make negative query through SQLalchemy? My real task is to find all the backups that are not stable (complete and error), so that I can restart it. Thanks for any suggestions, -- Pete [1] https://review.opendev.org/c/openstack/cinder/+/657543

3 3

Reg Cinder volume is not deleted by using gui
by Rohit Sansiya 01 Feb '24

01 Feb '24

*Dear Sir, *Despite attempts to delete a Cinder volume using the graphical user interface (GUI) in the OpenStack environment, the volume remains undeleted. Additionally, attempts to detach the volume via the GUI are unsuccessful. However, it has been observed that these operations can be successfully performed using command-line interface (CLI) commands. Help me! 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.

1 0