- openstack-discuss - lists.openstack.org

Upcoming Student Opportunities
by Kendall Nelson 26 Jul '24

26 Jul '24

Hello Everyone, I have a number of universities looking for projects and mentors for students in the coming semester. Three universities in particular - DIckinson University, Boston University, and the University of Jos in Nigeria. Dickinson University's course takes place over the whole academic year (two semesters) starting the start of September. Students will work in groups of 2-4 with the actual contribution period being October through May. Most students will be in their last year of a Bachelor's degree in CS. Boston University's course takes place across one semester. Groups of students will be 3-5 people and students will also be in their last year of a Bachelor's degree in CS. Students will make their project selections early September and begin contributing soon after. It's likely this course will also take place next semester. *For both universities, I need project proposals and volunteers (if interested of course), by the 23 of August. * The University of Jos partnership is more internship based and has a more flexible timeline. I am still gathering more details on what this will look like, but I wanted to give you all a heads up. If you have questions about any of these opportunities, please let me know!! Likewise, if you're interested, please let me know and I can support you in getting a project proposal together. -- Kendall Nelson *Senior Upstream Developer Advocate* The OpenInfra Foundation <https://openinfra.dev/>

1 0

update ubuntu and nova does not work
by kjme001＠gmail.com 26 Jul '24

26 Jul '24

update ubuntu and nova does not work During the update of ubuntu I selected option Y, as below and broke one node, the new service starts but does not work from the cluster side, what can I do now to fix it? Configuration file '/etc/nova/nova.conf' ==> Modified (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. *** nova.conf (Y/I/N/O/D/Z) [default=N] ?

2 1

[manila] Proposing Kiran Pawar to manila core
by Carlos Silva 26 Jul '24

26 Jul '24

Hello everyone, I would like to add Kiran Pawar to the OpenStack Manila core team. Kiran has been contributing with reviews [1], new features, bug fixes [2] to the OpenStack Manila components for several cycles and has clearly acquired knowledge on many areas of Manila. He has designed and worked in the implementation of several features in the core of Manila, such as share backups, deferred deletion for shares and snapshots, and most recently has been working on shares encryption and integrating Manila with Barbican. He's clearly demonstrated understanding not only on the manila core, but also in the integrations with share drivers. The participation on PTGs and other events evolving Manila has also been strong, and very impactful. Kiran also brings knowledge on large cloud environments, having worked closely on large deployments and finding solutions for their problems. This addition also means more diversity among the Manila core group, and maintaining a healthy community with different companies sharing the responsibility of maintaining an open source project. Kiran brings a lot of experience with cloud environments to the table and has been helpful on reviews and contributing with a lot of code to Manila, making him a good candidate to join the core team. In case there are no objections, I will add him to the core team in 1 week from now. [1] https://bit.ly/manila-contribution-60-days [2] https://bit.ly/kpdev-code-contributions-to-manila Thank you! Regards, carloss

4 4

[manila] Proposing Ashley Rodrigues to python-manilaclient and manila-ui core
by Carlos Silva 26 Jul '24

26 Jul '24

Hello everyone, I would like to nominate Ashley Rodriguez as python-manilaclient and manila-ui core. Ashley started contributing to OpenStack Manila more than three years ago, and managed to work on a couple of features such as the integration of Manila with OpenStack SDK, metadata for shares and share snapshots, several enhancements to the Ceph drivers testing on CI and several other bug fixes [1], which helped her in acquiring precious knowledge on the code bases, testing and providing feedback. Ashley has also been working as a mentor for many mentorship initiatives we have been promoting in Manila (Outreachy, NDSU, GHC and CMU), where we focused on different repositories, but she always demonstrated the ability to guide the interns providing insightful reviews, debugging and demonstrating good knowledge on python-manilaclient and manila-ui. This addition to the core team is one more step into maintaining a healthy community, as well as a very good way to recognize all the work and dedication Ashley has been putting on these repositories in different ways. In case there are no objections, I will add Ashley to the python-manilaclient and manila-ui core sub groups in 1 week from now. [1] https://review.opendev.org/q/owner:ashrod98@redhat.com [2] https://bit.ly/manila-contribution-60-days Thank you! Regards, carloss

4 4

Updating Instance Flavor Properties in OpenStack Cluster Without Downtime
by Mia smith 25 Jul '24

25 Jul '24

Hello OpenStack Community, In our OpenStack cluster, we recently updated some flavor properties. As a result, we need to apply these changes to all currently active instances that were created with the old flavor properties. We are looking for a solution that allows us to update these instance properties without causing any downtime or needing to resize the instances. Could anyone provide suggestions on how to achieve this? Is there a recommended method or ad-hoc command that can be used to safely update the properties directly in the database? Thank you for your assistance!

3 8

[Openstack-ansible][train] multi node deployment with CEPH-ansible
by Danish Khan 25 Jul '24

25 Jul '24

Dear Team, I am trying to deploy an openstack-ansible train with Ceph-ansible. I am stuck in a loophole due to python dependencies. As suggested, I applied a fix for the rabbitmq version and I am able to deploy openstack-ansible train successfully without ceph. But when I am deploying it with ceph then it is getting stuck at below: TASK [ceph_client : Install ceph packages] ********************************************************************************************************************************* FAILED - RETRYING: Install ceph packages (5 retries left). FAILED - RETRYING: Install ceph packages (4 retries left). FAILED - RETRYING: Install ceph packages (3 retries left). FAILED - RETRYING: Install ceph packages (2 retries left). FAILED - RETRYING: Install ceph packages (1 retries left). fatal: [sp-uat-infra-c1]: FAILED! => {"attempts": 5, "cache_update_time": 1721053914, "cache_updated": false, "changed": false, "msg": "'/usr/bin/apt-get -y -o \"Dpkg::Options::=--force-confdef\" -o \"Dpkg::Options::=--force-confold\" install 'ceph-common' 'python-ceph'' failed: E: Unable to correct problems, you have held broken packages.\n", "rc": 100, "stderr": "E: Unable to correct problems, you have held broken packages.\n", "stderr_lines": ["E: Unable to correct problems, you have held broken packages."], "stdout": "Reading package lists...\nBuilding dependency tree...\nReading state information...\nSome packages could not be installed. This may mean that you have\nrequested an impossible situation or if you are using the unstable\ndistribution that some required packages have not yet been created\nor been moved out of Incoming.\nThe following information may help to resolve the situation:\n\nThe following packages have unmet dependencies:\n python-ceph : Depends: python-cephfs (>= 12.2.13-0ubuntu0.18.04.11) but it is not going to be installed\n Depends: python-rados (>= 12.2.13-0ubuntu0.18.04.11) but it is not going to be installed\n Depends: python-rbd (>= 12.2.13-0ubuntu0.18.04.11) but it is not going to be installed\n", "stdout_lines": ["Reading package lists...", "Building dependency tree...", "Reading state information...", "Some packages could not be installed. This may mean that you have", "requested an impossible situation or if you are using the unstable", "distribution that some required packages have not yet been created", "or been moved out of Incoming.", "The following information may help to resolve the situation:", "", "The following packages have unmet dependencies:", " python-ceph : Depends: python-cephfs (>= 12.2.13-0ubuntu0.18.04.11) but it is not going to be installed", " Depends: python-rados (>= 12.2.13-0ubuntu0.18.04.11) but it is not going to be installed", " Depends: python-rbd (>= 12.2.13-0ubuntu0.18.04.11) but it is not going to be installed"]} python-ceph is not getting install due to dependencies: #vi /etc/ansible/roles/ceph_client/vars/debian.yml. python_ceph_packages: - python-ceph - python3-rados - python3-rbd I tried to update *python-ceph* with *python3-ceph* and the deployment was successful but the cinder-volume service is not coming up due to python error: #journalctl -u cinder-volume.service -f 2024-07-15 21:18:43.753 1277912 ERROR oslo_service.service [req-53d87e63-50ab-4976-b531-2b8ffdb82900 - - - - -] Error starting thread.: TypeError: expected bytes, str found 2024-07-15 21:18:43.753 1277912 ERROR oslo_service.service Traceback (most recent call last): 2024-07-15 21:18:43.753 1277912 ERROR oslo_service.service File "/openstack/venvs/cinder-20.2.6/lib/python3.6/site-packages/oslo_service/service.py", line 810, in run_service 2024-07-15 21:18:43.753 1277912 ERROR oslo_service.service service.start() 2024-07-15 21:18:43.753 1277912 ERROR oslo_service.service File "/openstack/venvs/cinder-20.2.6/lib/python3.6/site-packages/cinder/service.py", line 229, in start 2024-07-15 21:18:43.753 1277912 ERROR oslo_service.service service_id=Service.service_id) 2024-07-15 21:18:43.753 1277912 ERROR oslo_service.service File "/openstack/venvs/cinder-20.2.6/lib/python3.6/site-packages/cinder/volume/manager.py", line 444, in init_host 2024-07-15 21:18:43.753 1277912 ERROR oslo_service.service self._init_host(added_to_cluster, **kwargs) 2024-07-15 21:18:43.753 1277912 ERROR oslo_service.service File "/openstack/venvs/cinder-20.2.6/lib/python3.6/site-packages/cinder/volume/manager.py", line 478, in _init_host 2024-07-15 21:18:43.753 1277912 ERROR oslo_service.service self.driver.init_capabilities() 2024-07-15 21:18:43.753 1277912 ERROR oslo_service.service File "/openstack/venvs/cinder-20.2.6/lib/python3.6/site-packages/cinder/volume/driver.py", line 760, in init_capabilities 2024-07-15 21:18:43.753 1277912 ERROR oslo_service.service stats = self.get_volume_stats(True) 2024-07-15 21:18:43.753 1277912 ERROR oslo_service.service File "/openstack/venvs/cinder-20.2.6/lib/python3.6/site-packages/cinder/volume/drivers/rbd.py", line 643, in get_volume_stats 2024-07-15 21:18:43.753 1277912 ERROR oslo_service.service self._update_volume_stats() 2024-07-15 21:18:43.753 1277912 ERROR oslo_service.service File "/openstack/venvs/cinder-20.2.6/lib/python3.6/site-packages/cinder/volume/drivers/rbd.py", line 620, in _update_volume_stats 2024-07-15 21:18:43.753 1277912 ERROR oslo_service.service free_capacity, total_capacity = self._get_pool_stats() 2024-07-15 21:18:43.753 1277912 ERROR oslo_service.service File "/openstack/venvs/cinder-20.2.6/lib/python3.6/site-packages/cinder/volume/drivers/rbd.py", line 549, in _get_pool_stats 2024-07-15 21:18:43.753 1277912 ERROR oslo_service.service '{"prefix":"df", "format":"json"}', '') 2024-07-15 21:18:43.753 1277912 ERROR oslo_service.service File "rados.pyx", line 1067, in rados.Rados.mon_command 2024-07-15 21:18:43.753 1277912 ERROR oslo_service.service TypeError: expected bytes, str found 2024-07-15 21:18:43.753 1277912 ERROR oslo_service.service Regards, Danish Khan

2 5

[ops] [ec2-api] DB duplicate entry with ec2 list-images
by Massimo Sgaravatto 25 Jul '24

25 Jul '24

Dear all On a Yoga installation I see a problem with the ec2-api: [sgaravat@lxsgaravat ~]$ euca-describe-images -I ${EC2_ACCESS_KEY} -S ${EC2_SECRET_KEY} euca-describe-images: error (DBDuplicateEntry): Unknown error occurred. [sgaravat@lxsgaravat ~]$ In the log I see a duplicate entry errore [*] It's not fully clear to me what the problem is and why this query should add an entry in that table ... Any help is appreciated Thanks, Massimo PS: yes, I am aware that the ec2-api project is "dead" and not part of recent OpenStack distributions [*] 2024-07-25 14:49:11.052 37118 ERROR ec2api.api oslo_db.exception.DBDuplicateEntry: (pymysql.err.IntegrityError) (1062, "Duplicate entry '4ae7a803-d7cd-4725-8b2e-65797a64ef94' for key 'items.items_os_id_idx'") 2024-07-25 14:49:11.052 37118 ERROR ec2api.api [SQL: INSERT INTO items (id, project_id, vpc_id, os_id, data) VALUES (%(id)s, %(project_id)s, %(vpc_id)s, %(os_id)s, %(data)s)] 2024-07-25 14:49:11.052 37118 ERROR ec2api.api [parameters: {'id': 'ami-e561c280', 'project_id': '56c3f5c047e74a78a71438c4412e6e13', 'vpc_id': None, 'os_id': '4ae7a803-d7cd-4725-8b2e-65797a64ef94', 'data': '{"is_public": true}'}] 2024-07-25 14:49:11.052 37118 ERROR ec2api.api (Background on this error at: https://sqlalche.me/e/14/gkpj) 2024-07-25 14:49:11.052 37118 ERROR ec2api.api 2024-07-25 14:49:11.055 37118 ERROR ec2api.api [req-cda08c1a-009c-4c7d-b019-c30bce32baa4 9bd03f63fa9d4beb8de31e6c2f2c8d12 56c3f5c047e74a78a71438c4412e6e13 - - -] Environment: {"wsgi.url_scheme": "http", "REQUEST_METHOD": "POST", "SCRIPT_NAME": "", "RAW_PATH_INFO": "/services/Cloud", "PATH_INFO": "/services/Cloud", "CONTENT_TYPE": "application/x-www-form-urlencoded", "CONTENT_LENGTH": "53", "SERVER_PROTOCOL": "HTTP/1.0", "SERVER_NAME": "192.168.60.42", "SERVER_PORT": "8788", "REMOTE_ADDR": "192.168.60.229", "REMOTE_PORT": "33840", "GATEWAY_INTERFACE": "CGI/1.1", "HTTP_ACCEPT_ENCODING": "gzip, deflate", "HTTP_ACCEPT": "*/*", "HTTP_USER_AGENT": "euca2ools/3.4.1 (CPython 2.7.5; Linux 3.10.0-1160.92.1.el7.x86_64; x86_64) requestbuilder/0.7.1 requests/2.19.1", "HTTP_HOST": " cloud-areapd-test.pd.infn.it:8788", "HTTP_X_AMZ_CONTENT_SHA256": "afe617936fea90d9c62d9f87dd3e9d18e1fc5178d08aeebfb8737f32042a0b6d", "HTTP_X_AMZ_DATE": "20240725T124910Z", "HTTP_AUTHORIZATION": "AWS4-HMAC-SHA256 Credential=220cd4ffe5aa435cb56adfd5a9a3b234/20240725/undefined-15030/ec2/aws4_request, SignedHeaders=accept;accept-encoding;content-length;content-type;host;x-amz-content-sha256;x-amz-date, Signature=c0cc81d64a4477db4dc8be0d478b8746bb013f7273b6460f411d95a5d6efe946", "HTTP_X_FORWARDED_PROTO": "https", "HTTP_X_FORWARDED_FOR": "193.205.157.174", "HTTP_CONNECTION": "close"}: oslo_db.exception.DBDuplicateEntry: (pymysql.err.IntegrityError) (1062, "Duplicate entry '4ae7a803-d7cd-4725-8b2e-65797a64ef94' for key 'items.items_os_id_idx'") 2024-07-25 14:49:11.055 37118 INFO ec2api.api [req-cda08c1a-009c-4c7d-b019-c30bce32baa4 9bd03f63fa9d4beb8de31e6c2f2c8d12 56c3f5c047e74a78a71438c4412e6e13 - - -] 0.811724s 192.168.60.229 POST /services/Cloud DescribeImages 500 [euca2ools/3.4.1 (CPython 2.7.5; Linux 3.10.0-1160.92.1.el7.x86_64; x86_64) requestbuilder/0.7.1 requests/2.19.1] application/x-www-form-urlencoded text/xml 2024-07-25 14:49:11.056 37118 INFO ec2api.wsgi.server [req-cda08c1a-009c-4c7d-b019-c30bce32baa4 9bd03f63fa9d4beb8de31e6c2f2c8d12 56c3f5c047e74a78a71438c4412e6e13 - - -] 193.205.157.174,192.168.60.229 "POST /services/Cloud HTTP/1.1" status: 500 len: 348 time: 0.8139334 2024-07-25 14:49:14.391 37119 INFO ec2api.api [req-417ab595-646d-4468-9464-f19c7392c201 9bd03f63fa9d4beb8de31e6c2f2c8d12 56c3f5c047e74a78a71438c4412e6e13 - - -] 4.822310s 192.168.60.229 POST /services/Cloud DescribeInstances 200 [euca2ools/3.4.1 (CPython 2.7.5; Linux 3.10.0-1062.9.1.el7.x86_64; x86_64) requestbuilder/0.7.1 requests/2.19.1] application/x-www-form-urlencoded text/xml 2024-07-25 14:49:14.392 37119 INFO ec2api.wsgi.server [req-417ab595-646d-4468-9464-f19c7392c201 9bd03f63fa9d4beb8de31e6c2f2c8d12 56c3f5c047e74a78a71438c4412e6e13 - - -] 193.206.210.240,192.168.60.229 "POST /services/Cloud HTTP/1.1" status: 200 len: 11274 time: 4.8234410

1 0

[ironic] Call for maintainers: terraform-provider-ironic
by Dmitry Tantsur 25 Jul '24

25 Jul '24

Hi folks! In OpenShift, we used to use https://github.com/openshift-metal3/terraform-provider-ironic to drive Ironic and Inspector during the initial installation process before the control plane is up. Now that we have moved away from Terraform for this purpose, the project is on minimal support with the intention of completely abandoning it once no stable versions of OpenShift use it to provision the control plane. Are there any parties interested in maintaining terraform-provider-ironic after that point? It supports several features like inspection, BIOS settings, RAID. It does not, to the best of my knowledge, support Keystone authentication and has not been migrated away from Inspector. Dmitry

1 0

[cinder] No meeting today (7/24)
by Jon Bernard 24 Jul '24

24 Jul '24

Hello all, I failed in my effort to secure adequate childcare today, so I need to cancel today's meeting. Hope to see you in the next one. -- Jon

1 0

[horizon][puppet-openstack] Proper Python snippets placement
by Francesco Di Nucci 24 Jul '24

24 Jul '24

Hello, some time ago I found that on EL9 Horizon searches for extra Python snippets in "/usr/share/openstack-dashboard/openstack_dashboard/local/local_settings.d", while puppet-horizon places dashboards snippets in "/etc/openstack-dashboard/local_settings.d", so these are not loaded. At the same time, "/usr/share/openstack-dashboard/openstack_dashboard/local/local_settings.py" is a symlink to "/etc/openstack-dashboard/local_settings". Of the following, what should be adopted as proper approach on a machine? * Having symlinks to /etc/openstack-dashboard for both local_settings.py and local_settings.d * Editing files in /usr/share/openstack-dashboard without having symlinks * Using a symlink for local_settings.py but placing snippets under /usr/share/openstack-dashboard Best regards -- Francesco Di Nucci System Administrator Compute & Networking Service, INFN Naples Email:francesco.dinucci@na.infn.it

4 4

[kolla-ansible]Material choices for ephemerals
by Franck VEDEL 24 Jul '24

24 Jul '24

Hello. I would like your opinion regarding a hardware configuration and my Openstack cluster project. I have the possibility of purchasing 6 servers to build this cluster for students, my current Openstack being too small. I have a proposition from the manufacturer (DELL): 6 servers with characteristics per server: - BOSS-N1 controller card + with 2 M.2 960GB (RAID 1) - 5 x 3.84TB Data Center NVMe Read Intensive AG Drive U2 Gen4 with Carrier - 12 x 64GB RDIMM, 4800MT/s Dual Rank My problem is: BOSS is used to install the system (Ubuntu 22.04 in my case). But, various tests on a small cluster with SSD disks showed that the solution with ephemerals was really the most interesting for what I want to do. Problem: I don't believe you can have the system on the BOSS and the ephemerals on the NVMe disks. So my questions are: 1) am I wrong and ephemerals are possible on NVMe (I use kolla-ansible to deploy, I haven't seen how to do that)? 2) or the solution is to create a Ceph cluster on the NVME of the 6 servers 3) or a better solution exists Thank you in advance if you can help me make these choices. Franck

2 2

Unrestricted AC Access Rules: "You must upgrade keystonemiddleware on all services"
by openstack＠tr.id.au 24 Jul '24

24 Jul '24

Hey there, I'm interested in creating an unrestricted Application Credential (AC) which is still constrained by Access Rules. A use could be allowing admins to use automation to generate read-only ACs for various purposes. The AC for automatically generating other ACs would need to be unrestricted, but should still only have the minimal privileges required to create its children. However, when attempting this with multiple versions of keystone, including 2024.1, I get the following error in the keystone service log: ``` Attempted to use application credential access rules with a middleware that does not understand them. You must upgrade keystonemiddleware on all services that accept application credentials as an authentication method.: NoneType: None ``` A minimal way to reproduce this: 1. Install keystone according to https://docs.openstack.org/keystone/latest/install/keystone-install-ubuntu.…. (I've also tested with keystone running in a virtualenv and in a kolla container.) 2. Generate a "parent" AC using the bootstrap admin: `openstack application credential create --max-width 120 --role admin --access-rules '[ { "path": "/v3/**", "method": "POST", "service": "identity" }, { "path": "/v3/**", "method": "GET", "service": "identity" } ]' --expiration '2024-07-31T23:59:59' --unrestricted test_unrestricted` (This gives expected output, including an AC id and secret.) 3. In another terminal, load the parent AC and then try to generate the child: `openstack application credential create --max-width 120 --role admin --access-rules '[ { "path": "/v3/**", "method": "GET", "service": "identity" } ]' --expiration '2024-07-31T23:59:59' test_read_only`. (This returns `Invalid application credential: Cannot create an application credential with unassigned role` in the client, as well as the earlier error about upgrading middleware in keystone service log.) I've tested that the parent/unrestricted AC *can* generate the child successfully when the parent does *not* have Access Rules. I didn't see anything about these errors or constraints when going through the application credential documentation (eg https://docs.openstack.org/keystone/latest/user/application_credentials.html) or in a web search, or in a search of the openstack-discuss archives. I may raise a bug report/feature request, but before I do that, I just wondered if I have likely overlooked some possible extra configuration or documentation which could explain what I've done wrong? Alternatively, if this were raised as a feature request, would it likely be supported, or would the functionality I'm imagining be too difficult or impossible to implement? Cheers, Tim

1 0

Scheduler and filters
by Gk Gk 24 Jul '24

24 Jul '24

Hi, Can anyone tell me the difference between the schedulers and filters in nova. As per what I grasped, it seems we have the same type of weighers like schedulers. Then what's the difference ? Please explain.. Thanks Y.G

3 2

[OSSA-2024-002] OpenStack Nova: Incomplete file access fix and regression for QCOW2 backing files and VMDK flat descriptors (CVE-2024-40767)
by Jeremy Stanley 24 Jul '24

24 Jul '24

================================================================== OSSA-2024-002: Incomplete file access fix and regression for QCOW2 backing files and VMDK flat descriptors ================================================================== :Date: July 23, 2024 :CVE: CVE-2024-40767 Affects ~~~~~~~ - Nova: <27.4.1, >=28.0.0 <28.2.1, >=29.0.0 <29.1.1 Description ~~~~~~~~~~~ Arnaud Morin (OVH) reported a vulnerability in Nova. By supplying a raw format image which is actually a specially crafted QCOW2 image with a backing file path or VMDK flat image with a descriptor file path, an authenticated user may convince systems to return a copy of the referenced file’s contents from the server resulting in unauthorized access to potentially sensitive data. All Nova deployments are affected. Patches ~~~~~~~ - https://review.opendev.org/924734 (2023.1/antelope) - https://review.opendev.org/924733 (2023.2/bobcat) - https://review.opendev.org/924732 (2024.1/caracal) - https://review.opendev.org/924731 (2024.2/dalmatian) Credits ~~~~~~~ - Arnaud Morin from OVH (CVE-2024-40767) References ~~~~~~~~~~ - https://launchpad.net/bugs/2071734 - http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40767 Notes ~~~~~ - The patches linked above should apply cleanly to the public state of their respective branches at time of disclosure, and depend on some commits which merged after the `OSSA-2024-001 <https://security.openstack.org/ossa/OSSA-2024-001.html>`_ fixes as well as the final states of the Nova changes linked from that advisory (those did see some minor adjustments before they merged). - The QCOW2 issue is due to an incomplete fix in OSSA-2024-001 affecting systems where the ``use_cow_images`` configuration option is disabled, while the VMDK issue is a regression of the earlier `OSSA-2023-002 <https://security.openstack.org/ossa/OSSA-2023-002.html>`_ vulnerability reintroduced by the new implementation in OSSA-2024-001. Both problems were identified in the final hours before OSSA-2024-001 publication but, due to time constraints, were redacted from that bug and moved to a separate report. - Neither the methods introduced in these patches nor the fixes for OSSA-2024-001 are capable of blocking malicious images which are already resident in Nova's cache. At this time we do not have useful operator guidance for identifying and removing such existing images from the cache but strongly caution, if you do attempt to use the qemu-img tool to find them, to make sure you're using a version of it patched for `QEMU CVE-2024-4467 <https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-4467>`_. -- Jeremy Stanley OpenStack Vulnerability Management Team

1 0

[MAGNUM] Fedora Core OS include GPU drivers
by Oliver Weinmann 23 Jul '24

23 Jul '24

Hi all, I'm running OpenStack 2023.2 (Bobcat) deployed with Kolla-Ansible. Currently I'm struggling to get the NVIDIA drivers to work in a FCOS 35 image. I know FCOS 35 is EOL and outdated, but for a K8s 1.21.11 cluster it is the only version that still works with Magnum. So far I managed to get the GPU Passthrough working for two NVIDIA Tesla T4 GPUs. I have attached the GPUs to a Ubuntu instance and ran geekbench without any issues. Then I tried to install the latest NVIDIA drivers in FCOS 35 by running: sudo rpm-ostree install https://mirrors.rpmfusion.org/free/fedora/rpmfusion-free-release-$ (rpm -E %fedora).noarch.rpm https://mirrors.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-$ (rpm -E %fedora).noarch.rpm systemctl reboot rpm-ostree install --apply-live akmod-nvidia akmods pciutils rpmdevtools xorg-x11-drv-nvidia-cuda It fails on: rpm-ostree install --apply-live akmod-nvidia akmods pciutils rpmdevtools xorg-x11-drv-nvidia-cuda I guess the binaries are no longer hosted? Running the same on FCOS 36 and latest FCOS 40 works fine. Next I have taken new images from the FCOS instances with the NVIDIA driver. openstack server image create --name fedora_coreos_36_nvidia_cuda fedora_coreos_35_latest_no_update --wait This takes ages but anyway I can successfully deploy new instances from the images with my gpu flavor and the GPU is working fine. Again tested with geekbench. But now when adding new K8s worker nodes in a fresh nodegroup on an existing cluster 1.21.11 cluster the nodes are not joining the cluster: openstack coe nodegroup create \ --node-count 1 \ --role worker-gpu \ --flavor gpuflavor \ --image fedora_coreos_36_nvidia_cuda \ $CLUSTER_ID worker-gpu But I know from the past that FCOS 35 was the only version that was working fine with K8s 1.21.11. So I tried with FCOS 35 and this works fine, but unfortunately without the NVIDIA drivers. So maybe the problem is related to this and I need to get FCOS 35 working? Or a newer FCOS version? I'm also not sure if this is the best way of doing this. Maybe there is already a ready FCOS image with nvidia drivers? I can find lots of outdated information on the internet. Generally I tend to use Vexxhost CAPI from now on, which works great. This is really just a one off attempt to have a working NVIDIA T4 GPU in a K8s 1.21.11 cluster. Best Regards, Oliver

1 0

[Neutron] - Floating ip allocation in a specific subnet
by MIchele Delli Veneri 23 Jul '24

23 Jul '24

Dear all, My network setup includes a single external network (ext_vlan) with 2 subnets: 10.x.x.0/24 and 193.x.x.0/24. Is there a way to setup the allocation logic such as that given a project, all floating ips in the project are always allocated on one of the two subnets unless the subnet is explicited (as it may happen through the Openstack CLI or the admin horizon interface)? The ideal outcome would be, given the project test-project and test-project2 , that running openstack floating ip create —project test-project ext_vlan always allocate the floating ip on the 193.x.x subnet while openstack floating ip create —project test-project2 ext_vlan always allocates the floating ip on the 10.x.x. subnet. Best regards, Michele

4 4

Not able to find updated repos
by Ashok Thipe 23 Jul '24

23 Jul '24

Hi, We need to install latest community version of openstack but we are unable to get updated repositories. could anyone please help. With regards, Ashok Thipe

3 4

[cinder] How extend volume if cinder-volume host down
by Nguyễn Hữu Khôi 23 Jul '24

23 Jul '24

Hello guys. Every volume was managed by a specified host. When this host was down or removed. How Can I extend this volume which was managed by this host? I would like to know if we have a solution for this case? Nguyen Huu Khoi

2 4

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

23 Jul '24

Hello Stackers, As we get closer to the code freeze dates for the upcoming 2024.2 ("Dalmatian") release cycle [1], OpenStack project teams are finalizing features and bug fixes. We're ten weeks away from the official release date, but the feature freeze is squarely at halfway to that milestone. I'd like to share the governance changes that the OpenStack TC has approved in the past week. TC members joined several reviewers to approve the proposal to drop Eventlet from OpenStack [2]. Hervé Beraud (hberaud) and others will update the proposal further based on the feedback that was received through the review process. You may also see updates regarding this across Oslo and OpenStack service projects; and this may become an official community goal if we are able to close out on the feedback and agree upon a structure/timeline. I'd like to congratulate the Skyline team for having graduated from its "Emerging Project" status under the OpenStack services umbrella. In a similar vein, the Watcher project has been bootstrapped with a few new core maintainers and they have decided to adopt a "Distributed Project Maintainers" leadership model. We approved a request from the Freezer team to remain "inactive" as it builds back the contributor momentum necessary to churn out releases of its deliverables again. With the next OpenStack TC and PTL elections around the corner (nominations open on 2024-08-14 [3]), we updated the TC charter to clarify that changes proposed to documentation and governance repositories also qualify towards becoming an "Active Contributor" [4]. === Weekly Meeting === The last meeting of the OpenStack TC was held on IRC on 2024-07-16 [5]. We discussed CI instability and pending patches in Masakari and Adjutant. The project PTLs and maintainers responded to TC requests and have now addressed many concerns. We brainstormed gate issues in the past weeks, and difficulties getting all the patches concerning CVE-2024-32498 merged [6]. A constant theme seems to be test VM SSH connections failing within tests. Although this has been addressed a lot over the years and many changes have made the situation better, intermittent failures still remain. If you're interested in helping the OpenStack QA team with this, please let us know! We also discussed the goal proposal to drop Eventlet [2]. The proposal will require further work to be targeted as a goal. The next meeting of the OpenStack Technical Committee is on 2024-07-23. The agenda is on the OpenStack TC's wiki [7]. Please attend and voice your opinions! === Governance Proposals === ==== Merged ==== Update to include docs and miscellaneous repos for AC status | https://review.opendev.org/c/openstack/governance/+/915021 Move Skyline out from the "Emerging Projects" list | https://review.opendev.org/c/openstack/governance/+/924109 Remove Eventlet from OpenStack | https://review.opendev.org/c/openstack/governance/+/902585 Transition Watcher project to DPL | https://review.opendev.org/c/openstack/governance/+/923583 Inactive state extensions: Freezer | https://review.opendev.org/c/openstack/governance/+/923441 ==== Open for review/discussion ==== Follow up on the affiliation diversity handling | https://review.opendev.org/c/openstack/governance/+/923876 Update criteria for the 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 Retire kuryr-kubernetes and kuryr-tempest-plugin | https://review.opendev.org/c/openstack/governance/+/922507 === Upcoming Events === 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: OpenInfra Days, Vietnam: https://2024.vietopeninfra.org/ 2024-08-29: Dalmatian-3 milestone 2024-09-03: OpenInfra Summit Asia, Suwon I'll leave you with a link to the upbeat OpenInfra Summit welcome video featuring some of our APAC contributors: https://www.youtube.com/watch?v=aGuB1cf3DbY. 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] Goal to remove Eventlet from OpenStack: https://governance.openstack.org/tc/goals/proposed/remove-eventlet.html [3] OpenStack Elections: https://governance.openstack.org/election/ [4] Active Contributors: https://governance.openstack.org/tc/reference/charter.html#voters-for-tc-se… [5] TC Meeting IRC Logs, 2024-07-16: https://meetings.opendev.org/meetings/tc/2024/tc.2024-07-16-18.00.log.html [6] Arbitrary file access through custom QCOW2 external data (CVE-2024-32498): https://www.openwall.com/lists/oss-security/2024/07/02/2 [7] TC Meeting, 2024-07-23: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [8] OID North America Call for Proposals: https://docs.google.com/forms/d/1U3TokM5QWTe9_MJvKbOiDc_cNNW_LlFpOL3t-Loib1…

1 0

[neutron] Bug Deputy Report July 15 - July 21
by Miro Tomaska 23 Jul '24

23 Jul '24

Hello All, Here is the bug deputy report for the week of July 15th *Critical:* - https://bugs.launchpad.net/neutron/+bug/2073251 - linuxbridge/ovs jobs fails randomly as Test vms not getting ip from dhcp agent Assigned: Yatin Karel *High:* - https://bugs.launchpad.net/neutron/+bug/2073464 - [DHCP] Race condition when creating a network Assigned: Rodolfo Alonso - https://bugs.launchpad.net/neutron/+bug/2073567 [master][ml2-ovn] Multiple Unexpected exception in notify_loop: neutron_lib.exceptions.PortNotFound Unassigned - https://bugs.launchpad.net/neutron/+bug/2073585 - ubuntu focal jobs fails at dbcounter installation with TypeError: canonicalize_version() Unassigned, but Rodolfo Alonso already proposed a patch to lock down setup tools to v70.2.0 *Medium:* - https://bugs.launchpad.net/neutron/+bug/2073490 - [DHCP] Improve the DHCP agent log Assigned: Rodolfo Alonso - https://bugs.launchpad.net/neutron/+bug/2073309 Neither fdb_removal_limit or mac_binding_removal_limit get set in NB_Global.options when they are configured Assigned: Terry Wilson *Undecided:* - https://bugs.launchpad.net/neutron/+bug/2073326 - ovn] OVSDB Error ' references nonexistent' occurs when updating one router. Most likely will get closed as an unsupported and modified branch is being used. Move to "won't fix"? - https://bugs.launchpad.net/neutron/+bug/2073509 - east and west traffic is not allowed/blocked with neutron fwaas v2 Involves Neutron fwaas, simple reproducing steps but need to confirm if this even a valid bug or is it by design. -- Miro Tomaska Senior Software Engineer

1 0

Kolla deploy
by William Muriithi 23 Jul '24

23 Jul '24

Hello, What could I be doing wrong here? When we attempt openstack deploy, this step fails with the error message below? kolla-ansible -i /etc/kolla/multinode deploy debug3: mux_client_request_alive: done pid = 91641 debug3: mux_client_request_session: session request sent debug1: mux_client_request_session: master session id: 2 debug3: mux_client_read_packet: read header failed: Broken pipe debug2: Received exit status from master 1 The full traceback is: File "/tmp/ansible_kolla_container_payload_xai740dx/ansible_kolla_container_payload.zip/ansible/modules/kolla_container.py", line 425, in main File "/tmp/ansible_kolla_container_payload_xai740dx/ansible_kolla_container_payload.zip/ansible/module_utils/kolla_podman_worker.py", line 515, in recreate_or_restart_container self.start_container() File "/tmp/ansible_kolla_container_payload_xai740dx/ansible_kolla_container_payload.zip/ansible/module_utils/kolla_podman_worker.py", line 538, in start_container self.create_container() File "/tmp/ansible_kolla_container_payload_xai740dx/ansible_kolla_container_payload.zip/ansible/module_utils/kolla_podman_worker.py", line 501, in create_container container = self.pc.containers.create(**args) File "/usr/local/lib/python3.9/site-packages/podman/domain/containers_create.py", line 354, in create response.raise_for_status(not_found=ImageNotFound) File "/usr/local/lib/python3.9/site-packages/podman/api/client.py", line 75, in raise_for_status raise APIError(cause, response=self._response, explanation=message) fatal: [ostack-40.openstack.perasotech.com] FAILED! => { "changed": true, "invocation": { "module_args": { "action": "recreate_or_restart_container", "api_version": "auto", "auth_email": null, "auth_password": null, "auth_registry": "quay.io", "auth_username": null, "client_timeout": 120, "container_engine": "podman", "detach": true, "dimensions": { "ulimits": {} }, "environment": { "KOLLA_CONFIG_STRATEGY": "COPY_ALWAYS" }, "graceful_timeout": 60, "ignore_missing": false, "image": "quay.io/openstack.kolla/fluentd:master-rocky-9", "labels": {}, "name": "fluentd", "privileged": false, "remove_on_exit": true, "restart_policy": "unless-stopped", "restart_retries": 10, "security_opt": [], "state": "running", "tls_verify": false, "tty": false } }, "msg": "'Traceback (most recent call last):\\n File \"/tmp/ansible_kolla_container_payload_xai740dx/ansible_kolla_container_payload.zip/ansible/modules/kolla_container.py\", line 425, in main\\n File \"/tmp/ansible_kolla_container_payload_xai740dx/ansible_kolla_container_payload.zip/ansible/module_utils/kolla_podman_worker.py\", line 515, in recreate_or_restart_container\\n self.start_container()\\n File \"/tmp/ansible_kolla_container_payload_xai740dx/ansible_kolla_container_payload.zip/ansible/module_utils/kolla_podman_worker.py\", line 538, in start_container\\n self.create_container()\\n File \"/tmp/ansible_kolla_container_payload_xai740dx/ansible_kolla_container_payload.zip/ansible/module_utils/kolla_podman_worker.py\", line 501, in create_container\\n container = self.pc.containers.create(**args)\\n File \"/usr/local/lib/python3.9/site-packages/podman/domain/containers_create.py\", line 354, in create\\n response.raise_for_status(not_found=ImageNotFound)\\n File \"/usr/local/lib/python3.9/site-packages/podman/api/client.py\", line 75, in raise_for_status\\n raise APIError(cause, response=self._response, explanation=message)\\npodman.errors.exceptions.APIError: 500 Server Error: Internal Server Error (statfs /var/log/journal: no such file or directory)\\n'" } Have anyone see the issue before? Regards, William

2 3

[cinder][glance]Errors with patch bug/2059809
by Nguyễn Hữu Khôi 22 Jul '24

22 Jul '24

Hello, i encounter this error when apply patch about bug/2059809: raise exception.ImageConversionNotAllowed( 2024-07-20 03:35:28.067 736 ERROR oslo_messaging.rpc.server cinder.exception.ImageConversionNotAllowed: Image Conversion disallowed for image 7bacbdfb-2ea3-4ed8-90ad-3ec0e274a1d9: Image conversion is disabled. The volume type you have requested requires that the image it is being created from be in 'raw' format, but the image you are using has the disk_format property 'qcow2'. You must use an image with the disk_format property 'raw' to create a volume of this type. I am using Zed version. Could I have some suggestions? Thank you. Nguyen Huu Khoi

5 14

Kolla-Fluentd: not found: manifest unknown
by Ashok Thipe 22 Jul '24

22 Jul '24

Hi, I'm trying to deploy openstack using Kolla-ansible and encountering following error: 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.9/site-packages/docker/api/client.py\", line 268, in _raise_for_status\\n response.raise_for_status()\\n File \"/usr/local/lib/python3.9/site-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.46/images/create?tag=master-centos-stream9&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_7owwfp32/ansible_kolla_container_payload.zip/ansible/modules/kolla_container.py\", line 425, in main\\n File \"/tmp/ansible_kolla_container_payload_7owwfp32/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_7owwfp32/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.9/site-packages/docker/api/image.py\", line 429, in pull\\n self._raise_for_status(response)\\n File \"/usr/local/lib/python3.9/site-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.9/site-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.46/images/create?tag=master-centos-stream9&fromImage= quay.io%2Fopenstack.kolla%2Ffluentd: Not Found (\"manifest for quay.io/openstack.kolla/fluentd:master-centos-stream9 not found: manifest unknown: manifest unknown\")\\n'"} ansible version used: ansible [core 2.15.12] Kolla-ansible version: kolla-ansible@master OS: CentOS 9 stream Please suggest workaround for the above issue. Thanks and regards, Ashok Thipe

2 1

encountering repos metadata issue during overcloud deployment
by Ashok Thipe 22 Jul '24

22 Jul '24

Hi, I'm trying to deploy openstack (zed version) using tripleo method and encountering "error while loading metadata for repos: centos 8" issue during running overcloud deployment. If there are any possible solutions this issue/bug, please care to share. With regards, Ashok Thipe

3 3

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

21 Jul '24

Dear OpenStack Community, I am currently working with OpenStack Kolla Ansible 2023.1 1.setting up Trove instances as per the documentation https://docs.openstack.org/trove/2023.1/admin/building_guest_images.html Despite following the steps outlined, I am encountering some issues. Image Not Found: I followed the steps it downloads the required packages and it creates the image directory. However, the trove image is not present in the specified path $HOME/images. 2.I have also referred to https://satishdotpatel.github.io/trove-dbaas-openstack/ and followed each step, but below issue persists. Error with Messaging and Volume Configuration: While creating a Trove instance, I encountered the following errors: ERROR oslo.messaging._drivers.impl_rabbit [-] Failed to declare consumer for topic 'guestagent.01a5cdd0-df3c-4f61-817f-114b530a1bb3': Queue.declare: (406) PRECONDITION_FAILED - inequivalent arg 'x-queue-type' for queue 'guestagent.01a5cdd0-df3c-4f61-817f-114b530a1bb3' in vhost '/': received the value 'quorum' of type 'longstr' but current is none guest-agent[802]: 2024-07-01 09:24:13.831 802 ERROR trove.guestagent.volume [-] Volume '/dev/vdb' was not formatted.: oslo_concurrency.processutils.ProcessExecutionError: Unexpected error while running command. Steps Taken: Created and configured images as per the OpenStack documentation. Ensured that all Trove-related configurations are properly set up. Verified RabbitMQ configurations to avoid direct configurations and used Trove’s trove-guestagent configuration for managing RabbitMQ settings. /etc/kolla/config/trove.conf [DEFAULT] management_networks = ee2a2a81-178c-4d79-867b-8baf53ec236d nova_keypair = trove-ssh-key management_security_groups = 451e4b4a-58b4-4e9f-84a8-5bdb21e34cd5 /etc/kolla/config/trove-guestagent.conf [DEFAULT] transport_url = rabbit://openstack:<RABBITMQ_PASSWORD>@192.168.8.14:5672,openstack:<RABBITMQ_PASSWORD>@192.168.8.15:5672,openstack:<RABBITMQ_PASSWORD>@192.168.8.16:5672// control_exchange = trove root_grant = ALL root_grant_option = True debug = False [oslo_messaging_rabbit] heartbeat_in_pthread = false amqp_durable_queues = true rabbit_quorum_queue = true Request for Assistance: Are there any other recommended methods to build the Trove guest image if the documented steps do not work? Is there a known core issue related to the errors I am encountering with oslo.messaging and trove.guestagent.volume? What specific configurations or logs should I check to resolve these errors? Any additional steps or best practices for setting up Trove instances with Kolla Ansible? Thank you in advance for your help. Any insights or suggestions to resolve these issues would be greatly appreciated. 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."

2 2