- openstack-discuss - lists.openstack.org

[cinder] Bug Report from 01-18-2023
by Sofia Enriquez 18 Jan '23

18 Jan '23

This is a bug report from 01-11-2022 to 01-18-2023. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- High - https://bugs.launchpad.net/cinder/+bug/2003179 "Dell PowerFlex: password appears in plain text when creating a volume from an image." Unassigned. Medium - https://bugs.launchpad.net/cinder/+bug/2002535 "[NFS] Server resize failed when image volume cache enabled." Assigned to Jean Pierre Roquesalane. - https://bugs.launchpad.net/cinder/+bug/2002996 "storpool driver: drop the image-to-volume-and-back overridden methods." Unassigned. - https://bugs.launchpad.net/cinder/+bug/2002995 "storpool driver: fix the retype volume flow." Fix proposed to master. Cheers, -- Sofía Enriquez she/her Software Engineer Red Hat PnT <https://www.redhat.com> IRC: @enriquetaso @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com>

1 0

[cinder] 2023.1 R-9 virtual mid cycle on 18th January, 2023
by Rajat Dhasmana 18 Jan '23

18 Jan '23

Hello Argonauts, As discussed in yesterday's cinder upstream meeting[1], we will be conducting our second mid cycle on 18th January, 2023 (R-9 week). Following are the details: Date: 18th January 2023 Time: 1400-1600 UTC Meeting link: https://bluejeans.com/556681290 Etherpad: https://etherpad.opendev.org/p/cinder-antelope-midcycles Don't forget to add topics and see you there! [1] https://meetings.opendev.org/meetings/cinder/2023/cinder.2023-01-11-14.00.l… Thanks Rajat Dhasmana

1 1

[neutron] The meetings "ping list"
by Rodolfo Alonso Hernandez 18 Jan '23

18 Jan '23

Hello Neutrinos: As suggested by some community members, we now have a "ping list" for our Neutron meetings. If you want to be pinged just before the meeting starts, you can add your IRC nickname to the meeting agenda, in the "ping list" paragraph. As commented during the Neutron meeting, this is only a courtesy ping. Please check the meeting agendas: * Neutron meeting: https://wiki.openstack.org/wiki/Network/Meetings * CI meeting: https://etherpad.opendev.org/p/neutron-ci-meetings * Drivers meeting: https://wiki.openstack.org/wiki/Meetings/NeutronDrivers If you can't edit the agenda meetings, you can request that to any Neutron core in the #openstack-neutron channel. Regards.

2 1

[all][tc] Technical Committee next weekly meeting on 2023 Jan 18 at 1600 UTC
by Ghanshyam Mann 18 Jan '23

18 Jan '23

Hello Everyone, The technical Committee's next weekly meeting is scheduled for 2023 Jan 18, at 1600 UTC. If you would like to add topics for discussion, please add them to the below wiki page by Tuesday, Jan 17 at 2100 UTC. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting -gmann

1 1

[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 18 Jan '23

18 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