- openstack-discuss - lists.openstack.org

[security-sig] PTG schedule
by Jeremy Stanley 07 Jun '23

07 Jun '23

I've booked a PTG table for the two "slots" immediately prior to Thursday's lunch break (11:00-12:50 Vancouver time). See https://ptg.opendev.org/etherpads.html for a link to the notepad for it; I've added some ideas for things we could do or discuss but add anything you'd like to cover and I'm happy to pivot based on attendee interest. Given the timing, we can also turn it into an early lunch outing or whatever. -- Jeremy Stanley

1 0

[manila] Cancelling June 8th and June 15th weekly meetings
by Carlos Silva 07 Jun '23

07 Jun '23

Hello, Since June 8th is a holiday in some countries and that will impact the weekly meeting's attendance numbers, we are cancelling this meeting. The weekly meeting of June 15th is also being cancelled, as some members will be attending the OpenInfra Summit. The next upstream weekly meeting will be on June 22nd. Regards, carloss

1 0

[manila][ptg] Vancouver PTG
by Carlos Silva 07 Jun '23

07 Jun '23

Hello, zorillas and interested stackers. In the previous weekly meeting I mentioned the tentative time slot for next week's PTG and I got confirmation. We will host a hybrid session for our PTG on Thursday 9:40AM to 12:10 PM PDT. More details about the location, topics and connecting to the meeting bridge will be available in the PTG etherpad [1]. You can still add your topics until Friday (June 9th) to the etherpad. [1] https://etherpad.opendev.org/p/manila-openinfra-2023 Regards, carloss

1 0

[all][ops][rbac] RBAC feedback sessions in Vancouver Summit
by Ghanshyam Mann 07 Jun '23

07 Jun '23

Hello Everyone, If you are planning to attend Vancouver Summit, we will have a forum discussion on Tuesday to provide the RBAC updates and collect operators' feedback. "OpenStack RBAC: updates & operators feedback" - Tue, June 13, 1:45pm - 2:15pm | Vancouver Convention Centre - Room 9 I have created the etherpad to collect the feedback, feel free to write your feedback if you cannot attend this session. - https://etherpad.opendev.org/p/rbac-operator-feedback-vancouver2023 -gmann

1 0

[cinder] Vancouver PTG scheduling
by Brian Rosmaita 07 Jun '23

07 Jun '23

Hello Vancouver-bound Argonauts, In trying to put together a doodle pool, I found it was way easier to just use an etherpad. So please navigate on over to it and block out your unavailability before the Cinder Spec Review meeting at 1400 UTC on Friday 9 June. https://etherpad.opendev.org/p/vancouver2023-cinder-ptg-scheduling thanks, brian

1 0

Question About BGP Dynamic Routing, Floating IP, and SNAT
by Alex Z 07 Jun '23

07 Jun '23

Hi Everyone, Hope you are all doing well. I’m a beginner to Openstack and Neutron and now run into an issue about SNAT and shared floating IP. I’ve already deployed a neutron network which uses BGP to announce floating IP to PE (Provider Edge router), and everything works as expected when I assign the public floating IP (e.g., 123.0.0.10/24) to VMs. But when I tried to use floating IP port-forwarding function with floating IP 123.0.0.20/24 and rule (internal_ip 10.10.10.10, internal_port 5555, external_port 64000), and assign a private IP (10.10.10.10/24) to a VM. The floating IP 123.0.0.20 won’t be advertised through BGP. May I have some suggestions about how I could get this fixed, or the neutron just won’t work this way? FYI, 1. Per my understanding, the port_forwardings rule will make the port act like a SNAT role and forward any packets that reach it with destination 123.0.0.20:64000 to the private IP 10.10.10.10/24. 2. The IP address could be reached in the neutron network. 3. PE IP address, CE IP address, and floating IP gateway are using the same subnet A and subnet pool (192.168.123.0/24), while floating IP belongs to subnet B and subnet pool (123.0.0.0/24), both subnets belong to the provider network. 4. Only floating IP that assigned to the specific VM will be advertised to PE through BGP 5. Floating IP that is assigned to the port of a router in the neutron network won’t be advertised, even if the IP is activated and is reachable internally. Sincerely, Alex

1 0

[i18n] upstream investment: translations infrastructure engineer
by Brian Rosmaita 07 Jun '23

07 Jun '23

I've proposed an OpenStack "upstream investment opportunity" for an engineer to handle the Zanata -> Weblate re-plumbing for gerrit/zuul: https://review.opendev.org/c/openstack/governance/+/885379 Please leave comments if you have any. cheers, brian

1 0

Cinder Bug Report 2023-06-07
by Sofia Enriquez 07 Jun '23

07 Jun '23

Hello Argonauts, Cinder Bug Meeting Etherpad <https://etherpad.opendev.org/p/cinder-bug-squad-meeting> *Medium* - Volume creation fails if an old signature is found when using the LVM driver. <https://bugs.launchpad.net/cinder/+bug/2023073> - *Status*: Unassigned. - LIO target doesn't support discard on thin volumes. <https://bugs.launchpad.net/cinder/+bug/2023168> - *Status*: Fix proposed to master. <https://review.opendev.org/c/openstack/cinder/+/885451> *Low* - Cinder PowerMax driver volume attach/detach hang issues. <https://bugs.launchpad.net/cinder/+bug/2021999> - *Status*: Fix proposed to master <https://review.opendev.org/c/openstack/cinder/+/884957>. - Huawei Oceanstor volume driver is not up to date with official Huawei's driver <https://bugs.launchpad.net/cinder/+bug/2022152>. - *Status*: Please propose the topic to the cinder meeting <https://wiki.openstack.org/wiki/CinderMeetings>. *Incomplete* - [huawei] wrong hostname passed to os_brick. <https://bugs.launchpad.net/cinder/+bug/2017575> - *Status*: Waiting on <hillpd> keep the conversation on the Launchpad bug or propose a WIP patch to discuss the changes on the patch. -- 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

[nova][ptg][ops] Please collect your thoughs and wishlists for the Forum and the PTG !
by Sylvain Bauza 07 Jun '23

07 Jun '23

Hey folks and especially operators, As a reminder, we will have multiple opportunities during the next week for discussing about some topics : - we will have on Tuesday a general 30-min contributors Meet&Greet Forum session where operators and developers will be. If you want to attend this session and you have some questions or if you want to explain about your problems, you can provide those in the meet&greet etherpad : https://etherpad.opendev.org/p/nova-vancouver2023-meet-and-greet - we will also have a 2-day PTG on Wednesday and Thursday where operators and contributors on a table (#24) can discuss about everything that's in the physical PTG agenda that we will have in the below etherpad : https://etherpad.opendev.org/p/vancouver-june2023-nova The more we are able to collect insights, the better the Summit will be. Thanks folks and hope to see the most of you in Vancouver face-to-face ! -Sylvain

1 0

[kolla] IRC meeting cancelled today
by Bartosz Bezak 07 Jun '23

07 Jun '23

Hello, Unfortunately I have conflicting meetings and I am unable to run the IRC meeting today, let’s cancel it today. Best regards, Bartosz Bezak

1 0

[openstack-ansible] Tuesday June 13 meeting is CANCELLED
by Dmitriy Rabotyagov 06 Jun '23

06 Jun '23

Hi folks, Since some members will be attending OpenInfra Summit and as we are having a PTG session on Wednesday, weekly meeting on Tuesday, June 13 is cancelled.

1 0

[ptg][openstack-ansible] Upcoming hybrid PTG and operator hours
by Dmitriy Rabotyagov 06 Jun '23

06 Jun '23

Hi everyone, I'm glad to announce that OpenStack-Ansible team is going to have a hybrid PTG during the OpenInfra Summit in Vancouver. PTG will happen on Wednesday, June 14, 09:40 - 11:30 local time or 16:45 - 18:30 UTC For those who will be on-site: we have table number 23 booked in the PTG room (Ballroom A?) For those who can not make it to the summit, we have a Zoom room prepared [1] Moreover, we're planning to have an in-person Operator Hours session on Thursday, June 15, at 11:40 - 12:50, in an hour after the Project on-boarding session. So if you have more questions or wanna continue discussion or just can't make it to the Project on-boarding due to some conflict - you're warmly welcome to the operator hours slot. Etherpad with dates and topics that are to be discussed is here [2] [1] https://us06web.zoom.us/j/89099630568?pwd=WnBHYkEzdXJxQ2tLclQ1QXRvNjg5UT09 [2] https://etherpad.opendev.org/p/vancouver-june2023-os-ansible

1 0

Forum Etherpad Collection
by Kendall Nelson 06 Jun '23

06 Jun '23

Hello All! I started a wiki to collect etherpads into as we get them ready for next week. Feel free to add them as you create them! Can't wait to see everyone :) https://wiki.openstack.org/wiki/Forum/Vanvouver2023 <https://wiki.openstack.org/wiki/Forum/Vanvouver2023> -Kendall Nelson

1 0

[nova] Tuesday June 13 meeting is CANCELLED
by Sylvain Bauza 06 Jun '23

06 Jun '23

Some folks (including me) will be traveling for the OpenInfra Summit, so we deferred the nova meeting to the week after. -Sylvain

1 0

[neutron] Neutron meetings next week, Vancouver PTG
by Rodolfo Alonso Hernandez 06 Jun '23

06 Jun '23

Hello Neutrinos: As commented today during the Neutron meeting, next week we are cancelling all Neutron meetings (team, CI and drivers) due to the Vancouver PTG. See you there!

1 0

[qa] No office hour June 13th
by Martin Kopec 06 Jun '23

06 Jun '23

Hello everyone, we're cancelling our office hour on June 13th due to the OpenInfra Summit happening that week. If there is anything you would like to discuss in person in Vancouver, feel free to add it to the agenda [1]. The next office hour will be held on June 20th, 15:00 UTC as usual [2]. [1] https://etherpad.opendev.org/p/vancouver-june2023-qa [2] https://wiki.openstack.org/wiki/Meetings/QATeamMeeting Thanks, -- Martin Kopec Principal Software Quality Engineer Red Hat EMEA IM: kopecmartin

1 0

[ptg][qa] Planning for the upcoming June 2023 PTG
by Martin Kopec 06 Jun '23

06 Jun '23

Hello everyone, me and Ghanshyam will be present at the OpenInfra summit next week. If you have any topic you would like to discuss, feel free to add it to the etherpad [1]. Based on the number of topics we'll reserve a table and time accordingly. [1] https://etherpad.opendev.org/p/vancouver-june2023-qa Thanks, -- Martin Kopec Principal Software Quality Engineer Red Hat EMEA IM: kopecmartin <https://red.ht/sig>

1 0

OpenStack informations
by Imene Hessas 06 Jun '23

06 Jun '23

Greetings , As a curious person and a cloud enthusiast , I started recently documenting myself about OpenStack, learned about its components , methods of deployments .. etc And now am in front of an essential question : is there a lightweight version of Openstack ? Since I noticed that it requires significant hardware resources, including compute, storage, and networking infrastructure, to run efficiently. I'll be waiting patiently for your response ! Thank you.

2 1

[nova] Nova Spec review day next Tuesday 6 June
by Sylvain Bauza 06 Jun '23

06 Jun '23

Hey Nova community, As a reminder, you can find the Nova agenda for the 2023.2 Bobcat release here https://releases.openstack.org/bobcat/schedule.html As you can see, we plan to do a round of reviews for all the open specifications in the openstack/nova-specs repository by next Tuesday June 6th. If you're a developer wanting to propose a new feature in Nova and you have been said to provide a spec, or if you know that you need to create a spec, or if you already have an open spec, please make sure to upload/update your file before next Tuesday so we'll look at it. Also, if you can look again on your spec during the day, it would be nice as we could try to discuss your spec during this day. Thanks, -Sylvain

2 1

Nested template
by Antony P 06 Jun '23

06 Jun '23

Dear team, I have 2 template test1.yaml test2.yaml how to run this 2 templates as single template. what is steps i have to follow *--Warm Regards* *Antony P* *Jr. DevOps Engineer* antony(a)edgebricks.com Mob No: +919498079898 www.edgebricks.com

5 4

[devstack] Recent change breaks cloning with GIT_DEPTH setting
by Nell Jerram 06 Jun '23

06 Jun '23

FYI, devstack commit b0bd5b92 doesn't work with a GIT_DEPTH=1 setting. That commit basically changed from git clone ... --branch <BRANCH> to git clone ... git checkout <BRANCH> So it's easy for the desired <BRANCH> to be unavailable if GIT_DEPTH is limited. Best wishes - Nell

2 2

[neutron][ovn] The implementation status of DVR for port forwarding in OpenStack.
by 韩光宇 06 Jun '23

06 Jun '23

Hello I previously learned that distributed SNAT has not been implemented in ML2/OVS yet, and traffic for floating IP port forwarding still goes through the network node. Therefore, I tried using ML2/OVN. However, I found that the traffic for floating IP port forwarding still goes through the network node. Does anyone know if this is normal or if OVN has implemented DVR for port forwarding? Or is it because there is an issue with my configuration? I deploy a master ubuntu env by kolla, and I had set dvr of ovn. ``` # in /etc/kolla/globals.yml neutron_plugin_agent: "ovn" neutron_ovn_distributed_fip: "yes" ``` I would like to know if OVN currently implements DVR for port forwarding. If not, what can I do to distribute the traffic load for port forwarding of OpenStack? In my use case, I need to create a large number of port forwarding rules, which puts a lot of pressure on the network node. I will appreciate any help or advice. Best regards, Han Guangyu

2 1

[puppet] puppet module improvements
by Benedikt Trefzer 05 Jun '23

05 Jun '23

Hi all I use the openstack puppet modules to deploy openstack. I'd like to suggest some improvements to the modules and like to know what the community thinks about: 1.) use proper types for parameters Parameter validation is done with 'validate_legacy...' instead of defining the class/resource parameter with a proper type all over the code. I cannot imaging of any advantage not using proper type definitions. Instead using typed parameters would be more efficient an code readability would increase. 2.) params.pp This is the legacy way to define parameter defaults for different OS's. In the modern puppet world a module specific hiera structure is used, which eliminates the need of params.pp class (with inheritance and include). The usage of hiera improves readability and flexibility (every parameter can be overwritten on request, eg. change of packages names etc.) This also eliminate the restriction that the modules can only be used by certain OS'es (osfamily 'RedHat' or 'Debian'). 3.) Eliminate "if OS=='bla' {" statements in code These statements make the code very inflexible. It cannot be overruled if necessary (eg. if I use custom packages to install and do not need the code provided in the if statement). Instead a parameter should be used with a default provided in hiera. Since there is lot of code to change I do not expect this to be done in a single commit (per module) but in steps probably in more than one release cycle. But defining this as best practice for openstack puppet modules and start using above in new commits would bring the code forward. Finally: These are suggestions open for discussion. In no way I like to critic the current state of the puppet modules (which is quite good, but a bit legacy) or the people working on the modules. This is just a feedback/suggestion from an operator using the modules on a daily basis. Regards Benedikt Trefzer

4 4

[tc] Technical Committee next weekly meeting on June 6, 2023
by Nikolla, Kristi 05 Jun '23

05 Jun '23

Hi all, This is a reminder that the next weekly Technical Committee meeting is to be held on Tuesday, Jun 6, 2023 at 1800 UTC on Zoom. Meeting link and agenda can be found at https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting Please find below the current agenda for the meeting. * Roll call * Follow up on past action items ** knikolla Book timeslots for PTG in Vancouver ** knikolla Prepare PTG agenda for Vancouver ** knikolla To fix link redirect to release from docs ** knikolla Finish TC Tracker 2023.2 * Open Infra Summit and PTG in Vancouver, next week * Gate health check * Broken docs due to inconsistent release naming * Open Discussion and Reviews ** https://review.opendev.org/q/projects:openstack/governance+is:open Thank you, Kristi Nikolla

1 0

[ceph-users] Quuncy release - radosGW integration with Keystone
by fsbiz＠yahoo.com 05 Jun '23

05 Jun '23

Hi folks, My ceph cluster with Quincy and Rocky9 is up and running.But I'm having issues with radosGW authenticating with keystone. Was wondering if I'm missed anything in the configuration. From the debug logs below, it appears that radosgw is still trying to authenticate withSwift instead of Keystone.Any pointers will be appreciated. thanks, Fred Here is my configuration. # ceph config dump | grep rgw client advanced debug_rgw 20/20 client advanced rgw_keystone_accepted_roles admin,user * client advanced rgw_keystone_admin_domain Default * client advanced rgw_keystone_admin_password <secret> * client advanced rgw_keystone_admin_project service * client advanced rgw_keystone_admin_user ceph-ks-svc * client advanced rgw_keystone_api_version 3 client advanced rgw_keystone_implicit_tenants false * client advanced rgw_keystone_token_cache_size 0 client basic rgw_keystone_url <Identity URL> * client advanced rgw_s3_auth_use_keystone true client advanced rgw_swift_account_in_url true client basic rgw_thread_pool_size 512 client.rgw.s_rgw.dev-ipp1-u1-control01.ojmddc basic rgw_frontends beast port=7480 * client.rgw.s_rgw.dev-ipp1-u1-control02.adnjrx basic rgw_frontends beast port=7480 Here's the debug log. If I interpret it correctly, it is trying to do a swift authentication and failing.Am I missing any configuration for Keystone based authentication ? Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: beast: 0x7fddeb8e7710:10.117.53.10 - - [03/Jun/2023:18:47:03.060 +0000] "GET/swift/v1/AUTH_c668ed224e434c88a9e0fce125056112?format=json HTTP/1.1" 401 119 -"openstacksdk/0.52.0 keystoneauth1/4.0.0 python-requests/2.22.0 CPython/3.8.10"- latency=0.000000000s Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: HTTP_ACCEPT=*/*Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: HTTP_ACCEPT_ENCODING=gzip,deflateJun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: HTTP_CONNECTION=closeJun 03 11:47:03 dev-ipp1-u1-control02.radosgw[2802861]:HTTP_HOST=dev-ipp1-u1-object-storeJun 03 11:47:03 dev-ipp1-u1-control02radosgw[2802861]: HTTP_USER_AGENT=openstacksdk/0.52.0keystoneauth1/4.0.0 python-requests/2.22.0 CPython/3.8.10Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: HTTP_VERSION=1.1 Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]:HTTP_X_AUTH_TOKEN=gAAAAABke4qn779UQ_XMz0EDL3P3TgjBQsGG6p-MNhviJxLZTuMTnTDmpT5Yfi9UpgO_T3LOOsPjQAw6zoMUIaC22wPeryp5x-UumB3XwXOWp-qSXLbuN3b9oj_Qg5kCZWA0waWNRHzQ1mwtlEmmpTgvTXbU5V1ym6hEBOn6Q3RWhn34Hj3cF9oJun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: HTTP_X_FORWARDED_FOR=10.117.148.3Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: QUERY_STRING=format=jsonJun 03 11:47:03 dev-ipp1-u1-control02.radosgw[2802861]: REMOTE_ADDR=10.117.53.10 Jun 03 11:47:03 dev-ipp1-u1-control02.radosgw[2802861]: REQUEST_METHOD=GETJun 03 11:47:03 dev-ipp1-u1-control02.radosgw[2802861]:REQUEST_URI=/swift/v1/AUTH_c668ed224e434c88a9e0fce125056112?format=jsonJun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]:SCRIPT_URI=/swift/v1/AUTH_c668ed224e434c88a9e0fce125056112 Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: SERVER_PORT=7480Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: ====== starting new requestreq=0x7fddeb8e7710 ===== Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s initializing for trans_id = tx000003991cfc5c1791f95-00647b8aa7-30c56-default Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s rgw api priority: s3=8 s3website=7Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s host=dev-ipp1-u1-object-store Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s subdomain= domain= in_hosted_domain=0 in_hosted_domain_s3website=0 Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s final domain/bucket subdomain= domain= in_hosted_domain=0in_hosted_domain_s3website=0 s->info.domain=s->info.request_uri=/swift/v1/AUTH_c668ed224e434c88a9e0fce125056112 Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s name: format val: jsonJun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s ver=v1 first= req= Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s handler=29RGWHandler_REST_Service_SWIFT Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s getting op 0 Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s get_system_obj_state: rctx=0x7fddeb8e6790obj=default.rgw.log:script.prerequest. state=0x55f743b97720 s->prefetch_data=0 Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s cache get: name=default.rgw.log++script.prerequest. : hit (negative entry) Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s swift:list_buckets scheduling with throttler client=3 cost=1Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s swift:list_buckets op=29RGWListBuckets_ObjStore_SWIFTJun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s swift:list_buckets verifying requester Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s swift:list_buckets rgw::auth::swift::DefaultStrategy: tryingrgw::auth::swift::TempURLEngine Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s swift:list_buckets rgw::auth::swift::TempURLEngine denied with reason=-13 Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s swift:list_buckets rgw::auth::swift::DefaultStrategy: tryingrgw::auth::swift::SignedTokenEngine Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s swift:list_buckets rgw::auth::swift::SignedTokenEngine denied with reason=-1 Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s swift:list_buckets rgw::auth::swift::DefaultStrategy: tryingrgw::auth::swift::SwiftAnonymousEngine Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s swift:list_buckets rgw::auth::swift::SwiftAnonymousEngine denied withreason=-1 Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s swift:list_buckets Failed the auth strategy, reason=-1 Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: failed to authorize requestJun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s op->ERRORHANDLER: err_no=-1 new_err_no=-1Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s get_system_obj_state: rctx=0x7fddeb8e6790obj=default.rgw.log:script.postrequest. state=0x55f743b97960 s->prefetch_data=0 Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s cache get: name=default.rgw.log++script.postrequest. : hit (negative entry) Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s swift:list_buckets op status=0 Jun 03 11:47:03 dev-ipp1-u1-control02 radosgw[2802861]: req 41483251800463850450.000000000s swift:list_buckets http status=401

1 0