- openstack-discuss - lists.openstack.org

October 2025 PTG Dates & Registration
by Kendall Nelson 04 Jun '25

04 Jun '25

Hello Everyone! The next PTG[1] will take place October 27-31, 2025! Registration is now open[2] and free for all to attend, as per usual. Shortly, I will send along the team sign up to collect groups interested in participating. -- Kendall Nelson *Senior Upstream Developer Advocate* OpenInfra Foundation <https://openinfra.org/> [1] https://openinfra.dev/ptg/ [2] https://ptg.openinfra.org/

1 0

[neutron][ops] pre-created port remains in use after instance is deleted
by Eugen Block 04 Jun '25

04 Jun '25

Hello again, this is version Caracal, recently upgraded from Antelope. We're currently facing an issue with pre-created ports. This used to work just fine for years, now we have to delete the port, recreate it and try again. For example, we launch an instance with a pre-created port, notice that something is wrong and delete the instance. Previously, we could just launch a new instance and use the same port-id, but now we get this error: # openstack server create --image <image> --flavor 1 --port d10298ea-6dd9-40af-af7e-507f4d83a8cf test-port4 Port d10298ea-6dd9-40af-af7e-507f4d83a8cf is still in use. (HTTP 409) (Request-ID: req-e6cef8b4-d8af-4312-852b-d44ec92cf27a) I noticed that the device_id was still pointing to the previous instance, so I tried a couple of things to clear the port state, but to no avail. I tried: - openstack port set --device None d10298ea-6dd9-40af-af7e-507f4d83a8cf - openstack port set --device "" d10298ea-6dd9-40af-af7e-507f4d83a8cf and a couple of more set commands. I also don't see any option for port creation to allow reusing a pre-created port. Am I missing something? Thanks! Eugen

3 7

[Octavia] - Loadbalancer appear offline but are running
by Karl Kloppenborg 04 Jun '25

04 Jun '25

Hi Octavia Team. We’ve been recently running Octavia in our lab and despite load balancers creating and running correctly, status of them always reports offline, see attached screenshot.[cid:47E71115-B565-4330-8878-4E74F1BD57AF] Does anyone have any clues towards this? All the housekeeping and other processes seem to be working fine… Does anyone maybe have more information on how this telemetry is reported? Maybe that might send me down the correct rabbit hole. Thanks, Karl. Karl Kloppenborg Chief Technology Officer m: +61 437 239 565 resetdata.com<https://resetdata.com/> [cid:reset_69557fc2-1d63-4932-b5fd-93bd4f39ca7b.png] ResetData supports Mandatory Client Related Financial Disclosures – Scope 3 Emissions Reporting For more information on the phasing of these requirements for business please visit; https://treasury.gov.au/sites/default/files/2024-01/c2024-466491-policy-sta…<https://treasury.gov.au/sites/default/files/2024-01/c2024-466491-policy-sta…> This email transmission is intended only for the addressee / person responsible for delivery of the message to such person and may contain confidential or privileged information. Confidentiality and legal privilege are not waived or lost by reason of mistaken delivery to you, nor may you use, review, disclose, disseminate or copy any information contained in or attached to it. Whilst this email has been checked for viruses, the sender does not warrant that any attachments are free from viruses or other defects. You assume all liability for any loss, damage or other consequences which may arise from opening or using the attachments. If you received this e-mail in error please delete it and any attachments and kindly notify us by immediately sending an email to contact(a)resetdata.com.au<mailto:contact@resetdata.com.au>

1 0

[neutron] Approach to a spec for OVN BGP integration (RFE 2111276)
by Frode Nordahl 04 Jun '25

04 Jun '25

Hello, Jakub, Thank you for filing the RFE for Neutron support for OVN native support for route exchange, which includes BGP. We appear to have a common goal of making use of this with OpenStack, and we have time set aside this cycle to work towards this goal. Communication through IRC and e-mail often has limited bandwidth, and I wonder if you would be interested in participating in a A/V sync on some cadence to get us off the ground with the initial spec work. We have good experience with how the core OVN A/V sync is organized and we could do something similar for this. WDYT? -- Frode Nordahl

6 9

[cinder]How do I configure Cinder to recognize free space in the data pool when using a Ceph Erasure Coded Pool?
by Yuta Kambe (Fujitsu) 03 Jun '25

03 Jun '25

Hi everyone, I'm using a Ceph Erasure Coded pool as the backend for OpenStack Cinder. I've created a replicated pool (volumes_meta) for metadata and an erasure-coded pool (volumes_data) for data, following the documentation here: https://docs.ceph.com/en/latest/rados/operations/erasure-code/ When I set rbd_pool to volumes_meta in cinder.conf, I receive an "Insufficient free virtual space" error, even though volumes_data has ample free space. This is because Cinder is calculating free space based on the metadata pool. When rbd_pool is set to volumes_data, Cinder correctly calculates free space based on the data pool. However, I then encounter an "RBD operation not supported" error during volume creation. I need Cinder to recognize the free space available in volumes_data while avoiding the "RBD operation not supported" error. I'm unsure how to configure this correctly and would appreciate any advice. The following is supplemental information. cinder.conf is: [ceph] volume_driver = cinder.volume.drivers.rbd.RBDDriver volume_backend_name = ceph rbd_pool = volumes_meta rbd_ceph_conf = /etc/ceph/ceph.conf rbd_flatten_volume_from_snapshot = false rbd_max_clone_depth = 5 rbd_store_chunk_size = 4 rados_connect_timeout = -1 rbd_user = cinder rbd_secret_uuid = <uuid> For example, if the pool usage is as follows, Cinder gets 1.6TiB as the pool free space: $ ceph df --- POOLS --- POOL ID PGS STORED OBJECTS USED %USED MAX AVAIL volumes_meta 4 32 40 KiB 24 189 KiB 0 1.6 TiB volumes_data 7 32 61 GiB 15.67k 92 GiB 2.80 2.1 TiB $ cinder get-pools --detail +-----------------------------+-----------------------------------------------------------------------------------+ | Property | Value | +-----------------------------+-----------------------------------------------------------------------------------+ | allocated_capacity_gb | 523 | | backend_state | up | | driver_version | 1.3.0 | | filter_function | None | | free_capacity_gb | 1592.07 <-★free capacity of volumes_meta | | goodness_function | None | | location_info | ceph:/etc/ceph/ceph.conf:<uuid>:cinder:volumes_meta | | max_over_subscription_ratio | 20.0 | | multiattach | True | | name | <hostname>@ceph#ceph | | qos_support | True | | replication_enabled | False | | reserved_percentage | 0 | | storage_protocol | ceph | | thin_provisioning_support | True | | timestamp | 2025-05-29T07:44:17.903149 | | total_capacity_gb | 1592.07 | | vendor_name | Open Source | | volume_backend_name | ceph | +-----------------------------+-----------------------------------------------------------------------------------+ OpenStack and Ceph versions are: $ ceph -v ceph version 17.2.8 (f817ceb7f187defb1d021d6328fa833eb8e943b3) quincy (stable) $ dnf list --installed | grep openstack-cinder openstack-cinder.noarch 1:21.3.2-1.el9s @centos-openstack-zed

4 4

[kolla] Weekly meeting 04/06/2025 cancelled
by Michał Nasiadka 03 Jun '25

03 Jun '25

Hello Koalas, Due to clashes with other meetings from my side and majority of core reviewers - I’m cancelling the meeting tomorrow. See you next week Michal

1 0

[cyborg][nova][tc] cyborg support for pyproject.toml and failing ci jobs.
by Sean Mooney 03 Jun '25

03 Jun '25

hi everyone, tl;dr can anyone form the cyborg team approve https://review.opendev.org/c/openstack/cyborg/+/949772 As you all are likely aware when we updated the testing runtime for 2025.2 and unfroze the setuptool version by the removal of python 3.9 support setuptools 80 became available in ci. this resulted in any project that still religed on PBRs `wsgi_scripts` extension failing to deploy under devstack if they had note converted to providing a pyproject.toml Stephen finucan and i started trying to prepare openstack for this change 18 months ago but with the release of setup-tools 80 it became much more important given it blocked gates. while there are a lot of patches still in flight for other project https://review.opendev.org/q/topic:%22pip-23.1-support%22 im reaching out specifically related to https://review.opendev.org/c/openstack/cyborg/+/949772 because the cyborg job on the nova repo has been failing for several weeks now. this change should fix the failing jobs on the cyborg repo too but the nova team does still check the status of the non voting job in our check pipeline too. i pushed https://review.opendev.org/c/openstack/cyborg/+/949772 for review 20 days ago and i have a follow up to remove the jammy jobs https://review.opendev.org/c/openstack/cyborg/+/949777/1 to align cyborgs testing to the testing runtime for this release. in general the cyborg repo seam to have a number of bot and procedural patches open for the last few release https://review.opendev.org/q/project:openstack/cyborg+status:open so its not clear if any of the current core team member are active with that said there have been a few patches merged in the last 6 months https://review.opendev.org/q/project:openstack/cyborg+status:merged so the cyborg team does not seam to be entirely inactive currently. if anyone form the cyborg team sees this could you please review those patches to unblock the cyborg gate. if we don't see movent on this after m2 ill probably propose removing the cyborg job form the nova check line since its currently just wasting ci time given it always fails. regard sean. ps note for the cyborg team https://review.opendev.org/c/openstack/cyborg/+/949772 also complete the cyborg part of https://github.com/openstack/governance/blob/master/goals/proposed/migrate-… as that is the general approach we had selected to addressing the packaging issue sand adopting pyporejct.toml was required to make that possible since it was not merged before the setuptool changes.

1 0

[glance] pushing image to all stores upon creation
by Can Özyurt 03 Jun '25

03 Jun '25

Hi everyone, AFAIK the procedure to make an image available in all the stores is: 1) Create an image (on a selected/default store) 2) Import the image with all_stores option I am looking for ways to eliminate the second step and make uploading to all stores the default behaviour. 1) Is there a config for this? 2) If not, can glance plugins/flows be used to implement this behaviour? Both sync and async approaches are fine as long as images created via dashboard are pushed to all stores all well. Looking forward to your guidance. Thanks in advance. Regards, Can

2 6

Wallaby: Password rotation
by Albert Braden 03 Jun '25

03 Jun '25

I've been asked to rotate passwords in our Wallaby clusters. I found this document for zed: https://docs.openstack.org/kolla-ansible/zed/admin/password-rotation.html When I tried it in the lab I ended up with a broken cluster. Is it possible to rotate passwords in Wallaby?

1 0

[publiccloud-sig] Next meeting of Public Cloud SIG - June 4th at 0700 UTC
by Felix Kronlage-Dammers 02 Jun '25

02 Jun '25

Hi everyone, This upcoming Wednesday (June 4th - this is tomorrow :) the next meeting of the publiccloud-sig is going to happen. We’ll be meeting at 0700 UTC here: https://meetpad.opendev.org/publiccloud-sig See also here for all other details: https://wiki.openstack.org/wiki/PublicCloudSIG As I'm participating in the ALASCA Hackathon, I will not be able to join the SIG call myself. Have fun! cheers felix -- Felix Kronlage-Dammers 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

[tc][all] OpenStack Technical Committee Weekly Summary and Meeting Agenda (2025.2/R-17)
by Goutham Pacha Ravi 02 Jun '25

02 Jun '25

Hello Stackers, We're 17 weeks away from the release date for OpenStack 2025.2 "Flamingo" [1]. All projects following the cycle-trailing release model [2] will release their 2025.1 Epoxy deliverables by 2025-06-05, i.e., Thursday this week. The OpenStack Technical Committee is close to merging a resolution to require "Developer Certificate of Origin" [3] sign-offs from committers starting 2025-07-01. This will affect committers across the community. We request that you review what the DCO signifies [4] and how OpenStack governance plans to enforce it [3], and be prepared for the change. You can add "Signed-off-by" in your commit messages today. Project maintainers are requested to encourage this sign off, and spread the word to contributors via review comments and project team meetings. When Git is properly configured with your username and email, commit with the "-s" option to include the sign-off line in the commit message. In the past week, the TC didn't merge any new governance proposals; however, several, including the proposal to transition from the CLA to the DCO, are under review. === Weekly Meeting === Last week's meeting of the OpenStack Technical Committee occurred on 2025-05-27 on OFTC's #openstack-tc channel [5]. We covered a range of topics, including DCO implementation, the OpenInfra User Survey, and gate health. The primary focus was on the transition from CLA (Contributor License Agreement) to DCO. Many tooling changes are under review to facilitate this transition. Discussions also clarified that all new patches after July 1st will require a DCO sign-off, and existing patches can be rebased and signed off in Gerrit. There was a brief discussion about potentially abandoning patches in merge-conflict without a sign-off after July 1st, but the consensus was to instead add a comment to inform contributors about the need for the DCO with the updated patchset. The 2025 OpenInfra User Survey is currently live and will close in August [6]. Foundation staff will collate responses and share them with project leads/liaisons and the OpenStack TC in September. The TC reviewed the existing questions and decided not to make changes to avoid confusing the summarization of responses. There was also an update regarding the 2024 user survey, with clarification that anonymized raw data will be shared with PTLs and the TC, and that an NDA may be required for access. The next meeting of the OpenStack TC is on 2025-06-03. This meeting will be hosted simultaneously over video and IRC. You're welcome to join through any platform that you prefer. The agenda and call details are posted to the meeting's wiki page [7]. I hope that you'll be able to join us. === Governance Proposals === ==== Merged ==== - Fix outdated info on the tc-guide | https://review.opendev.org/c/openstack/governance/+/950446 ==== Open for review ==== - Require declaration of affiliation from TC Candidates | https://review.opendev.org/c/openstack/governance/+/949432 - [resolution] Replace CLA with DCO for all contributions | https://review.opendev.org/c/openstack/governance/+/950463 - Clarify actions when no elections are required | https://review.opendev.org/c/openstack/governance/+/949431 - Add nova-contrib repository | https://review.opendev.org/c/openstack/governance/+/951569 === Upcoming Events === - 2025-06-03: 15 ans d'OpenStack - OpenInfra UG, Paris: https://www.meetup.com/openstack-france/events/307492285 - 2025-06-05: OpenStack 15 ans! - OpenInfra UG, Rennes: https://www.meetup.com/openstack-rennes/events/306903998 - 2025-06-28: OpenInfra+Cloud Native Day, Vietnam: https://www.vietopeninfra.org/void2025 Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] 2025.2 "Flamingo" Release Schedule: https://releases.openstack.org/flamingo/schedule.html [2] "cycle-trailing": https://releases.openstack.org/reference/release_models.html#cycle-trailing [3] TC resolution to replace CLA with DCO for all contributions: https://review.opendev.org/c/openstack/governance/+/950463 [4] Developer Certificate of Origin: https://developercertificate.org/ [5] TC Meeting IRC Log 2025-05-27: https://meetings.opendev.org/meetings/tc/2025/tc.2025-05-27-17.00.html [6] Take the 2025 OpenStack User Survey: https://www.openstack.org/user-survey/survey-2025/ [7] TC Meeting Agenda, 2025-06-03: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

[ops][largescale-sig][scientific-sig] Ops Radio Hour on May 30, 2025
by Ildiko Vancsa 02 Jun '25

02 Jun '25

Hi OpenStack Community, I'm reaching out to you to draw your attention to a new online gathering called Ops Radio Hour. The call series is a casual setting for operators, engineers, and contributors to come together, share knowledge, and collaborate on the complexities of managing and deploying OpenStack environments. The first meeting is scheduled to May 30, 2025 at 1400UTC [1]. The call will happen on Meetpad, and you can find the agenda on the etherpad[2] created for the series. See You there! Best Regards, Ildikó [1] https://wiki.openstack.org/wiki/Operations/Meetups#2025_Ops_Radio_Hour_Seri… [2] https://etherpad.opendev.org/p/openstack_ops_radiohour

2 4

[nova][horizon] VNC console policy
by Eugen Block 02 Jun '25

02 Jun '25

Hi *, I'm a bit confused regarding the policy requirements to grant a user access to the vnc console via horizon dashboard. Since we have 10 years of history in our cloud, I tried to remove legacy stuff, e.g. old policy files and try with the defaults to see what we're missing. I recently upgraded this cloud to Caracal. It seems like currently, only a user with the admin role has access. Searching for some hints, I found the deprecated policies in (everything is commented): /usr/share/openstack-dashboard/openstack_dashboard/conf/nova_policy.yaml And then the defaults here: /usr/share/openstack-dashboard/openstack_dashboard/conf/default_policies/nova.yaml In the code I found two checks for "os_compute_api:os-consoles:show": class ConsoleTab(policy.PolicyTargetMixin, tabs.Tab): name = _("Console") slug = "console" template_name = "project/instances/_detail_console.html" preload = False policy_rules = (("compute", "os_compute_api:os-consoles:show"),) class InstanceDetailTabs(policy.PolicyTargetMixin, tabs.DetailTabsGroup): slug = "instance_details" tabs = (OverviewTab, InterfacesTab, LogTab, ConsoleTab, AuditTab) sticky = True policy_rules = (("compute", "os_compute_api:os-consoles:show"),) from /usr/share/openstack-dashboard/openstack_dashboard/dashboards/project/instances/tabs.py. But I don't find any policy like that in the defaults. So I'm wondering what the current recommendation would be. Should I add only "os_compute_api:os-consoles:show" to /usr/share/openstack-dashboard/openstack_dashboard/conf/default_policies/nova.yaml? I'm not sure if that would override the other defaults (because of one entry only) or if this would be an additional policy (haven't been playing with those for some time now). Could anyone point me to the best approach? Thanks! Eugen

1 0

[Neutron] Bug deputy - summary from week of May 26th
by Sławek Kapłoński 02 Jun '25

02 Jun '25

Hi, I was bug deputy last week and here is short summary: ### Critical None ### High None ### Medium - https://bugs.launchpad.net/neutron/+bug/2111660 - OVN_AGENT_NEUTRON_SB_CFG_KEY doesn't set when Neutron OVN Agent starts - I marked it as Medium but I don't really have env to confirm it currently, - https://bugs.launchpad.net/neutron/+bug/2111908 - [FT] ``test_subport_delete`` fails - fix proposed already by Rodolfo, - https://bugs.launchpad.net/neutron/+bug/2112110 - [ovn-octavia-provider] LoadBalancer member not coming back after disable-enable - fix already proposed by Fernando, ### Low - https://bugs.launchpad.net/neutron/+bug/2112123 - Functional: privsep helper command exited non-zero test_trunk_creation_with_no_subports - opened by Lajos to track failiure with some functional test, ### RFE - https://bugs.launchpad.net/neutron/+bug/2111899 - [RFE] Use stateless NAT rules for FIPs - proposed by Rodolfo - https://bugs.launchpad.net/neutron/+bug/2111891 - IPv6 Subnet-Router anycast address inappropriately used for gateway_ip when specifying --subnet-range - unassigned, - https://bugs.launchpad.net/neutron/+bug/2112297 - [RFE] Support Policy Based Routing for LRs in Neutron OVN driver ### To triage - https://bugs.launchpad.net/openstack-helm/+bug/2112130 - No port found in network None with IP address 169.254.169.254 - Brian already started looking into this, it seems for me that it is more OpenStack Helm issue rather than Neutron so I added Helm project to it too. -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[telemetry] Nominate Jaromír Wysoglad to Telemetry Core
by Juan Larriba 01 Jun '25

01 Jun '25

Hi, One of the things I wanted to do when becoming PTL of telemetry was to revive the interest in the community as I sensed that telemetry had been left a little bit behind from the rest of the projects. Since then, there has been a lot of movement: new Ceilometer features were added and even new projects (aethos, a prometheus-keystone proxy and grian-ui, a new metric displaying dashboard for Horizon) which has showed that the interest in gathering and displaying better and more scalable metrics is only growing. In these circumstances, the very small core contributor team needs to grow to keep up with all the influx of new features coming from the amazing community and I cannot think of anyone better than Jaromír Wysoglad to fulfill that role. Jaromír has been involved in the telemetry upstream community for years, tirelessly working to, among other things, make the whole telemetry suite to be compatible with Prometheus storage. He has implemented Prometheus compatibility with aodh, python-observabilityclient and many other things, including maintaining and improving the telemetry tempest test suite. Recently he created and is writing from scratch aetos, the new openstack-prometheus compatibility layer. I can't see a better contributor to the core group. If I don't hear any objections for one week, I'll add Jaromír to the group. Best Regards, Juan Larriba

3 3

Create image error
by BEDDA Fadhel 31 May '25

31 May '25

Hi everyone, I installed OpenStack (DevStack). At first, I was able to create three images (Ubuntu, Debian, and Windows) in addition to the Cirros image. When I tried to add another image, everything got stuck. I couldn't add any images, and I got the infamous error 550. HttpException: 502: Server Error for url:

2 1

[ops] Matrix room created #openstack-ops:opendev.org
by Jeremy Stanley 30 May '25

30 May '25

Discussion during today's Ops Radio Hour at one point led to talking about real-time/synchronous chat platforms. Consensus seemed to be that it was worth starting a Matrix room on the OpenDev Collaboratory's homeserver for OpenStack Ops discussions, and see how it works out for everyone. Visit https://matrix.to/#/#openstack-ops:opendev.org if you want to check it out. If you're already logged into your Matrix account then the "Continue" button should take you right to the room. If you're not logged in then it should prompt you to pick a client (choose Element and continue in your browser if you don't feel like installing a client right now) and then to sign in or create an account. If you choose to create an account at that point, it painlessly walks you through creating one on matrix.org (though you can join with an account from any other homeserver instead, if you prefer). -- Jeremy Stanley

1 0

Create image
by BEDDA Fadhel 30 May '25

30 May '25

Aidez moi svp HttpException: 502: Server Error for url: http://192.168.30.10/image/v2/images/2440ca4f-7a35-4fd1-88b2-5e4f269ef5d8/f…, 502 Bad Gateway: Bad Gateway: The proxy server received an invalid: response from an upstream server.: Apache/2.4.58 (Ubuntu) Server at 192.168.30.10 Port 80 Cdt

1 0

[ops] ops radio May 30 2025
by Chris Morgan 30 May '25

30 May '25

Hey Folks, Tomorrow the openstack ops meetups team (such as it is) would like to try something different, we're calling it "ops radio" a bit like talk radio. I posted a little about it here https://fosstodon.org/@osopsmeetup/114585889262579171 Time : 14:00 UTC which is 10am here (NYC). Just an hour free-form meeting on openinfra's jitsi so it's quite like just another zoom meeting. The jitsi link and agenda link are here on the ops meetups wiki: https://wiki.openstack.org/wiki/Operations/Meetups The idea is if people like this we could aim to do it regularly since in-person meetups have become much rarer and harder to do and since the community seems to be somewhat distributed across reddit, linkedin, mastodon, irc, mailing lists, bluesky, matrix, slack etc. technical topics will include the usual things like architecture. tools, upgrades, pain points depending on what people who attend want to discuss. Chris -- Chris Morgan <mihalis68(a)gmail.com>

1 1

some operations are available only to the administrator, regardless of the policies?
by sluge＠mail.ru 29 May '25

29 May '25

Hi everyone, I'm currently writing a custom nova's policy for my new role myrole. The current task is to create a role for a user with member role already assigned to see servers from other project. For example, I got a token for my user in project1, but want to see servers on project2, where my user has a member and myrole roles also. I added to nova's policy.json line: "os_compute_api:servers:show": "rule:project_reader_or_admin or role:myrole" I already assigned to my user roles member and myrole in the project1 and project2. But I always got a 404 error when I want to show servers from project2. I get 404 even when I use "os_compute_api:servers:show": "" i.e. always true. It only works if I use token of admin user or my user has admin role in project2. It looks like some operations are available for admins only?

3 3

[openstack-helm][loci] Retire Centos based images
by Vladimir Kozhukalov 28 May '25

28 May '25

Hi team, We have a bunch of Centos related stuff in the Loci repo. However we've not been building and testing centos based images for quite some time. Is anybody still interested in having/maintaining this stuff? I am talking about [1] - [5]. [1] https://opendev.org/openstack/loci/src/branch/master/dockerfiles/centos [2] https://opendev.org/openstack/loci/src/branch/master/scripts/install.sh#L37… [3] https://opendev.org/openstack/loci/src/branch/master/scripts/collect_info.s… [4] https://opendev.org/openstack/loci/src/branch/master/scripts/install_packag… [5] https://opendev.org/openstack/loci/src/branch/master/scripts/cleanup.sh#L14… -- Best regards, Kozhukalov Vladimir

1 1

Re: [neutron] Switching the ML2 driver in-place from linuxbridge to OVN for an existing Cloud
by Ohnsorge Borys 28 May '25

28 May '25

Hi James, I know this topic is old, but have you had the time/opportunity to describe the migration process based on openstack-ansible You mentioned? __ Best regards Borys Ohnsorge

2 1

[largescale-sig] Next meeting: May 28, 15utc
by Thierry Carrez 28 May '25

28 May '25

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

1 1

[openstack-ansible] [Antelope]operating upgrade from ubuntu 20 to ubuntu 22 on infra nodes
by Danish Khan 26 May '25

26 May '25

Dear Team, I am trying to upgrade Operating system of Infra node from ubuntu 20 to ubuntu 22. And I am following below docs for same: https://docs.openstack.org/openstack-ansible/2023.1/admin/upgrades/distribu… When I run: openstack-ansible setup-hosts.yml --limit localhost,reinstalled_host* I thought it would upgrade OS of LXC containers as well. I can see ubuntu-22-amd64 in /var/lib/lxc/ and /var/lib/machines/ I can see ubuntu-22-amd64 even when I run lxc-ls command. Should I destroy and recreate lxc containers one by one to upgrade it to ubuntu 22? or is there any playbook which can take care of this? Regards, Danish Khan

2 1

[OpenStack Kolla] Unable to upload image from Horizon
by ankit1999raikwar＠gmail.com 26 May '25

26 May '25

Hello All, We have deployed the latest version of the OpenStack using the Kolla-ansible deployment. Issue description: When we are uploading image from the horizon dashboard using the with the privilege of admin or any other normal user getting below error. we are using the ceph storage as the backend. Error: Type Error: response is undefined and Unable to create Image Details: 1. From CLI I'm able to Upload the image 2. From Horizon getting Error Command Line Interface openstack image create cirros-01 --disk-format qcow2 --file cirros-0.6.2-x86_64-disk.img Output: +------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Field | Value | +------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | checksum | c8fc807773e5354afe61636071771906 | | container_format | bare | | created_at | 2025-05-26T05:03:04Z | | disk_format | qcow2 | | file | /v2/images/f4bba9a3-8640-4162-b9de-0b7e29d32dcf/file | | id | f4bba9a3-8640-4162-b9de-0b7e29d32dcf | | min_disk | 0 | | min_ram | 0 | | name | cirros-01 | | owner | 302edafdf0114b41acad32725668cd13 | | properties | os_hash_algo='sha512', | | | os_hash_value='1103b92ce8ad966e41235a4de260deb791ff571670c0342666c8582fbb9caefe6af07ebb11d34f44f8414b609b29c1bdf1d72ffa6faa39c88e8721d09847952b', | | | os_hidden='False', owner_specified.openstack.md5='', owner_specified.openstack.object='images/cirros-01', owner_specified.openstack.sha256='', stores='rbd' | | protected | False | | schema | /v2/schemas/image | | size | 21430272 | | status | active | | tags | | | updated_at | 2025-05-26T05:03:05Z | | virtual_size | 117440512 | | visibility | shared | +------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------+ openstack image list +--------------------------------------+-----------+--------+ | ID | Name | Status | +--------------------------------------+-----------+--------+ | 6b92f1ae-9726-469b-a350-f116c36e61d7 | cirros | active | | f4bba9a3-8640-4162-b9de-0b7e29d32dcf | cirros-01 | active | +--------------------------------------+-----------+--------+ From CLI images getting created from cli but we have notice from horizon we are getting error but also in the backend image getting queued. (kolla-venv) root@controller-01:~# openstack image list +--------------------------------------+-----------+--------+ | ID | Name | Status | +--------------------------------------+-----------+--------+ | 5f030764-af42-437d-b6ee-670218a0c4e4 | ankit | queued | | 0195c152-f2b7-42f1-91b4-5e65f7588889 | ankit | queued | | 6b92f1ae-9726-469b-a350-f116c36e61d7 | cirros | active | | f4bba9a3-8640-4162-b9de-0b7e29d32dcf | cirros-01 | active | +--------------------------------------+-----------+--------+ Queued Image (kolla-venv) root@controller-01:~# openstack image show 5f030764-af42-437d-b6ee-670218a0c4e4 +------------------+------------------------------------------------------+ | Field | Value | +------------------+------------------------------------------------------+ | container_format | bare | | created_at | 2025-05-26T05:45:02Z | | disk_format | qcow2 | | file | /v2/images/5f030764-af42-437d-b6ee-670218a0c4e4/file | | id | 5f030764-af42-437d-b6ee-670218a0c4e4 | | min_disk | 0 | | min_ram | 0 | | name | ankit | | owner | 302edafdf0114b41acad32725668cd13 | | properties | os_hidden='False' | | protected | False | | schema | /v2/schemas/image | | status | queued | | tags | | | updated_at | 2025-05-26T05:45:02Z | | visibility | shared | +------------------+------------------------------------------------------+ Active Image (kolla-venv) root@controller-01:~# openstack image show 6b92f1ae-9726-469b-a350-f116c36e61d7 +------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Field | Value | +------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | checksum | c8fc807773e5354afe61636071771906 | | container_format | bare | | created_at | 2025-05-26T05:02:02Z | | disk_format | qcow2 | | file | /v2/images/6b92f1ae-9726-469b-a350-f116c36e61d7/file | | id | 6b92f1ae-9726-469b-a350-f116c36e61d7 | | min_disk | 0 | | min_ram | 0 | | name | cirros | | owner | 302edafdf0114b41acad32725668cd13 | | properties | os_hash_algo='sha512', | | | os_hash_value='1103b92ce8ad966e41235a4de260deb791ff571670c0342666c8582fbb9caefe6af07ebb11d34f44f8414b609b29c1bdf1d72ffa6faa39c88e8721d09847952b', | | | os_hidden='False', owner_specified.openstack.md5='', owner_specified.openstack.object='images/cirros', owner_specified.openstack.sha256='', stores='rbd' | | protected | False | | schema | /v2/schemas/image | | size | 21430272 | | status | active | | tags | | | updated_at | 2025-05-26T05:02:03Z | | virtual_size | 117440512 | | visibility | shared | +------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------+ Please find the horizon logs also 2025-05-26 04:53:24.723082 /var/lib/kolla/venv/lib/python3.12/site-packages/oslo_policy/policy.py:1133: UserWarning: Policy "modify_image": "rule:context_is_admin or (role:member and project_id:%(project_id)s)" failed scope check. The token used to make the request was domain scoped but the policy requires ['project'] scope. This behavior may change in the future where using the intended scope is required 2025-05-26 04:53:24.723167 warnings.warn(msg) 2025-05-26 04:53:24.732065 /var/lib/kolla/venv/lib/python3.12/site-packages/oslo_policy/policy.py:1133: UserWarning: Policy "reactivate": "rule:context_is_admin or (role:member and project_id:%(project_id)s)" failed scope check. The token used to make the request was domain scoped but the policy requires ['project'] scope. This behavior may change in the future where using the intended scope is required 2025-05-26 04:53:24.732130 warnings.warn(msg) 2025-05-26 04:53:34.669166 /var/lib/kolla/venv/lib/python3.12/site-packages/oslo_policy/policy.py:1133: UserWarning: Policy "os_compute_api:os-simple-tenant-usage:show": "rule:project_reader_or_admin" failed scope check. The token used to make the request was domain scoped but the policy requires ['project'] scope. This behavior may change in the future where using the intended scope is required 2025-05-26 04:53:34.669253 warnings.warn(msg) 2025-05-26 04:53:34.670620 /var/lib/kolla/venv/lib/python3.12/site-packages/oslo_policy/policy.py:1133: UserWarning: Policy "os_compute_api:os-quota-sets:update": "rule:context_is_admin" failed scope check. The token used to make the request was domain scoped but the policy requires ['project'] scope. This behavior may change in the future where using the intended scope is required 2025-05-26 04:53:34.670653 warnings.warn(msg) 2025-05-26 04:54:01.749398 /var/lib/kolla/venv/lib/python3.12/site-packages/openstack_dashboard/api/keystone.py:408: DeprecationWarning: Using the 'project' argument is deprecated in version '1.7.0' and will be removed in version '2.0.0', please use the 'default_project' argument instead 2025-05-26 04:54:01.749516 users = keystoneclient(request, admin=True).users.list(**kwargs) 2025-05-26 04:54:28.131860 /var/lib/kolla/venv/lib/python3.12/site-packages/oslo_policy/policy.py:1133: UserWarning: Policy "deactivate": "rule:context_is_admin or (role:member and project_id:%(project_id)s)" failed scope check. The token used to make the request was domain scoped but the policy requires ['project'] scope. This behavior may change in the future where using the intended scope is required 2025-05-26 04:54:28.131939 warnings.warn(msg) 2025-05-26 04:54:33.886717 Project switch successful for user "admin". 2025-05-26 04:54:44.853694 Forbidden: /api/glance/images/4b2517db-1352-45ed-ae87-5a6179bc3422/actions/reactivate 2025-05-26 04:54:51.522777 /var/lib/kolla/venv/lib/python3.12/site-packages/oslo_policy/policy.py:1133: UserWarning: Policy "deactivate": "rule:context_is_admin or (role:member and project_id:%(project_id)s)" failed scope check. The token used to make the request was domain scoped but the policy requires ['project'] scope. This behavior may change in the future where using the intended scope is required 2025-05-26 04:54:51.522876 warnings.warn(msg) 2025-05-26 04:55:07.647877 Project switch successful for user "admin". 2025-05-26 04:55:09.798541 OPENSTACK_IMAGE_BACKEND has a format "" unsupported by glance 2025-05-26 04:55:09.798708 OPENSTACK_IMAGE_BACKEND has a format "docker" unsupported by glance 2025-05-26 04:55:09.798760 OPENSTACK_IMAGE_BACKEND has a format "ova" unsupported by glance 2025-05-26 05:03:59.763647 /var/lib/kolla/venv/lib/python3.12/site-packages/oslo_policy/policy.py:1133: UserWarning: Policy "communitize_image": "rule:context_is_admin or (role:member and project_id:%(project_id)s)" failed scope check. The token used to make the request was domain scoped but the policy requires ['project'] scope. This behavior may change in the future where using the intended scope is required 2025-05-26 05:03:59.763801 warnings.warn(msg) Please help to solve this issue. also I don't see any issue or error in the glance api logs

2 2