OpenStack Object Storage (swift)

swift-docker: saio docker alpine uncorrect

Bug #2070029 reported by vajrock on 2024-06-21

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	OpenStack Object Storage (swift)	Fix Released	Undecided	Unassigned

Bug Description

Good afternoon
When trying to get acquainted with swift, I ran into the problem of launching it.
Instructions on the page https://hub.docker.com/r/openstackswift/saio simple, but not working.
When trying to launch "docker run -d -p 8080:8080 openstackswift/saio" port 8080 does not listen
Output of the netstat command:
1c1fe1064f44:/# netstat -tulpn
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 127.0.0.1:11211 0.0.0.0:* LISTEN 639/memcached
tcp 0 0 127.0.0.11:37845 0.0.0.0:* LISTEN -
udp 0 0 127.0.0.11:55677 0.0.0.0:* -

Analysis of the /var/log/s6-uncaught-logs/current log showed that the launcher could not find executable files:

1c1fe1064f44:/var/log/s6-uncaught-logs# cat current
2024-06-21 09:36:46.955165500 [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
2024-06-21 09:36:47.078039500 [s6-init] ensuring user provided files have correct perms...exited 0.
2024-06-21 09:36:47.080081500 [fix-attrs.d] applying ownership & permissions fixes...
2024-06-21 09:36:47.082251500 [fix-attrs.d] logging: applying...
2024-06-21 09:36:47.101616500 s6-envuidgid: fatal: unknown user: syslog
2024-06-21 09:36:47.102357500 [fix-attrs.d] logging: exited 0.
2024-06-21 09:36:47.103892500 [fix-attrs.d] srv_node: applying...
2024-06-21 09:36:47.119211500 [fix-attrs.d] srv_node: exited 0.
2024-06-21 09:36:47.120799500 [fix-attrs.d] swift: applying...
2024-06-21 09:36:47.221288500 [fix-attrs.d] swift: exited 0.
2024-06-21 09:36:47.222632500 [fix-attrs.d] tmp: applying...
2024-06-21 09:36:47.236795500 [fix-attrs.d] tmp: exited 0.
2024-06-21 09:36:47.238017500 [fix-attrs.d] done.
2024-06-21 09:36:47.239748500 [cont-init.d] executing container initialization scripts...
2024-06-21 09:36:47.241770500 [cont-init.d] 01_swift_logs: executing...
2024-06-21 09:36:47.247731500 [cont-init.d] 01_swift_logs: exited 0.
2024-06-21 09:36:47.249333500 [cont-init.d] 02_build_remakerings: executing...
2024-06-21 09:36:47.258000500 [[ checking --privileged ]]
2024-06-21 09:36:47.259259500 ip: RTNETLINK answers: Operation not permitted
2024-06-21 09:36:47.259443500 storage type is internal_dirs. container is privileged? false
2024-06-21 09:36:47.259455500 [[ checking what to use as storage devices ]]
2024-06-21 09:36:47.260856500 [[ creating directories ]]
2024-06-21 09:36:47.262075500 created /srv/node/swift-d0
2024-06-21 09:36:47.263094500 created /srv/node/swift-d1
2024-06-21 09:36:47.264194500 created /srv/node/swift-d2
2024-06-21 09:36:47.265232500 created /srv/node/swift-d3
2024-06-21 09:36:47.266292500 created /srv/node/swift-d4
2024-06-21 09:36:47.267310500 created /srv/node/swift-d5
2024-06-21 09:36:47.270391500 started /etc/swift/remakerings.object with 'swift-ring-build create'
2024-06-21 09:36:47.270457500 started /etc/swift/remakerings.container with 'swift-ring-build create'
2024-06-21 09:36:47.270530500 started /etc/swift/remakerings.account with 'swift-ring-build create'
2024-06-21 09:36:47.272752500 pushed command to add r1z1-127.0.0.1:6200/swift-d0 to /etc/swift/remakerings.object
2024-06-21 09:36:47.272863500 pushed command to add r1z1-127.0.0.1:6201/swift-d0 to /etc/swift/remakerings.container
2024-06-21 09:36:47.272970500 pushed command to add r1z1-127.0.0.1:6202/swift-d0 to /etc/swift/remakerings.account
2024-06-21 09:36:47.273069500 pushed command to add r1z1-127.0.0.1:6200/swift-d1 to /etc/swift/remakerings.object
2024-06-21 09:36:47.273164500 pushed command to add r1z1-127.0.0.1:6201/swift-d1 to /etc/swift/remakerings.container
2024-06-21 09:36:47.273255500 pushed command to add r1z1-127.0.0.1:6202/swift-d1 to /etc/swift/remakerings.account
2024-06-21 09:36:47.273349500 pushed command to add r1z1-127.0.0.1:6200/swift-d2 to /etc/swift/remakerings.object
2024-06-21 09:36:47.273440500 pushed command to add r1z1-127.0.0.1:6201/swift-d2 to /etc/swift/remakerings.container
2024-06-21 09:36:47.273641500 pushed command to add r1z1-127.0.0.1:6202/swift-d2 to /etc/swift/remakerings.account
2024-06-21 09:36:47.273721500 pushed command to add r1z1-127.0.0.1:6200/swift-d3 to /etc/swift/remakerings.object
2024-06-21 09:36:47.273779500 pushed command to add r1z1-127.0.0.1:6201/swift-d3 to /etc/swift/remakerings.container
2024-06-21 09:36:47.273832500 pushed command to add r1z1-127.0.0.1:6202/swift-d3 to /etc/swift/remakerings.account
2024-06-21 09:36:47.273887500 pushed command to add r1z1-127.0.0.1:6200/swift-d4 to /etc/swift/remakerings.object
2024-06-21 09:36:47.273941500 pushed command to add r1z1-127.0.0.1:6201/swift-d4 to /etc/swift/remakerings.container
2024-06-21 09:36:47.273992500 pushed command to add r1z1-127.0.0.1:6202/swift-d4 to /etc/swift/remakerings.account
2024-06-21 09:36:47.274045500 pushed command to add r1z1-127.0.0.1:6200/swift-d5 to /etc/swift/remakerings.object
2024-06-21 09:36:47.274096500 pushed command to add r1z1-127.0.0.1:6201/swift-d5 to /etc/swift/remakerings.container
2024-06-21 09:36:47.274147500 pushed command to add r1z1-127.0.0.1:6202/swift-d5 to /etc/swift/remakerings.account
2024-06-21 09:36:47.274209500 pushed command to rebalance ring into /etc/swift/remakerings.object
2024-06-21 09:36:47.274234500 pushed command to rebalance ring into /etc/swift/remakerings.container
2024-06-21 09:36:47.274258500 pushed command to rebalance ring into /etc/swift/remakerings.account
2024-06-21 09:36:47.274380500 created umbrella /etc/swift/remakerings, with deleting all ring files
2024-06-21 09:36:47.275575500 pushed /etc/swift/remakerings.object to /etc/swift/remakerings
2024-06-21 09:36:47.276637500 deleted /etc/swift/remakerings.object
2024-06-21 09:36:47.277651500 pushed /etc/swift/remakerings.container to /etc/swift/remakerings
2024-06-21 09:36:47.278657500 deleted /etc/swift/remakerings.container
2024-06-21 09:36:47.279635500 pushed /etc/swift/remakerings.account to /etc/swift/remakerings
2024-06-21 09:36:47.280623500 deleted /etc/swift/remakerings.account
2024-06-21 09:36:47.281597500 made remaketings executable (+x)
2024-06-21 09:36:47.284256500 /etc/swift/remakerings: line 2: swift-ring-builder: not found
2024-06-21 09:36:47.284269500 /etc/swift/remakerings: line 3: swift-ring-builder: not found
2024-06-21 09:36:47.284297500 /etc/swift/remakerings: line 4: swift-ring-builder: not found
2024-06-21 09:36:47.284310500 /etc/swift/remakerings: line 5: swift-ring-builder: not found
2024-06-21 09:36:47.284345500 /etc/swift/remakerings: line 6: swift-ring-builder: not found
2024-06-21 09:36:47.284379500 /etc/swift/remakerings: line 7: swift-ring-builder: not found
2024-06-21 09:36:47.284417500 /etc/swift/remakerings: line 8: swift-ring-builder: not found
2024-06-21 09:36:47.284442500 /etc/swift/remakerings: line 9: swift-ring-builder: not found
2024-06-21 09:36:47.284586500 /etc/swift/remakerings: line 10: swift-ring-builder: not found
2024-06-21 09:36:47.284598500 /etc/swift/remakerings: line 11: swift-ring-builder: not found
2024-06-21 09:36:47.284600500 /etc/swift/remakerings: line 12: swift-ring-builder: not found
2024-06-21 09:36:47.284603500 /etc/swift/remakerings: line 13: swift-ring-builder: not found
2024-06-21 09:36:47.284627500 /etc/swift/remakerings: line 14: swift-ring-builder: not found
2024-06-21 09:36:47.284655500 /etc/swift/remakerings: line 15: swift-ring-builder: not found
2024-06-21 09:36:47.284685500 /etc/swift/remakerings: line 16: swift-ring-builder: not found
2024-06-21 09:36:47.284723500 /etc/swift/remakerings: line 17: swift-ring-builder: not found
2024-06-21 09:36:47.284747500 /etc/swift/remakerings: line 18: swift-ring-builder: not found
2024-06-21 09:36:47.284854500 /etc/swift/remakerings: line 19: swift-ring-builder: not found
2024-06-21 09:36:47.284865500 /etc/swift/remakerings: line 20: swift-ring-builder: not found
2024-06-21 09:36:47.284867500 /etc/swift/remakerings: line 21: swift-ring-builder: not found
2024-06-21 09:36:47.284885500 /etc/swift/remakerings: line 22: swift-ring-builder: not found
2024-06-21 09:36:47.284902500 /etc/swift/remakerings: line 23: swift-ring-builder: not found
2024-06-21 09:36:47.284947500 /etc/swift/remakerings: line 24: swift-ring-builder: not found
2024-06-21 09:36:47.284962500 /etc/swift/remakerings: line 25: swift-ring-builder: not found
2024-06-21 09:36:47.285971500 [cont-init.d] 02_build_remakerings: exited 127.
2024-06-21 09:36:47.287532500 [cont-init.d] ~-socklog: executing...
2024-06-21 09:36:47.366263500 [cont-init.d] ~-socklog: exited 0.
2024-06-21 09:36:47.367652500 [cont-init.d] done.
2024-06-21 09:36:47.369497500 [services.d] starting services
2024-06-21 09:36:47.377542500 s6-applyuidgid: fatal: unable to exec swift-init: No such file or directory
2024-06-21 09:36:47.377554500 s6-applyuidgid: fatal: unable to exec swift-init: No such file or directory
2024-06-21 09:36:47.377581500 s6-applyuidgid: fatal: unable to exec swift-init: No such file or directory
2024-06-21 09:36:47.377892500 s6-applyuidgid: fatal: unable to exec swift-init: No such file or directory
2024-06-21 09:36:47.381935500 [services.d] done.
2024-06-21 09:36:48.379177500 s6-applyuidgid: fatal: unable to exec swift-init: No such file or directory
2024-06-21 09:36:48.379420500 s6-applyuidgid: fatal: unable to exec swift-init: No such file or directory
2024-06-21 09:36:48.379526500 s6-applyuidgid: fatal: unable to exec swift-init: No such file or directory
2024-06-21 09:36:48.380205500 s6-applyuidgid: fatal: unable to exec swift-init: No such file or directory
2024-06-21 09:36:49.379997500 s6-applyuidgid: fatal: unable to exec swift-init: No such file or directory
2024-06-21 09:36:49.380726500 s6-applyuidgid: fatal: unable to exec swift-init: No such file or directory

Fixing the /init script and adding the /opt/swift/bin path did not help
After adding /opt/swift/bin to /etc/profile, I got other errors:

cca745000cc4:/var/log/s6-uncaught-logs# cat current
2024-06-21 10:12:57.877741500 [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
2024-06-21 10:12:57.948843500 [s6-init] ensuring user provided files have correct perms...exited 0.
2024-06-21 10:12:57.950763500 [fix-attrs.d] applying ownership & permissions fixes...
2024-06-21 10:12:57.952907500 [fix-attrs.d] logging: applying...
2024-06-21 10:12:57.979778500 s6-envuidgid: fatal: unknown user: syslog
2024-06-21 10:12:57.980446500 [fix-attrs.d] logging: exited 0.
2024-06-21 10:12:57.981849500 [fix-attrs.d] srv_node: applying...
2024-06-21 10:12:58.026262500 [fix-attrs.d] srv_node: exited 0.
2024-06-21 10:12:58.027750500 [fix-attrs.d] swift: applying...
2024-06-21 10:12:58.094892500 [fix-attrs.d] swift: exited 0.
2024-06-21 10:12:58.096434500 [fix-attrs.d] tmp: applying...
2024-06-21 10:12:58.110325500 [fix-attrs.d] tmp: exited 0.
2024-06-21 10:12:58.111560500 [fix-attrs.d] done.
2024-06-21 10:12:58.112891500 [cont-init.d] executing container initialization scripts...
2024-06-21 10:12:58.114941500 [cont-init.d] 01_swift_logs: executing...
2024-06-21 10:12:58.117697500 ln: /var/log/swift/all.log: File exists
2024-06-21 10:12:58.119390500 ln: /var/log/swift/proxy_access.log: File exists
2024-06-21 10:12:58.120357500 [cont-init.d] 01_swift_logs: exited 1.
2024-06-21 10:12:58.121858500 [cont-init.d] 02_build_remakerings: executing...
2024-06-21 10:12:58.129773500 [[ checking --privileged ]]
2024-06-21 10:12:58.130977500 ip: RTNETLINK answers: Operation not permitted
2024-06-21 10:12:58.131143500 storage type is internal_dirs. container is privileged? false
2024-06-21 10:12:58.131149500 [[ checking what to use as storage devices ]]
2024-06-21 10:12:58.132570500 [[ creating directories ]]
2024-06-21 10:12:58.133714500 created /srv/node/swift-d0
2024-06-21 10:12:58.134702500 created /srv/node/swift-d1
2024-06-21 10:12:58.135687500 created /srv/node/swift-d2
2024-06-21 10:12:58.136644500 created /srv/node/swift-d3
2024-06-21 10:12:58.137596500 created /srv/node/swift-d4
2024-06-21 10:12:58.138687500 created /srv/node/swift-d5
2024-06-21 10:12:58.141883500 started /etc/swift/remakerings.object with 'swift-ring-build create'
2024-06-21 10:12:58.141987500 started /etc/swift/remakerings.container with 'swift-ring-build create'
2024-06-21 10:12:58.142094500 started /etc/swift/remakerings.account with 'swift-ring-build create'
2024-06-21 10:12:58.144361500 pushed command to add r1z1-127.0.0.1:6200/swift-d0 to /etc/swift/remakerings.object
2024-06-21 10:12:58.144485500 pushed command to add r1z1-127.0.0.1:6201/swift-d0 to /etc/swift/remakerings.container
2024-06-21 10:12:58.144593500 pushed command to add r1z1-127.0.0.1:6202/swift-d0 to /etc/swift/remakerings.account
2024-06-21 10:12:58.144694500 pushed command to add r1z1-127.0.0.1:6200/swift-d1 to /etc/swift/remakerings.object
2024-06-21 10:12:58.144794500 pushed command to add r1z1-127.0.0.1:6201/swift-d1 to /etc/swift/remakerings.container
2024-06-21 10:12:58.144887500 pushed command to add r1z1-127.0.0.1:6202/swift-d1 to /etc/swift/remakerings.account
2024-06-21 10:12:58.144980500 pushed command to add r1z1-127.0.0.1:6200/swift-d2 to /etc/swift/remakerings.object
2024-06-21 10:12:58.145071500 pushed command to add r1z1-127.0.0.1:6201/swift-d2 to /etc/swift/remakerings.container
2024-06-21 10:12:58.145163500 pushed command to add r1z1-127.0.0.1:6202/swift-d2 to /etc/swift/remakerings.account
2024-06-21 10:12:58.145255500 pushed command to add r1z1-127.0.0.1:6200/swift-d3 to /etc/swift/remakerings.object
2024-06-21 10:12:58.145346500 pushed command to add r1z1-127.0.0.1:6201/swift-d3 to /etc/swift/remakerings.container
2024-06-21 10:12:58.145438500 pushed command to add r1z1-127.0.0.1:6202/swift-d3 to /etc/swift/remakerings.account
2024-06-21 10:12:58.145549500 pushed command to add r1z1-127.0.0.1:6200/swift-d4 to /etc/swift/remakerings.object
2024-06-21 10:12:58.145646500 pushed command to add r1z1-127.0.0.1:6201/swift-d4 to /etc/swift/remakerings.container
2024-06-21 10:12:58.145742500 pushed command to add r1z1-127.0.0.1:6202/swift-d4 to /etc/swift/remakerings.account
2024-06-21 10:12:58.145837500 pushed command to add r1z1-127.0.0.1:6200/swift-d5 to /etc/swift/remakerings.object
2024-06-21 10:12:58.145927500 pushed command to add r1z1-127.0.0.1:6201/swift-d5 to /etc/swift/remakerings.container
2024-06-21 10:12:58.146020500 pushed command to add r1z1-127.0.0.1:6202/swift-d5 to /etc/swift/remakerings.account
2024-06-21 10:12:58.146106500 pushed command to rebalance ring into /etc/swift/remakerings.object
2024-06-21 10:12:58.146147500 pushed command to rebalance ring into /etc/swift/remakerings.container
2024-06-21 10:12:58.146186500 pushed command to rebalance ring into /etc/swift/remakerings.account
2024-06-21 10:12:58.146413500 created umbrella /etc/swift/remakerings, with deleting all ring files
2024-06-21 10:12:58.147663500 pushed /etc/swift/remakerings.object to /etc/swift/remakerings
2024-06-21 10:12:58.148738500 deleted /etc/swift/remakerings.object
2024-06-21 10:12:58.149834500 pushed /etc/swift/remakerings.container to /etc/swift/remakerings
2024-06-21 10:12:58.150864500 deleted /etc/swift/remakerings.container
2024-06-21 10:12:58.151998500 pushed /etc/swift/remakerings.account to /etc/swift/remakerings
2024-06-21 10:12:58.153020500 deleted /etc/swift/remakerings.account
2024-06-21 10:12:58.154201500 made remaketings executable (+x)
2024-06-21 10:12:58.156806500 /etc/swift/remakerings: line 2: swift-ring-builder: not found
2024-06-21 10:12:58.156843500 /etc/swift/remakerings: line 3: swift-ring-builder: not found
2024-06-21 10:12:58.156879500 /etc/swift/remakerings: line 4: swift-ring-builder: not found
2024-06-21 10:12:58.156914500 /etc/swift/remakerings: line 5: swift-ring-builder: not found
2024-06-21 10:12:58.156947500 /etc/swift/remakerings: line 6: swift-ring-builder: not found
2024-06-21 10:12:58.156981500 /etc/swift/remakerings: line 7: swift-ring-builder: not found
2024-06-21 10:12:58.157015500 /etc/swift/remakerings: line 8: swift-ring-builder: not found
2024-06-21 10:12:58.157047500 /etc/swift/remakerings: line 9: swift-ring-builder: not found
2024-06-21 10:12:58.157081500 /etc/swift/remakerings: line 10: swift-ring-builder: not found
2024-06-21 10:12:58.157115500 /etc/swift/remakerings: line 11: swift-ring-builder: not found
2024-06-21 10:12:58.157149500 /etc/swift/remakerings: line 12: swift-ring-builder: not found
2024-06-21 10:12:58.157183500 /etc/swift/remakerings: line 13: swift-ring-builder: not found
2024-06-21 10:12:58.157217500 /etc/swift/remakerings: line 14: swift-ring-builder: not found
2024-06-21 10:12:58.157250500 /etc/swift/remakerings: line 15: swift-ring-builder: not found
2024-06-21 10:12:58.157284500 /etc/swift/remakerings: line 16: swift-ring-builder: not found
2024-06-21 10:12:58.157315500 /etc/swift/remakerings: line 17: swift-ring-builder: not found
2024-06-21 10:12:58.157348500 /etc/swift/remakerings: line 18: swift-ring-builder: not found
2024-06-21 10:12:58.157381500 /etc/swift/remakerings: line 19: swift-ring-builder: not found
2024-06-21 10:12:58.157415500 /etc/swift/remakerings: line 20: swift-ring-builder: not found
2024-06-21 10:12:58.157448500 /etc/swift/remakerings: line 21: swift-ring-builder: not found
2024-06-21 10:12:58.157490500 /etc/swift/remakerings: line 22: swift-ring-builder: not found
2024-06-21 10:12:58.157525500 /etc/swift/remakerings: line 23: swift-ring-builder: not found
2024-06-21 10:12:58.157558500 /etc/swift/remakerings: line 24: swift-ring-builder: not found
2024-06-21 10:12:58.157589500 /etc/swift/remakerings: line 25: swift-ring-builder: not found
2024-06-21 10:12:58.158589500 [cont-init.d] 02_build_remakerings: exited 127.
2024-06-21 10:12:58.160133500 [cont-init.d] ~-socklog: executing...
2024-06-21 10:12:58.484035500 [cont-init.d] ~-socklog: exited 0.
2024-06-21 10:12:58.485575500 [cont-init.d] done.
2024-06-21 10:12:58.486993500 [services.d] starting services
2024-06-21 10:12:58.499241500 [services.d] done.
2024-06-21 10:12:58.519582500 Traceback (most recent call last):
2024-06-21 10:12:58.519586500 File "/opt/swift/bin/swift-init", line 20, in <module>
2024-06-21 10:12:58.519605500 from swift.common.manager import Manager, UnknownCommandError, \
2024-06-21 10:12:58.519606500 ImportError: No module named swift.common.manager
2024-06-21 10:12:58.519662500 Traceback (most recent call last):
2024-06-21 10:12:58.519663500 File "/opt/swift/bin/swift-init", line 20, in <module>
2024-06-21 10:12:58.519664500 from swift.common.manager import Manager, UnknownCommandError, \
2024-06-21 10:12:58.519665500 ImportError: No module named swift.common.manager
2024-06-21 10:12:58.519665500 Traceback (most recent call last):
2024-06-21 10:12:58.519668500 File "/opt/swift/bin/swift-init", line 20, in <module>
2024-06-21 10:12:58.519669500 Traceback (most recent call last):
2024-06-21 10:12:58.519669500 File "/opt/swift/bin/swift-init", line 20, in <module>
2024-06-21 10:12:58.519671500 from swift.common.manager import Manager, UnknownCommandError, \
2024-06-21 10:12:58.519677500 ImportError : from swift.common.manager import Manager, UnknownCommandError, \
2024-06-21 10:12:58.519677500 No module named swift.common.manager
2024-06-21 10:12:58.519679500 ImportError: No module named swift.common.manager
2024-06-21 10:12:59.509998500 Traceback (most recent call last):
2024-06-21 10:12:59.510002500 Traceback (most recent call last):
2024-06-21 10:12:59.510003500 File "/opt/swift/bin/swift-init", line 20, in <module>
2024-06-21 10:12:59.510003500 File "/opt/swift/bin/swift-init", line 20, in <module>
2024-06-21 10:12:59.510004500 from swift.common.manager import Manager, UnknownCommandError, \
2024-06-21 10:12:59.510004500 from swift.common.manager import Manager, UnknownCommandError, \
2024-06-21 10:12:59.510005500 ImportErrorImportError: : No module named swift.common.managerNo module named swift.common.manager
2024-06-21 10:12:59.510005500
2024-06-21 10:12:59.510005500 Traceback (most recent call last):
2024-06-21 10:12:59.510006500 File "/opt/swift/bin/swift-init", line 20, in <module>
2024-06-21 10:12:59.510006500 from swift.common.manager import Manager, UnknownCommandError, \
2024-06-21 10:12:59.510006500 ImportError: No module named swift.common.manager

I don't understand how to fix such problems

See original description

Tags:

Revision history for this message

vajrock (vajrock) wrote on 2024-06-21:

docker image openstackswift/saio:py3 is working

description:

updated

Revision history for this message

Tim Burke (1-tim-z) wrote on 2024-06-27:

Thanks for the bug report, and all the investigation so far! I see about three problems so far:

1. Looking at recent image build jobs, there's an error building pyeclib wheels. In particular, when it goes to run

gcc -shared build/temp.linux-x86_64-2.7/src/c/pyeclib_c/pyeclib_c.o -L/usr/lib -L/usr/lib -Wl,-R/usr/lib -lerasurecode -lpython2.7 -o build/lib.linux-x86_64-2.7/pyeclib_c.so

there's a bunch of errors like

ld: /usr/lib/liberasurecode.so: unknown type [0x13] section `.relr.dyn'
ld: skipping incompatible /usr/lib/liberasurecode.so when searching for -lerasurecode

2. Despite the pyeclib wheel-build failure, the image-build job still succeeds

3. We're still advertising the py2 build as "latest"

I'm not actually sure how to address that first one, but I think it may be moot because of the third. I'll try to get a patch together to publish the py3 build as both "py3" and "latest".

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2024-06-27: Related fix proposed to swift (master)

Related fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/swift/+/922983

Changed in swift:
status:	New → In Progress

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2024-06-28: Related fix merged to swift (master)

Reviewed: https://review.opendev.org/c/openstack/swift/+/922983
Committed: https://opendev.org/openstack/swift/commit/f29067631ee2e01c8fcc056bce13b689cb663e59
Submitter: "Zuul (22348)"
Branch: master

commit f29067631ee2e01c8fcc056bce13b689cb663e59
Author: Tim Burke <email address hidden>
Date: Thu Jun 27 14:24:32 2024 -0700

docker: Remove && chaining in install scripts

Something about them threw off the exit-immediately-on-non-zero-exit
behavior when building.

Related-Bug: #2070029
Change-Id: I3e40ebd78a9f8e93c905b24a12f5f54b2d27c2d9

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2024-06-28: Fix merged to swift (master)

Reviewed: https://review.opendev.org/c/openstack/swift/+/896450
Committed: https://opendev.org/openstack/swift/commit/a8be689fc74d1a3d1cf0220e3d4f6ffb087bb1e7
Submitter: "Zuul (22348)"
Branch: master

commit a8be689fc74d1a3d1cf0220e3d4f6ffb087bb1e7
Author: Tim Burke <email address hidden>
Date: Thu Jun 27 14:33:15 2024 -0700

Get rid of py2 docker image builds; switch "latest" to py3

Continue also tagging it "py3" so any users of that tag don't become
stuck in time.

    Closes-Bug: #2037268
    Closes-Bug: #2070029
    Change-Id: I38d9469238d2eb6647414c1107e68ff6f3a15797

Changed in swift:
status:	In Progress → Fix Released

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2024-08-07: Fix proposed to swift (feature/mpu)

Fix proposed to branch: feature/mpu
Review: https://review.opendev.org/c/openstack/swift/+/925875

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2024-09-04: Fix merged to swift (feature/mpu)

Download full text (20.2 KiB)

Reviewed: https://review.opendev.org/c/openstack/swift/+/925875
Committed: https://opendev.org/openstack/swift/commit/31b3823148bbda17d97a34b1fd7dd5cb389a91bb
Submitter: "Zuul (22348)"
Branch: feature/mpu

commit becb3ffc1a6cc39fa506ec130c92dc4efac0234b
Author: Matthew Oliver <email address hidden>
Date: Thu Aug 15 14:20:06 2024 +1000

tests: Attempt to use configured tmp in xprofile tests

    My home server has more strict controls on /tmp as it run selinux etc.
    When running unittests and the default log_filename_prefix deep under
    /tmp gets permission denied. It would be better to override this setting
    in the tests with a good known tmp location

Change-Id: I6c95ca3a0045a8f268802c6abb633bdfb0e56b73

commit 2e11ac32dac6ecdfc890adb4b1fa75dfd4eb5419
Author: Tim Burke <email address hidden>
Date: Tue Nov 14 14:57:06 2023 -0800

docs: Simplify reload-process-tree SVGs

Those were so unwieldy as to be uneditable before.

Change-Id: Ic9f4a0ea6b8e18e1624c516890ab69884a299773

commit 92eebe24c6837ef36302c801547c2de2e2726b2a
Author: Alistair Coles <email address hidden>
Date: Wed Aug 21 14:05:23 2024 +0100

Improve test coverage for proxy object DELETE and POST

Add unit tests for the proxy object controller to cover object DELETE
and POST scenarios.

Change-Id: I625a4cf03ee9d4a270d60fa2dc9795b36bb36bf1

commit 87bf4bf5da2cb0c8f640d96cd4304bec422dbaab
Author: Alistair Coles <email address hidden>
Date: Fri Aug 23 10:53:07 2024 +0100

sharder: rename state to db_state when it's the DB state

    Sharding involves both container DB state transitions and ShardRange
    state transitions. To avoid confusion, always use db_state as the var
    name when referring to the container DB state value.

Change-Id: Iaaf494fd4e02017005cb3811b673f967bd6b5e1d

commit d830703a32d16d4618a30684da92b78bf48deff6
Author: Alistair Coles <email address hidden>
Date: Thu Aug 22 12:11:47 2024 +0100

Setup proxy object GET and HEAD tests correctly

    Some unit tests for the proxy object GET and HEAD path were setup with
    insufficient mock responses. The mock connection would raise
    StopIteration exceptions once the mock responses were exhausted, which
    the object controller would handle as if they were error responses,
    potentially distorting the test scenario.

This patch makes the set_http_connect context manager check for
unexpected requests and raise an AssertionError if any are found.

Change-Id: I47774396d9d0a78ebceea6c628c9412b3ad67a11

commit e6b73612d1dcd0bace2361338e6ae82eb591282b
Author: Matthew Oliver <email address hidden>
Date: Tue Aug 13 17:04:40 2024 +1000

FakeStatsdClient: Stop issuing DNS calls for host.

    Running unittests on my home server, even though is a beast, would be
    painfully slow. Running them on my laptop ran much faster. I tried
    everything and couldn't figure it out.
    Chris, co-author, dug in and after we ran out of options he fired up his
    packet capture and realised most tests were issuing DNS queries for
    `host.`. On my home server, it runs ipv6 dual stack, so thes...

Reviewed:  https://review.opendev.org/c/openstack/swift/+/925875
Committed: https://opendev.org/openstack/swift/commit/31b3823148bbda17d97a34b1fd7dd5cb389a91bb
Submitter: "Zuul (22348)"
Branch:    feature/mpu

commit becb3ffc1a6cc39fa506ec130c92dc4efac0234b
Author: Matthew Oliver <matt@oliver.net.au>
Date:   Thu Aug 15 14:20:06 2024 +1000

tests: Attempt to use configured tmp in xprofile tests
    
    My home server has more strict controls on /tmp as it run selinux etc.
    When running unittests and the default log_filename_prefix deep under
    /tmp gets permission denied. It would be better to override this setting
    in the tests with a good known tmp location
    
    Change-Id: I6c95ca3a0045a8f268802c6abb633bdfb0e56b73

commit 2e11ac32dac6ecdfc890adb4b1fa75dfd4eb5419
Author: Tim Burke <tim.burke@gmail.com>
Date:   Tue Nov 14 14:57:06 2023 -0800

docs: Simplify reload-process-tree SVGs
    
    Those were so unwieldy as to be uneditable before.
    
    Change-Id: Ic9f4a0ea6b8e18e1624c516890ab69884a299773

commit 92eebe24c6837ef36302c801547c2de2e2726b2a
Author: Alistair Coles <alistairncoles@gmail.com>
Date:   Wed Aug 21 14:05:23 2024 +0100

Improve test coverage for proxy object DELETE and POST
    
    Add unit tests for the proxy object controller to cover object DELETE
    and POST scenarios.
    
    Change-Id: I625a4cf03ee9d4a270d60fa2dc9795b36bb36bf1

commit 87bf4bf5da2cb0c8f640d96cd4304bec422dbaab
Author: Alistair Coles <alistairncoles@gmail.com>
Date:   Fri Aug 23 10:53:07 2024 +0100

sharder: rename state to db_state when it's the DB state
    
    Sharding involves both container DB state transitions and ShardRange
    state transitions. To avoid confusion, always use db_state as the var
    name when referring to the container DB state value.
    
    Change-Id: Iaaf494fd4e02017005cb3811b673f967bd6b5e1d

commit d830703a32d16d4618a30684da92b78bf48deff6
Author: Alistair Coles <alistairncoles@gmail.com>
Date:   Thu Aug 22 12:11:47 2024 +0100

Setup proxy object GET and HEAD tests correctly
    
    Some unit tests for the proxy object GET and HEAD path were setup with
    insufficient mock responses.  The mock connection would raise
    StopIteration exceptions once the mock responses were exhausted, which
    the object controller would handle as if they were error responses,
    potentially distorting the test scenario.
    
    This patch makes the set_http_connect context manager check for
    unexpected requests and raise an AssertionError if any are found.
    
    Change-Id: I47774396d9d0a78ebceea6c628c9412b3ad67a11

commit e6b73612d1dcd0bace2361338e6ae82eb591282b
Author: Matthew Oliver <matt@oliver.net.au>
Date:   Tue Aug 13 17:04:40 2024 +1000

FakeStatsdClient: Stop issuing DNS calls for host.
    
    Running unittests on my home server, even though is a beast, would be
    painfully slow. Running them on my laptop ran much faster. I tried
    everything and couldn't figure it out.
    Chris, co-author, dug in and after we ran out of options he fired up his
    packet capture and realised most tests were issuing DNS queries for
    `host.`. On my home server, it runs ipv6 dual stack, so these calls
    would need to timeout before a test can continue.
    
    On finding this `host.` Ben, another co-author, dug into the code and
    found the only reference we have to `host` is in FakeStatsdClient.
    
    Sure enough as I dug a little further it turns out our FakeStatsdClient
    used to override a StatsdClient function `_determine_sock_family(self,
    host, port)` to stop actually creating a real socket.
    However, at some point the StatsdClient was refactored and that method
    was renamed and changed. Which leads to a DNS lookup every time we
    create a debug_logger as it brings up the socket.
    As you can imagine, this happens alot!
    
    This patch overrides the new function that handles to socket creation
    `_set_sock_family_and_target(self, host, port)`. Which eliminates the
    DNS call all together.
    
    Co-Authored-By: Ben Formosa <bformosa@nvidia.com>
    Co-Authored-By: Chris Smart <csmart@nvidia.com>
    Change-Id: Ie393075f79447627714692e3f01bb53e967a71e8

commit f5a8851dae98bc51c052c71bc6c6465eb008df38
Author: Shreeya Deshpande <shreeyad@nvidia.com>
Date:   Thu Aug 1 10:49:25 2024 -0400

Move utils/logs.py related tests out of test_utils
    
    Change-Id: Ie73988edf6be0e38d9004bee04ff46c906a759ff

commit 6a5a681227f21c4663259cf3f63942ffe44091be
Author: Alistair Coles <alistairncoles@gmail.com>
Date:   Wed Aug 7 16:08:12 2024 +0100

tests: don't mutate and re-use Response headers
    
    Some tests in test_account_quotas.py registered a response with
    FakeSwift during setUp and then subsequently mutated the response's
    headers dict. Worse, some tests then mutate the headers again and
    re-use the same response.
    
    This relies on the FakeSwift implementation not copying the original
    headers when the response is registered, which may not remain the case
    (as the author discovered with the Related-Change). It's also an
    unnecessary shortcut.
    
    Change-Id: I3217c17936d0c11b03de4a4a172bb2fb0a2be734
    Related-Change: I84604a7ea049850ad4d0f0cea2096ab8a98dfb4a

commit 9d14c7c830ba92dfa9bcb59efee367c66001479b
Author: Alistair Coles <alistairncoles@gmail.com>
Date:   Fri Aug 2 11:31:35 2024 +0100

expirer stats: add test coverage for 'errors' stat
    
    Drive-by: simplify patching of test expirer instance.
    Drive-by: fix comment spelling.
    
    Related-Change: Ib151c498ba325f39570e963e5b7948080ffcd3d6
    Change-Id: Ia0041c4eedc33a2675890d52cbbc33b9190f1665

commit b400a1fdb3ae609d5f86d4d0f1b590640337b8f0
Author: Jianjian Huo <jhuo@nvidia.com>
Date:   Wed Jul 31 21:30:50 2024 -0700

Expirer: add delete task iteration related metrics
    
    Four new metrics have been added into task iteration process:
        'tasks.parse_errors': count of errors when parsing the task object
        'tasks.skipped': count of task objects skipped because it doesn't
                         belong to this expirer.
        'tasks.delayed': count of objects is still within the delay
        'tasks.assigned': count of assigned objects to this expirer
    
    Co-Authored-By: Alistair Coles <alistairncoles@gmail.com>
    Co-Authored-By: Clay Gerrard <clay.gerrard@gmail.com>
    Change-Id: Ib151c498ba325f39570e963e5b7948080ffcd3d6

commit fd7861313f113652df10bcd31ff5ce79c09007d8
Author: Tim Burke <tim.burke@gmail.com>
Date:   Tue Jul 23 11:00:18 2024 -0700

Pass timeout as kwarg
    
    Cleans up a deprecation warning:
    
        DeprecationWarning: Passing more than 1 positional argument to
        _sqlite3.Connection() is deprecated. Parameters 'timeout',
        'detect_types', 'isolation_level', 'check_same_thread', 'factory',
        'cached_statements' and 'uri' will become keyword-only parameters
        in Python 3.15.
    
    Change-Id: I2b11487f8174e36b024c503d7e78de1904e0a281

commit 7c7ab03e2d984d68b0d3330bb698242e16f18a30
Author: Tim Burke <tim.burke@gmail.com>
Date:   Tue Jul 23 10:48:33 2024 -0700

Implement context manager protocol for logging mutexes
    
    Newer versions of python expect to be able to say `with self.lock:`
    down in logging.
    
    See https://github.com/python/cpython/commit/74723e11
    
    Change-Id: I30305566d12a1b8be4c8bde4b416b798322a1385

commit 78278c11a63d8abb697c37a0d990dc5b6e08396f
Author: Matthew Oliver <matt@oliver.net.au>
Date:   Wed Jul 24 16:16:17 2024 +1000

account info: Add --sync/-s option
    
    The container-info cli already supports the --sync/-s option to view
    incoming and outgoing syncs from the db. Account works exactly the same
    way. And hey be might want to interrogate who an account has been
    syncing with. So it should have the same option.
    
    This patch adds the same option to account_main parser:
    
      $ swift-account-info <path_to_account> -s
      Path: /a2
        Account: a2
        Deleted: False
        Account Hash: c1e207026da71a9237c5d9e206b9ec59
      Metadata:
        Created at: 2024-07-24T06:08:28.760490 (1721801308.76049)
        Put Timestamp: 2024-07-24T06:08:28.743650 (1721801308.74365)
        Delete Timestamp: 1970-01-01T00:00:00.000000 (0)
        Status Timestamp: 2024-07-24T06:08:28.743650 (1721801308.74365)
        Container Count: 10
        Object Count: 100
        Bytes Used: 880
        Chexor: 0673fe17a762662d74e8d3ad93e0785b
        UUID: 705ac602-5e85-49ef-92a4-3082d40cad4f-sdb3
      ...
      Incoming Syncs:
        Sync Point  Remote ID                                       Updated At
        10          285bbaae-90da-409a-9533-f0d113764e44-sdb4       2024-07-24T06:10:34.000000 (1721801434)
        11          80c45862-dcd3-4ffe-9659-91851276d244-sdb2       2024-07-24T06:10:35.000000 (1721801435)
      Outgoing Syncs:
        Sync Point  Remote ID       Updated At
      ...
    
    Change-Id: I1aa96e97281421c69cb75ea24ce427c20c4c615e

commit c3e1d91d1f3c03670fb051ad04df70a3de478266
Author: Tim Burke <tim.burke@gmail.com>
Date:   Tue Jul 23 11:47:48 2024 -0700

Move remaining bin scripts to cli modules
    
      - swift-account-audit
      - swift-config
      - swift-drive-audit
      - swift-get-nodes
      - swift-reconciler-enqueue
      - swift-oldies
      - swift-orphans
    
    Related-Change: Ifcc8138e7b55d5b82bea0d411ec6bfcca2c77c83
    Change-Id: Ie4a252ec51d23caa9e90e6c2f772847d0d71b1c8

commit 2c5dc64d2562030ba4976b1c88462e1ebf8717c4
Author: Tim Burke <tim.burke@gmail.com>
Date:   Wed Jun 26 12:15:07 2024 -0700

Pull swift-*-info scripts into swift.cli.info
    
    Related-Change: Ifcc8138e7b55d5b82bea0d411ec6bfcca2c77c83
    Change-Id: I2718d8b96193d13f913824fc1091d72737d755ea

commit dd86cecac1b1afe2255d008a521a2c6d9577d931
Author: Pete Zaitcev <zaitcev@yahoo.com>
Date:   Tue Jul 23 14:55:53 2024 -0500

AUTHORS: update Zaitcev
    
    Unfortunately, kotori had to be switched to a whitelist,
    so it's not appropriate for a public address list anymore.
    
    Change-Id: I86f10fcf4fd0bc5902c3dad49c6f3019fa159b64

commit 78b986cb390ad6e985b930ec6892b4efa226f53a
Author: Tim Burke <tim.burke@gmail.com>
Date:   Wed Jul 17 11:07:39 2024 -0700

swift-drive-audit: Work with ISO timestamps
    
    Recent OSes are using ISO format for their kernel logs.
    
    Closes-Bug: #2072609
    Change-Id: I92fce513d06d8b0875dabf9e9a1b2c5a3a79d9b5

commit e984de864dd0895f4bde81bed56691c48e7cea52
Author: Alistair Coles <alistairncoles@gmail.com>
Date:   Wed Jul 17 10:14:24 2024 +0100

trivial: assert non_negative_int treats float as valid
    
    Prior to the Related-Change, non_negative_int would raise a ValueError
    if it was passed a positive float. It now casts the float to an int,
    which is consistent with the docstring.
    
    This patch adds test assertions to verify this behavior, and similar
    behavior of config_positive_int_value.
    
    Change-Id: I5d62e14c228544af634190f16321ee97a8c4211c
    Related-Change: I06508279d59fa57296dd85548f271a7812aeb45f

commit d555755423c179d23ef02ab2e0b856fd2b04fa71
Author: Alistair Coles <alistairncoles@gmail.com>
Date:   Tue Jul 16 10:42:21 2024 +0100

proxy_logging config: unit tests and doc pointers
    
    Add unit tests to verify the precedence of access_log_ and log_
    prefixes to options.
    
    Add pointers from proxy_logging sections in other sample config files
    to the proxy-server.conf-sample file.
    
    Change-Id: Id18176d3790fd187e304f0e33e3f74a94dc5305c

commit 2e06b771edfc874448939c25748fb248f01884ab
Author: Tim Burke <tim.burke@gmail.com>
Date:   Tue Jun 25 16:32:37 2024 -0700

Pull swift-dispersion-populate to its own module
    
    Related-Change: Ifcc8138e7b55d5b82bea0d411ec6bfcca2c77c83
    Change-Id: I7f479359f94f102414f30e8aac87f377d10d34ee

commit 006fa6b3a7504b828f74e39cfeee635a20f3b709
Author: Tim Burke <tim.burke@gmail.com>
Date:   Tue Jun 25 16:28:27 2024 -0700

Use entry_points for swift-init
    
    I *think* swift.common.manager is a reasonable place for it?
    
    Related-Change: Ifcc8138e7b55d5b82bea0d411ec6bfcca2c77c83
    Change-Id: I48a345eedbf2369d481d18c0e2db37845673b647

commit 8f9d7db7f12527f0d848d0c89c60755ee14bc58b
Author: Tim Burke <tim.burke@gmail.com>
Date:   Mon Jun 17 13:14:53 2024 -0700

Use entry_points for a bunch more executables
    
    See https://review.opendev.org/c/openstack/swift/+/918365 for motivation.
    
    A handful of [files]scripts entries still remain, but they're more
    involved to change over. These ones were all fairly mechanical to fix.
    
    Related-Change: Ifcc8138e7b55d5b82bea0d411ec6bfcca2c77c83
    Change-Id: Ia43d7cd3921bc6c9ff0cee3100ef5f486fd3edcb

commit 6105b38e65b00c23d373e17ad9f89e4243395165
Author: Mohammed Al-Jawaheri <mjawaheri02@gmail.com>
Date:   Sun Jun 9 18:16:05 2024 +0300

add object-count quota for accounts in middleware
    
    It is currently possible to configure "X-Container-Meta-Quota-Bytes"
    and "X-Container-Meta-Quota-Count" on containers, as well as
    "X-Account-Meta-Quota-Bytes" on accounts. However, there is no way
    to configure an account quota limit for the number of files or
    "quota-count". This limitation could potentially allow a user to
    exhaust filesystem inodes.
    
    This change introduces the "X-Account-Meta-Quota-Count" header,
    allowing users with the ResellerAdmin role to add a quota-count
    limit on accounts. The middleware will enforce this limit similarly
    to the existing quota-byte limit.
    
    Co-authored-by: Azmain Adib <adib1905@gmail.com>
    Co-authored-by: Daanish Khan <daanish1337@gmail.com>
    Co-authored-by: Mohamed Hassaneen <mohammedashoor89@gmail.com>
    Co-authored-by: Nada El-Mestkawy <nadamaged05@gmail.com>
    Co-authored-by: Tra Bui <trabui.0517@gmail.com>
    
    Change-Id: I1d11b2974de8649a111f2462a8fef51039e35d7f

commit e8affa7db5817e50cd82130a8f4c250725b80884
Author: Matthew Oliver <matt@oliver.net.au>
Date:   Wed Mar 8 12:28:14 2023 +1100

Pass db_state to container-update and async_pending
    
    When the proxy passes the container-update headers to the object server
    now include the db_state, which it already had in hand. This will be
    written to async_pending and allow the object-updater to know more about
    a container rather then just relying on container_path attribute.
    
    This patch also cleans up the PUT, POST and DELETE _get_update_target
    paths refactoring the call into _backend_requests, only used by these
    methods, so it only happens once.
    
    Change-Id: Ie665e5c656c7fb27b45ee7427fe4b07ad466e3e2

commit 0fd36e395dbe05fb77a4e76bc6ea4c83597d86ff
Author: Jianjian Huo <jhuo@nvidia.com>
Date:   Tue Jul 2 08:37:12 2024 -0700

common: move memcached exceptions to the base file.
    
    Change-Id: I022404cd90d9755a09c20619c3a72588d3367467

commit 0c9a524bee2adf2afab83c45d12ff7457640d97d
Author: Tim Burke <tim.burke@gmail.com>
Date:   Fri Jun 28 10:08:42 2024 -0700

Provide content-type for long description in dists
    
    Previously, `twine check <swift wheel>` would report
    
       WARNING  `long_description_content_type` missing.
       defaulting to `text/x-rst`.
    
    Change-Id: I5d004218515d17b8cbace46b2c1e646f734779f3

commit 64086c30915349b1b6440aa2de36f753bbb0741c
Author: Cyril Roelandt <cyril@redhat.com>
Date:   Fri Jun 28 01:37:09 2024 +0200

Python 3.12: do not use ssl.wrap_socket
    
    The ssl.wrap_socket method has been removed in 3.12.
    SSLContext.wrap_socket should now be used.
    
    Change-Id: I6119e054289eac263ff5448d7d118209f98678d9

commit a8be689fc74d1a3d1cf0220e3d4f6ffb087bb1e7
Author: Tim Burke <tim.burke@gmail.com>
Date:   Thu Jun 27 14:33:15 2024 -0700

Get rid of py2 docker image builds; switch "latest" to py3
    
    Continue also tagging it "py3" so any users of that tag don't become
    stuck in time.
    
    Closes-Bug: #2037268
    Closes-Bug: #2070029
    Change-Id: I38d9469238d2eb6647414c1107e68ff6f3a15797

commit f29067631ee2e01c8fcc056bce13b689cb663e59
Author: Tim Burke <tim.burke@gmail.com>
Date:   Thu Jun 27 14:24:32 2024 -0700

docker: Remove && chaining in install scripts
    
    Something about them threw off the exit-immediately-on-non-zero-exit
    behavior when building.
    
    Related-Bug: #2070029
    Change-Id: I3e40ebd78a9f8e93c905b24a12f5f54b2d27c2d9

commit 130377bd271543708141eefc9c0d5afbf19e501d
Author: Alistair Coles <alistairncoles@gmail.com>
Date:   Tue Jun 25 10:45:22 2024 +0100

proxy-server: log correct path when listing parsing fails
    
    The proxy may use a sub-request to fetch a container listing response,
    for example for updating shard ranges. If it then fails to parse the
    response, it should use the sub-request path when logging a warning or
    error. Before, the proxy would use the original request path which may
    have been to an object.
    
    Change-Id: Id904f4cc0f911f9e6e53d4b3ad7f98aacd2b335d

commit 6220a473f3ad2b5238717de832f508b557c6586c
Author: Tim Burke <tim.burke@gmail.com>
Date:   Wed Apr 26 11:59:44 2023 -0700

Support tox4
    
    Change-Id: If15c3fee706d295de678f812839a5d0759089ccf

commit a7b69628d57370831998f4bd34df7f4ae6752e00
Author: Alistair Coles <alistairncoles@gmail.com>
Date:   Tue Jun 25 16:29:19 2024 +0100

trivial: assert SendtoCalls consistently
    
    Use same assertion pattern as introduced in the Related-Change and
    include the host and port in the assertion.
    
    Change-Id: I7cccf3b8cdfe157c27fb8e0b1f432a649970a865
    Related-Change: I9a016de1010dd17e91bc85877413b34d2c3287c7

commit a21d078009e2750b8a513dd9f832723c3b51dbe0
Author: Tim Burke <tim.burke@gmail.com>
Date:   Fri Sep 29 11:15:51 2023 -0700

tests: Check proxy-logging stats on the wire
    
    With labeled metrics on the horizon, I wanted some more end-to-end
    tests of stats emission.
    
    Change-Id: I9a016de1010dd17e91bc85877413b34d2c3287c7

commit 0c58afc7ee23fd5e5cca19318e3f055dcc79e021
Author: Shreeya Deshpande <shreeyad@nvidia.com>
Date:   Sun May 12 15:38:07 2024 -0700

Add get_statsd_client function
    
    It takes a config dict and some caller-specific options, similar to
    get_logger. Use this in get_logger, so our logging module doesn't
    need to know anything about statsd config options.
    
    Co-Authored-By: yanxiao@nvidia.com
    Change-Id: I5ae2cc5c257fb8d7eab885977d9d9cf602224ec7

commit 5d640985f7c7104b8ce9992c63c159c58c85ebe8
Author: Alistair Coles <alistairncoles@gmail.com>
Date:   Thu Jun 6 12:55:35 2024 +0100

s3api: include error response reason in log_info
    
    There's a variety of reasons why s3api may return a 4xx or 5xx
    response. It's useful to get some more detail in the log message,
    particularly when the request is a HEAD which won't get any detail in
    the response body.
    
    Change-Id: I0a499dc5c50bb534a23adcbfe7c3822d8954b0e0

commit 68adc5bff358cde91544c63f5ae21277cba3cc29
Author: Tim Burke <tim.burke@gmail.com>
Date:   Tue Jun 18 16:28:16 2024 -0700

CI: up-rev a few py2 constraints
    
    Noticed a few more projects had final py2 releases.
    
    Change-Id: I144efd5ee670a5a6b444fbc31e9434fac31bf2ec

commit 415420cc8ff6ecd2a1c39e0ff66066ba691f5874
Author: Tim Burke <tim.burke@gmail.com>
Date:   Mon May 6 15:10:26 2024 -0700

Use entry_points for server executables
    
    The old [files]scripts method of specifying executable Python scripts
    triggers some legacy easy-install-like mode for editable installs,
    which relies on pkg_resources. Recent versions of setuptools (67.5.0+)
    have started emitting warnings when importing pkg_resources, which in
    turn cause quite noticeable slowdowns in process startup. This is
    particularly prominant on py312, which stopped pre-installing (an often
    older version of) setuptools in new venvs.
    
    See also:
     - https://github.com/python/cpython/issues/95299
     - https://github.com/pypa/setuptools/pull/3843
     - https://github.com/pypa/setuptools/issues/3966
    
    Now, use [entry_points]console_scripts to specify these executables,
    which does not use pkg_resources in the generated script files.
    
    Change-Id: Ifcc8138e7b55d5b82bea0d411ec6bfcca2c77c83

commit fa088eb72d17aa37e72ce479411a48ea70e4d92e
Author: Tim Burke <tim.burke@gmail.com>
Date:   Fri Jun 23 12:08:28 2023 -0700

obj: Close replicator/reconstructor connections
    
    Change-Id: I02591038a089ce43684f0245665349e40381d75a

tags:

added: in-feature-mpu

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2024-09-12: Fix included in openstack/swift 2.34.0

This issue was fixed in the openstack/swift 2.34.0 release.

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

auto-github-pypa-setuptools #3966
[open bug Needs Triage] Edit
auto-github-python-cpython #95299
[closed type-feature 3.12 topic-ensurepip] Edit

Bug watches keep track of this bug in other bug trackers.