April 2024 - openstack-discuss - lists.openstack.org

[openstack-ansible] : Ussuri minor version update.
by keshav bareja 04 Apr '24

04 Apr '24

Hi Team I am planning to update my environment from the current ussuri minor version to the latest minor version available for the Ussuri. I found the procedure below. https://docs.openstack.org/openstack-ansible/ussuri/admin/upgrades/minor-up… I have some queries on this: 1. How to find the current minor release version of the Ussuri deployed on my environment? Is there any command or way that can help? 2. What is the latest minor version available for Ussuri? In the Ussuri release notes page I could see 2.10, can someone please confirm if 2.10 is the latest version? 3. Also I need to know the bug fixes between my current release to the latest minor ussuri release. 4. Can someone confirm what all pre-requisite I need to take care of before going with the update. 5. Anyone having experience with such minor updates , Please share precaution and recommendations, Ussuri Series Release Notes <https://docs.openstack.org/releasenotes/openstack-ansible/victoria.html> <https://docs.openstack.org/releasenotes/openstack-ansible/train.html> <https://bugs.launchpad.net/openstack-ansible/+filebug?field.title=Ussuri%20…> 21.2.10 <https://docs.openstack.org/releasenotes/openstack-ansible/ussuri.html#relno…>Security Issues <https://docs.openstack.org/releasenotes/openstack-ansible/ussuri.html#secur…> - This release eliminates following security issues: - OSSA-2021-005: https://security.openstack.org/ossa/OSSA-2021-005.html - OSSA-2021-006: https://security.openstack.org/ossa/OSSA-2021-006.html

2 5

Panko Service get_events function returning none
by Sandesh Kulkarni 04 Apr '24

04 Apr '24

Hi Openstack Team, I am using Panko for events retrieval, but I am getting None from the below query. My current SqlAlchemy version is 1.4.31. Could you please guide me in retrieving the correct events from the database? Output from the panko events api :- { "message_id": "2b4d83b4-3e23-4326-bedb-557a405c16db", "event_type": "audit.http.response", "traits": [ { "name": "action", "value": "None", "type": "string" }, { "name": "eventTime", "value": "2024-03-27T03:59:52.192750", "type": "datetime" }, { "name": "eventType", "value": "None", "type": "string" }, { "name": "id", "value": "None", "type": "string" }, { "name": "initiator_host_address", "value": "None", "type": "string" }, { "name": "initiator_id", "value": "None", "type": "string" }, { "name": "initiator_name", "value": "None", "type": "string" }, { "name": "initiator_typeURI", "value": "None", "type": "string" }, { "name": "observer_id", "value": "None", "type": "string" }, { "name": "outcome", "value": "None", "type": "string" }, { "name": "project_id", "value": "None", "type": "string" }, { "name": "reason_code", "value": "None", "type": "string" }, { "name": "requestPath", "value": "None", "type": "string" }, { "name": "request_id", "value": "None", "type": "string" }, { "name": "service", "value": "None", "type": "string" }, { "name": "target_id", "value": "None", "type": "string" }, { "name": "target_name", "value": "None", "type": "string" }, { "name": "target_typeURI", "value": "None", "type": "string" }, { "name": "typeURI", "value": "None", "type": "string" }, { "name": "user_id", "value": "None", "type": "string" } ], "generated": "2024-03-27T03:59:52.693294", "raw": {} } Query Link :- https://github.com/openstack/panko/blob/4d0c0d66da6833e5283d71fe5bdee9594e4… Thanks and Regards, Sandesh Kulkarni

1 0

[all][elections][tc] 2024.2 Dalmatian Technical Committee Election Results
by Ian Y. Choi 04 Apr '24

04 Apr '24

Please join me in congratulating the 5 newly elected members of the Technical Committe (TC). Amy Marrich (spotz) Goutham Pacha Ravi (gouthamr) Dmitriy Rabotyagov (noonedeadpunk) Artem Goncharov (gtema) (replacing Sylvain Bauza - bauzas as per the TC resolution) [1] Slawek Kaplonski (slaweq) Full results: https://civs1.civs.us/cgi-bin/results.pl?id=E_f8044ce7af316bf3 Election process details and results are also available here: https://governance.openstack.org/election/ Note that we encountered a situation where not all members as elected could be seated which requires TC resolution. More details on the resolution are explained in [1], and thank you all for the understanding and support in resolving this matter. Thank you to all of the candidates, having a good group of candidates helps engage the community in our democratic process. Thank you to all who voted and who encouraged others to vote. We need to ensure your voice is heard. Thank you for another great round. [1] https://governance.openstack.org/tc/resolutions/20240322-adjudication-of-20…

1 0

OpenStack 2024.1 Caracal is officially released!
by Herve Beraud 03 Apr '24

03 Apr '24

Hello OpenStack community, The official OpenStack 2024.1 Caracal release announcement has been sent out: https://lists.openstack.org/archives/list/openstack-announce@lists.openstac… Thanks to all who were a part of the 2024.1 Caracal development cycle! This marks the official opening of the openstack/releases repository for 2024.2 Dalmatian releases, and freezes are now lifted. stable/2024.1 is now a fully normal stable branch, and the normal stable policy applies from now on. Thanks, -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/

3 2

User survey 2023 - TC questions
by Sławek Kapłoński 03 Apr '24

03 Apr '24

Hi, I am doing analysis of the TC questions in the 2023 user survey [1] and I need some additonal information. In the results of the survey which I some time ago got from Allison there are only short "names" of the questions, like e.g. "TCContributions" but no full question which was asked. This is ok for me for the questions which were in the survey in previous years but this year TC added couple of new questions for which I don't have full questions at all. Short names of those questions are: - TCConsumingOpenStack - TCConsumingOpenStackOther - TCInteractOpenStack - TCInteractOpenStack - TCInteractOpenStackSkyline - TCInteractOpenStackSkylineList - TCInteractSkylineOther - TCInteractOpenStackInternal - TCInteractOpenStackInternalOther - TCCloudServices Can You maybe share with me what were those full questions in the survey? Or point me to the place where I can maybe find it? Thx in advanve for help with this. [1] https://review.opendev.org/c/openstack/governance/+/900516 -- Slawek Kaplonski Principal Software Engineer Red Hat

2 2

[all][tc] Next week TC meeting is canceled
by Ghanshyam Mann 02 Apr '24

02 Apr '24

Hello Everyone, As next week is vPTG happening, we are canceling next week's (April 9th) TC meeting. -gmann

1 0

[freezer] Project status update
by Dmitriy Rabotyagov 02 Apr '24

02 Apr '24

Hey there! In a previous email thread [1] an interest toward reviving the Freezer project was raised. As a result of the thread we've organized a first sync meeting with interested parties. It was a quite productive discussion and we came up with a couple of action points as a result of it. You can find more information in the etherpad [2] Among everything, one of the most important parts for now, is to step into the PTL role or move a project to a distributed leadership. At the moment the project is leadless, since there was no candidacy submitted for this election. We also agreed to schedule the next meeting on April 2 from 16-00 till 17-00 UTC and discuss progress and blockers which were found. I'm attaching an invitation to the meeting to the email. If it doesn't work, you can join on the mentioned time via the link [3] Hope to see you there and thanks for everyone who participated and stepped in for the project! [1] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [2] https://etherpad.opendev.org/p/freezer-status [3] https://meet.google.com/ckc-gevi-epe

1 2

[cinder] Canceling this week's meeting (3rd April)
by Rajat Dhasmana 02 Apr '24

02 Apr '24

Hello Argonauts, Given that tomorrow is the 2024.1 Caracal release and PTG coming up next week, we decided in last week's meeting to cancel the cinder meeting, which was going to be held on 3rd April, 2024. See you all next week at the PTG! Thanks Rajat Dhasmana

1 0

[neutron] Proposing Ihar Hrachyshka as neutron core reviewer
by Brian Haley 02 Apr '24

02 Apr '24

Hello Neutrinos, I would like to nominate Ihar Hrachyshka for Neutron core reviewer (again). He's been leaving some very useful comments lately, moved-up in the reviewer stats over the past 90 days [0], and has a lot of OVN knowledge. Ihar was previously a core reviewer from 2015-2018 so most might already know him. I think he'd be a great re-addition to the team. Please vote with a +1/-1. [0] https://www.stackalytics.io/report/contribution?module=neutron-group&projec… Thanks, -Brian, Neutron PTL

8 8

Re: [neutron][magnum][mcapi] floating IP delete permission issue
by Satish Patel 02 Apr '24

02 Apr '24

Thank you Mohammed, It would be really good if we have a flag in template to say release floating IP instead of delete. Technically operator assign floating IPs to project and only that project should use them as per need instead of delete floating ips and put it back to book. Let’s see if we can get some eyeballs on this feature. But this is very important feature for us to control public IP usage. On Mon, Apr 1, 2024 at 10:16 PM Mohammed Naser <mnaser(a)vexxhost.com> wrote: > Hi Satish, > > This is actually something that would have to be handled on the Cluster > API level, since it is the one that owns that resource. > > I would start raising an issue there first, if that gets traction then we > can integrate that with the driver after, however, if it doesn't make sense > for it to be there, we can maybe include a config flag to handle this (but > I'm not sure what other implications this would have) > > Thanks > Mohammed > ------------------------------ > *From:* Satish Patel <satish.txt(a)gmail.com> > *Sent:* April 1, 2024 10:09 PM > *To:* OpenStack Discuss <openstack-discuss(a)lists.openstack.org> > *Subject:* [neutron][magnum][mcapi] floating IP delete permission issue > > Folks, > > For regulatory purposes we set a neutron policy to not let normal users > delete their public floating IPs because they are assigned to specific > customers and we don't want them to delete them. So far that policy works. > > But now when it comes to magnum / mcapi. I am able to create a cluster but > not able to delete because when magnum is going to delete floating IP I am > getting an error saying you are not allowed to delete floating IP and k8s > are stuck in deleting state. > > Is there any way magnum can do floating IP release instead of delete? > > Following error I am seeing in CAPI logs. > > I0402 01:50:03.412447 1 recorder.go:104] "events: Failed to delete > floating IP 101.xx.xx.70: Request forbidden: [DELETE > https://os2.example.com:9696/v2.0/floatingips/492b2c4c-151b-437e-acfc-4778a…] > error message: {\"NeutronError\": {\"type\": \"PolicyNotAuthorized\", > \"message\": \"rule:delete_floatingip is disallowed by policy\", > \"detail\": \"\"}}" type="Warning" > object={"kind":"OpenStackMachine","namespace":"magnum-system","name":"kube-6aqje-csgft-nkz6s","uid":"97acabe1-e547-4bbc-8406-aebc563212cd","apiVersion":" > infrastructure.cluster.x-k8s.io/v1alpha7","resourceVersion":"31170690"} > reason="Faileddeletefloatingip" >

1 0