September 2022 - openstack-discuss

[neutron] bug deputy report of week 2022-09-19
by Bence Romsics 26 Sep '22

26 Sep '22

Hi All, Here comes last week's deputy report (we had only a handful of reports): Unassigned: * https://bugs.launchpad.net/neutron/+bug/1990229 [OVN] Stop using external_ids from SB Chassis table Edit Medium: * https://bugs.launchpad.net/neutron/+bug/1990129 [ovn-octavia-provider] Avoid LB in ERROR status on delete due to LR/LS not found proposed fix: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/857716 Low: * https://bugs.launchpad.net/neutron/+bug/1990285 Help for `network create --external` is incorrect Edit proposed fix: https://review.opendev.org/c/openstack/python-openstackclient/+/858708 Incomplete: * https://bugs.launchpad.net/neutron/+bug/1990561 Network filtering by provider attributes has a race condition with network removal Cheers, Bence

1 0

Re: RE : RE : [neutron][nova][ipv6]instance on compute node not getting dhcpv6
by mhazan＠mandint.org 26 Sep '22

26 Sep '22

no joy with the accept_ra fiddling, the image are all ubuntu or debian cloud-init ready and are working on all in one node but not dedicated compute node, it's as if the dhcpv6 packet (before address is allocated to interface) are not passing between the control node and the dedicated compute node. Le 2022-09-20 10:53, Michael Hazan a écrit : > Thanks for the suggestion, i will look into the accept_ra setting. However, the very same image that boot on the « old » all in one node are getting ipv6 and ipv4 without issue. The network interfaces are configured similarly on all nodes. > > Michael > > DE : Neil Jerram > ENVOYÉ LE :mardi, 20 septembre 2022 10:47 > À : Michael Hazan > CC : Lajos Katona; openstack-discuss(a)lists.openstack.org > OBJET :Re: RE : [neutron][nova][ipv6]instance on compute node not getting dhcpv6 > > They may be outdated now, but I wonder if any of the steps described at https://projectcalico.docs.tigera.io/networking/openstack/ipv6 would help you? In particular, given that you have no route, perhaps you need the accept_ra config. > > Best wishes, > > Neil > > On Tue, Sep 20, 2022 at 9:12 AM Michael Hazan <mhazan(a)mandint.org> wrote: > >> Hello, >> >> The 3 nodes are running Ubuntu 20.04 and using libvirt. The instance are Ubuntu or debian based. The openstack virtual network is configured with both a v4 and a v6 dhcp pool. The instance should be getting both v4 and v6 (on the same interface) but the instance that are hosted on the compute node only get v4. If i run the dhclient -6 -r the instance actually get it's ipv6 but it's wrongly configured with a /128 (instead of 64) and no route. >> >> Michael >> >> DE : Lajos Katona >> ENVOYÉ LE :mardi, 20 septembre 2022 09:39 >> À : mhazan(a)mandint.org >> CC : openstack-discuss(a)lists.openstack.org >> OBJET :Re: [neutron][nova][ipv6]instance on compute node not getting dhcpv6 >> >> Hi, >> >> Do you have some more details of your environment, which backend you use? OVS? >> >> Your VMs have both IPv4 and v6 addresses and you mean that they got IPv4 as expected? >> >> Lajos >> >> <mhazan(a)mandint.org> ezt írta (időpont: 2022. szept. 19., H, 16:19): >> >> Hello all, >> >> i manage a small openstack cluster installed via Ubuntu package, it has >> been upgraded since the day of Newton and currently running Victoria. it >> started as a single node with the basic services installed, later a >> dedicated storage node and compute node were added. after upgrading to >> victoria, any instance that boot on the dedicated compute node start up >> but fails to get it's global ipv6 via stateful dhcp6, only >> linklocal(fe80) ip is shown by the instance. The ipv6 is created in >> openstack, the dhcpv4 works and there are no issue if the instance boot >> on the "old" all in one node. i can manually allocate (by editing the >> instance network config file) the ipv6 config and it works. any pointer >> as to what could cause this issue ? >> >> BR, Michael

1 1

[magnum][heat][requirements][release] Potential blocker for release with python-magnumclient 4.0.0
by Tony Breeds 26 Sep '22

26 Sep '22

Hello all, In [1] baymodel code was removed, although it still seems to be listed in the API-ref. Story [2] states it's been deprecated for a long time, but a quick check failed to see this documented anywhere. Heat still supports baymodel and the removal is causing failures. Blocking the use of python-magnumclient 4.0.0[3] inzed, even though the 4.0.0 release is clearly meant for zed. I can see a couple of paths forward. 0. Remove the documentation in the api-ref for baymodels 1. Remove the support in heat for baymodels (I think the newer clusters API can be used instead?) 2. Revert the change in magnumclient and re-release etc etc 3. Keep 4.0.0 for the Antelope release, and reset the stable/zed branch python-magnumclient to fd0cb1e (before the removal of baymodels) Obviously option 1 looks like the least disruptive change, but potentially causes a problem for heat depending on the published state of baymodel support [1] https://review.opendev.org/c/openstack/python-magnumclient/+/803629 [2] https://storyboard.openstack.org/#!/story/2009104 [3] https://review.opendev.org/c/openstack/requirements/+/858089 -- Yours Tony.

3 4

[openstack-helm] OpenStack-Helm PTG
by Gage Hugo 25 Sep '22

25 Sep '22

Hey team, The next PTG is coming up (Oct 17-21). I've booked a slot for project discussions on Tue Oct 18th @ 1500 UTC Please sign up to the etherpad if you wish to propose any topics: https://etherpad.opendev.org/p/oct2022-ptg-openstack-helm See you there!

1 0

[all][tc] What's happening in Technical Committee: summary 2022 Sept 23: Reading: 5 min
by Ghanshyam Mann 23 Sep '22

23 Sep '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Sept 22. Most of the meeting discussions are summarized in this email. Meeting logs are available @ https://meetings.opendev.org/meetings/tc/2022/tc.2022-09-22-15.00.log.html * Next TC weekly meeting will be on Sept 29 Thursday at 15:00 UTC, feel free to add the topic on the agenda[1] by Sept 28. 2. What we completed this week: ========================= * Antelope Elections[2]. Thanks to all the leaders who step up for the role. Also thanks to the election official. * Updated node.js version to 18 in 2023.1 testing runtime[3] 3. Activities In progress: ================== TC Tracker for Zed cycle ------------------------------ * Zed tracker etherpad includes the TC working items[4], Five are completed and other items are in-progress. Open Reviews ----------------- * Thirteen open reviews for ongoing activities[5]. New community-wide goal proposal "Migration CI/CD to Ubuntu 22.04" -------------------------------------------------------------------------------------- As we decided to migrate the CI/CD testing from Ubuntu 20.04 to 22.04 in 2023.1 cycle, we need to define this task as a community-wide goal. This work requires more testing than changes which are covered in base jobs. The goal proposal is under review[6]. Thanks, Dmitriy to compose and volunteer to drive this goal. 2023.1 cycle Leaderless projects & TC Chair ---------------------------------------------------- * We had 9 projects that missed the PTL nomination but the good news is that we found the leaders for all 9 projects now[7]. TC is discussing their appointment on gerrit reviews. * TC Chair: we have two nominations for the TC Chair[8][9] which is really a good thing having multiple people stepping up for the role. We will keep nomination open until Tuesday (27 Sept) if anyone else also would like to add a nomination. On Tuesday, we can start the CIVS poll among TC members to select the chair for next term. 2023.1 cycle TC PTG planning ------------------------------------ Updates on PTG planning: * TC decided to meet at the below slots [10]: ** Monday 15:00 - 17:00 UTC (2 hours) for TC+leaders interaction discussion. ** Thursday 15:00 - 19:00 UTC (4 hours) ** Friday 15:00 - 19:00 UTC (4 hours) * Etherpads: ** https://etherpad.opendev.org/p/tc-2023-1-ptg ** https://etherpad.opendev.org/p/tc-leaders-interaction-2023-1 * I sent an email about the 'Operator Hours' slots in this PTG, please check and reserve the operator hour slot for your project[11] 2021 User Survey TC Question Analysis ----------------------------------------------- No update on this. The survey summary is up for review[12]. Feel free to check and provide feedback. Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[13]14]. Project updates ------------------- * None. 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[15]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [16] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://review.opendev.org/c/openstack/governance/+/858539 [3] https://review.opendev.org/c/openstack/governance/+/856927 [4] https://etherpad.opendev.org/p/tc-zed-tracker [5] https://review.opendev.org/q/projects:openstack/governance+status:open [6] https://review.opendev.org/c/openstack/governance/+/858690 [7] https://etherpad.opendev.org/p/2023.1-leaderless [8] https://review.opendev.org/c/openstack/governance/+/858947 [9] https://review.opendev.org/c/openstack/governance/+/858957 [10] https://lists.openstack.org/pipermail/openstack-discuss/2022-September/0305… [11] https://lists.openstack.org/pipermail/openstack-discuss/2022-September/0303… [12] https://review.opendev.org/c/openstack/governance/+/836888 [13] https://etherpad.opendev.org/p/zuul-config-error-openstack [14] http://lists.openstack.org/pipermail/openstack-discuss/2022-May/028603.html [15] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [16] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[manila] Antelope PTG planning
by Carlos Silva 23 Sep '22

23 Sep '22

Greetings, Zorillas and interested stackers! At this point, I bet you already know that the PTG is coming. It goes from 17th to 21st of October 2022, and if you have not registered yet, there is still time! [1] We have already booked the slots for our discussions, please add it to your agenda: 17th: 16:00 UTC to 17:00 UTC (Monday) 19th: 14:00 UTC to 17:00 UTC (Wednesday) 20th: 14:00 UTC to 17:00 UTC (Thursday) 21st: 13:00 UTC to 17:00 UTC (Friday) Please add the topics you would like to bring up to our planning etherpad [2]. Looking forward to meeting you there! [1] https://openinfra.dev/ptg/ [2] https://etherpad.opendev.org/p/antelope-ptg-manila-planning - carloss

1 0

[release] Release countdown for week R-1, Sep 26 - 30
by Előd Illés 23 Sep '22

23 Sep '22

Development Focus ----------------- We are on the final mile of the Zed development cycle! Remember that the Zed final release will include the latest release candidate (for cycle-with-rc deliverables) or the latest intermediary release (for cycle-with-intermediary deliverables) available. September 29th, 2022 is the deadline for final Zed release candidates as well as any last cycle-with-intermediary deliverables. We will then enter a quiet period until we tag the final release on October 5th, 2022. Teams should be prioritizing fixing release-critical bugs, before that deadline. Otherwise it's time to start planning the 2023.1 Antelope development cycle, including discussing Forum and PTG sessions content, in preparation of Virtual PTG @ October 17-21, 2022. Actions ------- Watch for any translation patches coming through on the stable/zed branch and merge them quickly. If you discover a release-critical issue, please make sure to fix it on the master branch first, then backport the bugfix to the stable/zed branch before triggering a new release. Please drop by #openstack-release with any questions or concerns about the upcoming release ! Upcoming Deadlines & Dates -------------------------- Final Zed release: October 5th, 2022 Virtual PTG: October 17-21, 2022 Előd Illés irc: elodilles

1 0

[kolla] Antelope PTG
by Michał Nasiadka 23 Sep '22

23 Sep '22

Greetings Koalas, As you most probably know the OpenStack Antelope PTG is coming soon (17-21th Oct 2022). I’ve booked the usual slots (Mon-Wed) for Kolla project group (Kolla, Kolla-Ansible, Kayobe) with Wed being primary a slot for Kayobe. For operator-focus - the Kolla projects Operator Hour is booked for Tue, 16-17 UTC. Please sign up to the ether pad https://etherpad.opendev.org/p/kolla-antelope-ptg <https://etherpad.opendev.org/p/kolla-antelope-ptg> and propose topics. See you on the PTG! Best regards, Michal Nasiadka

1 0

[nova][ironic][ptg] Improved ironic<>nova driver interactions session
by Jay Faulkner 23 Sep '22

23 Sep '22

Hello Nova folks, At the Ironic PTG planning meeting this morning, discussion of improving Nova and Ironic driver interactions; and specifically this spec: https://review.opendev.org/c/openstack/nova-specs/+/842015/ came up. It's important for our teams to come together and reach consensus as to how to fix this. According to the latest OpenStack user survey ( https://www.openstack.org/analytics/) over 20% of Nova deployments utilize the Ironic driver. However, in my years operating Ironic for multiple different organizations, the Nova<>Ironic driver interface has repeatedly been the source of most operational pain. We should work together to prioritize saving these operators from downtime and bad failure semantics. I'd love for Ironic and Nova to schedule a session together to talk about this and try to find a solution. We owe it to our users to no longer shy away from this hard technical problem and fix things. What's the best way for us to get this time scheduled? Someone can feel free to reach out to me on IRC (JayF), or reply here and I'm sure we can work it out. Thanks in Advance, Jay Faulkner G-Research Open Source Software lab OpenStack Ironic PTL OpenStack Technical Committee member

2 1

Swift not recognizing mounted drives
by Andrew Boring 22 Sep '22

22 Sep '22

Hi all. I have a new Openstack Swift install, currently a single node with 12 disks running CentOS 8 Stream and Openstack Yoga / RDO release with Keystone Auth. Disks are formatted with xfs and mounted at /srv/node/sd[a-l] as described in the Install docs, but no Swift services reccognize it. SELinux is set to permissive mode. Log sample: Sep 22 11:29:01 [hostname] account-replicator[182475]: Skipping: /srv/node/sda is not mounted Sep 22 11:29:01 [hostname] account-replicator[182475]: Skipping: /srv/node/sdb is not mounted Sep 22 11:29:01 [hostname] account-replicator[182475]: Skipping: /srv/node/sdc is not mounted Sep 22 11:29:01 [hostname] account-replicator[182475]: Skipping: /srv/node/sdd is not mounted Sep 22 11:29:01 [hostname] account-replicator[182475]: Skipping: /srv/node/sde is not mounted Sep 22 11:29:01 [hostname] account-replicator[182475]: Skipping: /srv/node/sdf is not mounted Sep 22 11:29:01 [hostname] account-replicator[182475]: Skipping: /srv/node/sdg is not mounted Sep 22 11:29:01 [hostname] account-replicator[182475]: Skipping: /srv/node/sdh is not mounted Sep 22 11:29:01 [hostname] account-replicator[182475]: Skipping: /srv/node/sdi is not mounted Sep 22 11:29:01 [hostname] account-replicator[182475]: Skipping: /srv/node/sdj is not mounted Sep 22 11:29:01 [hostname] account-replicator[182475]: Skipping: /srv/node/sdk is not mounted Sep 22 11:29:01 [hostname] account-replicator[182475]: Skipping: /srv/node/sdl is not mounted Sep 22 11:29:01 [hostname] account-replicator[182475]: Beginning replication run Sep 22 11:29:01 [hostname] account-replicator[182475]: Replication run OVER Sep 22 11:29:01 [hostname] account-replicator[182475]: Attempted to replicate 0 dbs in 0.00344 seconds (0.00000/s) Sep 22 11:29:01 [hostname] account-replicator[182475]: Removed 0 dbs Sep 22 11:29:01 [hostname] account-replicator[182475]: 0 successes, 144 failures Sep 22 11:29:01 [hostname] account-replicator[182475]: diff:0 diff_capped:0 empty:0 hashmatch:0 no_change:0 remote_merge:0 rsync:0 ts_repl:0 Container and Object processes show the same issue. And yet...devices are mounted: [root@swift]# mount | grep srv /dev/sdb on /srv/node/sdb type xfs (rw,noatime,seclabel,attr2,inode64,logbufs=8,logbsize=32k,noquota) /dev/sdc on /srv/node/sdc type xfs (rw,noatime,seclabel,attr2,inode64,logbufs=8,logbsize=32k,noquota) /dev/sdd on /srv/node/sdd type xfs (rw,noatime,seclabel,attr2,inode64,logbufs=8,logbsize=32k,noquota) /dev/sde on /srv/node/sde type xfs (rw,noatime,seclabel,attr2,inode64,logbufs=8,logbsize=32k,noquota) /dev/sdf on /srv/node/sdf type xfs (rw,noatime,seclabel,attr2,inode64,logbufs=8,logbsize=32k,noquota) /dev/sdg on /srv/node/sdg type xfs (rw,noatime,seclabel,attr2,inode64,logbufs=8,logbsize=32k,noquota) /dev/sdh on /srv/node/sdh type xfs (rw,noatime,seclabel,attr2,inode64,logbufs=8,logbsize=32k,noquota) /dev/sdi on /srv/node/sdi type xfs (rw,noatime,seclabel,attr2,inode64,logbufs=8,logbsize=32k,noquota) /dev/sdj on /srv/node/sdj type xfs (rw,noatime,seclabel,attr2,inode64,logbufs=8,logbsize=32k,noquota) /dev/sdk on /srv/node/sdk type xfs (rw,noatime,seclabel,attr2,inode64,logbufs=8,logbsize=32k,noquota) /dev/sdl on /srv/node/sdl type xfs (rw,noatime,seclabel,attr2,inode64,logbufs=8,logbsize=32k,noquota) /dev/sda on /srv/node/sda type xfs (rw,noatime,seclabel,attr2,inode64,logbufs=8,logbsize=32k,noquota) And the rings are built: [root@swift]# swift-ring-builder /etc/swift/account.builder /etc/swift/account.builder, build version 13, id 415987b4753847e9924147119872d547 2048 partitions, 3.000000 replicas, 1 regions, 1 zones, 12 devices, 0.00 balance, 0.00 dispersion The minimum number of hours before a partition can be reassigned is 1 (0:16:41 remaining) The overload factor is 0.00% (0.000000) Ring file /etc/swift/account.ring.gz is up-to-date Devices: id region zone ip address:port replication ip:port name weight partitions balance flags meta 0 1 1 172.16.2.2:6202 172.16.2.2:6202 sda 100.00 512 0.00 1 1 1 172.16.2.2:6202 172.16.2.2:6202 sdb 100.00 512 0.00 2 1 1 172.16.2.2:6202 172.16.2.2:6202 sdc 100.00 512 0.00 3 1 1 172.16.2.2:6202 172.16.2.2:6202 sdd 100.00 512 0.00 4 1 1 172.16.2.2:6202 172.16.2.2:6202 sde 100.00 512 0.00 5 1 1 172.16.2.2:6202 172.16.2.2:6202 sdf 100.00 512 0.00 6 1 1 172.16.2.2:6202 172.16.2.2:6202 sdg 100.00 512 0.00 7 1 1 172.16.2.2:6202 172.16.2.2:6202 sdh 100.00 512 0.00 8 1 1 172.16.2.2:6202 172.16.2.2:6202 sdi 100.00 512 0.00 9 1 1 172.16.2.2:6202 172.16.2.2:6202 sdj 100.00 512 0.00 10 1 1 172.16.2.2:6202 172.16.2.2:6202 sdk 100.00 512 0.00 11 1 1 172.16.2.2:6202 172.16.2.2:6202 sdl 100.00 512 0.00 Bash certainly thinks they are actually mounted and writable: [root@swift ~]# ls -l /srv/node/sda total 0 [root@swift ~]# touch /srv/node/sda/file [root@swift ~]# ls /srv/node/sda file [root@swift ~]# umount /dev/sda [root@swift ~]# ls /srv/node/sda [root@swift ~]# mount /srv/node/sda/ [root@swift ~]# ls /srv/node/sda file [root@swift ~]# rm /srv/node/sda/file rm: remove regular empty file '/srv/node/sda/file'? y And Swift is configured to look at /srv/node for the devices: [root@swift ~]# grep devices /etc/swift/*.conf /etc/swift/account-server.conf:devices = /srv/node /etc/swift/container-server.conf:devices = /srv/node /etc/swift/object-server.conf:devices = /srv/node Running "swift info" shows the expected configuration output, but "swift stat" throws this error: [root@controller ~]# swift stat Account HEAD failed: https:/[api endpoint]/v1/AUTH_5198a36c0f454ae49e9e8a5d6e154ee8 403 Forbidden Failed Transaction ID: tx9128250987cb4e07ad55d-00632c8d05 and the logs show account-server throwing "507 ERROR Insufficient Storage" before 503, and then returning a 403. [root@swift ~]# journalctl -b | grep tx9128250987cb4e07ad55d-00632c8d05 Sep 22 12:27:49 [hostname] account-server[182505]: 172.16.2.2 - - [22/Sep/2022:16:27:49 +0000] "HEAD /sdc/456/AUTH_5198a36c0f454ae49e9e8a5d6e154ee8" 507 - "HEAD http://[api endpoint]/v1/AUTH_5198a36c0f454ae49e9e8a5d6e154ee8?format=json" "tx9128250987cb4e07ad55d-00632c8d05" "proxy-server 182464" 0.0004 "-" 182505 - Sep 22 12:27:49 [hostname] proxy-server[182464]: ERROR Insufficient Storage 172.16.2.2:6202/sdc (txn: tx9128250987cb4e07ad55d-00632c8d05) Sep 22 12:27:49 [hostname] account-server[182515]: 172.16.2.2 - - [22/Sep/2022:16:27:49 +0000] "HEAD /sdj/456/AUTH_5198a36c0f454ae49e9e8a5d6e154ee8" 507 - "HEAD http://[api endpoint]/v1/AUTH_5198a36c0f454ae49e9e8a5d6e154ee8?format=json" "tx9128250987cb4e07ad55d-00632c8d05" "proxy-server 182464" 0.0004 "-" 182515 - Sep 22 12:27:49 [hostname] proxy-server[182464]: ERROR Insufficient Storage 172.16.2.2:6202/sdj (txn: tx9128250987cb4e07ad55d-00632c8d05) Sep 22 12:27:49 [hostname] account-server[182514]: 172.16.2.2 - - [22/Sep/2022:16:27:49 +0000] "HEAD /sdh/456/AUTH_5198a36c0f454ae49e9e8a5d6e154ee8" 507 - "HEAD http://[api endpoint]/v1/AUTH_5198a36c0f454ae49e9e8a5d6e154ee8?format=json" "tx9128250987cb4e07ad55d-00632c8d05" "proxy-server 182464" 0.0011 "-" 182514 - Sep 22 12:27:49 [hostname] proxy-server[182464]: ERROR Insufficient Storage 172.16.2.2:6202/sdh (txn: tx9128250987cb4e07ad55d-00632c8d05) Sep 22 12:27:49 [hostname] account-server[182506]: 172.16.2.2 - - [22/Sep/2022:16:27:49 +0000] "HEAD /sdl/456/AUTH_5198a36c0f454ae49e9e8a5d6e154ee8" 507 - "HEAD http://[api endpoint]/v1/AUTH_5198a36c0f454ae49e9e8a5d6e154ee8?format=json" "tx9128250987cb4e07ad55d-00632c8d05" "proxy-server 182464" 0.0011 "-" 182506 - Sep 22 12:27:49 [hostname] account-server[182504]: 172.16.2.2 - - [22/Sep/2022:16:27:49 +0000] "HEAD /sdf/456/AUTH_5198a36c0f454ae49e9e8a5d6e154ee8" 507 - "HEAD http://[api endpoint]/v1/AUTH_5198a36c0f454ae49e9e8a5d6e154ee8?format=json" "tx9128250987cb4e07ad55d-00632c8d05" "proxy-server 182464" 0.0010 "-" 182504 - Sep 22 12:27:49 [hostname] account-server[182504]: 172.16.2.2 - - [22/Sep/2022:16:27:49 +0000] "HEAD /sdi/456/AUTH_5198a36c0f454ae49e9e8a5d6e154ee8" 507 - "HEAD http://[api endpoint]/v1/AUTH_5198a36c0f454ae49e9e8a5d6e154ee8?format=json" "tx9128250987cb4e07ad55d-00632c8d05" "proxy-server 182464" 0.0002 "-" 182504 - Sep 22 12:27:49 [hostname] proxy-server[182464]: Handoff requested (4) (txn: tx9128250987cb4e07ad55d-00632c8d05) Sep 22 12:27:50 [hostname] account-server[182512]: 172.16.2.2 - - [22/Sep/2022:16:27:50 +0000] "HEAD /sda/456/AUTH_5198a36c0f454ae49e9e8a5d6e154ee8" 507 - "HEAD http://[api endpoint]/v1/AUTH_5198a36c0f454ae49e9e8a5d6e154ee8?format=json" "tx9128250987cb4e07ad55d-00632c8d05" "proxy-server 182464" 0.0011 "-" 182512 - Sep 22 12:27:50 [hostname] proxy-server[182464]: Handoff requested (5) (txn: tx9128250987cb4e07ad55d-00632c8d05) Sep 22 12:27:50 [hostname] account-server[182494]: 172.16.2.2 - - [22/Sep/2022:16:27:50 +0000] "HEAD /sde/456/AUTH_5198a36c0f454ae49e9e8a5d6e154ee8" 507 - "HEAD http://[api endpoint]/v1/AUTH_5198a36c0f454ae49e9e8a5d6e154ee8?format=json" "tx9128250987cb4e07ad55d-00632c8d05" "proxy-server 182464" 0.0010 "-" 182494 - Sep 22 12:27:50 [hostname] proxy-server[182464]: Handoff requested (6) (txn: tx9128250987cb4e07ad55d-00632c8d05) Sep 22 12:27:50 [hostname] account-server[182506]: 172.16.2.2 - - [22/Sep/2022:16:27:50 +0000] "HEAD /sdk/456/AUTH_5198a36c0f454ae49e9e8a5d6e154ee8" 507 - "HEAD http://[api endpoint]/v1/AUTH_5198a36c0f454ae49e9e8a5d6e154ee8?format=json" "tx9128250987cb4e07ad55d-00632c8d05" "proxy-server 182464" 0.0003 "-" 182506 - Sep 22 12:27:50 [hostname] proxy-server[182464]: Account HEAD returning 503 for [507, 507, 507] (txn: tx9128250987cb4e07ad55d-00632c8d05) Sep 22 12:27:50 [hostname] proxy-server[182464]: - - 22/Sep/2022/16/27/50 HEAD /v1/AUTH_5198a36c0f454ae49e9e8a5d6e154ee8%3Fformat%3Djson HTTP/1.0 503 - Swift - - - - tx9128250987cb4e07ad55d-00632c8d05 - 0.0337 RL - 1663864069.976659298 1663864070.010398626 - Sep 22 12:27:51 [hostname] proxy-server[182464]: [IP] 172.16.2.2 22/Sep/2022/16/27/51 HEAD /v1/AUTH_5198a36c0f454ae49e9e8a5d6e154ee8%3Fformat%3Djson HTTP/1.0 403 - python-swiftclient-3.13.1 gAAAAABjLI0FH9MP... - - - tx9128250987cb4e07ad55d-00632c8d05 - 1.4298 - - 1663864069.970289707 1663864071.400121450 - No data is being written to the disks by Swift: [root@swift ~]# ls -lR /srv/node /srv/node: total 0 drwxr-xr-x. 2 swift swift 6 Sep 22 11:13 sda drwxr-xr-x. 2 swift swift 6 Sep 22 11:07 sdb drwxr-xr-x. 2 swift swift 6 Sep 22 11:07 sdc ... /srv/node/sda: total 0 /srv/node/sdb: total 0 /srv/node/sdc: total 0 ... What am I missing here?

2 5