added changelog entries from stable releases

Code Issues Proposed changes

Change-Id: Ia2ba8f7a998bc55ba3fba3ce37f1d2974646494f

This commit is contained in:

John Dickinson

2019年02月25日 16:38:07 -08:00

parent 7641fd380d

commit 04a0ff2e96

4 changed files with 91 additions and 0 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

22
releasenotes/notes/2_15_2_release-6996eccabba558b4.yaml Normal file

View File

@@ -0,0 +1,22 @@

---

fixes:

- >

Fixed a cache invalidation issue related to GET and PUT requests to

containers that would occasionally cause object PUTs to a container to

404 after the container had been successfully created.

- >

Removed a race condition where a POST to an SLO could modify the

X-Static-Large-Object metadata.

- Fixed rare socket leak on range requests to erasure-coded objects.

- Fix SLO delete for accounts with non-ASCII names.

- >

Fixed an issue in COPY where concurrent requests may have copied the

wrong data.

- Fixed time skew when using X-Delete-After.

- Send ETag header in 206 Partial Content responses to SLO reads.

11
releasenotes/notes/2_17_1_release-dd6e6879cbb94f85.yaml Normal file

View File

@@ -0,0 +1,11 @@

---

fixes:

- Fix SLO delete for accounts with non-ASCII names.

- >

Fixed an issue in COPY where concurrent requests may have copied the

wrong data.

- >

Fixed a bug in how Swift uses eventlet that was exposed under high

concurrency.

16
releasenotes/notes/2_19_1_release-5072dd72557f5708.yaml Normal file

View File

@@ -0,0 +1,16 @@

---

fixes:

- >

Prevent PyKMIP's kmip_protocol logger from logging at DEBUG.

Previously, some versions of PyKMIP would include all wire

data when the root logger was configured to log at DEBUG; this

could expose key material in logs. Only the kmip_keymaster was

affected.

- >

Fixed an issue where a failed drive could prevent the container sharder

from making progress.

- >

Fixed a bug in how Swift uses eventlet that was exposed under high

concurrency.