-
Notifications
You must be signed in to change notification settings - Fork 1.1k
/
CHANGELOG
4755 lines (3146 loc) · 186 KB
/
CHANGELOG
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
swift (2.33.0, OpenStack Caracal)
* S3 API fixes:
* When the `+segments` container's storage policy differs from that of
the primary container, completed manifests are now written with the
correct policy in the primary container.
* Add basic read support for object locking. This improves
compatibility with an Ansible S3 module. Write support is not
yet implemented, so get-object-lock-configuration will always 404.
* If there's a conflict deleting the in-progress-upload marker when
completing a multipart-upload, a 503 is now returned to the client,
prompting it to retry.
* Added `Accept-Ranges: bytes` to object responses. Range requests
have always been supported; now, that support is properly advertised.
* Static large object fixes:
* Fixed a server error when handling conditional GET requests.
* Return an error if the SLO manifest could not be parsed. Previously,
a zero-byte response was returned.
* Proxy server fixes:
* Added a new `swift.proxy_logging_status` request environment key that
middlewares may use to override the logged status for a request.
* Transaction IDs are included in more error responses.
* Added a counter metric when caching shard ranges.
* The `recoverable_node_timeout` option no longer applies to
`X-Newest` GET requests.
* Improved error-handling in multi-part range responses.
* Sharding fixes:
* Prevent resets of a shard range's epoch.
* Cleaned up `X-Backend-*` headers in listing responses.
* Reduced the frequency of `Reclaimable db stuck waiting for shrinking`
messages when a root DB has been deleted but its shards have not been
shrunk away.
* The more-efficient shard range structure from the last release is now
used when fetching ranges from the backend.
* Include more information in shard-replication warnings.
* Object server fixes:
* Object POSTs and chunked PUTs are no longer accepted when the target
drive is already past its `fallocate_reserve`. DELETEs are still
allowed.
* Added the ability to configure cooperative yielding when servicing
GET responses, via the `cooperative_period` option. See the example
config for more information.
* Invalid `hashes.invalid` entries are now ignored, rather than
causing a complete partition rehash.
* Prefix-based tempurls may now be used to explore staticweb
listings within that prefix. Note that this opens a new ability
to list containers from tempurls, but only if staticweb's
`X-Container-Meta-Web-Listings` is enabled.
* When generating index pages from listings, staticweb now sends an HTML5
doctype. This makes them https://peps.python.org/pep-0503/ compliant,
allowing their continued use for simple Python package repositories.
* Per-service `auto_create_account_prefix` configuration options have
been removed. These options were deprecated in favor of `swift.conf`
configuration in Swift 2.24.0, part of the OpenStack Ussuri release.
* Added a `swift-reload` command to assist with safely reloading WSGI
servers.
* Daemons now send `STOPPING` and `RELOADING` systemd notifications
when the service is configured with `Type=notify`.
* Added more metrics to the container-server, allowing GET and PUT timings
to be broken out for listings, shard range operations, and container
creation.
* Daemons send object updates via the replication network in more cases.
* `swift-account-info` and `swift-container-info` now accept a `--sync`
flag to show information from the incoming/outgoing sync tables.
* Several fixes to prepare for Python 3.12 support. While not yet tested
in the gate, initial manual testing looks promising.
* Added support for recent versions of eventlet.
* The dark-data object audit watcher now works with sharded containers.
Previously, it would think that all data files were absent from
listings.
* Various other minor bug fixes and improvements.
swift (2.32.0, OpenStack Bobcat)
* Python 3 fixes:
* Python 3 object servers can now read unencrypted non-ASCII metadata
that was written under Python 2.
* Ssync no longer corrupts unencrypted non-ASCII metadata during
transfers.
* Fixed an encoding issue when writing non-ASCII object names to sharded
containers and shard range caching is not enabled.
* Fixed an encoding issue when handling non-ASCII account names.
* Fixed a `generator already executing` error on client disconnect.
* Suppressed `RemoteDisconnected` tracebacks.
* Metrics improvements:
* Metrics are now emitted for a variety of S3 error responses, in the
form `s3api.<status_int>.<error_class>[.<reason>]`
* Fixed an issue that prevented proxy servers from emitting metrics and
logs for backend requests made when getting account or container info.
* Account and container info metrics now include the response status code
when backend requests are made.
* Added timing metrics to the container sharder for various operations.
* Python 3.11 is now supported.
* Added the ability for reseller admins to set per-policy account quotas by
posting metadata of the form `X-Account-Quota-Bytes-Policy-<policy name>`.
* Added a `keepalive_timeout` option to the proxy server to limit how long
to wait for a client to initiate a request, separate from the general
`client_timeout` option. Note that this requires eventlet 0.34.0
(currently unreleased) or later.
* Added a `keep_cache_slo_manifest` option to the object server to better
control whether SLO manifests are dropped from the page cache.
* WSGI servers now accept a `--test-config` option that may be used to
validate configuration changes before reloading/restarting the server.
* The structure of cached shard ranges has changed, improving performance
when listing or writing to sharded containers. Note that immediately
after upgrade, the new structures will all be cache misses, which may
lead to a thundering herd problem. To avoid this, upgrade just a few
nodes first, let them service some fraction of traffic to populate the
cache, then upgrade the rest of the cluster.
* A variety of performance improvements have been made for sharded
container databases.
* Various logging and metrics improvements when talking to memcache.
* Fixed ssync's handling of timestamp offsets. Previously, this could cause
ssync to fail with a 409 Conflict, causing the transfer to fail and
preventing handoffs from clearing.
* Fixed an issue where an erasure-coded PUT could prevent other requests
from being processed when network calls rarely or never blocked.
* Fixed an issue when downloading an SLO manifest would hit a recoverable
error and attempt to resume from another node. This would manifest as
either a pyeclib decode error or an unexpected empty response.
* The proxy server now applies error-limiting to the correct node when
handling a recoverable node error.
* Account, container, and object log fields are now correctly identified
when returning `BadDigest` responses to S3 requests.
* Previously, under some circumstances, a non-standard config option such
as `RECLAIM_AGE` might get parsed as `reclaim_age` for some processes
but ignored by others. Now, all config parsing is case-sensitive;
non-standard names will always be ignored.
* Reduced the backend load of making `?versions` requests to a container
that has never had object versioning enabled.
* Improved formatting of meta and sysmeta for `swift-account-info` and
`swift-container-info`.
* The standard-library `logging` module is no longer monkey-patched when
importing `swift.common.utils`, making it easier to re-use swift code
in other contexts.
* Removed the hard dependency on netifaces; it may still be used if the
`getifaddrs` C function is not available. This fallback support may be
removed in a future release.
* Various other minor bug fixes and improvements.
swift (2.31.1, OpenStack Antelope)
* Sharding fixes
* Shards no longer report stats to the root database when they are in
the CREATED state.
* Sharding metadata is no longer cleared when databases are deleted.
This could previously cause deleted shards that still had rows to
become stuck and never move them to the correct database.
* Fixed a performance regression in the handling of misplaced objects.
* Swift path and on-disk path are now included with all sharder logging.
* `s3token` no longer mangles request paths that include the Access Key ID.
* User metadata is now exposed via CORS when encryption is enabled,
matching the behavior when encryption is not enabled.
* Fewer backend requests are now required when account or container
information is missing from memcache.
* Fixed logging of IP and port in the proxy-server; in particular,
internal clients now correctly log about the replication IP/port.
* Fixed a bug in the object replicator that would cause an under-reporting
of failures.
* Various other minor bug fixes.
swift (2.31.0)
* S3 API improvements
* Fixed a security issue in how `s3api` handles XML parsing that allowed
authenticated S3 clients to read arbitrary files from proxy servers.
Refer to CVE-2022-47950 for more information.
* Fixed a server error when handling malformed CompleteMultipartUpload
requests.
* Improved error reporting when attempting to set invalid `X-Delete-At`
or `X-Delete-After` values via the S3 API.
* Sharding improvements
* Sync more shard ranges from the root database to the shards. This
helps ensure shard range repairs effected at the root make their way
to shards that would otherwise be stuck trying to further divide
into sub-shards.
* Added a `merge` subcommand to `swift-manage-shard-ranges` to merge
arbitrary shard ranges into a container DB. Minimal safety checks
are performed; it should only be used for emergency shard range
manipulation by expert users.
* Improved performance of `delimiter` listings for sharded containers.
* Added more safety checks to the `repair` subcommand of
`swift-manage-shard-ranges`.
* Better handle `EOFError` and `KeyboardInterrupt` when prompting for
input in `swift-manage-shard-ranges`.
* Warnings are now emitted when sharding appears to have become stuck.
Use the new `container_sharding_timeout` option to configure the
"stuck" threshold; the default is 48 hours.
* Stop warning about transient overlaps when auditing shard ranges.
* Metrics improvements
* Added timing stats for memcached operations.
* Renamed and improved the granularity of shard range cache and
backend stats. Metrics dashboards may need to be updated.
* Emit stats when backend nodes are error-limited.
* Added support for Python 3.10.
* Added an optional `backend_ratelimit` middleware for backend servers.
See the backend server sample configuration files for more information.
* Added the ability to configure a chance to skip checking memcache when
querying account and container information. This allows some fraction
of traffic to go to disk and refresh memcache before the key ages out.
Recommended values for the new `account_existence_skip_cache_pct` and
`container_existence_skip_cache_pct` options are in the range of
0.0 to 0.01.
* Static large object segments may now be deleted asynchronously by
default. Operators may return to the old behavior by disabling the
`allow_async_delete` option in the `[filter:slo]` section
in their proxy-server.conf.
* Absolute-form request targets are now accepted. This enables access for
certain clients and SDKs (including some older versions of rclone that
were using an old version of aws-sdk-go).
* Fixed a path-rewriting bug introduced in Python 3.7.14, 3.8.14, 3.9.14,
and 3.10.6 that could cause some `domain_remap` requests to be routed to
the wrong object.
* Fixed a server error when attempting to access data in a deleted
container that had an erasure-coded storage policy.
* Improved error messages to clients that encounter errors using the
`formpost` middleware.
* Removed some inappropriate error-suppression when locking account and
container databases.
* Improved server start-up time when using multiple workers.
* Removed some unnecessary locking when logging.
* Added some basic object-metadata validation; invalid diskfiles will be
quarantined via the auditor or reconstructor.
* Enhanced logging when error-limiting a backend node.
* Various other minor bug fixes and improvements.
swift (2.30.1, zed stable backports)
* Fixed a security issue in how `s3api` handles XML parsing that allowed
authenticated S3 clients to read arbitrary files from proxy servers.
Refer to CVE-2022-47950 for more information.
* Fixed a path-rewriting bug introduced in Python 3.7.14, 3.8.14, 3.9.14,
and 3.10.6 that could cause some `domain_remap` requests to be routed to
the wrong object.
swift (2.30.0, OpenStack Zed)
* Sharding improvements
* The `swift-manage-shard-ranges` tool has a new mode to repair gaps
in the namespace.
* Misplaced tombstone records are now properly cleaved.
* Fixed a bug where the sharder could fail to find a device to use for
cleaving.
* Databases marked deleted are now processed by the sharder.
* More information is now synced to the fresh database when sharding.
Previously, a database could lose the fact that it had been marked
as deleted.
* Shard ranges with no rows to cleave could previously be left in the
CREATED state after cleaving. Now, they are advanced to CLEAVED.
* Metrics are now emitted for whether databases used for cleaving
were created or already existed, allowing a better understanding
of the reason for handoffs in the cluster.
* Misplaced-record stats are now also emitted to statsd. Previously,
these were only available in logs.
* S3 API improvements
* Constant-time string comparisons are now used when checking signatures.
* Fixed cross-policy object copies. Previously, copied data would
always be written using the source container's policy. Now, the
destination container's policy will be used, avoiding availability
issues and unnecessary container-reconciler work.
* More headers are now copied from multi-part upload markers to their
completed objects, including `Content-Encoding`.
* When running with `s3_acl` disabled, `bucket-owner-full-control` and
`bucket-owner-read` canned ACLs will be translated to the same Swift
ACLs as `private`.
* The S3 ACL and Delete Multiple APIs are now less case-sensitive.
* Improved the error message when deleting a bucket that's ever had
versioning enabled and still has versions in it.
* `LastModified` timestamps in listings are now rounded up to whole
seconds, like they are in responses from AWS.
* Proxy logging for Complete Multipart Upload requests is now more
consistent when requests have been retried.
* Logging improvements
* Signal handling is more consistently logged at notice level.
Previously, signal handling would sometimes be logged at info
or error levels.
* The message template for proxy logging may now include a
`{domain}` field for the client-provided `Host` header.
* The object-replicator now logs successful rsync transfers at debug
instead of info.
* Added a `log_rsync_transfers` option to the object-replicator.
Set it to false to disable logging rsync "send" lines; during
large rebalances, such logging can overwhelm log aggregation
while providing little useful information.
* Transaction IDs are now only included in daemon log lines
in a request/response context.
* Fixed a socket leak when clients try to delete a non-SLO as though
it were a Static Large Object.
* The formpost digest algorithm is now configurable via the new
`allowed_digests` option, and support is added for both SHA-256
and SHA-512. Supported formpost digests are exposed to clients in
`/info`. Additionally, formpost signatures can now be base64 encoded.
* Added metrics to the formpost and tempurl middlewares to monitor
digest usage in signatures.
* SHA-1 signatures are now deprecated for the formpost and tempurl
middlewares. At some point in the future, SHA-1 will no longer be
enabled by default; eventually, support for it will be removed
entirely.
* Improved compatibility with certain FIPS-mode-enabled systems.
* Added a `ring_ip` option for various object services. This may be
used to find own devices in the ring in a containerized environment
where the `bind_ip` may not appear in the ring at all.
* Account and container replicators can now be configured with a
`handoff_delete` option, similar to object replicators and
reconstructors. See the sample config for more information.
* Developers using Swift's memcache client may now opt in to having
a `MemcacheConnectionError` be raised when no connection succeeded
using a new `raise_on_error` keyword argument to `get`/`set`.
* The tempurl middleware has been updated to return a 503 if storing a
token in memcache fails. Third party authentication middlewares are
encouraged to also use the new `raise_on_error` keyword argument
when storing ephemeral tokens in memcache.
* Pickle support has been removed from Swift's memcache client. Support
had been deprecated since Swift 1.7.0.
* Device names are now included in new database IDs. This provides more
context when examining incoming/outgoing sync tables or sharding
CleaveContexts.
* Database replication connections are now closed following an error
or timeout. This prevents a traceback in some cases when the replicator
tries to reuse the connection.
* `ENOENT` and `ENODATA` errors are better handled in the object
replicator and auditor.
* Improved object update throughput by shifting some shard range
filtering from Python to SQL.
* Include `Vary: Origin` header when CORS responses vary by origin.
* The staticweb middleware now allows empty listings at the root of
a container. Previously, this would result in a 404 response.
* Ring builder output tables better display weights over 1000.
* Various other minor bug fixes and improvements.
swift (2.29.2, yoga stable backports)
* Fixed a security issue in how `s3api` handles XML parsing that allowed
authenticated S3 clients to read arbitrary files from proxy servers.
Refer to CVE-2022-47950 for more information.
* Constant-time string comparisons are now used when checking S3 API
signatures.
* Fixed a path-rewriting bug introduced in Python 3.7.14, 3.8.14, 3.9.14,
and 3.10.6 that could cause some `domain_remap` requests to be routed to
the wrong object.
* Improved compatibility with certain FIPS-mode-enabled systems.
swift (2.29.1, OpenStack Yoga)
* This is the final stable branch that will support Python 2.7.
* Fixed s3v4 signature calculation when the client sends an un-encoded
path in the request.
* Fixed multiple issues in s3api involving Multipart Uploads with
non-ASCII names.
* The object-updater now defers rate-limited updates to the end of its
cycle; these deferred updates will be processed (at the limited rate)
until the configured `interval` elapses. A new `max_deferred_updates`
option may be used to bound the deferral queue.
* Empty account and container partition directories are now cleaned up
immediately after replication, rather than needing to wait for an
additional replication cycle.
* The object-expirer now only cleans up empty containers. Previously, it
would attempt to delete all processed containers, regardless of whether
there were entries which were skipped or had errors.
* A new `item_size_warning_threshold` option may be used to monitor for
values that are approaching the limit of what can be stored in memcache.
See the memcache sample config for more information.
* Internal clients now correctly use their configured User-Agent in
backend requests, rather than only using it for logging.
* Various other minor bug fixes and improvements.
swift (2.29.0)
* S3 API improvements
* CORS preflights are now allowed for pre-signed URLs.
* The `storage_domain` option now accepts a comma-separated list of
storage domains. This allows multiple storage domains to configured
for use with virtual-host style addressing.
* Fixed the types of configured values in /info response.
* Fixed a server error when trying to copy objects with non-ASCII names.
* Fixed a server error when uploading objects with very long names.
A KeyTooLongError is now returned.
* Fixed an error when multi-deleting MPUs when SLO async-deletes
are enabled.
* Fixed an error that allowed list-uploads and list-parts requests to
return incomplete or out-of-order results.
* Fixed several bugs when dealing with non-ASCII object names and
multipart uploads.
* Reduced the overhead of retrieving bucket and object ACLs.
* Replication, reconstruction, and diskfile improvements
* The reconstructor now uses the replication network to fetch fragments
for reconstruction.
* Added the ability to limit how many objects per handoff partition
will be reverted in a reconstructor cycle using the new
`max_objects_per_revert` option. This may be useful to reduce
ssync timeouts and lock contention, ensuring that progress is made
during rebalances.
* Ensure that non-durable data and .meta files are purged from handoffs
after syncing.
* Fixed tracebacks when there's a race to mark a file durable or delete it.
* Improved cooperative multitasking during ssync.
* Upon detecting a ring change, the reconstructor now only aborts the
jobs for that ring and continues processing jobs for other rings.
* Fixed a traceback when logging about a lock timeout in the replicator.
* Object updater improvements
* Added the ability to ratelimit updates (approximately) per-container
using the new `max_objects_per_container_per_second` option. This may
be used to limit requests to already-overloaded containers while still
making progress on updates to other containers.
* Added timing stats by response code.
* Updates are now sent over the replication network.
* Fixed a race condition where swift would attempt to quarantine
recently-deleted updates.
* Memcache improvements
* Added the ability to configure a chance to skip checking memcache when
querying shard ranges. This allows some fraction of traffic to go to
disk and refresh memcache before the key ages out. Recommended values
for the new `container_updating_shard_ranges_skip_cache_pct` and
`container_listing_shard_ranges_skip_cache_pct` options are in the
range of 0.0 to 0.1.
* Added stats for shard range cache hits, misses, and skips.
* Improved handling of timeouts and other errors when obtaining a
connection to memcached.
* Recon improvements
* Added object-reconstructor stats to recon.
* Each object-server IP is now queried only once when reporting disk
usage. Previously, each port in the ring would be queried; when using
servers-per-port, this could dramatically overstate the disk capacity
in the cluster.
* Fixed a security issue where tempurl and s3api signatures were logged in
full. This allowed an attacker with access to log data to perform replay
attacks, potentially accessing or overwriting cluster data. Now, such
signatures are redacted in a manner similar to auth tokens; see the
`reveal_sensitive_prefix` option in `proxy-server.conf`.
See CVE-2017-8761 for more information.
* Added a new `swift.common.registry` module. This includes helper
functions `register_sensitive_header` and `register_sensitive_param`
which third party middleware authors may use to flag headers and query
parameters for redaction when logging. For more information, see
https://docs.openstack.org/swift/latest/misc.html#module-swift.common.registry
* Added the ability to configure project-scope read-only roles for
keystoneauth using the new `project_reader_roles` option.
* The cname_lookup middleware now works with dnspython 2.0 and later.
* The internal clients used by the container-reconciler, container-sharder,
container-sync, and object-expirer daemons now use a more-descriptive
`<daemon>-ic` log name, rather than `swift`. If you previously
configured the `log_name` option in `internal-client.conf`, you must
now use the `set log_name = <value>` syntax to configure it, even if
no value is set in the `[DEFAULT]` section. This may be done prior to
upgrading.
* Fixed a bug that allowed some statsd metrics to be annotated with the
wrong backend layer.
* The `StatsdClient.set_prefix` method is now deprecated and
may be removed in a future release; by extension, so is the
`LogAdapter.set_statsd_prefix` method. Middleware developers should
use the `statsd_tail_prefix` argument to `get_logger` instead.
* Fixed a traceback in the account-server when there's no account
database on disk to receive a container update. The account-server
now correctly 404s.
* The container-updater will quarantine container databases if all
replicas for the account respond 404.
* Fixed a proxy-server error when the read-only middleware tried to
handle non-Swift paths (such as may be used by third-party middleware).
* Some client behaviors that the proxy previously logged at warning have
been lowered to info.
* Removed translations from most logging.
* Various other minor bug fixes and improvements.
swift (2.28.1, xena stable backports)
* Fixed a security issue in how `s3api` handles XML parsing that allowed
authenticated S3 clients to read arbitrary files from proxy servers.
Refer to CVE-2022-47950 for more information.
* Constant-time string comparisons are now used when checking S3 API
signatures.
* Fixed a path-rewriting bug introduced in Python 3.7.14, 3.8.14, 3.9.14,
and 3.10.6 that could cause some `domain_remap` requests to be routed to
the wrong object.
* Improved compatibility with certain FIPS-mode-enabled systems.
* Ensure that non-durable data and .meta files are purged from handoffs
after syncing.
swift (2.28.0, OpenStack Xena)
* Sharding improvements:
* When building a listing from shards, any failure to retrieve
listings will result in a 503 response. Previously, failures
fetching a partiucular shard would result in a gap in listings.
* Container-server logs now include the shard path in the referer
field when receiving stat updates.
* Added a new config option, `rows_per_shard`, to specify how many
objects should be in each shard when scanning for ranges. The default
is `shard_container_threshold / 2`, preserving existing behavior.
* Added a new config option, `minimum_shard_size`. When scanning
for shard ranges, if the final shard would otherwise contain
fewer than this many objects, the previous shard will instead
be expanded to the end of the namespace (and so may contain up
to `rows_per_shard + minimum_shard_size` objects). This reduces
the number of small shards generated. The default value is
`rows_per_shard / 5`.
* Added a new config option, `shrink_threshold`, to specify the
absolute size below which a shard will be considered for shrinking.
This overrides the `shard_shrink_point` configuration option, which
expressed this as a percentage of `shard_container_threshold`.
`shard_shrink_point` is now deprecated.
* Similar to above, `expansion_limit` was added as an absolute-size
replacement for the now-deprecated `shard_shrink_merge_point`
configuration option.
* The sharder now correctly identifies and fails audits for shard
ranges that overlap exactly.
* The sharder and swift-manage-shard-ranges now consider total row
count (instead of just object count) when deciding whether a shard
is a candidate for shrinking.
* If the sharder encounters shard range gaps while cleaving, it will
now log an error and halt sharding progress. Previously, rows may
not have been moved properly, leading to data loss.
* Sharding cycle time and last-completion time are now available via
swift-recon.
* Fixed an issue where resolving overlapping shard ranges via shrinking
could prematurely mark created or cleaved shards as active.
* `swift-manage-shard-ranges` improvements:
* Exit codes are now applied more consistently:
- 0 for success
- 1 for an unexpected outcome
- 2 for invalid options
- 3 for user exit
As a result, some errors that previously resulted in exit code 2
will now exit with code 1.
* Added a new 'repair' command to automatically identify and
optionally resolve overlapping shard ranges.
* Added a new 'analyze' command to automatically identify overlapping
shard ranges and recommend a resolution based on a JSON listing
of shard ranges such as produced by the 'show' command.
* Added a `--includes` option for the 'show' command to only output
shard ranges that may include a given object name.
* Added a `--dry-run` option for the 'compact' command.
* The 'compact' command now outputs the total number of compactible
sequences.
* S3 API improvements:
* Added an option, `ratelimit_as_client_error`, to return 429s for
rate-limited responses. Several clients/SDKs have seem to support
retries with backoffs on 429, and having it as a client error
cleans up logging and metrics. By default, Swift will respond 503,
matching AWS documentation.
* Fixed a server error in bucket listings when `s3_acl` is enabled
and staticweb is configured for the container.
* Fixed a server error when a client exceeds `client_timeout` during an
upload. Now, a `RequestTimeout` error is correctly returned.
* Fixed a server error when downloading multipart uploads/static large
objects that have missing or inaccessible segments. This is a state
that cannot arise in AWS, so a new `BrokenMPU` error is returned,
indicating that retrying the request is unlikely to succeed.
* Fixed several issues with the prefix, marker, and delimiter
parameters that would be mirrored back to clients when listing
buckets.
* Partition power increase improvements:
* The relinker now spawns multiple subprocesses to process disks
in parallel. By default, one worker is spawned per disk; use the
new `--workers` option to control how many subprocesses are used.
Use `--workers=0` to maintain the previous behavior.
* The relinker now performs eventlet-hub selection the same way as
other daemons. In particular, `epolls` will no longer be selected,
as it seemed to cause occassional hangs.
* The relinker can now target specific storage policies or
partitions by using the new `--policy` and `--partition`
options.
* Partitions that encountered errors during relinking are no longer
marked as completed in the relinker state file. This ensures that
a subsequent relink will retry the failed partitions.
* Partition cleanup is more robust, decreasing the likelihood of
leaving behind mostly-empty partitions from the old partition
power.
* Improved relinker progress logging, and started collecting
progress information for swift-recon.
* Cleanup is more robust to files and directories being deleted by
another process.
* The relinker better handles data found from earlier partition power
increases.
* The relinker better handles tombstones found for the same object
but with different inodes.
* The reconciler now defers working on policies that have a partition
power increase in progress to avoid issues with concurrent writes.
* Erasure coding fixes:
* Added the ability to quarantine EC fragments that have no (or few)
other fragments in the cluster. A new configuration option,
`quarantine_threshold`, in the reconstructor controls the point at
the fragment will be quarantined; the default (0) will never
quarantine. Only fragments older than `quarantine_age` (default:
`reclaim_age`) may be quarantined. Before quarantining, the
reconstructor will attempt to fetch fragments from handoff nodes
in addition to the usual primary nodes; a new `request_node_count`
option (default `2 * replicas`) limits the total number of nodes to
contact.
* Added a delay before deleting non-durable data. A new configuration
option, `commit_window` in the `[DEFAULT]` section of
object-server.conf, adjusts this delay; the default is 60 seconds. This
improves the durability of both back-dated PUTs (from the reconciler or
container-sync, for example) and fresh writes to handoffs by preventing
the reconstructor from deleting data that the object-server was still
writing.
* Improved proxy-server and object-reconstructor logging when data
cannot be reconstructed.
* Fixed an issue where some but not all fragments having metadata
applied could prevent reconstruction of missing fragments.
* Server-side copying of erasure-coded data to a replicated policy no
longer copies EC sysmeta. The previous behavior had no material
effect, but could confuse operators examining data on disk.
* Python 3 fixes:
* Fixed a server error when performing a PUT authorized via
tempurl with some proxy pipelines.
* Fixed a server error during GET of a symlink with some proxy
pipelines.
* Fixed an issue with logging setup when /dev/log doesn't exist
or is not a UNIX socket.
* The container-reconciler now scales out better with new `processes`,
`process`, and `concurrency` options, similar to the object-expirer.
* The dark-data audit watcher now skips objects younger than a new
configurable `grace_age` period. This avoids issues where data
could be flagged, quarantined, or deleted because of listing
consistency issues. The default is one week.
* The dark-data audit watcher now requires that all primary locations
for an object's container agree that the data does not appear in
listings to consider data "dark". Previously, a network partition
that left an object node isolated could cause it to quarantine or
delete all of its data.
* More daemons now support systemd notify sockets.
* `EPIPE` errors no longer log tracebacks.
* The account and container auditors now log and update recon before
going to sleep.
* The object-expirer logs fewer client disconnects.
* `swift-recon-cron` now includes the last time it was run in the recon
information.
* `EIO` errors during read now cause object diskfiles to be quarantined.
* The formpost middleware now properly supports uploading multiple files
with different content-types.
* Various other minor bug fixes and improvements.
swift (2.27.0, OpenStack Wallaby)
* Added "audit watcher" hooks to allow operators to run arbitrary code
against every diskfile in a cluster. For more information, see
https://docs.openstack.org/swift/latest/development_watchers.html
* Added support for system-scoped "reader" roles when authenticating using
Keystone. Operators may configure this using the `system_reader_roles`
option in the `[filter:keystoneauth]` section of their proxy-server.conf.
A comparable group, `.reseller_reader`, is now available for development
purposes when authenticating using tempauth.
* Allow static large object segments to be deleted asynchronously.
Operators may opt into this new behavior by enabling the new
`allow_async_delete` option in the `[filter:slo]` section
in their proxy-server.conf. For more information, see
https://docs.openstack.org/swift/latest/overview_large_objects.html#deleting-a-large-object
* Added the ability to connect to memcached over TLS. See the
`tls_*` options in etc/memcache.conf-sample
* The proxy-server now caches 'listing' shards, improving listing
performance for sharded containers. A new config option,
`recheck_listing_shard_ranges`, controls the cache time and defaults to
10 minutes; set it to 0 to disable caching (the previous behavior).
* Added a new optional proxy-logging field `{wire_status_int}` for the
status code returned to the client. For more information, see
https://docs.openstack.org/swift/latest/logs.html#proxy-logs
* Errors downloading a Static Large Object that cause a shorter-than-expected
response are now logged as 500s.
* Memcache client error-limiting is now configurable. See the
`error_suppression_*` options in etc/memcache.conf-sample
* Added `tasks_per_second` option to rate-limit the object-expirer.
* Added `usedforsecurity` annotations for use on FIPS-compliant systems.
* Added an option to write EC fragments with legacy CRC to ensure a smooth
upgrade from liberasurecode<=1.5.0 to >=1.6.2. For more information, see
https://bugs.launchpad.net/liberasurecode/+bug/1886088
* **Known Issue**: Operators should verify that encryption is not enabled
in their reconciler pipelines; having it enabled there may harm data
durability. For more information, see https://launchpad.net/bugs/1910804
* S3 API improvements:
* Fixed a bug that prevented the s3api pipeline validation described in
proxy-server.conf-sample from being performed. As documented, operators
can disable this via the `auth_pipeline_check` option if proxy startup
fails with validation errors.
* Make allowable clock skew configurable, with a default value of
15 minutes to match AWS. Note that this was previously hardcoded at
5 minutes; operators may want to preserve the prior behavior by setting
`allowable_clock_skew = 300` in the `[filter:s3api]` section of their
proxy-server.conf.
* Fixed an issue where SHA mismatches in client XML payloads would cause
a server error. Swift now correctly responds with a client error about
the bad digest.
* Fixed an issue where non-base64 signatures would cause a server error.
Swift now correctly responds with a client error about the invalid
digest.
* Container ACLs are now cloned to the `+segments` container when it is
created.
* The correct storage policy is now logged for S3 requests.
* Added the ability to configure auth region in s3token middleware.
* CORS-related headers are now passed through appropriately when using
the S3 API. Note that allowed origins and other container metadata
must still be configured through the Swift API as documented at
https://docs.openstack.org/swift/latest/cors.html
Preflight requests do not contain enough information to map a
bucket to an account/container pair; a new cluster-wide option
`cors_preflight_allow_origin` may be configured for such OPTIONS
requests. The default (blank) rejects all S3 preflight requests.
* Sharding improvements:
* Prevent shard databases from losing track of their root database when
deleted.
* Prevent sharded root databases from being reclaimed to ensure that
shards can detect that they have been deleted.