- openstack-discuss - lists.openstack.org

[DIB][diskimage-builder] Debian Testing boot issues
by Michael Still 18 Jan '23

18 Jan '23

Has anyone else tried building Debian Testing (bookworm) images with DIB? I'm having troubles with getting them to boot, with errors that look like missing components in the initrd to me. The command I am using to build is: export ELEMENTS_PATH=elements:diskimage-builder/diskimage_builder/elements export DIB_CLOUD_INIT_DATASOURCES="ConfigDrive, OpenStack, NoCloud" export DIB_APT_MINIMAL_CREATE_INTERFACES=0 export DIB_PYTHON_VERSION=3 export DIB_RELEASE=bookworm export DIB_SF_AGENT_PACKAGE=shakenfist-agent export build_args="cloud-init cloud-init-datasources sf-agent vm" disk-image-create utilities debian debian-systemd ${build_args} -o temp.qcow2 Where shakenfist-agent / sf-agent are a custom element not really relevant to this query (I've left it for completeness). When I boot the output image, I get this: ... [ 1.906949] virtio_blk virtio2: 2/0/0 default/read/poll queues [ 1.908318] virtio_blk virtio2: [vda] 104857600 512-byte logical blocks (53.7 GB/50.0 GiB) [ 1.916912] vda: vda1 [ 1.917646] virtio_blk virtio3: 2/0/0 default/read/poll queues [ 1.917676] virtio_net virtio1 ens11: renamed from eth0 [ 1.918965] virtio_blk virtio3: [vdb] 184 512-byte logical blocks (94.2 kB/92.0 KiB) Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... done. Warning: fsck not present, so skipping root file system [ 2.024351] EXT4-fs (vda1): mounted filesystem with ordered data mode. Quota mode: none. done. Begin: Running /scripts/local-bottom ... [ 2.041352] EXT4-fs (vda1): unmounting filesystem. GROWROOT: WARNING: resize failed: failed [flock:127] flock -x 9 /sbin/growpart: line 714: flock: not found FAILED: Error while obtaining exclusive lock on /dev/vda [ 2.057556] vda: vda1 /scripts/local-bottom/growroot: line 97: wait-for-root: not found done. Begin: Running /scripts/init-bottom ... mount: mounting /dev on /root/dev failed: No such file or directory mount: mounting /dev on /root/dev failed: No such file or directory done. mount: mounting /run on /root/run failed: No such file or directory BusyBox v1.35.0 (Debian 1:1.35.0-4+b1) multi-call binary. Usage: run-init [-d CAP,CAP...] [-n] [-c CONSOLE_DEV] NEW_ROOT NEW_INIT [ARGS] Free initramfs and switch to another root fs: chroot to NEW_ROOT, delete all in /, move NEW_ROOT to /, execute NEW_INIT. PID must be 1. NEW_ROOT must be a mountpoint. -c DEV Reopen stdio to DEV after switch -d CAPS Drop capabilities -n Dry run Target filesystem doesn't have requested /sbin/init. BusyBox v1.35.0 (Debian 1:1.35.0-4+b1) multi-call binary. Usage: run-init [-d CAP,CAP...] [-n] [-c CONSOLE_DEV] NEW_ROOT NEW_INIT [ARGS] Free initramfs and switch to another root fs: chroot to NEW_ROOT, delete all in /, move NEW_ROOT to /, execute NEW_INIT. PID must be 1. NEW_ROOT must be a mountpoint. ... Which looks to me like I am missing fsck, flock and wait-for-root, probably in the initrd? Adding cloud-init-growpart and growroot as elements did not help, neither did ensuring that the image contained cloud-guest-utils or util-linux. I wonder if anyone else has seen this and has some hints? Thanks, Michael

1 0

Difficulties Developing a Horizon Customization Module
by Adam Cooper 18 Jan '23

18 Jan '23

Hello! I sent a message to the #openstack IRC last week, but did not receive any replies. I am attempting to create a customization module for Horizon and having difficulties getting things to function. I'm on a fork of the Xena release, and following these docs: https://docs.openstack.org/horizon/9.1.1/topics/customizing.html. At the present, I'm trying to figure out some weird behavior where having the file `openstack_dashboard/local/local_settings.py` causes Horizon to respond to every request with a 400 error. There is no information regarding this in the logs or the HTTP response as far as I can see. It does this with an empty module, or if it just contains HORIZON_CONFIG = {...}. Is there something I'm missing? I would just like to be able to debug this issue so I can actually develop the module. If this is not the right way to ask for help, I would appreciate a pointer to the correct channels. Thanks! -- Adam Cooper Cloud Computing Engineer, Security Point of Contact Chameleon Cloud University of Chicago, Argonne National Laboratory

1 0

[OSSA-2023-001] Swift: Arbitrary file access through custom S3 XML entities (CVE-2022-47950)
by Jeremy Stanley 17 Jan '23

17 Jan '23

=================================================================== OSSA-2023-001: Arbitrary file access through custom S3 XML entities =================================================================== :Date: January 17, 2023 :CVE: CVE-2022-47950 Affects ~~~~~~~ - Swift: <2.28.1, >=2.29.0 <2.29.2, ==2.30.0 Description ~~~~~~~~~~~ Sébastien Meriot (OVH) reported a vulnerability in Swift's S3 XML parser. By supplying specially crafted XML files an authenticated user may coerce the S3 API into returning arbitrary file contents from the host server resulting in unauthorized read access to potentially sensitive data; this impacts both s3api deployments (Rocky or later), and swift3 deployments (Queens and earlier, no longer actively developed). Only deployments with S3 compatibility enabled are affected. Patches ~~~~~~~ - https://review.opendev.org/870823 (2023.1/antelope) - https://review.opendev.org/870828 (Wallaby) - https://review.opendev.org/870827 (Xena) - https://review.opendev.org/870826 (Yoga) - https://review.opendev.org/870825 (Zed) Credits ~~~~~~~ - Sébastien Meriot from OVH (CVE-2022-47950) References ~~~~~~~~~~ - https://launchpad.net/bugs/1998625 - http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-47950 Notes ~~~~~ - The stable/wallaby branch is under extended maintenance and will receive no new point releases, but a patch for it is provided as a courtesy. -- Jeremy Stanley OpenStack Vulnerability Management Team

1 0

Re: Experience with VGPUs (Tobias Urdin)
by Karl Kloppenborg 17 Jan '23

17 Jan '23

Hi Tobias, I saw your message, interesting method to get around the transient mdev issue. Have you looked into implementing cyborg as a method to alleviate this? We are currently assessing it for a different project using nvidia A40’s. Would be keen to swap war stories and see if we can make a better solution than the current vGPU mdev support going on. Kind Regards, Karl. You can book a 30-minute meeting with me by clicking this link.<https://calendly.com/karl_rwts/30min> -- Karl Kloppenborg, Systems Engineering (BCompSc, CNCF-[KCNA, CKA, CKAD], LFCE, CompTIA Linux+ XK0-004) Real World Technology Solutions - IT People you can trust Voice | Data | IT Procurement | Managed IT rwts.com.au<http://rwts.com.au> | 1300 798 718 [uc%3fexport=download&id=1M0bR7j1-rXl-e7k5f1Rhwot6K_vfuAvn&revid=0B4fBbZ0cwq-1WFdQSExlR28rOEtUanJjOGcvQnJjMFhEMlEwPQ] Real World is a DellEMC Gold Partner This document should be read only by those persons to whom it is addressed and its content is not intended for use by any other persons. If you have received this message in error, please notify us immediately. Please also destroy and delete the message from your computer. Any unauthorised form of reproduction of this message is strictly prohibited. We are not liable for the proper and complete transmission of the information contained in this communication, nor for any delay in its receipt. Please consider the environment before printing this e-mail. From: openstack-discuss-request(a)lists.openstack.org <openstack-discuss-request(a)lists.openstack.org> Date: Tuesday, 17 January 2023 at 9:06 pm To: openstack-discuss(a)lists.openstack.org <openstack-discuss(a)lists.openstack.org> Subject: openstack-discuss Digest, Vol 51, Issue 51 Send openstack-discuss mailing list submissions to openstack-discuss(a)lists.openstack.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss or, via email, send a message with subject or body 'help' to openstack-discuss-request(a)lists.openstack.org You can reach the person managing the list at openstack-discuss-owner(a)lists.openstack.org When replying, please edit your Subject line so it is more specific than "Re: Contents of openstack-discuss digest..." Today's Topics: 1. Re: Enable fstrim automatically on cinder thin lvm provisioning (Rajat Dhasmana) 2. Re: Experience with VGPUs (Tobias Urdin) 3. Re: [designate] Proposal to deprecate the agent framework and agent based backends (Thomas Goirand) 4. Re: Experience with VGPUs (Sylvain Bauza) ---------------------------------------------------------------------- Message: 1 Date: Tue, 17 Jan 2023 10:11:27 +0530 From: Rajat Dhasmana <rdhasman(a)redhat.com> To: A Monster <amonster369(a)gmail.com> Cc: openstack-discuss <openstack-discuss(a)lists.openstack.org> Subject: Re: Enable fstrim automatically on cinder thin lvm provisioning Message-ID: <CAARK8KQ3rM9KSQ9vFP+CAVPL_xAksxfXvFuvZj8gd7FeFT6LTw(a)mail.gmail.com> Content-Type: text/plain; charset="utf-8" Hi, We've a config option 'report_discard_supported'[1] which can be added to cinder.conf that will enable trim/unmap support. Also I would like to suggest not creating new openstack-discuss threads for the same issue and reuse the first one created. As I can see these are the 3 threads for the same issue[2][3][4]. [1] https://docs.openstack.org/cinder/latest/configuration/block-storage/config… [2] https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031789… [3] https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031797… [4] https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031805… Thanks Rajat Dhasmana On Tue, Jan 17, 2023 at 8:57 AM A Monster <amonster369(a)gmail.com> wrote: > I deployed openstack using kolla ansible, and used LVM as storage backend > for my cinder service, however I noticed that the lvm thin pool size keeps > increasing even though the space used by instances volumes is the same, and > after a bit of investigating I found out that I had to enable fstrim > because the data deleted inside the logical volumes was still allocated > from the thin pool perspective and I had to do fstrim on those volumes, > > how can I enable this automatically in openstack? >

1 0

Enable fstrim automatically on cinder thin lvm provisioning
by A Monster 17 Jan '23

17 Jan '23

I deployed openstack using kolla ansible, and used LVM as storage backend for my cinder service, however I noticed that the lvm thin pool size keeps increasing even though the space used by instances volumes is the same, and after a bit of investigating I found out that I had to enable fstrim because the data deleted inside the logical volumes was still allocated from the thin pool perspective and I had to do fstrim on those volumes, how can I enable this automatically in openstack?

2 1

When is client-side modified being added?
by Adisa Nicholson aka Tynamite 17 Jan '23

17 Jan '23

Hello Openstack When is client-side modified being added as a new feature? Right now I'm paying for file hosting and when I upload a file, the "date modified" isn't respected for that file. It always takes the "date modified" for the file as the current date, not the one on the file I was uploading from my computer. I've contacted the company I brought it from, and they said that client-side modified isn't supported in the Openstack API <https://docs.openstack.org/swift/latest/s3_compat.html>. What API method would this be exactly? Would it be the "object tagging" method? Do you lot have any idea when this feature would be added in, so my file uploads will respect the "date modified" metadata?

1 0

[kolla] where to find docker compose files
by garcetto 17 Jan '23

17 Jan '23

good afternoon, where can i find docker compose files for quay,io docker images used in kolla-ansible? need to undestand how are build, thank you.

2 1

Cinder LVM backend shows 100% space usage
by A Monster 16 Jan '23

16 Jan '23

I deployed openstack using kolla ansible using LVM as a backend, but after using it for a while, I ended up creating multiple volume with different sizes, but now I can no longer create new volumes, after checking lvs I found out that the thin pool created by cinder displays a 100% space usage of 20TB , but the size used by the volumes created is less than 1TB. how can I fix this isse?

1 0

Re: [Heat][OpenStack-I18n] Need help in making sense of a message in Heat
by Ian Y. Choi 16 Jan '23

16 Jan '23

(Adding openstack-discuss mailing list and adding "[Heat]" on the subject) Hi, It would be so great if OpenStack Heat users or developers can help Juliette's question on i18n thread! Thank you all, /Ian On Fri, Jan 13, 2023 at 11:39 PM Juliette Tux <juliette.tux(a)gmail.com> wrote: > > Hello, > Could anybody kindly elaborate on the meaning of a condition in a message: > > "The flag which represents condition of reserved resources of the > lease. If it is true, the amount of reserved resources is less than > the request or reserved resources were changed." > > The obscure part for me is "less than the request or reserved > resources were changed." > > Context: heat/engine/resources/openstack/blazar/lease.py:233 > > TY! > > -- > С уважением, Дронова Юлия > > _______________________________________________ > OpenStack-I18n mailing list > OpenStack-I18n(a)lists.openstack.org

3 2

[neutron] Bug Deputy Report January 9 - 15
by Lucas Alvares Gomes 16 Jan '23

16 Jan '23

Hi, This is the Neutron bug report from January 9th to 15th. *Critical:* * https://bugs.launchpad.net/neutron/+bug/2002800 - "Allow multiple IPv6 ports on router from same network on ml2/ovs+vxlan+dvr" - Assigned to: Fernando Royo *High:* * https://bugs.launchpad.net/neutron/+bug/2002417 - "DVR+HA routers all answering to ping on private interface" - Assigned to: Arnaud Morin *Needs further triage:* * https://bugs.launchpad.net/neutron/+bug/2002577 - "The neutron-keepalived-state-change.log log is not rotated and grows without bound until disk is full" - Unassigned *Low:* * https://bugs.launchpad.net/neutron/+bug/2002839 - "Remove compatibility with OVN<20.09" - Unassigned *RFE / Wishlist:* * https://bugs.launchpad.net/neutron/+bug/2002687 - "[RFE] Active-active L3 Gateway with Multihoming" - Assigned to: Dmitrii Shcherbakov Cheers, Lucas

1 0

[skyline][i18n] Questions on more language translation support
by Ian Y. Choi 16 Jan '23

16 Jan '23

Hi Skyline team and I18n contributors, First, Skyline team, thank you for considering skyline with i18n! As Seongsoo started to talk via skyline IRC channel [1], I see that there are some needs for more language support for the Skyline project. Let me elaborate through the following questions as current I18n SIG lead: 1. Skyline team: While I believe you are welcome to contribute to other languages by adding per-language json files like [2], is it okay to contribute Korean language through Korea User Group members? Me and/or Seongsoo would like to happily step up as reviewers to guarantee sufficient language quality. 2. Any translation interests from other I18n language teams? Feel free to tell me or reply to this thread. 3. While number 1 would be a short-term approach to add Korean language support, to support more international languages, I want to suggest integrating with react-intl if skyline is using react (from my brief investigation, it is yes through [3]), since react-intl support to convert json <-> pot which functionality was previously used by tripleo-ui for i18n support [4]. Although I18n SIG is trying to migrate from Zanata to Weblate, a new translation platform [5], pot support would be essential for standardizing i18n and the translation process. With many thanks, /Ian [1] https://meetings.opendev.org/irclogs/%23openstack-skyline/%23openstack-skyl… [2] https://github.com/openstack/skyline-console/tree/master/src/locales [3] https://opendev.org/openstack/skyline-console/src/branch/master/package.jso… [4] https://opendev.org/openstack/tripleo-ui/src/commit/d1baef537f0746efceacfdd… [5] https://lists.openstack.org/pipermail/openstack-i18n/2022-October/003559.ht…

2 1

[kolla] [cinder] cinder.exception.NoValidBackend
by A Monster 16 Jan '23

16 Jan '23

I deployed openstack yoga using kolla ansible, and used LVM as a backend for cinder storage service, after the deployment everything was working fine, but after a month, I could no longer create a volume as I get an error message > schedule allocate volume:Could not find any available weighted backend. > and the cinder_scheduler log shows the following error message > ERROR cinder.scheduler.flows.create_volume > [req-2290223d-8f96-48d7-8680-959c5932d5be 3b4bd66ca3b04ab587a9a64a9e6966bc > ec29bdcd73064dfb8186f413537327eb - - -] Failed to run task > cinder.scheduler.flows.create_volume.ScheduleCreateVolumeTask;volume:create: > No valid backend was found. No weighed backends available: > cinder.exception.NoValidBackend: No valid backend was found. No weighed > backends available > the storage server doesn't show any apparent errors, any ideas of how can I fix this?

2 1

[Openstack Tacker] - Issue while creating NS
by Lokendra Rathour 16 Jan '23

16 Jan '23

Hi Team, Was trying to create NS using the document : https://docs.openstack.org/tacker/yoga/user/nsd_usage_guide.html But getting an error, the bug has been opened, requesting your kind assistance. https://bugs.launchpad.net/tacker/+bug/1999502 thanks once again. -- ~ Lokendra skype: lokendrarathour

2 1

Destroy a specific service from an openstack kolla deployment
by A Monster 15 Jan '23

15 Jan '23

Is it possible to remove a specific service from openstack, using > > kolla-ansible destroy -i multinode --tag service destroys all service and doesn't take into consideration the tag parameter.

1 0

Minimum Number Of Nodes for Deployment
by Nazmul Haque (N&C, SIL) 15 Jan '23

15 Jan '23

Hi, We are exploring various open source cloud platform. We are currently running Nutanix for our private cloud infrastructure. We would like to explore Openstack. Currently we have two clusters , one with 5 nodes and another with 3 nodes. In order to deploy two Openstack clusters what is the minimum number of nodes required for a private cloud infrastructure ensuring high availability and data integrity in mind. I will pursue the COA course however I want to have some background from industry experts since I am under the impression that Openstack deployment would require a lot of nodes for initial deployment which would be very expensive. Regards, Md Nazmul Haque Disclaimer: This e-mail, including any attachment with it may contain privileged, proprietary & confidential information and is intended solely for the addressee. If you are not the intended recipient of this e-mail, please notify us immediately and destroy this email without taking any copies or showing it to anyone. Unauthorized use of this e-mail is prohibited. SQUARE will not take any responsibility for misdirection, corruption or unauthorized use of e-mail communications, or for any damage that may be caused as a result of transmitting or receiving an e-mail communication. Caution: Do not click links or open attachments unless you recognize the sender and know the content is safe.

1 0

[all][tc] What's happening in Technical Committee: summary 2023 Jan 13: Reading: 5 min
by Ghanshyam Mann 14 Jan '23

14 Jan '23

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Jan 11. Most of the meeting discussions are summarized in this email. Meeting logs are available @ https://meetings.opendev.org/meetings/tc/2023/tc.2023-01-11-16.00.log.html * The next TC weekly meeting will be on Jan 18 Wed at 16:00 UTC, Feel free to add the topic to the agenda[1] by Jan 17. 2. What we completed this week: ========================= * Nothing specific for this week. 3. Activities In progress: ================== TC Tracker for the 2023.1 cycle ------------------------------------- * Current cycle working items and their progress are present in the 2023.1 tracker etherpad[2]. Open Reviews ----------------- * Five open reviews for ongoing activities[3]. Cleanup of PyPI maintainer list for OpenStack Projects ---------------------------------------------------------------- The horizon team discussed the 'xstatic-font-awesome' repo PyPi maintainer topic[4] in the weekly meetings[5], As the next step, they will be discussing it with PyPi non-OpenStack maintainers for the possible option to do the maintenance in a single place (either in OpenStack or outside of OpenStack). TC continued the discussion for all other repo/developers' PyPi maintainer cleanup. knikolla will be automating to get the list of deliverables that need PyPi maintainer's cleanup and after that TC will reach out to the respective project PTL to do the audit if we can cleanup those directly or need some more discussion with external maintainers (like 'xstatic-font-awesome' case) if there is any. We will continue this topic discussion in TC next weekly meeting also. Project updates ------------------- * Add Cinder Huawei charm[6] * Add the woodpecker charm to Openstack charms[7] Less Active/Inactive projects: ~~~~~~~~~~~~~~~~~~~~~~ * Zaqar status Zaqar gate is broken due to the MongoDB package not being present in Ubuntu 22.04 which is used for testing in 2023.1 cycle. Zaqar's team knows about the issue and discusses the same[8]. The TC is discussing and reaching out to the PTL about it. The release team is waiting to get a clear situation on the activeness/gate fix of this project so that they can decide on its release for 2023.1 cycle. It is also proposed to be marked as Inactive[9]. TC will continue the discussion with the Zaqar team and take the next action soon. * Mistral status: The Mistral team is actively merging the gate fixes[10], python-mistralclient gate is facing more issue which is being looked at by the Mistral team. The release team is trying the beta release patches for mistral deliverables[11][12] * Adjutant Status The Adjutant gate is green and its beta release is done[13][14]. With that, Dale proposed to remove this project from the Inactive project list[15] which has a positive response from the TC review. Thanks, Dale to make this project active again. 4. How to contact the TC: ==================== If you would like to discuss or give feedback to TC, you can reach out to us in multiple ways: 1. Email: you can send the email with tag [tc] on openstack-discuss ML[16]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15:00 UTC [17] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Agenda_Suggesti… [2] https://etherpad.opendev.org/p/tc-2023.1-tracker [3] https://review.opendev.org/q/projects:openstack/governance+status:open [4] https://github.com/openstack/xstatic-font-awesome/pull/2 [5] https://meetings.opendev.org/meetings/horizon/2023/horizon.2023-01-11-15.00… [6] https://review.opendev.org/c/openstack/governance/+/867588 [7] https://review.opendev.org/c/openstack/governance/+/869752 [8] https://review.opendev.org/c/openstack/zaqar/+/857924/comments/a0d5d45e_300… [9] https://review.opendev.org/c/openstack/governance/+/870098 [10] https://review.opendev.org/q/project:openstack/mistral [11] https://review.opendev.org/c/openstack/releases/+/869470 [12] https://review.opendev.org/c/openstack/releases/+/869448 [13] https://review.opendev.org/c/openstack/releases/+/869449 [14] https://review.opendev.org/c/openstack/releases/+/869471 [15] https://review.opendev.org/c/openstack/governance/+/869665 [16] hhttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [17] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[neutron] Drivers meeting cancelled today
by Rodolfo Alonso Hernandez 13 Jan '23

13 Jan '23

Hello Neutrinos: Due to the lack of agenda [1], today's meeting is cancelled. Have a nice weekend! [1]https://wiki.openstack.org/wiki/Meetings/NeutronDrivers

1 0

[horizon]
by Nguyễn Hữu Khôi 13 Jan '23

13 Jan '23

Hello guys. I use Openstack Xena which deployed by Kolla Ansible.My problem is when I launch instance from Horizon, Port selection won't show as below pictures: [image: image.png] [image: image.png] I try to change browser but this problem still persists Any suggestions for me? Thank you. Regards. Nguyen Huu Khoi

2 2

RuntimeError: The expected HostnameMap and RoleHostnameFormat are not defined in data file: /home/stack/dcn01/dcn01_overcloud-baremetal-deployed.yaml | Openstack wallaby | tripleo | centos 8 stream
by Swogat Pradhan 13 Jan '23

13 Jan '23

Hi, INFO: Openstack wallaby on centos 8 stream I am trying to deploy a DCN and during the ceph deploy command i am getting the following error: (undercloud) [stack@hkg2director dcn01]$ openstack overcloud ceph deploy dcn01_overcloud-baremetal-deployed.yaml --stack dcn01 --config initial-ceph.conf --output deployed_ceph.yaml --container-image-prepare containers-prepare-parameter.yaml --network-data custom_network_data.yaml --cluster dcn01 --roles-data dcn01_roles.yaml -vvv The full traceback is: Traceback (most recent call last): File "/tmp/ansible_ceph_spec_bootstrap_payload_c4o_1q1y/ansible_ceph_spec_bootstrap_payload.zip/ansible/modules/ceph_spec_bootstrap.py", line 241, in get_deployed_roles_to_hosts UnboundLocalError: local variable 'matching_hosts' referenced before assignment During handling of the above exception, another exception occurred: Traceback (most recent call last): File "<stdin>", line 102, in <module> File "<stdin>", line 94, in _ansiballz_main File "<stdin>", line 40, in invoke_module File "/usr/lib64/python3.6/runpy.py", line 205, in run_module return _run_module_code(code, init_globals, run_name, mod_spec) File "/usr/lib64/python3.6/runpy.py", line 96, in _run_module_code mod_name, mod_spec, pkg_name, script_name) File "/usr/lib64/python3.6/runpy.py", line 85, in _run_code exec(code, run_globals) File "/tmp/ansible_ceph_spec_bootstrap_payload_c4o_1q1y/ansible_ceph_spec_bootstrap_payload.zip/ansible/modules/ceph_spec_bootstrap.py", line 500, in <module> File "/tmp/ansible_ceph_spec_bootstrap_payload_c4o_1q1y/ansible_ceph_spec_bootstrap_payload.zip/ansible/modules/ceph_spec_bootstrap.py", line 471, in main File "/tmp/ansible_ceph_spec_bootstrap_payload_c4o_1q1y/ansible_ceph_spec_bootstrap_payload.zip/ansible/modules/ceph_spec_bootstrap.py", line 246, in get_deployed_roles_to_hosts RuntimeError: The expected HostnameMap and RoleHostnameFormat are not defined in data file: /home/stack/dcn01/dcn01_overcloud-baremetal-deployed.yaml 2023-01-13 01:27:15.811878 | 48d539a1-1679-ea57-d54d-000000000013 | FATAL | Create Ceph spec based on baremetal_deployed_path and tripleo_roles | undercloud | error={ "changed": false, "module_stderr": "Traceback (most recent call last):\n File \"/tmp/ansible_ceph_spec_bootstrap_payload_c4o_1q1y/ansible_ceph_spec_bootstrap_payload.zip/ansible/modules/ceph_spec_bootstrap.py\", line 241, in get_deployed_roles_to_hosts\nUnboundLocalError: local variable 'matching_hosts' referenced before assignment\n\nDuring handling of the above exception, another exception occurred:\n\nTraceback (most recent call last):\n File \"<stdin>\", line 102, in <module>\n File \"<stdin>\", line 94, in _ansiballz_main\n File \"<stdin>\", line 40, in invoke_module\n File \"/usr/lib64/python3.6/runpy.py\", line 205, in run_module\n return _run_module_code(code, init_globals, run_name, mod_spec)\n File \"/usr/lib64/python3.6/runpy.py\", line 96, in _run_module_code\n mod_name, mod_spec, pkg_name, script_name)\n File \"/usr/lib64/python3.6/runpy.py\", line 85, in _run_code\n exec(code, run_globals)\n File \"/tmp/ansible_ceph_spec_bootstrap_payload_c4o_1q1y/ansible_ceph_spec_bootstrap_payload.zip/ansible/modules/ceph_spec_bootstrap.py\", line 500, in <module>\n File \"/tmp/ansible_ceph_spec_bootstrap_payload_c4o_1q1y/ansible_ceph_spec_bootstrap_payload.zip/ansible/modules/ceph_spec_bootstrap.py\", line 471, in main\n File \"/tmp/ansible_ceph_spec_bootstrap_payload_c4o_1q1y/ansible_ceph_spec_bootstrap_payload.zip/ansible/modules/ceph_spec_bootstrap.py\", line 246, in get_deployed_roles_to_hosts\nRuntimeError: The expected HostnameMap and RoleHostnameFormat are not defined in data file: /home/stack/dcn01/dcn01_overcloud-baremetal-deployed.yaml\n", "module_stdout": "", "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", "rc": 1 } (undercloud) [stack@hkg2director dcn01]$ cat /home/stack/dcn01/dcn01_overcloud-baremetal-deployed.yaml parameter_defaults: DeployedServerPortMap: dcn01-hci-0-ctlplane: fixed_ips: - ip_address: 172.25.221.96 dcn01-hci-1-ctlplane: fixed_ips: - ip_address: 172.25.221.90 dcn01-hci-2-ctlplane: fixed_ips: - ip_address: 172.25.221.106 HCICount: 3 HCIHostnameFormat: '%stackname%-hci-%index%' HostnameMap: dcn01-hci-0: dcn01-hci-0 dcn01-hci-1: dcn01-hci-1 dcn01-hci-2: dcn01-hci-2 NodePortMap: dcn01-hci-0: ctlplane: ip_address: 172.25.221.96 ...> Can someone please tell me what could be the issue here?? Am I missing something? With regards, Swogat Pradhan

1 1

[ironic] Bugfix branches being EOL'd first week of Jan, 2023
by Jay Faulkner 13 Jan '23

13 Jan '23

OpenStack Community and Operators, As documented in https://specs.openstack.org/openstack/ironic-specs/specs/approved/new-relea…, Ironic performs bugfix releases in the middle of a cycle to permit downstream packagers to more rapidly deliver features to standalone Ironic users. However, we've neglected as a project to cleanup or EOL any of these branches -- until now. Please take notice that during the first week in January, we will be EOL-ing all old, unsupported Ironic bugfix branches. This will be handled similarly to an EOL of a stable branch; we will create a tag -- e.g. for bugfix/x.y branch, we would tag bugfix-x.y-eol -- then remove the branch. These branches have been out of support for months and should not be in use in your Ironic clusters. If you are using any branches slated for retirement, please immediately upgrade to a supported Ironic version. A full listing of projects and branches impacted: ironic branches being retired bugfix/15.1 bugfix/15.2 bugfix/16.1 bugfix/16.2 bugfix/18.0 bugfix/20.0 ironic-python-agent branches being retired bugfix/6.2 bugfix/6.3 bugfix/6.5 bugfix/6.6 bugfix/8.0 bugfix/8.4 ironic-inspector branches being retired bugfix/10.2 bugfix/10.3 bugfix/10.5 bugfix/10.10 Thank you, Jay Faulkner Ironic PTL

1 4

[ironic] Moving Aija to core-emeritus
by Jay Faulkner 13 Jan '23

13 Jan '23

Hi all, As many of you may already know, Aija is no longer actively working on OpenStack. She informed many Ironic cores over email of this last week. I asked her if she expected to contribute on her own time and she said no. In order to ensure we keep core reviewer lists up to date, I suggest we move Aija to core-emeritus status, removing core permissions from gerrit. If she decides to begin working on OpenStack again in the future, we'd obviously quickly return core permissions. What do you think? -- Jay Faulkner Ironic PTL TC Member P.S. A huge thanks to Aija for her hard work on the sushy project and the Dell driver in Ironic.

6 6

Overriding tox's install_command won't work for non-service projects
by Stephen Finucane 12 Jan '23

12 Jan '23

Another tox 4 PSA. It turns out the tox 3 was not using the command in '[tox] install_command' when installing the package under test. tox 4 does, which means overriding '[tox] install_command' to include a constraints file (-c) will prevent you installing any requirement that is listed in the upper-constraints file, even if said requirement is the thing you're currently working on. This applies to all libraries (e.g. oslo.db, python-cinderclient) but not the services (cinder, nova) since those aren't included in upper-constraints. The "correct" way to respect upper-constraints is to provide them in 'deps' alongside the requirements file(s), e.g. [testenv] deps = -c{env:UPPER_CONSTRAINTS_FILE:https://releases.openstack.org/constraints/upper/master} -r{toxinidir}/requirements.txt -r{toxinidir}/test-requirements.txt This will cause tox to install all of the package's dependencies first *with* constraints before installing the package itself *without constraints*. There is a bug report open against pip to change this behaviour [1], but it's been sat there for over two years with no activity so I wouldn't rely on this. Stephen [1] https://github.com/pypa/pip/issues/7839

2 3

Issue resizing volumes attached to running volume backed instances
by Jérôme BECOT 12 Jan '23

12 Jan '23

Hello Openstack, We have Ussuri deployed on a few clouds, and they're all plugged to PureStorage Arrays. We allow users to only use volumes for their servers. It means that each server disk is a LUN attached over ISCSI (with multipath) on the compute node hosting the server. Everything works quite fine, but we have a weird issue when extending volumes attached to running instances. The guests notice the new disk size .. of the last extent. Say I have a server with a 10gb disk. I add 5gb. On the guest, still 10gb. I add another 5gb, and on the guest I get 15, and so on. I've turned the debug mode on and I could see no error in the log. Looking closer at the log I could catch the culprit: 2022-12-08 17:35:13.998 46195 DEBUG os_brick.initiator.linuxscsi [] Starting size: *76235669504* 2022-12-08 17:35:14.028 46195 DEBUG os_brick.initiator.linuxscsi [] volume size after scsi device rescan *80530636800* extend_volume 2022-12-08 17:35:14.035 46195 DEBUG os_brick.initiator.linuxscsi [] Volume device info = {'device': '/dev/disk/by-path/ip-1...1:3260-iscsi-iqn.2010-06.com.purestorage:flasharray.x-lun-10', 'host': '5', 'channel': '0', 'id': '0', 'lun': '10'} extend_volume 2022-12-08 17:35:14.348 46195 INFO os_brick.initiator.linuxscsi [] Find Multipath device file for volume WWN 3624... 2022-12-08 17:35:14.349 46195 DEBUG os_brick.initiator.linuxscsi [] Checking to see if /dev/disk/by-id/dm-uuid-mpath-3624.. exists yet. wait_for_path 2022-12-08 17:35:14.349 46195 DEBUG os_brick.initiator.linuxscsi [] /dev/disk/by-id/dm-uuid-mpath-3624... has shown up. wait_for_path 2022-12-08 17:35:14.382 46195 INFO os_brick.initiator.linuxscsi [] mpath(/dev/disk/by-id/dm-uuid-mpath-3624) *current size 76235669504* 2022-12-08 17:35:14.412 46195 INFO os_brick.initiator.linuxscsi [] mpath(/dev/disk/by-id/dm-uuid-mpath-3624) *new size 76235669504* 2022-12-08 17:35:14.413 46195 DEBUG oslo_concurrency.lockutils [] Lock "extend_volume" released by "os_brick.initiator.connectors.iscsi.ISCSIConnector.extend_volume" :: held 2.062s inner 2022-12-08 17:35:14.459 46195 DEBUG os_brick.initiator.connectors.iscsi [] <== extend_volume: return (2217ms) *76235669504* trace_logging_wrapper 2022-12-08 17:35:14.461 46195 DEBUG nova.virt.libvirt.volume.iscsi [] Extend iSCSI Volume /dev/dm-28; new_size=*76235669504* extend_volume 2022-12-08 17:35:14.462 46195 DEBUG nova.virt.libvirt.driver [] Resizing target device /dev/dm-28 to *76235669504* _resize_attached_volume The logs clearly shows that the rescan confirm the new size but when interrogating multipath, it does not. But requesting multipath few seconds after on the command line shows the new size as well. It explains the behaviour. I'm running Ubuntu 18.04 with multipath 0.7.4-2ubuntu3.2. The os-brick code for multipath is far more basic than the one in master branch. Maybe the multipath version installed is too recent for os-brick. Thanks for the help Jerome

2 2

[CI][Tempest] Broken tempest-full-multinode-py3 job
by Lukas Piwowarski 12 Jan '23

12 Jan '23

Hi, I've got stuck trying to figure out why one of our tempest jobs is failing. I will be grateful for any kind of input regarding potential solutions. I did a little investigation of the failing job (tempest-multinode-full-py3 [1][2]) and this is what I found: - The failure is mostly caused by scenario tests. There was one occurrence of failure outside of the scenario tests ( test_create_servers_on_different_hosts_with_list_of_servers) - The failure is always connected to the creation of a VM. The reasons for the failure differ but most of the time it looks like the VM gets created but tempest is not able to access it ("Authentication (publickey) failed.") or the created instance can not be found ("Instance f4e582fe-52e6-40e3-b366-2b11ed589089 could not be found.") - The failure is not connected to one specific test. I am wondering why only the multinode job is failing as in other jobs the scenario tests are passing fine. Thanks for any kind of help Lukáš Piwowarsk [1] https://ca077a96786c794b51b6-8aab0ff599dd9fcfda722d0dee6871dd.ssl.cf5.rackc… [2] https://review.opendev.org/c/openstack/tempest/+/866692

1 0

[openstack][nova][kvm] numa
by Ignazio Cassano 12 Jan '23

12 Jan '23

Hello All, I would like to know if with numa in kvm hypervisor I must disable merge across nodes ? If yes, is there any metadata to do it ? Ignazio

2 2