- openstack-discuss - lists.openstack.org

Live migration fails
by Szabo, Istvan (Agoda) 06 Aug '24

06 Aug '24

Hi, I have couple of compute nodes where the live migration fails with existing vms. When I quickly spawn a vm and try live migration it works so I assume shouldn't be a big problem with the compute node. However I have many existing vms where it fails with a servername not found. /var/log/nova/nova-conductor.log:2021-04-21 14:47:12.605 227612 ERROR nova.conductor.tasks.migrate [req-f4067a26-a233-4673-8c07-9a8a290980b0 dce35e6eceea4312bb0baa0510cef363 ca7e35079f4440c78bd9870724b9638b - default default] [instance: 1517a2ac-3b51-4d8d-80b3-89a5614d1ae0] Unable to find record for source node servername on servername: ComputeHostNotFound: Compute host servername could not be found. /var/log/nova/nova-conductor.log:2021-04-21 14:47:12.605 227612 WARNING nova.scheduler.utils [req-f4067a26-a233-4673-8c07-9a8a290980b0 dce35e6eceea4312bb0baa0510cef363 ca7e35079f4440c78bd9870724b9638b - default default] Failed to compute_task_migrate_server: Compute host servername could not be found.: ComputeHostNotFound: Compute host servername could not be found. /var/log/nova/nova-conductor.log:2021-04-21 14:47:12.605 227612 WARNING nova.scheduler.utils [req-f4067a26-a233-4673-8c07-9a8a290980b0 dce35e6eceea4312bb0baa0510cef363 ca7e35079f4440c78bd9870724b9638b - default default] [instance: 1517a2ac-3b51-4d8d-80b3-89a5614d1ae0] Setting instance to ACTIVE state.: ComputeHostNotFound: Compute host servername could not be found. /var/log/nova/nova-conductor.log:2021-04-21 14:47:12.672 227612 ERROR oslo_messaging.rpc.server [req-f4067a26-a233-4673-8c07-9a8a290980b0 dce35e6eceea4312bb0baa0510cef363 ca7e35079f4440c78bd9870724b9638b - default default] Exception during message handling: ComputeHostNotFound: Compute host am-osfecn-4025 Tried with this command: nova live-migration --block-migrate id. Any idea? Thank you. ________________________________ This message is confidential and is for the sole use of the intended recipient(s). It may also be privileged or otherwise protected by copyright or other legal rules. If you have received it by mistake please let us know by reply email and delete it from your system. It is prohibited to copy this message or disclose its content to anyone. Any confidentiality or privilege is not waived or lost by any mistaken delivery or unauthorized disclosure of the message. All messages sent to and from Agoda may be monitored to ensure compliance with company policies, to protect the company's interests and to remove potential malware. Electronic messages may be intercepted, amended, lost or deleted, or contain viruses.

5 16

nova db queries
by engineer2024 06 Aug '24

06 Aug '24

Hi, I am trying to execute a query on nova db in a custom code file in nova. During the execution of a function like 'instance_get_all_by_filters_sort' from nova/db/main/api.py , I see this --- try: query_prefix = sqlalchemyutils.paginate_query( query_prefix, models.Instance, limit, sort_keys, marker=marker, sort_dirs=sort_dirs, ) except db_exc.InvalidSortKey: raise exception.InvalidSortKey() instances = query_prefix.all() --- So, my question is how does query_prefix.all() know the mysql db connection url to connect to for executing the query ? Thanks elinux

2 1

[ironic] HTTPS Provisioning
by Michael Koch 06 Aug '24

06 Aug '24

Good day, I hope this is the right way to ask. Is it possible to use IPXE HTTPS or UEFI HTTPS Network boot with Openstack Ironic, because most of the communication or completely should be encrypted. Or how do you have to configure this. Unfortunately, I have not yet found any instructions in the documentation. Of course, it is also necessary to import the certificates or install IPXE on the client side. Perhaps I have overlooked something and would like some clarification. Best regards Michael

2 1

[all][elections][ptl][tc] Combined PTL/TC 2025.1 cycle Election Season
by Sławek Kapłoński 06 Aug '24

06 Aug '24

Hello everyone, Election details: https://governance.openstack.org/election/ The nomination period officially begins Aug 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 4 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. [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 Thank you, Slaweq

1 0

[tc][all] OpenStack Technical Committee Weekly Summary and Meeting Agenda (2024.2/R-8)
by Goutham Pacha Ravi 05 Aug '24

05 Aug '24

Hello Stackers, It's been a quiet-yet-busy week for the OpenStack Technical Committee as we approach the tail end of the 2024.2 (Dalmatian) release cycle [1]. We're 8 weeks away from the release date (2024-10-02) and three weeks away from the feature code freeze across many OpenStack code repositories (2024-08-29). If you are a maintainer of an OpenStack repository with any Zuul jobs, I'd encourage you to check if your repository is flagged with any configuration errors [2]. It's possible you're referencing a nodeset or a code repository that isn't there anymore (for example, CentOS-8-Stream was recently deleted [3]). Or, it's possible that you have deprecated syntax. There's a lot of prior art if you would like to fix your Zuul configuration. If you're unsure what to do, please send an email to this list or chat with a Zuul maintainer on OFTC's #opendev channel. The nomination period for PTL positions and the OpenStack TC begins next week (2024-08-14). Election officials will be sharing more context over the next week. If you are a PTL or a member of the TC, motivate individuals to take on these leadership roles and support their enthusiasm. === Weekly Meeting === The TC had a productive meeting over IRC last week [4]. We discussed phased updates to the eventlet removal proposal [5] and the health of the CI system over the past week. Several contributors helped land CVE fixes in the past couple of weeks, which required bumping up package constraints within older stable branches. The removal of CentOS-8-Stream nodesets and the Linaro arm64 region from Zuul caused some gate instability; the Infrastructure team will be glad to assist anyone who's triaging failures caused by these actions. The TC noted the need to delay the retirement of "kuryr-kubernetes" until the Tacker project team has stopped relying on it. The next meeting is on Tuesday (2024-08-06), and it will be simultaneously hosted on Zoom and IRC. Information to join this meeting and the meeting's agenda are on our Wiki page [6]. I hope you'll be able to join us there. === Governance Proposals === ==== Merged ==== Follow up on the affiliation diversity handling | https://review.opendev.org/c/openstack/governance/+/923876 Add os-test-images under glance | https://review.opendev.org/c/openstack/governance/+/925044 [follow up] Fix typos in the eventlet removal proposal | https://review.opendev.org/c/openstack/governance/+/924944 ==== Open for Review/Discussion ==== Update criteria for inactive projects to become active again | https://review.opendev.org/c/openstack/governance/+/921500 Inactive state extensions: Monasca | https://review.opendev.org/c/openstack/governance/+/923919 === Upcoming Events === 2024-08-06: OpenInfra Board Meeting: https://board.openinfra.dev/meetings/2024-08-06 2024-08-12: Call for Proposals due for the OpenInfra Days NA [8] 2024-08-14: Nominations open for 2025.1 OpenStack PTL+TC elections 2024-08-24: Open Infra Days, Vietnam: https://2024.vietopeninfra.org/ 2024-08-29: Dalmatian-3 milestone 2024-09-03: OpenInfra Summit Asia, Suwon Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] Release Schedule: https://releases.openstack.org/dalmatian/schedule.html [2] Zuul Configuration Errors: https://zuul.opendev.org/t/openstack/config-errors [3] CentOS-8-Stream node pool removal: https://lists.opendev.org/archives/list/service-announce@lists.opendev.org/… [4] TC Meeting IRC Logs, 2024-07-30: https://meetings.opendev.org/meetings/tc/2024/tc.2024-07-30-18.00.log.html [5] Remove Eventlet From Openstack: https://review.opendev.org/c/openstack/governance/+/902585 [6] TC Meeting, 2024-08-06: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

Assistance needed - Application Credential
by Naveen Anbarasu 05 Aug '24

05 Aug '24

Hi team, I have created an application credential for the compute service and successfully obtained a token. Access rule: "service": "compute", "method": "GET", "path": "/v2.1/servers" However, when using the token to retrieve the server list, I receive a Error 403 Forbidden error with the message: 'Policy doesn't allow os_compute_api:servers to be performed. But i have a necessary permission within the respective project (member role) How can I solve this problem? Thanks in advance

7 12

designate-sink and find_records()
by Andrew Bogott 05 Aug '24

05 Aug '24

Hello! I use a custom designate sink driver to detect when VMs have been deleted in order to clean up associated resources specific to our cloud: certs, proxies, etc. When deleting proxies I relied on the find_records() call to get a list of IPs associated with the deleted VM; for example: records = central_api.find_records(context, crit) if records: ip = records[0].data LOG.debug("Cleaning up proxy records for IP %s" % ip) self._delete_proxies_for_ip(data["project_name"], ip) Now that the find_records() rpc call has been removed I'm at a bit of a loss. I don't think I can call back into nova for the IPs because by the time sink knows about a VM deletion it has most likely already been deleted from nova. Can anyone suggest a workaround for answering the question "what IPs were associated with that VM that just got deleted?" Or, better yet, is there someplace else in my infra where I should have my special deletion handler outside of designate-sink? Thank you for entertaining this very obscure question :) -Andrew

1 0

[publiccloud-sig] Reminder - next meeting August 7th - 0700 UTC
by Felix Kronlage-Dammers 05 Aug '24

05 Aug '24

Hi everyone, This Wednesday (August 7th) the next meeting of the public cloud sig is going to happen. We’ll be meeting at 0700 UTC here: https://meetpad.opendev.org/publiccloud-sig <https://meetpad.opendev.org/publiccloud-sig> See also here for all other details: https://wiki.openstack.org/wiki/PublicCloudSIG <https://wiki.openstack.org/wiki/PublicCloudSIG> See you on Wednesday! felix -- Felix Kronlage-Dammers 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

[horizon] How to enable MFA {TOTP} on Horizon (with ZED release)
by Shubham Kumar Yadav 05 Aug '24

05 Aug '24

Hi all, I was working on a MFA in openstack (ZED). Is it possible to enable MFA using TOTP on Horizon? I'm using a ZED Openstack with Ubuntu 22.04 , and I know that from the CLI point of view, you can have Multi Factor Authentication, but I don't see that implemented on Horizon. i added MFA using - https://docs.openstack.org/keystone/pike/advanced-topics/auth-totp.html but now the problem is i can use the token issued to run openstack cli but not able to login into Horizon with user and password/totp. I see The Totp support was added to Horizon in the Bobcat (2023.2) release I tried the Bobcat image and TOTP seems to work fine with Google Authenticator but doesnt work with the Zed release i added this with Bobcat release image - https://review.opendev.org/c/openstack/charm-openstack-dashboard/+/920704 *So I would like to ask how it is possible to backport the feature in Horizon in the Zed release.* I would appreciate any help! Thanks!

1 0

Bug Deputy Report 29 July - 04 August
by Elvira Garcia Ruiz 05 Aug '24

05 Aug '24

Hi neutrinos! Here you have the list of bugs reported during last week (29 Jul - 04 Aug) High ------ - https://bugs.launchpad.net/neutron/+bug/2062385 "neutron-tempest-plugin-api-ovn-wsgi" not working with TLS Fix proposed by Rodolfo https://review.opendev.org/c/openstack/neutron/+/925376 - https://bugs.launchpad.net/neutron/+bug/2075151 ovs-master jobs failing with lib/actions.c:4549:9: error: struct ofpact_sample has no member named obs_domain_imm; did you mean obs_domain_id? Fix proposed by Pierre Riteau https://review.opendev.org/c/openstack/neutron/+/925091 Medium ----------- - https://bugs.launchpad.net/neutron/+bug/2075207 Neutron ports don't work for certain names Unassigned Incomplete --------------- - https://bugs.launchpad.net/neutron/+bug/2075529 Unable to delete "access_as_shared" RBAC policy Unassigned. Reporter said they were working on a fix. RFEs -------------- - https://bugs.launchpad.net/neutron/+bug/2075958 [RFE] Allow binding SecurityGroups to Network Unassigned - https://bugs.launchpad.net/neutron/+bug/2075955 [RFE] Limit who may bind security groups Unassigned Best regards, Elvira

1 0

[openstack][kolla-ansible]about upgrading openstack
by Nguyễn Hữu Khôi 04 Aug '24

04 Aug '24

Hello. I read this doc about upgrading openstack https://docs.openstack.org/kolla-ansible/latest/user/operating-kolla.html But I would like to know if We install a new kolla-ansible(version to upgrade) on the new deployment host, apply changes with password.yml, global.yml and multinode and keep old /etc/kolla/config. Finally, we use kolla-ansible deploy instead of kolla-ansible upgrade. Are these steps ok? Pls correct me if I am wrong. Thank you. Regards Nguyen Huu Khoi

3 8

[dev][neutron] Interest for a network-level SecurityGroup binding ?
by David Pineau 02 Aug '24

02 Aug '24

Hello Neutron Team, I'm part of a company that is currently migrating from homemade software to manage the infrastructure for a virtualization-based product towards an openstack based infrastructure. As such, this platform includes both private and public cloud usages, which brings me to our current network problem. Essentially, as administrators of the system, we want to expose a pre-configured network, which provides access to some non-openstack managed resources, via some routing mechanisms. The various VMs on this network must not be able to see each-other, as this network may be exposed to multiple customers/projects. Note that in this context, we're using the OVN driver for our network stack. We were initially looking at external networks for this, but understood through our attempts and experimentations that: - External networks are shared to all projects by default - Default sharing of external networks can be disabled by removing the automatically injected rbac for '*', allowing us to expose the network to only the projects we specify - VMs on this network can communicate with each other - Applying FlowControl does not solve this for VMs on the same Hypervisor (as they're directly communicating, and traffic does not seem to go through the host) - Only security groups can prevent such communication, but since it's associated to a Port, we cannot enforce it - All flow control for the various networks connected to a VM are currently setup on a single bridge interface on the hypervisor First question is simple: Did we miss anything ? Or is our understanding of the mechanisms on point ? In the second case, this leads me to the proposal mentioned in the subject: Offer a Network/SecurityGroup binding mechanism that would automatically/implicitly include its rules to the port's rules. The idea is that this would allow an administrator (and project administrator?) to enforce specific rules via security groups attached to the network itself, effectively providing a category of network aimed at providing connectivity to a specific external service. Additionally, this creates a behavior where unless the administrator allows it, no two VMs on this network may be able to communicate together, as a default. What do you think about this feature ? Is there any major risk/flaw that I might be missing ? Would you, as a community, welcome such an effort ? Kind regards, -- David Pineau Engineer @Shadow IRC nick: joa

3 3

[election] [tc] Notification of non-candidacy; how it impacts TC diversity
by Jay Faulkner 01 Aug '24

01 Aug '24

Hi all, The nomination period for TC members / PTLs is coming up soon. I wanted to inform the community that I do not intend on standing for election for another year on the TC. Now is a good time, especially if you work somewhere other than Red Hat, to consider serving as a TC member to ensure our leadership team contains representation for all perspectives of OpenStack use. I'm happy to speak with anyone privately who is interested in running about what it's like to be on the TC, and to share some strategies I exercised to ensure the value of my TC membership was being communicated to leadership at my job. Thanks, Jay Faulkner Technical Committee Member

6 5

oslo.service
by engineer2024 01 Aug '24

01 Aug '24

Can anyone guide me how to configure and use oslo.service for nova-api service for tracing and debugging ? Thanks elinux

3 2

filter out unsupported volume type for a given compute node
by Jiatong Shen 01 Aug '24

01 Aug '24

Hello Stackers, Our company is operating many sophisticated clusters with different storage types, such Ceph and SAN storage. What makes things trickier is that some compute node cannot use certain volume types. For example, some compute nodes do not have HBA, so they cannot take advantage of FC based SAN storage; the others do not have 10GbE ethernet, so they cannot connect to Ceph. Such deployment sometimes makes resize virtual machine quite tricky. So my question is what is best practice for this situation? Is it possible to determine if certain volume type is usable on a given compute node? Thank you very much for help. -- Best Regards, Jiatong Shen

2 1

[manila] Mid cycle on Aug 12th and 13th
by Carlos Silva 01 Aug '24

01 Aug '24

Hello zorillas and interested stackers! Over the PTG, we have agreed on having a mid-cycle checkpoint meeting, so we can discuss the progress of all things we planned. We have settled on the dates, and it will happen on August 12 and 13, from 14 to 16 UTC both days. We will use a meetpad for the meeting [1]. During the first day we will focus on covering the PTG topics, and for the second day, we will focus on the collaborative review sessions for all of the features being proposed on this cycle. We highly encourage everyone proposing and targeting features for this cycle to participate and propose collaborative review sessions, so we can speed up the reviews on gerrit. The meeting room and some topics are already available in the mid cycle etherpad [1], so please add your topics and propose collaborative review sessions for the features you are working on. [1] https://etherpad.opendev.org/p/manila-dalmatian-mid-cycle-notes Looking forward to it! Regards, carloss

1 0

placement issue
by Parsa Aminian 01 Aug '24

01 Aug '24

hello Im using kolla-ansible openstack version 2024.1 and all of my nova_compute containers are unhealthy because of this error : ERROR nova.compute.manager nova.exception.ResourceProviderAllocationRetrievalFailed: Failed to retrieve allocations for resource provider 3b09027d-c622-489e-bc73-4c5877069977: {"errors": [{"status": 404, "title": "Not Found", "detail": "The resource could not be found.\n\n No such resource class 0. ", "request_id": "req-a33704ce-4dad-4ac3-a46c-bd5a4d0d126b"}]} How can I solve this problem ? thanks in advance

1 0

[cinder] Stepping down from Cinder core
by Pete Zaitcev 01 Aug '24

01 Aug '24

Hello: Because of a job change, my time available is becoming quite limited, so I'm not going to be able to contribute at the appropriate level. So, I contacted our PTL to get me removed from the core team. Thanks everyone for the help and the journey in Cinder. Greetings, Pete

3 2

nova deploy issue
by Parsa Aminian 30 Jul '24

30 Jul '24

hello when I try to reconfigure nova with kolla ansible this error will be shown : TASK [nova-cell : Waiting for nova-compute services to register themselves] ******************************************************************************************* task path: /usr/local/share/kolla-ansible/ansible/roles/nova-cell/tasks/wait_discover_computes.yml:8 fatal: [control01 -> {{ groups[nova_cell_conductor_group][0] }}]: FAILED! => { "msg": "The conditional check 'inventory_hostname == all_computes_in_batch[0]' failed. The error was: error while evaluating conditional (inventory_hostname == all_computes_in_batch[0]): 'all_computes_in_batch' is undefined\n\nThe error appears to be in '/usr/local/share/kolla-ansible/ansible/roles/nova-cell/tasks/wait_discover_computes.yml': line 8, column 7, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n- block:\n - name: Waiting for nova-compute services to register themselves\n ^ here\n" Does anyone have any idea what I should do ?

1 0

Assistance Needed for Trove Instance Creation
by Thamanna Farhath 30 Jul '24

30 Jul '24

Hello community, I am currently deploying Trove using Kolla Ansible 2023.1, following the guide provided here: https://satishdotpatel.github.io/trove-dbaas-openstack/ . Despite cleaving to the instructions, I am facing an issue where the Trove instance ends up in an error state. trove-guestagent.conf [DEFAULT] transport_url = rabbit://openstack:USI0SmaT7lPF7MJCxHPZ4alm8wiyxoihssD1VlnA@192.168.1.101:5672,openstack:USI0SmaT7lPF7MJCxHPZ4alm8wiyxoihssD1VlnA@192.168.1.102:5672,openstack:USI0SmaT7lPF7MJCxHPZ4alm8wiyxoihssD1VlnA@192.168.1.103:5672// control_exchange = trove root_grant = ALL root_grant_option = True debug = False Docker Status Check: docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES f698ee14d928 mysql:5.7.29 "docker-entrypoint.s…" 18 minutes ago Up 18 minutes 0.0.0.0:3306->3306/tcp, :::3306->3306/tcp, 33060/tcp database Telnet Connection: telnet 192.168.50.78 3306 Trying 192.168.50.78... Connected to 192.168.50.78. Escape character is '^]'. J 5.7.29p+C5 }0^k[zH3mysql_native_password Syslog(SSH into the trove instance) ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)\n": Exception: Running command error: b"mysql: [Warning] Using a password on the command line interface can be insecure.ERROR trove.guestagent.datastore.service [None req-a03ff3dd-5a8f-4fd4-80d5-76e31fa16dd0 - - - - - -] Timeout while waiting for database status to change. Expected state healthy, current state is running When looking for the missing directory, I discovered it in /var/lib/mysql/mysqld.sock and /var/lib/mysql/mysqld.pid paths. How can I get an active instance?Kindly help me resolve this. Thank you in advance Disclaimer : The content of this email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error, please notify the sender and remove the messages from your system. If you are not the named addressee, it is strictly forbidden for you to share, circulate, distribute or copy any part of this e-mail to any third party without the written consent of the sender. E-mail transmission cannot be guaranteed to be secured or error free as information could be intercepted, corrupted, lost, destroyed, arrive late, incomplete, or may contain viruses. Therefore, we do not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email."

3 2

[horizon] How to enable MFA using TOTP on Horizon (ZED)
by Shubham Kumar Yadav 30 Jul '24

30 Jul '24

Hi all, I was working on a MFA in openstack (ZED). Is it possible to enable MFA using TOTP on Horizon? I'm using a ZED Openstack with Ubuntu 22.04 , and I know that from the CLI point of view, you can have Multi Factor Authentication, but I don't see that implemented on Horizon. i added MFA using - https://docs.openstack.org/keystone/pike/advanced-topics/auth-totp.html but now the problem is i can use the token issued to run openstack cli but not able to login into Horizon with user and password/totp. I see The Totp support was added to Horizon in the Bobcat (2023.2) release So i would like to ask how it is possible to backport the feature in Horizon in the zed release. I would appreciate any help! Thanks!

2 1

[ironic] ironic-inspector bugfix branches
by Riccardo Pittau 30 Jul '24

30 Jul '24

Hello ironicers! With the deprecation and the migration of the ironic-inspector functionalities to the new agent interface in ironic we have decided to also stop cutting bugfix branches for the project. The last bugfix branch for ironic-inspector is bugfix/12.2 supported until December 2024. We'll continue with the normal release schedule until full retirement of the project. Thanks Ciao! Riccardo

1 0

[neutron] CI Meeting cancelled for today
by Yatin Karel 30 Jul '24

30 Jul '24

Hello Neutron Team !! I will not be able to chair the CI meeting today as I have to attend some internal meetings. Sorry for the late notice. We have some known issues in CI and all are under track with patches in gate or already merged. There are some issues in the periodic line specific to ovs-master jobs and 9-stream so will report issues for those. -- Thanks and Regards Yatin Karel

1 0

[tc][all] OpenStack Technical Committee Weekly Summary and Meeting Agenda (2024.2/R-9)
by Goutham Pacha Ravi 29 Jul '24

29 Jul '24

Hello Stackers, We're counting down 9 weeks to the 2024.2 (Dalmatian) release [1]. OpenStack projects that follow the cycle-with-rc release model [2] will have their code freeze in 4 weeks. Between now and the release, the release team will communicate with us weekly to coordinate deliverables across the community. The elections for OpenStack PTLs and Technical Committee members are around the corner as well, so now is a good time to ensure that you are eligible to vote in these elections! Please navigate to: https://civs1.civs.us/cgi-bin/opt_in.pl Enter your preferred email address on Gerrit and request activation. It only takes a minute! :) The following are updates from the OpenStack Technical Committee during the past week. === Weekly Meeting === The TC had a productive meeting via IRC on OFTC's #openstack-tc channel last week [3]. We discussed follow-ups for the eventlet removal goal proposal [4] and recent updates to inactive and emerging OpenStack projects. We spent some time assessing gate health concerns, including an issue with a change to `setuptools` that requires us to bump the upper constraint on the "packaging" library in stable/2023.1 [5]. This was important to get some CVE fixes landed in various OpenStack code repositories. Finally, we refreshed our understanding of the TC's house rules. To summarize: - Changes to the TC charter require at least 2/3 of the TC voting in favor, while governance motions require at least 1/3 of the TC to vote in favor. - TC members can vote positively, negatively, or abstain (using the “RollCall-Vote” in Gerrit). - Decisions need more positive votes than negative votes (ties mean the proposal is rejected). - Any motion or charter-change is deliberately open at least a week after it was last proposed/updated, allowing the TC and the wider community to participate fully. - Significant governance changes take a while to merge because of the importance of ensuring full TC and community engagement in votes. Our next weekly meeting is tomorrow (2024-07-30) at 1800 UTC via IRC on OFTC's #openstack-tc channel. You can find the agenda on the OpenStack TC wiki page [6]. Please consider joining us and remember, you can edit the wiki and propose new topics! === Governance Proposals === ==== Merged ==== - Add `os-test-images` under glance | https://review.opendev.org/c/openstack/governance/+/925044 ==== Open for review/discussion ==== - [Follow-up] Fix typos in the eventlet proposal | https://review.opendev.org/c/openstack/governance/+/924944 - Update criteria for inactive projects to become active again | https://review.opendev.org/c/openstack/governance/+/921500 - Follow up on the affiliation diversity handling | https://review.opendev.org/c/openstack/governance/+/923876 - Inactive state extensions: Monasca | https://review.opendev.org/c/openstack/governance/+/923919 === Upcoming Events === - 2024-08-12: Call for Proposals due for the OpenInfra Days NA [7] - 2024-08-14: Nominations open for 2025.1 OpenStack PTL+TC elections - 2024-08-24: OpenInfra Days, Vietnam: https://2024.vietopeninfra.org/ - 2024-08-29: Dalmatian-3 milestone - 2024-09-03: OpenInfra Summit Asia, Suwon The OpenStack Technical Committee serves you! We're always willing to chat and would love feedback: === How to contact the TC === You can reach out to the TC in multiple ways: 1. Email: Send an email with the tag [tc] on this email list. 2. Ping us using the 'tc-members' keyword on the #openstack-tc IRC channel. 3. Join us at our weekly meeting: The Technical Committee meets every week on Tuesdays at 1800 UTC [7]. Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] Release Schedule: https://releases.openstack.org/dalmatian/schedule.html [2] OpenStack cycle-with-rc model: https://releases.openstack.org/reference/release_models.html#cycle-with-rc [3] TC Meeting IRC Logs, 2024-07-23: https://meetings.opendev.org/meetings/tc/2024/tc.2024-07-23-18.00.log.html [4] Remove Eventlet From Openstack: https://review.opendev.org/c/openstack/governance/+/902585 [5] Update packaging constraint in stable/2023.1: https://review.opendev.org/c/openstack/requirements/+/924764 [6] TC Meeting, 2024-07-30: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [7] Call for Proposals, OpenInfra Days NA: https://docs.google.com/forms/d/e/1FAIpQLSeFQBL1qGNegDWDHCVTLtu_wLf06w7JJkc…

1 0

Cinder Bug Report 2024-07-29
by Jon Bernard 29 Jul '24

29 Jul '24

Hello Argonauts, Cinder Bug Meeting Etherpad <https://etherpad.opendev.org/p/cinder-bug-squad-meeting> Undecided - When restoring volume using the imported backup, it is always scheduled to the same host. <https://bugs.launchpad.net/cinder/+bug/2074058> - Status: In Progress (assigned) - The cinder-backup swift driver connects to swift in a different region. <https://bugs.launchpad.net/cinder/+bug/2074126> - Status: In Progress (assigned) - allow_qcow2_backing_file flag cannot be passed into some image_utils operations <https://bugs.launchpad.net/cinder/+bug/2074377> - Status: New (unassigned) Thanks, -- Jon

1 0