- openstack-discuss - lists.openstack.org

[swift][s3api] put-object-acl in SLO objects
by Thiago De Moraes Teixeira 12 Mar '24

12 Mar '24

Hi, I've got this error when trying to put acl in objects that are a multipart upload with s3api client. *aws s3api put-object-acl --bucket ramac --key darwin --acl public-readAn error occurred (BadDigest) when calling the PutObjectAcl operation (reached max retries: 4): The Content-MD5 you specified did not match what we received.* And for objects greater than 5Gb the error is: *An error occurred (EntityTooLarge) when calling the PutObjectAcl operation: Your proposed upload exceeds the maximum allowed object size.* I noticed this is happening because s3 middleware did not recognize this object as an SLO, so when the request reaches the ServerSideCopyMiddleware, the request did not have the query param "multipart-manifest". I tried this swift patch, to solve this problem, identifying if the object is an SLO, on head object in acl_handlers.py class, and retrieving this information before request transformation to swift_request, adding the query param. While this patch resolves the immediate issue, I believe there's room for improvement. I welcome any suggestions or feedback on enhancing this patch further. Your insights would be greatly appreciated. https://paste.openstack.org/show/bd2nAHIHPtUtDNbWLorD/ Best regards -- _‘Esta mensagem é direcionada apenas para os endereços constantes no cabeçalho inicial. Se você não está listado nos endereços constantes no cabeçalho, pedimos-lhe que desconsidere completamente o conteúdo dessa mensagem e cuja cópia, encaminhamento e/ou execução das ações citadas estão imediatamente anuladas e proibidas’._ * **‘Apesar do Magazine Luiza tomar todas as precauções razoáveis para assegurar que nenhum vírus esteja presente nesse e-mail, a empresa não poderá aceitar a responsabilidade por quaisquer perdas ou danos causados por esse e-mail ou por seus anexos’.*

1 0

[swift][middleware][s3] Content-type of s3api versioning response
by m.victorello＠luizalabs.com 12 Mar '24

12 Mar '24

Hello, We are having some compatibility problems caused by the lack of content-type in this part: https://github.com/openstack/swift/blob/5e5fde12400fc76b9df43b3fcd13eb8a226… def GET(self, req): """ Handles GET Bucket versioning. """ sysmeta = req.get_container_info(self.app).get('sysmeta', {}) elem = Element('VersioningConfiguration') if sysmeta.get('versions-enabled'): SubElement(elem, 'Status').text = ( 'Enabled' if config_true_value(sysmeta['versions-enabled']) else 'Suspended') body = tostring(elem) return HTTPOk(body=body, content_type=None) Is there a reason for it?

1 0

[swift][s3][multipart] S3 multipart re-upload leaves orphan segments
by m.victorello＠luizalabs.com 12 Mar '24

12 Mar '24

Hello, I understand that this is a known issue for some time, but I dont know if it has been resolved. As far as I know stable/2023.2 still has this problem, is there any related work? We think there are two fronts: - Segments of incomplete multipart, forgotten by the user - Completed re-uploads We plan to fix those: - Using the object-expirer in a new middleware - Deploying workers to review all files, checking if they are still in use What are your thoughts?

1 0

[kolla-ansible] Building images from source
by wodel youchi 11 Mar '24

11 Mar '24

Hi, I am trying to build kolla's container images from source, especially octavia's images. I've read the kolla-build documentation, then I tried to follow along but I am having some problems. I am not a developper, my goal is to be able to push patches to kolla images if something goes wrong. For example now I am having a problem with octavia not being able to create an LB when using a self-signed certificate. I searched and I found a patch and I wanted to test-it. https://bugs.launchpad.net/kolla-ansible/+bug/2046382 https://launchpadlibrarian.net/706867161/octavia.patch Here are the steps I followed : - I am using podman - I've created a local registry - pyhton3.9 -m venv kollavnenv/2023.2 - source kollavnenv/2023.2/bin/activate - pip install kolla - pip install podman - I downloaded octavia source code from git 2023.2 version - https://github.com/openstack/octavia/tree/stable/2023.2 - I've prepared kolla_build.conf like this - [octavia] type = local location = /root/work/octavia - And I started the build like this - kolla-build --registry 192.168.2.35:4000 --push -b rocky --tag 2023.2-1 --engine podman --config-file ./kolla_build.conf octavia - Results - (2023.2) [root@r9localrepo work]# podman images REPOSITORY TAG IMAGE ID CREATED SIZE 192.168.2.35:4000/kolla/octavia-driver-agent 2023.2-1 1a6217ad71b4 22 minutes ago 1.31 GB 192.168.2.35:4000/kolla/octavia-api 2023.2-1 41ad8e1760a2 22 minutes ago 1.31 GB 192.168.2.35:4000/kolla/octavia-health-manager 2023.2-1 4922b7f0259f 22 minutes ago 1.28 GB 192.168.2.35:4000/kolla/octavia-housekeeping 2023.2-1 8b5a4785fc18 22 minutes ago 1.28 GB 192.168.2.35:4000/kolla/octavia-worker 2023.2-1 46107a14e78d 22 minutes ago 1.28 GB 192.168.2.35:4000/kolla/octavia-base 2023.2-1 23963c04eda7 22 minutes ago 1.28 GB 192.168.2.35:4000/kolla/openstack-base 2023.2-1 add627cfde2f 25 minutes ago 1.14 GB 192.168.2.35:4000/kolla/base 2023.2-1 a8299a02411a 29 minutes ago 580 MB <none> <none> 0421c38fd25c 8 hours ago 1.14 GB docker.io/library/registry 2 a8781fe3b7a2 6 weeks ago 26 MB quay.io/rockylinux/rockylinux 9 da830f5e2510 3 months ago 181 MB - The problem : - When exploring the octavia-api images for example (podman save),* and verifying the modified file I didn't find the patched-code* It seems that the build process is not using the local code? What am I missing? I think that my kolla_build.conf is wrong or not complete ... any ideas? Regards.

1 2

[kolla-ansible][2023.2] Cloudkitty support for Openseach?
by wodel youchi 11 Mar '24

11 Mar '24

Hi, Does Cloudkitty now support Opensearch as a storage backend in kolla? Regards.

2 1

[oslo][release][requirements] RFE for tooz and taskflow
by Takashi Kajinami 11 Mar '24

11 Mar '24

Hello, During this cycle we updated the redis support implementations to support authentication and SSL for redis sentinel, following the new implementation in oslo.cache. However later it turned out this change breaks kolla because it has been using redis sentinel without authentication while it enables authentication in redis[1]. I've submitted the changes[2] to restore the old behavior (not to enable AUTH or SSL for sentinel even when one is enabled in redis). Once these are merged in master then I'll propose backports to stable/2024.1 and propose new stable/2024.1 release. I'd like to request approval about the release and also bumping tooz and taksflow version in stable/2024.1 requirements to unblock kolla and any other deployments using the partial authentication for redis sentinel. Thank you, Takashi [1] https://bugs.launchpad.net/python-tooz/+bug/2056656 [2] https://review.opendev.org/c/openstack/taskflow/+/912346 https://review.opendev.org/c/openstack/tooz/+/912344/ -- Takashi Kajinami irc: tkajinam github: https://github.com/kajinamit launchpad: https://launchpad.net/~kajinamit

3 3

[neutron] Bug deputy report Mar 4th to 10th
by Oleg Bondarev 11 Mar '24

11 Mar '24

Hello Neutron Team, Bug report for the week of March 4 is below: High: - https://bugs.launchpad.net/neutron/+bug/2055876 - [ovn-octavia-provider] OVN LB health checks for IPv6 not working - in progress: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/911413 - assigned to froyoredhat Medium: - https://bugs.launchpad.net/neutron/+bug/2056199 - ``DvrDriver`` and ``OvnDriver`` incorrectly define distributed flag - fix released: https://review.opendev.org/c/openstack/neutron/+/911151 - fixed by rodolfo-alonso-hernandez - https://bugs.launchpad.net/neutron/+bug/2056276 - unmaintained/yoga periodic jobs broken - confirmed - assigned to yatinkarel - https://bugs.launchpad.net/neutron/+bug/2056366 - Neutron ml2/ovn does not exit when killed with SIGTERM - in progress: https://review.opendev.org/c/openstack/neutron/+/911625 - assigned to otherwiseguy - https://bugs.launchpad.net/neutron/+bug/2056537 - [ovn-octavia-provider] gateway chassis not filled on LogicalRouterPort event - in progress - assigned to froyoredhat - https://bugs.launchpad.net/neutron/+bug/2056558 - ``OVNL3RouterPlugin._port_update`` can be called before the LRP is created in the OVN DB - in progress: https://review.opendev.org/c/openstack/neutron/+/912349 - assigned to rodolfo-alonso-hernande Low: - https://bugs.launchpad.net/neutron/+bug/2055886 - [FT] Check port binding object in "test_virtual_port_host_update_upon_failover" - fix released: https://review.opendev.org/c/openstack/neutron/+/910941 - fixed by rodolfo-alonso-hernandez Thanks, Oleg

1 0

[kolla-ansible][2023.2] Manila cephFS NFS ganesha need some clarifications
by wodel youchi 10 Mar '24

10 Mar '24

Hi, I am trying to configure Manila with cephsfs NFS as backend. My first problem is with installing and configuring nfs ganesha : - Do I have to deploy nfs ganesha from ceph? - What about the /etc/ganesha/ganesha.conf config file? Could someone give me some steps to follow... Regards.

3 11

deploy error
by Parsa Aminian 09 Mar '24

09 Mar '24

hello I want to add new compute to my kolla ansible but i gave this error : TASK [nova-cell : Get a list of existing cells] ****************************************************************************************************************** fatal: [R6SC15.cpaas.ir -> control01]: FAILED! => {"msg": "The conditional check 'existing_cells_list.rc != 0' failed. The error was: error while evaluating conditional (existing_cells_list.rc != 0): 'dict object' has no attribute 'rc'"} can anyone help me whats the problem ?

1 0

[neutron][horizon] disable permission to release floating ip for non-admin users
by Satish Patel 09 Mar '24

09 Mar '24

Folks, I want to disable permission or the horizon button or whatever best way to not allow end users to "Release floating IP" because I want them to stick with assigned IP and not releasing them because of some regulatory process. Not sure what is the best way to have this level of control. I found neutron policy delete_floatingip: but is this the correct way to implement this policy? OR Does Horizon have some level of ACL to remove buttons or disable it? Looking for advice or clues. Thanks!

3 2